Related
Hello xda-community!
First of all, thank you for your great material, guides and information you are offering here!
Now to the point:
I've flashed my Kindle Fire HDX 7" (Thor) with TWRP 3.0.3-1 with the LineageOS 14.1 and everything was great the first day.
After the night with my Kindle plugged in to AC charger I recognised my device turn off overnight. Was a little bit tricky to turn on (60s power-button reset) again.
No issues while using it in day-time. This time over night I didn't plug it in.
The next morning I saw the device rebooted and got stuck in the grey kindle fire bootloader screen. I reset then booted to Recovery TWRP showed me 14% battery left.
I've pluged it in AC charger and booted to Lineage. Lineage then showed me 100% battery charged. Even when I unplugged the kindle form power it remains 100 % charged and says its connected to AC power.
After this I let my Kindle run empty. The battery indicator in Lineage still remained 100%. The OS didn't shut down when power was low. In the end the screen was showing dark spots and was flashing 2 seconds to white and then the device was dead.
I've plugged it in again. Since this Lineage still shows 100% charged. If I boot to TWRP the battery indicator in the status bar disappeared mysteriously.
adb shell dumpsys battery brings up:
Code:
adb shell dumpsys
Current Battery Service state:
AC powered: true
USB powered: true
Wireless powered: false
Max charging current: 0
Max charging voltage: 0
status: 2
health: 2
present: true
level: 100
scale: 100
voltage: 0
temperature: 424
technology:
I've also flashed the LinageOS again and I've tried older versions of TWRP still the same (TWRP no battery indicator; Lineage 100%)
Also in CM13 it shows 100% charged. The kindle became very unstable and can only be run plugged in now. It seems the battery isn't chrarging at all any more.
What can I do to use the battery normal? Should I replace the battery?
I've also saw that the folder /sys/class/power_supply/ only contains 3 subfolders:
Code:
smb349_ac
smb349_usb
usb
I'm not sure but it seems to me that the folder for my battery is missing. Anybody have an idea?
Necronomynus said:
I've also saw that the folder /sys/class/power_supply/ only contains 3 subfolders:
Code:
smb349_ac
smb349_usb
usb
I'm not sure but it seems to me that the folder for my battery is missing. Anybody have an idea?
Click to expand...
Click to collapse
Can please someone post the "normal" view of this class? Thank you
OK folks, seems my battery has found its way back to life.
The class now looks like this:
Code:
bq27x41
smb349_ac
smb349_usb
usb
And the bq27x41 subclass contains all the info of my battery I could wish for. Charging and discharging behaviour seems pretty normal at the moment.
adb shell dumpsys battery now brings up:
Code:
ads su shell dumpsys
Current Battery Service state:
AC powered: false
USB powered: false
Wireless powered: false
Max charging current: 0
Max charging voltage: 0
Charge counter: 0
status: 3
health: 2
present: true
level: 86
scale: 100
voltage: 4105
temperature: 358
technology: Li-ion
Don't ask me what how I've exactly repaired my device. That's what I did:
flash kindle fire OS recovery system data boot with TWRP
flash vunarable bootloader and unlock it
flash TWRP 3.0.2-2 again
wipe everything also format data
flash CM13 and GAPPS
reboot/reset
let device in TWRP turned on and connected to AC power for 24h
wipe and flash Linage14. 1 and GAPPS
used my device normal while plugged in all the time for 3 days. When I'm not using it, I shutdown OS and unplugged my device. Then I've always powered it on again while connected to the AC-charger
after OS was running 2h I've unplugged my device from AC and now the battery is working again
Damn. I've booted to TWRP to see if the battery indicator is back but it was not. So no I've the same status again like in the OP.... No battery indicator in Lineage14. 1, too. I don't get it what happened.
Can someone please explain how and when this class is initialised by Android and when the objects (power_supply/bq27x41) are created. How can I trigger this?
Necronomynus said:
Damn. I've booted to TWRP to see if the battery indicator is back but it was not. So no I've the same status again like in the OP.... No battery indicator in Lineage14. 1, too. I don't get it what happened.
Can someone please explain how and when this class is initialised by Android and when the objects (power_supply/bq27x41) are created. How can I trigger this?
Click to expand...
Click to collapse
Met the same problem... I ran out of the battary and charged. After I rebooted, the battery indicator never worked again.
Necronomynus said:
Damn. I've booted to TWRP to see if the battery indicator is back but it was not. So no I've the same status again like in the OP.... No battery indicator in Lineage14. 1, too. I don't get it what happened.
Can someone please explain how and when this class is initialised by Android and when the objects (power_supply/bq27x41) are created. How can I trigger this?
Click to expand...
Click to collapse
Have you finally solved the problem? I reflashed Lineage and also tried CM13, but the problem remained. I plan to try the official OS to see if it works.
fhh2626 said:
Have you finally solved the problem? I reflashed Lineage and also tried CM13, but the problem remained. I plan to try the official OS to see if it works.
Click to expand...
Click to collapse
Thoughts:
- downgrade TWRP to 3.0.0-1 (yes, this seems unrelated; eliminating variables)
- try Fire Nexus (KitKat build) which shares the largest common base w/stock
- be sure to wipe system and data partitions prior to each attempt
Obviously Nexus is not a permanent solution; just trying to drive to root cause)
Davey126 said:
Thoughts:
- downgrade TWRP to 3.0.0-1 (yes, this seems unrelated; eliminating variables)
- try Fire Nexus (KitKat build) which shares the largest common base w/stock
- be sure to wipe system and data partitions prior to each attempt
Obviously Nexus is not a permanent solution; just trying to drive to root cause)
Click to expand...
Click to collapse
I tried Nexus..doesn't help. thanks anyway
fhh2626 said:
I tried Nexus..doesn't help. thanks anyway
Click to expand...
Click to collapse
no I have not found a solution yet. Still facing the same problem sometimes it works for some hours or days in LineOS and the suddenly the battery status is not updated anymore (e.x. at 55% battery doesn't change even when I plug in) after reboot it shows imediateley 100 % for some days) Then even while operating LineOS and without need of a reboot the indicator suddenly is working again.
It would be really helpful to know which event and which command the kernel issues to refresh/rebuild battery information from the smb349 (battery power-management IC) via i2cget command.
While using the Kindle without working battery indicator (I can still use it normally, even unplugged now) I just have to remember myself how long I've used it unplugged not to run out of battery unexpected.
While the working battery indicator days I've run "Accu Battery 1.1.7c" App which reports good health status and about 93% of the design capacity (4550 mAh) of my battery left
I always power it off and unplug it in phases I'm not using it for longer time (e.x. overnight). This improved the stability a lot.
Necronomynus said:
no I have not found a solution yet. Still facing the same problem sometimes it works for some hours or days in LineOS and the suddenly the battery status is not updated anymore (e.x. at 55% battery doesn't change even when I plug in) after reboot it shows imediateley 100 % for some days) Then even while operating LineOS and without need of a reboot the indicator suddenly is working again.
It would be really helpful to know which event and which command the kernel issues to refresh/rebuild battery information from the smb349 (battery power-management IC) via i2cget command.
While using the Kindle without working battery indicator (I can still use it normally, even unplugged now) I just have to remember myself how long I've used it unplugged not to run out of battery unexpected.
While the working battery indicator days I've run "Accu Battery 1.1.7c" App which reports good health status and about 93% of the design capacity (4550 mAh) of my battery left
I always power it off and unplug it in phases I'm not using it for longer time (e.x. overnight). This improved the stability a lot.
Click to expand...
Click to collapse
Curious - which build of TWRP do you have installed? Obscure long shot but updgrading/downgrading might yield some insights. Does battery status show correctly from the recovery UI?
Another (albeit riskier) option is to reflash the vulnerable bootloader.
Davey126 said:
Curious - which build of TWRP do you have installed? Obscure long shot but updgrading/downgrading might yield some insights. Does battery status show correctly from the recovery UI?
Click to expand...
Click to collapse
Thank you Davey for trying to help us.
I'm using TWRP 3.1.0.0. At the periods the indicator works in LineageOS it also works in TWRP and vice versa if not then both not.
I've also tried TWRP 3.0.2-2 which shows the same behaviour.
I've upgraded to the LOS 02. May release today. Maybe the indicator works better now. I will let you know.
In the Folder /sys/class/power_supply/
The bq27x41 is a link to the object:
Code:
/sys/devices/f9967000.i2c/i2c-0/0-0055/power_supply/bq27x41
This object and all it's sub objects are these
Code:
/power/autosuspend_delay_ms
/power/control
/power/runtime_active_time
/power/runtime_status
/power/runtime_suspended_time
capacity
charge_full
charge_full_design
charge_now
charge_now_design
current_now
device.lnk
energy_avg
health
manufacturer
status
subsystem.lnk
technology
temp
type
uevent
voltage_now
Davey126 said:
Curious - which build of TWRP do you have installed? Obscure long shot but updgrading/downgrading might yield some insights. Does battery status show correctly from the recovery UI?
Another (albeit riskier) option is to reflash the vulnerable bootloader.
Click to expand...
Click to collapse
The problem still the same in the LOS 14.1 May release. But overall performance getting better now only approx 25% of usage time of the device my battery indicator doesn't work.
What is the risk with flashing the vulnerable boot loader? Do I have to unlock it again?
Necronomynus said:
The problem still the same in the LOS 14.1 May release. But overall performance getting better now only approx 25% of usage time of the device my battery indicator doesn't work.
What is the risk with flashing the vulnerable boot loader? Do I have to unlock it again?
Click to expand...
Click to collapse
I find it interesting the battery indicator also does not work when booted into a custom recovery (TWRP) which operates independently from whatever lives in the system partition (eg: LinOS).
A refreshed bootloader would likely need to be unlocked; depends where keys are held (above my wage grade). Risks include potential result data loss and/or bricking the device should the flash goes bad; a twiddled bit can yield a very bad day at the office. I view the last two as unlikly but would be remiss in not mentioning the possibility.
@draxie - thoughts?
genie in the battery...
Davey126 said:
I find it interesting the battery indicator also does not work when booted into a custom recovery (TWRP)
which operates independently from whatever lives in the system partition (eg: LinOS).
Click to expand...
Click to collapse
Independent is a relative term in this case, I'd posit.
Based on my quick read of this thread, that battery
appears to enter some weird state from time to time,
gets stuck there for a while, only to get "unstuck" for
no obvious reason after some random period in limbo.
The only firm conclusion I could make is that neither
LineageOS nor TWRP have the chops to systematically
pull the battery out of limbo. In other words, when it's
stuck, it simply doesn't show up in either... (Now, why
LineageOS decides to show a missing battery as fully
charged is beyond me, but that's beside the point.)
To me, that implies a strong dependence in how each
'partition' will behave, since that appears to be fully
determined by the state of the battery.
The more interesting question is what triggers the limbo.
Based on the first few posts, I had the theory that Lineage
was clearly to blame (as I haven't found any mention of
the "good state" going bad while in TWRP), but then post#5
made me less sure, as it gave the impression that booting
into TWRP _when_everything_worked_ in Lineage caused
the battery to go missing again...
BTW, what I find *most* curious is that 'dumpsys battery'
output in post#4. If that was really generated from 'adb'
(as opposed to a terminal emulator on the device itself),
'USB powered: false' is decidedly not what I would expect.
Here's the output of the same command on my test Thor:
Code:
[B][email protected]:/ # dumpsys battery [/B]
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
status: 2
health: 2
present: true
level: 87
scale: 100
voltage: 4175
current now: 606000
temperature: 256
technology: Li-ion
I attribute the fact that the fields are different to me running FireOS,
but it may also be indicative of different drivers/device definitions.
Also the discrepancy in the temperature readings (256 vs 358) may be
a cause for alarm (depending on the ambient temperature there at the
time; I don't have a thermometer, but I'd guess it's around 23-25C here).
Davey126 said:
A refreshed bootloader would likely need to be unlocked; depends where keys are held (above my wage grade). Risks include potential result data loss and/or bricking the device should the flash goes bad; a twiddled bit can yield a very bad day at the office. I view the last two as unlikly but would be remiss in not mentioning the possibility.
@draxie - thoughts?
Click to expand...
Click to collapse
If you mean flashing the very same vulnerable bootloader to the aboot
partition anew by a "refreshed bootloader", then you wouldn't need to
unlock again (i.e. the device "stays unlocked"), unless you flash another
version in between. On the other hand, I'm not quite sure what you
expect to gain from flashing a bit for bit identical image... (if it wasn't
the device wouldn't even boot; the bootloader is also signed).
Instead, I'd suggest to test running with FireOS for a few days (there's
no way to get closer to stock, if you can stand it) and see if the battery
still behaves erratically. If so, you should probably consider swapping it
(although, the root cause could easily be a _related_ HW component
and not the battery itself). I have a hard time seeing this as a pure SW
issue in LineageOS, since we should have seen plenty more reports (or,
at least, more meetoos on this thread). I've tested Lineage briefly on
this test Thor and haven't seen anything similar.
draxie said:
Instead, I'd suggest to test running with FireOS for a few days (there's
no way to get closer to stock, if you can stand it) and see if the battery
still behaves erratically. If so, you should probably consider swapping it
(although, the root cause could easily be a _related_ HW component
and not the battery itself). I have a hard time seeing this as a pure SW
issue in LineageOS, since we should have seen plenty more reports (or,
at least, more meetoos on this thread). I've tested Lineage briefly on
this test Thor and haven't seen anything similar.
Click to expand...
Click to collapse
Thank you draxie for you're precise analysis and help.
I'm still operating LinageOS. It's very stable now.
I don't know what sends the battery object to limbo but it seems like I found a solution to get it out there:
I've found out after the battery indicator stayed in limbo for approx. 10 days.
I've always used a USB-Charger with only 500mA through out this period.
But recently I have incidentally used another power source (Anker 28W Wall-Charger) with a original Kindle USB-Cable. After booting (because battery run totally empty before) it started with 5% battery indicator and its behaviour normal.
In the beginning (of this thread) I often changed chargers and cables (1 A Apple charger, USB-charging via Laptop, 2 A "China-noname" charger, 1.5 A Sony Charger) so it would explain the random behaviour.
So I have the theory it all depends on the charger and USB-cable to cause this issue with my device.
However I will try with the weak 500 mA charger if I can send the battery indicator to limbo with it. After this I hope I can confirm you that the strong charger and original cable can recover the battery indicator.
Necronomynus said:
Thank you draxie for you're precise analysis and help.
I'm still operating LinageOS. It's very stable now.
I don't know what sends the battery object to limbo but it seems like I found a solution to get it out there:
I've found out after the battery indicator stayed in limbo for approx. 10 days.
I've always used a USB-Charger with only 500mA through out this period.
But recently I have incidentally used another power source (Anker 28W Wall-Charger) with a original Kindle USB-Cable. After booting (because battery run totally empty before) it started with 5% battery indicator and its behaviour normal.
In the beginning (of this thread) I often changed chargers and cables (1 A Apple charger, USB-charging via Laptop, 2 A "China-noname" charger, 1.5 A Sony Charger) so it would explain the random behaviour.
So I have the theory it all depends on the charger and USB-cable to cause this issue with my device.
However I will try with the weak 500 mA charger if I can send the battery indicator to limbo with it. After this I hope I can confirm you that the strong charger and original cable can recover the battery indicator.
Click to expand...
Click to collapse
Thanks for the info!
Chargers having a short-term effect sounds plausible to me.
And, so does the propensity of aging batteries to act erratically.
I guess we could be looking at the combination of both....
How often do you need to charge your Kindle?
My 4-year-old Apollo is having trouble keeping up with my
usage patterns. Some days I have to charge twice.
And, the battery indicator does behave _somewhat_ odd,
when charge is around 10% (it can jump back up to 25%, when
going from idle to heavy use [why?!?], or it can drop dead
from 7%; but sometimes it's still ticking with 0% ).
Recently, it has also started to complain about the stock
charger that came with it as being "low power"...
Hey,
A few days ago I got an update to MIUI10 Beta for my RN3 (snapdragon). After uploading the update, my phone started to charge with a maximum current of 0.4A (screen turned on, 0.6A when turned off). I decided to unlock the phone and flash LineageOS 14.1, unfortunately I still have the same problem.
Searching for topics related to this problem I found a "solution": https://forum.xda-developers.com/redmi-note-3/how-to/fix-slow-charging-t3662571
I tried - it does not work.
I tried also wipe cache/dalvik - it does not work too.
I tested on 3 chargers:
1. Apple 2.1A Out
2. Apple 1.5A Out
3. no-name 1.0A Out
-----
I used 6 cables for the test - on each of them the same.
Summary:
Before the upgrade to MIUI 10 - loading about 3h 0-100%,
After upgrade to MIUI 10 - charging about 8h 0-100%
After changing to LineageOS - charging about 8h 0-100%
Additional info:
I have this RN3 for 3 years. Maybe it's battery problem? After 3 years battery capacity has dropped from 4k to 3.2k-3.3k.
I would ask for help in solving this problem.
Sosinsky said:
Hey,
A few days ago I got an update to MIUI10 Beta for my RN3 (snapdragon). After uploading the update, my phone started to charge with a maximum current of 0.4A (screen turned on, 0.6A when turned off). I decided to unlock the phone and flash LineageOS 14.1, unfortunately I still have the same problem.
Searching for topics related to this problem I found a "solution": https://forum.xda-developers.com/redmi-note-3/how-to/fix-slow-charging-t3662571
I tried - it does not work.
I tried also wipe cache/dalvik - it does not work too.
I tested on 3 chargers:
1. Apple 2.1A Out
2. Apple 1.5A Out
3. no-name 1.0A Out
-----
I used 6 cables for the test - on each of them the same.
Summary:
Before the upgrade to MIUI 10 - loading about 3h 0-100%,
After upgrade to MIUI 10 - charging about 8h 0-100%
After changing to LineageOS - charging about 8h 0-100%
Additional info:
I have this RN3 for 3 years. Maybe it's battery problem? After 3 years battery capacity has dropped from 4k to 3.2k-3.3k.
I would ask for help in solving this problem.
Click to expand...
Click to collapse
Flash miui fastboot rom using miflash with pc .
In miflash select " clean all "and flash option. And check if same problem.
naik2902 said:
Flash miui fastboot rom using miflash with pc .
In miflash select " clean all "and flash option. And check if same problem.
Click to expand...
Click to collapse
Thanks for reply! I will do this tomorrow.
New anomaly -> RN3 is turning off at 15% or less.
naik2902 said:
Flash miui fastboot rom using miflash with pc .
In miflash select " clean all "and flash option. And check if same problem.
Click to expand...
Click to collapse
Okay, I flashed miui and... nothing. RN3 is still charging 0.41A.
Second anomaly - on Xiaomi Powerbank 10k, RN3 is charging 0.72A
Third anomaly - 11h charging from 18% to 100%.
Fourth anomaly - RN3 is charging only to 75%. I have plug off and plug on charging to continue charging more than 75%.
-------
Any suggestions? Maybe should I change the battery? Maybe this module with usb port?
Sosinsky said:
Okay, I flashed miui and... nothing. RN3 is still charging 0.41A.
Second anomaly - on Xiaomi Powerbank 10k, RN3 is charging 0.72A
Third anomaly - 11h charging from 18% to 100%.
Fourth anomaly - RN3 is charging only to 75%. I have plug off and plug on charging to continue charging more than 75%.
-------
Any suggestions? Maybe should I change the battery? Maybe this module with usb port?
Click to expand...
Click to collapse
Take ear bud and apply some spirit alcohol on itand clean ur charging port of ur phone. May be sometimes dirt or carbon or rust affects the current. Spirit alcohol or isopropanol is volatile and helps in cleaning the charging port.
If u dont have spirit alcohol then buy a small bottle from pharmacy.
I have the same problem in miui 9 then I installed lineage os but issue remains . then I tried random kernal problem solved
naik2902 said:
Take ear bud and apply some spirit alcohol on itand clean ur charging port of ur phone. May be sometimes dirt or carbon or rust affects the current. Spirit alcohol or isopropanol is volatile and helps in cleaning the charging port.
If u dont have spirit alcohol then buy a small bottle from pharmacy.
Click to expand...
Click to collapse
I tried and nothing changed.
Joyel said:
I have the same problem in miui 9 then I installed lineage os but issue remains . then I tried random kernal problem solved
Click to expand...
Click to collapse
Okay, I changed ROM to ViperOS and it was still 0.41A, so I decided to flash NitrogenOS. A little bit better. Now it's charging on 0.80A on 13% battery.
Maybe some more suggestions?
Thank you so much for replies. I really appreciate your help!
@edit
Now charging from 13%-100% take "only" 5 hours. It's bad result but it could be worse (11h on 0.4A).
@edit2
Also fifth anomaly - RN3 is randomly turning off after show a 0% battery notification. (On LineageOS 14.1).
Maybe this is problem with overheating battery. When battery is too hot system limits charging current. Did you tried measure real charging currend using eg. multimeter?
RN3SE-kate said:
Maybe this is problem with overheating battery. When battery is too hot system limits charging current. Did you tried measure real charging currend using eg. multimeter?
Click to expand...
Click to collapse
Hello there,
I have this small buddy:
https://ae01.alicdn.com/kf/HTB10vcSQVXXXXbRXXXXq6xXFXXXk.jpg
and all values which I wrote here were measured by this.
I will try thermal libs on NitrogenOS.
UPDATE
I tried thermal libs - nothing changed.
I have a notification on lock screen: "Slow charging (5hr to 100%) 715mA - 3.9V - 34*C"
Even I am facing this exact same issue after MIUI 10 update and it persists even when I changed the ROM to DotOs. The extra bit of information I can add is, the only reason for me to flash custom ROM was to get the charging done faster and immediately after flashing the ROM it did show "Charging Rapidly at 2022mA" in the lockscreen(a custom ROM feature) but only for 3 times and after that it keeps showing 0.4mA as the charge current. In my opinion we need to flash an older firmware of MIUI as MIUI might have purposefully done this in its latest update to make charging safe for old batteries (mine too is 3 years old!) and temperatures where climbing up to 45°C when it was fast charging. Any help would be highly appreciated with a thank you.
ap6709 said:
Even I am facing this exact same issue after MIUI 10 update and it persists even when I changed the ROM to DotOs. The extra bit of information I can add is, the only reason for me to flash custom ROM was to get the charging done faster and immediately after flashing the ROM it did show "Charging Rapidly at 2022mA" in the lockscreen(a custom ROM feature) but only for 3 times and after that it keeps showing 0.4mA as the charge current. In my opinion we need to flash an older firmware of MIUI as MIUI might have purposefully done this in its latest update to make charging safe for old batteries (mine too is 3 years old!) and temperatures where climbing up to 45°C when it was fast charging. Any help would be highly appreciated with a thank you.
Click to expand...
Click to collapse
Why don't you just flash a custom kernel, instead of ROMS
I tried plenty of ROMS - POSP (PIE), Bootleggers (PIE), CM14 (Nougat), LineageOS (Nougat), NitrogenOS (Nougat).
I tried few kernels - Radon (for PIE and Nougat), Shadow (Nougat), AGNi (Nougat) - For all kernels I checked few options - new thermal lib, old thermal lib, QC 2400mA, default options and other variations.
I corrupted my persist.img (all of my sensors were dead) due to flash too many of roms/kernels/stuff - had to flash new through fastboot
On all of roms/kernels/stuff I had 0.41A - Only on Bottleggers I had 0.6A and NitrogenOS 0.8A max.
edit:
Vijay G said:
Why don't you just flash a custom kernel, instead of ROMS
Click to expand...
Click to collapse
Can you tell me, which kernel would improve my charging?
update (18.03.19 3:23PM):
I changed stock kernel (ROM: LineageOS<Nougat> - 0.41A) to Badjingan pie. Actually I did it completely by accident. I thought that this is a nougat kernel. Aaaaand... it increase charging to 0.8A. Checked on USB 3.0 in laptop, Lenovo QC charger and no-name charger 2A.
Another update (18.03.19 5:27PM):
I changed the Badjingan kernel to Radon 6.3 for Nougat. Again 0.41A and nothing changed if I choosed new or old thermal but I found an option in Radom Kernel Control which is "Quick charge by USB" and when enabled, the current is changing from 0.41A to 0.80A and that's it.
Update (26.03.2019 12:20PM)
I flashed stock Miui 10.2 Global (Android 6.0.1) and charging issue still remains.
Also tried to flash thermal libs - still nothing.
I will order new battery and usb charging module.
Hello there again.
After this tries above I ordered a USB charging module in my RN3. So few minutes ago I mount it up to phone and check if charging is better. Aaand... Nothing Still 0.41A. Checked on POSP 9.0 (stock kernel). Tomorrow I'll try to change to other kernel (maybe Viper N).
Few days before, I changed ROM to Miui 10.2 Global. The charging current was aprrox 0.06A-0.2A.
The same problem
I have the same problem. As you have described, it has also happened to me after upgrading to the latest version. I have Already tried with different chargers and cables but nothing. I don't think it's a coincidence, I've already been through all the Roms that are here but I have not solved anything and the issue begins to be tired.
Thanks for reply. We will figure something out
Okay so there is an update:
I've changed (again) to MIUI 10 Beta ROM -> 0.41A
I've installed AGNI Kernel with old thermal libraries option (during installation) and... 0.66A from laptop USB 3.0 on 50% battery. The same current on MI Powerbank 20k.
The next and the last thing before throwing RN3 through window is replace the battery.
Stay tuned
I used to charge it while watching videos or playing, but today that is no longer possible. Sometimes, for example, being at 20% battery power and connecting it while I do those activities, it stays at 20% all the time or even low instead of charging.
I don't know in your case or if you've already tried it, but I've seen that the problem is only charging the phone when it's on. If I charge it when it is turned off, the charging time is normal. About 2 hours.
Clean flashed Havoc OS 9.0 Rom and Nano gapps + Thunder Kernal
Everything seems to be working fine.
Only 1 big issue is that The phone is super slow charging now,
Using a blitzwolf 2.4A/QC3.0 charger and the cable can charge at 1A or more on my Oneplus One but on the Redmi Note 3 SE (kate) seems to charge only around 0.2A
I use to be able to Charge at 2A under stock MIUI ROM
but since flashing this rom barley gets past 0.2A
Anyone know why?
Huntakillaz said:
Clean flashed Havoc OS 9.0 Rom and Nano gapps + Thunder Kernal
Everything seems to be working fine.
Only 1 big issue is that The phone is super slow charging now,
Using a blitzwolf 2.4A/QC3.0 charger and the cable can charge at 1A or more on my Oneplus One but on the Redmi Note 3 SE (kate) seems to charge only around 0.2A
I use to be able to Charge at 2A under stock MIUI ROM
but since flashing this rom barley gets past 0.2A
Anyone know why?
Click to expand...
Click to collapse
Hahha.....lol..
Get ready to go service center. Never use quick charge 2 or 3 on rn3. It will burn ur charging board.
Always use stock charger 5v 2A.
it worked fine for 3yrs, only when I changed the Rom did i encounter the slow charge issue
Huntakillaz said:
it worked fine for 3yrs, only when I changed the Rom did i encounter the slow charge issue
Click to expand...
Click to collapse
Dont use quick charger on custom roms.
Hello guys,
So the other day I was messing with thermals and I flashed a thermal that basically removes entire thermal throttling. Because of that, I was able to charge my phone at 33wat constantly for about 20 mins. The charging speed was super awesome, but I'm wondering is it safe to do so constantly? When I was back on stock settings, the charge speed would randomly fluctuate b/w 10-18 watt but with no throttling it just constantly remains on 33watt.
So again is it safe to keep charging my phone on these higher voltages constantly?
alifarhad said:
Hello guys,
So the other day I was messing with thermals and I flashed a thermal that basically removes entire thermal throttling. Because of that, I was able to charge my phone at 33wat constantly for about 20 mins. The charging speed was super awesome, but I'm wondering is it safe to do so constantly? When I was back on stock settings, the charge speed would randomly fluctuate b/w 10-18 watt but with no throttling it just constantly remains on 33watt.
So again is it safe to keep charging my phone on these higher voltages constantly?
Click to expand...
Click to collapse
Not knowing enough about this, I'd assume it's not safe and that heating of the battery would be the issue and would lead to your battery being cooked over a series of charging cycles, but I see your point temperature was not excessive (34°) - I'd advise using an app to record moment by moment charging temperature
Assuming you didn't have your phone in a pool of cooled mineral oil during charging I'd assume that you've just become a test pilot. Let us know what happens... [consider also the possibility that your house might burn down]
thesoupthief said:
Not knowing enough about this, I'd assume it's not safe and that heating of the battery would be the issue and would lead to your battery being cooked over a series of charging cycles, but I see your point temperature was not excessive (34°) - I'd advise using an app to record moment by moment charging temperature
Assuming you didn't have your phone in a pool of cooled mineral oil during charging I'd assume that you've just become a test pilot. Let us know what happens... [consider also the possibility that your house might burn down]
Click to expand...
Click to collapse
OK thanks for your insights. Yes I did some research on my own. Particularly from battery university (yes that's a thing, a whole website..) and I learned that as long as your battery temp doesn't hit 50c you can do whatever you want because in the end your phone only ever draws enough power that its circuitry was designed for. So that information was enough for me to continue my journey into hotter waters.
So far, during charging from 49% to 80% my poco only took about 17 mins to reach there and right when it reached 80c that I saw it start to throttle a bit so by the time it was 82, the watts came down to 25-28 range. So I guess that's hardware throttling in effect since I have already got the software ones removed? And anyway during these 17 mins, while the ambient temp at my place was 32c, the battery temp soared as far as 43c. I believe I would frequently hit the same temp even when I had all thermal enabled running on stock setup. So we can safely rule out that it didn't happen because of not having thermals but just because the ambaint + charging had their own way.
Lastly, I would continue doing this for few more days checking under air-conditioned room next and see how it goes. For now I'm sticking with 20-80 battery rule because that's supposed to be the safest thing in the world of li-on batteries.
Normally quickcharge will keep stuff safe so it will adjust accordingly.
If temps would get over 40-45 deg. c. over a long time it would take a hit on the 'life' of the cell.
Charging slow and between a range of 10 and 90% will help cell life for sure.
what kind of adapter were you using to get 33 watts? most i've seen on my phone is 22 or something watts
also, what font is that if you don't mind me asking
mine does 33 watts too ??
MinBCrafter said:
what kind of adapter were you using to get 33 watts? most i've seen on my phone is 22 or something watts
also, what font is that if you don't mind me asking
Click to expand...
Click to collapse
Stock adapter that comes with box. And font is from IOS. Available in handy magisk model. Search inside magisk manager.
MinBCrafter said:
mine does 33 watts too ??
Click to expand...
Click to collapse
Yep its 33watt as shown. What's your Rom + kernel setup?
alifarhad said:
Yep its 33watt as shown. What's your Rom + kernel setup?
Click to expand...
Click to collapse
Pixel Experience w/f2fs (7/22/2019) + Optimus Drunk kernel latest
MinBCrafter said:
Pixel Experience w/f2fs (7/22/2019) + Optimus Drunk kernel latest
Click to expand...
Click to collapse
Whats the deal about f2fs I keep seeing this pop every once in a while but never got enough details on it. Since you are using it, can you educate me what it's and does it even make any difference?
alifarhad said:
Whats the deal about f2fs I keep seeing this pop every once in a while but never got enough details on it. Since you are using it, can you educate me what it's and does it even make any difference?
Click to expand...
Click to collapse
It's a file system for android, and yes it does make quite a decent (not like huge) difference when you load up apps (f2fs is usually used in the /data partition) basically apps open faster and it makes the phone feels snappier.
alifarhad said:
OK thanks for your insights. Yes I did some research on my own. Particularly from battery university (yes that's a thing, a whole website..) and I learned that as long as your battery temp doesn't hit 50c you can do whatever you want because in the end your phone only ever draws enough power that its circuitry was designed for. So that information was enough for me to continue my journey into hotter waters.
So far, during charging from 49% to 80% my poco only took about 17 mins to reach there and right when it reached 80c that I saw it start to throttle a bit so by the time it was 82, the watts came down to 25-28 range. So I guess that's hardware throttling in effect since I have already got the software ones removed? And anyway during these 17 mins, while the ambient temp at my place was 32c, the battery temp soared as far as 43c. I believe I would frequently hit the same temp even when I had all thermal enabled running on stock setup. So we can safely rule out that it didn't happen because of not having thermals but just because the ambaint + charging had their own way.
Lastly, I would continue doing this for few more days checking under air-conditioned room next and see how it goes. For now I'm sticking with 20-80 battery rule because that's supposed to be the safest thing in the world of li-on batteries.
Click to expand...
Click to collapse
But, how long does it take to reach 49% from 0% or from 20% as you say you follow the 20-80 rule?
Removing thermals is not a good idea, I'm not an expert but I get more fluid experience playing CODM , capping the max speed of all proccesors to 1.7ghz , and keep the phone charging at low voltage. I can play for hours at 60fps and the battery never hits 44c. Removing thermals and processor's cap, I would have a great 15 minutes of game and then it would be very hot and hardware throttle, to the extreme of even get only 20 frames /sec or even less.
All that heat is bad for battery and the components. The battery will go bad faster, inflating in worst cases, and the IPS panel can get permanent ghosting. I know this from previous devices poco included. I do gaming for hours. Removing thermals + gaming at high brightness is bad.
unrafa said:
Removing thermals is not a good idea, I'm not an expert but I get more fluid experience playing CODM , capping the max speed of all proccesors to 1.7ghz , and keep the phone charging at low voltage. I can play for hours at 60fps and the battery never hits 44c. Removing thermals and processor's cap, I would have a great 15 minutes of game and then it would be very hot and hardware throttle, to the extreme of even get only 20 frames /sec or even less.
All that heat is bad for battery and the components. The battery will go bad faster, inflating in worst cases, and the IPS panel can get permanent ghosting. I know this from previous devices poco included. I do gaming for hours. Removing thermals + gaming at high brightness is bad.
Click to expand...
Click to collapse
Um, you don't just remove thermal limitations and charge like yesterday.
That is useless and in some cases counter-intuitive.
You highly decrease the temperature to 14 degree Celsius to 26/28 Degree Celsius and charge in that.
However as you say, if you're doing high intense activities that use a lot of hardware, which generally heats the phone, then having a heated phone for extended periods of time *might* be bad for the battery, well having any electronic device heated is bad for the internal circuitry. I have a personal experience with this.
That said, as long as you're using your phone for mild to medium intensity activities like watching multi-media applications and surfing, calling, etc removing thermals will have no significant issues and not reduce the battery life because your phone is mostly never going above 35/36 degree Celsius.
Or if you can, remove thermals whenever you're charging and put them back on whenever you're not.
what
alifarhad said:
Hello guys,
So the other day I was messing with thermals and I flashed a thermal that basically removes entire thermal throttling. Because of that, I was able to charge my phone at 33wat constantly for about 20 mins. The charging speed was super awesome, but I'm wondering is it safe to do so constantly? When I was back on stock settings, the charge speed would randomly fluctuate b/w 10-18 watt but with no throttling it just constantly remains on 33watt.
So again is it safe to keep charging my phone on these higher voltages constantly?
Click to expand...
Click to collapse
what app is that?
Fgacko said:
what
what app is that?
Click to expand...
Click to collapse
FKM. Franco Kernel Manager.
shivy25 said:
FKM. Franco Kernel Manager.
Click to expand...
Click to collapse
ah, thanks
Hi,
So I've been using an app called Battery Charge Limit from the Play Store (https://play.google.com/store/apps/details?id=com.slash.batterychargelimit) to limit my battery charging upto 80% using root access. This was to increase the longevity of the battery.
Worked fine on Oreo, but now for some reason it doesn't seem to stop the battery charging at 80% on Pie. I was wondering if anyone else has encountered this issue and has found a fix/workaround?
I know its probably better just to ask the app developers, but I was just wondering if anyone else is having this issue as I also have access to an S7 Edge on OneUI Pie and it doesn't seem to have any issues.
Thanks
DBZLegend9000 said:
Hi,
So I've been using an app called Battery Charge Limit from the Play Store (https://play.google.com/store/apps/details?id=com.slash.batterychargelimit) to limit my battery charging upto 80% using root access. This was to increase the longevity of the battery.
Worked fine on Oreo, but now for some reason it doesn't seem to stop the battery charging at 80% on Pie. I was wondering if anyone else has encountered this issue and has found a fix/workaround?
I know its probably better just to ask the app developers, but I was just wondering if anyone else is having this issue as I also have access to an S7 Edge on OneUI Pie and it doesn't seem to have any issues.
Thanks
Click to expand...
Click to collapse
The xda thread for it is here: https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Sent from my LG-US998 using Tapatalk
DBZLegend9000 said:
Hi,
So I've been using an app called Battery Charge Limit from the Play Store (https://play.google.com/store/apps/details?id=com.slash.batterychargelimit) to limit my battery charging upto 80% using root access. This was to increase the longevity of the battery.
Worked fine on Oreo, but now for some reason it doesn't seem to stop the battery charging at 80% on Pie. I was wondering if anyone else has encountered this issue and has found a fix/workaround?
I know its probably better just to ask the app developers, but I was just wondering if anyone else is having this issue as I also have access to an S7 Edge on OneUI Pie and it doesn't seem to have any issues.
Thanks
Click to expand...
Click to collapse
I do not see any sense in such charging settings, the V30 with 100% notification is still charging for 30 minutes with low current and then only reaches a physical 100% battery which is to save the battery. As the program disconnects charging at 80% it will be physical about 70% = 2/3 for battery use. You probably don't discharge the battery less than 30% because you will "damage it". Then use 1/3 charging it 3 times at the same time as I do ... So think about whether after these 4 years you won't have a more dead battery than I, kids, I charge 15> 100%.
Yes, the answer is simple, charge up to 100% and disconnect immediately, just like LG limits charging to physical 95% so that the battery does not lose capacity.
marcinb24 said:
I do not see any sense in such charging settings, the V30 with 100% notification is still charging for 30 minutes with low current and then only reaches a physical 100% battery which is to save the battery. As the program disconnects charging at 80% it will be physical about 70% = 2/3 for battery use. You probably don't discharge the battery less than 30% because you will "damage it". Then use 1/3 charging it 3 times at the same time as I do ... So think about whether after these 4 years you won't have a more dead battery than I, kids, I charge 15> 100%.
Yes, the answer is simple, charge up to 100% and disconnect immediately, just like LG limits charging to physical 95% so that the battery does not lose capacity.
Click to expand...
Click to collapse
Fair enough. I simply limit it to 80% as from what I understand the majority of battery wear happens between 80-100%, even if it is charging at a much lower voltage and current.
Even if the phone doesn't show the true values of physical charge, a physical 70% charge is enough to get me through the day and I don't worry too much about how much battery I drain so only put the phone back to charge when it's at ~5%. So only charge the phone once a day.
Even if it may/may not make a difference to longevity it's worth a shot. At best it'll improve the lifespan of the battery, at worst it'll do nothing with normal degradation.
Maybe in a year or so when 80% charge can't get me through the day I might drop the limit. For now it seems worth a try.
DBZLegend9000 said:
Fair enough. I simply limit it to 80% as from what I understand the majority of battery wear happens between 80-100%, even if it is charging at a much lower voltage and current.
Even if the phone doesn't show the true values of physical charge, a physical 70% charge is enough to get me through the day and I don't worry too much about how much battery I drain so only put the phone back to charge when it's at ~5%. So only charge the phone once a day.
Even if it may/may not make a difference to longevity it's worth a shot. At best it'll improve the lifespan of the battery, at worst it'll do nothing with normal degradation.
Maybe in a year or so when 80% charge can't get me through the day I might drop the limit. For now it seems worth a try.
Click to expand...
Click to collapse
Just for your information, deep discharges are also not very good for Lion batteries. Discharging to 5% regularly is as bad, if not worse, than charging to 100%. The optimal is to always keep the battery level between 40%-80%.
I am not so sure if that will make any visible real world difference since most people don't tend to keep their phones for too long. And since that limits the effective battery capacity too much, I would suggest that you don't worry too much about charging/discharging too much.
DBZLegend9000 said:
Hi,
So I've been using an app called Battery Charge Limit from the Play Store (https://play.google.com/store/apps/details?id=com.slash.batterychargelimit) to limit my battery charging upto 80% using root access. This was to increase the longevity of the battery.
Worked fine on Oreo, but now for some reason it doesn't seem to stop the battery charging at 80% on Pie. I was wondering if anyone else has encountered this issue and has found a fix/workaround?
I know its probably better just to ask the app developers, but I was just wondering if anyone else is having this issue as I also have access to an S7 Edge on OneUI Pie and it doesn't seem to have any issues.
Thanks
Click to expand...
Click to collapse
To answer your original question, the same feature works as intended on a different app (AccuBattery) on my phone, stock unrooted open EU H93030b. So it looks like your problem is not the OS but the app.
PIntus_aleborn said:
Just for your information, deep discharges are also not very good for Lion batteries. Discharging to 5% regularly is as bad, if not worse, than charging to 100%. The optimal is to always keep the battery level between 40%-80%.
I am not so sure if that will make any visible real world difference since most people don't tend to keep their phones for too long. And since that limits the effective battery capacity too much, I would suggest that you don't worry too much about charging/discharging too much.
Click to expand...
Click to collapse
Yeah I am aware that discharging to 5% can be just as bad for the battery. But even if I charged to 100% I would still use the phone till there was only 5% left. So I just thought might as well try to limit the charging and see if it makes a difference on the long run, since 80% gets me through a the day anyway.
PIntus_aleborn said:
To answer your original question, the same feature works as intended on a different app (AccuBattery) on my phone, stock unrooted open EU H93030b. So it looks like your problem is not the OS but the app.
Click to expand...
Click to collapse
Thanks for your help! I did try out Accubattery and yes it detects when the battery is at 80%. Just wish it could set limits with root access as well.
In any case, I seem to have found a solution now. There's a Magisk module called Advanced Charging Control (ACC). This seems to work well and limits charging to 80%. It also has a companion app that you can use to set your own preferences and limits.
I've linked the relevant thread below, might be useful to others.
https://forum.xda-developers.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427/amp/
DBZLegend9000 said:
Yeah I am aware that discharging to 5% can be just as bad for the battery. But even if I charged to 100% I would still use the phone till there was only 5% left. So I just thought might as well try to limit the charging and see if it makes a difference on the long run, since 80% gets me through a the day anyway.
Click to expand...
Click to collapse
Your doing more worse then good letting the phone go to 5%. That app will not do ANYTHING for you.
Sent from my LG-H932 using XDA Labs
I find ACC works well at stopping the chargeing at a certain % level.
Hoiwever then while still connected to usb it draws power from the battery - not good.
Battery charge Limit on Oreo stoped charging and used then power from usbb onwards while still connected.
I wonder how ACC stops the charging on Pie, i.e. with what control file. Has anyone got an idea?
I foudn out that the switch is /sys/devices/platform/lge-unified-nodes/charging_enabled. This starts/stops the chargi8ng.
Unfortunately, on Pie, when this is set to disabled from then on power ist not drawn from the charger but from the battery.
Is there any other switch / wax to prevent this?
Ich want charging to be stopped and from then on power to be taken from the charger while connected to it.
Here are the paths to the CTRL files that I've found to work with the two ROMs that I've used recently:
Havoc-OS wired and wireless: /sys/devices/platform/lge-unified-nodes/charging_enable (no 'd' on the end, unlike what bladecgn gave)
Lineage OS wired: /sys/class/power_supply/battery/charging_enabled
Lineage OS wireless: /sys/class/power_supply/dc-wireless/charging_enabled
One quirk that I've noticed is that, on wireless, the app ignores the "Recharge below" setting and starts recharging as soon as the percentage drops just 1% below the max (ex. if the max is 80% and the charge drops to 79%, it'll immediately recharge back to 80%, even if "Recharge below" is set at 76%).
For the record, the ROM that I'm using is LineageOS 17.1, so the app definitely still works on Android 10.
bladecgn said:
I foudn out that the switch is /sys/devices/platform/lge-unified-nodes/charging_enabled. This starts/stops the chargi8ng.
Unfortunately, on Pie, when this is set to disabled from then on power ist not drawn from the charger but from the battery.
Is there any other switch / wax to prevent this?
Ich want charging to be stopped and from then on power to be taken from the charger while connected to it.
Click to expand...
Click to collapse
Were you able to figure out how to use only power from the charger instead of the battery, @bladecgn?
Osprey00 said:
Here are the paths to the CTRL files that I've found to work with the two ROMs that I've used recently:
Havoc-OS wired and wireless: /sys/devices/platform/lge-unified-nodes/charging_enable (no 'd' on the end, unlike what bladecgn gave)
Lineage OS wired: /sys/class/power_supply/battery/charging_enabled
Lineage OS wireless: /sys/class/power_supply/dc-wireless/charging_enabled
Click to expand...
Click to collapse
Stock Pie doesn't have the /sys/class/power_supply/battery/charging_enabled file, but it does have /sys/class/power_supply/battery/battery_charging_enabled. Would that work?
aospray said:
Stock Pie doesn't have the /sys/class/power_supply/battery/charging_enabled file, but it does have /sys/class/power_supply/battery/battery_charging_enabled. Would that work?
Click to expand...
Click to collapse
I don't know. You'll just have to try. It's a process of trial and error to find which path works with which ROMs.
I've been experiencing this for a wile now. In the beginning, when the battery hit 10%, my Le Max 2 would get really slow, basically unusable. Now it's staring around 15%. I've tried multiple ROMs and it persists through all of them. Does anyone share this problem, or know if there's a fix to it?
joaoVi said:
I've been experiencing this for a wile now. In the beginning, when the battery hit 10%, my Le Max 2 would get really slow, basically unusable. Now it's staring around 15%. I've tried multiple ROMs and it persists through all of them. Does anyone share this problem, or know if there's a fix to it?
Click to expand...
Click to collapse
What rom do you use?
Rodcoco said:
What rom do you use?
Click to expand...
Click to collapse
I'm using Lineage OS 17.1 august 28
Heyyo @joaoVi, this is the expected behaviour as Qualcomm intended it to be. It is NOT recommended to let your battery drain below 10%. Qualcomm has a safety put in place in the kernel that disables the big cores, so that only the little cores are running. This is to try and prevent further battery wear.
The safest ranges for a battery is 40% to 80%. Anything higher or lower will cause extra wear to the battery charge cycles which is why I also never recommend charging a device with a poly-lithium battery overnight, as charging it to 100% and then letting it sit at 100% causes a lot of battery wear.
Linus Tech Tips has a good video on this subject too
It's winter and the 4 year old battery cannot supply enough voltage to the CPU so the big cores turn off. You can verify this behavior by CPU monitoring quick settings tile built in most ROMs
It gets more difficult for a battery to supply higher energy at lower tempreatures (winter!)