HI,
i've installed the latest nightly (cm-12.1-20160822-NIGHTLY-xt925) for the xt925 and gapps. It was running fine so far but after a while it starts crashing during boot or "optimizing apps" and it starts over again. This happens usually after installing updates from the playstore. My guess is that streetcomplete or mapillary might cause this issue (not sure the clock app crashed often too).
So my question is, has anyone else issues with the latest nightly and found a fix?
Are there any other ROMS available? I couldn't find a lineageos Rom.
I am able to reinstall and i think it will work again buts that no solution if i can't update apps.
I'm not sure which bootloader it currently uses. It has the cyanogenmod recovery installed and wiping Cache didn't resolve the issue.
Thx
bitboy85 said:
HI,
i've installed the latest nightly (cm-12.1-20160822-NIGHTLY-xt925) for the xt925 and gapps. It was running fine so far but after a while it starts crashing during boot or "optimizing apps" and it starts over again. This happens usually after installing updates from the playstore. My guess is that streetcomplete or mapillary might cause this issue (not sure the clock app crashed often too).
So my question is, has anyone else issues with the latest nightly and found a fix?
Are there any other ROMS available? I couldn't find a lineageos Rom.
I am able to reinstall and i think it will work again buts that no solution if i can't update apps.
I'm not sure which bootloader it currently uses. It has the cyanogenmod recovery installed and wiping Cache didn't resolve the issue.
Thx
Click to expand...
Click to collapse
For some reason all the official nightlies i have tried have this issue, some cant even make it past the setup screen. I guess something bad ended up in the sources.
Its not maintained anymore for our devices but one of the best CM12 builds in my experience was Mokee OS. You can run the builds for the Photon Q (xt897) just make sure its the old one- i recall having issues with the more recent builds.
Personally though i have moved on to the Nougat builds. I'm currently running the builds for the xt907 and they work fine with my xt926. The crDroid build seems to be the most stable - https://forum.xda-developers.com/dr.../crdroid-3-8-nougat-xt907-xt905-jbbl-t3697571 The only requirements are you must be running the JBBL and the TWRP version for the XT907 (its linked in the ROMs thread instructions). You also need to format your data and cache partitions as F2FS.
Related
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Have you tried deleting the telephone system app?
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
graphdarnell said:
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
Click to expand...
Click to collapse
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
hardslog said:
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
Click to expand...
Click to collapse
I upgraded to the latest TWRP 2.7.0.1, deleted everything and started from scratch. Everything works great now and using new kernel that clocks to 1.8 is flying.
I have 2 of the same phones (i747M with twrp 2.7.1 for d2att installed)
On one, everything worked flawlessly (the older one)
On the other, I had to talk to a developer of twrp to get twrp working...
Now I just realized that the camera app isn't working. It works fine when I restore to the touchwiz stock rom.
I tried wiping my entire device before installing the new stable build 6 rom for d2lte. I also tried flashing the weekly roms for that device on both phones
the result is the same: camera works fine on the older phone while on the newer one, it doesn't
Someone suggested that this might be a hardware issue.. Basically, the TWRP guys fixed my other problem by pulling the latest cyanogenmod build and compiling a recovery. -So I'm wondering if something can be done to make my camera work again on my new phone...
(Before all of this, I of course tried rebooting, closing other apps, clearing data, etc...)
Update: I tried flashing the latest cyanogenmod nightly (June 30) and the camera app worked, but I prefer slimrom
Another update: all the bug report shows when I reproduce the error is
Device: Slim-d2lte-4.4.4.build.6-OFFICIAL-5242
Kernel: 3.4.95-cyanogenmod-gd56ed95 [email protected] #1
Seems I inadvertently killed my working CM11 opo with 9/30 Nightly
Factory Reset and wiped all data via twrp 2.8.0.1
Installed Nightly, Gapps, Gapps remover, franco r22 and cm11s app pack via USB-OTG
wiped dalvik/cache
reboot to "Unfortunately, the process android systemui has stopped working" > hit ok > infinite repeat
tried to revert to 9/25 and even the M9 snapshot to the same issue
I have a nandroid of when i first got the phone with cm11s on it but no efs backup.
I was using franco r20-updated to r21 just yesterday, Nightly 9/25 just fine with a few issues with certain apps. Figured waiting for a few more days in between nightlies would help with those issues.
Anyone got any suggestions as to what I can do to resolve this? Out of a phone at the moment so in a tough spot.
Factory wipe. Only flash CM11 nightly, flash each zip one by one. One of them is causing your phone to constantly fc.
Seems issue in last CM nightly 0930... Flash 0928 and wait for fix. Affected more (maybe all) devices.
Happened to mine as well. Though I still can't use the cm boot.img past 9/19 either lol
I flashed back 29 nightly and all works fine.
Same issue for me updating to the 09/30 nightly!
@zephiK 9/29 is offline apparently lol
9/28 seems to work (with no other zips done including gapps)
Samsung GS3 - Pulled battery to get control - boot to TWRP and installed 9/28 nightly. All is well. :good:
S5 30/09 can confirm SystemUI crash. On 28/9 atm and fully works.
Autobuilder placed bad commit and built it for all devices.
Hi. After I posted this message, the problem seems to be that my ROM is hopelessly old. But after following the recommendations, I still couldn't update.
I tried to install "cm-11-20141112-SNAPSHOT-M12-moto_msm8960.zip" from ClockworkMod recovery. Got this error message:
Code:
This package is for device: moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish; this device is xt925.
(Status 7)
Installation aborted.
But I was told (and the message on the CM wiki confirms it) that builds have been unified.
What should I do?
Looking for installs for xt925 specifically, the last stable is the one I have, and the few nightlies are very old as well and I doubt would solve the problem.
There is the CM12 nightly for xt925 released today, but since I'm highly dependent on my phone functioning while traveling next week and can't afford things going wrong, I'd rather avoid nightlies and experimental versions unless I have absolutely no alternative to have my phone encrypted.
Advice?
Thanks a lot.
By the way, I prefer to not make a factory reset unless it's necessary.
Is it necessary? Do I have to wipe cache? Wipe dalvik? Some sites say yes, some sites say not needed.
Is the answer different depending on whether I would be upgrading to a more recent version of CM 11 or to CM 12 nightly?
Thanks!
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
That's right, I overlooked that, thank you. Was able to upgrade now.
I thought that because my Android stock was KitKat before I flashed CM11, that the bootloader would also be KK. It was a jbbl, because now it worked.
Everything seems to be working just fine, was no need to clear caches or data or anything. My compass is also now fixed.
I just started encryption and it wasn't locked in the robot anymore, it booted and now shows a progress bar with 4% complete.
Thanks, kabaldan!
Just one more question, will there be CM12 for moto_msm8960_jbbl later, or if I want to upgrade to CM12 I will have to do this kkbl workaround you mentioned?
kabaldan said:
@taylortm Please read again what I wrote to you here: http://forum.xda-developers.com/showpost.php?p=58132610&postcount=2
You can't use moto_msm8960 CM11 builds nor xt925 CM12 build unless you update your device to stock KitKat firmware by Motorola first.
While your device is still using JellyBean bootloader/modem firmware, you can update only to moto_msm8960_jbbl CM11 builds.
Click to expand...
Click to collapse
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.