yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] jdl512:
same issues with May 2 nightly.

Also, this has always been an issue since the previews....no bluetooth sound control on my JBL Charge speaker. it is either full or off. same output regardless of setting. that is as of April 25 nightly since I've been returning to that backup after checking to see if the notifications/tiles issue is fixed. Works on other bluetooth devices like the old inchargehomebt receiver.
[Moto Maxx Original Android Development] siberian85:
This is cm13 thread !
[Moto Maxx Original Android Development] Andrey G.:
The solution of this problem is to wait for the answer in appropriate thread (in which you've already asked same question) and stop flooding around.:mad:
[Moto Maxx Original Android Development] siberian85:
Also one more point, don't have yet, battery mode, in settings>battery
[Moto Maxx Original Android Development] c3pbl4:
Guys, now I have stock 6.0.1 on my MAXX XT1225. Rooted. (before I have CM 13)

How to change on locked screen mic to some other program? (I need phone app)

And how to change camera open from twist gesture to flashlight?

Thanks.
[Moto Maxx Original Android Development] ChazzMatt:
Maybe I'm misunderstanding... But you are dumping CM13 for stock then asking how to have the custom functions of CM13?

Go back to CM13. ;)
[Moto Maxx Original Android Development] ImpheOtus:
LOL, weird post indeed!
[MENTION=5006582]c3pbl4[/MENTION]: You can use xposed module GravityBox (I think that option is there)
[Moto Maxx Original Android Development] jdl512:
Notifications and tiles returned with May 4 nightly. Still getting 'music has stopped' messages throughout everyday when no sound is playing, after booting, etc. Haven't had any lock screen freezes. When that was freezing, you could pull down the notifications screen, but couldn't go anywhere from it. You could also try to open camera , etc from lock screen, but they would crash and return to lockscreen. That seems to be fixed.
[Moto Maxx Original Android Development] leandrodeassis:
Hi, there's a way to record the call automatically without using a third party app?
[Moto Maxx Original Android Development] Jeffy!:
Can someone please help me understand the cell radio battery drain bug? My phone worked beautifully with cm12.1. On cm13 my battery life is awful, I currently have 2 hours SOT and I'm at 41%, unplugged for only 12 hours. Android OS used 20% battery, mobile radio used 15%, and screen 5%. This is 5 days after a completely fresh wipe and install, so it's had time to settle in.

When I flash back to cm12.1 I immediately get great battery again. If I flash to cm13 it goes straight down the toilet. What's going on??
[Moto Maxx Original Android Development] RLShiftyDoggit:
Just go flash the LP radios for your device you'll be back to normal or at least I was

From op #1

This is CM13.0 (Lollipop, Android 6.0.1) firmware for Moto MAXX XT1225 and Droid Turbo XT1254. It's an official build.<br />

<br />

Maintainers: Skrilax_CZ<br />

Credits: CyanogenMod Team<br />

<br />

<b>Disclaimer</b><br />

<br />

<br />

<br />

<font color="Red"><b>Known bugs</b></font><br />

* Wake by voice support not tested and has unknown status<br />

* Support for XT1250 may require tweaking<br />

* VoLTE is not supported on Verizon<br />

<br />

<br />

<b>Source</b><br />

Device: https://github.com/CyanogenMod/android_device_motorola_quark<br />

Kernel: https://github.com/CyanogenMod/android_kernel_motorola_apq8084<br />

<br />

<font color="Red"><b>Unlocked bootloader required!</b></font><br />

<font color="Red"><b>Flash over latest Lollipop or Marshmallow stock SW or flash the following packages to update bootloader & radio (do not downgrade them)!</b></font><br />

<br />

<b>Radio & Bootloader packages</b><br />

XT1225 5.0.2 RETBR (LXG22.33-12.16): http://skrilax.droid-developers.org/cm12quark/QUARK_RETBR_502_RADIO_AND_BOOTLOADER_PACKAGE_2.zip<br />

XT1225 5.0.2 RETEU INDIA (LXG22.33-12.16): http://skrilax.droid-developers.org/cm12quark/QUARK_RETEU_502_RADIO_AND_BOOTLOADER_PACKAGE_2.zip<br />

========================================================================================================================<br />

XT1250 5.0.2 LRA (LXG22.33-12.27): http://skrilax.droid-developers.org/cm12quark/QUARK_LRA_502_RADIO_AND_BOOTLOADER_PACKAGE.zip<br />

========================================================================================================================<br />

XT1254 5.1 VERIZON (SU4TL-44_44): http://skrilax.droid-developers.org/cm12quark/QUARK_VRZ_511_SU4_RADIO_AND_BOOTLOADER_PACKAGE.zip<br />

<br />

Flash steps after you extract the zip:<br />

<br />

<br />

<b>Crossflashing & Configuration Override</b><br />

You can crossflash radio image for a different variant of the phone, but the automated setup will not pick it up. Thus you'll need to manually override it through fastboot:<br />

<br />

<br />

<b>Download</b><br />

ROM & Recovery: http://download.cyanogenmod.org/?device=quark<br />

GAPPS: http://opengapps.org/?api=6.0
[Moto Maxx Original Android Development] siberian85:
how to check what version of radio is on the phone after flashing ?
[Moto Maxx Original Android Development] ChazzMatt:
Settings/About Phone/Baseband version.

Or boot into fastboot and it will show there.
[Moto Maxx Original Android Development] Jeffy!:
Any way to do that without using ADB? I tried flashing from TWRP recovery and it gave me a verification failure
[Moto Maxx Original Android Development] siberian85:
I have successfully flash it via adb very easy, have now cm13 latest nightly and LL radio MDM9625_104438.245.02.85BR but the cell radio bug battery drain is still there :(
[Moto Maxx Original Android Development] ChazzMatt:
If you have an XT1254 Droid Turbo, [MENTION=2730403]firstEncounter[/MENTION] made a TWRP flashable version for radio/bootloader here:

http://xdaforums.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327

BUT it's for XT1254 radio AND bootloader. Be aware of the risks. I'm pretty sure you are still on Lollipop bootloader as you have not installed the XT1225 Marshmallow soak tests (which does not work on XT1254). But you don't want to be flashing a Lollipop bootloader over a Marshmallow bootloader.
[Moto Maxx Original Android Development] Jeffy!:
Thanks! How do I find out which bootloader i've got ? I didn't see it under "About phone"
[Moto Maxx Original Android Development] RLShiftyDoggit:
I'm gonna guess you have a XT1245 droid turbos right now have LP bootloader
[Moto Maxx Original Android Development] Nitefire77:
If you are using the droid turbo, that means your bootloader is unlocked and is the lollipop bootloader, the same as the flashable zip offers. There has been no marshmallow update for the droid turbo and the lollipop bootloader is the latest
[Moto Maxx Original Android Development] Jeffy!:
Thanks!
[Moto Maxx Original Android Development] siberian85:
Very weird battery stats after flashing LP radio currently on latest cm13 nightly
[Moto Maxx Original Android Development] The Horak:
I just wanna report that I'm on the 05.07.16 build with my Droid Turbo, and I have not found any bugs. It's smoother than the 04.23 build that I came from. For the record, I don't use root or anything like that.
[Moto Maxx Original Android Development] syphix:
How's MMS picture quality (usually blurry on Verizon)? How's Bluetooth audio (dropped audio on my Uconnect Chrysler radio)?
[Moto Maxx Original Android Development] The Horak:
As far as I can tell, the MMS thing has to do with Verizon and custom ROMs. But I haven't received one since I flashed. I'm assuming they're still low-res. I never have BT issues with any of these nightlies. The same goes for this one. Some head units/car radios don't play nice.
[Moto Maxx Original Android Development] siberian85:
Anyone know if there would be any changes in Radio once official Marshmallow is released for Brazilian version, or is better to ditch cm13 once Brazilian Version gets official Marshmallow BTW I have Brazil Version of xt1225

---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------

Just said Brazilian 3 times
[Moto Maxx Original Android Development] quantum tao:
Running RR now, which is cm 13 based and MMS pics are back to normal. When I first tried cm13 the MMS pics were crappy.
[Moto Maxx Original Android Development] ChazzMatt:
You can use the Marshmallow radio over CM13.

With the stock Marshmallow image you don't have the features of a custom ROM.

I don't see any advantage of stock ROM...except for possibly radio if it's improved. And you can have that with CM now that [MENTION=5747496]baybutcher27[/MENTION] created TWRP modem backup.
[Moto Maxx Original Android Development] siberian85:
Thanks Chazz what are you think when will most likely Marshmallow get realised for xt1225 (so that I can flash modem/radio only) and when cm13 stable will be up. Thanks
[Moto Maxx Original Android Development] ChazzMatt:
XT1225 owners on Resurrection Remix Marshmallow (which is CM13 based) are already using the radio that came with XT1225 soak test. [MENTION=5747496]baybutcher27[/MENTION] uploaded it as a TWRP backup. You just restore it in TWRP. Should work just fine in CM13.

Here's one who already used that new TWRP feature (to restore modem backups):
[Moto Maxx Original Android Development] The Horak:
Any idea what's different with RR?
[Moto Maxx Original Android Development] syphix:
I've tried the latest RR and I still have blurry MMS pics (on Verizon).
[Moto Maxx Original Android Development] Darevas:
sorry about my stupid question but, what is the difference between that and the pre-installed on CM13?

and what's it used for? :confused:

Thanks! ;)
[Moto Maxx Original Android Development] ChazzMatt:
The one in CM13 is Lollipop radio, which works OK in a custom Marshmallow ROM.

But this one is from the Marshmallow XT1225 soak test #3, which became the official Marshmallow OTA. Even though ostensibly the same version number, something is different.

It's only for the XT1225, and only for people using Marshmallow-based ROMs.

From my sources, there is a Marshmallow soak test going on for the Droid Turbo... So if someone - ahem, quietly - wanted to make a backup of the XT1254 Marshmallow modem files in the newest version of TWRP and send it to [MENTION=5747496]baybutcher27[/MENTION], he could post it with the XT1225 Marshmallow modem. Just don't post it publicly in the forum.

I don't have an XT1254 so I have no issues discussing soak tests for the XT1254. [emoji14] And I keep my sources confidential.
[Moto Maxx Original Android Development] quantum tao:
That would be awesome.
[Moto Maxx Original Android Development] Andrey G.:
CM or RR, or any other such ROM doesn't have any radio, it is only system and boot partitions (no modem etc.). So on CM you are using radio firmware that came from your last stock ROM until you intentionally change it.
[Moto Maxx Original Android Development] ChazzMatt:
Radios are supplied in this thread, in the op post. Go look at all the radios in post #1 of this custom Marshmallow ROM. All Lollipop radios at this point.

That's what we are talking about. And it's what people frequently re-flash.

But now at least XT1225 users on Marshmallow custom ROMs (CM13, RR, Mokee) can have Marshmallow radio without having to go to Marshmallow soak test.

And soon so can XT1254, if people on that soak test will backup and share their modem files.
[Moto Maxx Original Android Development] Andrey G.:
He told "CM built-in radio", " built-in" and "provided with this thread" are not the same things, moreover, "built-in radio" is not depending on CM and different among Quark models according to what I've said earlier, agree? So IMHO "CM built-in radio" is confusing, wrong definition.
[Moto Maxx Original Android Development] quantum tao:
I'm not sure if something was changed in RR or cm. But last time I tried cm13 pics were blurry, I couldn't read the text on a pic of a document. I switched back to cf1.3.0 and then on to RR. I went back to this same text message and could read the text in the picture perfectly. I use Verizon message+.
[Moto Maxx Original Android Development] ChazzMatt:
OK, true. But I understood him to mean the radios being used with CM13. Yes, he wasn't using the proper wording but I understood what he meant. However you are correct in educating users that radios aren't actually integrated into custom ROMs like CM13, RR, Mokee. They are however, often supplied as add-ons -- like GAPPS. They are prominently listed with instructions in pos #1 of our ROM threads.

There's been a lot of discussion about re-flashing radios, especially for those few people with GPS issues. I myself have not had those issues but I flashed India radio (actually the entire 5.0.2 ROM) over my Puerto Rico XT1225 a year ago -- before I went to CM12 -- and since then I've flashed just the Puerto Rico radio part back over my XT1225 after moving to CM12.1.

[MENTION=5747496]baybutcher27[/MENTION]'s method of backing up Marshmallow radio in newer version of TWRP and making that file available is quite an improvement over having to flash in ADB -- especially for people who don't have access to Windows easily. Plus it's the only way for people to get Marshmallow radio in custom Marshmallow ROM without first having to install stock Marshmallow.
[Moto Maxx Original Android Development] drizzzzzz:
In the changelog for the upcoming update, there is this:

quark: remove chop-chop from gestures

Anyone know what this is about?
[Moto Maxx Original Android Development] ChazzMatt:
It was also removed in stock Motorola XT1225 Marshmallow ROM. Was in soak test #1, but removed by #3. People have complained. They want it back. Looks like CM is copying Motorola?
[Moto Maxx Original Android Development] drizzzzzz:
Hmm, that's awful. It's one of the best features of the phone..

Looks like I'll hold off on updating, as I don't know of any workaround...
[Moto Maxx Original Android Development] Andrey G.:
If they'll continue such Motorola copying further, soon they'll leave us without updates just like Motorola does. :D:D:D
[Moto Maxx Original Android Development] Polarisfff:
Hi,

do you also have slow camera opening and whatsapp chrashs by playing videos and photos?

Latest nightly.

Greetings
[Moto Maxx Original Android Development] ChazzMatt:
Yeah, someone asked for it to be extracted from soak #1 as it was still there but taken away in soak #2 and #3. But no one ever answered.

From the Soak Test Thread:
[Moto Maxx Original Android Development] svprm:
I have a issue of slow camera opening but not a whatsapp crash.
[Moto Maxx Original Android Development] gimpy1:
Deleted wrong thread. ?
[Moto Maxx Original Android Development] jdl512:
any ideas on why I can't see my contacts stored under 'phone' ? I am now on the latest may 10 nightly Verizon turbo and they are there but contacts app won't display them.
[Moto Maxx Original Android Development] quantum tao:
Software update test survey emails are out so hopefully very soon for Verizon quark mm kernel.
[Moto Maxx Original Android Development] Skrilax_CZ:
The reason is proprietaries have been updated to soak #3 as well. It'll keep it disabled until I learn more about why it was disabled.
[Moto Maxx Original Android Development] Steve One:
Could someone please explain the proper way to update nightly’s using twrp please. For instance do you need to flash gapps again also?

Edit found it. Thank you very much.
[Moto Maxx Original Android Development] drizzzzzz:
The app "ClickLight" works really well as a replacement. Tap power twice to turn on/off.
[Moto Maxx Original Android Development] ironhiro:
I flashed it but it reboots when calling. Is it bug?
[Moto Maxx Original Android Development] iiWoodstocK:
Settings -> Apps -> gear icon -> Default apps -> Phone app

It's because your GApps installed Google Dialer, and it needs to manually be set as the default app, otherwise it will cause reboots anytime you make or receive a call
[Moto Maxx Original Android Development] andray:
It's not good at all that Ambient Display turns on the screen when carry the phone in hand and then I unpredictably press different control buttons. Like audioplayer's Next button.
[Moto Maxx Original Android Development] quantum tao:
YeS, happens to me too. I prefered moto display. Some people around think ambient display is better because it has more options.
[Moto Maxx Original Android Development] ChazzMatt:
1) Ambient Display only works with a locked screen. if your screen is LOCKED how are you pressing "buttons" you don't want?

2) Turn off those the ambient display options if you don't like them. Like "pickup"? Please look at the various options. That still doesn't address point #1, which makes no sense. But if you don't want Ambient Display coming on when carrying the phone, turn off the pickup option.

Unless you have "show all notifications" on a locked screen (including music app controls?) -- which is ANOTHER option you can turn off.

I carry my phone too and with pattern lock ambient display doesn't make me do anything I don't want to do. Again, your screen has to be locked (swipe/pattern/passcode) for Ambient Display to work.

You don't have to enable all options, if you don't want them.

Same to you. ;) That's why the options are there, to use or not use.
[Moto Maxx Original Android Development] The Horak:
Yeah, if we turn off everything that we want to do with our phones, and nothing is enabled, then yeah, I guess nothing will go wrong. I think their point is that with Moto display you can have lockscreen music controls and you don't need a swipe password, and yet you still never have accidental pressing. Moto Display uses more sensory input to help make sure that accidental touching doesn't happen. Telling people not to use features that they want to use is never a good answer.
[Moto Maxx Original Android Development] andray:
Well, i meant that i *LIKE* Ambient Display but it acts like black&white lockscreen allowing me to press control buttons.

I need to press Power button to show real lockscreen, which prevents me from accidental clicks. With Ambient Display we don't have such a protection.

So.

It would be good to have an option which blocks all input on Ambient Display screen (except for unlocking of course). And it would be incredibly cool to have an option which switches Ambient Display to old good lockscreen on double click only.

Of course i can just switch off "show all notifications" as you said.
[Moto Maxx Original Android Development] ChazzMatt:
It's not that you turn everything off. Look at the options below. With Moto Display it's either off or on, you have no control.

With the CM dev's implementation of Ambient Display which is so much better than the "Ambient Display" in phones that don't have IR sensors like ours, it takes the same functions of Moto Display but gives you more control.

Maybe you just need "wave your hand" but you don't need "pickup" because you carry your phone a lot in your hand apparently. I don't carry my phone a lot in my hand, I have a belt holster for that. When I do carry my phone, I'm not usually playing music.

---------- Post added at 10:25 AM ---------- Previous post was at 10:21 AM ----------

The double click idea is good. Maybe the CM dev would be interested in investigating that.
[Moto Maxx Original Android Development] quantum tao:
this is not correct but you keep repeating it.

you can toggle " wave to silence".

you can set what app notifications appear and content.

you can set the display to stay on when looking at it.

it is definitely not all or nothing.

and regarding the point that caused this ambient display discussion: moto display never woke up in my pocket and somehow did stuff like send gibberish text messages or assdial my phone, ambient display has.

https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/103951/related/1
[Moto Maxx Original Android Development] ChazzMatt:
How can a locked display "assdial" your phone or send text message? Please tell me how. You must have a magical phone.

The answer is you are UNLOCKING your phone. You must have simple swipe to unlock. And that is not Ambient Display it is YOU.

You are unintentionally unlocking your phone and assdialing and sending text messages.

Change it to pattern or passcode.

(There is an "emergency call" function on a pattern/passcode screen, but it won't send text messages, so that's how I know you probably have swipe to unlock function. :rolleyes: )
[Moto Maxx Original Android Development] quantum tao:
i use a pin, but that is not a solution if you use smart lock. my point is still valid, this did not happen with moto display.

moto display is just as configurable and more reliable than ambient for me.

it is my opinion that moto display is better. just because you think ambient display is wonderful doesn't mean everyone else has to.

and i mean you no dis-respect, as i consider you a valuable member of xda.
[Moto Maxx Original Android Development] ChazzMatt:
OK, now we are getting somewhere. I use Smart Lock, while I also use Ambient Display with a pattern code. But if you are using Smart Lock, your display is NOT locked under certain conditions.

If you are using Smart Lock, meaning your display is NOT locked while connected to certain trusted devices like Bluetooth or ON YOUR BODY, then THAT is why you are pressing controls and such. Your display is NOT locked. Ambient Display only works when the device is locked.

If your display is unlocked, then at that point Ambient Display has NOTHING to do with the issue. IF Ambient Display was on and you were sending text messages you would have a magical phone. That's why I knew Ambient Display was not involved and somehow you were unlocking your phone. I suspected you were swiping to unlock (thus turning off Ambient Display), but Smart Lock options will also keep you UNLOCKED, so Ambient Display is NOT activated.

You are blaming Ambient Display when Ambient Display isn't even on! Ambient Display is NOT activated until the display is LOCKED.

Do you (or did you) have ON BODY DETECTION option enabled?

Turn off the Smart Lock option that is causing the device to remain unlocked while you are carrying it. STOP blaming Ambient Display, which has NOTHING to do with the issue! It's your Smart Lock options which are causing the issue...

I also use Smart Lock, but only for my Pioneer stereo and Jawbone headset. In both cases, my phone is either mounted on my windshield or in my view so I know what buttons I'm pressing. I would NEVER have my phone unlocked where I couldn't see it (like in my pocket).

If your display were locked it would be impossible to send text messages.

Plus, it's not even clear when you last used Ambient Display. It seems you may be back on stock-based ROM?
[Moto Maxx Original Android Development] quantum tao:
that is the issue, moto display worked fine with it.

or better yet: you're right moto display pales in comparison to ambient display, i am an idiot for expecting smart lock to work well with ambient display, the phone waking up in my pocket and doing its own thing is 100% my fault even though it never happened in 1+ years of using moto display. I am totally irresponsible and should take credit for my mistakes.

a poem:

ambient display is great, i should just kill myself.

i made the big mistake, i should just kill myself.

my fault it comes awake, i should just kill myself.

these voices i just can't shake, i should just kill myself.

ChazzMatt has sealed my fate, i should just kill myself.

ambient display is great, i should just kill myself.

:silly: