Related
After weeks of tryna figure our my battery drain on froyo I think I pinned it down. In spare parts under battery history/ sensor usage/ android system is running on my phone 100 percent of the time.I've already wiped and that doesn't help.any help?
b33zy682 said:
After weeks of tryna figure our my battery drain on froyo I think I pinned it down. In spare parts under battery history/ sensor usage/ android system is running on my phone 100 percent of the time.I've already wiped and that doesn't help.any help?
Click to expand...
Click to collapse
Ya I have 17 hours of sensor usage in all time (I guess that's since I did a hard reset a few days ago).
Yea and the only solution I've found is factory reset but I can't find it in cm6 settings nor do I know if factory reset does anything to rooted users
Factory reset erases all user data. It's essentially wiping Data and Cache partitions.
Has anyone figured this out yet? My phone has been unplugged for 1 hour and has 24 minutes of sensor usage when I've used the phone for maximum 8 minutes.
rickytenzer said:
Has anyone figured this out yet? My phone has been unplugged for 1 hour and has 24 minutes of sensor usage when I've used the phone for maximum 8 minutes.
Click to expand...
Click to collapse
I'd have to bet it's an app doing it... You'll have to figure it out probably.
Definitely it must be some app you have installed. Try nandroid and wipe if you have root and if it solves your problem then nandroid restore back and uninstall apps one by one until you figure it out.
I recommend you to start uninstalling apps which using sensor as first.
rickytenzer said:
Ya I have 17 hours of sensor usage in all time (I guess that's since I did a hard reset a few days ago).
Click to expand...
Click to collapse
My guess would be that the sensor usage is part of the android system, therefore it uses the light sensor to read ambiant light for automatic backlighting for the phone, proximity sensor for the dialer, light sensor for the camera and orientation? sensor for the gallery perhaps???
I would guess that if you turned off the proximity sensor for the dialer, disabled automatic backlighting, etc you wouldn't see the same results. Just a guess tho.
That would be any app that uses the motion sensor. Like the new gesture search that can be triggered by flipping the phone back and forth. Or maybe a Tasker task you set up for some sort of motion gesture. Or a live wallpaper that reacts to 'gravity'.
I'd first look for any programs like those that could be running. They are misbehaving if it is constantly on, even when the screen is off. Or it could be by design 'to shake the screen on' for instance.
I have a similar sort of issue but instead of android being 100%, I have internet at 50% under battery info/sensor usage?
I charged my battery to full last night, set my alarm to wake up this morning, then put my desire into airplane mode.
I wake up this morning and my battery has gone down from full to 88%? How is this possible, and more unusual, how has the internet been the reason when I had my phone in airplane mode?
Sent from my HTC Desire using XDA App
Same problem
I have a Desire (running CM-6.0.2) and am experiencing similar problems. Mine is actually much worse than reported here; in 8 hours of over-night table sitting, my phone drained the battery from 70% down to nearly 20%!!
I am careful to check which Apps are running, and meticulously shut things down. I always have my 3G data connection turned off, WiFi off, GPS off...
The Testing > Battery History > Sensor Usage frequently seems to be showing "Android System" with times that even exceed what is recorded as "Running"!!
The battery performance isn't always terrible like this, but I've noticed when BatteryGraph shows steep decline, that the Sensor Usage is really high.
I don't know how to try to diagnose this further, but we've got to figure something out.
msc4985 said:
I have a similar sort of issue but instead of android being 100%, I have internet at 50% under battery info/sensor usage?
I charged my battery to full last night, set my alarm to wake up this morning, then put my desire into airplane mode.
I wake up this morning and my battery has gone down from full to 88%? How is this possible, and more unusual, how has the internet been the reason when I had my phone in airplane mode?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Sorry for reviving this old thread, but I have the same problem. I charged my phone two days ago, didn't use it much before the first night. The battery in the first morning was about 95%.
I then barely used the phone yesterday and just used a default browser for 10-15 minutes before going to sleep. Don't recall the exact battery percentage, but during the second night the battery had drained a lot more than during the first night.
I have disabled auto-rotation and auto-brightness, gps and network connections and the phone was locked in it's pouch.
Under battery history (sensor usage, since last unplugged) I have:
Android system: 1d 14h 56m 48s
Internet: 11h 45m 35s
I didn't use the Internet for more than 15 minutes.
What could cause so high sensor usage?
Was a fix for this ever found?
I'm experiencing the same issue where "Android System" shows the "Sensor Usage" in Spare Parts as running 100% of the time.
Looking for input on a ROM with no phone function or a way to disable the phone function(no sim) to just simply use with Garmin Mobile XT. Something that boots up extremely fast with no function except auto execute the Garmin would be ideal.
Any Ideas?
Battery Issue:
BTW: The reason for this is the phone is completely useless as a normal phone because the battery only lasts a few hours. I actually get better battery life booting android. The battery heats up the entire phone and the current draw is 400-600 idle. When charging the light never turns green for fully charged thought booting up it will say 98% before it starts plummeting. I have tried multiple batteries and multiple ROMs with the same result so I figured I would just use it as a GPS plugged into my car with the Garmin Software. If anyone has any incite on this that would be great too. Thanks
Don't think someone would cook such a rom.
But you always turn off the phone in wireless control, switch off manila (having nothing in today boot up in around 48s) and put garmin.ink to StartUp folder.
By the way i think your battery is dead, mine can standby for around 3days/around 3-4 hours of talk time for a full charge.
Hi there!
I just bought four days ago a Note 8 (my 6 month old Pixel XL simply bricked itself) and i found it a pretty nice device.
But one strange thing is happening, maybe you guys can help me pinpoint where the problem is: when I put my device inside my jacket pocket, it goes really hot and battery goes down the drain.
If I remove it from my pocket, it cools down and battery drain comes back to acceptable levels.
My initial conclusion is that something using the proximity sensor is draining the battery... any ideas?
Do you guys recommend any tools that would help detect where the problem is? I don't want to root the device.
I use kin screen to keep the screen on while I am using the phone. I thought it might be the culprit at first, but uninstalling it didn't solve the problem.
I used package disabler pro to disable some bloatware like onedrive, carrier apps and such, no success. Enabled all apps again, same problem.
Any help would be appreciated... thanks in advance!
StealthNet said:
Hi there!
I just bought four days ago a Note 8 (my 6 month old Pixel XL simply bricked itself) and i found it a pretty nice device.
But one strange thing is happening, maybe you guys can help me pinpoint where the problem is: when I put my device inside my jacket pocket, it goes really hot and battery goes down the drain.
If I remove it from my pocket, it cools down and battery drain comes back to acceptable levels.
My initial conclusion is that something using the proximity sensor is draining the battery... any ideas?
Do you guys recommend any tools that would help detect where the problem is? I don't want to root the device.
I use kin screen to keep the screen on while I am using the phone. I thought it might be the culprit at first, but uninstalling it didn't solve the problem.
I used package disabler pro to disable some bloatware like onedrive, carrier apps and such, no success. Enabled all apps again, same problem.
Any help would be appreciated... thanks in advance!
Click to expand...
Click to collapse
Not sure what could be draining your battery in your pocket but you may want to try this setting: Settings>Display>Block accidental touches (prevent the screen from detecting touch input while your phone is in a dark place such as a pocket or bag)
See if it happens when the phone is in Safe Mode (ask Bixby)
djlee0314 enabled it...
After searching on google for a while, I found some threads that relates this battery drain with camera settings related to sensors and movement...
And voi la, it seemed to work for the most part.
Removed the phone from the charger at 7am and battery was draining as supposed until 1pm when the phone started getting hot again.
Removed from my pocket because I needed it online... placed it in the pocket in the evening and... cold.
I am starting to think that I might have a faulty unit... I am trying to avoid restoring it to factory defaults... will keep monitoring.
Thanks!
StealthNet said:
djlee0314 enabled it...
After searching on google for a while, I found some threads that relates this battery drain with camera settings related to sensors and movement...
And voi la, it seemed to work for the most part.
Removed the phone from the charger at 7am and battery was draining as supposed until 1pm when the phone started getting hot again.
Removed from my pocket because I needed it online... placed it in the pocket in the evening and... cold.
I am starting to think that I might have a faulty unit... I am trying to avoid restoring it to factory defaults... will keep monitoring.
Thanks!
Click to expand...
Click to collapse
Whats did you do whit this to fix it?
Never experience this issue with my N950N. Try enabling accidental screen touches maybe that will resolve it
My phone got the update to Android 9 a little over a week ago, and since then it has been losing battery like crazy. For example, last night I left it unplugged as a test, and it lost 30-40% of battery within 6 hours (while I was sleeping). Before the update, a fully charged battery was able to last for two days, now it doesn't even manage one. The phone is often noticeably warm.
I restricted all "consuming apps" some days ago, that did not make any difference. I also tried 3rd-party apps to analyze the battery consumption, but did not find any way to figure out what consumes all the battery in the background / while the screen is off.
Using Google I found other people with the same problem, but I did not find a solution. What can I do?
I had a same kind of problem but it started a few days after a manual update flash. I had been experimenting with some root stuff (mostly magisk though so they should go away by uninstalling the modules) but could also not figure out the reason for the drain.
I also tried to reflash only system and vendor partitions, but ended with a bootloop, so I had to flash the whole firmware again. No problems after that.
I would try a factory reset if I were you.
You can also try GSam battery monitor (if you already haven't) to figure out what's happening with your phone while the screen is off and it should be sleeping.
I upgrade the XPZ yesterday to 4.41 Pie. Charge the mobile after upgrade to 100%.
The current situation looks like:
18hour active, 30 Min Display, a few calls... Whatsall, newsletter, Mail..... are running in the Background, LTE, EDGE and WiFi are always on, BT has a connection to my watch...
88% are still in the Accu. (Save mobil datatransfer is aktiv; additional the option is enabled to reduce power consumption for apps in background)
Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge.
Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.
I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.
jljtgr said:
I've been running A11 for about a week and did not encounter any issues with Battery Charge Limit. Maybe make sure that it's not battery optimized? I have it "not optimized" because I'm paranoid about it, rather than having direct problems.
Click to expand...
Click to collapse
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
This the settings you have?
Path Data: /sys/class/power_supply/charger/charge_disable
Enable Value: 0
Disabled Value: 1
hawkswind1 said:
I made sure battery charge limit wasn't optimized. You're using the same custom setting from android 10? Maybe I'll try it again
Click to expand...
Click to collapse
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1
jljtgr said:
I didn't change anything at all... and honestly with all of the other A11 problems I've been having... I didn't even think to check that it was working. It just has been. I also double-checked with AccuBattery and the history never shows above my limit.
This is my control file settings as seen on the main screen:
Code:
/sys/class/power_supply/charger/charge_disable, 0, 1
Click to expand...
Click to collapse
I think that's the custom setting probably restored from your Google backup. Same one I was using. I'm gonna try it again though, thanks
hawkswind1 said:
Anyone found a consistent way to limit battery charge % on Android 11? The custom settings I used with Battery Charge Limit app on 10 work intermittently on 11. Often times I'd wake up to 100% charge. Currently I'm using Advanced Charging Controller magisk module with it's accompanying AccA app but often AccA gets killed in the background even after not optimizing it in battery optimization. The only workaround I've found is to create a macro that opens AccA every time I plug in the charger. With that step it's consistent but I'd like to find something not so hacky.
Click to expand...
Click to collapse
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).
v12xke said:
Have you tried Accubattery? Along with charge limiting it has other useful features, including reporting battery capacity vs. new (under health).
Click to expand...
Click to collapse
Accubattery is fine and all for reporting and giving an idea of where you want to stop charging... but it has no ability to limit charging. The only thing it can do is nag you to take the phone off the charger. This thread is about root applications actually blocking the phone from charging past a certain level without making the user do anything or even notifying the user about what's being done.
I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.
rcbjr2 said:
I realize this is a couple of months old. but I just got a new OnePlus 8T, now rooted, and I'm trying to use Battery Charge Limit on it. I can't quite figure out the settings to have it work consistently. Let's say the phone is already at 100% when I plug it in. Battery Charge Limit starts, but then it flip-flops between Charging and Not Charging, starting and restarting. The phone woke me up last night because it was making a ding every time Battery Charge Limit flipped between charging and not charging. One would think that if the phone was at 100% Battery Charge Limit would turn off charging and let it drop down to my 85% limit and then back up to 91%, but never got above 91%. Thoughts? Thanks.
Click to expand...
Click to collapse
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.
jljtgr said:
It's possible it's not configured correctly for your phone. You can also just disable that notification channel, since mostly it's just annoying. It constantly fliping might mean that there's more than one control file for your phone type and it's using an ineffectual one that the OS is overriding immediately. For example, the default one it detects for Pixel 4's is not the one it should use.
Click to expand...
Click to collapse
Thanks for the reply. The problem is that I use the notification to trigger Tasker profiles, so I was hoping to figure out a way to get it to stop flipping back and forth while also retaining the notification. I think it's just the standard control file since it's a OnePlus phone, but I'm not sure I can figure out otherwise. When I first start using BCL, I found the control file and was able to manipulate it with a SQL editor and Shell commands in Tasker, but I haven't poked around the OnePlus 8T that much yet.
Just as a PSA, I think Adaptive Charging from the January update can conflict with this. On days where I set a morning alarm, I found that my battery was more full than it should be. I suspect that Adaptive Charging does something that Battery Charge Limit cannot block. I won't know for a few days if turning this off in settings fixes things 100% or the January update just really screws with this.
Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com
Well, as a root method it does seem to work. Depending on your taste, it might be cleaner than an app toggling a different variable. Of course you need an app to set the file back to 100 when you want it. Some Tasker widgets work for my purposes... could probably make it a QuickSettings toggle in the shade, actually.
Bottom of that thread, I was wondering specifically if there might be way to force an unrooted device to think it met one of these conditions, so it only charges to 80%.
Specific post link:
Battery Charge Limit settings for pixel 3
Hi all, I like the app, Battery Charge Limit (root required), but was wondering how to set the control file. I works fine with Xperia (with/without Lineage), but doesn't work with Pixel 3 stock firmware (Android 10). And finally found how to...
forum.xda-developers.com
i.e.
... your phone automatically limits charging to about 80% under certain conditions:
Continuous charging under high battery drain conditions, like game play.
Continuous charging for four days or more.
I've done very little research on this, but I expect the ways to fool the phone into thinking those things are happening is even more complicated than using that root file control. Meaning also requiring root but manipulating other control files.
I suppose you could have a case and a ribbon USBC connector that fools the charging logic into thinking it is constantly connected to a hardware charger even though it's still at a net negative power. After 4 days of having the case on, it might work. I don't know why anyone would have already built something like that, however.
I would root my phone but, as my daily driver, I need things like banking apps to work. They (at least some) detect rooted phones and refuse to load as a security measure (which is probably a good thing) :-(
Banking apps are usually just a frontend to their website used API. They have no problem with you using a browser on a rooted phone or Linux PC, etc. Any app that stores sensitive data on your phone and relies 100% on the filesystem being locked down was created wrong and lazily. The only thing about banking apps that might be legitimate is when things like unique CC info is stored for NFC and using a TPM can't be assured. Most banking apps, however, do not store anything sensitive on your phone aside from a login token which all websites also do. (it's called a cookie)
My personal preference is that no app is better for me than being able to root my phone. I don't play mobile games that want to keep you from cheating and I don't even care about Google Pay, which I'm not sure has legitimate need to block root either... they just do it to keep banks happy, which as I suggested, I think they're full of BS.
The only thing more BS than this no-root nonsense from app companies is when carriers do it by locking bootloaders. I try to re-use my phones for as long as possible and without the ability to limit battery charge, the batteries swell and die quickly, every time. It's good news that Google added code where phones plugged in constantly will limit charge automatically... but I doubt there is a way to trick it from the outside. (without root)
Hmmm. Maybe lazy programming, but I'm not ready to change my Bank so I can root my phone
Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.
jljtgr said:
Back to the topic... I don't think I'm ready to trust the /sys/devices/platform/soc/soc:google,charger/charge_stop_level method. Several times I found my phone at low battery and not pulling any current from the USB port, but not losing charge either. It had put itself into a stalemate where it was stuck below 10% for hours. Resetting the value from 60 to 100 allowed charging again. The battery charge limit app never really caused this. So I guess I'm going back to the full app method.
Click to expand...
Click to collapse
I would like to definitely solve this problem I have been struggling with for years. What did you do, can you please help me? It seems extremely similar to what you wrote here.
I have been using battery charge limit on my Xiaomi Mi Mix (1st model) since android 7.1 (lineageos) (and I might have messed with a couple files, not sure, can't remember). When updating to android 9 (lineageos) couple years ago I started having the problem you described. Also I notice sometimes I plug the phone at safe levels such as 35% or 60% and it doesn't charge same thing. Also it only charges with certain chargers and not others.
Earlier today it was 11% battery, could not boot android, didn't charge. I got the idea for the first time to try booting in TWRP (on+volume up buttons) and it immediately started charging at full speed. So there's obviously nothing wrong in the hardware, it's software or just config.
I would like to definitely solve this problem, but I don't understand exactly what you did on your side to fix it. Please reply or message me if you have any suggestion Thank you!