yashsingh1/xdaforums huggingface dataset:
[Droid Ultra Android Development] kude87:
What did you notice most that the kernel improves upon from the stock CM kernel? I may try it, but right now it's running so well, I'm not sure where to even look for improvements.
[Droid Ultra Android Development] Johnny Wong:
I would say it has marginally better battery life. I'll report back if there are any significant to report but like you said, can't go wrong with the stock. They made a big deal out of it in the Moto X forum so I gave it a shot.
[Droid Ultra Android Development] monsterlucifer:
I have also disabled browser, mail, calendar but haven't disable music as I sometime use that app. I have also allowed root access to ES Explorer.

Haven't made any changes to radio but both GPS and mobile data is working perfectly fine for me. The GPS stays on high accuracy throughout the day and keeps a log of my location history. GPS is also working fine in Google Maps.

I went ahead and changed both status bar icons and edited notification drawer icons, it did said system UI has stopped once but after that it worked fine. I reboot after that and it boot up fine.

PS: I made a backup using TWRP so in case if I get stuck on bootloop like you, I could restore back :P
[Droid Ultra Android Development] .: SID :.:
Finally it works! I think in my case there was useful to wipe internal sdcard.

But now I have 2 issues:

1. Adfree doesn't block ads in apps.

2. If I plug on charge phone which is turned off there is no battery animation as in CM12.1, only Moto logo.

But in other things it works perfect! Thank you very much for new life of my phone! And special thanks for LED patch!!! :good::good::good:
[Droid Ultra Android Development] s_u_n:
This is awesome news (I know I am jumping in quite late).

Just as I was about to restore from my NANDdroid backup, I got to know of CM 13 for the phone.

Somehow nobody is talking about it on the Maxx thread - and all users are discussing here. Well, never mind. :)

If the speakerphone issue is not there for a majority of the users, then I will be installing this one pretty soon.

I have always got the option to go back to my Exodus ROM which has been running fine (except for the occasional reboot, when the flash light is kept on a little longer than usual or something freezes - very rarely though).

Thanks to the OP for bringing in new life and bringing the 2013 Droids up to the latest security patch levels.

You and CM team have done what Motorola refused to do.
[Droid Ultra Android Development] monsterlucifer:
Flashing over cm12.1 after factory reset has seemed to fixed the speakerphone issue for me. I'm now on this rom for a few days and speakerphone is working well!!
[Droid Ultra Android Development] kude87:
Use Adaway instead. That has always been my go-to ad blocker since ICS. Working great on MM.
[Droid Ultra Android Development] Nido221:
These developers are great men to bring the Droids at this stage...
[Droid Ultra Android Development] tom.etc:
has anyone tried F2FS with these CM13s? a quick google didn't really have much to tell me. imma poke around xda here and see if i can't answer my own question.

edit: so it seems CM13 will support F2FS on some devices. attempted. 15m on bootscreen, reflashed n reboot, 30 minutes. nada mas.

edit2: clean FXZ (well, mostly. since i'm unlocked i spliced TWRP2.8.7.0-ghost into to the FXz and removed the md5 from the xml inside. didn't know if that was gonna work but it did. #sweatingstops) not sure if i will persue this further. would be nice just to get cm13 running. i have the same difficulty with this unit as someone in a previous post said. just seems to find ways to screw up during a rather standard install process. ugh
[Droid Ultra Android Development] Nido221:
How did you manage to unlock boot loader at Su 6-7.3 and Android KK 4.4.4 while Sunshine v3.2.6 support says,

.''We currently support most HTC phones, and Droid Turbo, Moto X (2014), Moto X (2013), MotoG (2013) and Droid Maxx/Mini/Ultra on Android 4.4.3 and lower''.

Any help?
[Droid Ultra Android Development] .: SID :.:
I've unlocked bootloader before flashing 4.4.4. ;) And it was a long story to keep phone ready for unlocking with Sunshine.

For me speakerphone works also!
[Droid Ultra Android Development] petech81:
Alright so I am having a problem, installed cm-13.0-20160301-UNOFFICIAL-obake-led , and open_gapps-arm-6.0-stock-20160305.

The problem is that when I go to add my google account I get "There was a problem communicating with Google servers. Try again later"

I've looked and tried to fix it, but nothing works.

Is anyone else having problems with this?

My phone is a Maxx Developer Edition with an unlocked bootloader.
[Droid Ultra Android Development] Nido221:
Thanks, is there any way to try my luck for having an unlock boot loader at this stage (Su 6-7.3 & KK 4.4.4) ???
[Droid Ultra Android Development] .: SID :.:
I don't know such possibility. The only thing for locked bootloader is cleaned from Verizon firmware by Crash][ (http://4pda.ru/forum/index.php?showtopic=516020&st=8500#entry44997215). You may have a root in it and install Xposed module with some extentions. It's good but not so wonderful as 13.0. :)
[Droid Ultra Android Development] bigv5150:
Not unless an exploit is found
[Droid Ultra Android Development] gandhiy:
Thanks notz76 its work... good job...
[Droid Ultra Android Development] murhaava1:
Just in case others were wondering and holding off flashing this, I also tried installing cm12, and then cm13 and the speaker phone is working! So far have not found any other issues with this build (cm-13.0-20160301-UNOFFICIAL-obake-led.zip)
[Droid Ultra Android Development] wgwg:
I've been using this rom for 3 days now on a Droid Mini. It's working very well for me, other than that screen autorotation does not seem to work at all. Has anyone else had that problem?
[Droid Ultra Android Development] inquisitive:
Yeah, I have the same question... . Would love to flash this new ROM. But, from what I've researched so far, no cigar.
[Droid Ultra Android Development] Nido221:
Downgrade, as for as I know would not help also at this stage?
[Droid Ultra Android Development] inquisitive:
I have the exact same question.

It's my understanding that once 4.4.4 is installed on a MAXX or Ultra, it's not possible to go back. And, there is no method to unlock 4.4.4. (only 4.4).

I could be wrong but after much searching this is the conclusion I've come to.

If you find something different please post in this thread because I'd really like to install this ROM.
[Droid Ultra Android Development] thebrasskicks:
Very polished

Just flashed today. I was on cm12.1 and I did a factory reset in twrp and dirty flashed to cm13 with pico gapps. Very stable so far. The only problem I've had is with speakerphone. It's the same problem I had with cm12.1. When the speakerphone button is pressed in call, you can no longer hear the conversation and they cannot hear you until you unselect speakerphone. I'll be using this as my daily driver due to the fact that it is already so polished and runs faster than cm12.1.
[Droid Ultra Android Development] krgarwick@gmail.com:
Use AdAway - works perfectly.

---------- Post added at 06:37 PM ---------- Previous post was at 05:44 PM ----------

:good::good:

Excellent ROM - very fast, very stable. I have flashed multiple versions of LP on my Droid Maxx (unlocked bootloader) but I always ended up reloading Moto 4.4.4 because it worked far better. LP never even approached the battery life of Moto stock.

You have done some really nice work here - I have been blowing off porting CM13 to my Maxx because it's a major pain in the rump. So, I have been waiting for this build with great anticipation.

I have included the files for download (I keep them on my Google Drive). Here's what worked for me:

- Download cm-12.1-20160302-NIGHTLY-obake.zip

https://drive.google.com/file/d/0B_IgzpLrVzMeSC1Qc2pGNzRKbjQ/view?usp=sharing

- Download cm-13.0-20160301-UNOFFICIAL-obake-led.zip

https://drive.google.com/file/d/0B_IgzpLrVzMeNVFUaTQ4d3pxTlE/view?usp=sharing

- Download gapps-601-base-20160224-1-signed.zip

https://drive.google.com/file/d/0B_IgzpLrVzMec2JLUlBlWHl2MHc/view?usp=sharing

- Download twrp2.8.6.0-ghost.img (yeah, I know that it's for a Ghost, but just flash it onto the Obake with mfastboot - it will be fine)

https://drive.google.com/file/d/0B_IgzpLrVzMecXk3RHBRLUs5SUU/view?usp=sharing

*Flash twrp2.8.6.0-ghost.img as your recovery (you can use Flashifly if you want, I just use mfastboot from bootloader mode)

Load both CM builds ad the gapps onto your Droid

*Boot into TWRP and factory wipe (but don't wipe internal memory). Then flash cm-12.1-20160302-NIGHTLY-obake.zip

*Boot you Droid and let it spool up into CM12 but don't bother wasting any time setting up the system. Enable Developer Mode and turn on USB debugging, set ROOT for apps and adb. Boot back into TWRP recovery.

*Now, without wiping anything, setup to flash BOTH cm-13.0-20160301-UNOFFICIAL-obake-led.zip and gapps-601-base-20160224-1-signed.zip MAKE SURE THAT THEY ARE SET TO FLASH ONE AFTER THE OTHER AUTOMATICALLY

*Boot system and there you have it! Google Services should now be working, and you will be running CM13.

*Drop back into TWRP and make a nandroid copy - I keep extra copies of nandroid on my laptop and Google Drive just in case.

Give a shout if you have any problems or if I have missed a step.

---------- Post added at 06:47 PM ---------- Previous post was at 06:37 PM ----------

Excellent suggestion - flashing CM12.1 first, I copied your lead with success. Much appreciated.
[Droid Ultra Android Development] kude87:
I ended up going back to the stock kernel. Tycoo gave me screen flickering upon lock and unlock, a bit of audio crackling, and seemingly less battery life. Stock runs better for me.

Also, TiBu question: Anyone else having issues with converting system apps to user apps? I usually like to convert some of the google apps to user apps so I can easily greenify them because they always wake each other up, but currently they say they convert but never do. Tried twice to no avail. Not really a rom question, but more general.

Edit: Seems TiBu also doesn't remove system apps either. It says it does, but does not. Not sure if it's a 6.0 thing or rom. It does freeze them, though.
[Droid Ultra Android Development] Johnny Wong:
Agreed, I've also gone back to the stock kernel. The Tycoo kernel was giving me a huge wifi related battery drain. Seems to be back to normal now.
[Droid Ultra Android Development] monsterlucifer:
Did you install gapps without rebooting after rom install? I'm on mini opengapps package and have installed about 3 times with no issues.

Follow the unlocking the device instructions on this page: https://wiki.cyanogenmod.org/w/Install_CM_for_obake
[Droid Ultra Android Development] Nido221:
This method do not helpful as it required unlock code from Motorola...

And Droid maxx not eligible for unlock promotion.
[Droid Ultra Android Development] cdfjr1975:
I had the same problem and flashed the gapps package again and it worked. Not sure of the technicals behind it, but happy it was resolved. Hope you find the same success.
[Droid Ultra Android Development] s_u_n:
Several critical vulnerabilities have been patched by Google in this month's security update. I am hoping that we get a new build, which we all can deploy soon.
[Droid Ultra Android Development] .: SID :.:
Is it possible to:

1. ...activate dark theme which included by default in source code? https://twitter.com/intent/retweet?tweet_id=651182873047732224

2. ...add cgarging animation for turned off phone? Now it's just a Moto logo.
[Droid Ultra Android Development] Surmoka:
Hi,

is it possible to painlessly revert back to 5.1 if anything goes wrong with this rom? I've arranged my 5.1 way too much to risk losing it and falling to the ground between two chairs.
[Droid Ultra Android Development] gandhiy:
Last check...My gps not working. are you have fix that ? :)
[Droid Ultra Android Development] MArtyChubbs:
Nandroid backup and restore via TWRP?
[Droid Ultra Android Development] Surmoka:
Of course I can backup and restore. But this is not always possible, now I'm on 5.1.1 and cannot revert back to my 4.4.2 despite it's backed up. TWRP will just not restore correctly, there is some part of the phone that will not be saved.
[Droid Ultra Android Development] MArtyChubbs:
I've had problems downgrading stock roms, but had better success going from CM to stock from Nandroid backups. Good news, I am getting a new phone today (S7E) so I will be the test case for you. I'll keep you posted on the results.
[Droid Ultra Android Development] Surmoka:
Thanks. It is also possible that newer TWRP versions now include full-scale backup. (Never had such problems with Clockworkmod)
[Droid Ultra Android Development] twidave:
I'm liking this ROM so far with only 2 exceptions:

1. For some reason Bluetooth only half works - I can stream music, but I can't make or answer phone calls unless Bluetooth is off first, and then switched on after the call is connected.

2. I was really hoping for Camera2 API. Honestly, the only reason I went to CM12.1 and now CM13 was for Manual Focus... :(

The Led/Flashlight issue from the pull down drawer is no biggie. This ROM is like 99% there. Have used it for a couple of days and really like it.

If I may ask a question of those more experienced than I, these CM ROMs are just patches to KitKat 4.4.4 correct? I mean, they aren't full 5.1 or 6.0 OS's right?

If that is true, would I be better off flashing the Moto X 5.1 OEM ROM? (does it even have Camera2 API?)

Thanks for the great work on this by the way! :)
[Droid Ultra Android Development] notz76:
I have created new builds with latest security patches.

Gesendet von meinem DROID Mini mit Tapatalk
[Droid Ultra Android Development] monsterlucifer:
Many thanks!!
[Droid Ultra Android Development] SnipeR_TT:
Thanks!
[Droid Ultra Android Development] Summersett:
I'm using the updated build, stock gapps from opengapps.org, and TWRP 2.8.7.0, but otherwise wiped System+Data/Dalvik/Cache and then followed the instructions to flash CM 12.1 and flash CM 13+Gapps over it, but my flashlight and speaker phone still aren't working. I'll get over it until a patch is made though; not a big deal to me. Thanks for the great ROM [MENTION=2873535]notz76[/MENTION]!
[Droid Ultra Android Development] monsterlucifer:
Initially, I also did a complete wipe + erase via TWRP then installed this rom and my speakerphone was not working in the first instance. I reverted to stock ROM then. After that, I again did a complete wipe + erase via TWRP. Flashed cm12.1 latest nightly (speakerphone didn't work on cm12.1 either). On this install of cm12.1, I didn't install anything, just booted up clean cm12.1, reboot into TWRP, factory reset and installed this rom followed by OpenGApps. From that day onwards, the speakerphone just worked flawlessly. I again dirty flashed the latest LED rom on my droid mini and so far it works without any issues. May be you should duplicate the steps above and try it out. Flash light issue is still a work in progress as reported by OP and is reportedly resolved using 3rd party app.
[Droid Ultra Android Development] Summersett:
Well I found something interesting...

When the screen is on and I get a call, I hit answer from the heads up notification (or drop down notification) and the internal speaker works fine but speakerphone is muted (I can't hear them and they can't hear me).

When the screen is off and I get a call, I hit answer by swiping the button to the right and the internal speaker is muted (I can't hear them and they cant hear me) but speakerphone works fine!

So screen on/off when receiving the call flipflops the behavior. This is with a complete wipe+erase and flashing CM13. Hope this might help [MENTION=2873535]notz76[/MENTION] fix it.
[Droid Ultra Android Development] kude87:
Couple observations after a few weeks of use:

1) Audio on video recording doesn't have great quality. Sounds a bit muffled and distorted. Nothing huge, but noticeable.

2) Sometimes the camera button is greyed out, and you can't snap a picture unless you clear the camera app from memory. One time I had to reboot entirely. Seems to happen rarely.

3) Bluetooth is sometimes finicky. Works well with my Sync in my car, but for some reason when I call it goes through the phone and not the car. Will do more checking. Also the battery drain with bluetooth is high for me, but will monitor it.

Still easily my daily driver. Great rom.
[Droid Ultra Android Development] s_u_n:
I just installed the latest build from March on my Droid Maxx along with 'nano' OpenGapps.

Coming from TeamEXODUS ROM, the upgrade was very smooth and seamless.\

The speakerphone mode does not work at all during calls. You cannot hear anything nor does the other party hear anything when the Speakerphone is kept on.

I had not wiped Internal Storage but had wiped everything else.
[Droid Ultra Android Development] s_u_n:
Tried a few things from the previous page in order to fix the speakerphone problem.

Since speakerphone was not working on CM 13, I downloaded CM 12.1 from 27 January. I did not download corresponding GApps.

Now, I copied over the file to the device and rebooted to recovery.

Then, I wiped everything other than internal data and then flashed CM 12.1

I could not test if speakerphone worked, because after CM 12.1 was booted, the device would reboot after the 'configure WiFi' stage.

Then I flashed CM 13 and OpenGapps after a factory reset. The speakerphone did not work. The torch worked though in my case, unlike someone else's observation above.

Now, I am trying to restore the device to 5.1 (from Team Exodus).

Edit: Restoring to 5.1 (Team Exodus) landed me into trouble. After restoration, the phone got stuck in the animation.

So, I decided to go back to stock 4.4.

I tried to restore my backup from TWRP (to my stock 4.4). I selected only system and data (unselected boot) in the Restore screen inside TWRP.

Now, I am not sure if that was the right thing to do. The phone got stuck on the "Warning bootloader unlocked" screen.

Adding some of my notes here as I progressed....

So, I again went into Recovery and this time I did a format of cache, dalvik and system. Then tried to restore my

stock 4.4

Again back in the "Warning bootloader unlocked" screen. The phone is sitting on that screen since 3 minutes.

So, again rebooted to Recovery and this time I am trying to restore System, Data and Boot partition. Without this,

the phone is not booting into Android it seems.

So, flashing the boot partition above seems to work. Now, I get the familiar "Droid.." sound.

I was back on Stock 4.4.4

Now, inside recovery, I wiped cache, data, dalvik and system (did not touch internal storage)

Installed CM 12.1

This time CM 12.1 did not have any crashes. I made a test call. Speakerphone did not work.

Rebooted to recovery and did a factory reset. Then installed CM 13 followed by GApps. Rebooted.

Speakerphone still does not work.

The only thing I have not done is wipe "Internal Storage". I don't know if that could be affecting somehow.
[Droid Ultra Android Development] mushbert:
My device is still running 4.2.2, and if I try a newer version I want to maintain the ability to downgrade to it - which means keeping the bootloader under a specific version.

Is a minimum bootloader version required for this ROM (or any others)?
[Droid Ultra Android Development] s_u_n:
The best thing you could do, in my opinion, is to get the bootloader unlocked via Sunshine.

If you have already done so, then you can upgrade to 4.4.4 (stock). This was the last update from Motorola.

You can then install TWRP 2.8.x.x. and then take a backup from the same.

Now, once this backup is in place, you can always try out different ROMS (Android L or Android M). If you don't like them you can simply revert back to stock via the backup taken earlier in TWRP.
[Droid Ultra Android Development] mushbert:
Thank you but I don't believe this answers my question. My understanding is that the bootloader included with 4.4.4 is the element which subsequently prevents downgrades, but that if I were to flash the partitions manually, skipping the bootloader, 4.4.x would still run with the JB bootloader. Unfortunately I don't know if this is the case with Android L or M.

I'm still on JB because there are several aspects of it that I prefer to KK.
[Droid Ultra Android Development] s_u_n:
Well, I am sorry that I do not have an answer to that.

If you prefer JB, then you might as well stick to it. Remember that your phone is missing several critical security patches and Motorola has no intention to fix the vulnerabilities (even on 4.4.4).

----Meanwhile, on my phone, I can confirm that the speakerphone issue causes a major problem.

If I receive a phone while the phone is at rest, I will have to make the conversation in speakerphone mode ONLY. This makes it impractical to have conversations in office. I suppose, I will have to revert back to Exodus ROM running 5.1.x now unless someone knows how to fix this.

I have already tried the solution on the previous page and that did not seem to help in my case.

Edit:

It seems the speakerphone problem is not unique to Droid Maxx. I can see people complaining about this issue on OnePlusOne threads as well right from CM 12.

I tried some of the suggestions on those threads, but was not successful.
[Droid Ultra Android Development] MArtyChubbs:
Anyone else have issues with making a google hangouts video call? I don't see my contacts image. They can see me.

If someone could please test this for me, it would be greatly appreciated.

Running CM13 on XT1080

Thank you!
[Droid Ultra Android Development] kude87:
Mine is working just fine, outside of the usual grainy video quality I always seem to have, on any rom.

Also, speakerphone is working fine for me for others asking.
[Droid Ultra Android Development] s_u_n:
This ROM has been very smooth. Other than the speakerphone issue and the torch issue (torch goes off after few seconds), I have had a positive experience.

BTW: CVE-2015-1805 has been patched a couple of days ago. So, can the OP please try and get that patch for us?

I am continuing for some more time with this ROM, hoping to find a solution to the speakerphone issue.

Edit: I have a strong feeling that the speakerphone issue is this one: https://jira.cyanogenmod.org/browse/CYAN-5728
[Droid Ultra Android Development] kude87:
Anyone having Bluetooth issues? My issues are persisting. When I'm connected to my sync in my car, it plays media fine but does stop for about 2 seconds when you lock the screen. Also, if I try to make a phone call it only goes through the phone. If media is playing and I try to make a call, it locks up my phone. I think it's a bug, but would appreciate if someone could report their Bluetooth usage. Unfortunately if I can't sort this I'm going to have to go back to stock. Just wondering if it's my car's sync that it is not compatible with first.

Edit: this is the exact problem I am seeing

http://forum.cyanogenmod.org/topic/120393-cm13-bluetooth-issues/
[Droid Ultra Android Development] s_u_n:
This sound problem seems to be affecting many phones - including Nexus series.

See this link.

There is a hint that the modem/ radio could be causing this issue when you upgrade to CM 12/ 13.

[MENTION=6852422]monsterlucifer[/MENTION]: Since calling issues are sorted out for you, I wish to ask what is the version of the modem/ radio for your phone?

At the moment all my incoming calls need to be taken on speakerphone.
[Droid Ultra Android Development] monsterlucifer:
Attached.
[Droid Ultra Android Development] s_u_n:
I see I am on a much older modem/ radio MSM8960PRO_BP_232.55.52.00R

[MENTION=6852422]monsterlucifer[/MENTION] You seem to be on the latest MSM8960PRO_BP_23255.132.81.01R

Now, I am trying to see if I could download just the radio from somewhere (instead of downloading the full FXZ.