Database Users

[Q] Huge Battery Drain

Hi,
since a week or so my u8800 suffers from a huge battery drain.
Today i just got 10hours out of it and almost did nothing. (4min. phone call/ 10messages/ max. 10min surfing)
The last 10% of battery was gone in 30 seconds.
It all started last week when my phone was on stock 2.2. Then i updated to the latest stock 2.3.5, but still the same problem.
Model number : u8800
Android version : 2.3.5
base band version : 404020
Kernel version : 2.6.35.7-perf [email protected]#1
Build number : U8800V100R001C00B528G001
I also wanted to calibrate the battery, but i can't root the phone. Tried every program out there
Anyone got the same problem or has a solution ?

Hello Kawadude,
I use superoneklick and it works fine to root the device. Hier ist the how to, what you must do before use superonklick:
- Dial * # * # 2846579 # * # *
- Go to projectmenu, background settings, log settings, log switch and set Log on
- Reboot phone
- Set USB debugging on
- Run superonklick http://depositfiles.com/files/n0dcxce3t or http://shortfuse.org/
Hope it helps

Already tried that without a result.
I also tried DooMLoRD v4, Unlock Root and One-click Root.
Since i installed the official 2.3.5 i can't root my device annymore. On stock 2.2 this wasn't a problem.

Hello, do you keep wi fi enabled at all times? i noticed my battery drains increased greatly when i leave my wifi on 24/7

No, wifi is only enabled when I'm at home.
A couple of weeks ago the battery life was just fine. (With the same usage)

Kawadude said:
No, wifi is only enabled when I'm at home.
A couple of weeks ago the battery life was just fine. (With the same usage)
Click to expand...
Click to collapse
Close any application in your pc that might try to connect with an android device (like huawei's or Asus PC Sync, etc). Those applications use the adb driver and block superoneclick. Check if windows recognize your device and install it properly. Hum... That's all I can think of... ;-)

Igory0k said:
1.Settings-> Applications -> Developer Tools-on
2.Unknown sources -> Settings-> Applications -> Unknown sources-on.
3.Fast boot -> Settings-> Applications-off
4.Dial: *#*#2846579#*#*
5. Go to projectmenu > background settings > log settings > log switch > set Log on
6.log setting-dump & log-on
7.Reboot Phone
Download B528_ROOT
8. Run B528_root.bat
9. Your phone should now be Rooted.
10. You can now go back *#*#2846579#*#* and turn logging off if you want.
Click to expand...
Click to collapse
Try this. I did hear that this last release from huawei (B528) couldn't be/was really hard to get rooted. I haven't tried this, just found it. Credit to @Igory0k.

MtG92 said:
Try this. I did hear that this last release from huawei (B528) couldn't be/was really hard to get rooted. I haven't tried this, just found it. Credit to @Igory0k.
Click to expand...
Click to collapse
Didn't work for me.
The phone rebooted and freezed at the huawei logo.
The only thing i didn't find is step 6: "6.log setting-dump & log-on"

Kawadude said:
Didn't work for me.
The phone rebooted and freezed at the huawei logo.
The only thing i didn't find is step 6: "6.log setting-dump & log-on"
Click to expand...
Click to collapse
You have to do it, rooting apps need that option
And launcher apps etc. don't install them, your battery won't drain Uninstall unnecessary apps too

Moved To Q&A​
Please post all questions in the Q&A section​

Howto: Solving notification issues. [ROOT]

After having a great deal of stress regarding the notification issues, I have come up with a solution.
Please note:
1. I have no idea why my solution works on only this one version of the firmware, but I can only reproduce it on build number NXT-AL10C00B129SP02 (The second-to-newest Chinese firmware). I cannot reproduce the solution on other versions and have not yet gotten notifications working on them, so please make sure you have the same version of everything as I do to make it go smoothly. I have only tried and failed on the latest Chinese and the latest international firmware, so perhaps an older version of that will have good results.
2. I can't guarantee this will work for everyone. Everyone has a different combination of software and settings, etc. What works for me very well may not work for you, and vice versa.
That being said, here is what I did, and how you can test and make sure it's working right for you.
Step One: Set up the OS.
Get NXT-AL10C00B129SP02 (available from the development section of this forum). You can unpack it and flash it with flashboot. The unpacking tool is as follows:
http://fs1.d-h.st/download/00173/wwfQ/HuaweiUpdateExtractor_0.9.9.3.zip
This tutorial won't cover flashboot usage. Please figure it out with google and feel free to ask if you need additional help.
You will then need to get TWRP installed. Please refer to root thread.
Getting into TWRP, please first format your /data partition, then flash the following in order. (maybe different versions will work, but these are what I used, and they worked for me, so maybe better safe than sorry.)
---
decrypt boot B129SP02.zip (can be found in this forum)
BETA-SuperSU-v2.66-2016013015024.zip
open_gapps-arm64-6.0-micro-20160108.zip
---
Then, clear cache and dalvik cache, boot the device up, and set it up.
Get into developer options and turn on ADB debugging. We will use adb to check that everything is working properly. Also, configure an email account with gmail. We'll use gmail to test as well.
Step Two: Doze Settings
Download and install Doze Settings Editor, available from the following:
http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130
Open SuperSU, then open Doze Settings Editor. SuperSU will ask for root permission, please grant it.
Go into Doze Setting Editor. To keep it easier, go to preferences and change display from milliseconds to seconds.
Set the following, from the top down.
30, 0, 0, 20.0, 0, 0, 12, 12, 2.0, 60, 600, 2.0, 3600, 300, 60, 20
(Easier way to do this is to load tuhinxp04's profile and just change idle timeout and max idle timeout to 60 sec and 600 sec respectively)
Step Three: Test
Now, we will test! Make sure you have adb on your computer, plug your phone into your computer, and run the following commands:
adb shell
dumpsys battery unplug
(turn off the screen of your phone)
dumpsys deviceidle step
(repeat this command until the state is IDLE.)
Now, check the status with this command:
dumpsys deviceidle
Things to look at from the output of this command are:
mState
mNextAlarmTime
Basically, mNextAlarmTime will count down to zero. When it reaches zero, mState will go from IDLE to IDLE_PENDING (and that's when you'll get your notifications). The settings we put in Doze Settings Editor make it so that the countdown starts at one minute, then increases twofold each time until it hits ten minutes. So the longest you'll wait to receive an email notification would be 9 min, 59 seconds.
If everything went well, the device will go from IDLE to IDLE_PENDING after the countdown. Send a test email and watch it arrive.
That's it! If this works, you'll get your notifications. You can adjust the numbers in Doze Settings Editor to match your personal preference.
Now here's the odd thing. With the latest Chinese firmware and international firmware, it does not go into IDLE_PENDING after the countdown. Instead, the countdown goes from +1sec to 0sec to -1sec and counts up, when debugging with ADB. I have no idea how to fix this, but if anyone with other firmware wants to try this solution and see what happens, hopefully we can fix notifications for all software versions. For now I'll stick with NXT-AL10C00B129SP02
UPDATE: I have somehow gotten AL10C00B129SP02 to behave the same as the newer version. I will look further into this as best I can and figure this out. So please hang on a little longer

Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!

Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I tried this on my L29 running B162. It seems to have made no difference at all. Notifications are still significantly delayed, especially for email.
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Vikram1988 said:
Is the push notification issue affecting every firmware and model or only few? I'm still deciding to buy the phone or not, so wondering.. Thanks!
Click to expand...
Click to collapse
I think this is a Huawei EMUI thing. If you look back at older phones on older versions of Android (P8, Mate 7, etc) they all had this issue (and still do). People try to blame doze, but this issue existed long before Marshmallow was around.
I have the European L29 model and I see this issue. Don't let anyone try to tell you that model doesn't suffer from it. It's real.

Guys check my post on 100% working solution for Notifications http://forum.xda-developers.com/mat...ues-huawei-t3345380/post66044102#post66044102

Enable DCI-P3 for OP3T with S6E3FA5 display panel

Update: Thanks to @MishaalRahman for the great summary article. More discussion there.
Update: Thanks to @GR0S for the app solution, available in this post
Update: Thanks to @doubleaykay for the magisk module, available in this post
I am no developer but I was researching the OP5 DCI-P3 calibration, saw that some international users were able to activate the calibration on their OP3T, and thought I would share what I have found so far. Long story short, this probably works if your device is a OP3T with the S6E3FA5 display panel, but not if your device is a OP3T with the S6E3FA3 display panel.
Note: I believe this changes the actual calibration for the "Default" selection in the display settings, but you will not see the name "Default" change to "DCI-P3"
Sources:
Credit to @rquandt on Twitter for getting the ball rolling: Tweet
Proposed command-line solution from ITHome: Link
Proposed modified apk solution from OnePlusBBS: Link
More discussion from OnePlusBBS: Link
Even longer thread (86 pages) from OnePlusBBS: Link
Even longer thread (583 pages) from OnePlusBBS: Link
This post to Weibo discusses S6E3FA5 vs S6E3FA3 compatibility: Post
Procedure:
Find out if your display panel is compatible (looking for S6E3FA5)
Install AIDA64 and check Display > "Panel ID"
(optional) I also checked to see if the profiles were available on my OP3T running Oxygen OS Open Beta 9 using a file explorer.
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 1 > sys/devices/virtual/graphics/fb0/DCI_P3
The changes will revert to previous configuration on reboot, so this must be re-applied after reboot.
To revert changes
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 0 > sys/devices/virtual/graphics/fb0/DCI_P3

I'm on VertexOS and DCI-P3 profile is not available in said location. Will flash OB9 and report back.
---------- Post added at 03:53 PM ---------- Previous post was at 03:20 PM ----------
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.

I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....

twoxa said:
I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....
Click to expand...
Click to collapse
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled. DCI-P3 is a lot more colorful, but not quite as the default calibration, which is borderline psychodelic. The selected calibration will still read "sRGB" though, as this new standard isn't officialy included in OP3T software. And yes, after a reboot, calibration will return either to standard values, or sRGB.

Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.

twoxa said:
Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.
Click to expand...
Click to collapse
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.

redsmith said:
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled.
Click to expand...
Click to collapse
Cool, sounds like it works even if you don't select "Default" before running the commands. Thanks!
redsmith said:
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.
Click to expand...
Click to collapse
twoxa said:
Phone switches back to sRGB after reboot...
Click to expand...
Click to collapse
redsmith said:
after a reboot, calibration will return either to standard values, or sRGB.
Click to expand...
Click to collapse
I'll update the instructions accordingly. Thanks!

redsmith said:
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.
Click to expand...
Click to collapse
So i think it's useless for now!
Let's hope for a magisk module,maybe...

Still trying to see if there's a way to enable a setting to allow this to work on S6E3FA3 display panels.
Found this mention of a "OPScreenColorMode.java" configuration file on the OP3T but I can't find where that would be on the device.
I decompiled the Settings.apk and couldn't find the file, but I did see a mention of that synonym (as well as OPNightMode and OPReadingMode) inside "display_settings.xml":
Code:
<PreferenceScreen android:title="@string/oneplus_night_mode_enabled_op" android:key="oneplus_night_mode" android:fragment="com.oneplus.settings.better.OPNightMode" />
<PreferenceScreen android:title="@string/oneplus_reading_mode" android:key="oneplus_reading_mode" android:fragment="com.oneplus.settings.better.OPReadingMode" />
<PreferenceScreen android:title="@string/oneplus_screen_color_mode_title" android:key="screen_color_mode" android:fragment="com.oneplus.settings.better.OPScreenColorMode" />
Not sure where to go from here, though.

soccerwuedo5 said:
Not sure where to go from here, though.
Click to expand...
Click to collapse
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.

Hi all,
I packaged this into a Magisk module for everyone to enjoy. It simply runs the provided command as part of the Magisk late_start service.
Here is a link to the GitHub repo: https://github.com/doubleaykay/DCI-P3_Enabler_OP3T. I have submitted it to the repo.
In the meantime, I have attached a zip you can install in Magisk.
I have tested it on my own device and it works perfectly!
Enjoy!
Edit: Yes, this allows it to persist through reboots!

nicesoni_ash said:
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.
Click to expand...
Click to collapse
Thanks for taking a look! It seems the guys on OnePlusBBS have overridden that removal for compatible devices to add the menu items back in on the OP3T. It's over my head but maybe someone can replicate their efforts here.

Root required
Will add srgb button tomorrow

GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
I have an A3 display and I still see a change when using DCI-P3!

vampire36 said:
I have an A3 display and I still see a change when using DCI-P3!
Click to expand...
Click to collapse
That's awesome! I tried the app and saw no change but maybe there's some other variable involved.

Magisk module isn't working for me, but the command is

Navi44 said:
Magisk module isn't working for me, but the command is
Click to expand...
Click to collapse
You could at least be more specific and include OxygenOS version and Magisk version for him/her to compare. . .

I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.

tzbigworm said:
I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.
Click to expand...
Click to collapse
That is bizzare, maybe it's an issue with Magisk v13. Could you post your Magisk log?
I am using Magisk v12, the stable release, and it works perfectly fine for me.... odd.
Could we have more people test the Magisk module to make sure it works?

GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
This works like a charm! The colours take a bit of getting used to though.

Android System - Excessive Battery consumption on MIUI 11.0.4

Hello all,
Maybe somebody can help me here.
I've recently updated my device into the MIUI 11.0.4.0 (QFJEUXM) rom . Official OTA update by Xiaomi,
I've noticed an increase in battery consumption ( mainly caused by android system app around 25%).
Somebody with similar issue ? is there a way to rollback safely into a previous version ? My previous version 11.0.3.0 was working just fine... I'm actually regretting having updated my phone.
Kudos!

Yes, many users have the same problem, including me.

Well, I feel my Mi9T has strange battery consumption through all the roms.
I'm now on custom rom with 11.0.4 vendor. Some times it uses more than 1%/h while deep dozing.
Screen on time is estimated to be around 8h, is this too short?

I'm getting sick of the android system drain. Does anyone know if xiaomi.eu rom any better? Is it worth flashing?

yellowbear4 said:
I'm getting sick of the android system drain. Does anyone know if xiaomi.eu rom any better? Is it worth flashing?
Click to expand...
Click to collapse
Yes or try this https://sourceforge.net/projects/mi...edmiK20_MIUI_20.2.27_MiRoom_10.0.zip/download

Benfatica said:
Yes or try this https://sourceforge.net/projects/mi...edmiK20_MIUI_20.2.27_MiRoom_10.0.zip/download
Click to expand...
Click to collapse
Yeah.. flashed 20.2.27 and got 2.6% drain per each hour tonight, in deep sleep... - 21% per night.
Cell standby 530 mAh.

1. Unlock Developer Mode
Settings > About phone > tap (many times) on MIUI version until you've a message "You are developers!"
2. Turn off MIUI optimization
Settings > Additional settings > Developer options > Turn on Developer options (if it's not) > scroll down to the last page and Turn off MIUI optimization
it's work for me!

nzing82 said:
1. Unlock Developer Mode
Settings > About phone > tab (many times) on MIUI version until you've a message "You are developers!"
2. Turn off MIUI optimization
Settings > Additional settings > Developer options > Turn on Developer options (if it's not) > scroll down to the last page and Turn off MIUI optimization
it's work for me!
Click to expand...
Click to collapse
Doesn't work for me have it turned off since I got the phone and the battery drain issues are only since android 10 update.

Benfatica said:
Yes or try this https://sourceforge.net/projects/mi...edmiK20_MIUI_20.2.27_MiRoom_10.0.zip/download
Click to expand...
Click to collapse
nzing82 said:
1. Unlock Developer Mode
Settings > About phone > tap (many times) on MIUI version until you've a message "You are developers!"
2. Turn off MIUI optimization
Settings > Additional settings > Developer options > Turn on Developer options (if it's not) > scroll down to the last page and Turn off MIUI optimization
it's work for me!
Click to expand...
Click to collapse
I have just checked this 3 times... I don't have this option under developer settings at all

[Guide] Fix battery life on PixelExperience 12 [UNOFFICIAL]

Code:
Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Story:
I have updated my phone (12Gb/256Gb/CN) to PixelExperience 12 [UNOFFICIAL] and faced a huge battery drain afterwards (from 100% to 40% after one night). This wasn’t useable for me as a daily driver and so I searched for a solution. I installed an App to read logs in my phone and found the following problems.
Problems discovered:
Battery drain due to Play Services trying to load an Update
Like described in this thread:
https://forum.xda-developers.com/t/...ry-drain-due-to-google-play-services.4406617/
My phone was continuously throwing errors about an update similar, to the in the thread and had a high battery consumption in idle, due to Play Services (about 25% in 24h).
Errors from the light sensor
When auto brightness adjustments were activated, my phone was continuously throwing errors like the following one:
Code:
sensors-hal handle_sns_std_sensor_event:75, wise_light: lux 36 ,period 108 ms, data c 0
Fix:
To fix the first issue, I followed the guide in the thread:
Install Magisk and root the device
Download Magisk (https://drive.google.com/file/d/1hpU74PWLJQzNoEeyn1W9IhOSgcTx0yL2/view) only for this ROM!
Boot into fastboot mode (power on while holding Volume - and the power button)
Flash magisk using the following command:
Code:
fastboot flash boot magisk_patched-24100_VLvH8.img
Disable the attempts to download the update
Download a terminal application like Termux from the Play Store
Grant the terminal application Superuser rights
Enter the command:
Code:
su
Enter the command:
Code:
pm disable com.google.android.gms/.chimera.GmsIntentOperationService
Done
To fix the second issue just disable the auto brightness option in the settings:
Code:
Settings -> Display -> auto brightness
Additionally I installed the App Naptime from the Play Store and granted it Superuser rights as well to increase battery life even more.
Conclusion:
After the described steps, my battery life is as good, as before and I can daily drive my phone again. Maybe the described fixes can help to increase battery life on your Custom ROM as well.

Thanks.

@konsensknilch - Same battery drain on Pixel 3a with June build of 12+. What app did you use to read logs in your phone?​

I used the Logcat Reader from the Google Play Store:
Logcat Reader - Apps on Google Play
View your device's logs
play.google.com

konsensknilch said:
I used the Logcat Reader from the Google Play Store:
Logcat Reader - Apps on Google Play
View your device's logs
play.google.com
Click to expand...
Click to collapse
Many thanks. Also, did you clean flash or dirty flash? And I assume you were flashing the April build?

sconebranch said:
Many thanks. Also, did you clean flash or dirty flash? And I assume you were flashing the April bui
Click to expand...
Click to collapse
You are right, I did a clean flash of the April build.

konsensknilch said:
Code:
Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Story:
I have updated my phone (12Gb/256Gb/CN) to PixelExperience 12 [UNOFFICIAL] and faced a huge battery drain afterwards (from 100% to 40% after one night). This wasn’t useable for me as a daily driver and so I searched for a solution. I installed an App to read logs in my phone and found the following problems.
Problems discovered:
Battery drain due to Play Services trying to load an Update
Like described in this thread:
https://forum.xda-developers.com/t/...ry-drain-due-to-google-play-services.4406617/
My phone was continuously throwing errors about an update similar, to the in the thread and had a high battery consumption in idle, due to Play Services (about 25% in 24h).
Errors from the light sensor
When auto brightness adjustments were activated, my phone was continuously throwing errors like the following one:
Code:
sensors-hal handle_sns_std_sensor_event:75, wise_light: lux 36 ,period 108 ms, data c 0
Fix:
To fix the first issue, I followed the guide in the thread:
Install Magisk and root the device
Download Magisk (https://drive.google.com/file/d/1hpU74PWLJQzNoEeyn1W9IhOSgcTx0yL2/view) only for this ROM!
Boot into fastboot mode (power on while holding Volume - and the power button)
Flash magisk using the following command:
Code:
fastboot flash boot magisk_patched-24100_VLvH8.img
Disable the attempts to download the update
Download a terminal application like Termux from the Play Store
Grant the terminal application Superuser rights
Enter the command:
Code:
su
Enter the command:
Code:
pm disable com.google.android.gms/.chimera.GmsIntentOperationService
Done
To fix the second issue just disable the auto brightness option in the settings:
Code:
Settings -> Display -> auto brightness
Additionally I installed the App Naptime from the Play Store and granted it Superuser rights as well to increase battery life even more.
Conclusion:
After the described steps, my battery life is as good, as before and I can daily drive my phone again. Maybe the described fixes can help to increase battery life on your Custom ROM as well.
Click to expand...
Click to collapse
WOW MAN IT WORKS!!!! Finally, i can use the latest android version experience from PE with good battery life as MIUI (maybe even better!!!). 0 percent drain in 20 minutes activity i'm so happy i wanna cry
Edit:
Unfortunately, while the service is disabled i can't make any backup to google including whatsapp. Changing the command from disable to enable doesn't work. Any idea to start the service again?

konsensknilch said:
Code:
Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Story:
I have updated my phone (12Gb/256Gb/CN) to PixelExperience 12 [UNOFFICIAL] and faced a huge battery drain afterwards (from 100% to 40% after one night). This wasn’t useable for me as a daily driver and so I searched for a solution. I installed an App to read logs in my phone and found the following problems.
Problems discovered:
Battery drain due to Play Services trying to load an Update
Like described in this thread:
https://forum.xda-developers.com/t/...ry-drain-due-to-google-play-services.4406617/
My phone was continuously throwing errors about an update similar, to the in the thread and had a high battery consumption in idle, due to Play Services (about 25% in 24h).
Errors from the light sensor
When auto brightness adjustments were activated, my phone was continuously throwing errors like the following one:
Code:
sensors-hal handle_sns_std_sensor_event:75, wise_light: lux 36 ,period 108 ms, data c 0
Fix:
To fix the first issue, I followed the guide in the thread:
Install Magisk and root the device
Download Magisk (https://drive.google.com/file/d/1hpU74PWLJQzNoEeyn1W9IhOSgcTx0yL2/view) only for this ROM!
Boot into fastboot mode (power on while holding Volume - and the power button)
Flash magisk using the following command:
Code:
fastboot flash boot magisk_patched-24100_VLvH8.img
Disable the attempts to download the update
Download a terminal application like Termux from the Play Store
Grant the terminal application Superuser rights
Enter the command:
Code:
su
Enter the command:
Code:
pm disable com.google.android.gms/.chimera.GmsIntentOperationService
Done
To fix the second issue just disable the auto brightness option in the settings:
Code:
Settings -> Display -> auto brightness
Additionally I installed the App Naptime from the Play Store and granted it Superuser rights as well to increase battery life even more.
Conclusion:
After the described steps, my battery life is as good, as before and I can daily drive my phone again. Maybe the described fixes can help to increase battery life on your Custom ROM as well.
Click to expand...
Click to collapse
Man that is just plain superduper awesome! Have been switching back to MIUI on Xiaomi which is so dumb. Wish i googled this sooner and found your fantastic explanation !!
Thanks for also explaining why it happens.
Respect bro.