yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] rhcreed:
Definitely looking for recommendations regarding battery life, concerned that I'm not seeing the apps using it..

---------- Post added at 12:33 AM ---------- Previous post was at 12:29 AM ----------

Love the notification led, the track change with volume rocker, and gesture support!
[Moto Maxx Android Development] Septfox:
BetterBatteryStats is generally the app of choice to figure out what's wakelocking.

There are generally two major killers:

msm_hsic_host will tend to throw a ton of wakelocks if using the Marshmallow radio (Turbo/xt1254, might not affect others). Flash the Lollipop radio to see if there's an improvement.

Bluetooth wakelocks quite a bit while on and especially while connected, if you have it off but are still getting wakelocks from it, this is due to location services periodically forcing it on and poking nearby broadcasting bluetooth devices. You can disable this behavior by going to Settings>Location>Scanning (menu button in top right) and toggling it off.

If you don't care about your mail syncing as often (among other things), enabling Aggressive Doze and Doze on the Go (Greenify specifically can, but there are non-paid ways to do it) can save quite a bit of power by keeping apps - including Google housecleaning stuff - from waking the phone as often.

Finally, using Tasker/AutomateIt/etc to change governor when the screen is off to something more battery-friendly - namely Zzmoove - can save a good chunk of power, in exchange for a bit of choppiness at the lock screen.

Have you tried using iSU? It's currently working for bypassing Safetynet, provided it's set up properly.
[Moto Maxx Android Development] rhcreed:
And wtf does my phone power itself off when it gets to around %15? It powers off, not just a hard shut down..
[Moto Maxx Android Development] Septfox:
A proper Android shutdown? If so, are you positive it's still reporting 15% while it shuts down?
[Moto Maxx Android Development] rhcreed:
Yes, "shutting down" and everything... Has happened twice, both times within a few points of %15..
[Moto Maxx Android Development] Septfox:
Hmm. Generally, the only time it does this is when it suddenly thinks the battery is dry, which should report 0% in the status bar. That's been my experience anyway, though mine was happening at 8%.

Two things to try:

Make sure the BCL driver is enabled in the Kernel Adiutor, it throttles the CPU back when the battery voltage gets too low (fast enough that you shouldn't notice much performance penalty, if any at all).

As our battery ages, the CPU running at full speed can sag the voltage low enough to make the battery controller freak out (because it thinks that the battery is about to be damaged) and shut the phone off...generally this manifests itself as a sudden cutoff, though.

"Recalibrate" your battery reading. No idea if it actually has any lasting effect, yet, but it did allow me to go down to 3% before I chickened out and put it on the charger:

Edit: possibly relevant, I used a quick/"turbo" charger to get to 30%.
[Moto Maxx Android Development] rhcreed:
Found and enabled the bcl driver, thx!

I'll try a recalibrate, thx!

I'm making changes to the included kernel app, do those apply if I'm using the stock kernel (didn't flash one when I did the Rom)

---------- Post added at 02:32 AM ---------- Previous post was at 02:23 AM ----------

Are there doze settings we can modify in the settings?
[Moto Maxx Android Development] Septfox:
Any options you can change in the audiutor app should take effect. The flashable kernel includes more governors to use for the CPU and storage, overclocking, a better thermal management module, more hotplugger choices, etc. The stock kernel is fine, though, if you don't feel like really digging into things.

Messing with doze settings is traditionally done via ADB, and the only associated settings exposed to the user are whitelisting controls (so you can prevent things like Maps from being shut off when the phone goes into a deep doze).

This app sounds to do the same thing that the settings in Greenify do if you want to give it a go. 4.5/5 stars suggests it works as intended.
[Moto Maxx Android Development] rhcreed:
I'll give the app a shot, thank you!
[Moto Maxx Android Development] rhcreed:
I am seeing a lot of these, where can I find the files and instructions to flash that radio package?

I'm seeing "cell standby" as a big battery drain, are these related? If not, is there a way to reduce the impact of the cell standby?

Thanks!
[Moto Maxx Android Development] rhcreed:
Is there a way to see what it's actually doing? I'm not really seeing any difference yet..
[Moto Maxx Android Development] Septfox:
Assuming it is indeed the problem, you can try blocking the wakelock for msm_hsic_host (toggling it off) in the Kernel Adiutor, under Wake Locks. I've tried doing this before to see what happened, and it didn't seem to hamper the radio's ability to operate or anything. Alternatively you can "divide" the wakelock to limit how much it can wake the phone.

To bring it down to normal levels "naturally", you can get the TWRP package for SU4TL-49's radio and bootloader from here, and grab the clean modem status zip.

Make a TWRP backup of your Boot partition first (include the Radio partition in the backup if you're inclined), flash the SU4TL-49 package, then restore the backup of your Boot partition. That way, you only change out the radio.

Flash Clean_Modem_Status after flashing the radio, otherwise you'll probably have random GPS and signal issues (this should always be done after changing radios).

msm_hsic_host is a kernel wakelock; it stands for Mobile Station Modem High-Speed InterConnect Host, and is a wakelock held by the interface for the radio.

Doze enforces lowered activity (be it local or background data transfer) among apps, but doesn't go any "deeper" than that. If the radio interface is keeping the phone awake anyway...yea, it's not going to make a difference unfortunately.

This is all assuming that your primary problem is msm_hsic_host. If the above doesn't help, you really should get Better Battery Stats and make sure that that is what's keeping the phone up. "Cell Standby" covers several different things, this is just the most common problem child among those things.
[Moto Maxx Android Development] maxisgsm:
Sorry, wrong section
[Moto Maxx Android Development] ryadav664:
[MENTION=5747496]bhb27[/MENTION] I flashed the kernel and downloaded the kernel adiutor app and followed battery saving recommendations, still battery has'nt improved and phone gets very warm when mobile data is turned on
[Moto Maxx Android Development] fgl27:
ROM update! crDroidAndroid-7.1.2-20170724-quark-v3.6.zip​

Recommended clean install this version

Changelogs:

Device Click Here

CRDroid Android Nougat source and Quark Click Here

Download Links :

Download: ROM Click Here

Gapps:

7.1 Banks Dynamic GAPPS click here (Choose SDK25 version)

Open Gapps Click Here (Choose Platform: ARM, Android: 7.1, and a Variant

TWRP For Quark: TWRP Click Here

Instructions :

Download the latest build and GApps.

Reboot to recovery (recommended make a backup)

Coming from different ROM? Then Always wipe Data (without media aka without internal memory)

Wipe System and Cache

Flash the latest build* and GApps **

Reboot and profit!

** Gapps not demanding the ROM works perfect without it and there is ways to have play to work without gapps. In a ROM updates "dirty flash" if you have gapps always flash gapps again after the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.

Always start a post with a bug report with [MENTION=5747496]bhb27[/MENTION] and always attached a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

** If the device Random reboot all the logs are lost so just described like I ask above without logs

Bugs without logs that are not reboots and without [MENTION=5747496]bhb27[/MENTION] will not be read, there is too much posts on the thread I don't have time to read it all, you guys can post as much as you need of course as long is things related to this thread
[Moto Maxx Android Development] KARIM9377:
its happened to my ones on 25% turn it self off
[Moto Maxx Android Development] ryadav664:
[MENTION=5747496]bhb27[/MENTION] hi.. when I connect my phone to my car's stereo via Bluetooth and play song it says streaming instead of showing the name of the song it never happened in stock ROM. How to fix this issue,I am on crdroid- 20170724 v3.6
[Moto Maxx Android Development] fgl27:
I don't know, is not easy to compare this to stock as there is not Nougat stock, a lot have change on nougat, maybe the cause of this is a google security related update on how android handles this, or just a simple config that need to be changed adapted, as I don't have any Bluetooth that give me that exactly problem I particularly have no idea on how to start a fix.
[Moto Maxx Android Development] fgl27:
han't improve how?

what is so bad for you and what are all the number...

and how warm?

data logs and etc that can help me understand what you wanna to described is necessary to I fully understand your problem.

:good:
[Moto Maxx Android Development] ryadav664:
[MENTION=5747496]bhb27[/MENTION] I think this problem is not circumscribed to nougat it persists in every custom rom previously i was using moto x 2014 and previous to that moto g 1st gen i rooted them and installed various custom roms(including cyanogenmod) they to had this problem but before rooting and installing custom roms non of them showed this issue,its not a major problem for me i just asked if it can be fixed. Thanks anyways
[Moto Maxx Android Development] ryadav664:
[MENTION=5747496]bhb27[/MENTION] battery- one of the most important reason why I root and install custom ROM on my devices is enhanced battery life they provide,but in this rom I am unable to get more than three and a half hour of screen on time while I get around 5 hours of screen on time in stock mm. Battery health is good.

Temp-the idle temperature is 42 to 44 degrees which raises up to 55 degrees when I browse internet on LTE network

-while gaming(which I rarely do) it becomes uncomfortable to touch the device and the CPU throttelling makes it difficult to play games. It never got this hot

Apart from battery drain (which I think is the problem for increased temperature too) the ROM is buttery smooth everything seems to work flawlessly ,please resolve this issue as I don't want to go back to stock mm.Appreciate your help,Thanks
[Moto Maxx Android Development] fgl27:
not a specific device problem how do I fix it?

must be the aosp source that has something missing that is not simple to fix, mostly because I can't reproduce it here.

the device max temps, are 70 soc, 90 per core but the thermal driver will try keep everyone under 70, but you can spot they going over it up to 90.

I can't find a problem that causes drain, that is associated to yours use, you can't tell me that you can 100% of battery discharge get the same result on stock or on any other ROM, so the behavior and config you use is causing this.

On my use I can easily get 3 to 5h of sot whit battery over 40%, is just my use when I use the screen is for regular use not gaming or high resolution video, when the device is at sleep is at sleep I don't have app running on the background, because I don't allow or have app that do so.

log for battery and temperature will not provede what is discharging the battery, you need to use specif battery apps that can tell what is keeping the device awake and what is really discharging the battery, if afer seeing what is doing and is something that you think I can fix you share here.

there is a tool to overlay the cpu and gpu use freq and temp, you find it on crdroid extra config in setting, it can tell you some data that may help to understand what is going on, on it situation, high spikes of use and temp indicated something off, just need to associated what is a high spike, temps under 60 are not.
[Moto Maxx Android Development] aleks_tar:
I've installed the last version of this ROM (crDroidAndroid-7.1.2-20170724-quark-v3.6) on my Motorola Moto Maxx. And I notice, that there is no support for "Ok, Google". That's what I see in the Settings of Google App -> Settings -> Voice -> "Ok Google" detection (in attachment). Is there an ability to work with Google Now or Google Assistant in this ROM and how can I make it work?
[Moto Maxx Android Development] newbe1droidx:
I think you need to install larger gapps for that. I know it's not in pico that I use.
[Moto Maxx Android Development] fgl27:
ROM update! crDroidAndroid-7.1.2-20170801-quark-v3.6.zip​

Recommended clean install this version

Changelogs:

Device Click Here

CRDroid Android Nougat source and Quark Click Here

Download Links :

Download: ROM Click Here

Gapps:

7.1 Banks Dynamic GAPPS click here (Choose SDK25 version)

Open Gapps Click Here (Choose Platform: ARM, Android: 7.1, and a Variant

TWRP For Quark: TWRP Click Here

Instructions :

Download the latest build and GApps.

Reboot to recovery (recommended make a backup)

Coming from different ROM? Then Always wipe Data (without media aka without internal memory)

Wipe System and Cache

Flash the latest build* and GApps **

Reboot and profit!

** Gapps not demanding the ROM works perfect without it and there is ways to have play to work without gapps. In a ROM updates "dirty flash" if you have gapps always flash gapps again after the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.

Always start a post with a bug report with [MENTION=5747496]bhb27[/MENTION] and always attached a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

** If the device Random reboot all the logs are lost so just described like I ask above without logs

Bugs without logs that are not reboots and without [MENTION=5747496]bhb27[/MENTION] will not be read, there is too much posts on the thread I don't have time to read it all, you guys can post as much as you need of course as long is things related to this thread
[Moto Maxx Android Development] dantexperia:
I have serious battery problems!

When my device reaches 22% it turns off, it will not let me do anything. I connect it off and the battery has 16%. The duration stinks.

Please, I need to solve this problem. I have this version: crDroidAndroid-7.1.2-20170801-quark-v3.6

Thanks.
[Moto Maxx Android Development] ChazzMatt:
I only see this complaint on the Nougat custom ROMs. I'm still on RR Marshmallow (two phones) and my wife and I do not have this problem.

I'm not saying the Nougat custom ROMs are causing this, as I'm not a dev. But try installing RR 6.X for a week and see if it happens to you.
[Moto Maxx Android Development] Aptahar:
Try this old trick for Turbo:

1. Reboot to bootloader

2. Select Bootloader Logs

3. Hold power button until device reboot.
[Moto Maxx Android Development] fgl27:
maybe because there is way to few users running it... because if this is a HW problem doesn't matter the OS you are on, as is not happening to everyone is hard to point as a OS problem.
[Moto Maxx Android Development] Hlcpereira:
Maybe it's the battery in fact "saying" to change it or calibrate (I don't know if it works, but anyway...) it. Here in my XT1225 I've never had this problem in any Nougat ROM.
[Moto Maxx Android Development] fgl27:
ROM update! crDroidAndroid-7.1.2-20170808-quark-v3.6.zip​

Recommended clean install this version

Changelogs:

Device Click Here

CRDroid Android Nougat source and Quark Click Here

Download Links :

Download: ROM Click Here

Gapps:

7.1 Banks Dynamic GAPPS click here (Choose SDK25 version)

Open Gapps Click Here (Choose Platform: ARM, Android: 7.1, and a Variant

TWRP For Quark: TWRP Click Here

Instructions :

Download the latest build and GApps.

Reboot to recovery (recommended make a backup)

Coming from different ROM? Then Always wipe Data (without media aka without internal memory)

Wipe System and Cache

Flash the latest build* and GApps **

Reboot and profit!

** Gapps not demanding the ROM works perfect without it and there is ways to have play to work without gapps. In a ROM updates "dirty flash" if you have gapps always flash gapps again after the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.

Always start a post with a bug report with [MENTION=5747496]bhb27[/MENTION] and always attached a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

** If the device Random reboot all the logs are lost so just described like I ask above without logs

Bugs without logs that are not reboots and without [MENTION=5747496]bhb27[/MENTION] will not be read, there is too much posts on the thread I don't have time to read it all, you guys can post as much as you need of course as long is things related to this thread
[Moto Maxx Android Development] fgl27:
ROM update! crDroidAndroid-7.1.2-20170811-quark-v3.6.zip​

Recommended clean install this version

Changelogs:

Device Click Here

CRDroid Android Nougat source and Quark Click Here

Download Links :

Download: ROM Click Here

Gapps:

7.1 Banks Dynamic GAPPS click here (Choose SDK25 version)

Open Gapps Click Here (Choose Platform: ARM, Android: 7.1, and a Variant

TWRP For Quark: TWRP Click Here

Instructions :

Download the latest build and GApps.

Reboot to recovery (recommended make a backup)

Coming from different ROM? Then Always wipe Data (without media aka without internal memory)

Wipe System and Cache

Flash the latest build* and GApps **

Reboot and profit!

** Gapps not demanding the ROM works perfect without it and there is ways to have play to work without gapps. In a ROM updates "dirty flash" if you have gapps always flash gapps again after the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.

Always start a post with a bug report with [MENTION=5747496]bhb27[/MENTION] and always attached a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

** If the device Random reboot all the logs are lost so just described like I ask above without logs

Bugs without logs that are not reboots and without [MENTION=5747496]bhb27[/MENTION] will not be read, there is too much posts on the thread I don't have time to read it all, you guys can post as much as you need of course as long is things related to this thread
[Moto Maxx Android Development] fgl27:
In changelog and here

last V fix the below

Fix some random apps crash demanding do a wipe of Dalvik art cache and cache after flashing so this fix have full effects if problem find after do a clean install
[Moto Maxx Android Development] root.xda:
Can i flash this rom on Moto Droid Turbo without unlocking the bootloader? --> NoobQuestion :)
[Moto Maxx Android Development] NepoRood:
No
[Moto Maxx Android Development] Q9Nap:
There is a bug in this build where crDRoid Settings force closes every time I try to change tabs.

I tried on a clean install with no gapps or any other modifications.
[Moto Maxx Android Development] Anhell:
The same to me
[Moto Maxx Android Development] fgl27:
ROM update! crDroidAndroid-7.1.2-20170812-quark-v3.7.zip​

Recommended clean install this version

Changelogs:

Device Click Here

CRDroid Android Nougat source and Quark Click Here

Download Links :

Download: ROM Click Here

Gapps:

7.1 Banks Dynamic GAPPS click here (Choose SDK25 version)

Open Gapps Click Here (Choose Platform: ARM, Android: 7.1, and a Variant

TWRP For Quark: TWRP Click Here

Instructions :

Download the latest build and GApps.

Reboot to recovery (recommended make a backup)

Coming from different ROM? Then Always wipe Data (without media aka without internal memory)

Wipe System and Cache

Flash the latest build* and GApps **

Reboot and profit!

** Gapps not demanding the ROM works perfect without it and there is ways to have play to work without gapps. In a ROM updates "dirty flash" if you have gapps always flash gapps again after the ROM update

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand and can't be reproduced, I can't fix.

Always start a post with a bug report with [MENTION=5747496]bhb27[/MENTION] and always attached a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

** If the device Random reboot all the logs are lost so just described like I ask above without logs

Bugs without logs that are not reboots and without [MENTION=5747496]bhb27[/MENTION] will not be read, there is too much posts on the thread I don't have time to read it all, you guys can post as much as you need of course as long is things related to this thread
[Moto Maxx Android Development] fgl27:
Is all fixed on latest V...

@ all

let me know if any problem is found...
[Moto Maxx Android Development] RL_Wells:
I noticed issue on previous version, i haven't noticed it occurring in this version. Thanks for providing this ROM, I've been using for past month and all seems near flawless, great battery life on 1250, Verizon.
[Moto Maxx Android Development] Soul reaper:
I am facing this issue since a long time and i guess its getting out of hand now.. I have read about this here too but the discussion had no conclusion.. I tried to search about it online and found this Gservice fix thing but its just temporary.

As you can see in the ss it utilises enormous amount of battery.. The phone heats up usually. Tried turning off location and sync to no avail. Its also happens in airplane mode. Yes the phone was in airplane mode for 9 hours and it still persists. So its not radio related maybe

http://imgur.com/a/36dAv

http://imgur.com/a/rG1wt