[Moto MAXX XT1225 / Droid Turbo XT1254][OFFICIAL] CyanogenMod 13.0

[ChazzMatt]

Is this device no longer supported on CM13? I am not seeing new nightlies and the change log no longer exists.

Dev is still working on it. He posted a few times this week over here in the OTHER Quark forum:

http://forum.xda-developers.com/mot...axx-xt1225-droid-turbo-xt1254-t3315912/page79

 

[CyanoTurbo]

Everything I tested so far works. Except searching for network operators which immediately returns an error for me.

Can anyone confirm?

Here is the log:

08-02 12:35:08.658  1872  1872 D phone   : [NetworksList] connection created, binding local service.
08-02 12:35:08.658  1872  1872 D phone   : [NetworksList] load networks list...
08-02 12:35:08.700  1872  1872 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
08-02 12:35:08.700  1872  1872 D NetworkQuery: registering callback class com.android.phone.NetworkSetting$3
08-02 12:35:08.702  1872  1872 D NetworkQuery: starting new query
08-02 12:35:08.712  4884  4884 I HK/LatinKeyboardBaseView: closing org.pocketworkstation.pckeyboard.LatinKeyboardView{97b7608 V.ED..... ......ID 0,0-1440,640 #1020026 android:id/keyboardView}
08-02 12:35:08.761  1872  1872 D NetworkQuery: scan completed, broadcasting results
08-02 12:35:08.762  1872  1872 D NetworkQuery: AsyncResult has exception 1
08-02 12:35:08.762  1872  1872 D NetworkQuery: broadcasting results to class com.android.phone.NetworkSetting$3
08-02 12:35:08.762  1872  1872 D phone   : [NetworksList] notifying message loop of query completion.
08-02 12:35:08.776  1872  1872 D phone   : [NetworksList] networks list loaded
08-02 12:35:08.776  1872  1872 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
08-02 12:35:08.776  1872  1872 D phone   : [NetworksList] hideProgressPanel
08-02 12:35:08.778   745   779 I ActivityManager: Displayed com.android.phone/.NetworkSetting: +216ms
08-02 12:35:08.790  1872  1872 D phone   : [NetworksList] error while querying available networks
08-02 12:35:08.791   745  7685 I NotificationService: cancelToast pkg=com.android.phone [email protected]
08-02 12:35:08.791   745  7685 W NotificationService: Toast already cancelled. pkg=com.android.phone [email protected]

 

[ChazzMatt]

Everything I tested so far works. Except searching for network operators which immediately returns an error for me.

Can anyone confirm?

Here is the log:

08-02 12:35:08.658  1872  1872 D phone   : [NetworksList] connection created, binding local service.
08-02 12:35:08.658  1872  1872 D phone   : [NetworksList] load networks list...
08-02 12:35:08.700  1872  1872 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
08-02 12:35:08.700  1872  1872 D NetworkQuery: registering callback class com.android.phone.NetworkSetting$3
08-02 12:35:08.702  1872  1872 D NetworkQuery: starting new query
08-02 12:35:08.712  4884  4884 I HK/LatinKeyboardBaseView: closing org.pocketworkstation.pckeyboard.LatinKeyboardView{97b7608 V.ED..... ......ID 0,0-1440,640 #1020026 android:id/keyboardView}
08-02 12:35:08.761  1872  1872 D NetworkQuery: scan completed, broadcasting results
08-02 12:35:08.762  1872  1872 D NetworkQuery: AsyncResult has exception 1
08-02 12:35:08.762  1872  1872 D NetworkQuery: broadcasting results to class com.android.phone.NetworkSetting$3
08-02 12:35:08.762  1872  1872 D phone   : [NetworksList] notifying message loop of query completion.
08-02 12:35:08.776  1872  1872 D phone   : [NetworksList] networks list loaded
08-02 12:35:08.776  1872  1872 D NetworkQuery: unregistering callback class com.android.phone.NetworkSetting$3
08-02 12:35:08.776  1872  1872 D phone   : [NetworksList] hideProgressPanel
08-02 12:35:08.778   745   779 I ActivityManager: Displayed com.android.phone/.NetworkSetting: +216ms
08-02 12:35:08.790  1872  1872 D phone   : [NetworksList] error while querying available networks
08-02 12:35:08.791   745  7685 I NotificationService: cancelToast pkg=com.android.phone [email protected]
08-02 12:35:08.791   745  7685 W NotificationService: Toast already cancelled. pkg=com.android.phone [email protected]

Try re-flashing your radio?

 

[CyanoTurbo]

Try re-flashing your radio?

I just tested flashing 44 and 49 radios and the problem persists.

To clarify, auto-detection works just fine (not Verizon btw. I'm not in the US at the moment). But scanning for a list of operators fails.

 

[ChazzMatt]

I just tested flashing 44 and 49 radios and the problem persists.

To clarify, auto-detection works just fine (not Verizon btw. I'm not in the US at the moment). But scanning for a list of operators fails.

and you are sure your SIM card is seated properly? No one else has complained about this, so I'm just trying to figure out where something could be wrong.

 

[CyanoTurbo]

and you are sure your SIM card is seated properly? No one else has complained about this, so I'm just trying to figure out where something could be wrong.

The native network is connected and everything is working just fine. So, I believe the SIM card is seated properly.

I only get an error when:
Settings -> Cellular Networks -> Network operators

I'm not traveling anywhere anytime soon. So it's not a deal-breaker for me at the moment. I just wanted to report it in case the issue is reproducible and the fix is simple.

 

[ahaynes42]

Quick question - I searched this thread but didn't find a definitive answer. If coming from Computerfreek's latest rom based off of .49, do I need to flash radio or bootloader before flashing this? I noticed in the OP that the only Verizon radio/bootloader package listed was .44, not .49.

Edit: Flashed it over latest CF Rom and all is good!

 

[muhammadtalha-13]

Hi. I have seen some bugs on the new nightlies. The nightly released on July 30th was working fine for me, but when I updated, whenever I try to make a call, phone reboots. Also sometimes I receive text messages in a strange way, like when your service provider send you the setting for internet or MMS with a 'save' option. Weird.

And does anyone have info on when are we going to see a CM13 'snapshot' for droid turbo?
Also when a new nightly appears, is it okay to get it via OTA or is it better to do a clean flash? Thanks.

 

[The Horak]

Hi. I have seen some bugs on the new nightlies. The nightly released on July 30th was working fine for me, but when I updated, whenever I try to make a call, phone reboots.

I had an issue similar to that in the past. It has to do with conflicts of some kind (my knowledge is limited) between CM's dialer and Google's dialer. My recommendation is to reflash the same Gapps package every time you update CM. Personally, this is what I do to prevent these issues. People may argue otherwise, and I couldn't care less. Just make sure you check to see if your Gapps package has been updated since the last time you flashed Gapps. I know that Open Gapps updates their packages quite frequently. I hope this helps.

As a fix for now, you can try wiping the system partition, reflash the CM13 ROM, reflash Gapps, reflash any custom kernel if you use one, and see what happens. I always aim for the most stability, though, and would recommend a full wipe. Again, people may say otherwise.

 

[quantum tao]

Hi. I have seen some bugs on the new nightlies. The nightly released on July 30th was working fine for me, but when I updated, whenever I try to make a call, phone reboots. Also sometimes I receive text messages in a strange way, like when your service provider send you the setting for internet or MMS with a 'save' option. Weird.

And does anyone have info on when are we going to see a CM13 'snapshot' for droid turbo?
Also when a new nightly appears, is it okay to get it via OTA or is it better to do a clean flash? Thanks.

you need to select your default dialer. (because you used a gapps that included google dialer).
check your cell network settings and apn setting for the text issue.
ota worked fine for me with nightlies.

 

[CyanoTurbo]

Everything I tested so far works. Except searching for network operators which immediately returns an error for me.

FWIW, I no longer have this issue. I'm going to share what I did in case anyone
else runs into this issue.

* I updated to the nightly from August 10.
* Then, I changed the Preferred network type to 3G.
* Then, I searched for network operators with success.
* Then, I changed the Preferred network type back to LTE.
* Then, I searched for network operators again, also with success.

I don't know if the update alone fixed the issue. Or the change from LTE to 3G
and back.

 

[tutorialbs]

Updating to the Aug 16 nightly put my droid trubo in a boot loop. First time that's happened. Had to reflash Aug 14 nightly from TWRP for it to work again.

 

[kingersj1]

Updating to the Aug 16 nightly put my droid trubo in a boot loop. First time that's happened. Had to reflash Aug 14 nightly from TWRP for it to work again.

Same happened to me. Take this as a warning everyone, stay away!

 

[T.C.]

Same happened to me. Take this as a warning everyone, stay away!

Same here DO NOT UPDATE TO AUG 16 Nightly!

Thank you

 

[RogueGeek]

Same here. Aug 16 Nightly = Boot loop.

 

[muhammadtalha-13]

I just downloaded the latest nightly. How lucky that I opened this thread before flashing.

And now with the CM13 snapshot being released, hopefully we'll get it soon.

 

[muhammadtalha-13]

Has anyone tried Aug 17 nightly? Is the boot loop problem of Aug 16 nightly still there?

 

[wellwisher_k]

GAPPS: http://opengapps.org/?api=6.0[/QUOTE]

Which variant of GAPPS should I download for cm 13? There are many listed.

 

[skythian]

Has anyone tried Aug 17 nightly? Is the boot loop problem of Aug 16 nightly still there?

Yes. Same problem.

 

[ahaynes42]

Media Volume Bug

I have a bug in music apps when a song ends and starts the next song, the bluetooth media volume gets lowered, either just a step or two or sometimes completely down to zero. It's not consistent on every song change, but it happens enough to be really annoying in day-to-day usage. Has anybody else seen this or can you recreate it?