yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] ChazzMatt:
I had more trouble with that in the September 12 nightly. LTE kept crashing, going to HSPA -- even though I know there's a strong LTE signal.

In the September 11 nightly, for me it often goes to zero LTE bars (no signal), but then it comes back -- doesn't actually crash. Again, it shouldn't be zero -- there's a strong LTE signal.

Ever since CM did something in early August to telephony stuff, seems like LTE Preferred is (often) ignored? :confused: When I get off Wi-Fi, my phone almost always locks on to HSPA (even though there's strong LTE signal around). I have to pull SIM card out, push it back in, sometimes a couple of times for LTE to activate.

But then other times, it goes to LTE OK and I think everything is fine... :silly: Then BAM, back to HSPA, even though LTE is all around.

The issue seems to happen when leaving Wi-Fi and going to mobile network... If I pull out SIM card and force LTE, I get "sign into AT&T network" error message, pull out SIM card and put it back in again, and then everything is OK.

CM12.1 is smooth, love it. Just wish the LTE wasn't wonky for the past six weeks. I hate having to pull out my SIM card, put it back in while driving. :eek:

It's not my SIM card -- I even went to AT&T to get another one. I may go back to July 29 or July 23 nighly to see if it fixes the issue. I haven't upgraded my wife's phone past July 29 and she doesn't have that issue on her phone. I still have a copy of those two nighties in her download folder...
[Moto Maxx Original Android Development] RoPipo:
I still have the issue with the bluetooth. I'm using a Jabra Rox headphones, the music sounds great, but when I make phone calls, I can't hear nothing and the other person hear me with a robotic voice and is not understanding nothing. Why is this with a lot of nightlies before? with the stock rom I haven't this issue, and with the news nitghlies the battery performance was great! :( The bluetooth is the only thing that it keeps wrong
[Moto Maxx Original Android Development] Shooting Star Max:
For me it seems to work well when I let the phone sit without Wi-Fi enabled. When LTE kicks in, I turn on Wi-Fi and everything is well. I can even disable Wi-Fi and LTE will work well too. I didn't get to experience this before because in my home country I didn't have 4G/LTE, but here in the UK I got it.
[Moto Maxx Original Android Development] romaxx:
In the latest versions continued the problem with video calls?.
[Moto Maxx Original Android Development] screege:
I have the same problem as ropipo, hope someone can answer this or solve this I have the same issue also.

Regards
[Moto Maxx Original Android Development] junior_ilha:
Unfortunately here the in-app camera does not work.

Does anyone know how to make the Slow Motion on motorola camera work on CM12? Or make the shaking gesture to change from the front camera to selfie mode as in stock?
[Moto Maxx Original Android Development] fgl27:
[MENTION=2228410]Skrilax_CZ[/MENTION]

this commit

is making this error...i tink:

This is from peregrine but quark is the same error...

12.1/out/target/product/peregrine/obj/ETC/file_contexts_intermediates/file_contexts: Multiple different specifications for /sys/devices/virtual/graphics/fb0/rgb (u:object_r:livedisplay_sysfs:s0 and u:object_r:display_sysfs:s0).
Error loading context file from /opt/jenkins/android/workspace/android/cm-12.1/out/target/product/peregrine/obj/ETC/file_contexts_intermediates/file_contexts
make: *** [/opt/jenkins/android/workspace/android/cm-12.1/out/target/product/peregrine/obj/ETC/file_contexts_intermediates/file_contexts] Error 4
make: *** Deleting file `/opt/jenkins/android/workspace/android/cm-12.1/out/target/product/peregrine/obj/ETC/file_contexts_intermediates/file_contexts'
make: *** Waiting for unfinished jobs....

it affect not just quark build but other.

probably CM members are already looking to that.

I did not have time to find a fix.

Add later...

I find the duplicated entry on:

https://github.com/CyanogenMod/android_device_motorola_quark/blob/cm-12.1/sepolicy/file_contexts

Will make a fix and report...
[Moto Maxx Original Android Development] fgl27:
This fix the problem in RR source...

https://github.com/CyanogenMod/android_device_motorola_quark/blob/cm-12.1/sepolicy/file_contexts

remove line 17

- /sys/devices/virtual/graphics/fb0/rgb u:object_r:display_sysfs:s0

I believe will work for CM too.
[Moto Maxx Original Android Development] ChazzMatt:
Which issue does this fix?

This has been submitted to the CM channels? I'm not sure how it works to submit fixes...
[Moto Maxx Original Android Development] fgl27:
A lot of change has be made to improve CM source (just like is done every day).

And one change/improve affect, the build process of new nightly for quark and other devices, in the CM jenkins server you can see it.

The error was, one line on a new change, that overlay a existent entry on quark tree.

I don't submit my change i leave that for the OP, If the change is ok, he will make it (and i don't think any change I submit will be approved until OP approves it, i never try it)...

But until he or some one make this or other change to fix this particular error, nightly may not be successful.

[MENTION=535343]all[/MENTION]

BTW...

I'm not pointing errors, i just try to make a ROM build on my on, and get the same error, i fix and share it so OP can use it or not. Any other custom ROM uses CM as base, so i share my fix to make other life easier...
[Moto Maxx Original Android Development] Skrilax_CZ:
I know (we are getting notified on changes that can break stuff), just I'm in China again :)
[Moto Maxx Original Android Development] RoPipo:
I'm testing the nightly of 15/09 and it's still having the issue with Bluetooth headsets on phone calls. All good in music listening. Hope the next nighlty have solved the problem
[Moto Maxx Original Android Development] ChazzMatt:
Strange it works on some Bluetooths and not others. My Jawbon Icon Thinker is working fine . I've talked several times over it in phone calls.

I'm still on the September 11 nightly, but I've seen these Bluetooth posts for awhile now.
[Moto Maxx Original Android Development] Dani01c:
It doesn't work on my powerbeats on any custom rom.. Has anyone ever figured out what the problem is?
[Moto Maxx Original Android Development] Emisand:
Hello,

I have installed the latest version of CM (20150920) on my Moto Maxx and im having problems with the camera when using Whatsapp.

I want to use Whatsapp Web, and it uses the camera to scan a QR code, but for some reason, the camera is not encoding as expected.

I've attached a screenshot so you can see the problem with the camera.
[Moto Maxx Original Android Development] RoPipo:
I have the same problem from the first nightly that I've installed. I thought that I was the only one.

On nightly 20150919 I still have the same issues with Bluetooth and my headsets. I have to remember, in stock Roms this problem is not exist
[Moto Maxx Original Android Development] romaxx:
Problem has always existed.

Try changing DPI to 500. On the screen everything looks smaller but it works.
[Moto Maxx Original Android Development] Bobboman:
i have to random folders that have appeared on the root of my Storage partition both named storage, i tried deleting them but all it did was erase everything from my SD card

is there anyway to safely remove these or am i stuck with them?
[Moto Maxx Original Android Development] TonyStark R.I.P.:
Your thread is now located in the new Moto Maxx device forum
[Moto Maxx Original Android Development] Gundabolu SC:
Please Change the Forum Name to Moto Maxx cuz Droid Max is a 2013 device and many threads of the older Droid are included into this forum and inexperienced users could brick their devices flashing wrong stuff... Please at least move the posts to correct forums...
[Moto Maxx Original Android Development] ChazzMatt:
Yes, Droid Maxx (2013) is a completely different phone from the 2014/2015 Moto Maxx (XT1225/XT1250)/Moto Turbo (XT1225)

Motorola create two Quark phones under three names -- released in late 2014/early 2015.

1) U.S. Moto Maxx XT1250/Verizon Droid Turbo XT1254 -- same device, same FCC ID, same bands. The Verizon Droid Turbo has a bootloader which cannot be unlocked.

2) International Moto Maxx XT1225/Moto Turbo XT1225 - same device, same FCC ID. No CDMA, slightly different mix of LTE bands.

None of these Motorola Quarks are "Droid Maxx" phones -- which is a 2013 phone sold by Verizon.
[Moto Maxx Original Android Development] TonyStark R.I.P.:
The change of device section name is in the process to Moto Maxx:good:
[Moto Maxx Original Android Development] RoPipo:
I'm using the nightly of 20150926 and the bluetooth still not working on headphones., on calls, even if they are from whatsapp, Facebook, or Skype. But its works in movies or music, and yes, also works with my car system audio from Suzuki. Please, can you solve this for once??? In the stock roms this problems doesn't even exists, can you use something from there, pleaseeee????

I really love CyanogenMod, but, this is the only trouble that I have :(. And I'm not the only one.
[Moto Maxx Original Android Development] fedecape:
Yo, relax. He's not charging us for this rom. He is aware of this issue and it is probably not as easy as "using something from stock."

Try an older nightly. It used to work before (at least for me)
[Moto Maxx Original Android Development] screege:
Ropipo could you please update in this which older ROM works?
[Moto Maxx Original Android Development] Skrilax_CZ:
I have to check what "fix permissions" does. Sounds a little strange though, but I don't think the backup restored radio partitions, so if "fix permissions" does something there, perhaps that's what to look on.
[Moto Maxx Original Android Development] fedecape:
Hi guys,

I'm on 0927 and everything seems to working fine! LTE is good, WiFi is good, GPS is good, Bluetooth is ok (no mic), and battery life seems decent 4~5 SOT. The only minor issue I have is that the screen is not turning off automatically when charging. I have sleep set up after one minute (Settings > Display & Lights) but it doesn't seem to be working. Any ideas?

Other than that, super happy. Way faster than stock.

Also, do you guys update every night?
[Moto Maxx Original Android Development] ChazzMatt:
They update almost every night. They seem to take weekends off. Last one was October 3. Today is October 5, so there should be one available in the next 5 or 6 hours.
[Moto Maxx Original Android Development] fedecape:
Hey, thanks.

I meant to ask if you guys are updating your phones every night to the latest nightly. I'm still on 0927 with no issues.

Fede.
[Moto Maxx Original Android Development] Gundabolu SC:
I Know its too soon and too much to ask for but we are gonna have Marshmallow support too right??? :) :D
[Moto Maxx Original Android Development] andresgvc:
With the latest nigtly "cm-12.1-20151006-NIGHTLY-quark.zip" Xposed is broken, system hangs on logo or boot-loop.
[Moto Maxx Original Android Development] fgl27:
Try the xposed thread they are reporting that there... [DISCUSSION] Xposed for Lollipop the fix must come from there not a ROM problem...

Google security update pack of October 2015 apparently kills xposed.
[Moto Maxx Original Android Development] junior_ilha:
Xposed v75 working on newest (10/06) Cm12.1
[Moto Maxx Original Android Development] assanches:
Instalation Failure

Hi,

I tried to install the last cyanogem but in TWRP and Cyanogem recovery but give me an error and don't install de Cyanogem. The error is something about partition. what might be happening?

Sorry for my english
[Moto Maxx Original Android Development] Shooting Star Max:
Please post the exact error you are receiving, and detail what have you done before.
[Moto Maxx Original Android Development] xuanhac87:
Support for XT1254

Hi, this rom support XT1254

Do you known link howto root Motorola droid turbo xt1254. I find its.

Thanks
[Moto Maxx Original Android Development] ChazzMatt:
No, ROM won't work on the Motorola Quark XT1254 Droid Turbo, since it has a locked bootloader.

However with [MENTION=2228410]Skrilax_CZ[/MENTION] help, it will work on the XT1250 U.S. Moto Maxx, which is IDENTICAL to the XT1254-- same FCC ID, same CDMA/GSM/HSPA/LTE bands and has an unlock-able bootloader. The XT1250 can be fully rooted, and custom recovery (TWRP) installed.

The XT1250 will run on ANY network the XT1254 Droid Turbo runs on, including Verizon. The XT1250 is basically the "dev" version of the Droid Turbo. Many people have bought them and run them on Verizon with a Verizon SIM card -- just like a non-Verizon Moto Nexus 6.

The U.S. Moto Maxx XT1250 is sold in the United States by regional CMDA/LTE carriers.

For someone who has a U.S. Moto Maxx XT1250, be sure to contact op [MENTION=2228410]Skrilax_CZ[/MENTION] first. He will need to help you with the kernel.

But for the XT1254, sorry -- you bought a phone with a carrier-locked bootloader.
[Moto Maxx Original Android Development] fedecape:
Camera Info (metadata) on Cyanogenmod

Hey guys,

I noticed that all photos taken with Google Camera on CM12.1 show as taken by "phone" instead of XT1225 (as it did on stock). Is there any way to change this?

Thanks
[Moto Maxx Original Android Development] xuanhac87:
Thanks you.

I have bought its. Carrier Verizon.
[Moto Maxx Original Android Development] gabriellajeado:
Will Cm13 supported? If yes, it will take a long time to come to xt1225? Thanks :)
[Moto Maxx Original Android Development] Skrilax_CZ:
CM13 will be supported, but it's not ready by itself at the moment.
[Moto Maxx Original Android Development] Skrilax_CZ:
I've noticed that I didn't update the radio & bootloader packages with the OTA that we received after the initial 5.0.2, so added versions for those as well. They come from QUARK_RETBR_5.0.2_LXG22.33-12.16_cid12_subsidy-DEFAULT_CFC.xml.zip and QUARK_RETEU_5.0.2_LXG22.33-12.16_cid7_subsidy-DEFAULT_CFC.xml.zip
[Moto Maxx Original Android Development] dbirkett:
xt1250

I have a xt1250 I just bought and would like to get CM working on Verizon. Already bootloader unlocked, flashed TWRP recovery. Tried CM, no radios, reading the thread sounds like kernel tweaks are required?
[Moto Maxx Original Android Development] svprm:
Thanks for CM 13 support.

Waiting for it.

How can i find my current Radio version?
[Moto Maxx Original Android Development] Skrilax_CZ:
I've added some stuff that could help with bluetooth audio. [MENTION=5747496]baybutcher27[/MENTION] pointed out how to fix charge only mode, done (although atm. the battery icon is small, will fix later). Then added experimental support for XT1250 (use the latest radio image, which is still oh yes 4.4.4; XT1254 SU3TL also contains LRA radio, but SU4TL does not for some reason).
[Moto Maxx Original Android Development] fedecape:
Hey, first of all: thanks for all your hard work.

Are 5.0.2 RETBR (LXG22.33-12.16) & 5.0.2 RETEU INDIA (LXG22.33-12.16) the new files? I'm using the previous packages so I'm assuming we just have to re-run the commands. Is this correct? Will I notice anything?

Thanks!
[Moto Maxx Original Android Development] core720:
waiting next build... thks
[Moto Maxx Original Android Development] ChazzMatt:
[MENTION=2228410]Skrilax_CZ[/MENTION]I see a bunch of Quark stuff coming up in the next nightly! Thank you!

___

One thing...

The HSPA/LTE issue never really got fixed -- where it locks onto HSPA for a long, long time and ignored "LTE Preferred". However, I've discovered something interesting. IF I boot up from a powered off mode with wi-fi turned off -- or turn off wi-fi and force onto mobile network, it will lock onto HSPA for exactly 15 minutes. THEN, it will changed to LTE, if I am in an LTE area. Most of Atlanta is LTE, of course. I've observed this several times, whether driving or stationary. One time I even tuned on my clock timer. 14 minutes, still HSPA. 15 minutes, changed to LTE.

_______

I am at my desk. SAME location. Not moving.

I booted up my phone, turned off Wi-Fi, started the timer...

After 14 minutes, STILL HSPA.

now at 15 minutes, changes to LTE! (I didn't start the time EXACTLY when the HSPA signal locked in. Took me a few seconds. But trust me, it's 15 minutes.)

NOTHING has changed, except 15 minutes goes by. LTE locks in!

It's as if SOMETHING turns on, or queries at 15 minutes and says "Oh! He prefers LTE". Or it searches and says "Hey! LTE is available after all!" :)

Any ideas?

When I changed my wife from the July 29 nightly, her phone now acts just like mine -- whereas on the July 29 nightly she would immediately get LTE when leaving Wi-Fi.

I don't know if while driving, if you encounter an open wi-fi signal and it locks onto that the "15 minute timer" re-sets to another 15 minutes? I've not experimented with that. All I've done is try without wi-fi turned on.

If I let it go to LTE (15 minutes) and then reboot a second time, it seems to lock on faster, like around 10 minutes. But still a long time, when LTE is available. Just very strange...
[Moto Maxx Original Android Development] Shooting Star Max:
Something that happens to me sometimes...

If I turn the device on and I leave Wi-Fi turned on (and it connects to a network with Internet connectivity), the device connects to the Wi-Fi network, and then the mobile signal comes and goes. It goes from 100% (or whatever reception I have) and then to zero (as in "no service"). If I turn Wi-Fi off, then it stabilises and gets HSDPA+/LTE. Everything works perfectly after that, I can turn Wi-Fi on and off, use Airplane Mode or whatever, and it will work normally. It doesn't really matter to me, since I got the habit of turning Wi-Fi off before rebooting.

Maybe our issues are somehow related?
[Moto Maxx Original Android Development] mirdones:
I got stuck on today's nightly 10/19/2015.

It optmized all apps and then got stuck on initializing apps for more than 10 minutes.

I tried again without xposed and it got stucked at the same point.
[Moto Maxx Original Android Development] Skrilax_CZ:
Can you reflash the latest radio package and see if that helps?
[Moto Maxx Original Android Development] mirdones:
I have just went back to the 10/14/2015 nightly and all is fine now.

Before using CM, I was already on the latest brazilian version.

Would it make a difference to reflash the same radio package?

The process would be:

1- Go to bootloader

2- Flash 5.0.2 RETBR (LXG22.33-12.16)

3- go to TWRP

4- flash 10/19/2015 nightly

Is that correctly?
[Moto Maxx Original Android Development] Skrilax_CZ:
It will wipe the modem status partitions, that why asked to reflash it. Yes, the process is correct.
[Moto Maxx Original Android Development] dbirkett:
XT1250

tried flashing on XT1250, wont go past bootloader unlocked warning. 10-13-15 nightly boots, but no service. Tried flashing both over stock and over previous nightly, with factory resets, and reflashing radio (4.4.4 version). Any ideas?
[Moto Maxx Original Android Development] mirdones:
It did not work.

The phone stayed on the initializing apps state for more than 15 minutes.

I am returning now to the 10/14/2015 nightly.
[Moto Maxx Original Android Development] romaxx:
I have the same problem!!
[Moto Maxx Original Android Development] fgl27:
[MENTION=2228410]Skrilax_CZ[/MENTION]

Is a kernel bug...

I made a experimental kernel using the latest Linux 3.10.90 + the changes of device tree that you made, and my new kernel doesn't boot, it bootloop on RR and CM12.1...

I try 10/19, clean install it get that bug stayed on the initializing apps....

If I flash my kernel V1.0.6 on 10/19 it boot fines pass that bug.

After have the ROM running go back to TWRP and flash only the boot.img inside 10/19 get bootloop, same to my experimental Kernel.

Don't know the fix to the problem....I'm busy this week if i find time and find a solution I let you know, will try run some new experimental Kernel tomorrow. :good: :fingers-crossed:
[Moto Maxx Original Android Development] Skrilax_CZ:
Let me look into it, well thing is that I don't have this issue, booted 3.10.90 just fine. Strange.
[Moto Maxx Original Android Development] fgl27:
The 10/19 boot.img over RR doesn't boot either... The latest RR I release is form 10/12, that is the one I test the boot.img...

Because of that I think is a kernel bug, but if you flash 10/19 and it boot just fine, I don't know...

To all

Any of you that have the bug have ever use my kernel? or RR ROM?
[Moto Maxx Original Android Development] Skrilax_CZ:
Can you try booting the latest kernel and send me "adb logcat"? My guess is that modem fails to initialize for some reason. It is possible that one of the patches between 3.10.87 - 3.10.90 is bogus. Or can you try will all the device tree changes, but checkout back 3.10.87 - the patches SHA to checkout in kernel repo are:

- 3.10.87: 8d71f293d860b7b6d2ca415461d59e8431f07292 (previous nightly)

- 3.10.88: efa548a057db1c5ac0c28273ac6f1d194f64b226

- 3.10.89: 4b0f961921e72f02a65afff1a0144a641d59f85d

If you can pinpoint the latest working one for you, it would be very helpful.
[Moto Maxx Original Android Development] icondeg:
no bugs until now

good kernel

congratulations

regards

Enviado desde mi Moto MAXX mediante Tapatalk
[Moto Maxx Original Android Development] core720:
Install Ultra Clean...

Last Firmware BR 5.0.2

TWRP

CM-12.1 10/19

DONT BOOT, BOOTLOGO loop

Install CM-12.1 10/17 and perfect boot old version
[Moto Maxx Original Android Development] fgl27:
Reverting all the commit from 3.10.87 to 3.10.90, build using 87 and levying the device tree changes, and the kernel work. The kernel boot no error.

But to test if is 88, 89 or 90 will take a long time i need to make all the commit that take from 87 to 88 separately build test and then 88 to 89... And that is a lot of work time i have no time right know. But yes I will try that, if you find the patch that may be the cause tell me i do a specific RUN over one commit.

I made one big merge/commit containing the 87 to 90 may be you can see the problem...
[Moto Maxx Original Android Development] Skrilax_CZ:
Oh, no need to make the commits separately. Just navigate to the kernel, and do "git checkout efa548a057db1c5ac0c28273ac6f1d194f64b226" and you're on 3.10.88, then build.

I understand you tested having none of the device tree changes with 3.10.87 and that worked? Can you check with having all the device tree changes in AND 3.10.87 kernel as well?
[Moto Maxx Original Android Development] fgl27:
I used all the device tree change, just revert the kernel. I check the .rc files and they are just like the device tree so is only a kernel tree ting...

Ok I will try that checkout to see if work, never use that way.
[Moto Maxx Original Android Development] Gambler_BE:
Ok guys, sadly, I saw the new posts in this topic only after I applied the new nightly using Cyan Delta. My phone is now stuck on "Starting apps" for about 20 minutes so I guess I have the same issue.

Am I correct that this could potentially be fixed by flashing an older version of the kernel? I was in a bit of a hurry, and as the brainless idiot I am I didn't make a backup, so I really want to solve this without wiping :/
[Moto Maxx Original Android Development] core720:
Install 10/19 and old kernel 10/17 and perfect work
[Moto Maxx Original Android Development] Gambler_BE:
Ok I'll try that, you just extracted the kernel from the 10/17 zip?
[Moto Maxx Original Android Development] maximuscesar:
Looks like they finally addressed the headset problem, someone can confirm it? I'm still downloading the 10/17 again (bootloop here).

Nevermind, I will try flashing the 10/17 zip and see what happens.
[Moto Maxx Original Android Development] Gambler_BE:
Let me know how it goes. I just flashed the 10/17 zip (without full wipe), but it looks to be stuck on the cyanogenmod logo now :p
[Moto Maxx Original Android Development] maximuscesar:
For me it worked. No wipe, no anything. And now I see an OTA notification (WTF! Never saw that!) and it shows me and 10/20 nightly so perhaps all our problems are solved.