Develop Bugs

Charging while phone is off?

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 =)

[Q] Odd Battery / Boot Issue

Running a rooted, unlocked, EVO 4g running CM 7.2.0 Rom
I've seen this same behavior twice. Once yesterday and once today.
Yesterday
Phone was plugged into usb port of laptop charging (around 50% at the time) was running Pandora and Wifi Tether (build into ROM). Phone crashes to off, no reboot attempt. Attempt to power phone back on yields no result (no lights, no screen ... nothing). Remove battery for 10-15 mins, insert and hook up to a AC charger and hit power button. Red light starts flashing, I wait for it to turn solid and try booting again. This time phone turns on and hangs at white HTC EVO splash screen. I then boot phone into custom recovery image, clear cache partition, and reboot. Phone boots ROM fully, batter reads 50% still and works fine until the next day.
Today
Phone was plugged in running Wifi tether, but not Pandora. Same behavior in crashing, removing battery, hooking up ac charger etc... this time however it didn't hang on the HTC EVO splash screen, and boots the ROM. However, the battery no reads 0% and wasn't charging. Removing the AC charger causes phone to shutdown. Reboot rom again, still read 0%, but let it sit for a few minutes and begins to charge. Appears to be charging fine and holds its own without the ac charger. **Note - battery was also around 50% or so when it crashed out
Questions:
Whats the root here? Bad battery? Bad rom? Thoughts on root cause would help if anyone has gone through this.
Thanks!

I'd say a combination of battery and ROM. Try flashing a new ROM and if it continues, try a new battery.

Cyanogen rom - not charging after drains out

I have note 2 with twrp recovery installed. I flashed cyanogenmod 10.1.3 and i have 2 problems:
-1: after the battery drains completely, i plug the phone and the battery shows up but it doesn't fill up (no animation, just an empty battery that normally would fill up). I long press the power button but the phone doesn't turn on. I have to do the 3 button combo, to start into recovery so i can turn it on from there. So i can see that it charges but if the battery completely died, i cannot start the phone normally.
-2: i have 16 gb but the phone has only 10 available, total space is 10,46 to be exact. I know that it should have 13,... But i think i have to format it somehow because part of the memory is occupied like i was using a samsung rom.
Any solutions?
Thanks !

serpentetdr said:
I have note 2 with twrp recovery installed. I flashed cyanogenmod 10.1.3 and i have 2 problems:
-1: after the battery drains completely, i plug the phone and the battery shows up but it doesn't fill up (no animation, just an empty battery that normally would fill up). I long press the power button but the phone doesn't turn on. I have to do the 3 button combo, to start into recovery so i can turn it on from there. So i can see that it charges but if the battery completely died, i cannot start the phone normally.
-2: i have 16 gb but the phone has only 10 available, total space is 10,46 to be exact. I know that it should have 13,... But i think i have to format it somehow because part of the memory is occupied like i was using a samsung rom.
Any solutions?
Thanks !
Click to expand...
Click to collapse
1) It's a known issue with CM/AOSP roms that when your charge your phone by powering it off or in your case battery was completely that charging animations dont show the battery charging just a stuck round circle in the middle but your phone is charging fine.So just let it charge for 10 mins or so to gain enough charge to boot into your system.To boot your phone from this charging mode unplug the charging cable from the phone and press and hold the power button for 10 seconds or more until screen goes black and you'll see your samsung note 2 logo,let the system boot and plug your charger back in.
2)Samsung by default has implemented 5.4 gb space out of 16gb to run the system.There's a MOD available in note II android development that decreases system partition by 1.9 gb so after flashing that mod you get 12+gb of free space.I'll re direct you to the thread so you can take a look at do the exact steps as described the person posting it.
How to gain 1.9gb

[Q] New G3, cannot boot/restart without charger

I've bought an LG G3 today. Everything worked fine at first, but then when I restarted it for the first time this happened:
Device boots
Lockscreen is visible
Asks for pincode -> I enter correct pin
Few seconds later screen turns black..
After the screen turns black, the only thing I can do is remove battery and try to boot again. Or plug it in to the charger.
If I plug it in to the charger it shows a battery icon in the middle of the screen and when I press the power button it boots, and does not shut down after it's fully booted.
I've read the other shutdown thread but it looks like that is not entirely the same issue I'm facing?

Have you customized anything? Sounds to me like either a bad battery or a faulty device. Take it back to the store.

seboj said:
Have you customized anything? Sounds to me like either a bad battery or a faulty device. Take it back to the store.
Click to expand...
Click to collapse
It's rooted with TowelRoot and exposed installed, just installed - nothing changed yet. Today I was not able to reproduce the issue when rebooting. Although it did shutdown when I just tapped send in the default messaging app.. Couldn't get it back on without plugging it in to the charger. Battery level was around 25%.. Removing the battery also does the trick.. So it looks like it totally freezes..
When I got the device, I immediately started configuring and testing it and only charged fully when battery level was +- 25% (started out at 45%).

NtotheO said:
It's rooted with TowelRoot and exposed installed, just installed - nothing changed yet. Today I was not able to reproduce the issue when rebooting. Although it did shutdown when I just tapped send in the default messaging app.. Couldn't get it back on without plugging it in to the charger. Battery level was around 25%.. Removing the battery also does the trick.. So it looks like it totally freezes..
When I got the device, I immediately started configuring and testing it and only charged fully when battery level was +- 25% (started out at 45%).
Click to expand...
Click to collapse
Definitely nothing normal about that. Return the device for a new one.

How do I force my Lineageos device to shutdown at 10% battery level?

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.