Related
Just to say I've never used the Gear with a Samsung device. I also updated it immediately to Tizen so have no idea what battery life would have been like on Android.
I'm using a Moto G LTE and the gear Manager and Stub apk. It's not rooted or modded in any way. It works fantastically but I'm finding that the battery doesn't even last a day. I have the Gear set up so it only lights up when I press the standby button so aside from incompatibilities or some problem with the flash I've no idea what the problem is. Just wanted to know if I should EXPECT poor battery life with a non-Samsung phone paired to the watch or if I should investigate re-flashing or going back to Android. The Gear is a lovely device but is a bit useless if I can't make it through the day. I'm already down to 91% and I only took it off charge two hours ago.
Does anyone have any advice? If I can expect the battery to be rubbish I might just order an Android Wear watch; though I actually prefer the extra functionality of the Gear.
Thanks in advance.
bluetooth tethering
leoni1980 said:
Just to say I've never used the Gear with a Samsung device. I also updated it immediately to Tizen so have no idea what battery life would have been like on Android.
I'm using a Moto G LTE and the gear Manager and Stub apk. It's not rooted or modded in any way. It works fantastically but I'm finding that the battery doesn't even last a day. I have the Gear set up so it only lights up when I press the standby button so aside from incompatibilities or some problem with the flash I've no idea what the problem is. Just wanted to know if I should EXPECT poor battery life with a non-Samsung phone paired to the watch or if I should investigate re-flashing or going back to Android. The Gear is a lovely device but is a bit useless if I can't make it through the day. I'm already down to 91% and I only took it off charge two hours ago.
Does anyone have any advice? If I can expect the battery to be rubbish I might just order an Android Wear watch; though I actually prefer the extra functionality of the Gear.
Thanks in advance.
Click to expand...
Click to collapse
Do you have Bluetooth tethering enabled and so you use Bluetooth often?
hoddy4 said:
Do you have Bluetooth tethering enabled and so you use Bluetooth often?
Click to expand...
Click to collapse
How do you mean? The only thing I use Bluetooth for is the watch, other than the odd occasion at home when I connect a Bluetooth speaker.
The only notifications I have it set to send to the device are Robird and Hangouts. Nothing else is set to notify me. Not even Gmail.
It's not tethered to the internet via my phone if that's what you mean. Not even sure that's possible on Tizen. It just is set to send notifications from two ticked third party apps and for phone calls. Brightness is set to 3 and auto wake with hand movement is switched off. Battery now down to 82% with basically no use whatsoever other than being connected.
leoni1980 said:
How do you mean? The only thing I use Bluetooth for is the watch, other than the odd occasion at home when I connect a Bluetooth speaker.
The only notifications I have it set to send to the device are Robird and Hangouts. Nothing else is set to notify me. Not even Gmail.
It's not tethered to the internet via my phone if that's what you mean. Not even sure that's possible on Tizen. It just is set to send notifications from two ticked third party apps and for phone calls. Brightness is set to 3 and auto wake with hand movement is switched off. Battery now down to 82% with basically no use whatsoever other than being connected.
Click to expand...
Click to collapse
Yes, I was talking about Bluetooth tethering to the internet which can really affect battery. On Android (not Tizen), I would expect battery usage to be about 2% per hour with very light usage.
hoddy4 said:
Yes, I was talking about Bluetooth tethering to the internet which can really affect battery. On Android (not Tizen), I would expect battery usage to be about 2% per hour with very light usage.
Click to expand...
Click to collapse
OK, I did a hard reset via the recovery menu on the Gear and it seems to have improved things. Currently on 96% after over 4 hours. Still only have two apps set to give notifications - SMS and WhatsApp - and only when phone screen is off. Also still have auto screen activate switched off. Not really sure what sort of battery life to expect but this is better at least!
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.
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!
Morning all
Probably a silly question but while Bluetooth is on - myy s10 doesnt go to sleep and the battery drains very fast.
With it off its fine.
Unfortunately I use BT for my sony wireless buds and Galaxy watch.
Are there any tweaks to help out with battery life?
Its connected to the watch all the time while im wearing it so is this something i need to get used to?
adesad said:
Morning all
Probably a silly question but while Bluetooth is on - myy s10 doesnt go to sleep and the battery drains very fast.
With it off its fine.
Unfortunately I use BT for my sony wireless buds and Galaxy watch.
Are there any tweaks to help out with battery life?
Its connected to the watch all the time while im wearing it so is this something i need to get used to?
Click to expand...
Click to collapse
Hmmn. I keep mine on to connect to my Xiaomi Mi Band 5 though I notice it Bluetooth does turn off occasionally. Hadn't noticed S10e draining faster (it does seem to still go to sleep) but maybe I haven't been paying enough attention. I'll be interested in any replies.
Try disabling all power management.
Load Karma Firewall. Android Services and Goggle Play Services* are big offenders.
Unfortunately if your on Q or higher Karma's logging feature doesn't work. This shows you real time what's hogging the internet and battery.
Another reason I'm still on Pie.
* enable briefly to access Gmail etc.
I have been using Better Battery Stats to keep an eye on it.
While BT is on the CPU sits at 1.95 at over 90% of the time I've tested it against.
With BT off - it does goto sleep and battery is loads better.
I need it on for the reasons above but its a right hog.
adesad said:
I have been using Better Battery Stats to keep an eye on it.
While BT is on the CPU sits at 1.95 at over 90% of the time I've tested it against.
With BT off - it does goto sleep and battery is loads better.
I need it on for the reasons above but its a right hog.
Click to expand...
Click to collapse
Disabled all power management.
Try clearing apk data and going back to factory load.
Clear system cache on boot menu.
Disable any 3rd party apks other than Wearables using bt.
Start locking down apks that don't really need internet access with Karma Firewall* until you find the hog. Probably a system apk and the drain may actually be from constant internet traffic. Misreporting which apk is the culprit isn't uncommon as many have related dependencies.
*if you're running Q or higher it's logging function is disable I believe. It works fine with Pie and is an important tool. Otherwise you'll need to do it the hard way. Thanks Google, you suck.
Android Services, Google Play Services, Google Backup Transport and Google Framework are all hog candidates. Best to package block the last two and clear apk data on all but Android services as needed. This what I did to take my 10+ running on Pie.