every time I turn off or reboot my phone, when it boots again it shows a battery charge way lower then before, most of times it doesnt even boot due to low battery although it was 100% charged before. to "fix" this I need to turn on my phone with the charging cable plugged in. Is there a real fix to this problem?
Are you using a custom rom? I can report I'm experiencing the same with Lineage OS 18.1. Don't know about any solutions though
Related
Hi,
Yesterday I came across strange issue. In WinMo, when the phone was off it was charging normally untill the battery was fully charged...
After Flashing Android to NAND I can not do that. It seems to be charging (orange LED is on) for about 10 sec. and than the Display blinks with white light and the phone dies completely.
The only thing you can do after that is to pull out the battery and put it back. Than you can turn the phone on and charge as usually.
What is that issues origin? Battery driver? Or another thingie in Firmware? It seems to be quite strange, that it lights the display even with the phone being off...
a.s.j said:
Hi,
Yesterday I came across strange issue. In WinMo, when the phone was off it was charging normally untill the battery was fully charged...
After Flashing Android to NAND I can not do that. It seems to be charging (orange LED is on) for about 10 sec. and than the Display blinks with white light and the phone dies completely.
The only thing you can do after that is to pull out the battery and put it back. Than you can turn the phone on and charge as usually.
What is that issues origin? Battery driver? Or another thingie in Firmware? It seems to be quite strange, that it lights the display even with the phone being off...
Click to expand...
Click to collapse
i have this problem too
a.s.j said:
Hi,
Yesterday I came across strange issue. In WinMo, when the phone was off it was charging normally untill the battery was fully charged...
After Flashing Android to NAND I can not do that. It seems to be charging (orange LED is on) for about 10 sec. and than the Display blinks with white light and the phone dies completely.
The only thing you can do after that is to pull out the battery and put it back. Than you can turn the phone on and charge as usually.
What is that issues origin? Battery driver? Or another thingie in Firmware? It seems to be quite strange, that it lights the display even with the phone being off...
Click to expand...
Click to collapse
My Kaiser does the exact same thing, and what it is, is for some reason the phone is booting back up. I came across this the other day, and my phone did the exact same thing described, and not sure what I did, but I managed to turn on the screen and Android was booted up to the lock screen.
It's even done it when I plug the phone into A/C power without the battery even connected.
so here is why it happens, basicly what would happen is in WinMo when the phone would turn off and boot into a charge loop and it would charge and shut off when finished our kernel doesnt have this built into it so it just boots like normal when power is applied
thoughtlesskyle said:
so here is why it happens, basicly what would happen is in WinMo when the phone would turn off and boot into a charge loop and it would charge and shut off when finished our kernel doesnt have this built into it so it just boots like normal when power is applied
Click to expand...
Click to collapse
yup... happens to all of us, its not a big deal... there are a lot of worse problems devs are trying to solve... maybe whn they reach a point where the kernel is more stable they should pay attention to the details like this (and the camera driver, camcoder... etc)
thoughtlesskyle said:
so here is why it happens, basicly what would happen is in WinMo when the phone would turn off and boot into a charge loop and it would charge and shut off when finished our kernel doesnt have this built into it so it just boots like normal when power is applied
Click to expand...
Click to collapse
Well that answers my question... Yah knew it was something inside the kernel, just didn't know if it was a bug, or something that wasn't implemented yet.
Of course this is low priority task but I just wanted to have that confirmed to know, that my oldie holdie is not broken or what
Quick question:
How old is your kaiser and/or battery ?
About 5 years with original battery
Sent from my Full Android on Kaiser using XDA App
It used to be that if Linux NBH was flashed, the phone wouldn't charge at all when off. Then somebody (dzo I believe) added code to the kernel so that the phone turns on when it is plugged in, so that it will charge. That used to work, with a full complete boot. Now, as you say, the phone tries to wake up but doesn't really make it. Maybe we should look into that, we should be able to fix that, maybe by looking carefully at the git logs for the past six months or so.
There are bigger problems, like data reliability, but if somebody wants a problem in the kernel that they can study and perhaps fix, this is a good one to start with.
To correctly charge the battery system need to be on so i can do this:
start kernel
in initrd:
if it found the power connected then the phone wait for power button (trying the sleep mode)
else
start the system
i need some testing to do it.
Windows do quite the same thing.
l1q1d said:
To correctly charge the battery system need to be on so i can do this:
start kernel
in initrd:
if it found the power connected then the phone wait for power button (trying the sleep mode)
else
start the system
i need some testing to do it.
Windows do quite the same thing.
Click to expand...
Click to collapse
If only the real code was as easy as the pseudocode =)
hello
i had resurrection ROM and suddenly the phone turn off battery turn from 50 to 7 and turn off again and didn't stop unless i connect power cable
i format the device to ARHD ROM and its still doing it
but the problem is when im in TWRP it doesn't turn off with out power cable so it probably not the battery
any help please what it can be?
I have come across this problem of rapid battery loss but not as severe as yours, it took only 9 minutes for my whole battery to drain from 100 to 10. But i also did switch roms and even recovered stock firmware but nothing seemed to work. After a while, i kept switching and switching roms and eventually, the power issue stopped, i had no idea what happened. Is it because i don't use my phone often Anyways a battery replacement would probably be necessary if the problem still occurs. This power issue is inconvenient and would like to know if someone else would be able to know of a better solution.
Hi, I've been trying to find out how to fix an issue with my SIII. My phone will turn on when it has full charge and will turn off after like 3 minutes, then turn off and show my phone charging at about 90%.
When i turn it back on it will turn back off at the spash screen or even when when it gets to the home screen. If i turn on the phone in recovery however, it will stay until it reaches 0% charge. I have hard reset the phone and nothing
I've even tried flashing different roms and i still encounter the same issues. I can only get the phone to turn on to the OS and run perfectly for a few minutes when the charge is at 100%. even with the charger connected... rarely it will stay on for a very long time until i try to do alot of things with it.
Anyone ever encouter this issue or can help guide me on how to fix it?
Thanks in advance
Hi
I flashed lineage 14.1 OS over the manufacturers stock ROM about 3 weeks ago. The Lineage ROM had issues BUT the battery was still charging normally. (Worth noting that the battery was also charging perfectly fine on when the manufacturers Rom was still installed). Seeing as Lineage 14.1 had a host of other issues, I then flashed AOKP's version of Pie with GAPPS Micro. At first, the battery would charge until 53%. However after it drained to 0%, it has not charged properly since. (6 days or so).
A) Battery is about 6 months old, so relatively new
B) non-charge problem started with installation of AOKP version of Pie
C) I have used a couple of battery health apps,which reveal the following:-
c.1) Battery health is fine
c2) Voltage 3.5V (essentially 0% charge)
c3) amperage averaging around 30mA
c4) Battery Manager and other apps state that the battery is "connected but not able to charge"
D) I have tried deleting the batterystats.bin file, which had no affect
E) I have tried using recalibration apps off Google Play Store with no affect.
F) I have cleaned the USB port and tried different cables, also with no affect.
I'm going to try flash another OS shortly. Other than that my last idea is to purchase a new battery. HOWEVER just thought I'd ask if anyone has any other bright ideas as to what might have happened to a perfectly functional battery? Another thing worth mentioning is that the power button on this device doesn't 'click' anymore. So one cannot feel that the button has been pressed, you have to press harder to ensure that the device powers on. It was like that for a long time before this battery problem started but thought I'd mention it. Can a faulty power button be causing a massive power drain on the battery OR be stopping it from charging?
EDIT - when the phone is off and plugged in to the charger, the battery icon shows it as "charging". However if I leave it for a few hours and switch the phone on again, it still reflects as 0% charged and only switches on with the power cable attached. Also I cannot get into recovery mode, after shutting down, unless I leave the phone plugged in and "charging" for a while. It's like recovery mode needs at least some power from the battery.
Debcal said:
Hi
I flashed lineage 14.1 OS over the manufacturers stock ROM about 3 weeks ago. The Lineage ROM had issues BUT the battery was still charging normally. (Worth noting that the battery was also charging perfectly fine on when the manufacturers Rom was still installed). Seeing as Lineage 14.1 had a host of other issues, I then flashed AOKP's version of Pie with GAPPS Micro. At first, the battery would charge until 53%. However after it drained to 0%, it has not charged properly since. (6 days or so).
A) Battery is about 6 months old, so relatively new
B) non-charge problem started with installation of AOKP version of Pie
C) I have used a couple of battery health apps,which reveal the following:-
c.1) Battery health is fine
c2) Voltage 3.5V (essentially 0% charge)
c3) amperage averaging around 30mA
c4) Battery Manager and other apps state that the battery is "connected but not able to charge"
D) I have tried deleting the batterystats.bin file, which had no affect
E) I have tried using recalibration apps off Google Play Store with no affect.
F) I have cleaned the USB port and tried different cables, also with no affect.
I'm going to try flash another OS shortly. Other than that my last idea is to purchase a new battery. HOWEVER just thought I'd ask if anyone has any other bright ideas as to what might have happened to a perfectly functional battery? Another thing worth mentioning is that the power button on this device doesn't 'click' anymore. So one cannot feel that the button has been pressed, you have to press harder to ensure that the device powers on. It was like that for a long time before this battery problem started but thought I'd mention it. Can a faulty power button be causing a massive power drain on the battery OR be stopping it from charging?
EDIT - when the phone is off and plugged in to the charger, the battery icon shows it as "charging". However if I leave it for a few hours and switch the phone on again, it still reflects as 0% charged and only switches on with the power cable attached. Also I cannot get into recovery mode, after shutting down, unless I leave the phone plugged in and "charging" for a while. It's like recovery mode needs at least some power from the battery.
Click to expand...
Click to collapse
Does anyone know of a battery app/ software that one can run in recovery mode OR prior to booting? I'm wondering if this battery problem is software related or hardware related.
Debcal said:
Does anyone know of a battery app/ software that one can run in recovery mode OR prior to booting? I'm wondering if this battery problem is software related or hardware related.
Click to expand...
Click to collapse
Now, it appears, I cannot even boot into TWRP recovery. I suspect the non-charging battery is the problem.
Debcal said:
Now, it appears, I cannot even boot into TWRP recovery. I suspect the non-charging battery is the problem.
Click to expand...
Click to collapse
You won't believe it!!! After trying every solution known to man, turns out that the battery just doesn't sit snugly in the phone, so it doesn't make good contact. ???*♂??
Charging now that I manually pushed it up against the contacts.
My Galaxy tab S 8.4 wifi (klimtwifi) doesn't turn back on most of the time if the device runs out of battery completely and shutdown.
Even if I put it for charging overnight, it won't start charging at all and doesn't turn back on when i press the power button. When I try charging say 30 times, in the end, it may charge and turn back on. It's very difficult to go through the same process every time battery completely drains off.
When I had this problem it was running official Samsung stock rom, I then installed LineageOS 14.1 and I still have the same problem.
Question
1. Is this a hardware problem? What could be a hardware fix? Change battery? Has anyone managed to fix this problem?
2. For now, I would like to fix the problem by using software. So can I make lineageos 14.1 to force shutdown every time charge reaches 10% instead of letting it drain completely? This way I can put it on charge and restart the device every time.
mrcet007 said:
My Galaxy tab S 8.4 wifi (klimtwifi) doesn't turn back on most of the time if the device runs out of battery completely and shutdown.
Even if I put it for charging overnight, it won't start charging at all and doesn't turn back on when i press the power button. When I try charging say 30 times, in the end, it may charge and turn back on. It's very difficult to go through the same process every time battery completely drains off.
When I had this problem it was running official Samsung stock rom, I then installed LineageOS 14.1 and I still have the same problem.
Question
1. Is this a hardware problem? What could be a hardware fix? Change battery? Has anyone managed to fix this problem?
2. For now, I would like to fix the problem by using software. So can I make lineageos 14.1 to force shutdown every time charge reaches 10% instead of letting it drain completely? This way I can put it on charge and restart the device every time.
Click to expand...
Click to collapse
Maybe you don't give the device enough time for charging. Buy an usb ampere meter to see device charges without showing any reaction.