http://review.cyanogenmod.org/#/c/120142/
Prepare for floodgates, they said. Bacon is on first line, as usual.
CM13 nightlies are ready to start. But they should merge this commit. I don't think we will wait too much, maybe next nightly will be CM13.What are "floodgates"? Does it mean cm13 official nightlies are going to start?
Looks like someone's already ported cm13 to the Moto G.So, floodgates merged. CM13 official nightlies will start soon
[edit]
Sorry, not yet. I was looking at most discussed commit there: http://review.cyanogenmod.org/#/c/118987/
Seem to be last preventing nigtlies from start
Looks like someone's already ported cm13 to the Moto G.
http://www.xda-developers.com/xda-external-link/cyanogenmod-13-lands-on-moto-g-2015/
Hopefully, opo shouldn't be far off. For when it comes - should have a dedicated thread, I think?
i have the official YOG4PAS3JL build in my rooted one plus one.When i try to install this via TW recovery i get error that i cant install this rom over my current rom.what should i do?
I haven't encountered bugs on CM in awhile..Hey why don't you guys bother fixing CM12 first before you start shoving CM13 out the door! I just switched back to CM12.1 on my OP1 since running OxygenOS for about 6 months because I was tired of the bugs in OxygenOS and the complete lack of support from OP for OxygenOS on the 1 and CM12.1 from the "release" channel (the 11/17 build) has been a BUGGY NIGHTMARE.
So apparently my choices are OxygenOS (buggy) or CM12 (buggy). Thanks, guys! Seriously, fire whoever is in charge of your QA department, because they suck. It didn't even take long to find the bugs. My proximity sensor still doesn't turn off the screen during phonecalls, the "detect accidental wakeups" feature is garbage (was preventing waking my phone up when it was sitting in my hand and I was pressing wake several times) and, oh yeah, PUSH NOTIFICATIONS AREN'T WORKING FOR ANY OF MY APPS.
So yeah. Glad to see everyone's rushing to CM13. I'm guessing because they're hoping it'll be less of a mess than CM12 is at present.
And for those of you wondering, I did a clean flash, full wipe, etc.
Latest Baseband version? Show us your version.Hey why don't you guys bother fixing CM12 first before you start shoving CM13 out the door! I just switched back to CM12.1 on my OP1 since running OxygenOS for about 6 months because I was tired of the bugs in OxygenOS and the complete lack of support from OP for OxygenOS on the 1 and CM12.1 from the "release" channel (the 11/17 build) has been a BUGGY NIGHTMARE.
So apparently my choices are OxygenOS (buggy) or CM12 (buggy). Thanks, guys! Seriously, fire whoever is in charge of your QA department, because they suck. It didn't even take long to find the bugs. My proximity sensor still doesn't turn off the screen during phonecalls, the "detect accidental wakeups" feature is garbage (was preventing waking my phone up when it was sitting in my hand and I was pressing wake several times) and, oh yeah, PUSH NOTIFICATIONS AREN'T WORKING FOR ANY OF MY APPS.
So yeah. Glad to see everyone's rushing to CM13. I'm guessing because they're hoping it'll be less of a mess than CM12 is at present.
And for those of you wondering, I did a clean flash, full wipe, etc.
I haven't encountered bugs on CM in awhile..
Sent from my A0001 using Tapatalk
Neither have I lol.. not even on the last 12.1 Nightly
---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------
Downloading now, will report back after flashing
I got it to boot after doing a factory reset and reflashing from twrp. I lost all data though. bootloop over cm12.1 nightly.
-edit- after installing opengapps for 6.0 kept getting system ui and pay store crashes, unusable
CyanogenMod tries to build a new, fresh "nightly" version every 24 hours for each of the devices it supports, which includes the most up-to-date changes to the source code, provided from all over the Internet. Of course, the nightly builds may also contain newly-introduced bugs, but hey- if you feel adventurous, you can help make CyanogenMod better by trying these experimental builds and reporting back bugs to the developers.
1. If you didn't wipe cache / dalvik-ART from recovery when you flashed 12.1 over 12.0, go back and do that first.
2. If you still have FCs, go to Settings » Apps, find the offending app and click Clear data.
3. Still no go, time to do a factory reset.
post to androidfilehost, that seems like a great place for a rom.
Exactly some number of minutes after soon.