yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] nik1180:
CM 13?
[Moto Maxx Original Android Development] lkthomas:
Is it exists?
[Moto Maxx Original Android Development] Shooting Star Max:
Don't ask for ETA, it's not ready yet. Our developer has been working with his second Quark device to bring CM13 to us.

Not yet.

By the way, good news. Motorola has released the source for the 2014 Moto X (aka Victara), so it might be useful for us Quark people. Anyway, I hope Motorola releases the source for our phones too.
[Moto Maxx Original Android Development] NeoWave:
I disabled "waking up" for Google Play services in the privacy manager. Now i have no more power drain on standby
[Moto Maxx Original Android Development] pmortari:
What is the impacts of doing this? I know, it will prevent it from waking up the device, but what exactly this can do (mostly in a negative way, I mean)? Does anyone knows?
[Moto Maxx Original Android Development] meskes:
My Samsung fandom began and ended with the SIII. I'm glad to be back with Motorola.

Sent from my DROID Turbo with Tapatalk. Now with that CyanogenMod goodness.
[Moto Maxx Original Android Development] lkthomas:
It's hardly go wrong with Motorola
[Moto Maxx Original Android Development] itsdubai:
Ok hey guys last night my phone died and I passed out. I woke up and it was dead. I plugged it in and it booted normally. I played with it for a few minutes and then everything went haywire, everything was force-closing etc. I turned it off to boot into recovery mode to wipe cache but it will boot into "fastboot_secure" and then when I try to select boot "recovery", screen flashes and just comes back to "fastboot". The phone won't boot and won't boot into recovery. Any ideas? Thanks

EDIT: When I scroll to Bootloader Logs, it says "failed to validate boot image" and Fastboot Reason is "Fall-through from normal boot mode"
[Moto Maxx Original Android Development] beanman97:
Flash stock IMG. With RSD lite, then install TWRP. Su. Then cm12.1 and gapps.(wipes all data)
[Moto Maxx Original Android Development] gambiarraweb1:
Testing CM13? Link :)
[Moto Maxx Original Android Development] beanman97:
marshmallow

I hope it brings VoLTE when it is ready. Granted I've got a dead motherboard at the moment so I'm not using tether but when I am which is 100%of my desktop internet it's annoying to completely lose all net connectivity any time you get a call. Like reverse dial up.

Phew. Vent over. Ty
[Moto Maxx Original Android Development] Shooting Star Max:
Current builds have VoLTE provided your network supports it.
[Moto Maxx Original Android Development] beanman97:
I know Verizon network supports it. But I don't have the menu option for it

And the first page says known bugs. VoLte doesn't work
[Moto Maxx Original Android Development] beanman97:
I seam to have a new problem now. I made a backup on twrp . then installed the last nightly. And I only get connectivity for a min. When the phone boots then it shows nothing. Restored to the said backup and same thing

Also no desktop to work from atm
[Moto Maxx Original Android Development] fgl27:
[MENTION=2228410]Skrilax_CZ[/MENTION]

victara audio_policy.conf fix that audio alsa kernel ting. I have tested on my kernel.

Made this commit you may wanna use as example.

this fix call rec, and some other audio bug that happens only to some games.

this may have some improve on that Bluetooth bug that is present to only some users. :good:
[Moto Maxx Original Android Development] beanman97:
Is it possible to flash a radio with out a desktop, using twrp.
[Moto Maxx Original Android Development] Nitefire77:
If someone made a flash able zip with it yes. I've flashed plenty of radios on my galaxy s3 and LG G2 and G3 when I had them
[Moto Maxx Original Android Development] Skrilax_CZ:
Victara issue with offload was of a different nature than ours + Motorola uses customized Audio HAL, which creates some difference between CM HAL and stock. 12000 and 24000 are removed due to kernel lack of support due to above issue, but since they are used so rarely, then it has no impact (typical rates are 11025 | 22050 | 44100 and 48000). Will try to add the missing items (deep_buffer), perhaps that's the missing configs ppl with bluetooth need (deep_buffer).
[Moto Maxx Original Android Development] fgl27:
I dont really know much about what moto uses or not, my point is victara and quark use the same hardware/qcom/audio-caf folder, as 8084 foder is just a link to msm8974.

So for me what works for they must works in all most situation to quark, and they don't seem to have bugs in audio or Bluetooth.

In my test deep_buffer desnoto help much but there is changes to CM/google source that seems to need that for msm devices, for me after removing "compress_offload" all the bugs I had was gone (but I only test call rec, after use all the victara file and believed that some audio is better because all the extra audio entry, and those other new entry can help Bluetooth too), any one can test just by running antutu 6 3d bench the sound is all truncated before.

then I enable that alsa kernel ting + some new sample rates in the kernel, and the sound to me seems better, this is one ting that is really simple to test as is just change one file no need to build a new ROM if test without that alsa ting.

If you find a better or improve fix let me know.
[Moto Maxx Original Android Development] Skrilax_CZ:
[MENTION=5747496]baybutcher27[/MENTION] MSM8974 does not use the same audio as APQ8084 - they share the codebase, but if you look into it, you'll see differences (see all the #ifdef PLATFORM_APQ8084). I am not sure we have issues with compress_offload right now. While a lot is shared with victara, there still are some differences.

Thanks for the tip with Antutu 3D bench. Noticed the issue, but I didn't need to remove compress_offload to fix it. Attaching the *.conf file I had used is attached (no changes elsewhere). Also I suggest testing with Audio FX as well.

EDIT: Actually found an issue - Audio FX will not apply the equalizer if offload is on (because DSP then does the job, and doesn't receive the equalizer parameters properly).
[Moto Maxx Original Android Development] fgl27:
Yes I get confused because I was using that alsa kernel thing.

in my test is very simple.

use that conf file you share and alsa on the kernel, no sound on google music and maybe other.

removing "compress_offload" allows to use the alsa on the kernel and those 12000 and 24000 plus is easy to add other sample rates that "multichannel" uses high sample.

I will use alsa and no "compress_offload" if the user experience with that is worse I see and adapt in the future.

I just hope this change with or without alsa and "compress_offload" help with that Bluetooth thing ages and no fix...
[Moto Maxx Original Android Development] Skrilax_CZ:
[MENTION=5747496]baybutcher27[/MENTION] The alsa kernel thing is just a way how to pass parameters to enable 12000 and 24000 rates for offload, nothing more (which are not important anyway). It has no impact on anything else. Actually, checking the HAL, there is a way for a proper fix of that (by defining AUDIO_FEATURE_ENABLED_NEW_SAMPLE_RATE).
[Moto Maxx Original Android Development] junior_ilha:
I also Noticied a truncated sound on horizon Chase game if you need more tests...

The call recording will be working on next release after this discovery [MENTION=2228410]Skrilax_CZ[/MENTION]?
[Moto Maxx Original Android Development] Skrilax_CZ:
Still reviewing audio as a whole (some kernel changes as well).
[Moto Maxx Original Android Development] Skrilax_CZ:
[MENTION=5747496]baybutcher27[/MENTION] I've uploaded the changes to gerrit:

Device repo:

http://review.cyanogenmod.org/#/c/126547/

Kernel repo:

http://review.cyanogenmod.org/#/c/126548/

http://review.cyanogenmod.org/#/c/126549/

http://review.cyanogenmod.org/#/c/126550/

http://review.cyanogenmod.org/#/c/126551/

http://review.cyanogenmod.org/#/c/126552/

http://review.cyanogenmod.org/#/c/126553/

Must apply all. Still reviewing to make sure audio_effect.conf are set right. QC has it really customized ._.
[Moto Maxx Original Android Development] fgl27:
Ok, I see, the last time I try to compile this

http://review.cyanogenmod.org/#/c/126549/

it didn't workout. Have you try?

I will give it a try and post you the result. :good:
[Moto Maxx Original Android Development] Skrilax_CZ:
Yes, you need http://review.cyanogenmod.org/#/c/126553/ to make it compile. I've updated http://review.cyanogenmod.org/#/c/126547/ , should now work as desired (offload with no effects, deep_buffer with effects).
[Moto Maxx Original Android Development] fgl27:
yes it build ok I miss that one the last time.

I did all the changes manually used the stock cm12.1 kernel with the new mod, and call rec, those game app, flac audio files, youtube app and normal system audio is ok.

But mp3 don't work, of course I don't have build on the rom I'm using that one line:

AUDIO_FEATURE_ENABLED_NEW_SAMPLE_RATE := true

do you think that is the problem?

If I use your audio_policy.conf but remove "compress_offload" and place the "compress_offload" flags with "deep_buffer" flags those mp3 work ok.

I use that google play music app that was the one reported when the firs audio bug was reported. :good:

One more thing those "offload" system.prop is your intention to remove it all or just the duplicated lines?

I did the test with and without those lines on the prop same result. :good:
[Moto Maxx Original Android Development] Skrilax_CZ:
Yes, it is. That one line mirrors the alsa patch in the HAL.

Just removed the duplo lines.
[Moto Maxx Original Android Development] Skrilax_CZ:
Looking at the build log, 01/04 nightly should have the audio fixes included (http://download.cyanogenmod.org/get/jenkins/142717/cm-12.1-20160104-NIGHTLY-quark.zip)
[Moto Maxx Original Android Development] beanman97:
If someone could make a stock xt1250 radio. Or one for Verizon. Which ever works. I'd be greatful. Because the bootloader radio combo zip on the op will not flash in twrp
[Moto Maxx Original Android Development] junior_ilha:
Just a feedback: call recording and horizon Chase working fine after sound fix from nightly 160104
[Moto Maxx Original Android Development] munchy_cool:
for Turbo ..used the TWRP package successfully 2 days ago

http://xdaforums.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
[Moto Maxx Original Android Development] edaknik:
xt1250: Running ROM cm-12.1-20160104-NIGHTLY. Bluetooth with "media audio" works fine, but "phone audio" totally non-functional. I can connect device to BT speaker and play music stored in device's internal storage (with A2DP profile). Can pair device to Bluetooth headset (Plantronics M55) and listen to music in headset from device. However, cannot get any audio in Bluetooth headset when making a phone call. It would appear that Bluetooth is functional for me in both A2DP and HSP profiles, except for phone calls. Could I have not flashed the correct radio.img file?
[Moto Maxx Original Android Development] beanman97:
Well it successfully installed. Now it says I have no sim. And the band is locked to

WCDMA preferred
[Moto Maxx Original Android Development] Skrilax_CZ:
No, that will be something left out in the audio config (perhaps forgotten flag for phonr calls). Will review again. Anyway, it's some progress.
[Moto Maxx Original Android Development] beanman97:
Would it be possible to get a factory radio IMG as a zip installable with twrp. Out of the box it came with 4.4.4 and I've fixed this problem with rsd reflash before. But have no computer to work from at the moment
[Moto Maxx Original Android Development] fedecape:
Hey [MENTION=2228410]Skrilax_CZ[/MENTION],

Hope you're doing great. First of all allow me to thank you for all the great work you have done for this community.

I am bothering you because, like probably most of us, I am curious about the progress of CM13. I understand that you are working on it using your second Maxx. Is this still the case? Have you had the time to make some progress?

This is by no means a request, a complaint, or anything like that. Just simple curiosity.

Thanks in advance

Fede
[Moto Maxx Original Android Development] screege:
Same problem here
[Moto Maxx Original Android Development] Skrilax_CZ:
CM13 will take a while, since I need to dig deeper in it to get it working properly.
[Moto Maxx Original Android Development] beanman97:
Cool. Thanks for update. Good luck
[Moto Maxx Original Android Development] pitchinnate:
Re: [Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 12.1

Any idea why the newest daily has this in the changelog?

All other dailys the changelog shows up fine.
[Moto Maxx Original Android Development] duowing:
It looks like there were no changes for 01/07: http://www.cmxlog.com/12.1/quark/
[Moto Maxx Original Android Development] Skrilax_CZ:
I have fixed BT voice calls, for the moment you can download the attachment, unzip and do:

adb root
adb remount
adb push audio.primary.apq8084.so /system/lib/hw/
adb reboot

Indeed, the reason why only some users were affected is, that if you used 8 kHz sample rate in your phone call, then it was configured properly, while 16 kHz sample rate is misconfigured.

EDIT: I've reuploaded the HAL, the original upload had a bug that once you used your BT headset (16 kHz sample rate), then it would not switch back to 8 kHz sample rate (for your car) until you reboot. Fix will be in nightlies when this is merged: http://review.cyanogenmod.org/#/c/127448/ (or resolved otherwise).
[Moto Maxx Original Android Development] ChazzMatt:
I never had any issues with BlueTooth on a Jawbone Icon headset or on my Pioneer car stereo. Was it just configured for both to be 8 kHz by luck? Or is this something a user would change somewhere on their phone? I don't see any settings like that in Settings/Bluetooth in CM12.1...

But thanks for fixing it for others!
[Moto Maxx Original Android Development] Skrilax_CZ:
This part affects phone calls only. Typically cars do not use 16 kHz for calls.
[Moto Maxx Original Android Development] ChazzMatt:
OK.

FYI, I stream Pandora music all the time from my phone through my Pioneer car stereo, via Bluetooth -- before, during and after phone calls. No issues.

And when I make/receive calls, while driving the music volume automatically turns down and the call volume goes up. It all goes through my speakers and I have a mic on the windshield. Then, when the call ends, the music goes back up automatically.

Has always worked fine for me. But others complained about Bluetooth, enough that I knew it was a real issue for some.
[Moto Maxx Original Android Development] screege:
Will try it and post thanks a lot!
[Moto Maxx Original Android Development] localceleb:
I was one of the users that was affected by this bug. Cannot wait to test!
[Moto Maxx Original Android Development] Skrilax_CZ:
01/10 nightly should have the bugfix.
[Moto Maxx Original Android Development] meskes:
OK. Right now, I don't have a working PC, so I'm having to Mcgyver everything together. I'm currently having an issue with my phone's radio not wanting to go into LTE even though I've go it on Global, like its supposed to. Does anybody have any suggestions about how to fix this without having to reflash the radio or stock rom?
[Moto Maxx Original Android Development] edaknik:
I can confirm that this fixed the issue with Bluetooth audio not working for phone calls. [MENTION=2228410]Skrilax_CZ[/MENTION], thank you very much!!!
[Moto Maxx Original Android Development] edaknik:
Bluetooth voice calls are working now, but I just realized that like meskes the device only indicates a 3G connection. I've tried various things I've found from searching the issue, but none has worked.
[Moto Maxx Original Android Development] ChazzMatt:
Does LTE show up eventually, if you wait long enough? When I leave Wi-Fi I have 3G (HSPA) for 10-15 minutes, then suddenly the phone finds LTE signal (which was there all along).
[Moto Maxx Original Android Development] edaknik:
No, I went for a day or two with only 3G connectivity. For fun, I reflashed radio.img from an image from post number one of this thread, which only served to give me give me "SIM not found" messages on boot. I restored the device to the factory image (using a TWRP backup), then wiped everything and reinstalled cm-12.1-20160110-NIGHTLY-quark.zip fresh. LTE works now, which would suggest that this is not a general problem with the latest nightly, but something either specific to my device or some issue with the upgrade process. Not ideal, but a relatively small price to pay for running this firmware. Thanks again to Skrilax_CZ and everyone else developing and/or testing this build.
[Moto Maxx Original Android Development] Shooting Star Max:
I have noticed something weird.

There is a constant clicking noise in recorded videos (both in 4K and in 1080p). The noise is absent from sound-only recordings. It happens with Motorola's camera, with the AOSP camera, and with Google Camera. Anybody has this weird issue? I just noticed it because I rarely record video, though.
[Moto Maxx Original Android Development] screege:
I can confirm bluetooth calls now work!
[Moto Maxx Original Android Development] ragtim:
I never noticed this until I got a new Bluetooth headset as my car bluetooth work fine. This fix fixed my Bluetooth issues with headset.
[Moto Maxx Original Android Development] Diego1751:
so all data conectivity texts, phone, data do not work it randomly stopped working yesterday while I was texting someone, I have double checked all the settings and reflashed the radio for verizon (it was a droid turbo from verizon same service
[Moto Maxx Original Android Development] fedecape:
Hey guys, what's your average battery life / sot time? Thanks
[Moto Maxx Original Android Development] richii0207:
Same as stock for me.
[Moto Maxx Original Android Development] mrkhigh:
Again same as stock. I'm a relatively heavy user, lots of surfing and graphic intense games.

I typically will make it a whole work day easy. Weekends however I "may" have to plug in.

A user who does not use it much would make it two days.

I've been up since 5am (now 9pm) and I'm 21%

Unfortunately I don't think cm12 here has a screen on time.
[Moto Maxx Original Android Development] fedecape:
Thanks for your input!

Do you have a number for SoT?

Hey, thanks for your input. For screen on time scroll down to the list of apps/services and tap on screen. This while being on the 'Battery' menu which you can access from Settings.
[Moto Maxx Original Android Development] mrkhigh:
6 minutes 14 seconds.

I'll post tonight....
[Moto Maxx Original Android Development] richii0207:
Tough to say a number. Some days I have bad service, others I may use GPS, or listen to music with screen off.
[Moto Maxx Original Android Development] brennam7:
I've had the same sort if issues. Haven't figured out how to make it stop. Normally just reboot the phone to get it working again
[Moto Maxx Original Android Development] Aravindtop:
I'm sorry, I just have to ask this, and trying to find previous similar questions is too hard on a massive thread like this. Where is CM13 for Turbo/Maxx? Has any progress been made on it? I just learned that my Motorola DROID Bionic from 2011 got CM13 today. Sorry about whining, but I'm very much yearning for the Marshmallow experience.
[Moto Maxx Original Android Development] miketoasty:
From what I've seen there hasn't been anything posted for a while but if it makes you feel better I have MM on my Nexus 10 and other than the battery improvements it really feels exactly the same as LP.
[Moto Maxx Original Android Development] Aravindtop:
Well, Doze, Notification dropdown customization, Now on Tap, Permissions, Volume Controls, improved Menus, and the System UI Tuner is all what I'm looking forward to in Marshmallow. Yes, I do know I can get some of those via Xposed (Which I currently do), but it just irritates me to no end that I'm using outside code and not native implementations.
[Moto Maxx Original Android Development] Skrilax_CZ:
I have found out why the camera preview in some apps is corrupted (WhatsApp etc.), the reason is wrong alignment of the buffer in memory. This affects only some resolutions, hence it works fine in camera apps, but not so well when the apps user lower preview resolution. Will fix soon in nightlies. For now, unpack the attached library and push it to /system/lib via adb.
[Moto Maxx Original Android Development] junior_ilha:
Nice work...

Now I don't remember another bug in our ROMs. Cm13, run for it! lol
[Moto Maxx Original Android Development] Gambler_BE:
This question has been asked before, and has been answered by OP. It's really not that hard to find, it's even top thanked as you can see...
[Moto Maxx Original Android Development] Diego1751:
Any ideas or etas on when a build that isn't a nightly would be released? How long does that usually take?
[Moto Maxx Original Android Development] hpbrasil:
The day was asked to gaming performance correction, when it begins to play and the device heats up the game gets ridiculous performance .... And even using other kernel gpu lose more performance than the stock rom.

Left new blobs for processor 805 have been added in the latest version of the rom? :confused::confused:
[Moto Maxx Original Android Development] ChazzMatt:
It's my understanding a couple of months ago (November 17, 2015), the Quark nightlies started to be based on CM 12.1 "stable" branch. CM 12.1 went stable. Then, nightly changes built on that. So, they aren't just pure nightlies, like in the beginning.

For instance, look at this change in the January 22 nightly: http://review.cyanogenmod.org/#/c/129200/

If you want only pure stable (without the subsequent nightly overlays), you would have the find that "stable" build from a couple of months ago. BUT, lot of improvements (like Bluetooth fixes) have been made in the past two months since then in the Quark nightlies! ;) So, you would be missing out.

Also, don't misunderstand the word "nightly".... Even before being based on the "stable" build, the "nightlies" are very stable -- enough to be used as a daily driver. In the 8 months since I've been using them, I can only remember one time a build was messed up (wrong version of kernel included accidentally). And that was easy enough to fix -- just reflash previous nightly (or restore from backup) and wait for a fix.

And that one mistake was in the 8 months since I've been using them. Go back to March 2015 when CM became available for our phone and it's even longer.

_____

If I've said something incorrect, [MENTION=2228410]Skrilax_CZ[/MENTION] feel free to clarify. ;) I'm not a dev.
[Moto Maxx Original Android Development] Skrilax_CZ:
So what happened before with the YOG7D stable branch build in November, was that it used old proprietaries, thus not working right. This is what I've fixed and applied all fixes since that time (i.e. XT1254, VoLTE for non-Verizon, audio / bluetooth) at last and there will be soon new build off the stable branch (not sure if the preview fix will make it's way), I suppose early next week when the build bots are available.

Nightlies are built from the main branch for cm-12.1, although given most development has shifted to cm-13.0 (non-platform related), it in its way is becoming a stable branch (of course there is always a risk of picking a one with a bad commit).
[Moto Maxx Original Android Development] Fulbring:
Great to hear that! I've been waiting for a stable build for a while. Hopefully, the next build I flash is a stable one and then after that, a CM13.0 Nightly!
[Moto Maxx Original Android Development] The Horak:
Simple question, there's no way to use this ROM and get Android Pay to work, right? I know that it won't happen with root, but I don't want root. Please don't start a discussion about how its been answered and such, just wondering if there have been any breakthroughs or ways to make Play Services think the ROM is a trusted build. Thanks so much, guys.