yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] ChazzMatt:
see this post and see if it is similar to what you experience?

http://xdaforums.com/showpost.php?p=63380543&postcount=719

when leaving Wi-fi I get stuck on HSPA for about 15 minutes even though there's lots of LTE around. After 15 minutes, like magic, it changes to LTE.

Started happening after some telephony changes back beginning of August a few months ago.

But I'm still using CM as it's an excellent ROM. And I do eventually get LTE. Just strange the HSPA lock.
[Moto Maxx Original Android Development] IonAphis:
How do I get the ro.boot.cid number? And if happens to be 0x2, what can I do to change it / fix it.

Chazz, I havent tried the 15 minute rule, but it thats abou the gist of it. If I switch to LTE only, I will find good LTE signal. But until I manually do so, it just decides H/H+ is better....
[Moto Maxx Original Android Development] AndroidFanMan:
You can't and don't want to change this. This will eventually be resolved by the dev, from what I know.

Using ADB, type "adb shell getprop ro.boot.cid". That should return whatever value you have.
[Moto Maxx Original Android Development] Revenge282:
Can confirm the issue with the LTE signal. Running a Turbo myself on the 11-29 nightly. 11-27 did not seem to have this issue. Running BBH kernel too since the 11-27 build. Should not that even without the kernel it still failed locking LTE. GPS lock is also super wonky.

My ro.boot.cid is 0x2

I will update to 12-02 and report back.
[Moto Maxx Original Android Development] pvhien:
Sorry wrong box.
[Moto Maxx Original Android Development] fgl27:
did you try this?

1°this

http://xdaforums.com/droid-turbo/he...-rr-cm12-1-t3260228/post64119739#post64119739

2° then if no good the 1° this:

http://xdaforums.com/droid-turbo/he...-rr-cm12-1-t3260228/post64088863#post64088863

and if you do report please...
[Moto Maxx Original Android Development] ChazzMatt:
GPS lock issue fixed by installing TopNTP from Google Play (make sure you check the settings script box to survive ROM flashing), freeze Motorola's wonky geofences GPS with Titanium Backup, make sure you are on "high accuracy" settings. But TopNTP is a GPS helper that works great.
[Moto Maxx Original Android Development] Revenge282:
Thank you guys. I managed to grab an LTE signal earlier today between the short commute from the office to my house. The GPS also seems to be locking very accurately now. Under an aluminum roof in both buildings though, so I haven't had much chance to test it for any length of time.

Also am now running the 12/2 build, so that doesn't have any negative effects.
[Moto Maxx Original Android Development] cadenmiller60:
Why no cm13 yet? Just curious
[Moto Maxx Original Android Development] ChazzMatt:
Because it's not ready yet:
[Moto Maxx Original Android Development] neur0tk:
I want to flash the 12/2 nightly so everyone having good luck with it so far who flashed it??
[Moto Maxx Original Android Development] IonAphis:
Hey Chazz, just curious... Did you try going into Mobile Networks in Settings, searching for your network and instead of clicking "select automatically" selected your network instead?

That seems to have fixed the issue for me.. As simple and as dumb as that sounds.. I now have no issues getting LTE as soon as it is available..
[Moto Maxx Original Android Development] ChazzMatt:
I'm on AT&T here in the U.S.

Under manual choices, TWO AT&T networks show up (probably for contract and for prepaid? I'm on prepaid.) But when I manually choose either one, it tries to register, but then after a couple of minutes it fails.

This happens no matter which "AT&T" I choose...

Whereas if I choose automatically select, it works. I connect to the AT&T network.

But, thanks for the suggestion. The LTE issue only happens when I leave a Wi-Fi network (like home or work) and I'm out driving around. It locks onto HSPA for some reason, and only after about 15 minutes does it then lock onto LTE -- even though LTE is available. (The large city I live in is well covered with AT&T LTE.) Since when I'm driving, I'm only using GPS mapping and maybe Pandora music streaming, then HSPA for 15 minutes is OK. After I lock onto LTE, then it stays on LTE -- until I connect to another wi-fi network.

Sometimes it locks on to LTE sooner than 15 minutes, sometimes after only 5 minutes. But that is the exception, not the norm. I have no explanation. It all started wth CM telephony changes around the beginning of August. And maybe it's only AT&T-specific? Something quirky with AT&T? I don't know.

But I love the CM ROM and will continue to use it for both my phone and my wife's phone.

_____

Edit: as in mentioned on other posts, taking my SIM card out briefly, then putting it back in does force the phone to recognize LTE signal, for that one session. So I don't have to wait 15 minutes... But it's a hassle to do that while driving.
[Moto Maxx Original Android Development] pjd2011:
This fixed the issue for me as well on top of a reboot after selecting the change.

My only problem now is the gallery being wonky. I installed QuickPic and that eased that issue for now.

In the meantime....battery life on the 11/29 build has been nothing short of phenomenal! I used to be barely making it through the day with a Turboid build to having anywhere from 40-60% left with the same usage levels. Could definitely see this phone making it 48 hours with light usage (~5 hours screen on time).
[Moto Maxx Original Android Development] tecsironman:
What head unit model do you have . I have a x6600 and when I turn off my car my phone volume is so low I have to restart my phone. I also have a 7700 in my other car and don't have that issue.
[Moto Maxx Original Android Development] ChazzMatt:
Pioneer AVIC-X950BH

Specs:

http://www.pioneerelectronics.com/PUSA/Car/GPS-Navigation/AVIC-X950BH

My picture from my car:

Product picture:

For volume, you can download an app called Volume Control Plus that lets you set different profiles for "regular" use and for "bluetooth". When the Bluetooth connection is ended, it will revert back to full volume -- or whatever you have set for "regular" profile.

https://play.google.com/store/apps/details?id=com.cb.volumePlus&hl=en

IF for some reason the volumes don't return to normal after the Bluetooth disconnects, you can quickly open the app (via shortcut on the desktop screen) and manually push over all the volumes to full. No need to reboot the phone.

The app picture on Google Play shows the volume "knob" interface, like on the right above. I changed my to the slide control interface, as on the left above.
[Moto Maxx Original Android Development] localceleb:
Strange. I have the Pioneer AVH-4100NEX and BT calling doesn't work. However, streaming music via BT works flawlessly.
[Moto Maxx Original Android Development] SyCoREAPER:
I for the life of me cannot get gapps to play along. Tried full and pico. Both give me a FC.

Turns out that it was the crappy opengapps that everyone was suggesting. PA gapps was the solution.
[Moto Maxx Original Android Development] mrkhigh:
Odd, works fine for me.
[Moto Maxx Original Android Development] tecsironman:
Ooooo touch screens.. I just have a basic deh-x6600bt. Everything works except when I turn off the car. My ringtones and notifications are somewhat muted which requires a reboot to fix.
[Moto Maxx Original Android Development] fedecape:
Hey guys, I'm having issues with my Android Wear LG G Watch R.

The watch gets disconnected every 2-3 hours and usually the only solution is to reboot both devices. Ideas?

Thanks
[Moto Maxx Original Android Development] TheBassDude:
I've had no problems using Open Gapps micro package. As I understand it that whole thing is just an updated sort of continuation of the old PA Gapps project.
[Moto Maxx Original Android Development] SyCoREAPER:
I have no idea why I always have these goofy problems. Play Services does crash every once in a blue moon but the other ones didn't even allow me to do anything
[Moto Maxx Original Android Development] cadenmiller60:
Can i update to the next nightly build without wiping data?
[Moto Maxx Original Android Development] :
XT1250 on Verizon

I've flashed all of the xt1254 packages on my xt1250 and used

fastboot oem config fsg-id verizon
fastboot oem config fsg-id verizon_gsm
fastboot oem config fsg-id lra
fastboot oem config fsg-id lra_gsm

after setup, using this and Resurrection, and the phone still won't recognize my sim. Suggestions?

EDIT: Nevermind, had to reflash bootloader, gpt, and radio after flashing the rom. Then use the oem config.
[Moto Maxx Original Android Development] soldrag:
Hello. Any plans about cyanogen 13 for quark?
[Moto Maxx Original Android Development] duowing:
[MENTION=3250376]ChazzMatt[/MENTION] when you have the issue with the WiFi to LTE switching is it when you leave WiFi connected and leave the area that it does the long lock time, or does it do it even if you manually switch off LTE? I just finally went back to CM after being on stock rom for a long time and I'm not noticing what you've mentioned with the LTE switching. I didn't do the mfastboot flash partition gpt.bin/bootloader.img/radio.img and so far no issues. Every time I switch off wifi it immediately jumps back to LTE. I'm also using the Puerto Rico 5.0 Radio. I always had better luck with that radio more than any others, even on stock roms.
[Moto Maxx Original Android Development] TheBassDude:
I was having problems with LTE connectivity on the XT1254 to where it would only connect to 3G/CDMA. Flashed the radio.img file from post #1 and now all is well.

EDIT: Sorry, moved my question to the appropriate thread. Thanks, admin.
[Moto Maxx Original Android Development] xuanhac87:
unlock

hello

i can't unlock bootloader
[Moto Maxx Original Android Development] Skrilax_CZ:
My XT1225 has died :'( (due to EMMC, commands fail for operations after certain block in system partition). New one on the way.
[Moto Maxx Original Android Development] Gundabolu SC:
Noooooooooooooooooooo! :( :( :( :( :( :(
[Moto Maxx Original Android Development] Gundabolu SC:
I know you always know what you are doing and i might not be of much help but would this be of this help? :)
[Moto Maxx Original Android Development] fedecape:
It's probably the watch because I'm testing the Moto 360 now and it seems to be working fine.
[Moto Maxx Original Android Development] Shooting Star Max:
Can we help you with donations or anything?
[Moto Maxx Original Android Development] Gambler_BE:
This used to happen on previous builds with my Moto 360, but not as frequent. It happened about once a day, and like you said rebooting solved the problem.

I am currently on 11/29 and have not experienced this behavior anymore, but I might just be lucky. My best guess is it might be related to those other Bluetooth issues people have been discussing here.
[Moto Maxx Original Android Development] richii0207:
You can view any changes in the upcoming nightlies so you don't have to flash or wonder if anything is changed using http://www.cmxlog.com/12.1/quark/
[Moto Maxx Original Android Development] fndpena:
Hey guys, how is battery life on this rom compared to the latest stock rom? I know this is related to usage, but overall we get less drain?
[Moto Maxx Original Android Development] mrkhigh:
I'd call it about even.
[Moto Maxx Original Android Development] ChazzMatt:
If I leave Wi-Fi connected, especially in downtown urban area, it almost never goes to LTE. Because there's so many Comcast and AT&T hotspots (to which I have free access) that my phone tries to connect to those when I stop at traffic lights.

If I turn off Wi-Fi when I leave home or work, it stays stuck on HSPA for around 15 minutes, then magically switches to LTE. I've proven it even work.

Yet, there are exceptions. Just now (at work, in downtown Atlanta), I turned off Wi-Fi and the phone immediately locks on to LTE. I do not know why the difference. :confused:
[Moto Maxx Original Android Development] Nitefire77:
I just saw that the Nexus 6 has been getting CM13 night lies the past few days, and seeing its just a bigger droid turbo/Maxx it shouldn't be long till we get ours
[Moto Maxx Original Android Development] duowing:
If you've never tried the Puerto Rico modem, you may want to give it a try and see if it makes any difference for you. I'm on AT&T's network via Straight Talk over here in Ohio and in the past I never had a lot of luck/consistency with the Mexico/India/Latin America modems on the Nexus/CM roms. Puerto Rico always worked better which was why I kept coming back. Then Once 5.0 for Puerto Rico came out I started using that. I just finally went back to CM with the 12/4 nightly and with the PR 5.0 modem it switches to LTE immediately regardless of if I leave WiFi or turn off WiFi, and just seems to have better signal in areas where I would have problems on any of the other modems. Might be worth a try.
[Moto Maxx Original Android Development] ChazzMatt:
Waiting for CM dev [MENTION=2228410]Skrilax_CZ[/MENTION] to get his replacement XT1225!
[Moto Maxx Original Android Development] fgl27:
Nexus 6 is not just a bigger Maxx, it is a device that has Google support and not Lenovo :( .

Nexus will always be on the front...

But Moto E, G and X have already CM13, but then again that doesn't help much, regards stock MM, E I don't know but my G is already on MM and X I don't have one but it is too on MM. having the stock MM ROM helps a lot.
[Moto Maxx Original Android Development] fedecape:
Yeah, nevermind my previous comments. It's the phone/rom, confirmed. It's happening again, even with the 360. Again it's weird but it doesn't happen as much as it did with the G Watch R.
[Moto Maxx Original Android Development] mrkhigh:
[MENTION=3250376]ChazzMatt[/MENTION] [MENTION=2228410]Skrilax_CZ[/MENTION] so I thought GPS was working but upon trying maps today I realized it wasn't. Chazz, I tried your suggestions. They do not appear to help. Suggestions anyone?
[Moto Maxx Original Android Development] fgl27:
check RR #2 post.

use TWRP to make backup of custom, go back to stock (you must have a backup), get gps lock go back to custom.

Works every time.
[Moto Maxx Original Android Development] mrkhigh:
Will report back.

Back and have GPS coordinates.

Thank you.
[Moto Maxx Original Android Development] fedecape:
Hey guys, my father got himself a shamu on thanksgiving and he no longer needs his Turbo. Should I leave my xt1225 and use his xt1224? Is there any advantage to my Maxx now that the boot loader isn't locked anymore?

Thanks
[Moto Maxx Original Android Development] TheBassDude:
Is that the US or International Moto Maxx?
[Moto Maxx Original Android Development] Skrilax_CZ:
Looks like doing HW reset (disconnecting the battery), then erasing & reflashing the FW revived it (VZW SU4, so it updates the eMMC firmware). I guess I'll have two then :confused:

I wonder if the reason was, that touching some "bad sector" caused it to misbehave.
[Moto Maxx Original Android Development] ChazzMatt:
Yes, there is still advantage to the XT1225 over the XT1254 unless you use Verizon and/or need LTE band 13 or CDMA bands. The XT1225 has more LTE bands (2, 3, 4, 5, 7, 17) , including all of AT&T and more HSPA bands. The XT1254 has less number of LTE bands but does include LTE band 13, and has less number of HSPA bands but does have CDMA bands. For most people NOT on Verizon (or some regional CMDA carrier), the XT2225 is a better choice.

Also, unless his is the 64GB version of the XT1254, the XT1225 always has 64GB storage space. The XT254 comes in 32GB and 64GB, but most people cheaped out and got the 32GB.

---------- Post added at 04:09 AM ---------- Previous post was at 04:04 AM ----------

XT1225 is "international", but has all the AT&T LTE bands (2, 4, 5, 17). It actually has 2, 3, 4, 5, 7, 17.

See? XT1225 has more LTE bands and more HSPA bands. :good:

I think for the other one he means XT1254, the Droid Turbo. The U.S. Moto Maxx, which was the unlocked Droid Turbo is the XT1250.
[Moto Maxx Original Android Development] quangv:
Can i flash XT1225 radio on XT1254? I'm not live in US
[Moto Maxx Original Android Development] Gundabolu SC:
Haha... That's awesome that you could fix it and kinda sad u already bought another one! :)
[Moto Maxx Original Android Development] ChazzMatt:
No. You can flash the XT1250 and XT1254 over each other. They both have the same FCC ID.

But you cannot flash XT1225 over XT1254/XT1250. It has a different FCC ID and different frequency capabilities.

I've told many people outside the U.S. to forget the XT1254, that the XT1225 was the best phone for them. I don't know wny so many were enamored with a locked down phone with limited LTE/HSPA bands....

Well, it's not locked down now, but for a year it was. And it STILL has limited capabilities compared to the XT1225.

---------- Post added at 11:40 AM ---------- Previous post was at 11:36 AM ----------

Never anything wrong with having a backup! That's why I bought two -- in case I screwed up something rooting and flashing.

Initially my wife still used her Nexus 5. Only in July did she start using the 2nd XT1225. I'm thinking about buying a 3rd XT1225 for backup purposes. ;) The Moto X Force (Kinzie) doesn't excite me any. This phone is still gangbusters.
[Moto Maxx Original Android Development] Shooting Star Max:
I am having some problems with the latest build.

The device restarts after dashing through the ART optimisation (it only takes a couple of seconds to finish optimising 117 apps). If it does not restart, it starts saying that there's no free space for the system.

Checking with TWRP, no data is being written to the cache partition. Tried changing to F2FS, but it does not start. Tried wiping system and flashing everything again, to no avail. The only thing I have not done yet is factory reset, until I get some more feedback.

Anyone is having this problem too?
[Moto Maxx Original Android Development] GreaterLesser:
Yea I am too
[Moto Maxx Original Android Development] ChazzMatt:
Boot back into recovery, wipe cache and dalvik cache, then reboot.

Has happened to my wife's phone a couple of times for some reason.

That clears the issue.

We both have XT1225 with same ROM, same kernel, same settings, mostly the same apps -- but it happens to her phone, not mine. Strange.
[Moto Maxx Original Android Development] GreaterLesser:
That was my thought and that's exactly what I did. Just waiting for it to finish "optimizing"

---------- Post added at 04:51 PM ---------- Previous post was at 04:36 PM ----------

So following this changelog: CM 12.1 for Quark

This build should have VoLTE support right? or am I misunderstanding and it's still a WIP?

Also I'm having issues getting cellular service (data or voice) Gonna reflash my radio and make the edit to the fsg-id in the BL

Update: Phone keep trying to connect to GSM networks instead of CDMA even after doing the above. LTE data will connect for a bit but then the entire radio turns off and I have neither cellular nor data.
[Moto Maxx Original Android Development] Shooting Star Max:
I have done that, and it still reboots itself after optimising very fast (I think it actually doesn't optimise anything at all). I even flashed the previous nightly, but the problem persists.
[Moto Maxx Original Android Development] ChazzMatt:
OK, try this. Do the same thing, but stick it in the freezer for 10 minutes. On my wife's phone this last time, it optimized like 5 appps, rebooted optimized like 10, rebooted, optimized some more...

I stuck it in the freezer so it wouldn't overheat from all the rebooting.

Eventually it finished optimizing all the apps.
[Moto Maxx Original Android Development] Shooting Star Max:
Now it works, thank you very much! I didn't put it in the freezer, but I let it turned off for some time to cool it down, and removed the case. It then started to optimise apps correctly instead of rushing through them.
[Moto Maxx Original Android Development] ChazzMatt:
12/09 nightly adds VoLTE!

See changelog:

http://www.cmxlog.com/12.1/quark/

Thanks [MENTION=2228410]Skrilax_CZ[/MENTION]
[Moto Maxx Original Android Development] GreaterLesser:
The latest nightly broke all cellular communications on my device and I've tried almost everything to recover it. Not happy at all...
[Moto Maxx Original Android Development] miketoasty:
Cell comms work fine for me, just can't find the option for VoLTE.
[Moto Maxx Original Android Development] GreaterLesser:
Can you make a call?
[Moto Maxx Original Android Development] miketoasty:
Yep, just called two different people on WiFi and LTE.

Edit: And have been texting people all night.
[Moto Maxx Original Android Development] ChazzMatt:
I can.
[Moto Maxx Original Android Development] GreaterLesser:
You're on an XT1225 I'm on a XT1254 so there has to be something breaking on mine that isn't on yours ( or so it seems )

---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------

So then just my phone is f'ed up on the latest nightly...wonderful
[Moto Maxx Original Android Development] miketoasty:
Are you running a custom kernel? I'm on stock.
[Moto Maxx Original Android Development] GreaterLesser:
I'm on stock CM kernel as well.
[Moto Maxx Original Android Development] miketoasty:
Try redownloading and re flashing the latest nightly. Has to be something going on in the background.

What's happening when it fails? Does it give you any info?
[Moto Maxx Original Android Development] GreaterLesser:
That's the thing that confuses me is that the download or install of the update never fails

I've downloaded and flashed it 3 times total by now
[Moto Maxx Original Android Development] miketoasty:
Might just want to format all and start from scratch. Best thing to try to see if it at least makes calls then.
[Moto Maxx Original Android Development] GreaterLesser:
Did that....
[Moto Maxx Original Android Development] quantum tao:
do the verizon apps work? visual voice mail, message+, and my verizon?
[Moto Maxx Original Android Development] GreaterLesser:
Message+ and My Verizon do (download from the playstore) but visual voicemail doesn't seem to be working still
[Moto Maxx Original Android Development] ChazzMatt:
Settings/mobile network
[Moto Maxx Original Android Development] miketoasty:
On the 12/09 monthly. Am I missing something stupid?
[Moto Maxx Original Android Development] ChazzMatt:
Enhanced 4G LTE mode is new. Why are you on "global"?
[Moto Maxx Original Android Development] miketoasty:
It's what it was set on by default, but I'm guessing you aren't on the XT1224?
[Moto Maxx Original Android Development] quantum tao:
mine looks like this also, running 12/09 nightly
[Moto Maxx Original Android Development] Skrilax_CZ:
Can you do "adb shell getprop ro.fsg-id" and post result? Might have been the other patch, but it works fine for me on T-Mobile (XT1225).

Verizon might need full IMS though :/
[Moto Maxx Original Android Development] ChazzMatt:
no I'm not on the XT1254, but that enhanced LTE option was not there before.
[Moto Maxx Original Android Development] Fulbring:
The clock application keeps crashing with the new nightly build
[Moto Maxx Original Android Development] miketoasty:
My point was that I'm guessing that it doesn't work on the Verizon variant right now, anything I could do to help get this working [MENTION=2228410]Skrilax_CZ[/MENTION]?
[Moto Maxx Original Android Development] GreaterLesser:
I checked this before and this is what's confusing me as to why it doesn't work. Here you go.
[Moto Maxx Original Android Development] ChazzMatt:
Over in the Resurrection Remix thread some XT1254 are seeing the new Enhanced 4G LTE Mode , some are not.

The people not seeing it seem to be on "global" instead of "LTE Preferred". Or at least that's what it seems. See this post:

http://xdaforums.com/showpost.php?p=64247774&postcount=418

Both these people below are Verizon CDMA/LTE:

But, perhaps that difference is a symptom of the problem, not the cause. I don't know. I just see the difference.