yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] Competentpsycho:
Depends on your settings. You can overclock for performance and it will be worse. Alternatively you can undervolt or change CPU governor settings for battery savings.

Anecdotally, the default settings on BHB kernel seemed to be decently better than stock, but I don't run the default settings typically so mine is likely not a good representation of what you should expect since I don't have a lot of experience on those settings.

Test out different governors and see what works for you. If you look through this thread there are posts from others with some settings that got them pretty good battery life. With the replacement battery and my current settings (which I based on one of those posts), I have had days where I get 6-7 hrs screen on time. 5 is fairly easy to achieve for me now and still not have to charge all day. Before replacing the battery it was nowhere near that good - maybe 5 hrs screen on on a good day with low brightness and would have to charge before day was up, and typically could barely break 4 hrs screen on time. That is with the same settings, only difference was the new battery.
[Moto Maxx Android Development] monza1412:
Thanks!, believe me that I use almost stockish google apps also no gaming, so I don't know what to blame here, no xposed (in 6.0.1), or hacks of any kind whatsoever.

If you think of anything I could possibly try in order to do some further testing or gather some log info send me a pm.
[Moto Maxx Android Development] fgl27:
on those random situation is odd, and update the other post to included that if you find a one version of the kernel that is stable for you helps...

And the list of rooted app and .zip you flash can also help...
[Moto Maxx Android Development] monza1412:
These are my rooted apps:

AdAway

BetterBatteryStats

BHB27Kernel Auditor

Link2SD

SD Maid

MiExplorer

My problems started with the 202 family, back in marshmallow; as I posted here: https://xdaforums.com/showpost.php?p=69338144&postcount=1223

Somehow, the random reboot problem continued with later kernel versions. As it's very difficult for me to identify the cause and give an accurate description I didn't complain about it.

Reading the kernel changelog: https://github.com/bhb27/BHB27Kernel/wiki/Changelog-M

I tend to believe that could be some of the changes made in that version that still remains in these later V kernel versions that causes my particular phone to freeze and reboot at some point of the day :(

I can't tell if the cause of these reboots was always the same or not.

The thing is that with the cm kernel (also yours) I didn't encounter any problems, even undervolting it and with the same installed apps. So I think that it has to be something that is not present in the stock CM kernel and its enabled by default in the V45.

That's why I'm disabling one by one the added options in the v45 in order to have some idea of what is causing it, as I strongly prefer your more complete kernel version.

I did not understand you, you mean you're running like this?

These are my current settings
[Moto Maxx Android Development] fgl27:
like I write before cm-sotck kernel and my kernel over 3000 changes can't compare... have no idea what is the cause of yours base on that...

I no longer support version 202 or older or any thing on this changelog https://github.com/bhb27/BHB27Kernel/wiki/Changelog-M those are different kernel with similarities but is all different.

I only support this...

https://github.com/bhb27/BHB27Kernel/wiki/Changelog-M-and-N

if you find a version on that list that is OK let me know...

....

my crc and fsync is just like that in yours pic... always off for years.

way you need this app?

Link2SD

you don't need to move anything to fake sdcard it is fake it is inside data, you will not gain space or anything how knows if that can cause the problems you have

don't use this app for testing purpose

BetterBatteryStats

what this app do for you?

SD Maid

MiExplorer

you don't flash any .zip?
[Moto Maxx Android Development] monza1412:
All those apps are prescindible for me, to be realistic the only ones that are indispensable are AdAway and your kernel auditor version in order to tweak the kernel settings. All others can be uninstalled.

I use SDMaid like a registry cleaner, Miexplorer as a rootexplorer, Link2SD in order to uninstall some system apps that come with Los or the verizon 6.0.1 (can be done with SDMaid or manually with Miexplorer).

I don't flash any zip, any mod or any hack other than Rom and opengapps stock package in LOS 14.1, or ROM and SuperSu 2.62 beta in the verizon stock 6.0.1.

I will try a couple of days with CRC and FSYNC disabled (same as yours) in order to see if somehow are involved in this reboot thing. Will keep you posted :good:
[Moto Maxx Android Development] FlavioV:
Switch to the Aroma gapps and install only the apps you're actually gonna use. The graphical installer also lets you uninstall some stock LOS/AOSP apps if needed. It should eliminate the need of Link2SD, at least for LOS.
[Moto Maxx Android Development] Raistlen0:
bhb are you able to put you "kernel auditor" app on the google play store and that way we can get auto updates for it as you post them?
[Moto Maxx Android Development] fgl27:
you remove this from the quoted post

[IMG="XDA Labs"]https://img.xda-cdn.com/oshFRo1rSEHTP5__wCXMO3e3u-I=/http%3A%2F%2Fimgs.xda-labs.com%2F0621sigs%2Flarge%2Fcontributor.png[/IMG]

I prefer some projects be xda only, use xda labs for updates that is way that picture/link is there...
[Moto Maxx Android Development] monza1412:
Grrr after 2 days the phone reboot again :(. So I guess we can discard fsync and CRC of the equation.

Going to test some other changes.
[Moto Maxx Android Development] fgl27:
If the device takes two days to a random reboot to happens how can you tell is not somethings else and not the kernel?

battery, yours changes anything else related that can happens...
[Moto Maxx Android Development] monza1412:
I don't know man, It piss me off not to identify the reason, after 2 days I was pretty sure that with those options disabled the issue was solved.

I believe its not an app, because I don't have this problem with the stock CM/LOS kernel.

Will try to get a logcat in the next reboot as Competentpsycho suggested in his latest post.
[Moto Maxx Android Development] mubaidr:
Can you try down-clocking device or upvolting it a bit (~10-15mv) and see if it behaves correctly?
[Moto Maxx Android Development] monza1412:
Can't hurt to try, but bhb said that there is no difference between the CM and the v45 kernel branch in the voltage/under voltage department, did you have a similar problem and sort it out this way?.
[Moto Maxx Android Development] mubaidr:
Can't be very sure, but reboot happened when my device was low on battery (< 50) so i thought it might be related to lower voltage issue.

Now a days i am using AOSPEx with v45 bhb27 kernel (cpu: 2764, gpu 700) and everything is smooth.
[Moto Maxx Android Development] RSDamasceno:
Could anyone share the settings for battery saving, since the one of the second post is outdated?
[Moto Maxx Android Development] fgl27:
Kernel Adiutor update

KernelAdiutor-0.9.9.4.+39.BHB27-Mod.apk​

Download Kernel auditor

Changelog

Installation

Just Install the apk on any ROM enjoy it.

If encounter any problem:

Clear data of yours BHB27 Kernel Adiutor app + deleted the KernelAdiutor and KA_profiles folder from internal memory (if not possible by the android file manager use TWRP one), reboot to recovery and clean/wipe Dalvik and cache before reporting things.

You can make a copy of profiles.json file inside KA_profiles folder (in case you save a profile), after the reboot place it back on the folder then apply the setting on the app, if encounter problem after the apply the profile is the problem deleted it and redo the cleaning and don't use it again...

This helps when the apps functions are odd, misbehaving and or slow to load/display.

Sharing profiles

The only thing need to share a profile is the file profile.json in side KA_profiles folder, it can be just simple copy and past to another devices, the file is very small and easy to share.

Use my version of Kernel Adiutor to better support this Kernel. :good:

[IMG="XDA Labs"]https://img.xda-cdn.com/oshFRo1rSEHTP5__wCXMO3e3u-I=/http%3A%2F%2Fimgs.xda-labs.com%2F0621sigs%2Flarge%2Fcontributor.png[/IMG]
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V46​

Nougat and Marshmallow, Custom and Stock ROM.

Download BHB27-Kernel Click here

Changelog Click here

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+39 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

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 post a bug with [MENTION=5747496]bhb27[/MENTION] and 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
[Moto Maxx Android Development] fgl27:
For anyone having problems with tethering...
[Moto Maxx Android Development] Septfox:
Haven't tried the tethering fix, but I guess it's possible that the changes might fix the problem I'm having.

Getting some reboots during screen-off in kernel v46. It looks like last_kmsg is no longer a thing, but I did find the attached ramoops files in /sys/fs/pstore/, taken after the last two reboots...don't know how useful they'll be.

On a possibly related note, trying to use the wlan wakelock block seems to cause even more frequent reboots, however, I've had it turned back off for the last day and it's still happening.
[Moto Maxx Android Development] fgl27:
the stock position for wake lock featuring is on, you seems to have a wake lock related problem I have them all disable for days no problem, without others logs I don't know what is your rom config you change etc, I don't know the relation of the problem just reading this, I need more info...

is the dmesg-ramoops log, also in /sys/fs/pstore/? It doesn't exist here but I did not get random reboot for a wile...

last_ksmg in proc/ doesn't appears on quark I never try to find were it was disable or never created... probably that pstore replace it all..
[Moto Maxx Android Development] Septfox:
Sorry, that's what I meant, by "off" I meant I stopped blocking the wakelock. None are currently disabled/all on.

And that's what I was afraid of. Unfortunately the only way I can think of to grab a log of the issue is to keep an adb shell open, which would prevent the device from sleeping, which would prevent the problem from occurring...

I'm wiping /system and reflashing everything...I flashed v46 over v45, maybe something broke along the way.

I think it's only created on a kernel panic. This page told me where to find it.

I have three files here:

annotate-ramoops (1kb in size, I didn't bother including it)

console-ramoops-0

dmesg-ramoops-0

I haven't thought about in a while, but think I remember [MENTION=3457922]stargo[/MENTION] telling us that last_kmsg is deprecated after KitKat.
[Moto Maxx Android Development] monza1412:
Could you detail more how the reboot is happening? It's only happening while your screen is off? did you have any while you were using the phone? heavy loads? random? also, what rom are you currently using? any other changes to the kernel settings? undervolt?

Please give some more detailed info as I'm facing this reboot problem for a while now, maybe between your logs and mine can help bhb to solve this issue. :good:
[Moto Maxx Android Development] Septfox:
I think it's only happening when the phone is going into deep sleep, e.g. when suspending all the CPU cores.

The only time I've had issues with reboots while awake (that I know I didn't cause while derping around; I've had Gapps kill the phone a couple times while I was needlessly messing with services for example) are after I flashed 7.1 for the first time, at which time it crashed out and rebooted twice during the post-boot frenzy before stabilizing. I kind of expected it to, though, fresh flashes are the worst :<

No/minimal load, I have Greenify auto-hibernate specific apps that like to sit and keep things awake.

Again, going into deep sleep. It might even be when Aggressive Doze is kicking in, but since that only suppresses app activity and uses the inbuilt Doze functionality, I doubt it's to blame.

RR 7.1.x, whatever's newest.

I had Fsync and Software CRC turned off, but turned them back on when the crashes continued, to be safe. I usually have State Notifier turned off, turned it on for a bit, and back off when the crashes persisted. Hmm...I'm actually not sure which things are specific to the kernel, aside from the governors, hotpluggers and Intellithermal. Currently using conservative(screen on)/zzmoove(screen off), Bricked Hotplug and Intellithermal for those, respectively.

I am undervolting by...gosh, I think it's 40mv at the moment, did it one day and never thought to undo it. But it's been perfectly stable for weeks prior to flashing the new kernel, so I don't think that's it. I'll disable that next if problems continue.

---

[MENTION=5747496]bhb27[/MENTION], while I was reflashing, I also placed the modified wifi configuration...it appears to work fine, I was able to connect and pull data through the hotspot. Nice work :good:
[Moto Maxx Android Development] monza1412:
I believe my problem its slightly different but has the same outcome, a hard reboot. You should try the kernel with the default config and see what happens.
[Moto Maxx Android Development] fgl27:
I don't think the problem is in the kernel, is probably doze not alloying it to sync properly as is all disable or force sleep, that wlan is always display on whenever warning happens the problem is not it.

I will make a update, flash new kernel and app and let me know if the problem persist, use the app to generate a log as I add the pstore logs to the list..
[Moto Maxx Android Development] fgl27:
Kernel Adiutor update

KernelAdiutor-0.9.9.4.+40.BHB27-Mod.apk​

Download Kernel auditor

Changelog

Installation

Just Install the apk on any ROM enjoy it.

If encounter any problem:

Clear data of yours BHB27 Kernel Adiutor app + deleted the KernelAdiutor and KA_profiles folder from internal memory (if not possible by the android file manager use TWRP one), reboot to recovery and clean/wipe Dalvik and cache before reporting things.

You can make a copy of profiles.json file inside KA_profiles folder (in case you save a profile), after the reboot place it back on the folder then apply the setting on the app, if encounter problem after the apply the profile is the problem deleted it and redo the cleaning and don't use it again...

This helps when the apps functions are odd, misbehaving and or slow to load/display.

Sharing profiles

The only thing need to share a profile is the file profile.json in side KA_profiles folder, it can be just simple copy and past to another devices, the file is very small and easy to share.

Use my version of Kernel Adiutor to better support this Kernel. :good:

[IMG="XDA Labs"]https://img.xda-cdn.com/oshFRo1rSEHTP5__wCXMO3e3u-I=/http%3A%2F%2Fimgs.xda-labs.com%2F0621sigs%2Flarge%2Fcontributor.png[/IMG]
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V47​

Nougat and Marshmallow, Custom and Stock ROM.

Download BHB27-Kernel Click here

Changelog Click here

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+40 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

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 post a bug with [MENTION=5747496]bhb27[/MENTION] and 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
[Moto Maxx Android Development] Septfox:
It was fine all night after clearing and reflashing, then rebooted this afternoon. Flashed v47, rebooted again about 15 minutes ago. Logs attached.
[Moto Maxx Android Development] mubaidr:
Can you try using pico gapps and see if it works fine? I have had issues with nano gapps too but pico gapps works good.
[Moto Maxx Android Development] Septfox:
I tried using the Aroma installer to just install the core stuff and a couple things that are hard to get ahold of (Connectivity Services for example), made no difference. I don't think it's a gapps problem.

I don't think it's strictly a kernel issue at this point, at least not in my case. It happened just a bit ago using the v45 kernel and a fresh install of the 4/12 RR build, the former of which had been fine since...well, since it came out.

Gonna try a few things to narrow down whether it's me doing something wrong or the actual software at fault.
[Moto Maxx Android Development] fgl27:
Do you run yours device whit that temp config for how long?

echo 86 > /sys/module/msm_thermal/parameters/core_limit_temp_degC
echo 83 > /sys/module/msm_thermal/parameters/limit_temp_degC

max is max for a reason, you have fried your cpu whit those values, they are too high, and can make the cpu weak.

I don't understand those logs because they are uncommon and are not happening to any one else and it may be a hardware related problem...

but it may be a simple battery problem it gets old and get weak, you can try to reset the kernel a stock config and redo your config but don't change thermal options, bcl, voltage, don't undervoltage, and use a hotplug that can disable cores and disable two cores, use max cpu freq [MENTION=252019]2000[/MENTION] gpu [MENTION=1989751]400[/MENTION], yes you will get a very low performance, but you will be able to see the effect, then enable more cores and try a higher freq little by little to see what make it crash...

I fully don't know the problem, but you have multiple hardware problems, they get increased with a mod kernel because you made too many changes related to the hardware problems...
[Moto Maxx Android Development] Septfox:
More than two months now.

Shortly after you posted, I restored my backup that was running the RR 3/16 and kernel v45, and have had no panics while sleeping since then. I'm going to wait a couple more days to make sure, then I'll try updating ROM and kernels one after each other, with test periods between, to see what's breaking my phone.

Granted. I'm not wholly convinced it's hardware though, I think I've probably changed a setting somewhere that disagrees with the newer kernels. I'm not sure what I could have done that would survive a clean flash...and I've changed very few things outside of Kernel Adiutor.

I tried running a stock configuration before giving up and restoring the backup, with no apparent improvement.

I did do some testing and find that the random cut-offs that some people have been complaining about are, indeed, due to the battery (or the inability for the battery controller to cope with power demands using an aging battery).

Compiling themes in Substratum places an extreme, reproducible load on the CPU. With my battery charge under 80% and CPU speed set to whatever the default is, I can reliably cause a power cut-off by building DNA Dark for my 170 or so apps.

The problem worsens as the available charge drops, I could get to around 55%-60% with my preferred 2.57ghz, each maximum frequency step under that is good for 10% or so less battery.

The other users having issues are probably triggering them with momentary CPU-saturating loads. I think the aggressive stock thermal throttle and forced frequency dropping as the battery gets lower, are why the shut-offs are practically unheard-of in the stock ROMs. That Motorola probably didn't build the phone to be used this long, doesn't help. Hooray for the upgrade-and-throw-away society...

I'll repost the above with some additions in the RR thread, so people quit specifically blaming RR for their device shutting off.
[Moto Maxx Android Development] mubaidr:
Is this possible that this issue is related to this? I know devices are very different but could this be issue with the Android 7+ https://www.extremetech.com/mobile/241772-google-nexus-pixel-devices-shutting-battery-drained

BTW above mentioned issue is semi-fixed in 7.1.2
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V48​

For Nougat and Marshmallow, Custom and Stock ROM.

Download BHB27-Kernel Click here

Changelog Click here

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+40 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

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 post a bug with [MENTION=5747496]bhb27[/MENTION] and 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
[Moto Maxx Android Development] zys52712:
When I have this kernel installed Geekbench 4 always crashes before the benchmark finishes.
[Moto Maxx Android Development] ChazzMatt:
The Quark Nougat ROMs are now on 7.1.2 and have been for like two weeks.

Do a seach for "7.1.2" on this page:

https://github.com/bhb27/scripts/blob/master/etc/changelogs/Changelog_RR_N.md

That's [MENTION=5747496]bhb27[/MENTION]'s ROMs and I know the unofficial LOS also was on 7.1.2 as well as AOKP. Can't speak for the Dev Marsh ROMs.
[Moto Maxx Android Development] mubaidr:
Did i say that Roms are not updated to "7.1.2"? I give a hint again what i want to mention: "BTW above mentioned issue is semi-fixed in 7.1.2".

I am just giving my opinion on the possibility of origin of bug affecting some users. Just don't get upset.
[Moto Maxx Android Development] ChazzMatt:
[MENTION=5747496]bhb27[/MENTION] said before with 7.1.1 in his expert opinion the battery issue was not related to Android version and that going to 7.1.2 would NOT fix the issue.

But people keep talking about this magical 7.1.2. ;) So just pointing out it's been here for two weeks now if you were waiting for it.

This is actually some good info here:

My phone and my wife's phone is still on Marshmallow RR with CM Themes, so not using Substratrum on Nougat.
[Moto Maxx Android Development] Raistlen0:
This is when I notice mine doing it too. Mine has done this for about the last three builds and I assumed it was just a bad install of DNA Dark.

Well last night I did a clean wipe of everything and installed latest ROM and Latest Kernel. About a quarter of the way through every build of DNA Dark, phone just would die and I would have to turn it back on. It was around 54% charge while doing this. I thought it may be option related in DNA Dark so I wouldn't change every option for DNA Dark, but the phone would still die during themeing.

Anyway I remembered this above post and this time plugged my phone into the the Turbo charger and ran Substratum. Once I did this it applied everything with no problems of shutting off. So obviously it appears to shutdown the phone under a heavy power draw.

On the other hand I have no idea what tweaks should be made to the kernel so this does not happen. Not a big deal because I can just remember to plug it in if I want to do theme adjustments. Oh and I have not made any changes to the kernel. I have bhb's kernel installed and obviously the kernel auditor is in the ROM, but I have everything at his default settings.

It's not just this version of ROM. Its done this to me basically since the first version that had Substratum support in it.

Edit------------------------------------------------------

Sorry forgot to mention this is ROM RR 7.X. I forgot I was not in that thread.