[ROM][NOUGAT][QUARK][AOKP 7.?]DROID Turbo/Moto MAXX

[Nitefire77]

Can you please check if it does work in Portuguese?

How am I supposed to test that? I only speak 3 languages, and they are Sarcasm, asshole, and English.

Doing a google search led me to believe it only works with English and Hindu, but one would have to test it to see

 

[Debuffer]

How am I supposed to test that? I only speak 3 languages, and they are Sarcasm, asshole, and English.

Doing a google search led me to believe it only works with English and Hindu, but one would have to test it to see

You can turn your language to Portuguese (Brasil) and test if it works. If it does open the Google Assistant, it does work. If it opens the normal Google Now on Tap, it doesn't work.

 

[mdehrlich]

When the screen is off, the voice function is a hit or miss in my experience, but I don't have any problem triggering the search app in any screen when the phone it's in use.

My nexus5x running official release is reliable for "OK Google" anytime, even screen dark. The droid asks to retrain voice Everytime it's triggered. Not saving voice model wherever it's supposed to go. Never works with dark screen. Really want to use droid for daily. I like your enhancements.

 

[johnjingle]

I have a mathematics and computer science degree and I have looked through all the VoLTE files from the site I posted, but I can't understand how and or what we are missing here code wise. SQL and databases are easy for my but I cannot make sense of what little bit of coding we are missing.
I know are phones are old, but it is the best phone I have ever had.

At least I tried. I wish there was someone more knowledgeable to point me in the right direction. I don't mind spending a little time looking through code, but what I have deducted is that there is some kind of hidden encrypted key that Verizon uses. To put it simply, it is like when you install a program on your computer and some other random files get installed to make sure you can't bypass "their" algorithm.

Correct if I am wrong.

 

[tecsironman]

I have a mathematics and computer science degree and I have looked through all the VoLTE files from the site I posted, but I can't understand how and or what we are missing here code wise. SQL and databases are easy for my but I cannot make sense of what little bit of coding we are missing.
I know are phones are old, but it is the best phone I have ever had.

At least I tried. I wish there was someone more knowledgeable to point me in the right direction. I don't mind spending a little time looking through code, but what I have deducted is that there is some kind of hidden encrypted key that Verizon uses. To put it simply, it is like when you install a program on your computer and some other random files get installed to make sure you can't bypass "their" algorithm.

Correct if I am wrong.

I bet it has something to do with the stock apps installed with the stock ROM. Everything could be correct on the custom ROM side but it seems like there is program check or device check with the cell service that doesn't register.

Sent from my XT1254 using Tapatalk

 

[00ffej]

ComputerFreak said stock myvzw app needs to be installed for VoLTE, so I'm assuming that's the case

 

[johnjingle]

ComputerFreak said stock myvzw app needs to be installed for VoLTE, so I'm assuming that's the case

I completely agree that you are right, but there has to be some way to trick the code/system I am missing something. What is Verizon implementing/injecting to thwart this? If the boot loader has been unlocked there should be a way to do this. If anyone can give me help, I will read the code. I just need direction.

Unlocking the bootloader should be way more hard than this, or am I wrong?

 

[00ffej]

Have you seen the patch for VoLTE on Nougat?
https://forum.xda-developers.com/re...t/volte-patches-nougat-based-cm-roms-t3509257

 

[johnjingle]

I am using computerfreeks ROM right now because of work and the necessity of VoLTE. I need a laptop with Internet and the capability to talk to clients while using my laptop. He did a great job with the new MM Rom.

 

[00ffej]

https://github.com/MotorolaMobilityLLC/kernel-msm/issues/85
May have to wait until an official radio is released before we get VoLTE on N

 

[johnjingle]

https://github.com/MotorolaMobilityLLC/kernel-msm/issues/85
May have to wait until an official radio is released before we get VoLTE on N

Moto/Verizon will probably not ever release another radio... this phone unfortunately is not their priority. It's old in terms of phones at and the end of life as far as they are concerned.

Still the best phone I ever purchased.

 

[ChazzMatt]

Moto/Verizon will probably not ever release another radio... this phone unfortunately is not their priority. It's old in terms of phones at and the end of life as far as they are concerned.

Still the best phone I ever purchased.

I'm probably keeping my Quarks another year. If Google, LG or even Moto made a phone like the 5.5" 1440p AMOLED ZTE Axon 7 with front facing stereo speakers (but please add wireless charging ) THAT would be my next phone. But ZTE overachieved on the hardware and under-delivered on the software optimization -- and it has no wireless charging.

I want a reasonable sized, updated NEXUS 6. (This phone was my "Nexus 6".) Until then, I'll keep this phone for 3 years!

---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------

I completely agree that you are right, but there has to be some way to trick the code/system I am missing something. What is Verizon implementing/injecting to thwart this? If the boot loader has been unlocked there should be a way to do this. If anyone can give me help, I will read the code. I just need direction.

Unlocking the bootloader should be way more hard than this, or am I wrong?

You are on the right track in my opinion. There's some secret code or something.

---------- Post added at 04:51 AM ---------- Previous post was at 04:50 AM ----------

https://github.com/MotorolaMobilityLLC/kernel-msm/issues/85
May have to wait until an official radio is released before we get VoLTE on N

But we can't get VoLTE on Marshmallow or Lollipop ROMs either. Has nothing to do with official radio being released. Hasn't official radio been released for at least Lollipop?

 

[Killimanjaro]

Bootloop after theme install

I was running CM13 and was looking into CM14 when I read about CM changing over to Lineage. Searched Lineage to find out they don't have support for XT1254 yet. Anyways, I flashed this ROM (1.11.2017 update) and am happy to report it was initially stable. I installed a theme and like a dummy ignored all the "bootloop warnings" it told me because, "that never happens to me" LOL. I booted to TWRP and re-flashed the ROM and loaded it back. I do get still get the warning about com.phone closing as you mentioned initially but I just click somewhere on the screen and it goes away. I will play around some and continue to report back any issues.

Consesus: Stable and amazing, just be careful in your quests to pimp the theme Many thanks for this awesome update!!

 

[NepoRood]

I was running CM13 and was looking into CM14 when I read about CM changing over to Lineage. Searched Lineage to find out they don't have support for XT1254 yet. Anyways, I flashed this ROM (1.11.2017 update) and am happy to report it was initially stable. I installed a theme and like a dummy ignored all the "bootloop warnings" it told me because, "that never happens to me" LOL. I booted to TWRP and re-flashed the ROM and loaded it back. I do get still get the warning about com.phone closing as you mentioned initially but I just click somewhere on the screen and it goes away. I will play around some and continue to report back any issues.

Consesus: Stable and amazing, just be careful in your quests to pimp the theme Many thanks for this awesome update!!

I didn't post an update on the 11th, that's a nightly from Basketbuild, yes? You (and everyone else) flash nightlies at your own risk. As of now, all my builds are on AFH, the latest will have "official" in the name, older versions as well, some of those say "beta" or "unofficial", you should always get my most current official build.

Regards,
Nepo

 

[ChazzMatt]

I was running CM13 and was looking into CM14 when I read about CM changing over to Lineage. Searched Lineage to find out they don't have support for XT1254 yet.

You wouldn't be looking for XT1254. You would look for

• Quark (phone development code name, like "Shamu" is for Moto Nexus 6) or
• Moto Maxx (the REAL global name of this phone).

In fact, the U.S. Moto Maxx XT1250 is exactly the same device as the Droid Turbo XT1254, down to the FCC ID and exact same radio bands. But Verizon demanded an "exclusive", so Motorola RE-NAMED the Moto Maxx XT1250 to be the "Droid Turbo XT1254". Nothing else changed. As the "international" Moto Maxx XT1225 has ALL the AT&T (and even an HSPA T-mobile band other carriers don't use), this phone was clearly intended to be sold as the "Moto Maxx" across all platforms by at least 3 major U.S. carriers -- Verizon. AT&T and T-Mobile.

Verizon's narcissism screwed up those plans for this phone. Due to Verizon's demands, the "Droid Turbo" was announced and released first, then a month later Motorola released the Moto Maxx XT1250/XT1225 to the rest of the world. But it was supposed to be ALL Moto Maxx! Motorola dropped the plans for AT&T/T-mobile to release this phone in the U.S., even though at least a dozen U.S. regional CMDA/LTE carriers still did carry the U.S. Moto Maxx XT1250. But as those carriers fly under the radar, Verizon was still able to LIE and claim they had an "exclusive". There was no exclusive, not even in the U.S. Motorola released the AT&T-friendly model Moto Maxx XT1225 in Latin American countries and initially left off some of the LTE bands on the official specs, even though we knew they were there. (Some spec websites still don't show LTE band 5 for the XT1225, even though the FCC found it and Motorola later admitted it's there, when they released the XT1225 in India, March 2015.)

Then, months later when the Moto Maxx XT1225 was going to be released in India, Motorola realized there was a Max/Maxx carrier in that country and did not want confusion about any association with that carrier. So, for India, they re-named the XT1225 as the Moto Turbo. But still, "Moto Maxx" is the REAL name for Quark, just like LG G3 and LG G4 is called LG G3 and LG G4 (all with different radios, FCC ID -- but still considered the "same" phone model), no matter where it's sold or used in any part of the world.

If you look at this official Lineage OS list, you will see Quark/Moto Maxx.

Supported List Of Devices for Official Lineage OS
http://www.lineageosrom.com/2016/12/list-of-devices-getting-official.html

Our official CM dev @Skrilax_CZ (who did the initial kernel work for CM12, CM12.1, CM13 and gave us OFFICIAL versions of all those ROMS -- which then allowed all the other custom ROMs for our Quark) has taken a break for a little while. We hope he's OK, but the work still continues! We've long had Nougat CM14-based ROMs and even an unofficial CM14-based ROM from @calsurferpunk -- with recent name change to reflect Lineage OS.

And we've long had other custom ROMs based on CM14, now called Lineage (nicknamed LOS).

I don't normally post about other ROMs in someone's ROM thread, and this AOKP Nougat ROM by @NepoRood is reportedly one of the best. But you seem to think there's no CM14/LOS ROMS for Quark (XT1254/XT1250/XT1225) out there? Maybe you don't know about the OTHER QUARK XDA forum?

Currently we have FOUR Nougat ROMs and all are based on CM14/Lineage sources to varying degrees, especially Resurrection Remix, crDroid, and the unofficial CM14/LOS ROM.

[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=70473048&postcount=58

I installed a theme and like a dummy ignored all the "bootloop warnings" it told me because, "that never happens to me" LOL. I

At least two of those four ROMs have substratum theme support. I know one does not, not sure about the third.

 

[NepoRood]

You wouldn't be looking for XT1254. You would look for Quark (development code name, like "Shamu" is for Moto Nexus 6) or Moto Maxx (the REAL global name of this phone). In fact, the U.S. Moto Maxx XT1250 is exactly the same device as the Droid Turbo XT1254, down to the FCC ID. But Verizon demanded an "exclusive", so Motorola RE-NAMED the Moto Maxx to be the "Droid Turbo". Nothing else changed.

If you look at this list, you will see Quark/Moto Maxx.
http://www.hacksandgeeks.com/single-post/2016/12/31/Lineage-OS-Supported-Devices

Our official CM dev is missing in action, but we've long had Nougat CM14-based ROMs and even an unofficial CM14-based ROM from @calsurferpunk -- with recent name change to reflect Lineage OS.

And we've long had other custom ROMs based on CM14, now called Lineage (nicknamed LOS).

I don't normally post about other ROMs in someone's ROM thread, and this AOKP Nougat ROM by @NepoRood is reportedly one of the best. But you seem to think there's no CM14/LOS ROMS for Quark (XT1254/XT1250/XT1225) out there? Maybe you don't know about the OTHER QUARK XDA forum?

Currently we have FOUR Nougat ROMs and all are based on CM14/Lineage sources to varying degrees, especially Resurrection Remix, crDroid, and the unofficial CM14/LOS ROM.

[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=70473048&postcount=58



At least two of those four ROMs have substratum theme support. I know one does not, not sure about the third.

I don't mind you quoting other ROMs, all the Nougat ones are based off @bhb27's work anyway :highfive:

 

[Killimanjaro]

I didn't post an update on the 11th, that's a nightly from Basketbuild, yes? You (and everyone else) flash nightlies at your own risk. As of now, all my builds are on [AFH], the latest will have "official" in the name, older versions as well, some of those say "beta" or "unofficial", you should always get my most current official build.

Regards,
Nepo

I downloaded an update you upped on 12.11.2016. Apologies, I got my dates mixed up after an 18 hour work day. I downloaded your 1.8.17 update and flashed. Somehow the overlay that Substratum applied caused the bootloop from the 12.11.2016 update. I was able to apply an overlay through Substratum without any hiccups.

I will continue using and reporting any issues I come across to help with development. Battery consumption seems a bit more excessive than previous ROM. I have Greenify activated but want to look into governor/CPU tweaks to see if it improves the battery life.

I had the system UI crash when I tried to enable and screen auto rotate. Firefox seems to crash frequently but need to view the log to determine if it may be app/add-on related or if its the OS.

Also XDA app related. And maybe I need to go to a forum specific for it but keep getting "Post creation failed" when replying. Any ideas?

---------- Post added at 10:56 PM ---------- Previous post was at 10:50 PM ----------

You wouldn't be looking for XT1254. You would look for

• Quark (phone development code name, like "Shamu" is for Moto Nexus 6) or
• Moto Maxx (the REAL global name of this phone).

In fact, the U.S. Moto Maxx XT1250 is exactly the same device as the Droid Turbo XT1254, down to the FCC ID and exact same radio bands. But Verizon demanded an "exclusive", so Motorola RE-NAMED the Moto Maxx XT1250 to be the "Droid Turbo XT1254". Nothing else changed. As the "international" Moto Maxx XT1225 has ALL the AT&T (and even an HSPA T-mobile band other carriers don't use), this phone was clearly intended to be sold as the "Moto Maxx" across all platforms by at least 3 major U.S. carriers -- Verizon. AT&T and T-Mobile.

Verizon's narcissism screwed up those plans for this phone. Due to Verizon's demands, the "Droid Turbo" was announced and released first, then a month later Motorola released the Moto Maxx XT1250/XT1225 to the rest of the world. But it was supposed to be ALL Moto Maxx! Motorola dropped the plans for AT&T/T-mobile to release this phone in the U.S., even though at least a dozen U.S. regional CMDA/LTE carriers still did carry the U.S. Moto Maxx XT1250. But as those carriers fly under the radar, Verizon was still able to LIE and claim they had an "exclusive". There was no exclusive, not even in the U.S. Motorola released the AT&T-friendly model Moto Maxx XT1225 in Latin American countries and initially left off some of the LTE bands on the official specs, even though we knew they were there. (Some spec websites still don't show LTE band 5 for the XT1225, even though the FCC found it and Motorola later admitted it's there, when they released the XT1225 in India, March 2015.)

Then, months later when the Moto Maxx XT1225 was going to be released in India, Motorola realized there was a Max/Maxx carrier in that country and did not want confusion about any association with that carrier. So, for India, they re-named the XT1225 as the Moto Turbo. But still, "Moto Maxx" is the REAL name for Quark, just like LG G3 and LG G4 is called LG G3 and LG G4 (all with different radios, FCC ID -- but still considered the "same" phone model), no matter where it's sold or used in any part of the world.

If you look at this official Lineage OS list, you will see Quark/Moto Maxx.

Supported List Of Devices for Official Lineage OS

Our official CM dev @Skrilax_CZ (who did the initial kernel work for CM12, CM12.1, CM13 and gave us OFFICIAL versions of all those ROMS -- which then allowed all the other custom ROMs for our Quark) has taken a break for a little while. We hope he's OK, but the work still continues! We've long had Nougat CM14-based ROMs and even an unofficial CM14-based ROM from @calsurferpunk -- with recent name change to reflect Lineage OS.

And we've long had other custom ROMs based on CM14, now called Lineage (nicknamed LOS).

I don't normally post about other ROMs in someone's ROM thread, and this AOKP Nougat ROM by @NepoRood is reportedly one of the best. But you seem to think there's no CM14/LOS ROMS for Quark (XT1254/XT1250/XT1225) out there? Maybe you don't know about the OTHER QUARK XDA forum?

Currently we have FOUR Nougat ROMs and all are based on CM14/Lineage sources to varying degrees, especially Resurrection Remix, crDroid, and the unofficial CM14/LOS ROM.

[ROMs][Quarks][List for Moto Maxx and Droid Turbo]




At least two of those four ROMs have substratum theme support. I know one does not, n

Thanks for all of this information! I liked CM mostly because of the ease of updates and the fact they were so frequent. I read where CM14 may not have continued support. I didnt see where LOS supported quark, I got some misinformation obviously. This thread peaked my interest because I wanted to try Nougat out and see how it ran. If LOS continues support I will definitely be willing to try it!

 

[mdehrlich]

I just tried dynamic gapps and the behavior for "OK Google" was identical to opengapps-stock. Not saving voice model. Requests retraining every time it's triggered. No recognition on lock screen or in sleep (dark screen).

 

[cmrntnnr]

Daily Driver

This is an impressive ROM! It has been performing exceedingly well as a daily driver. It is stable, the battery life is long, and the phone is quick and responsive. There are two minor issues that I have bumped into during use. For what it is worth, activation of the flashlight from the pull down is flakey. Sometimes the flashlight turns on sometimes not. When it doesn't work, the button is inactive.

The second is the com.android.phone has stopped message. Neither a dirty flash nor clearing the cache resolve the problem, at least for me. It is just a hunch but it looks like some process needed by com.android.phone doesn't start or doesn't finish starting if you leap immediately in and start using the phone after a reboot or cold-start. I do not experience the message if I let the phone sit idle at the pin screen for about 1-2 minutes after a cold start or reboot. I'd like to help debug. Can someone point me to a guide to monitor the boot process to gather some info about what is happening?

 

[johnjingle]

This is an impressive ROM! It has been performing exceedingly well as a daily driver. It is stable, the battery life is long, and the phone is quick and responsive. There are two minor issues that I have bumped into during use. For what it is worth, activation of the flashlight from the pull down is flakey. Sometimes the flashlight turns on sometimes not. When it doesn't work, the button is inactive.

The second is the com.android.phone has stopped message. Neither a dirty flash nor clearing the cache resolve the problem, at least for me. It is just a hunch but it looks like some process needed by com.android.phone doesn't start or doesn't finish starting if you leap immediately in and start using the phone after a reboot or cold-start. I do not experience the message if I let the phone sit idle at the pin screen for about 1-2 minutes after a cold start or reboot. I'd like to help debug. Can someone point me to a guide to monitor the boot process to gather some info about what is happening?

Get a logcat and you can look through it to see where the errors are.
You an download apps from the PlayStore like:
Kernel Adiutor or aLogcat