Database Develop

Most stable, fasted ROM?

I am coming from a Nexus 5, where we didn't have to worry about downgrading or upgrading, or which ROM to flash for which variant. Everything was so clean and ready to flash for me. I loved it.
Due to damage, I lost my Nexus 5 and ended up with a Moto X, for Sprint on 4.4.4. I have already unlocked the bootloader and rooted it on stock. But the bloatware on this thing is ungodly. So without me having to go and individually freeze everything, I wanted a lightweight, fast, and stable ROM to flash.
The problem is I see none. I see a lot of unofficial, and nightly ROMs, but nothing really fitting my criteria. I don't want something with bugs either. I couldn't find a good (Sprint) stock ROM. I saw one thread, but I didn't understand why there were 3 download links, ROM, Firmware, and SOAK. I am just unsure how to go about finding the ROM of my dreams (lol). I'd prefer something like stock de/odexed (either) with all bloat removed and maybe some minor/major speed/tweak enhancements. I don't really care though. Just bloat removed, quick, and stable.
Any suggestions? Thanks.

Heck, I'd event be thankful for a complete guide on what I can uninstall/change myself! The Moto X is a great phone, just feels incredibly slow.

Sounds like Eclipse is what your looking for.

Or Krypton. I just use stock with Xposed and GravityBox.

Krypton is good also. Try them both and make your own decision

The problem I have is I would REALLY love a stock ROM with all bloatware removed except like active notifications/screen thing. But it doesn't really exist for this phone. That's why its hard for me to use stock as of now.

DRatJr said:
The problem I have is I would REALLY love a stock ROM with all bloatware removed except like active notifications/screen thing. But it doesn't really exist for this phone. That's why its hard for me to use stock as of now.
Click to expand...
Click to collapse
Krypton is essentially stock debloated.
Sent from my Moto X using XDA Free mobile app

jco23 said:
Krypton is essentially stock debloated.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
Which one do I download for Sprint Moto X unlocked bootloade and rooted?
I have an XT1056

DRatJr said:
The problem I have is I would REALLY love a stock ROM with all bloatware removed except like active notifications/screen thing. But it doesn't really exist for this phone. That's why its hard for me to use stock as of now.
Click to expand...
Click to collapse
Why not just debloat with titanium backup yourself. Stock, your way.
[emoji106]

How far can i go on my phone?

I have a non dev Moto X from Verizon (XT1060, first gen). It is currently running 4.4.4. What is the most I can do with it? Reading several threads, I am unable to find a conclusive answer regarding this. Looks like sunshine doesn't work nor do most one click tools. My goal is to flash a debloated ROM at the very least if possible.

You won't be able to flash any custom rom without an unlocked bootloader and that's that really. At most you could root(when possible) and manually uninstall bloatwares from the stock rom. I'm glad I had troubles upgrading my phone initially and was able to read about sunshine app on time.
Sent from my XT1060

to the moon and back at least, of course try krypton, or maybe even the modded 5.1 for the 1060, I prefer krypton but the modded 5.1 came a long way quickly I just wasn't feeling the change from simplicity (less options but works perfect for me) of Moto Assist, to the more complex options in LP :/ Check out the respect threads for each rom!

Safestrap only works for 4.4.2 no?

CM13 for Quark

Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.

channing173 said:
Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.
Click to expand...
Click to collapse
The CM Quark dev @Skrilax_CZ just bought a 2nd phone so he can test CM13 while still keeping CM12.1 going on his main phone.
http://forum.xda-developers.com/mot...xx-xt1225-cm12-0-pre-release-t3060089/page100

Rule #1 of Fight Club: Never ask for ETAs.
Sent from my DROID Turbo using Tapatalk

Patiently waiting here too ...
Patiently waiting here too. Marshmallow changes look interesting.
and Thanks in advance,

You'll know as soon as you see a changelog here http://www.cmxlog.com/13/quark/
Sent from my XT1254 using Tapatalk

I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.

EnderKR said:
I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.
Click to expand...
Click to collapse
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was released.
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have -- or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with that ROM let me use my phone the way I wanted, giving me choice back while still using that ROM. The problem with using xposed + custom ROMs is xposed modules are only guaranteed to work on AOSP ROMs that have not been heavily modified. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in the example I gave, "clear all recents".
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options... but I'm comfortable with CM12.1. (CM dev @Skrilax_CZ brought the first custom ROM and kernel for our Quarks, all others that followed are based his work -- especially the kernel.) I'm running CM12.1 on both my Quarks and have been for months. But the point is both Resurrection Remix and CM12.1 are way more advanced than Motorola stock 5.1, as they are both 5.1.1 + custom features.
NOTE: There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else, but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus, Resurrection Remix and even CM12.1 would have the security updates stock ROM does not.
I'm running CM12.1 plus Moto Camera because someone ported the Moto camera for CM users, and CM12.1 has all the other functionality I need (just different names).

ChazzMatt said:
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was .
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with the ROM let me use the phone the way I wanted, giving me choice back while still using that ROM. The problem with that is xposed modules are only guaranteed to work over ROMs that have not been heavily customized already. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in my case, clear all recents.
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options, but I'm comfortable with CM12.1. BOTH are way more advanced than stock 5.1, as they are both 5.1.1 + custom features.
There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus Resurrection Remix would have the security updates stock ROM does not.
Click to expand...
Click to collapse
Fair enough, I appreciate the input. I'm still pretty new to the custom ROM scene, so there's lots to learn. Why not, I'll give Resurrection Remix a try. Sounds like people love it, and I really like the Moto features so I'd want to keep those. Thanks for the advice

I honestly just like the "all my devices are the same" so all my devices that can run cm.

As for CM-13.0, there is still a lot to be done to get it to a daily driver state.

Hurts not having stock mm I'm guessing?
Sent from my XT1254 using Tapatalk

Skrilax_CZ said:
As for CM-13.0, there is still a lot to be done to get it to a daily driver state.
Click to expand...
Click to collapse
koftheworld said:
Hurts not having stock mm I'm guessing?
Click to expand...
Click to collapse
Not necessarily. That didn't stop @Skrilax_CZ from giving us Lollipop (March 2015) before Motorola released stock Lollipop for any of the Quarks. April 2015, Moto Turbo XT1225 was released with stock Lollipop 5.0.2 -- that was the first Quark with stock Lollipop from Motorola. @Skrilax_CZ beat them by using CM12.0 (Lollipop 5.0.2) with Kitkat 4.4.4 kernel, until Motorola publicly released Lollipop 5.0.2 kernel code. (Even though Motorola gave the Moto Turbo XT1225 5.0.2 in April 2015, they didn't release their Lollipop 5.0.2 kernel code publicly for devs to use until a few weeks later.)
Point is, we had Lollipop for Quark before Motorola gave Lollipop to Quark!
And we had CM12.1 (Lollipop 5.1.1) months (mid-April 2015) before Motorola finally gave just 5.1 to the Droid Turbo XT1254 in July 2015:
Skrilax_CZ said:
15th April 2015, 03:37 PM
Done. I have also moved to CM12.1 from now on, so I'll not be backporting latest set of patches back to CM-12.0
Click to expand...
Click to collapse
@Skrilax_CZ used CM12.1 (Lollipop 5.1.1) first with Motorola's 4.4.4 kernel code and then Motorola's 5.0.2 kernel code, until Motorola finally released Lollipop 5.1.x kernel code (September 2015).
Motorola never gave the other Quarks Lollipop 5.1 -- the Moto Turbo XT1225 and Moto Maxx XT1225 officially still have 5.02. and the U.S. Moto Maxx XT1250 (same identical device as the Droid Turbo XT1254, even the same FCC ID) is still "officially" stuck on Kitkat 4.4.4 -- unless you root and install custom Lollipop 5.1.1. ROM. But thanks to devs like @Skrilax_CZ we've had Lollipop 5.1.1 since April 2015!
So, NO, we do not have to wait for Motorola's slow roll-out of stock MM for our Quarks.
____________
mrkhigh said:
I honestly just like the "all my devices are the same" so all my devices that can, run cm.
Click to expand...
Click to collapse
Same here. When I help friends and family, I install CM so I know exactly where all the settings and options are. Two LG G2 phones, a Nexus 7 tablet all owned by other friends or in-laws. My wife's and my Quark XT1225. For some reason I never rooted my wife's Nexus 9 (yet) -- but when I do, it will have CM.
I also install Nova launcher and set all those options the same all all devices (including non-rooted Nexus 9). My wife said, "But my tablet looks like my phone." I replied, "Exactly." That was my intention.
If something isn't acting right, I can quickly diagnose it without having to remember it's set up differently or has an entirely different ROM.

Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.

IonAphis said:
Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.
Click to expand...
Click to collapse
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk

http://forum.xda-developers.com/showpost.php?p=64573429&postcount=1050

cadenmiller60 said:
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears

kitcostantino said:
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears
Click to expand...
Click to collapse
Few things to note and remember that the DPI for the two devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?

GreaterLesser said:
Few things to note and remember that the DPI for the too devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?
Click to expand...
Click to collapse
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.

kitcostantino said:
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.
Click to expand...
Click to collapse
Well for WiFi, Radios, Bluetooth, etc doesn't the drivers need to be added to the build.prop for the system to actually use them? If possible you could use a build.prop for the turbo in Carbon and just tailor it a bit, theoretically of course. I know it's more complicated than I'm making it sound.

lol. yes, but i get what you mean. in older roms (cm10, cm11) to port, youd copy/paste all of the set perm recursives. in cm12.1 i dont know where to start pulling things from. mind you, i know its not as simple as it used to be because of the new dat format. guess i should read up a bit. lol

Data lost

OK, couldn't get much help from the ROM thread... Maybe here I can, Droid turbo, running latest reservation ROM nougant... On any and all calls, I loose data connection, went to Verizon turned off HD, then turned back on, with no success.. any help would be appreciated.....
..

rriffle08 said:
OK, couldn't get much help from the ROM thread... Maybe here I can, Droid turbo, running latest reservation ROM nougant... On any and all calls, I loose data connection, went to Verizon turned off HD, then turned back on, with no success.. any help would be appreciated.....
..
Click to expand...
Click to collapse
You are basically complaining for some reason you were not aware you can't get Verizon VoLTE on any non-stock based ROM with this phone. If you searched the ROM thread you would have known that.
Very well known that Verizon VoLTE only works on stock firmware or stock firmware-based ROM. So, far for the only ROM is CF's debloated, tweaked stock-based Marshmallow ROM. (Somewhere in there is the secret handshake and even he doesn't know what it is.)
ZTE recently got Verizon VoLTE to work on a non-Verizon phone (the ZTE Axon 7) and that VoLTE carries over to LOS/CM based ROMs -- but no devs have yet figured out what ZTE did to get it, nor what LOS/CM has that allows it on THAT phone. Marshmallow didn't have it, but their Nougat does.

First off, wasn't complaining, obviously I'm not nearly as smart as you.. there's a lot of talk on the forums for flashing volte, and thought I might have overlooked something. Or didn't have something set right... And I know when the original Droid, original firmware was installed, if you didn't have HD calling on you would loose data.... Thanks so much for your help.....

rriffle08 said:
First off, wasn't complaining, obviously I'm not nearly as smart as you.. there's a lot of talk on the forums for flashing volte, and thought I might have overlooked something. Or didn't have something set right... And I know when the original Droid, original firmware was installed, if you didn't have HD calling on you would loose data.... Thanks so much for your help.....
Click to expand...
Click to collapse
Not that I'm smart, It's just something we all know. And seriously the information is EVERYWHERE in this forum. Almost every ROM thread has talked about it. Search is your friend in a forum over 2 years old, like this one.
Go read this. It's the most recent complete ROM list for our phones, and it's in the Development section of THIS forum.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=70473048&postcount=58
And then this recent exchange:
tuckeran5607 said:
What would you say is the most stable rom out there right now? Besides stock obviously.
I'm looking to get Google Assistant via Xposed. Everything was great on Nexus Experience, however I ran into issues getting the Google Now Voice prompt to work outside the Google Now App. =/
Click to expand...
Click to collapse
ChazzMatt said:
If you want Nougat, any of these three ROMS have very high reviews. You can go to those threads and ask questions, and see other Droid Turbo owners.
#2 and #3 are maintained by Droid Turbo owners who use Verizon, if that makes a difference to you. But all three are excellent and many Droid Turbo owners are using all three.
[ROM][All Quark][7.x] Resurrection Remix
[ROM][UNOFFICIAL]AOKP 7.x For All Quark
[ROM][Quarks][LOS/CM 14.1 Unofficial][7.1.x][2016-12-30] (hybrid of CM14 and Resurrection Remix)
However, if you need Verizon VoLTE, then you should go with a debloated, tweaked Marshmallow ROM based on stock Motorola Verizon firmware. See below. It's not Nougat, but right now only stock Verizon firmware or a ROM based on stock Verizon firmware can get Verizon VoLTE on this phone -- until a dev discovers the secret handshake. (ZTE has discovered the secret handshake for Verizon VoLTE. Now a dev just needs to figure out what they did.)
_________
@computerfreek274 has now released a Marshmallow ROM for the Droid Turbo XT1254 based on the Verizon's belated Marshmallow firmware. He has debloated it, tweaked it. It has Verizon voicemail app, Verizon VoLTE (only works on Verizon), Verizon Wi-Fi calling (only works on Verizon), some volume boost, and battery saving tweaks.
* Computerfreek274_MM_1.0.4 Marshmallow 6.0.1 Stock rooted VOLte Debloated
http://forum.xda-developers.com/droid-turbo/development/computerfreek274mm1-0-android-6-0-1-t3503634
Click to expand...
Click to collapse
@bhb27 tried to make VoLTE work, and got tired of messing with it as he lives in Brazil, doesn't use Verizon and doesn't have a Droid Turbo XT1254. He owns another Quark, the same one I have, the XT1225. He has said some other dev who uses Verizon and has a Droid Turbo needs to figure it out.
As I said above, ZTE has figured it out with the ZTE Axon 7 (it's not even a Verizon phone!) -- but I guess no one has yet taken the time to compare the differences between their Marshmallow and Nougat builds to see what they did.
There was even a thread here in this forum recently about getting VoLTE on custom ROMS, which has gone nowhere:
VoLTE and Advanced Calling on Droid Turbo Custom Roms
https://forum.xda-developers.com/droid-turbo/general/volte-advanced-calling-droid-turbo-t3564936
BriCo84 said:
I have been watching, waiting, and hoping that someone would figure out and post about being able to use VoLTE or Advanced calling on any of the custom roms (except Computerfreeks), and i am seeing the same scattered information through the forums. I definitely do not have the skills to figure this out, but hopefully some of the skilled developers in this community can post here and work together to figure this out.
I love using a custom rom, and this device is amazing. But the one thing I miss since using @bhb27 custom Resurrection Remix Rom is VoLTE and Advanced Calling.
Click to expand...
Click to collapse
In that thread, I posted all the detailed info I know about the ZTE breakthrough, but that's basically it.

Any good dual boot solutions out there?

I've checked multiROM Manager and XT1254 is not supported, however if some dev would like to take a crack at it here is a wiki that explains how to port it (and if you can in the first place). I've also done extensive testing with dual boot patcher. I got it to work once with a 4.4 ROM (I can't remember exactly which), but after switching back and forth between the ROMS once I couldn't "escape" the secondary ROM and had to restore a backup to get back into the primary ROM (crdroid v3.3).
If you have attempted to dual boot on the Droid Turbo please leave your experiences and findings below, I'd love to see a working solution. Thanks!
Edit: I've found two that work with crdroid v3.3
Bliss xda post Specific tested ROM download
AOKP version list (there is no marshmallow xda post) Specific tested ROM download

Well I have found one ROM (AOKP MM unofficial) that worked flawlessly with dual boot patcher running on crdroid v3.3. What's odd is that the nougat version by the same author does not work, and in fact no nougat ROM has worked with dual boot patcher for me.

Just some commentary... I've never understood the multi-ROM booting thing. I really only run one ROM at a time for both me and my wife. (I buy two phones at a time, and keep them identical as far as settings.) I do have many more apps than my wife -- but same phone, same ROM, same settings.
If I wish to save a ROM to try another out, I can always use TWRP backup save my current ROM and settings, and temporarily install another to see if it's better. But I have no desire to constantly switch back and forth between ROMs, for my "daily driver".
I'm not criticizing your desire in any way, I'm just suggesting maybe that's why it's not available with this phone. Not much demand for reasons I stated.

ChazzMatt said:
Just some commentary... I've never understood the multi-ROM booting thing. I really only run one ROM at a time for both me and my wife. (I buy two phones at a time, and keep them identical as far as settings.) I do have many more apps than my wife -- but same phone, same ROM, same settings.
If I wish to save a ROM to try another out, I can always use TWRP backup save my current ROM and settings, and temporarily install another to see if it's better. But I have no desire to constantly switch back and forth between ROMs, for my "daily driver".
I'm not criticizing your desire in any way, I'm just suggesting maybe that's why it's not available with this phone. Not much demand for reasons I stated.
Click to expand...
Click to collapse
I'm actually with you as far as temporarily installing it to test the ROM, however I have a rather annoying reason to still want it. The only ways to cash checks with my bank is to either physically mail the checks or deposit them by photo. As I'd rather have an automatic solution, I'm left with the latter. However, this leaves me with the problem that the camera doesn't work in their app on custom nougat ROMS (which I run). I tried talking their dev team into fixing it, but they reasonably don't want anything to do with supporting custom ROMS. As I'd rather not go through the whole backup/wipe/restore/repeat routine every time I want to cash a check, I am unfortunately left with dual booting a ROM that their app does support (most ROMS marshmallow or older).

I found another one that works (and finally works with my bank as well ). Here is the forum post for the Bliss ROM.

Stuckurface said:
Edit: I've found two that work with crdroid v3.3
Bliss xda post Specific tested ROM download
AOKP version list (there is no marshmallow xda post) Specific tested ROM download
Click to expand...
Click to collapse
Both of those ROMs are by @NepoRood. He posted them over here in the Droid Turbo forum instead of the other Quark forum as he owned a Droid Turbo. But so does @calsurferpunk, and he still posts his CM14/LOS ROM over in the other Quark forum. We used to be one big forum, but after the split most Quark development got posted over there as the Droid Turbo bootloader had not yet been unlocked by Sunshine. After the Sunshine team unlock, devs just continued posting over there for the most part...
@NepoRood shattered his Droid Turbo, and now has a different phone -- but you could ask him what he did differently to allow multi-ROM for those two Marshmallow ROMs that changed with his Nougat ROM. He said he was still going to post AOKP ROM updates with the help of testers in this forum.
Also, for his Nougat AOKP, make sure you are using his PERSONALIZED builds, not any of the "nightlies". To gain official status, he had to agree not to change anything in the AOKP ROM, but he was allowed to make and post personalized builds which have tweaks.
Last, you've tried all these? Current list of Nougat and Marshmallow. I didn't bother keeping track of Lollipop.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=71821604&postcount=73
___________
Stuckurface said:
I'm actually with you as far as temporarily installing it to test the ROM, however I have a rather annoying reason to still want it. The only ways to cash checks with my bank is to either physically mail the checks or deposit them by photo. As I'd rather have an automatic solution, I'm left with the latter. However, this leaves me with the problem that the camera doesn't work in their app on custom nougat ROMS (which I run).
Click to expand...
Click to collapse
OK, that's a practical reason I can understand.
So, it's nothing about "Safety Net" issues, it's basically newer custom ROMs (Nougat) don't work?
The app of the bank I use (a nationwide mega bank) works fine with RR 6.X (Marshmallow) and before that with CM12.1 (Lollipop) in depositing checks via photo. I've not tried Nougat ROMs yet. So, I may run into the same problem...
I've stayed with RR 6.x as it's rock solid and allows me to use a few xposed modules like Google Assistant Enabler (to turn on and unlock display), YouTube Adaway (to block YouTube ads, which regular Adaway does not) and MinMin Guard (which blocks 99.9% of all in app ads). I wish @bhb27 would release one more "rollup" update before development completely ends.
Of course I will switch to Nougat one day, but I didn't switch to Marshmallow until October of 2016, about the time Nougat was being released.

ChazzMatt said:
We used to be one big forum, but after the split most development got posted over there as the Droid Turbo bootloader had not yet been unlocked by Sunshine....
....Last, you've tried all these? Current list of Nougat and Marshmallow. I didn't bother keeping track of Lollipop.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=71821604&postcount=73
Click to expand...
Click to collapse
I knew that Moto Maxx and Droid Turbo were basically the same phone, but I always stuck to the Turbo forum for fear of bricking my phone/messing up my cell connectivity. I didn't realize that most of the ROMS are cross compatible :/
I tested a few of them but I never saw your list. Thanks for maintaining that, I just wish I had seen it sooner!
ChazzMatt said:
So, it's nothing about "Safety Net" issues, it's basically newer custom ROMs (Nougat) don't work?
Click to expand...
Click to collapse
Yep, I've got the photo check deposit to work on ROMS that don't pass safety net multiple times. The problem appears stem from the way custom nougat ROMS (and more specifically the way my bank app) interacts with the camera, though I haven't tried logging the app's behavior so your guess is as good as mine.

I miss Bliss, on my Turbo (heck, I miss my Turbo, lol)
Nougat ROMs have more security than Marshmallow, it's most likely Your bank app that is causing the problems though. I'm running Screw'D Nougat on my Nexus 6P and have no problems with using my banks mobile app (but, we're Rednecks, )
As far as MultiROM goes, I didn't do anything special to my builds, I don't know why Nougat doesn't work...

Stuckurface said:
I didn't realize that most of the ROMS are cross compatible :/
I tested a few of them but I never saw your list. Thanks for maintaining that, I just wish I had seen it sooner!
Click to expand...
Click to collapse
All the ROMs (especially Marshmallow and Nougat) are cross compatible for all Quarks -- except for CF's Verizon stock-based ROM. This is thanks to the CM dev @Skrilax_CZ who adapted the Motorola kernel so all CM (now LOS) based ROMs would work for all Quarks, after Sunshine team unlocked the Droid Turbo bootloader. @bhb27 has continued that work. Even ROMS like "AOSP" still all use that "universal" kernel coding for all Quark ROMs. Again, the exception is CF's ROM, which are purely Verizon stock firmware, just debloated and tweaked.
There was one older Lollipop ROM that never got updated with the "universal" kernel (after the November 2015 Droid Turbo bootloader unlock), but even CM12.1 (Lollipop), RR Lollipop, and @calsurferpunk's "unofficial" CM12.1 was also cross-compatible with all Quarks.

Multi-ROM has now been released by @bhb27, plus we now have SEVEN Nougat ROMs.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
https://forum.xda-developers.com/showpost.php?p=73459132&postcount=80