Temperature Sensor - Battery Charging Issue - Nexus 6 Q&A, Help & Troubleshooting

I recently changed batteries. After a single charge cycle, the temperature sensor now gives an obviously false -30 or -20 C. This prevents the battery from charging. An Xposed app called Sensor Disabler allows you to control the sensors. Unfortunately, Xposed isn't working on Nougat which I am running. Anyone know of an alternative app for this purpose? Anyone know how to write an app for this purpose? Anyone know where the temperature sensor is located and how to replace/ fix it? No longer under warranty, so that won't work.. Any other suggestions?

groundslug said:
I recently changed batteries. After a single charge cycle, the temperature sensor now gives an obviously false -30 or -20 C. This prevents the battery from charging. An Xposed app called Sensor Disabler allows you to control the sensors. Unfortunately, Xposed isn't working on Nougat which I am running. Anyone know of an alternative app for this purpose? Anyone know how to write an app for this purpose? Anyone know where the temperature sensor is located and how to replace/ fix it? No longer under warranty, so that won't work.. Any other suggestions?
Click to expand...
Click to collapse
My guess is you messed up putting one of the plugs back in... The battery temp sensor is in either the battery harness(probably not) or the wireless charger (more likely)...
Take it apart again and make sure the connections are made properly
Sent from my Nexus 6 using Tapatalk

rignfool said:
My guess is you messed up putting one of the plugs back in... The battery temp sensor is in either the battery harness(probably not) or the wireless charger (more likely)...
Take it apart again and make sure the connections are made properly
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Right you are! Thank you for your help.

Hello. I've changed battery too. But battery temp always 25 degree C°. And moreover any app can't display cpu temp anymore. How can it be? I admit the battery sensor is bypassed (China's battery). But what happened with cpu temp sensors?
Thanks for your opinion.

lionbs said:
Hello. I've changed battery too. But battery temp always 25 degree C°. And moreover any app can't display cpu temp anymore. How can it be? I admit the battery sensor is bypassed (China's battery). But what happened with cpu temp sensors?
Thanks for your opinion.
Click to expand...
Click to collapse
Loose connection... Recheck em all
Sent from my Nexus 6 using Tapatalk

Related

[Q] Nook battery dies fast

I only have 5 widgets, and my brightness is also low as possible. I have wifi off when i don't use it, but my battery still dies kinda fast. Should i delete cell standby? And what else can i do?
You really should define "kinda fast" so folks can answer objectively
Well just playing games like angry birds for 20 minutes it drops like 10%
EverythingNook said:
Well just playing games like angry birds for 20 minutes it drops like 10%
Click to expand...
Click to collapse
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.
HotShotAzn said:
1) Which ROM
2) What widgets
3) What are you using to monitor battery drop
10% in 20 minutes (screen on, in use) is pretty aggressive.
Click to expand...
Click to collapse
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery
EverythingNook said:
1. Stock with launcherpro
2. Typoclock power control beautiful battery google search and music
3. Beautiful battery
Click to expand...
Click to collapse
What drain are you seeing with screen off/idle?
with the screen off for about 5 hours i saw a 21% drain.
Drop the widgets and livewallpaper if you've got it. Retest standby.
If you're getting high battery drain during standby your nook isn't going into deep sleep and chances are that background overhead translates to poor efficiency at idle when the nook is on as well. Couple poor idle efficiency with CPU intensive work while in use and your overall battery life is terrible.
If you're forcing the nook to stay out of deep sleep for other reasons like keeping wifi alive then you may be stuck with living with some sort of elevated drain but you can minimize it by reducing idle overhead by keeping widgets to a minimum and refraining from using live wallpapers and other background services that aren't critical.
Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!
distortedloop said:
Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running.
Click to expand...
Click to collapse
If you suspect it, disable it and see. I'm thinking that would be a prime suspect.
distortedloop said:
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Click to expand...
Click to collapse
I believe typically overnight you should see less than 10% drain.
In CM7 at least, in Spare Parts you can see what uses the battery while the NC is asleep.
distortedloop said:
Tacking on to here rather than starting a new thread...
My Nook Color rooted, but still on stock ROM goes from 100% charge to 25% in about 8-9 hours with zero usage. Obviously something's going on (I suspect it's that I have Advanced WiFi sleep policy set to never and am away from WiFi), but no other widgets running. I do have Google Voice app installed.
What I'm curious about is what would normal standby battery drain be? What would be typical after 8-9 hours of just sitting untouched in my brief case?
Thanks in advance!
Click to expand...
Click to collapse
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
No, not yet. It's 100% stock, other than rooting and downloading apps. I'm going to put SystemPanel on it and see if it gives a clue.
I've got a good idea of how to track down battery issues on most android devices, I was just mostly curious what the typical drain other rooted users saw was.
Thx for the suggestions to all.
hxh103 said:
do you have it overclocked? if so, have a profile that clocks it down to 300mhz when the screen is locked
Click to expand...
Click to collapse
Good lord, this isn't going to help anything. Normal Nook Colors on the stock ROM (and kernel....) use about .2%/hr in standby.
Clearly something is running wild on this guys NC, and needs to look at Spare Parts. Install it from the market.
System Panel as well as other tools can help as well.
Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)
distortedloop said:
Okay, I'm a pretty smart guy usually, but I'll publicly put on the dunce cap and admit to my ignorance on this one.
System Panel actually showed some amazingly good lack of drain with all my apps running.
The reason my battery was so low when I checked it each afternoon is because even though I thought I was charging the thing over night, I wasn't. I was using a regular micro-usb cable for my phone to plug the thing in most nights.
Turns out the Nook Color has an extra deep micro-usb receptacle and requires a better endowed male plug to get it charged properly.
Lame...
(Lame of me, but also lame of B&N to make such a design decision. What were they thinking? I HATE proprietary connectors.)
Click to expand...
Click to collapse
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.
Extra deep. Two stages...
First stage 5 pins, second stage 12 pins...
Sent from my Nexus One using XDA Premium App
Yup same cable as my Droid2 and Droid before it....
Krazypoloc said:
Yup same cable as my Droid2 and Droid before it....
Click to expand...
Click to collapse
Does this mean we can use the droid2 and droid's cables as alternatives?
khaytsus said:
Extra WIDE, not deep. And there's good reason USB standards are .5A over the typical 4 pin connection. The B&N cable has FOUR extra pins, delivering the other 1.4A of power.
Click to expand...
Click to collapse
Thanks for the extra info about the additional voltage; so it will charge much faster this way? (rhetorical question)
I still am annoyed at yet another non-standard cable that I'll have to carry around with me when I travel to keep various devices charged, but in the scheme of things it's a minor annoyance. Stuff like this should be standardized, IMHO.
And it's extra DEEP, not wide. It's the same width as a standard micro-usb cable or I wouldn't have been able to stick my phone's charging cable into it at all, but I was able to, it just didn't go in deep enough to charge at all. On the flips side, the B&N cable fits into my phone, but only inserts half-way deep; if it were extra wide it wouldn't fit into my phone at all.

[Q] Disable temperature check?

Is there a way to disable temperature check for battery and CPU on CM7 rom on X8. I know that i can delete sysmon.cfg for some rom-s, but this one doesnt have one.
the problem isn't in the app, maybe some modules, why would you want it removed anyways?
Swyped via Tapatalk 2
Do you use an app for that?
i need to disable temperature sensor becouse of wrong readings, i have battery that overheats and turns off the phone, but when i tape middle pin on battery readings are fine, so i need software solution to disable readings of android temperature
mile18 said:
i need to disable temperature sensor becouse of wrong readings, i have battery that overheats and turns off the phone, but when i tape middle pin on battery readings are fine, so i need software solution to disable readings of android temperature
Click to expand...
Click to collapse
Our phone doesn't have temperature sensor ..
sent using internet explorer, hope it reaches on time :fingers-crossed:
Gogeta said:
Our phone doesn't have temperature sensor ..
sent using internet explorer, hope it reaches on time :fingers-crossed:
Click to expand...
Click to collapse
gogeta, every android phone has battery temperature sensor, please read that i have written in first post

WACKLOCKS i need your help guys

hi guys
i have abattery drain in idle like 4% for hour even with 3g ,wifi,and all stuff off
some one told to send my device back ,and i want to chack with you last time what you say.
even when my phone power off i lose battery ,before few days i was left him with 64% and power off for 24 hours when i power on i was on 6 %
i want you to chack my karnel wacklocks , and sensor
wait for your answers tnx alot
The Same Issue here
Help Plz
Your wake locks look just fine....
So it's losing battery when it's completely off? That doesn't sound right at all
Sent from my Tricked out HTC One
Squirrel1620 said:
Your wake locks look just fine....
So it's losing battery when it's completely off? That doesn't sound right at all
Sent from my Tricked out HTC One
Click to expand...
Click to collapse
yep even when the phone power off i lose battery
That doesn't sound right. I was getting quite a lot of battery drain during screen off/sleep, not as much as you mind, but I disabled Google maps, installed a third party navigation app and tuned Google location settings off and pow...I'm on my second day without charging and still on 50% battery! Really has made a big difference. And the third party nav app works offline so no data usage.
Sent from my HTC One using xda app-developers app
VaderXI said:
That doesn't sound right. I was getting quite a lot of battery drain during screen off/sleep, not as much as you mind, but I disabled Google maps, installed a third party navigation app and tuned Google location settings off and pow...I'm on my second day without charging and still on 50% battery! Really has made a big difference. And the third party nav app works offline so no data usage.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i dont think this will work for me ,what you think about the sensor wakelocks?
Mine look exactly like that. I don't know why audio_out needs a wake lock, but it does. I get about 2% drain per hour though. Really do try disabling the location services. That uses a lot of battery.
aooga said:
Mine look exactly like that. I don't know why audio_out needs a wake lock, but it does. I get about 2% drain per hour though. Really do try disabling the location services. That uses a lot of battery.
Click to expand...
Click to collapse
hi man
does your sensor and karnel waklocks look like this?
i had the problem with audio_out4 before and factory reset fix it
before he workd like servel hours now its 14 min that i play agame
if you can upload some photos please
help guys
What's your CPU bin number ?
Look at the file /proc/last_kmsg
search for where it says something like [0.602014] c0 1 acpuclk-8064 acpuclk-8064: ACPU PVS: 5
That PVS number is your CPU bin number quality. 0 is the lowest (bad quality & high drain) and 6 is the highest (best quality & reduced drain)
If you've got a PVS 0,1,2 or maybe 3 you should consider going and swapping the phone with your provider.
snachez said:
What's your CPU bin number ?
Look at the file /proc/last_kmsg
search for where it says something like [0.602014] c0 1 acpuclk-8064 acpuclk-8064: ACPU PVS: 5
That PVS number is your CPU bin number quality. 0 is the lowest (bad quality & high drain) and 6 is the highest (best quality & reduced drain)
If you've got a PVS 0,1,2 or maybe 3 you should consider going and swapping the phone with your provider.
Click to expand...
Click to collapse
where can i find this file?
i am on stock not root
roy1210 said:
where can i find this file?
i am on stock not root
Click to expand...
Click to collapse
It's in the /proc directory. You'll need to be rooted to access it afaik sorry
more help guys tnx
This is the second thread this OP has started about the same issue. He refuses to accept that he can't achieve 0% battery loss when the phone is idle or even powered off. I really don't know what we can do for him... :/
See his original thread.
Squirrel1620 said:
So it's losing battery when it's completely off? That doesn't sound right at all
Click to expand...
Click to collapse
Actually, this is quite correct. No battery technology to date retains charge forever--the physics simply aren't there. As a battery ages, it will deplete if it is not fed a constant charge. Now, I'll grant you that this depletion is VERY VERY VERY VERY VERY SLOW, but it's still there. My Droid RAZR MAXX would be incredibly low on battery in about 4 days even completely turned off.
EDIT: Re-reading the OP's post here, I noticed he cites that he lost alot of battery while the phone was "powered off" for 24hrs. Likely, I suspect he had "Fast Boot" mode turned on, which actually puts the phone into a hibernate mode rather than actually powering it down completely. These are not the same thing.
unremarked said:
This is the second thread this OP has started about the same issue. He refuses to accept that he can't achieve 0% battery loss when the phone is idle or even powered off. I really don't know what we can do for him... :/
See his original thread.
Actually, this is quite correct. No battery technology to date retains charge forever--the physics simply aren't there. As a battery ages, it will deplete if it is not fed a constant charge. Now, I'll grant you that this depletion is VERY VERY VERY VERY VERY SLOW, but it's still there. My Droid RAZR MAXX would be incredibly low on battery in about 4 days even completely turned off.
EDIT: Re-reading the OP's post here, I noticed he cites that he lost alot of battery while the phone was "powered off" for 24hrs. Likely, I suspect he had "Fast Boot" mode turned on, which actually puts the phone into a hibernate mode rather than actually powering it down completely. These are not the same thing.
Click to expand...
Click to collapse
in my first thread it was audio_out4 that wacklocs and i did factory reast and its good now now its not the same issue
its just to know what you think hardware or softwere
tnx for your answers

Sensor causing battery drain?

Hi all,
I know that there are hundreds of threads already about eeking out more from the battery.
I can just about get to the end of the day without charging most days, but not always so I'd appreciate your help.
Using gsam battery monitor shows that TMD4906 proximity sensor has had 294 wakelocks so far today (1h 58 mins cpu time) since I unplugged 4 hours ago.
Battery is down to 69% for just 1h 17mins of SOT today.
Happy to send Gsam screen shots if that helps, but it seems a huge amount of drain is from the above.
CHeers,
Andy
With reset you solve problemes
michelino159 said:
With reset you solve problemes
Click to expand...
Click to collapse
ah sorry, forgot to mention that I've done a factory reset and manually installed apps one by one.
Same problem
You could try with "force doze" app, has an option to deactivate sensors, there is a thread about it
I'm having the same issue. Try leaving your phone with the screen down over the table. It looks like the proximity sensor wakelock disappears according to GSam Battery Monitoring.
dehkun said:
I'm having the same issue. Try leaving your phone with the screen down over the table. It looks like the proximity sensor wakelock disappears according to GSam Battery Monitoring.
Click to expand...
Click to collapse
Where does it show this information on gsam? All I see under Android system within gsam is tmd4906 prox usage 5 hours since 1D 7HOURS.
Limeybastard said:
Where does it show this information on gsam? All I see under Android system within gsam is tmd4906 prox usage 5 hours since 1D 7HOURS.
Click to expand...
Click to collapse
Gsam reports tmd4909 prox using only seconds, never more than 14 or 16 of use, I find it strange, because I use gravity screen app which uses prox sensor all the time!
Think I figured it out. Last night I didn't close my wallet style case and the figure remained low.
Basically it seems to be the wallet style case covering the front of the phone causing increased proximity usage it would appear. Will run without wallet style case for a while to verify.
EDIT : THIS WASN'T IT.
Sent from my SM-N950U using Tapatalk

Limit Battey Charge % Android 11

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!

Categories

Resources