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.
Related
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
Just tried to update my ROM from temasek v146 to 147, which is basically like updating from CM11 nightly from the 6th of october to the 11th.
I use this as a reference cause it uses the same base with a few additions.
After the update I noticed that google search kept crashing and that I couldn't do a voice search anymore.
I thought that this was the only problem and flashed again with new gapps and even did a clean install with latest slim gapps, but nothing helped.
When I restore my back up with CM based source from the 6th (temasek v146) everything works fine again.
Any ideas what might have caused this?
Hi everyone, I'm new to all Android development and have tried to build CM 14.1 from source for my Oneplus One.
I ran into some ninja related errors and ended up disabling that in order to get a successful build.
I also had some issues with Gello (v40) causing failures so I edited that out from bacon.mk.
After my fixes I can build the ROM without issues, but when I flashed it to upgrade from 11/22 to 11/23 the CyanogenMod Version listed in my settings shows 11/22 nightly instead of 11/23. There are two log errors when flashing, but I've seen this with basically every 7.0 ROM I have flashed thus far. Otherwise there are no errors when flashing.
I noticed that my ROM for 11/23 is 334.21 MB while the nightly on CM's website is 399.16 MB. I'm not sure why the large discrepancy. I can't imagine Gello would affect it that way
Any help would be appreciated!
Thanks
Edit: So my .zip does have 2 noticeable effects:
1. Browser is installed after flashing
2. Data doesn't work (not sure if this is a bug in 11/23 or my build specifically)
I restored my 11/22 backup after this because I need data.
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.
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.