[Verizon Motorola Droid Turbo Android Development] ChazzMatt:
Wow, you work quick!

The only issue with Resurrection Remix which might concern you is the same as all custom ROMs not based on Verizon stock firmware. Verizon VoLTE doesn't work yet. Verizon has some secret code for their VoLTE which the Quark custom ROM devs (CM or AOSP) have not cracked yet. Even CF who made this stock-based ROM doesn't know how or why Verizon VoLTE works -- except when he debloated the stock firmware he apparently didn't remove whatever makes it work. ;)

Since I'm not using the Droid Turbo -- I have another Quark -- and since I'm not a Verizon customer (I'm on AT&T), I personally don't care about Verizon VoLTE, but to some people it's very important. I don't even care about AT&T VoLTE. However, you may care deeply about Verizon VoLTE. But I explain all this below...

(WARNING: LOTS OF INFORMATION, SOME EDITORIALIZING AHEAD)

The Quark series includes:

Droid Turbo XT1254

U.S. Moto Maxx XT1250 (identical to the XT1254 in every way; they are clones -- except no locked down bootloader.)

Moto Turbo XT1225 (identical to the Moto Maxx XT1225, just re-named for the India market)

"international" Moto Maxx XT1225 (I own three of those, to run on AT&T)

-- and we have

custom ROMs that run on ALL of them

. (That link is to all current Nougat and Marshmallow ROMs for our device.) The Quark had AMAZING top tier specs in late 2014:

1440p AMOLED,

64GB internal memory -- at least on mine!

3GB RAM,

21MP camera,

Qi wireless charging,

QuickCharge 2.0 (which Motorola re-branded as "turbo charge")

and is relevant even this year. Apple is will be going to 1440p AMOLED later this year with the 2017 iPhone, and reportedly finally adding Qi wireless charging. Ha! Welcome to 2014, Apple. ;) In fact, only this year in 2017 are there some flagship Android phones which are clearly superior to what I bought in 2014. Running a custom ROM like RR 6.x (Marshmallow) has made the phone even better -- for instance the notification LED is enabled, for when I get texts/emails/voicemails. (People on stock Moto ROM don't even know there's a notification LED on this device.) Yes, there's Quark Nougat ROMs out there -- SIX at last count -- including RR 7.X, but my set-up very stable and I'm just not ready to switch two daily phones over to a different OS just yet.

Verizon never had any kind of exclusive on this device, in spite of their blatant PR lies. They didn't even have an exclusive in the U.S. -- as the U.S. Moto Maxx XT1250 has the same FCC ID, same radio bands, was sold by at least a dozen regional CDMA/LTE carriers, and runs on Verizon with a Verizon SIM card. The XT1254/XT1250 are the exact same device on every way -- but the Verizon model is simply called "Droid Turbo" instead of "Moto Maxx". Verizon owns the rights to the Droid name, which they licensed from LucasArts (now owned by Disney), and they can call ANY mobile device a "Droid" while no one else can. That is the only exclusivity they have.

"Droid" doesn't even mean "Motorola" -- although Verizon has only used it on Motorola phones. They could also slap the name on an LG or Samsung phone if they wished, since they (the carrier) own the rights to the name, not any manufacturer. Two years ago in 2015 Verizon even used the Droid name on mid-tier Motorola phone with a 6XX Snapdragon chipset with 1080p, 2GB RAM, 16GB internal memory -- so Droid doesn't even mean "the best" anymore, if Verizon intended the name to mean that. The

2014 Droid Turbo has HIGHER SPECS than the 2015 Droid Maxx 2

! (1440p vs 1080p, 3GB RAM vs 2GB RAM, etc.) It's whatever Verizon wants it to mean any particular year. :rolleyes:

The only REAL difference between any of these Quark phones is the XT1254/XT1250 has one FCC ID (and same radio bands) and the XT1225 models (Moto Turbo, "international" Moto Maxx) have another FCC and radio bands (XT1225 has ALL the AT&T radio bands). The XT1225 is 64GB only, the XT1250 is 32GB only while the XT1254 came in choice of 32/64GB internal storage. Oh, I guess the key difference in the Quarks is Verizon demanded Motorola lock down the XT1254 bootloader, while the other models were not. These were phones sold all over the world in different countries, by different carriers -- but the XT1254 was the only one with a locked down bootloader. Blame Verizon for that. We have people from other countries (who are using GSM-based carriers) who buy the Droid Turbo on the used-phone market and then complain about the locked down bootloader. Well, you bought the WRONG Quark.

The XT1225 and XT1254/XT1250 all share LTE bands 2, 3, 4, 7.

The XT1225 additionally has LTE band 5 and 17 (more bands used by AT&T).

___________________

FCC ID IHDT56PK2

____________________

The XT1254/XT1250 instead has LTE band 13 (Verizon LTE band), plus CDMA bands. While it does have some HSPA bands, there's not as many as in the XT1225.

FCC ID IHDT56PK1

______________________

The Quarks were released in late 2014, early 2015 (India) to the world. In 2014 I immediately bought two of them to run on AT&T, and a year later bought a 3rd to have a emergency backup and is still new in the box. From the very beginning we could root, install Xposed/Gravity Box to emulate a ROM (except the Droid Turbo XT1254, because of the locked down bootloader). And there's been a plethora of CM-based custom ROMs for the Quarks since March 2015 (again, except the Droid Turbo XT1254, because of the locked down bootloader).

So, when the XT1254 bootloader FINALLY was unlocked by Sunshine team in November 2015, the CM dev at the time [MENTION=2228410]Skrilax_CZ[/MENTION] modified the CM tree kernel so that it would be compatible for ALL Quarks, including the XT1254. HE was the one who modified the Motorola XT1225 kernel in the first place to be compatible for CM. The Droid Turbo XT1254 was finally able to join the custom ROM party. Since then [MENTION=5747496]bhb27[/MENTION] (who lives in Brazil) has taken over that work. [MENTION=5747496]bhb27[/MENTION] made the TWRP you are using; he got us official TWRP status for our device. He develops a standalone advanced kernel, as well as two custom ROMs -- Resurrection Remix and crDroid. He also made the "clean modem" status file we often use when flashing ROMs to clear the modem cache.

BUT, Verizon introduced VoLTE in July 2015 with Lollipop and that is one thing all the options and tweaks of the CM-based custom ROMs haven't yet been able to replicate: VoLTE for Verizon. Still a ton of Droid Turbo users either don't need it because they are not actually Verizon customers (they use some other carrier) or they don't care because custom ROMs offer so many other tweaks/options/enhancements they deem are better than the ability to have data + voice during a phone call. It's a trade-off. Many people use their smartphones more as a hand held computer and only occasionally make phone calls. Two of the Quark custom ROM devs -- AOKP and the unofficial LOS/CM 14.1 -- do own the Droid Turbo XT1254 and are Verizon users. So, to them not having Verizon VoLTE is not a deal-killer to using non-stock based ROM. That's not to say they don't want it also -- there's

an entire thread in this forum devoted to the subject.

And of course, none of the other non-Droid Turbo Quark owners (like me on the XT1225 on AT&T) need Verizon VoLTE. As an AT&T customer with a non-AT&T branded Motorola phone (imported from two Latin American countries), I'll never even get AT&T VoLTE and I don't care. When I make a phone call, my phone automatically drops down temporarily to HSPA (which has simultaneous voice + data). When phone call is over, my phone jumps back to LTE. No big deal. It's only CDMA-based carriers like Verizon which NEED VoLTE. CDMA is handicapped in not being able to do simultaneous voice + data, and LTE is data only, unless you have VoLTE. Whereas GSM/HSPA has always been able to do simultaneous voice + data.

Where this CF Verizon stock-based ROM shines is for Droid Turbo owners who want Verizon firmware, but made better. VoLTE works on Verizon. Bloatware is gone. Audio is enhanced. All Moto features are there under Moto names. The

CM-based custom ROMs

(even the ones that claim to be AOSP still have to use the Quark CM-kernel) have Quark Ambient Display that replicates the proprietary "Moto Display", but some people want it to say "Moto Display". Most of the Moto apps can be downloaded and installed from Google Play store on custom ROMs. But for Moto Display you have to use Quark Ambient Display, and for Moto Voice you have to use "OK Google" or comparable 3rd party app (there's several last time I checked). In fact, there's no Motorola feature (I'm aware of) that are unique and which has not been duplicated a built-in option in the various custom ROMs or at least available by installing a 3rd party app -- and in many cases even IMPROVED. :rolleyes: But some people don't want that -- they just want stock firmware, but don't want to spend endless hours tweaking stuff themselves when a dev like CF has done it for them. I have recommended this CF ROM to many Droid Turbo users who just unlocked their bootloaders, rooted, installed TWRP and don't know what to do next. It's the best way to immediately improve their Droid Turbo XT1254.

But Verizon VoLTe is not a Moto feature, it's a carrier feature. And as a rescue truck driver, and if you are a Verizon customer, I can see how that feature would be important to you -- maps navigation while making a voice phone call. However, I do know Google Maps also has an "offline" feature where you can download a custom area for Google maps that will stay resident in your phone and can use just your GPS to navigate (while you temporarily don't have data). It doesn't depend on data signal from carrier. Here in Atlanta area, I do that for my and my wife's phones just in case we get into a no-signal area. I designate a huge metro Atlanta area in Google Maps, and have it download to our devices. It will automatically re-new every 30 days for any changes (lots of highway construction in this area, so that's good). This example below is for New York city, but you get the idea...