yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] ChazzMatt:
And even then only VoLTE on Verizon network. CF ROM is merely debloated, tweaked stock Verizon Marshmallow firmware for Verizon Droid Turbo XT1254/U.S. Moto Maxx XT1250 (which is really the same phone, with same FCC ID as the XT1254). You will not get Verizon VoLTE with the XT1225, as it has a different FCC ID.

C.F. merely did not remove whatever makes VoLTE work on Verizon in that ROM, for the XT1254/XT1250.

You will only get Verizon VoLTE with that stock-based ROM and no VoLTE on any carriers (including Verizon) with any other ROM.
[Moto Maxx Android Development] sheerxda:
I dirty flashed v4.4 over v4.3 (which is also dirty flashed over v4.2)

Since I upgraded to v4.4 I don't get any crashes except for the audio mods, and even those are fewer now.

Settings still crashes when I go to Settings > Gestures > Device Gestures

EDIT: Updated to magisk v13.1 and now I can use Android Pay! :D

So far so good. Keep it up DevMarsh, you're great! Thanks for releasing v4.4 so quickly after v4.3! Now I'm ready for DefCon :cool:

Edit: Magisk v13.1 notes
[Moto Maxx Android Development] newbe1droidx:
Well i have a strange problem, just did a clean install, wiped everything, latest gapps pico and cant get past google verify your phone. Nomatter what email i use get unknown error try again 24hrs. Any ideas?

Cant skip it either.

Droid turbo 32gig

Well couldnt get it to work so went back to rr-n.
[Moto Maxx Android Development] kenedi jr:
I'm the last update... How i can root ? I miss fault This
[Moto Maxx Android Development] K3n H1mur4:
This ROM needs manual root, use magisk or flash a SuperSU zip in recovery and you're good to go.
[Moto Maxx Android Development] EVNS:
I have seen the same problem.

Settings still crashes when I go to Settings > Gestures > Device Gestures, when click get app stop work.

Hope next update a repair. Thx [MENTION=8166511]Dev Marsh[/MENTION]
[Moto Maxx Android Development] Iqu_5:
Excellent ROM! But, is there the Camera API 2 in the build? If not, how can i get it?

Thanks
[Moto Maxx Android Development] K3n H1mur4:
I'm not sure the Quark supports Camera 2 (even though it is supposed to be a smaller and non-google-branded version of the Nexus 6, which supports it). I'd like to see this working also, though, manual controls are pretty handy considering how I use the phone's camera.
[Moto Maxx Android Development] Septfox:
I was curious about this, so I went and looked at the specs.

The Nexus 6 has a lot of similar hardware, but one of the things that is completely different is the camera; it uses a 12mp module with OIS, while we have a 21mp module with...uh...more pixels. I think that was around the time where manufacturers were all "the camera has fewer pixels but they're BIGGER so better low-light performance!", but not sure.

Sooo...the Quark probably has an older camera that missed out on Camera2 support. I'm curious as to whether the N6 module is electrically and physically compatible though, it would be neat if upgrading was as simple as snapping the camera in and swiping the needed software from the N6. But I doubt it is.
[Moto Maxx Android Development] LifeAsADroid:
Hi all.

Installed latest quark build, clean flash install (after wiping system, data, cache, and dalvik), then flashed opengapps arm 7.1 nano, then flashed supersu beta 2.62. Took a while to load but ended up rebooting, however the phone had no cellular data signal. Did I do something wrong? Something I have to enable after flash?

XT1254 (Turbo)
[Moto Maxx Android Development] ChazzMatt:
At this point in time you can use newest latest SuperSu. It's only when you first unlock your bootloader and want initial root for that stock Motorola Marshmallow that you need the older beta 2.62 SuperSu. After that, no need, even if you had stayed on stock firmware, you can update to the newest stable SuperSu.

As for cell data signal, three things to try/check.

1) Go into Settings,

make sure Cellular Networks is turned on and

under Data usage, make sure Cellular Data is turned on.

On my phones, about once a month one of those two settings gets turned off for no reason -- but when it happens, it's always after a reboot.

2) Download [MENTION=5747496]bhb27[/MENTION]'s Clear Modem file and flash it in TWRP. Changing ROMs, your modem can get confused. Usually it's GPS issues, but could be this also. This file basically cleans your modem's cache for a fresh start.

Clean_modem_status.zip

https://www.androidfilehost.com/?fid=24531035584725320

3) Re-flash your modem in TWRP. For Droid Turbo XT1254, this is the latest TWRP-flashable file:

MCG24.251-5-5 ModemFsg.zip (Only for XT1254 or XT1250, not for XT1225!)

https://www.androidfilehost.com/?fid=745425885120733904

Even if you do #3, also make sure you do #2.
[Moto Maxx Android Development] LifeAsADroid:
Thanks for the links to the flashable files and for the info on helping to get on cell data. Turns out the cell data was turned off by default (I guess turned on during initial setup then switched off upon first arriving at the home screen), so problem is solved. I did flash the new modem anyway prior to booting up again with the flashed ROM (I reverted back to my backed up stock MM I came from when data wasn't working and I couldn't figure it out), I figured the new modem couldn't hurt since I was last on -5 stock software and not the -5-5.

Thanks so much for all the help you've given me in multiple threads in the last 24 hours or less. It is always reassuring that people like you with your expansive knowledge are out there to help those of us who are not as in-the-know.

EDIT: It turns out I've thanked you too much according to xda. I'll hit you up again when my fresh set of 8 "thanks" are renewed.
[Moto Maxx Android Development] LifeAsADroid:
I had an interesting question whilst setting up AOSPExtended for my tastes. Without having to set up an on-screen navigation bar (which would seem rather silly with the capacitive buttons just below the screen) is there a way to adjust the functionality of the capacitive buttons themselves? i.e. - I'd like to make a long press on the back button act like a "kill app" long press, all without having a lower on-screen navigation bar.

EDIT: I also can't seem to figure out where to find the adjustments for the notification light colors, etc.

With latest build, nano GApps, and flashing the -5-5 modem update I haven't had any problems so far. Really liking this device and OS.
[Moto Maxx Android Development] ChazzMatt:
For the capacitive button, in RR 6.x it's in Settings/Configuration/Button Controller. Do a search in Settings for "Button", see what comes up? In RR 6.X. I made the Recents button also be the app menu button with a long press, in addition to being the Recents button with short (regular) press. Also, made the Home button bring up Search Assistant with long press.

Also in Settings, go up to Search and type in Notification light. See what comes up? I know those are in RR 6.X and 7.X, but I don't know much about this ROM.
[Moto Maxx Android Development] LifeAsADroid:
I think it might be different for this ROM as far as the capacitive buttons go. I couldn't find any adjustment, including in the Extended section of settings and with a "button" search.

The Notification Light search worked, thanks. Side note, I did notice that my notification light only seems to display a green color when custom colors are active and no matter what the custom value is set for a specific app (i.e. - mail.com email app blinks green when email received when set to blue color, led blinks green during setup of color as well). Also noticed that the led itself behind the glass front is sort of off-set from the clear hole it should be showing through.

It's a refurbished phone, so who knows.
[Moto Maxx Android Development] ChazzMatt:
These Quark phones only have green LED. It's supposed to be for low battery notifications, but [MENTION=5747496]bhb27[/MENTION] repurposed it to be for general notification. Motorola didn't put in a regular LED, just green.

Here's the part of the button control panel from RR.
[Moto Maxx Android Development] LifeAsADroid:
Just an FYI for others:

Found the capacitive button custom settings in AOSPExtended. Settings --> Extenstions --> System --> Buttons --> scroll down. Don't know how using search for "button" or "buttons" in settings as you suggested didn't take me here, maybe the way the search function is set up and what it searches on.

Thanks for the notification led info. Good to know. :good:
[Moto Maxx Android Development] guneri:
Essa rom é boa mesmo? Viu você já teve problema com a tela dele? Muitas vezes a minha tela "congela", quando estou usando algum aplicativo, aí preciso bloquear a tela com o botão power e desbloquear que volta ao normal, eu achava que era sistema, mas todas as versões continuaram com esse problema, até que um dia eu tirei todos os efeitos gráficos, e até agora não se repetiu, mas queria saber, se isso é um bug do moto maxx. Valeu
[Moto Maxx Android Development] Hlcpereira:
Only English here at XDA, ok? And so, yes it's good, do a format data in TWRP if a clean install don't solve the screen issue in any ROM.
[Moto Maxx Android Development] Marky__Mark:
Should be another build coming out soon...
[Moto Maxx Android Development] guneri:
Hi, when i will start capture using some app, show a windows whit this message ("this app will start capturing everythings that's displayed no your screen.")

and have 2 options that i can choice ("CANCEL or START NOW"), but the option "START NOW" i cant not press, the BUTTON gets stuck, nothing happend.

And this BUG happens in other apps that this windows show. Someone could help me ?
[Moto Maxx Android Development] Hlcpereira:
Remove all overlay apps and see if it works.
[Moto Maxx Android Development] tismond:
I clean flashed the latest build and so far smooth as silk. I am only using it about 8 hours and I haven't found any bugs as yet
[Moto Maxx Android Development] fgl27:
Can you not use my custom kernel on your ROM build, can you request use of my work on yours ROM before use?

Can you give the developers that you are using they work credit?

can you please?

this is the branch that I'm OK of you or anyone to use on a custom ROM

https://github.com/bhb27/BHB27Kernel/commits/N

my N_c branch, is for my on personal use for my kernel tread I do not give you or anyone that wanna to included that on a ROM permission unless they prove they know what they are doing, yes is a open source repo but I'm don't support that one to be released with a ROM as I personally make a "special" zip that do things that unless you are doing from others three you are releasing a bad version of my kernel as you do not post any tree on your ROM thread never contact me to use it I must assume you are doing it wrong and sharing my work on a way is not supported by me, as you are not delivering the experience I wish from my work, that on my view is very bad I don't like it.

Yes all my work is open source yes is for anyone to use, but you must give the proper credit and use it the right way, share the specific device tree, kernel or wherever you are using to build this ROM on the OP quoted here so any one can see that you are not dong it the right way, sharing the tree you are using is a XDA rule, that is way I share not because I wanna credit, but credit must be given on wherever they apply, after all I give a lot of my free time for quark for my view you are just copy my work releasing here without any permission any communication with me any credit.

thank you.
[Moto Maxx Android Development] Romullo Sousa:
[MENTION=5747496]bhb27 [/MENTION] Felipe Leon, I apologize to you! At no time did I want to harm or harm the image of your work. I recognize all your potential and work involving the quark, I have always used the version of your kernel in my constructions, by the exelençia of the same ones ... and even by the request of the users .. and at no time I wanted to do a KANG! The credits were fixed on my thread and were only removed in this update when I updated it. A lack of attention on my part! I just found the best option when it comes to the quark and I thought there would be no problem since other devs use their source for constructions ... you're in luck for your work .. and Again forgive me for this ... I'll be arranging this in a next update.

And I'm sorry I used the N_c!

thank you!
[Moto Maxx Android Development] ChazzMatt:
All the other Quark devs (including [MENTION=5747496]bhb27[/MENTION]) use the "stock" CM/LOS kernel. Yes, [MENTION=5747496]bhb27[/MENTION] also codes that... but it's not his advanced custom kernel. He doesn't even use that custom kernel in his own ROMs. Users have to download and install that manually.

I think he's upset you used the "wrong" kernel, besides not giving credit (which may have been a mistake).
[Moto Maxx Android Development] Romullo Sousa:
Yes i understand him
[Moto Maxx Android Development] Marky__Mark:
[MENTION=8166511]Dev Marsh[/MENTION] The only bug i found in this build is the "in pocket detection". It sometimes stays on while on the lockscreen.
[Moto Maxx Android Development] fgl27:
Thanks I appreciate, to be clear as I was not complete last post...

If I have something on a thread, and share it only on that thread I personally don't wanna anyone sharing it on any other thread, the way is very simple, I push updates there whenever I wanna but I only release a final version whenever I fell is ready, some one building it whenever they wanna (that is the case of adding it to a ROM) may build my unfinished work and that unfinished kernel may be problematic or not how I expect it to be, as I experiment a lot some times it is really "bugged", plus the minor changes that I make on the zip that complete the kernel work, they prevent from some random boot problem and set the kernel config the way I wanna.... Plus of course anyone on xda or wherever site must always ask for permission to released someone current active work on some other place that the maker of the thing is not aware of.

:good:
[Moto Maxx Android Development] Marky__Mark:
Whats changed in this build?
[Moto Maxx Android Development] FlavioV:
Check changelog in op right below the download link :good:
[Moto Maxx Android Development] Marky__Mark:
Thats for 8/9. I was hoping for 8/15 and i know all that was changed is the kernel, but wanted to check if the pocket detection bug was also fixed. Ill have to tey out the rom.
[Moto Maxx Android Development] Romullo Sousa:
For users who are having problems with scrolling speed modify these two lines in build.prop!

[B]

ro.min.fling_velocity=140
ro.max.fling_velocity=20000

[/B]

I'll be correcting this in the next update
[Moto Maxx Android Development] Marky__Mark:
Appears the pocket detection bug is fixed. Maybe it was the kernel.
[Moto Maxx Android Development] GeekyTanuj:
Great work!

I highly appreciate the much needed work in our quark section however if you guys could port more aosp roms like cardinal aosp,pure nexus, paranoid Android,aosp+OMS ;the work of base should be much appreciated here since some users like me would like more of a pure untouched ROM too!
[Moto Maxx Android Development] Hlcpereira:
[MENTION=8166511]Dev Marsh[/MENTION] have plans to bring a pure Android ROM with OMS support for us (MainstageOS) and I'm with plans to bring Paranoid Android and maybe Pure Nexus too. But first I want to finish school and take a look on kernel and device tree development.
[Moto Maxx Android Development] Rawwr:
Hey I'm on stock marshmallow build, my bro just gave me this device.

i want to install this ROM (as my galaxy note 3 is running on AEX as well)

i need some info about installation ( i have never tried installing custom rom on a locked bootloader of motorola)

can someone help me with unlocking bl ?
[Moto Maxx Android Development] ChazzMatt:
What device? WHICH model Quark do you have? XT1254, XT1225 or XT1250?

For XT1225 or XT1250, go here:

UPDATED GUIDE: How to unlock your MOTO MAXX/MOTO TURBO bootloader/install TWRP/root

For XT1254, go here:

[GUIDE] How to unlock your bootloader, install TWRP and gain root access

Verizon's Droid Turbo XT1254 requires Sunshine's paid bootloader unlock exploit, and thus a different guide. Blame U.S. carrier Verizon. All the other Quarks (XT1225, XT1250) have FREE bootloader unlock from Motorola, but Verizon won't allow that for their phone.

FYI: For the Quark series, model numbers are more important than model names. Motorola used the names repeatedly, i.e. there are TWO "Moto Maxx" phones, the U.S. Moto Maxx XT1250 and the "international" Moto Maxx XT1225. There's also two "Turbo" phones, the Droid Turbo XT1254 and the Moto Turbo XT1225. Yet, they are really all the same phones (just like an LG G3 is an LG G3), with the same specs -- except for radio bands and internal memory options (32GB/64GB) -- and all the custom ROMs (those not based on stock firmware) are compatible with all the Quarks. Because Motorola stupidly used different model names for the same phone for different markets/different carriers, we simply use the Motorola series name "Quark" for the ROMs.

However, you need to know the model NUMBER to know which guide to use to unlock your bootloader, and you will need the model number to know which radio to flash.
[Moto Maxx Android Development] Rawwr:
thanks mate, unfortunately i have XT1254 verizon

i think i'm gonna sell this device and buy some other xD
[Moto Maxx Android Development] RSDamasceno:
Hello!

Firstly, I wanted to thank you for the ROM!

I would like to report a bug that I found when installing this ROM as a secondary in recovery with MultiROM support provided by [MENTION=5747496]bhb27[/MENTION].

Magisk modules do not appear installed after restart and are impossible to install through the MagiskManager.

Logs:
[Moto Maxx Android Development] Marky__Mark:
A lot of my apps are force closing constantly. I dirty flashed so i dont know if its the latest kernel or not. Im on the 8/15 and am going to go back to the previous and see if that corrects it.
[Moto Maxx Android Development] Marky__Mark:
8/9 runs better.
[Moto Maxx Android Development] tismond:
8/9 definitely runs better. So I have moved back to it
[Moto Maxx Android Development] LifeAsADroid:
Agreed. The kernel from 8/9 runs much better.

Anyone having issues with the "screen off after x-time of no activity" function? I set it for 2 minutes, 1 minute, but have never been able to get it to work correctly.
[Moto Maxx Android Development] ChazzMatt:
The kernel from 8/9 was [MENTION=5747496]bhb27[/MENTION] custom kernel used without credit or permission, instead of "stock" CM/LOS kernel (also maintained by [MENTION=5747496]bhb27[/MENTION]). You can

read back in the thread the discussion

between [MENTION=5747496]bhb27[/MENTION] and the

maintainer of this ROM.

The issue has been worked out between the two devs, and I am not saying anything bad about [MENTION=1323566]DevM[/MENTION]arsh. He apologized profusely for the mistake/misunderstanding. Again, you can go back and read the posts.

You can download and install that custom kernel yourself, if you feel that's really the difference. It's just [MENTION=5747496]bhb27[/MENTION] custom kernel. But it's a standalone kernel with advanced features and options. [MENTION=5747496]bhb27[/MENTION] wants users to use it on purpose, not have it bundled into a ROM. [MENTION=5747496]bhb27[/MENTION] doesn't even include it in his own Quark ROMs (RR, crDroid, Mokee, etc.). All Quark ROMs are supposed to use the basic CM/LOS kernel, and if users want the [MENTION=5747496]bhb27[/MENTION] advanced custom kernel, they download and install it themselves in their ROMs.

[MENTION=5747496]bhb27[/MENTION] started doing this custom kernel back when our CM dev [MENTION=2228410]Skrilax_CZ[/MENTION] was coding the basic kernel for CM ROM -- which was also used by all the other ROMs (including the ROMs [MENTION=5747496]bhb27[/MENTION] maintains). Since [MENTION=2228410]Skrilax_CZ[/MENTION] has left, [MENTION=5747496]bhb27[/MENTION] now maintains that basic ROM kernel, as well as still doing his advanced custom namesake kernel.

[Kernel][All Quark]BHB27-Kernel[5.1.1][6.0.1][7.x.x] For Custom and Stock ROM's

Just see what the kernel settings are you currently have on the 8/9 version of this ROM and replicate those on [MENTION=5747496]bhb27[/MENTION] custom kernel on future versions of this ROM, using [MENTION=5747496]bhb27[/MENTION]

modded Kernel Adiutor.

Because that is what you are REALLY USING right now anyway, on 8/9 -- the [MENTION=5747496]bhb27[/MENTION] custom kernel. ;)
[Moto Maxx Android Development] Marky__Mark:
Yes, i know what happened. bhb27 should let it go and let Dev Marsh use his damn kernel. His credit has been given.
[Moto Maxx Android Development] fgl27:
you really don't understand what my point was, really amazing you are, way don't you go back and re read it.

or you think is OK if I do the below?
[Moto Maxx Android Development] ChazzMatt:
Why don't YOU download and install it yourself?

I even provided a link for you.

Same reason you need to install GAPPs yourself, you need to take responsibility and install a custom kernel yourself.
[Moto Maxx Android Development] Marky__Mark:
I understand and now he has credited you so...

---------- Post added at 08:21 AM ---------- Previous post was at 08:21 AM ----------

Seriously? Why are you in this conversation explaining things i already know?

---------- Post added at 08:25 AM ---------- Previous post was at 08:21 AM ----------

Also, im pretty sure hes used your kernel since April when this project started. And i could be wrong, but i do recall you being credited in the OP so it was surprising to me when I saw that was missing recently.
[Moto Maxx Android Development] ChazzMatt:
Because you don't seem to understand. The kernel dev doesn't want his kernel used in that manner, integrated into a ROM. He doesn't even integrate it into his own ROMs.

Read that again.

Do you not know how to install the kernel? Is that the issue? Because you aren't making any sense.

You seem to love the kernel. It's freely available, go install it.

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

Is so, he's been using it without permission since April.
[Moto Maxx Android Development] Marky__Mark:
I get it much better than you since you probably dont even use this rom and love to butt in on threads for roms you're not using with your very elementary advice. Im a tester and the only way i would know if 8/9 was even better in the first place was to revert back to it. Then i can determine it was the kernel, which still isn't 100% proven. I do know i haven't had the best luck with bhb27s kernel and im pretty sure its the adiutor app now, but thats a whole different subject. Dont tell me stuff already know. I install kernels on other devices regularly. Thanks for your help though. I reeeeeally appreciate it!
[Moto Maxx Android Development] ChazzMatt:
Then we agree. You'll go install it, like we've told you several times. And don't blame the kernel dev. You should praise him for making such a good product. You seem to really love it or you wouldn't be complaining so much about it's removal from this ROM. But it's FREELY available and easy to install. It's the exact same kernel you are using right now.

As for the Kernel Adiutor app, make sure you are using the latest modded one by [MENTION=5747496]bhb27[/MENTION], which supports his custom kernel. You should be able to note all your current settings and replicate them on an installation of his custom kernel by using that app. I linked it in a post on previous page, with the kernel link.
[Moto Maxx Android Development] Marky__Mark:
You dont have to tell me to do anything. I will do what i please. Who are you, boss?

---------- Post added at 09:19 AM ---------- Previous post was at 09:17 AM ----------

I dont have to do anything, you see. My rom is running great! I think you should hijack someone elses thread cuz you haven't taught me anything i didn't already know. Install this rom on your phone, then i will listen to you. Even if i already know it.