Database Users

(Q) Screen using way to much battery

Recently on every build i use the display is taking up about 80% of the overall battery use i use it moderately but it only lasts about 8-9 hours. I looked on my battery usage and over the 9 hours my screen had been on bout about 50 minutes but had used 80% I have it on lowest brightness and have set it to turn off after 15 secs. Anybody else having this issue or know of a way around this. Also use setcpu with screen off settings and current widget is showing around 3-6mah when in standby.

Nobody else experiancing this?

I've had this issue in the past. Check this thread out, its a POSSIBLE reason why the screen is draining the battery. Basically the proximity sensor keeps running constantly when it should only activate during phone calls. In winmo the proximity sensor behaves correctly and turns off once you've hanged up. I'm hoping devs notice this and can hopefully find a fix for it
http://forum.xda-developers.com/showthread.php?t=870149
P.S. try installing system panel lite, just in case a rogue app is draining cpu constantly in the background even when your screen is off

Hmm no I'm pretty sure it's got nothing to do with the proximity sensor, this is a way more serious battery drain.
I suggest trying another build, maybe you're using an outdated one? If not, try reformatting your SD card (full format, not the quick one), changing radio and changing WinMo. You don't have to do them all at once, it may very well work after just one or a couple of these steps.

StephanV said:
Hmm no I'm pretty sure it's got nothing to do with the proximity sensor, this is a way more serious battery drain.
I suggest trying another build, maybe you're using an outdated one? If not, try reformatting your SD card (full format, not the quick one), changing radio and changing WinMo. You don't have to do them all at once, it may very well work after just one or a couple of these steps.
Click to expand...
Click to collapse
Its strange as its doing it will all builds i have formatted my card several times i have tried several new builds also swapped radios, done task 29 and tried several wm roms bit confused by it as some people are saying they get a days use and i dont not even in aeroplane mode :/

Jammie_1989 said:
Its strange as its doing it will all builds i have formatted my card several times i have tried several new builds also swapped radios, done task 29 and tried several wm roms bit confused by it as some people are saying they get a days use and i dont not even in aeroplane mode :/
Click to expand...
Click to collapse
That pretty much leaves out one option: try another SD card. Not all cards are equally optimal for Android. Just borrow one from a friend, and check if it makes a difference.

Another Possible Battery Drain Solution?

We have yet another possible remedy for those of us experiencing wakelock/battery drain issues still. Read about it from someone on the bugtracker.
Try leaving your GPS set to on, rather than toggling it. I switched mine on this morning (yesterday, now) and now for the first time in over a month I have now had my Evo unplugged for 13 hours and still have 31% battery remaining after moderate usage today.
It seems that CM may be managing it better or something (someone will have to look into it if this proves successful for more people)
Give it a try and post your results here!

I have never turned off my GPS once since I had the phone in like 6 months. GPS is not the issue for me.
I've always found that about 2 weeks after flashing a new ROM, I start getting wake lock issues which I can never track down. They always resolved themselves after I flash a new ROM, but reappear about 2 weeks later again.
Rinse and Repeat.

The GPS-on fix makes it look like there's an issue with the network location. This would tie in to earlier reports. In this case, it would be best to turn off "Use wireless networks" from Settings > Locations and Security until this bug is fixed.
The two most common causes mentioned so far are network location issues and SMD_RPCCALL wakelock issues.
Click to expand...
Click to collapse
Taken from bugtracker

What PRI are you guys running? This is likely unrelated, but PRI 1.90 seems to cause wake lock (100% wake) for some.
Edit: BTW, for every post I read, reverting to 1.77 PRI solves the 100% wake issue.

Not sure, haven't flashed a sense ROM in awhile... I'll try to check when I get a chance

kevinbear said:
We have yet another possible remedy for those of us experiencing wakelock/battery drain issues still. Read about it from someone on the bugtracker.
Try leaving your GPS set to on, rather than toggling it. I switched mine on this morning (yesterday, now) and now for the first time in over a month I have now had my Evo unplugged for 13 hours and still have 31% battery remaining after moderate usage today.
It seems that CM may be managing it better or something (someone will have to look into it if this proves successful for more people)
Give it a try and post your results here!
Click to expand...
Click to collapse
You do realize that this makes no sense, don't you?

Not if something keeps trying to call on the GPS when it's off causing some sort of wakelock while it loops trying to get a GPS fix. Leaving it on allows CM6 to manage it or something. But it does seem to help.

nabbed said:
You do realize that this makes no sense, don't you?
Click to expand...
Click to collapse
You know there's a well-known bug with Sense ROMs and the HTC 4G widget that forces 4g into a scan loop when you try to toggle 4G off that absolutely _kills_ the battery in a few hours...
I've not tested his suggestion, but the community has found stranger things before.
Side note: before two days ago I _never_ ran wifi on ... but also never ran into a wakelock ... I've left my wifi on just over the weekend as I was playing with something completely unrelated ... maybe with your suggestion Ill just continue to leave it up and see if i run into this wake-lock issue.

I've never turned gps off, it's been on since I got the phone this summer. I think it's funny that one of the settings we see for gps says something about "may cause excessive use of batter" or whatever and fact is - gps on 100% of the time doesn't do ANYthing until an app needs it. It's not used at all. No gps icon, no nothing.
The 4g problem is a PITA but it doesn't drain the battery within a few hours. It draws a little ut unless someone had shown me and proven it to me.....I wouldn't have known. And even now that I do know and I know to reboot my phone after I use 4g, I haven't noticed a big gain in battery life. Leaving 4g ON after you leave a 4g area or no longer need it WILL drain your battery within a few hours. fact

Crazy Battery Drain (Current Widget Log Included)

Running
[7.Sep.11][ZIP]★★★★★HyperDroid-CM7-v3.0.0[apps2sd][CyanogenMod7 LEO 2.3.5][seader_R5]
I have like maybe 2-3 apps installed
Current LOG file is included
http://www.multiupload.com/5WF2YRCW75

blank...........

what do you mean? i dont get it.

pinky1981 said:
what do you mean? i dont get it.
Click to expand...
Click to collapse
If you look in the picture...i have the current widget up and its showing like 200+ mA WHICH I've heard is too much and something is draining my battery...as i said in my 2nd post i will update this thread with my log file and see if some Dev or someone else has solutions....I'm not the only one having battery drain issues with this particular build...I've seen numerous people complaining about it in the thread.
I'm doing this to hopefully solve the problem for my self and anyone else who needs it.
When the phone is is deep sleep mode. The current is around 2-3 mA, but the second I turn on the screen and start doing things on it, the current jumps up sometimes to 800mA...that is not gooood. I've gotten so far 2 days on the battery so far but I haven't been using the phone as much, just letting it sleep...

bump..cause i uploaded vital info

Nexus 10 turning off in sleep mode

Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.

nando_pt said:
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
Click to expand...
Click to collapse
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.

bigmatty said:
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
Click to expand...
Click to collapse
Thanks for the response anyway.
Is that thread about freezing? My Nexus is not freezing.

Hello! Yes, that is one of the threads Im talking about. I found it to hard to find people who posted with as good of detail as you did, so I had to "latch on" to the biggest group that was vocal about their problems. But mine manifests itsself almost always as sleep of death, and NOT reboot - just like yours. Here are some links:
Google: https://groups.google.com/a/googleproductforums.com/d/msg/mobile/-/GFnACv1nC0MJ
On of the XDA: http://forum.xda-developers.com/showthread.php?t=1998496&page=39
As I say on the Google thread:
My thoughts on the error:
1) The most logical explanation I've heard yet is the memory leak that B has been posting about
2) I think this memory leak/problem can manifest its self as crash, reboot, or sleep of death
Right now I am trying Stock 4.2.2, rooted, using KTmanta kernal. This is the second day Im on a non-stock kernal, too early to post any useful info.
Good luck on this,
bm
---------- Post added at 02:09 PM ---------- Previous post was at 02:05 PM ----------
say, quick question since you are in same boat as me - does your device's serial # start with R32C or R32D?

My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.

nando_pt said:
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
Click to expand...
Click to collapse
I agree that the inability of this device to reliably stay powered on is a deal breaker, at least in a work scenario.
I actually bought mine "just for games", but have been really concerned about trying to resolve this issue to verify its not a hardware issue and I miss my warranty period. I cant honestly say I think its a harware issue, so I am really trying to find a ROM/Kernal/settings combo that resolves this.
I have a lot of faith in the dev community for ROMs and kernels, but I think its absolutely scandalous and horrible that I have to click past a warning that says 'may void your warranty' to install softare on my device to make it perform AS IT SHOULD HAVE direct from Google.
If not for all these issues I would have NEVER gone custom recovery, root, and new kernel. Im glad this has forced me to do so because Ive loved finally having a justification for "risking" my expensive device, but again that learning experience is NOT what Google is taking $500 payments for here https://play.google.com/store/devices/details?id=nexus_10_32gb so Google should be SHAMED!
Thanks for the info on your serial number, that actually relieves a concern of mine that somehow the 'newer' units werent having this problem. Mine's a C.
bm

just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.

jamir5 said:
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
Click to expand...
Click to collapse
I hope it stays that way for you. It will take a few more days with the device to know for sure. If the problem comes back it'd be worth noting here for troubleshooting. :good:

I called back the seller, and they will do the return. Really bad situation...

i left my n10 in my house and its idle with 41% on battery i just got home and open the device it consume only 1% without random reboots. hope itll stay this way ill root this and install crom maybe nextweek.

So - now I am 2.5 days into testing 4.2.2 OS with a different kernel. And so far, NO sleep of death! AND I've been using the tablet a lot more than my "minimal use" in my other tests! This of course is the ultimate test - I'm posting/talking about it on the internet so certainly if its going to blow up in my face, now would be the time. But as of right now - it looks like the alternate kernal is better for my device than Google's...
I am using the KTmanta kernel.

It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.

neatchee said:
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
Click to expand...
Click to collapse
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/clock settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Oh, and the LED flashing does not mean the unit is actually on, you can test that by plugging in a charger before attempting a long (power on) press = if you get instant battery charge indicator your unit was actually off.

bigmatty said:
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/click settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Click to expand...
Click to collapse
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\

neatchee said:
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
Click to expand...
Click to collapse
After my two months of trouble shooting I feel strongly that there are two main issues: memory leak and "something to do with power". Likely a software/driver/OS problem on the memory leak like the majority says. BUT - not everyone has the power problems. I think the power problems are hardware related.
Only a couple other users have talked about experiencing the power problems...
If I was going to place a bet, I'd say based on your description of symptoms you too have the power problem. Ask the others in threads you are following if they have the LED thing, I'm guessing they don't.
Rxnelson on these forms does. He's seen it on two physical units. For me, it didn't appear on my second physical unit.
Good luck!!

"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.

Also please note the tip I shared about diagnosing if it's off or on via the charger I posted above, handy trick another user taught me.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
neatchee said:
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Click to expand...
Click to collapse
Not quite what it seems. If the unit was on, plugging in the charger would not instantly,w/out delay, display the powered off charging indicator.

Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that

neatchee said:
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
Click to expand...
Click to collapse
Yes dude, I understand. Just test what I am saying. When I saw my white gmail led flash, but then couldn't turn on I thought the exact same thing you typed. Then while discussing w/power users someone told me to try that. Next time it happened I tried it, was SHOCKED to see what happened, knew I had a problem (that was not just shell reboot.)

My tablet just started doing this as well. It's never done it before, it started about a week ago. What could be causing this? I just factory reset to see if it'll fix the problem. I'll report back in a few days to see if this fixes the issue.
Sent from my Nexus 10 using xda app-developers app

BUGS & BATTERY USAGE on JULY official rom

hi MI A1 owners.
for those brave enough to use the latest vanilla, official OTA rom, what change did you notice?
does the battery still suffer huge drain that appeared in 2018 roms?
it's a big "NOPE" for me to update, i'm still on official DEC rom because of this drain issue.

Battery life is good on 8.1 no issue for me getting 5-6 hours SOT on gaming.

Never had battery drain problems. Only "issue" is notification led not blinking.

Just noticed that led light is no longer blinking when notifications arrive. Light stays on only when screen is off. Also Bluetooth is constantly disconnecting.

Ambient display isn't working for me.
Led notifier is also not blinking anymore!

Led not blinking, proximity sensor doesn't work properly all the time, some scrolling lag. That's what I've got so far

dudes thanks for your answers.
i'm just more convinced to not doing the update.
maybe the drain i had was magisk-related. (?)

Nothing for me, even got ten hours of screen after some cycles. Led doesn't bother me and it's the only thing i noticed.

Yes, the LED is always on, which is annoying, but the bigger issue is there is no change in the battery drain. I charged to 100%, set the phone down and did not move it or use it overnight. 8 hours later almost 14% of battery was drained. I have tried everything I can think of to try, including turning off high accuracy location, not allowing any location things like safe area, etc. and still I get this drain even when the phone is not in use. Android kernel and system consumed 85% of that usage, and System UI, Play Store and Phone Services accounted for 7%! SO basically, basic Android paired with the A1 hardware seems to be the issue and I don't know that there is any fix for that.
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!

KB_Thailand said:
8 hours later almost 14% of battery was drained.
Click to expand...
Click to collapse
Dunno what to say man. Mine is below.
2-3% at most over night.

And now it would appear that there is an issue with airplane mode.
I put the phone into Airplane mode at 2300 last night with 90% battery and did not pay attention to it. This morning I turned to phone on to find there was only 69% battery left, and WiFi was working. (see screen shot) WTF???? I have started using airplane mode to keep the battery drain to a minimum when the phone is not in use, and now it would appear that this doesn't work either.
I am REALLY getting frustrated with Android and Xiaomi as it seems that every time they do an update, something else goes bump! I have gone from totally happy with the AI when I first got it to being ready to write off Xiaomi as a company I would consider for purchase.

IjazCI said:
Is your WiFi scanning is on. ( Under location / scanning)
Play services also cause these type of sudden battery losses.
Try downloading latest play services apk from apkmirror . Latest one is
"com.google.android.gms_12.8.74_(090408-204998136)-12874034_minAPI26(arm64-v8a,armeabi-v7a)(480dpi)_apkmirror.com.apk"
Uninstall your current one. Install this .
Power off your phone for a few seconds and reboot.
Click to expand...
Click to collapse
Thanks for the thoughts, but unless I totally misunderstand what airplane mode is, WiFi should not be active when airplane mode is invoked. You can see by the screen cap that airplane mode is on AND WiFi is active. This seems to be a one off as it has not happened again for the last two days. I turn airplane mode on to stop the overnight battery drain while the phone is doing nothing. I have location set to GPS Only. IIRC play services was just updated 3 days or so ago, so it should have the latest version. I will check it and see though. Again, thanks for the thoughts.

KB_Thailand said:
At one point, I thought an upgrade to the A2 was going to be a no brainer, but with the issues with updates being broken and this battery drain issue that nobody seems to be able to pinpoint and resolve, I am thinking I may not buy ANY other Xiaomi. It may be time to try something else because the only way I can get two days of battery is to turn on airplane mode when the phone is not in use!
Click to expand...
Click to collapse
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.

ludditefornow said:
I can't logically understand why you would think it is the hardware causing the issue. If it was hardware, what you are seeing would be happening to every owner of the phone and clearly that is not happening. By saying it is the hardware when you have other software loaded is akin to saying your car's air conditioning doesn't work properly when you have all the windows wound down.
Click to expand...
Click to collapse
Actually, I think it is a combination of hardware/software, but that is just a WAG. Others have noted the exact same issue without running the same software. My bet would be on the RCS services stuff.
There is something loaded on your phone that is causing the systemUI to be working when you think nothing should be happening. The first thing I see on the screenshot on your phone is that in the top left of the screen you have two non standard icons. That tells me that you have a skin or non standard software constantly running.
Click to expand...
Click to collapse
Those icons are my Email client and GSAM Battery Monitor (presently 0.1% and 0.8%) and are the only two constantly running programs other than the stock apps and Sophos (0.3%). Neither use much battery compared to the Android stuff. Presently Kernel is 41.6%, RCS/Phone is 30.3%. SystemUI is 3.3%, Play Services is 2.0% and Phone Services is 1.8%
The way to solve any issue like this is to go back to basics. I would get the fresh rom and do a Miflash whilst keeping your data. Make sure you do a backup first.
If that does not work, back up your data and do a clean install and check the phone's battery life. Do not load any non google software / app at this stage.
Then each day add one app and test for 24 hours. You will find this issue and the offending app or apps and I would be willing to bet you a few Singhas it will be an app you downloaded not the hardware causing this.
Click to expand...
Click to collapse
Good advice. I will do this when I have a few days to play with it. In the interim, it's airplane mode every night. Thanks for the reply. If it turns out to be one of these apps, let me know where to send the Singhas.

Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.

For me, night light auto schedule not working properly.

I can't tether via wifi/bluetoth/usb
Made another post with the problem.

ludditefornow said:
Good luck with it. I hope you find the solution. It can be frustrating, but getting to the bottom of it will be worthwhile. I haven't used Sophos for a long time and even then it was for PC. I am not up with how Sophos AV is integrating into Android but that would be my first guess.
I have only had one issue with this phone after updating and it was that the OS was constantly asking for a password on unlock after using fingerprint not just on startup. A clean install solved it and I have been trouble free since with every update. With over 50 PCs in my office, I could only wish that I had so few issues with Windows updates as I do with Android.
Click to expand...
Click to collapse
Just for grins and giggles, I uninstalled my email client, GSAM, and Sophos, the only programs that run constantly other than system and Line. I then turned my phone off and back on, forced stopped Line, charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed, but still not close to what I would consider normal. When I first got the phone, it easily lasted 2-3 days between charges, with 6-7 hours SoT. Overnight would use MAYBE 2% of the battery. Now if I want it to last 2 days I need to turn on airplane mode overnight and then I can make it through a day.
So I guess the next step is to do as you recommended and load up the fresh rom when I have time to mess with it. At least I am now pretty sure that those apps aren't the culprits causing the biggest part of the battery drain. I hate to do it, but I am seriously thinking of a factory reset and seeing if that clears the issue. Would that put me back to Nougat?

IjazCI said:
I always disable carrier services apk. As rcs is not here in India.
Click to expand...
Click to collapse
How do you disable this apk? I seriously think this is the major culprit in the battery drain.

KB_Thailand said:
charged it to 100% and set it down with the screen off. It did not move of get used for 8 hours, yet it still used 12% of the battery. (see screenshots) This is better than the 20% with those apps installed,
Click to expand...
Click to collapse
So those apps were causing 40% of of the 20% of the battery drain. That is a good start. I am confident there are software issues with your phone. I see you have some GPS app on your home screen, if that was running askew, it might be constantly pinging. That is just a guess.
In things like this, work methodically through it. But of cause a hard reset would be the best way to go. I see no reason why you wouldn't stay on your current version after a hard reset.
If you want to go make to version 7 you would need to use the MiFlash program and a downloaded standard fastboot rom. You may need to do something else to the phone to go back to 7, but I would not think so.