yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] imcensored1:
No luck there for me. I've had this issue with Lineage Nougat, Lineage Oreo, RR pie, and now Lineage 10. I've done multiple clean installs over the course of using each OS. I've also had the battery replaced 3 times. with the exception of the first (which was 2016), ive been getting 3-6 months of flawless usage before random shutoffs.
[Moto Maxx Android Development] newbe1droidx:
Wow, sorry to hear that. It might just be time to move on then. Have you tried the stock modded rom? Its 6.0.1 but still works and volte and wifi calling work. To go back to that rom you will need to wipe everything including internal then bring rom to internal and flash. Good luck
[Moto Maxx Android Development] imcensored1:
I'm not going to step that far back.

I'm still convinced my battery is trash and most of the replacements are trash.

I've been doing some research and I found that TWRP uses significantly less CPU. I also believe TWRP doesn't use a battery monitor to shut the phone down if it sees a drop out.

As for my battery, I booted in to TWRP the other day, cleared cache, and allowed my phone to die. It took 8 hours (which included intermittent screen taps), I noticed that while constantly tapping the screen, I would lose 1-3% over a 2 minute span. Once I got to 52%, it took 5 or more minutes to drop 1% while tapping. Once I got to 2%, it took 20 minutes to drop, and finally from 1% to 0% it took 45 minutes (again while constantly tapping). Once it hit zero, it stayed running. Since I don't know how TWRP handles low battery, I didn't want to push it while on 0. I attempted to reboot back in to TWRP, and the battery monitor would not let me boot, telling me it's at 0. After 90 minutes on the Motorola Rapid Charging block, with phone powered off, the phone charged up to 48%... Then within 10 minutes, it jumped to 100%. So I know my battery is bad.

Going back to my thought about CPU usage, I used the kernal editor to set my min/max to 300 and 1500(ish) respectfully. I will see over time if I gain extra battery life before shutdown, or if I just slowed my phone down. Time will tell.
[Moto Maxx Android Development] 99913308:
Is mhl working？
[Moto Maxx Android Development] MI95SHO:
Any updates on getting Magisk support?
[Moto Maxx Android Development] fgl27:
last time I tried it causes boot fail, not up to me to fix it as is not a device issue

I tried they support on github, no one seems to care for old devices.

https://github.com/topjohnwu/Magisk/issues/2695
[Moto Maxx Android Development] MI95SHO:
Reading through that forum, have you tried the solution lightvortex proposed?
[Moto Maxx Android Development] fgl27:
if you look quark device tree you will see that is how the device work already.

So have you take a look at how quark works? before ask me that?
[Moto Maxx Android Development] fgl27:
Last rom was randomly freezing this seems fine, also update the custom kernel if you use it as the problem possible come from changes on the kernel.
[Moto Maxx Android Development] Clivo:
Thanks Bhb27, it's works!! ?
[Moto Maxx Android Development] vovatema:
Flashed on this firmware.

Found 2 problems:

1. Problems with Bluetooth: hands-free communication (the conversation works normally), but after the conversation, music playing via Bluetooth is intermittent( playback hangs) . It only helps to turn on / off Bluetooth a few times. But if the call went through, then playback is not possible again.

2. Navigation (TomTom, Sygic, Yandex) when used for a long time ( more than 40 minutes), they fly to the background mode (instead of navigating to the main screen) , while voice accompaniment is provided
[Moto Maxx Android Development] fgl27:
I current own zero Bluetooth devices.

Does 1. Happens on any music and phone app?

You can try different phone apps with different music player and inform the result.

2. I don't understand, maybe you don't speak English, try to describe different.

Also read post #3 of this thread explains how to retort bugs
[Moto Maxx Android Development] Marky__Mark:
I just installed this and everything seems to work except for the email app. It opens then force closes. Is this normal or a lineage os issue??
[Moto Maxx Android Development] Einsteindks:
Not saying that it's mandatory, but I believe most folks go and use their own email app instead of the stock one. That said, did you try clearing the caches while in recovery? It's possible you may have to wipe the data from the app if all else is failing.
[Moto Maxx Android Development] Marky__Mark:
Yeah I did that. Wiped all the data even though it never worked properly once. Thanks
[Moto Maxx Android Development] fgl27:
I t works but you need to manually give contact permission.

This is a bug will probably get fix on a future update... As it should have or at least request before use it.

At least here the app has no permission, so after give that you may need to give others so it work...

I only give contact permission and it stop force closing, but I didn't add a account or try to use it as a email app, I already have gmail app, and gmail app works very well not just for gmail accounts you can have others none google accounts there.
[Moto Maxx Android Development] Einsteindks:
I use MailDroid Pro. It has a settings back-up feature, among many options. Starting over with multiple emails is SO easy.
[Moto Maxx Android Development] vhayes:
anyone else get random freezes / lockups where you have to restart the phone?
[Moto Maxx Android Development] newbe1droidx:
I have not, but I installed the latest ROM, kernel and pico gapps. I had to wipe everything including internal the bring to phone from PC. Installed and bootlooped, got in twrp and wiped all again re flashed all again and it took a while to boot. While setting up it powered off. Re installed all again and been working OK since. Hope that helps
[Moto Maxx Android Development] fgl27:
That happens on latest ROM version? Or last month one?
[Moto Maxx Android Development] dady_Al:
Yes, one-two in day
[Moto Maxx Android Development] fgl27:
I revert some changes that supposed to add minor not really demanding improves, to see if random freezes stop.

If you had those try a clean install of this ROM to make sure all is OK.
[Moto Maxx Android Development] Davi_15:
Do you intend to bring other custom roms?
[Moto Maxx Android Development] fgl27:
Only android 11 next year.

I don't have time to work in more then one project. This way I can focus on improve the "quark" project itself and not waste time making ROM.

Anyone can use my work as base to start another custom ROM project, I share the process here:

https://github.com/fgl27/device_motorola_quark#how-to-build-this

For most custom ROM that are lineage base it will just work, some custom ROM need modification of this file https://github.com/fgl27/device_motorola_quark/blob/Q/lineage_quark.mk

But the change is usually very simple as change the file name from "lineage_quark" to "team_name_quark" and maybe change this lineage works here:

https://github.com/fgl27/device_motorola_quark/blob/Q/lineage_quark.mk#L14-L17

To "team_name"... where team name is the custom rom team name... Usually there is instructions on the team main repo page on what changes are needed.

If the custom ROM is not base on lineage but aosp without lineage changes that allows you to build to none aosp device that it will not work... lineage is technically aosp but they change the source to support almost all type of devices.
[Moto Maxx Android Development] fgl27:
Did the freezes stooped?
[Moto Maxx Android Development] newbe1droidx:
I never had a problem, runs smooth so far. Thx so much
[Moto Maxx Android Development] Davi_15:
Any Solution ?
[Moto Maxx Android Development] fgl27:
How do you even cause that?
[Moto Maxx Android Development] Einsteindks:
New phone. I may not know a whole lot about the technicalities behind cell phones, that looks as much a self destruct screen as any I've seen.
[Moto Maxx Android Development] Davi_15:
This happened shortly after installing the latest version of Lineage, I was using it when the screen suddenly froze and then this screen appeared. This also happened when I put a usb otg
[Moto Maxx Android Development] fgl27:
Using how? I ask you how to cause it. What exactly you did is the only way to know what is going on.... Did you update the rom clean flash... Inform it all
[Moto Maxx Android Development] Davi_15:
I did a clean install. The first time this occurred, apps were being installed through the play store, as I was installing them, I configured them, and it was at that moment that this screen first appeared. The other time, I put the usb otg, and I realized that the screen froze and then this red screen appeared
[Moto Maxx Android Development] fgl27:
Try a old version tell me with doesn't cause it.

I don't know from where that red screen comes from, when I get a freeze using USB otg the device just reboots.
[Moto Maxx Android Development] Davi_15:
Ok, i will try
[Moto Maxx Android Development] fgl27:
I also update the custom kernel, I expect no more freezes on this version, if you use the custom kernel also update it.

If freezes keep happening let me know.
[Moto Maxx Android Development] newbe1droidx:
Well no freezes, when I clean flashed I couldn't install mini gapps said error 70 not enough space. Tried pico and it worked. Thanks for all your hard work...
[Moto Maxx Android Development] Einsteindks:
Yep, had to go micro, myself. Deleting/replacing for a custom-custom ROM.
[Moto Maxx Android Development] Davi_15:
The red screen happens again
[Moto Maxx Android Development] fgl27:
The long explanation is always demanding to report a problem...

So again how?
[Moto Maxx Android Development] Davi_15:
Again, I did a clean install, with the custom kernel, the rom and the gapps. While the Playstore was installing the apps, I was configuring the system options, gestures, etc ... It was at that moment that the phone screen froze and this screen appeared
[Moto Maxx Android Development] fgl27:
With old version works for you?
[Moto Maxx Android Development] Davi_15:
In the old version the same thing happened. I noticed that this happens after the first time the system is started, after that it is "normal" and this screen does not appear anymore, at least here it did not appear anymore.

---------- Post added at 06:21 AM ---------- Previous post was at 06:17 AM ----------

In the old version, it appeared as an error on the red screen "kernel panic detected". In this new version, the error "watchdog reset detected"
[Moto Maxx Android Development] Kinzhal:
Many thanks

[MENTION=5747496]fgl27[/MENTION] Thank you so much for fixing the video recording on the native camera app! Way to go! :good::good::good:
[Moto Maxx Android Development] fgl27:
I didn't notice it stop working, when you find a problem share it on the thread.
[Moto Maxx Android Development] fgl27:
I found that the BCL hotplug option when enable was causing the random device freezes, I force disable it by default in latest version.

So don't enable this until I have manage to properly understand the conflict of the bcl hotplug with the main hotplug

Unfortunately without bcl hotplug some device will power off more then others, so only enable this if isn't causing problem for you, the problem only happen when the battery voltage is under the bcl limits
[Moto Maxx Android Development] Kinzhal:
Bug reports

Yah bro, I know we're a community and sharing is caring but I'm a casual so I have no idea on how to make a bug report. Also, I didn't want to act like this is customer service or whatever. I promise I'll try to work on my skills, though.
[Moto Maxx Android Development] fgl27:
Don't worry, how to report bug on post #3... is allow to report just what happens if need more info I will ask, also if needed I can explain how to share a log so in doubt just ask.
[Moto Maxx Android Development] Kinzhal:
Got it

Ok, next time I will ask. Cheers!
[Moto Maxx Android Development] fgl27:
On latest version I remove the bcl hotplug as it doesn't properly work with android 10 power profile and hotplug support (mpdecision + power service).

I expand the options of the automatic power save feature (see attached) to show all usable battery % options, I recommend to use that and set a higher value for those that have battery issue. When the power save start the device will disable two cores and set max freq to 1.73 GHz on my test that is a OK performance and will in most cases (if the battery is at least above 15%) prevent the device from power it self off, is a good option until you can charge it.

If any doubt or problem let me .now
[Moto Maxx Android Development] fgl27:
This version adds supports to magisk.

Because of that iSu and AdAway was removed, and SU add on doesn't have support anymore...

SU and iSu are no longer needed, so remove it.

AdAway included on the ROM was a modified version that worked with SU add on with is no longer supported so remove it.

If yo use AdAway download the release version from https://github.com/AdAway/AdAway/releases/tag/v4.3.6

Make sure to not use the latest Pre-release version as those don't work at least I can't make it work...

To make AdAway v4.3.6 to work first enable the systemless host option in magisk then reboot after enable the same but on AdAway and aplye the host files, after reboot again and ads will be blocked... on updates of the host will not be needed to reboot only on those two first steps.

Regarding magisk the latest release version will work

If yo use the custom kernel make sure to use the latest version V9.50 as if you don't the device will not boot using magisk 20400 version.

If you enable the beta or canary version don't update magisk to version 20423 as that will not work, the latest canary that works is 20422, the apk magisk manager can be updated to latest version no problem.

In doubt let me know.
[Moto Maxx Android Development] fgl27:
After I post this magisk canary update to 20424 and that works fine... So one can update to latest apk and magisk from canary channel
[Moto Maxx Android Development] imcensored1:
I updated to the latest version yesterday and removed isu and installed magisk, now my Bluetooth is acting weird. It will connect to my radio but audio (music and Google maps) is still coming out of my phone's speaker. I've restarted the phone and deleted and re-paired my phone to the radio with no luck. I'm going to try another bluetooth device later to verify whether it's the phone or my radio. Anyone else dealing with new BT issues?

Edit: the phone portion of Bluetooth is working, but it's refusing to connect the media portion.

Edit2: it's definitely the phone. I cannot stream media through any of my Bluetooth devices
[Moto Maxx Android Development] fgl27:
With magisk, device Bluetooth mac address is all zeros... You can see if you try to par a new device...

Removing magisk fixes the problem of the Mac must fixed the rest, I don't have any audio Bluetooth device to test...

I'll check if it can be fixed.
[Moto Maxx Android Development] Davi_15:
In the latest versions, I have noticed that the phone is getting very hot performing simple tasks, like listening to music via streaming, and social networks
[Moto Maxx Android Development] fgl27:
You can use the CPU info tile to check what is going on with the device...

Here is all fine, my room temp is around 18c.
[Moto Maxx Android Development] FlavioV:
Flashing BHB27 kernel over Magisk fixes Bluetooth, though you lose root in the process until you flash Magisk again.

Not the best workaround but that should do until a proper fix.
[Moto Maxx Android Development] fgl27:
There is a Magisk-uninstaller-20200323.zip check here https://github.com/topjohnwu/Magisk/releases/tag/v20.4
[Moto Maxx Android Development] FlavioV:
Yes I know. But the Magisk uninstaller wipes its data including root permissions and installed modules. Flashing the custom kernel alone disables Magisk but keeps its data intact.

You can quickly switch between root and Bluetooth media by flashing either Magisk or the custom kernel in recovery. This rom boots up in seconds (at least on my phone) so the process shouldn't take more than a minute.

There was this issue with Magisk in the past where you couldn't install or update any apps, you had to reboot with MagiskHide disabled to fix that, it's basically the same process.
[Moto Maxx Android Development] fgl27:
This version has the latest version of android and kernel, security and bug fixes.

I discovered what magisk does that breaks Bluetooth, but didn't find a solution...

I post a issue on magiks repo to see if we get some support and more info so it can be fixed see it here

https://github.com/topjohnwu/Magisk/issues/3179

Because of the issue I re-add the add on SU support it can be installed if someone wanna

download the add on SU from here

https://sourceforge.net/projects/fgl27/files/Android/Root/

and iSu from here

https://androidfilehost.com/user/?w=settings-dev-files&flid=120360

or

https://labs.xda-developers.com/store/app/com.bhb27.isu

I update the CPU info that was only a tile, to be a settings app called System info overlay, it can be acceded in Settings -> System -> System info overlay, it also has a tile with the same name.

Now is possible to not just enabled/disabled it but change color position and size using the settings... is very useful to understand what is going on with the device Battery, RAM, GPU and CPU...

The % value at the end of it line, is...

Battery percentage.

Amount of the RAM that is be used from the available RAM, that is around 2.7 GB (system reserves 10% to prevent odd OS behavior when the RAM is full)

eg. 70% here meas 70 % (1.81 GB) of the 2.7 GB of RAM is be used and 30% (0.81 GB) is free

GPU and CPU is estimated utilization and or load

On next version I'll add a Celsius to fahrenheit option for temps
[Moto Maxx Android Development] fgl27:
Magisk had a surviving scrip, for me with latest canary version of magisk and the latest version of the kernel the only way to remove magisk is using the uninstaller, as the script is working.

You can share what exactly version of kernel and magisk you had success.
[Moto Maxx Android Development] imcensored1:
I fixed it. I'm not sure how permanent this is, but I copied the file in question and pasted it in Mirror / System Root / Persist. I rebooted and now I have a BT Address.

I'm now sitting in my car and BT streaming is working.
[Moto Maxx Android Development] fgl27:
This version fix the magisk conflict that cause issue to root folders, and cause issue most noticeable to Bluetooth.
[Moto Maxx Android Development] Davi_15:
With the return of the RR team, have any chance of seeing a version of it on Android 10?
[Moto Maxx Android Development] fgl27:
No only lineage. Same reason as previously from above.

Anyone with any computer can make a ROM, if on windows is as simple as use a VM software and run linux on a VM the rest is simple as follow instructions.

O good modify lineage ROM source today is crDroid and not RR.
[Moto Maxx Android Development] Moto Maxx 2019:
Congratulations [MENTION=5747496]fgl27[/MENTION] thanks for continuing to update our device even after so many years ...

How do I get back to ROM STOCK 6.0.1? I've been using modified ROM for a few years now and would like to go back to Stock again, but I plan to go back to LineageOs again after a while
[Moto Maxx Android Development] mrkhigh:
Thanks [MENTION=5747496]fgl27[/MENTION] dug out the old turbo and within 15 minutes in running los 17. It's been a trusty old friend thanks to you.
[Moto Maxx Android Development] fgl27:
I didn't had much free time tom make this sooner, this latest version is just the latest Android 10 version plus all latest security updates.
[Moto Maxx Android Development] fgl27:
If you didn't made a backup, you need to flash the latest version of stock for yours device via bootloader

All the stock ROM that I have access here

https://androidfilehost.com/user/?w=settings-dev-files&flid=39558

You must use the mfastboot or any fastboot program in terminal to install those files or use a dedicated flash software

I prefer to do via fastboot as I explain it on bellow post, but on that thread first post there is a software that does it for you I just don't use it and can't explain how to use

https://xdaforums.com/moto-maxx/gen...maxx-droid-t3063470/post63469991#post63469991

Some ROM have more or less system.img_sparsechunk.X files so make sure to flash all base on the name of the file, after you extract the zip you will be able to see how many there is.

There is dedicated threads on xda that discuss the process

https://xdaforums.com/moto-maxx/general/quark-stock-firmware-moto-maxx-droid-t3063470
[Moto Maxx Android Development] fgl27:
This version has the latest android 10 version with latest kernel and Android improves and security fixes.
[Moto Maxx Android Development] imcensored1:
[MENTION=5747496]fgl27[/MENTION] i installed the uodate before you pulled it... Now the phone won't see my sim card. Where are the ota updates stored so I can use twrp to restore the prior version
[Moto Maxx Android Development] fgl27:
This is good enjoy it.
[Moto Maxx Android Development] fgl27:
That isn't the issue that I notice... both download links have a Old_version folder
[Moto Maxx Android Development] imcensored1:
[MENTION=5747496]fgl27[/MENTION] I found the directory in /data. I flashed back to the prior version... My sim card is working but the lock screen won't actually unlock. It just loops. I just flashed back to the pulled version. No sim card but it's moving past the lock screen. I will attempt the version you just pushed.

---------- Post added at 01:57 AM ---------- Previous post was at 01:46 AM ----------

[/COLOR [MENTION=5747496]fgl27[/MENTION] the latest version you pushed is working properly here. Thanks
[Moto Maxx Android Development] fgl27:
OK good.

What type of lock you use?

The deep sleep issue is related to CPU timers and that may cause those other issues, I'll do some test to understad all so it doesn't happens again
[Moto Maxx Android Development] imcensored1:
I use pattern swipe.
[Moto Maxx Android Development] fgl27:
I believe the issue here was the downgrade process, as an service that is used by the lock screen changed and the downgrade may have messed it up, you shouldn't downgrade/upgrade manually without wiping the system. always follow the instruction from OP to do manual installations
[Moto Maxx Android Development] ilia3367:
fgl27 You are a cool dude! I'm here again.
[Moto Maxx Android Development] Ihet:
Thank you for your work! Can l enable data encryption?
[Moto Maxx Android Development] fgl27:
Yes but backup of the Data partition via TWRP will not work.
[Moto Maxx Android Development] Ihet:
I turn on encryption but the phone just restarts. No encryption occurs.(
[Moto Maxx Android Development] fgl27:
Last time I tested worked, but was some time ago, I don't have time to test this now as I only have this phone there is a lot on my phone that I need to backup as I don't use encryption I must dp all the test then go back something I will not do for a simple test as will cost me a lot of time.

If you did used encryption before on a different OS there is a chance that it didn't fully clean the last encryption status, you can try to format the data partition then flash the rom and try again encrypt it, that will erase it all on yours device, but may solve it.

Also if you didn't resolved the issue yet, or don't wanna to erase it all, you may be able to clean install the ROM, by erase data without erasing the internal storage, and all will be fine, then try again but probably will result in the same issue if you don't fully format the data partition.

if you try any of those let me know the result.
[Moto Maxx Android Development] Ihet:
Did as you said. It works! Thank you too!)
[Moto Maxx Android Development] luiz-663:
eu preciso de uma ajuda, instalei a sua ultima versão (20201109) e, monitorando o clock do processador do meu Maxx, percebi que ele não passa de 1,7ghz, eu não faço ideia do que possa estar causando isso, a temperatura está ok, não alterei nenhuma config, deixei como vem, quando eu mudo o plano de energia de "balanceado" para "desempenho" não acontece nada e ele continua travado a 1.7ghz. Alguma ideia do que seja?