I'm confused, I've been doing the CM nightlies for months, v5.02 and just downloaded and installed the latest nightly, v5.02. What are you talking about in your post? Is there some other nightly that I don't know about?FYI: http://review.cyanogenmod.org/#/c/104986/
The cm12.1 d80[01,2,3] builds have been approved for nightlies. People are going to get excited. There are some things you should all be aware of.
- The builds are bumped, not lokified
- This isn't the same adapted JB/KK kernel as on cm12, it's the CAF lollipop kernel
- You should NOT simply upgrade from cm12.0, a clean cm12.1 install should be followed
- There's a lollipop bootstack that should be installed for this, the builds will NOT install if it isn't present
From my experience, this release will be far more stable than 12.0, probably owing to the fact that it isn't based on the JB kernel. The CAF nature of the new kernel means that you can't just upgrade from 12 to 12.1. It also means that the stock LP radio (and KK radio) will work just fine without modification, no need for special "AOSP" versions. There are asserts on the install that will keep the build from installing without the right bootstack. I'll post back once I know where the upload for that is finalized.
The only real-ish issues I've had are: 1) full on UI crashes (looks like a reboot) during calls, most likely because I didn't realize that my phone was on the KK bootstack (haven't seen this bug since upgrading my bootstack); 2) Kernel uses stock G2 lollipop power driver for the chargers, which means it will be less forgiving to crappy chargers. When I upgraded to 12.1, my charger went from charging my phone fully in a couple of hours, to requiring 8 hours or more. If you see this after the upgrade, switch to a better charger. Unless you can personally dedicate the time to port the modification from the last kernel, it is unlikely to be "fixed".
I'm posting this because I'm concerned that people will just go and flash this all willy-nilly, and that is more than likely a bad idea.
That being said, I'm fairly certain the upgrade is worth it for all curious parties. And as always, do a full backup before attempting ANYTHING and have a full backout plan ready in case you royally screw up your phone.
Great explanación. Maybe we will need another thread for cm12.1 right?That is correct. When I wrote this the latest round of nightlies (the weekly/monthly cm11 and cm12 forced rebuild) had already been started. I think the build date/time is based on when the build started in GMT.
The post is specific enough that I'm definitely talking about CM-12.1 (Android 5.1.1). The link is to the change that enables the builds for our device(s) in jenkins (the build system). Once the next round of builds start, d800 (and 801/2/3) builds should begin. Other than potential issues with the build (which are always possible) we will see CM-12.1 officially become a supported build.
If I had to guess, judging by the build times for amani as the first alphabetical build target for cm12.1, and if I guessed right about GMT, the new build run should begin in about 3 hours (6pm EST). Once the new build run starts, cmxlog should remove the d800 from the list of CM-12 logs and add it to the list of CM-12.1 logs. However there won't be any logs till the first build is complete. Judging from the times for the d850 (at&t g3, likely the build right before ours), we should see the builds pop up 1.5-2 hrs later (8pm?). These are all just guesses. With my luck, the builds will fail for a typo.
I've been running CM-12.1 for some time now. Anyone that knows how to build CM themselves will have been able to build for the d80X series themselves for the past month. I've been helping test the many changes under the hood that have been necessary for the upgrade. The kernel is all new and required quite a bit of work, and this took some time. And CM-12.1 added some requirements before builds were allowed, and those needed to be satisfied as well.
I'm hoping many people will be as happy with 12.1 as I have been. However there are some major changes necessary with the upgrade path due to the new kernel, and I want to make people aware of them so that they don't go bricking a phone, or losing a working installation, or ending a marriage cuz they monkied with their wife's phone.
Anyone else having problems with the phone rebooting while streaming music via bluetooth? Happened to me several times today while I was driving. Running 20150817 currently, noticed it happening on 20150822 as well.
I also had several lock ups on the phone while in a voice call over my bluetooth headset on the 20150822, but nothing like that on 20150817.