[ROM][5.1.1][condor] Official CyanogenMod 12.1

[maosilva]

ohh alright thanks ,but is it necessary ? i mean if i did it with my current recovery would it cause any problems ?

No, it is not necessary! I have indicated because I like to use the latest versions!

 

[Akshay_92]

No, it is not necessary! I have indicated because I like to use the latest versions!

haha...oh thats ok :laugh: ..thanks man:good:

 

[Akshay_92]

Successfully flashed the January nightly so far no issues,a little hiccup here and there with chrome but its quite solid, @maosilva..

 

[Akshay_92]

Music player is "force closing"... It worked seamlessly for a few days ,but now it would close as soon as it opens on the 20160110 nightly ..

 

[Papdya]

Music player is "force closing"... It worked seamlessly for a few days ,but now it would close as soon as it opens on the 20160110 nightly ..

Try clearing data of the music app and rebooting the device.

 

[Akshay_92]

Try clearing data of the music app and rebooting the device.

tried that still the same ,even tried clearing data as well as force stopping and re opening it,it won't work

 

[JimDandy68]

I'm not sure from reading various posts here whether flashing latest pico open_gapps (20161201) over an older pico pa_gapps (20150418) will cause any problems on my Moto E. I'm running the CM12.1 20160401 snapshot, and I've been getting play services errors recently. I thought I might try installing the latest open gapps for the phone, but want to avoid any unwanted issues. Any advice is appreciated. Thanks.

 

[Papdya]

I'm not sure from reading various posts here whether flashing latest pico open_gapps (20161201) over an older pico pa_gapps (20150418) will cause any problems on my Moto E. I'm running the CM12.1 20160401 snapshot, and I've been getting play services errors recently. I thought I might try installing the latest open gapps for the phone, but want to avoid any unwanted issues. Any advice is appreciated. Thanks.

Update your google play services app.

 

[JimDandy68]

Update your google play services app.

(EDIT). Thanks. I see there's an app to determine which version I should use (or just reinstall what I have). Going to try that out.
(EDIT2) For anyone who needs to know, Moto E XT1021 uses the version starting with 234- [so 10.0.84_(234-137749526), in my case].

 

[Papdya]

I allow all updates, freely. Google play services isn't prompting me to update. Is there an apk I should grab separately somewhere?

Download 'play services info' from playstore.

 

[JimDandy68]

Download 'play services info' from playstore.

Well, managed to reinstall with an APK of the same, but no difference. Still getting the error message, randomly.

 

[Papdya]

Well, managed to reinstall with an APK of the same, but no difference. Still getting the error message, randomly.

Lol. I dont know then. I usually used to get that error when my play services would be outdated. Why dont you try the marshmallow roms they are quite stable. Do read the comments though. Cause some CM13 builds are not booting.

 

[JimDandy68]

Lol. I dont know then. I usually used to get that error when my play services would be outdated. Why dont you try the marshmallow roms they are quite stable. Do read the comments though. Cause some CM13 builds are not booting.

I've read none are as stable as this one, and this one has generally been stable, minus this hiccup. I'll search around, but also might try out stock rooted. Thanks.

 

[TigerKing]

I've read none are as stable as this one, and this one has generally been stable, minus this hiccup. I'll search around, but also might try out stock rooted. Thanks.

Not like that.. try wiping cache and dalvik cache.
Or try wiping above and again installing gapps
Or try factory reset then gapps.

Try cm13 Nov 8 build, is most stable with no issues as known. Other updates build have bootloop problems from Nov 13 build to latest Dec 4 build.
Cm14 is still in fast working.

 

[JimDandy68]

Not like that.. try wiping cache and dalvik cache.
Or try wiping above and again installing gapps
Or try factory reset then gapps.

Try cm13 Nov 8 build, is most stable with no issues as known. Other updates build have bootloop problems from Nov 13 build to latest Dec 4 build.
Cm14 is still in fast working.

Thanks for this follow-up. I missed it. I actually moved to that build of CM13 and switched to a different Moto E (had two, one with a broken screen and evidently one maybe with a bad mobo, so I franken-swapped). The phone is actually running quite well now with the 11/8 CM13.

 

[Akshay_92]

hey, i was using the 20160110 cm12.1 nightly on my motorola xt1022 and the recovery is twrp 2.8.7.0 by ashwin007 and it was working really well ,barring the music fc every time ,but i learned to live with it, it didn't bother me that much,to point out this nightly was working flawlessly for 20 odd days ,but today things got a little troublesome ,a couple of my apps started force closing,and they force closed every time i opened them,so i decided to wipe the dalvik cache ,after that it normally booted and started doing the usual '' optimizing apps'' thing but after it finished that the issue wasn't resolved and while i was in the lock screen i normally pushed the volume button to unlock it (as my power button is damaged so i use the volume buttons to control it ) the screen froze and the device rebooted ,and after that it kept stuck in a bootloop ,i decided to re-flash the same nightly with the same pico gapps from open gapps i had ,i wiped everything from the wipe option in recovery except micro-sd and flashed both the zip files in the same flashing session ,the installation went normal but after it booted to the ''welcome screen'' and as soon as i selected the language it rebooted!! on its own! and after rebooting when i was again on the welcome screen but i noticed that i was unable to turn the '' WIFI'' ON but i finished the setup thinking that i would do so manually ,but i was not able to turn the wifi on ,it wouldn't turn on from the quick panel and also didn't from the settings menu ,but as soon as i also decided to check bluetooth boom!!, it was also busted and after that the device keeps rebooting endlessly ...i have no clue whats gone wrong ,i clean flashed the rom again but the issue persists...please help me right now i have to hang around with this device and i can't afford a new one

 

[Ujwal Agrawal]

hey, i was using the 20160110 cm12.1 nightly on my motorola xt1022 and the recovery is twrp 2.8.7.0 by ashwin007 and it was working really well ,barring the music fc every time ,but i learned to live with it, it didn't bother me that much,to point out this nightly was working flawlessly for 20 odd days ,but today things got a little troublesome ,a couple of my apps started force closing,and they force closed every time i opened them,so i decided to wipe the dalvik cache ,after that it normally booted and started doing the usual '' optimizing apps'' thing but after it finished that the issue wasn't resolved and while i was in the lock screen i normally pushed the volume button to unlock it (as my power button is damaged so i use the volume buttons to control it ) the screen froze and the device rebooted ,and after that it kept stuck in a bootloop ,i decided to re-flash the same nightly with the same pico gapps from open gapps i had ,i wiped everything from the wipe option in recovery except micro-sd and flashed both the zip files in the same flashing session ,the installation went normal but after it booted to the ''welcome screen'' and as soon as i selected the language it rebooted!! on its own! and after rebooting when i was again on the welcome screen but i noticed that i was unable to turn the '' WIFI'' ON but i finished the setup thinking that i would do so manually ,but i was not able to turn the wifi on ,it wouldn't turn on from the quick panel and also didn't from the settings menu ,but as soon as i also decided to check bluetooth boom!!, it was also busted and after that the device keeps rebooting endlessly ...i have no clue whats gone wrong ,i clean flashed the rom again but the issue persists...please help me right now i have to hang around with this device and i can't afford a new one

Update the TWRP as well as the ROM . CM 14.1 is very good have a try.

 

[ABSathe]

hey, i was using the 20160110 cm12.1 nightly on my motorola xt1022 and the recovery is twrp 2.8.7.0 by ashwin007 and it was working really well ,barring the music fc every time ,but i learned to live with it, it didn't bother me that much,to point out this nightly was working flawlessly for 20 odd days ,but today things got a little troublesome ,a couple of my apps started force closing,and they force closed every time i opened them,so i decided to wipe the dalvik cache ,after that it normally booted and started doing the usual '' optimizing apps'' thing but after it finished that the issue wasn't resolved and while i was in the lock screen i normally pushed the volume button to unlock it (as my power button is damaged so i use the volume buttons to control it ) the screen froze and the device rebooted ,and after that it kept stuck in a bootloop ,i decided to re-flash the same nightly with the same pico gapps from open gapps i had ,i wiped everything from the wipe option in recovery except micro-sd and flashed both the zip files in the same flashing session ,the installation went normal but after it booted to the ''welcome screen'' and as soon as i selected the language it rebooted!! on its own! and after rebooting when i was again on the welcome screen but i noticed that i was unable to turn the '' WIFI'' ON but i finished the setup thinking that i would do so manually ,but i was not able to turn the wifi on ,it wouldn't turn on from the quick panel and also didn't from the settings menu ,but as soon as i also decided to check bluetooth boom!!, it was also busted and after that the device keeps rebooting endlessly ...i have no clue whats gone wrong ,i clean flashed the rom again but the issue persists...please help me right now i have to hang around with this device and i can't afford a new one

The issue may be causing because of google play services ..(my device too had similar issues when I tried LP ROM with latest open Gapps) You may try older Gapps (banks Gapps or something like that ) . My another device having stock lollipop also had issues with updated play service .If you really want to use lollipop . But it's pretty outdated (from my point of view).. so I'd suggest you to upgrade to marshmallow or nougat :good
Good luck !!

 

[Akshay_92]

Update the TWRP as well as the ROM . CM 14.1 is very good have a try.

i greatly appreciate your advice but i would rather stick with cm 12.1, isn't there a way to fix this ? ..thank you for your advice .

---------- Post added at 05:42 PM ---------- Previous post was at 05:01 PM ----------

The issue may be causing because of google play services ..(my device too had similar issues when I tried LP ROM with latest open Gapps) You may try older Gapps (banks Gapps or something like that ) . My another device having stock lollipop also had issues with updated play service .If you really want to use lollipop . But it's pretty outdated (from my point of view).. so I'd suggest you to upgrade to marshmallow or nougat :good
Good luck !!

I am really grateful and acknowledge the fast response ,but is their any way to fix this issue? , i'd really appreciate if i got this working,as i have an exam coming and i"m without my pc to do any tweaking... I hope you understand

 

[ABSathe]

i greatly appreciate your advice but i would rather stick with cm 12.1, isn't there a way to fix this ? ..thank you for your advice .

---------- Post added at 05:42 PM ---------- Previous post was at 05:01 PM ----------



I am really grateful and acknowledge the fast response ,but is their any way to fix this issue? , i'd really appreciate if i got this working,as i have an exam coming and i"m without my pc to do any tweaking... I hope you understand

As a first step of debugging .. try clean flashing ROM only .. don't flash Gapps
If this works fine .. you can obviously conclude that Gapps are faulty .. if Gapps are faulty .. try some other Gapps

If your ROM is faulty .. try stock optimized ROM (by @lost101) it's available in android development section :good:

Hope this helps