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!
Related
I love the phone but battery performance is poor. I installed BBS. Enclosed a screenshot. I'm not rooted so can't look into alarm details. Makes me sad. LTE speed amazing but how can you enjoy phone if recharging once during day? Any advice greatly appreciated. I have disabled anything extraneous that I could
I'm using 2x.battery pro right now. Tried all the others too.
The same app set on my Xperia U has none of these battery issues.
Just charge in overnight, I don't see the problem in that. Then you won't have any problems.
Sent from my phone using XDA Premium
I do
I do charge every night. But most of time charging in evening as well
junkaholic said:
I do charge every night. But most of time charging in evening as well
Click to expand...
Click to collapse
charging continuously over extended periods can cause battery failure also heavy use of the phone whilst charging can damage the battery and as the T is a solid phone (cannot change battery) id recommend having it turned off whilst charging that way it will fully charge and you wont damage the battery more .... also try turning data connection 3g wifi etc etc off when your not using it as they can drain the battery a lot checking for facebook ,gmail and almost all your other apps , also listening to music and using bluetooth use more battery too
AW: [Q] Xperia T battery just not there, advice?
1. is that avast installed? Remove it. Useless anyway if you'd ever need it and only uses resources if yu dont need it.
2. battery surveillance crap? Remove it. Known to be very prone to cause wakeup.
3. Update your system, .3.195 is not the latest available.
4. About 5000 wakeups by what looks to me a failing google backup. A wakeup multiplied by 3-6 seconds on-time equals 15000-30000 seconds. Thats 5-8 hours. Thats like what the battery can give. Something is ****ed up, I suggest a fullwipe and start over from scratch.
Oh, and never mind that crap about turning all services off and totally rendering your device useless. Correctly setup the T (TL...?) lasts for a whole day with quite some abuse. And I simply dont trust the minimally booted kernel not enough to correctly regulate charging current and keep the voltages and temperatures in check. I trust the fully booted and full fledged kernel more in that regard. And turning off your device to make it use MORE battery after turning it on in the morning because it needs to go and sync all services again, check all data and find out if anything in the cloud got updated in the meantime and most importantly, needs to run the media scanner again, a very battery hungry process...? No thanks. I'll leave it on. And if that would make me feel bad, I'd use the flightmode as a maximum measure. Still better than killing the device alltogether.
Seems like to me that you might be using loads of craps that you don't need mate.
Sent from my LT30p using xda premium
Anyone using battery monitoring apps like BBS or GSam, can you share some of your stats here? I'm trying to figure out whether the seemingly massive amount of wakelocks I'm having is normal or not. The biggest problems seem to be coming from the kernel itself. BBS shows a lot of kernel wakelock time, and GSam consistently lists the kernel as the highest drain in its app sucker screen. Also, the Phone app seems to be waking the device a lot since upgrading to .5.51, which wasn't a problem on .3.374.
I've attached some screenshots that illustrate the problem. I'm already using ForceDoze and Greenify, which have been enabled via ADB, and I've restricted background activity and data for the vast majority of my apps. I'm really hoping there's something I can do about this given that it's impossible to use another kernel (LB and none available for this phone anyway). I've software repaired/clean flashed 3 times.
My battery drain is actually not bad at under 4%/hr (combined screen on/off) and about 1%/hour with the screen off overnight. Today I've logged over 4.5 hours SOT in a period of 17 hours and am sitting pretty at 36%. That's better than any phone I've ever used. But I worry that all the wakelocks are using my phone's CPU, raising its temperature, and might contribute to faster battery degradation.
Also, this is with bluetooth off and my Pebble not paired, but battery drain becomes substantially worse with that setup. My idle drain triples with my Pebble connected. I'm trying to troubleshoot one issue at a time and want to nail these wakelocks before moving onto the bluetooth issues.
If your battery stats looked like mine and especially if you figured out how to fix it, please share!
Given that Sony ended .5.51 deployment prematurely and is currently rolling out .8.49, I think you should update to .8.49 (or wait until your region gets the update if you don't have it yet) then recheck if your problem still persists.
Pouring time and resources into a version that Sony is no longer pushing isn't that great of an investment, especially since it's possible that it was fixed in .8.49.
mhaha said:
Given that Sony ended .5.51 deployment prematurely and is currently rolling out .8.49, I think you should update to .8.49 (or wait until your region gets the update if you don't have it yet) then recheck if your problem still persists.
Pouring time and resources into a version that Sony is no longer pushing isn't that great of an investment, especially since it's possible that it was fixed in .8.49.
Click to expand...
Click to collapse
Everything except the phone app using more battery was the same on .374. And I fixed that after force stopping the phone app and rebooting. I've been trying to troubleshoot this for weeks but just upgraded to .5.51 a couple of days ago. I will flash it when it comes out for Customized UK, but I don't think .5.51 is the root of the problem.
(Oh cool, Xperifirm actually shows .8.49 available for Customized UK now. Time for some flashing!)
Edit: I'm seeing the same degree of wakelocks so far on .8.49.
Update: The battery drain from "phone" is actually Android System. There's a bug in Oreo where sometimes Android System is showing as Phone/RCS in the battery stats. Doesn't explain why Android System is using so much battery though.
https://www.reddit.com/r/GooglePixel/comments/7f7jk2/pixel_2_rcs_battery_drain_is_there_any_way_to/
https://www.reddit.com/r/GooglePixel/comments/7edcav/rcsservice_draining_battery/
https://forums.oneplus.net/threads/rcs-draining-battery.657535/
https://forums.oneplus.net/threads/rcs-service.666045/
https://forums.oneplus.net/threads/found-way-to-end-rcs-sucking-battery-after-oreo.659711/
So I managed to get a lot of my battery drain figured out, but a few things are still bothering me.
1) Google Play Services and Android System and/or Phone (see my last post) are using the Significant Motion Sensor to wake my device constantly.
2) Sony's smart charger (com.sonymobile.smartcharger) is waking my device. I'm assuming this has something to do with Battery Care, which I find to be a useful feature. But why does it need to continue sending alarms to wake up our phones when not plugged in?
I've attached 2 screenshots from Better Battery Stats showing the first issue (Sensors/Play Services and Phone) and 1 showing the second (Alarms/Smart Charger). Note the "wakeup=true" and long times recorded for Significant Motion. This held true when I had my phone sitting face-down on a table for 6+ hours to do battery testing earlier.
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
jrbmed08 said:
So I managed to get a lot of my battery drain figured out, but a few things are still bothering me.
1) Google Play Services and Android System and/or Phone (see my last post) are using the Significant Motion Sensor to wake my device constantly.
2) Sony's smart charger (com.sonymobile.smartcharger) is waking my device. I'm assuming this has something to do with Battery Care, which I find to be a useful feature. But why does it need to continue sending alarms to wake up our phones when not plugged in?
I've attached 2 screenshots from Better Battery Stats showing the first issue (Sensors/Play Services and Phone) and 1 showing the second (Alarms/Smart Charger). Note the "wakeup=true" and long times recorded for Significant Motion. This held true when I had my phone sitting face-down on a table for 6+ hours to do battery testing earlier.
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
Click to expand...
Click to collapse
I'm with you on RCSService being main culpirt for me. No I don't think it's a bug, it actually does use lots of battery. I listen to 3+ hours of bluetooth music a day and when I saw that RCSService was using more power than my bluetooth, then I thought it was time to experiment. So I uninstalled Carrier Service and RCSService and suddenly my battery life jumped by 20%. There was something in the November update to these services that made them go nuts. Several people have noticed a jump in battery usage, but most people, myself included, thought it was down to the new firmware. Uninstalling these 'features' has made no difference to SMS for me, other than I don't get a read confirmation.
I don't know about smart charger, sorry.
Pretty sure the proximity sensor is always on and that must use some power, but I don't know what that would be called in BBS.
Didgesteve said:
I'm with you on RCSService being main culpirt for me. No I don't think it's a bug, it actually does use lots of battery. I listen to 3+ hours of bluetooth music a day and when I saw that RCSService was using more power than my bluetooth, then I thought it was time to experiment. So I uninstalled Carrier Service and RCSService and suddenly my battery life jumped by 20%. There was something in the November update to these services that made them go nuts. Several people have noticed a jump in battery usage, but most people, myself included, thought it was down to the new firmware. Uninstalling these 'features' has made no difference to SMS for me, other than I don't get a read confirmation.
I don't know about smart charger, sorry.
Pretty sure the proximity sensor is always on and that must use some power, but I don't know what that would be called in BBS.
Click to expand...
Click to collapse
Thanks! I should clarify that when I say it's a bug, I believe something is using a lot of battery, but I don't know that it's necessarily Phone/RCS, because it shows up randomly as either that or just Android System. I think it might be something within Android System but being labeled as Phone or RCS. (Edit: Or the other way around; it could be 100% RCS and sometimes shows up as Android System because the phone is part of that umbrella.) I could be wrong but based my judgment on the links I posted above.
That being said, I disabled Carrier Services on your recommendation in the other thread because my carrier doesn't support VoLTE, VoWiFi, or RCS, I've never seen a "delivered" message, and I don't even use the Google Messages app anyway (I use Texra for SMS and keep Messages disabled). So like you, I don't need these services. And I do think there's been an improvement. Might be time to go through the rest of what you recommended via ADB. The only thing that concerns me about doing that is that I'll have to factory reset if I ever switch carriers and want those services, but I guess that's a small price to pay and an unlikely scenario anyway.
The smart charger thing is just weird. It shouldn't need to constantly check whether I'm charging since it kicks in when you plug in. Yesterday I disabled battery care during the day and re-enabled it at night to charge, and I had the best battery life since I've owned the phone: 4.5 hours of SOT over 18 hours off the charger with 30% remaining. I may have to look at idle drain with battery care disabled. I like the idea of battery care, but if it's draining my battery then it just defeats the purpose.
Regarding sensors, BBS has its own category for proximity sensor; this is a separate sensor for significant motion. Somehow Google Play Services and either Phone/RCS or Android System are using that particular sensor all the time. And not just listening to it, but causing lots of wakeups and doing so while the device is sitting on a table all night. I can only deduce that it's somehow seeing motion when there isn't any.
jrbmed08 said:
Regarding sensors, BBS has its own category for proximity sensor; this is a separate sensor for significant motion. Somehow Google Play Services and either Phone/RCS or Android System are using that particular sensor all the time. And not just listening to it, but causing lots of wakeups and doing so while the device is sitting on a table all night. I can only deduce that it's somehow seeing motion when there isn't any.
Click to expand...
Click to collapse
Do you have 'On Body Detection' enabled in smart lock? That would force the phone to affirm if it's moving/stationary regularly and quite often.
Didgesteve said:
Do you have 'On Body Detection' enabled in smart lock? That would force the phone to affirm if it's moving/stationary regularly and quite often.
Click to expand...
Click to collapse
I never enabled that from the start, but just checked in case Google did something, and it's still off.
I also checked my app permissions, and the only ones with access to body sensors are Google Play Services and Tasker. None of my active Tasker profiles require the significant motion sensor. One of them does use the orientation sensor to turn the speakerphone on when it's face-up during a call, but I tried disabling that profile and the stats didn't change.
Maybe I have a messed-up accelerometer...do you know of a way to test that? (Edit: Found it in the Support app - my accelerometer, gyroscope, and proximity sensor are fine)
I think I might head to the Sony Mobile forums with the smart charger issue for that matter. It may be a bug that affects all phones with Qnovo features, or maybe they could at least give me an explanation.
jrbmed08 said:
Might be time to go through the rest of what you recommended via ADB. The only thing that concerns me about doing that is that I'll have to factory reset if I ever switch carriers and want those services, but I guess that's a small price to pay and an unlikely scenario anyway.
Click to expand...
Click to collapse
Correct me if I'm wrong, but couldn't you just "reinstall" those services via the same adb commands? Where you typed uninstall, just replace with install?
Maybe, but I don't know where I would be installing them from...? Since I don't have a backup of the package. I uninstalled a bunch of stuff via adb before and it didn't return with a dirty reflash. I had to flash userdata. So that's all I'm going by.
I'm not sure of the actual technical mechanics, but I believe uninstalling system apps doesn't actually remove the package from the system image, so you can reinstall them at any time.
I think it's like taking down a sign on a store, the actual store is still there, just all references to it are no longer there, so to the OS it's not listed - "uninstalled".
Hello - was there any solution found for this issue?
jrbmed08 said:
Anyone else who uses battery monitoring apps: have you noticed any similar issues?
Click to expand...
Click to collapse
Hi there, what was the final solution to your issue?
Dean F said:
Hi there, what was the final solution to your issue?
Click to expand...
Click to collapse
I gave up. I still have a ton of wakelocks. GSAM shows a bunch of them even when my phone is supposedly dozing. My battery life is OK, not nearly as great as I hoped I'd have with this phone, but it gets me through the day so I've just been living with it. I have noticed better battery on the latest firmware (July patch) than June. I also got rid of the RCS stuff, which helped a bit. And finally I traced a lot of my drain to an app I was using called "hide running in background notification" which the last few firmwares can do natively.
(Edit: Sorry for missing your previous post!)
Edit: I was sadly mistaken about better battery on the July patch. The battery is only better if I'm not on wifi. I posted in the wifi drain thread about it just now.
General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
beache said:
General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
Click to expand...
Click to collapse
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Craz Basics said:
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Click to expand...
Click to collapse
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Tips for better battery life.
And a lot of common sense.
tuncan said:
Tips for better battery life.
And a lot of common sense.
Click to expand...
Click to collapse
very helpful thanks
chewingum16 said:
very helpful thanks
Click to expand...
Click to collapse
Tnx. :good:
Zombie said:
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Click to expand...
Click to collapse
yes it will on many cases, but I can't tell with the OP5. Is the circuit will cut-off the battery from the phone to avoid drain? If yes, in that case, it won't hurt significantly the battery.
In general , what can hurt li based batteries : time, heat and numbers of time of electrons changing direction.
Having the phone plugged in, every X time the % will drop, and the charging circuit will trigger the battery.
As I said, can't tell how op5 is working, and it probably be minimal anyway. But technically it will reduce the capacity : http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
Heat : 20W charger, even if its a vooc, at one point the battery will get a high current load = heat, and chemical li-po arrangement changes.
Time : cant do nothing here, chemical arrangement will degrade, its a normal process for most battery, specially li based one.
But at the end, not much people would see any difference, since nowadays people changing their phone every 1-2 years, fck ridiculous...
Back to topic :
Pixel off apps , many of them on the play strore, can't tell which one is good or not.
Basically, it will turn off pixels on the screen.
https://play.google.com/store/apps/details?id=com.anrapps.pixelbatterysaver&hl=fr
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
dkryder said:
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
Click to expand...
Click to collapse
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
shangxor said:
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
Click to expand...
Click to collapse
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
dkryder said:
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
Click to expand...
Click to collapse
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
[/COLOR]
shangxor said:
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
Click to expand...
Click to collapse
yes, i offered the link as a punchline to your comment about joking. however i do have a question about your comment,
"He had based part of his study on incorrect data also"
why didn't you include the part of the study and the incorrect data? because, when statement like this is made it is left to the reader to determine the part of the study and the incorrect data which may lead to misunderstandings.
My Gear S2 operates as normal as it should, however even at idle, the battery drains rapidly. Once the unit is completely dead, I then dock it and it will say 60% charge, which I know is wrong given that the unit will not power on undocked, meaning the battery had been completely depleted. Unit charges normally but I think a bug is preventing it from reaching actual 100% since it believes 0% to be 60%. Is there a way I can fix this without tearing apart the unit or replacing the battery?
same issue
I'm having the exact same issue, did a factory reset today updated all apps still same. I use a basic watch face, turn brightness to 2, everything off except Bluetooth and can get about a day of use . Is anyone else having this issue and has a solution?
Battery dead
So update on this issue, (on the Gear App on the phones most updated version) I went to the basic watch face in gray scale, then turned off all notifications, under gear connection, I unchecked sync wi-fi profiles, and under about gear I unchecked marketing information. I'm not sure which of those if any made the difference but at the end of day one 16 hours of use I was at 70%. So on the second day I tried a colorful watch face with animations, and 16 hours in I was at 63%. So one of those changes I made may have fixed my issue.
I did uninstall and reinstall the app on the phone, as well as reset the watch itself, neither seemed to work until I did the above changes. Hopefully that will help someone, or at least help to find out what is causing the massive battery drain.
dbrothers1 said:
So update on this issue, (on the Gear App on the phones most updated version) I went to the basic watch face in gray scale, then turned off all notifications, under gear connection, I unchecked sync wi-fi profiles, and under about gear I unchecked marketing information. I'm not sure which of those if any made the difference but at the end of day one 16 hours of use I was at 70%. So on the second day I tried a colorful watch face with animations, and 16 hours in I was at 63%. So one of those changes I made may have fixed my issue.
I did uninstall and reinstall the app on the phone, as well as reset the watch itself, neither seemed to work until I did the above changes. Hopefully that will help someone, or at least help to find out what is causing the massive battery drain.
Click to expand...
Click to collapse
With all that I have done with my gear, most I was able to get was about 10 hours. Though today it did to something odd. It died completely like it normally does, (it dies anywhere between 3-10% ish, and when it does die, its completely dead) so I placed it on the dock. Two minutes later I check and it reports 34%, "thats odd" I think to myself so I undock it and power it up thinking I would get no more than 5 minutes battery life on it since it couldnt possibly have that much charge in two minutes. I also expected it to report a low percentage but it didnt. I placed it back on my wrist and it continues to run about 10 minutes later down to 25% and still going! I find it odd. My current leakage issue I think remains and might be why the watch doesnt last as long. I might end up getting a new battery and see. My top battery user: watch faces at ~45%, even if the face hardly came on, and I am using one with a custom background that is mostly pure black.
Drain
That does sound pretty weird. I had a custom watch face installed "Mr Time" and started with a brand new install and I'm slowly adding things back in.
I would suggest a fresh install of the phone app, and the watch, using the classic face black and white. If you can get similar results to what I have then one by one start customizing it. I tried a lot of things to get it to work, over several days and that's what worked for me. I even uninstalled all of the watch faces I want using from the app"i felt that Mr time was still running in the background, even though it probably wasn't.
Good Luck
Hi everyone,
I got my new S20 FE just a few days ago, and I'm still getting used to it, but I wonder if having to charge the battery every day on average is "normal" or not.
When I plug the phone into the charger, the battery is never flat. Rather, it's hovering at around 30%, and I usually stop charging when it reaches 85 to 90%. I use the 15W (?) charger that was in the box, so no ultra-quick charge for this one.
I tried to plug it into a Xiaomi/Poco 33W charger for a few minutes, just to see if it would speed things up, but the remaining charging time was the same as with the regular charger so I reverted to it, just to be on the safe side.
Still, I wonder if it's normal to have to recharge the phone every day, when my Poco X3 Pro needed to be charged every two days on average. Granted, the Poco has a bigger battery, but it has an LCD screen instead of an AMOLED.
I spend a lot of time on Twitter, especially in the evening, mostly, but that's it. No gaming of any kind.
What say you?
try this https://eu.community.samsung.com/t5/galaxy-s20-series/s20fe-battery/td-p/2988440
Topo's said:
try this https://eu.community.samsung.com/t5/galaxy-s20-series/s20fe-battery/td-p/2988440
Click to expand...
Click to collapse
Hi,
I've turned Auto brightness off. I'll tell you if it changes anything in terms of battery life. I've also set AOD to fixed brightness instead of auto.
Thanks for the tip!
No problem, thank you for the question!
I think that debloating is not a bad idea, also try to go to all individual apps settings and set the battery to Restricted, except mail and messaging apps, so they won't drain the battery when you're not using them. Lowering the screen refresh rate also helps a bit, as well as restricting mobile data to 4G only, if you don't need 5G. Also, you can limit processor speed, turn Adaptive battery on and Enhanced processing off.
Hi again!
I've changed network settings to 4G and below since my SIM doesn't give me access to 5G yet, but battery life was still iffy. I then changed the network settings to something called "GLOBAL", and it's a bit better, though I don't know what that setting does exactly.
It also depends on how much your using your phone, what apps your running (games vs non-games, etc).
For example, I've played some games, but mainly have been on the internet via apps like social media, email, web browser.
I'm currently at 55% And it's been over 24 hours since I last fully charged it. The Battery graph says based on how I've been using the phone that I still have about 1d 3h left.
I do usually charge once a day, but it's definitely more than 24 hours after the last charge. I went to bed last night with over 62% left after having charged it probably 12 hours prior. When I woke up this morning, it was done to 59% and since then, is now at 55%.
So I've been pretty pleased with the battery life for me. Whether that's good or bad, I have no idea but it's definitely better than my last phone.
I don't do games on my phone (in fact, I don't do games at all, period), but I think the AOD being set on automatic lighting could have something to do with my relatively poor battery life. I'll try to set it to a fixed brightness and see if it changes things, though the brightness scale is pretty rudimentary. Maybe the light sensor is turned off when automatic brightness is off.
I usually spend more time on Twitter when I'm on the phone, so this could explain that.
Another possible factor is my application launcher: I use Microsoft Launcher, which I adore, but every time I wake up the screen, it does a position fix to update the weather widget. That could also explain why my battery drains faster than I expected.
I've just set AOD to fixed brightness. I'll tell you if it helps or not. Thanks for your input anyway!
UglyStuff said:
I don't do games on my phone (in fact, I don't do games at all, period), but I think the AOD being set on automatic lighting could have something to do with my relatively poor battery life. I'll try to set it to a fixed brightness and see if it changes things, though the brightness scale is pretty rudimentary. Maybe the light sensor is turned off when automatic brightness is off.
I usually spend more time on Twitter when I'm on the phone, so this could explain that.
Another possible factor is my application launcher: I use Microsoft Launcher, which I adore, but every time I wake up the screen, it does a position fix to update the weather widget. That could also explain why my battery drains faster than I expected.
I've just set AOD to fixed brightness. I'll tell you if it helps or not. Thanks for your input anyway!
Click to expand...
Click to collapse
I used to use Microsoft Launcher, but then switched to Nova launcher. However, since getting this phone, I've moved to OneUI and I'm loving it. I haven't really changed anything. AOD is set to whatever it was out of the box and I've been on Twitter and the web since I last posted and I'm currently at 53%.
I think I have seen MS Launcher be a battery hog if I remember. Nova isn't as bad, but OneUI seems to work great.
Also, the number and type of widgets you have installed could also cause battery drain. For me, I only have one screen. I use smart widgets to "stack" widgets I need which are calendar, weather (from WeatherBug), Brave Search, PowerAmp (for music) and then the phone maintenance widget. So far, battery life is pretty good like I've said.
You can also go into Settings->Battery and Device Care and maybe check in there to see what might be eating up your battery the most.
I like the look and feel of MS Launcher, compared to others (I believe I've tried them all over the years...), even if I have to admit Nova is a close second. MS Launcher is a possible culprit, obviously. I may switch back to One UI to check how things are going, I don't know.
I've just topped-off the battery, and just idling, the phone is supposed to last over 2 days until the next charge, but I know it won't last that long.
So I got my phone used (only 2 months, still has back poly attached) and it came with august 1 update and the battery drain on it is abysmal. I can see the battery go down while I'm browsing insta or whatever, not even gaming. You know what instantly fixed it? Downclocking my gpu and cpu using FKM. But this is not a pretty solution as it requires root and I would like to experience stock without root for a bit.
Which makes me think the system isn't properly downclocking the soc when idle leading to increased drain. I would like to know if anyone has a better fix than just disabling all the options on your phone.
KHSH01 said:
So I got my phone used (only 2 months, still has back poly attached) and it came with august 1 update and the battery drain on it is abysmal. I can see the battery go down while I'm browsing insta or whatever, not even gaming. You know what instantly fixed it? Downclocking my gpu and cpu using FKM. But this is not a pretty solution as it requires root and I would like to experience stock without root for a bit.
Which makes me think the system isn't properly downclocking the soc when idle leading to increased drain. I would like to know if anyone has a better fix than just disabling all the options on your phone.
Click to expand...
Click to collapse
Well, considering it's used (was it refurbished or did you purchase it off eBay or some other market)? That might be why it was being sold. You said 2 months. Does that mean it was only used for 2 months or you've had it for 2 months? If the phone itself is only 2 months old, who knows how the previous owner used the phone.
Did you do a factory reset when you got it to ensure it was back to stock settings? If so, then it might be your battery is bad and could be the reason it was sold/returned by the previous owner. If you haven't factory reset it, that is possibly the only other option that I can think of if you've already rooted and downclocked it.
Mine was new when I got it a few weeks ago and the battery lasts 1.5 days for me, even with the refresh rate set to 120 Hz. And that's with moderate use (playing games a bit, browsing the web, texting, phone calls).
You might want to try setting your screen refresh to 60 Hz to see if that helps as well if you haven't done that yet.
Go to Settings->Display->Motion Smoothness and select "Standard" to set it to 60 Hz refresh. That will save some battery as well.
See if that helps as well. If not, and as I stated, if you haven't done a factory reset, that might be your only other option unless someone else has something I haven't thought of.
iBolski said:
Well, considering it's used (was it refurbished or did you purchase it off eBay or some other market)? That might be why it was being sold. You said 2 months. Does that mean it was only used for 2 months or you've had it for 2 months? If the phone itself is only 2 months old, who knows how the previous owner used the phone.
Did you do a factory reset when you got it to ensure it was back to stock settings? If so, then it might be your battery is bad and could be the reason it was sold/returned by the previous owner. If you haven't factory reset it, that is possibly the only other option that I can think of if you've already rooted and downclocked it.
Mine was new when I got it a few weeks ago and the battery lasts 1.5 days for me, even with the refresh rate set to 120 Hz. And that's with moderate use (playing games a bit, browsing the web, texting, phone calls).
You might want to try setting your screen refresh to 60 Hz to see if that helps as well if you haven't done that yet.
Go to Settings->Display->Motion Smoothness and select "Standard" to set it to 60 Hz refresh. That will save some battery as well.
See if that helps as well. If not, and as I stated, if you haven't done a factory reset, that might be your only other option unless someone else has something I haven't thought of.
Click to expand...
Click to collapse
Yeah I got it from a store second hand. Came with the back poly still attached and no damages on the body. A killer deal. As for the battery issue, I had flashed wrong region stock rom. After learning what csc meant and figuring out I was on the wrong region I flashed the right rom and now my battery life is top notch. On a side note it has only 54 charge cycles after I got it.
KHSH01 said:
Yeah I got it from a store second hand. Came with the back poly still attached and no damages on the body. A killer deal. As for the battery issue, I had flashed wrong region stock rom. After learning what csc meant and figuring out I was on the wrong region I flashed the right rom and now my battery life is top notch. On a side note it has only 54 charge cycles after I got it.
Click to expand...
Click to collapse
Glad you were able to figure it out. Even though the phone is reaching 2 years since it's release, I've been very happy with it. My S7 finally died over a week ago after 5+ years of dependable service.
iBolski said:
Glad you were able to figure it out. Even though the phone is reaching 2 years since it's release, I've been very happy with it. My S7 finally died over a week ago after 5+ years of dependable service.
Click to expand...
Click to collapse
This is actually the second device I bought this year. At first I upgraded my Redmi Note 5 Pro which gave me 4 years of great service. Could have reached 5 but then I would not be able to exchange it so I did and got a Redmi Note 11 Pro Plus 5g. Considering how much I paid for it I was more or less satisfied except the camera. Then I bought this after months of careful consideration and also because it was a killer deal. I got a brand new device for half the price. Flagship specs at 33k bdt. You can't get a better deal.