Just installed latest CM12.1 along with gapps latest pico (1204). Install all OK but on first boot it gets stuck at the "no sim card installed" screen. Every time I hit skip play services stop and then I'm back at "no sim card". Have restored to previous working backup of CM from 1202 (CM of 1203 was also OK but no otg).
Going to retry with earlier gapps in case that was the problem. Anyone else had similar?
Gapps Problem
I have heard reports of people having trouble with Gapps on 12.1 for the fire. From what I understand you have to use the ARM Pico Gapps for it to work properly. That is what I used and have never encountered the problem you are describing.
QUEW1134 said:
I have heard reports of people having trouble with Gapps on 12.1 for the fire. From what I understand you have to use the ARM Pico Gapps for it to work properly. That is what I used and have never encountered the problem you are describing.
Click to expand...
Click to collapse
Yes, using pico and no probs with two previous builds of CM12.1, only with today's build. Unfortunately I can't find either yesterday's CM build or gapps, thought I'd saved them. Going to try today's CM again with the only other gapps I have which is from a week or so ago.
Re the above, what are the risks of doing a more complete wipe in twerp before installing a rom? So far just doing a factory reset and flashing over but would like to make sure I wipe any existing gapps otherwise I suspect that an older version will not update a newer. Is it safe to wipe the system partition?
I am also having this issue installing the latest version of CM. Just got my tablet today so I don't have any previous versions of the rom or gapps to test with. If you find links to older versions of these can you let me know.
Hokie99 said:
I am also having this issue installing the latest version of CM. Just got my tablet today so I don't have any previous versions of the rom or gapps to test with. If you find links to older versions of these can you let me know.
Click to expand...
Click to collapse
I can't find yesterday's version of ggow's CM but for an earlier gapps you can go to rootjunkies download site at rootjunkysdl.com and in the "Android Fire 5th gen" section under CM12 there are earlier versions of both CM and gapps.
Where I am now is with a working version of today's CM12.1 (to whit, 20151204) which I flashed over a restore from a couple of days ago without installing gapps so that I'm using the gapps that were in the restored setup, those, I think, are from the 1st or 2nd of this month. So far all seems fine but I've only just down it so there's not been much testing (eg. Otg)
It's also worth getting rootjunkies "SuperTool" as it has a convenient option to boot recovery when you have trouble starting twerp (at least it helped me)
kramalot said:
I can't find yesterday's version of ggow's CM but for an earlier gapps you can go to rootjunkies download site at rootjunkysdl.com and in the "Android Fire 5th gen" section under CM12 there are earlier versions of both CM and gapps.
Where I am now is with a working version of today's CM12.1 (to whit, 20151204) which I flashed over a restore from a couple of days ago without installing gapps so that I'm using the gapps that were in the restored setup, those, I think, are from the 1st or 2nd of this month. So far all seems fine but I've only just down it so there's not been much testing (eg. Otg)
It's also worth getting rootjunkies "SuperTool" as it has a convenient option to boot recovery when you have trouble starting twerp (at least it helped me)
Click to expand...
Click to collapse
Downloaded the version of gapps from rootjunkies site and and all seems to be working now. Thanks for your help.
Hokie99 said:
Downloaded the version of gapps from rootjunkies site and and all seems to be working now. Thanks for your help.
Click to expand...
Click to collapse
Guess its a problem with the latest gapps build, or an incompatibility between gapps and the latest CM.
OTG is now working for me but with the problem that when a USB drive is removed android seems to think that the SD card is gone and invalidates any apps stored on it ( though it is still available in file manager) until a reboot. This is is not unique to CM so I suppose it's an android problem; the same thing happens on my Hudl2 running kk4.4.4 and my Moto G running L5.1, though on the Hudl2 you can get around it by just yanking the USB device without unmounting.. Makes using otg a real pain!
I have been having this problem as well. I installed the latest CM12.1 with the latest OpenGAPPS and the play store (google services) kept crashing repeatedly. I tried all the different latest GAPPS. and nothing would work.
The GAPPS from rootjunkies 20151120 did however work. Thanks for pointing me to that version.
I cant seem to find a reliable gapps for CM12.1, SlimLP and Resurrection Remix. I have tried Dankomans slim mini, TkGapps, OpenGapps pico, nano, full, they all install just fine but then when the system boots and i try to login to the play store to update my apps they all start 505ing and its usually just google apps and services, i seem to be able to install other non google apps just fine.
If someone could help point me in the right direction i'd really appreciate it, ive been flashing for hours, im at my wits end. :crying::crying::crying:
NightCrayon said:
I cant seem to find a reliable gapps for CM12.1, SlimLP and Resurrection Remix. I have tried Dankomans slim mini, TkGapps, OpenGapps pico, nano, full, they all install just fine but then when the system boots and i try to login to the play store to update my apps they all start 505ing and its usually just google apps and services, i seem to be able to install other non google apps just fine.
If someone could help point me in the right direction i'd really appreciate it, ive been flashing for hours, im at my wits end. :crying::crying::crying:
Click to expand...
Click to collapse
Open GAaps arm/5.1/nano works fine. Your problem lies elsewhere. Be sure to do a full wipe and flash GAaps concurrent with rom. Leave FlashFire defaults alone.
I tried to use Open Gapps and it didnt work for SlimLP, so I installed CM12.1 with Open Gapps, I am getting the same problems with CM12.1, So i said lets try another rom, I installed Resurrection Remix, same problem, so i tried tkgapps same thing. why is it 505ing with every gapps package and rom that i Use? is there something im doing wrong? Perhaps the newer builds on open gapps have probelms? Should i try an older build? I am using flashfire 0.53
Here is what i do when flashing list order first to last:
1. Wipe: System Data, 3rd Party apps, Dalvik, Internal storage, Cache Partition
2. Install Rom.xxx.zip (default ff settings)
3. install SuperSU (default settings)(if necessary)
4. Install Gapps package (Default ff settings)
everything goes through smoothly, i get to a good running environment. Then, once I add my google account and open the store, it attempts to check for updates. Updates are usually available for google webview etc, they all fail with a 505. Tried, removing account then signing back in, changing time, clearing cache stopping processes, nothing seems to solve the issue.
so ive finally encountered a solution to at least get everything running. Install CM12.1 with TKgapps (tk_gapps-modular-pico(uni)-5.1.1-20150920-signed.zip) NOT opengapps. Not sure why opengapps isnt working right now but its not, with no rom that i have tried (fire 7" 2015) other versions of tkgapps didnt work either they also 505ed on me, but these ones work great.
You can find them here:
https://basketbuild.com/devs/osm0sis/gapps
Still hoping for good working gapps for SlimLP (my favorite so far)
yeah... so even after all of that, i woke up just to find it 505ing again. fml.
i have never had this problem with any rom for any other device, EVER. this is so frustrating.
I gave up on finding a fully functional gapps package for any roms on this device. What I did is just force update every apk 505ing on me through ADB. Everything is running smoothly now. Will update if anything changes. (should have done this like 5 hours ago... but when you are tired you dont think straight... hahahaha)
:crying: :cyclops:
NightCrayon said:
I gave up on finding a fully functional gapps package for any roms on this device. What I did is just force update every apk 505ing on me through ADB. Everything is running smoothly now. Will update if anything changes. (should have done this like 5 hours ago... but when you are tired you dont think straight... hahahaha)
:crying: :cyclops:
Click to expand...
Click to collapse
Sorry to hear of all the problems w/GAaps packages. Seems to be a 1-off as a large community uses Open GAaps on this device w/o issue. Multiple ROMs.
I just flashed 7.1.1 LineageOS 14.1-20170321-nailyk-z3c via TWRP.
I installed Gapps micro and after I read something about fixing the problem via Gapps I cleared dalvik cashe and flashed Gapps mini after this, still got no effect.
Somebody got the same problem?
At this moment I found a workaround to install the App "DisableServices" and I disabled in Google Play Services "CheckInService" but no effect too ...
sleep0r said:
At this moment I found a workaround to install the App "DisableServices" and I disabled in Google Play Services "CheckInService" but no effect too ...
Click to expand...
Click to collapse
Install latest version, calls works fine
https://forum.xda-developers.com/z3-compact/orig-development/rom-unofficial-lineageos-14-1-t3577224
Thanks Kunqa, and after that what do you think will be the best Gapps package to add? Mini, Micro ...? ?
I installed the latest version, had Error 7, fixed the ROM and go on ...now I got Lineages Android 7.1.2, Gapps Nano and after all I flashed AddonSU to get root back, it works.
Good to know XDA!
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
I have Resurrectionremix and Magisk 14.3
No any lag on my phone.
Tapatalk - Xiaomi Mi6
You need to list what modules you're using.
BIGWORM said:
You need to list what modules you're using.
Click to expand...
Click to collapse
I only flash the ROM, GApps and Magisk without any additional flashable ZIPs.
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
yung40oz84 said:
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
Click to expand...
Click to collapse
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
irfanfadilah said:
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
Click to expand...
Click to collapse
Ya I was gonna say cause I use all AOSP and CAF based
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Danilo-Sanchez said:
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Click to expand...
Click to collapse
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
Yes.
Try it and let me know if this also fix the problem for you.
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
dragos281993 said:
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
Click to expand...
Click to collapse
I'm glad I'm not the only one experienced this issue, that's mean it's not entirely user fault. Maybe you're right, on more high-spec phones they won't really notice the lags/stutters.
Looking forward to the news/updates regarding this issue.
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Camandros said:
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Click to expand...
Click to collapse
I haven't got the chance to try it.
Currently I'm using SuperSU to root my device.
I tried installing magisk on my currently in use ROM, i.e., a long time after flashing it, and although it got less laggy, there still was a heavy lag impact in some applications. Maybe it has less impact on lineage or on lighter ROMs? I'm using official LG nougat.
I'm using Mi 6 in Xiaomi.eu rom
YES, magisk causing laggy.
Same here
Mi5, tested on MIUI 9 and 10
Without Magisk everything was great and after flashing Magisk, the phone got laggy!
I have the same problem with my LG G6
interesting, first I thought that emmc will be broken. because the problem is the same (lag). but after i replace emmc, all back is fine. I just think emmc is broken because it is often flashing rom.
ChessPiece said:
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
Click to expand...
Click to collapse
what magisk version 16.0 or beta? magisk can't make the phone lag but kernel or something in ROM may interrupt try to change kernel or flash the lastest Gapps
Every time I flash a ROM based on LP or MM, after completing my setup and installing all apps my phone just goes into a boot loop...?
I've tried RR, DU, Turbo, Bean stalk, Tesla, Lineage Os... But all ended in boot loop... Can anyone explain me why this is happening?:crying:
It is a bug in the gapps, a while ago I was able to use the MM roms using a gapps of 2017/04
But last week I tried to use some MM's Roms again, but after a few minutes on it with those same gapps that work, I did not go into bootloop, but rather I received FC from the home screen (regardless of the launcher) and it was impossible to use the appliance
Anyway, if you want to use some rom MM or LP, your only option will be to stock unfortunately
Princknoby said:
It is a bug in the gapps, a while ago I was able to use the MM roms using a gapps of 2017/04
But last week I tried to use some MM's Roms again, but after a few minutes on it with those same gapps that work, I did not go into bootloop, but rather I received FC from the home screen (regardless of the launcher) and it was impossible to use the appliance
Anyway, if you want to use some rom MM or LP, your only option will be to stock unfortunately
Click to expand...
Click to collapse
Did u try bean gapps or Delta gapps? Or without gapps...?
!!!!!!!Root2!!!!!! said:
Did u try bean gapps or Delta gapps? Or without gapps...?
Click to expand...
Click to collapse
I tried OpenGapps, it was the only very old one I had, but it no longer works
Princknoby said:
I tried OpenGapps, it was the only very old one I had, but it no longer works
Click to expand...
Click to collapse
Just when I was going to try RR without gapps. Found this...