Develop Bugs

[Q] Battery draining after powering down

Hello All
Im powering down my phone at night (quick boot enabled) & when i wake up in the morning the battery is completely drained. There is normally at least half a charge left before i power down.
This has only just happened the past few days. The phone is around 2 months old.
Any ideas ? Has my battery become faulty ? Should i return the phone ?
Thanks.

Sounds like a hardware fault probably the battery. How did you charge the phone normally?
Try taking the battery out, see if it loses charge after same amount of time.
Sent from my Desire HD using XDA App

I agree with sengork.
Powerdown should use only a few microamps.

sengork said:
Sounds like a hardware fault probably the battery. How did you charge the phone normally?
Try taking the battery out, see if it loses charge after same amount of time.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Thanks for the reply
I normally charge via the mains, occasionally via usb.
Its only the last couple days its happened.
Will try taking the battery out at night & see what happens.

Normally charged the battery whilst the phone was off?
Sent from my Desire HD using XDA App

sengork said:
Normally charged the battery whilst the phone was off?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
How i charge my phone varies - sometimes i will charge via the mains with either the phone still on or off at night, sometimes with the phone on via usb. I've never had a problem with regards to charging the battery.
I always turn the phone off at night (with quick boot enabled as i said) but the past 2 days, with the battery at least half full, the battery has completely drained by the morning.

Hi,
Try with and without fast boot and see if you yield any different results, I would tend to leave fast boot off if your leaving it off for a prolonged amount of time as the phone doesn't completely shut down.
Also there could be an app draining it too, so u could get autostarts and kill any unwanted apps from starting up when certain criteria are met, like when you switch your screen off, some apps are activated, i know kakao chat does that, even if it doesn't help the prob it's still a good app to have to kill apps from starting when you don't want them.
Let us know how u get on.
PS: Are you using an overvolted kernel ? Maybe knock it down to stock to see if that helps, just to test and then knock it back up when you know what the problem is.

This happened to me on my old phone. Turned out to be a problem with a torn USB cable

Well, took the battery out last night before bed with half power remaining & this morning...re inserted battery & no change at all - so i guess the battery is not faulty.
I am planning on turning off fast boot tonight, powering down the phone & see'ing what sort of state the battery is in tomorrow morning.
Thanks all for the replies so far.

mcstone said:
Hello All
Im powering down my phone at night (quick boot enabled) & when i wake up in the morning the battery is completely drained.
Click to expand...
Click to collapse
I was having almost the exact same problem. Phone seemed to drain about 30 - 40 % overnight ( with phone off - fastboot on ).
Anyway I turned off Fastboot and switched off the phone and went to bed last night with about 20% battery and woke up this morning and still had 20%.
I'm not sure how Fastboot is supposed to work but turning it off seems to have solved the problem. It's not really a big loss anyway.
Thanks.

Interesting thread.
What are the benefits of fastboot anyway?
I never had it on my Hero and haven't tired it on my DHD as I've been too busy flashing ROMs since I got it!

Where can I switch of fast boot? I'm on stock rom 1.72. Searched my phone but no luck in finding it...
Sent from my Desire HD using XDA App

KevinNolan said:
Where can I switch of fast boot? I'm on stock rom 1.72. Searched my phone but no luck in finding it...
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Menu > Applications

CitizenLee said:
What are the benefits of fastboot anyway?
Click to expand...
Click to collapse
Other than stating the obvious ( i.e. the phone boots faster ) I don't think there is any other advantage. I think it is sort of similar to putting your computer ( if you are using Windows ) into Hibernate rather than shutting down completely.
Anyway there obviously was some sort of conflict with another app as a friend ( and many other users I'm sure ) with a Desire HD uses Fastboot without any overnight battery drain. Anyway I can live without it ( didn't have it on my last phone - a Motorola Milestone ).
It is odd that the battery drained more when the phone was off overnight than it would have done being left on overnight ( just with the screen off doing nothing ).
Anyway as I said - no big deal - and I certainly can't be bothered to uninstall each app one by one until I find the one responsable.
Cheers.

Haha, yeah a faster boot time was the obvious one but I was wondering if that was all.
I have it unticked anyway, and very rarely ever turn my phone off.
Anyway, I hope you manage to fix your problem

CitizenLee said:
Anyway, I hope you manage to fix your problem
Click to expand...
Click to collapse
Thanks - as I said above turning off Fastboot seems to have fixed the issue for me. I'm too lazy (!) to find out what about leaving Fastboot on caused the battery drain but as it is a feature I can live without I'll just live with the mystery!!
Cheers.

[Q] Boot on power: power on when plug in USB

Hello!
Is it possible to change some setting so the DInc will power on when the usb is plugged in (connected to a charger or a PC)? The original Motorola Droid had this feature.
I have an application where I would like to leave a DInc unattended with an extra battery, DC-DC converter, solar charge controller, and solar panel. The setup can last for a few days with the extra battery and forever when sunny most of the time. If it is cloudy/rainy for too long, the system will loose power and the phone will shut off. Eventually when the sun comes back the batteries charge and the system should come back on, but it will not since the phone will not boot.
Is the boot on power feature possibly handled by the boot rom, the boot loader, or the kernel? Is there some setting for hboot or in the nv.img or somewhere that would instruct the phone to boot when plugged in? I've work with single board computers with this sort of feature... usually set in the bootldr or the bios (some PC's even have it).
I suspect it must be possible on many phones. Some other phones (Droid X, Samsung Galaxy S) I have run animations when the phone is powered off but plugged into a charger, so there is some code running somewhere. What would it take to make this code boot the phone?
I have searched and only found people wanting to turn off this feature on the Motorola Droid. Where else might I ask this question or search for the answer?
Thank you!

Our dincs do have this feature.... have you tried it? When I plug mine in when its dead but not wherethe led us flashing it will boot
If the led us flashing that means the battery is too low and it won't even try to boot.
Maybe your running it too dead so it won't boot
Sent from my Incredible using XDA App

superchilpil said:
Our dincs do have this feature.... have you tried it? When I plug mine in when its dead but not wherethe led us flashing it will boot
If the led us flashing that means the battery is too low and it won't even try to boot.
Maybe your running it too dead so it won't boot
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Hi! Thank you for your response.
Mine does not power on when I plug it in. Here is how I tested this:
- Full battery
- Power off phone
- Plug into charger or plug into PC
- Phone does not turn on
I also tried it with a somewhat used battery and an almost dead battery.

__martin__ said:
Hi! Thank you for your response.
Mine does not power on when I plug it in. Here is how I tested this:
- Full battery
- Power off phone
- Plug into charger or plug into PC
- Phone does not turn on
I also tried it with a somewhat used battery and an almost dead battery.
Click to expand...
Click to collapse
Thats normal, the DInc doesn't have this feature... I don't recall the OG droid having it either.. then again I traded it for an eris after a week. lol

ACD168 said:
Thats normal, the DInc doesn't have this feature... I don't recall the OG droid having it either.. then again I traded it for an eris after a week. lol
Click to expand...
Click to collapse
So yes, it is clear that the current state of the phone does not support this. Maybe superchilpil misunderstood my question.
Sorry to be so persistent. A clearer way to ask my question is if the hardware support this and if a modification to the boot loader or kernel could enable this.
Is there a better place to ask this sort of question in general for Android phones? There is an android-internals mailing list on google groups but it seems dead.
Thanks again!

[Q] Unusable in car for navigation/black box?

Hi,
whenever I use navigation or a black box recorder (tried several) in car, phone gets really hot, stops charging and will in fact discharge even when plugged in (tried 2 different chargers - 1A and 2A, no change).
I wonder if this will ever be solved? It can't navigate for more than 2 hours straight (I got 25% off my battery on a 30 minute trip!) which makes it unusable as a navigation. And usually, when you are done driving, you want your phone ready and charged, not on the verge of shutting down.
Anybody else seeing this? I noticed a lot of "overheating" threads, but those were mostly gamers. I don't think I'm asking much when I want to actually use it in car!
So what's your experience? I should note it's quite warm here nowadays.
I got a white version exactly for the reason of not getting that hot in sunlight - byt my black iPhone could keep going unless I was doing something really crazy - it did overheat on me, but usually turning AC on did the trick. With One X it's another story...

Yes, the same here. It's very disappoint behaviour and I really don't know any solution.
Simply sad, HTC One X is unusable for GPS navigation. Sad, but true.

The battery is limited to 1a so 2a won't charge faster also charging and doing stuff makes the phone hot, you'll know when its to hot while on charge as the notification flashes red and green.
If your rooted mount your system as r/w and go to /sys/kernel/debug/tegra_hotplug open max_cpu and change it from 4 to 2 and save, that will make your phone only use two cores till you reboot. That should help with overheating.
Sent from my HTC One X using xda premium

Do any of you think that there will be a fix in the future? Or is this a limitation of the phone.
Like you have said, the battery actually loses charge when plugged into the charger at full brightness with an intensive app open.
It takes about 4-5 hours just to charge the thing with the phone on but screen off, double that if you're actually using the phone.

ahmadcentral said:
Do any of you think that there will be a fix in the future? Or is this a limitation of the phone.
Like you have said, the battery actually loses charge when plugged into the charger at full brightness with an intensive app open.
It takes about 4-5 hours just to charge the thing with the phone on but screen off, double that if you're actually using the phone.
Click to expand...
Click to collapse
when you put power into a battery it heats up, when you run apps and are using 4 cores it heats up, battery + cpu = over heat
the best way to help it is to disable 2 cores and run it as a dual core.
their might be a fix if people complain to HTC where they limit the phone to 2 or 1 cores while charging.
you could mount a USB powered fan behind the phone, i've done this when bench marking while on charge and it was sitting at 22 C, i was trying to beat my friend's HOX beanch lol cooler = better marks, boosted my score on antutu from 10.4 k to 11.4 k.

treebill said:
The battery is limited to 1a so 2a won't charge faster also charging and doing stuff makes the phone hot, you'll know when its to hot while on charge as the notification flashes red and green.
If your rooted mount your system as r/w and go to /sys/kernel/debug/tegra_hotplug open max_cpu and change it from 4 to 2 and save, that will make your phone only use two cores till you reboot. That should help with overheating.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks, didn't think of that and I will try it.
I upgraded my charger because it kept saying that input current is not enough to charge, doesn't do that anymore with 2A. It's possible my 1A charger didn't actually provide 1A...
But even then, this is not really a solution. I have never seen a phone (or notebook, netbook, tablet) that was not able to keep running 100% for infinite amount of time when plugged in. If it overheats so badly it doesn't hold the charge then it's a clear defect (by design?).
So unless this is solved I probably will demand it be "repaired" under warranty (so I guess they'll try swapping it at which point I'll get my money back).

zvieratko said:
Thanks, didn't think of that and I will try it.
I upgraded my charger because it kept saying that input current is not enough to charge, doesn't do that anymore with 2A. It's possible my 1A charger didn't actually provide 1A...
But even then, this is not really a solution. I have never seen a phone (or notebook, netbook, tablet) that was not able to keep running 100% for infinite amount of time when plugged in. If it overheats so badly it doesn't hold the charge then it's a clear defect (by design?).
So unless this is solved I probably will demand it be "repaired" under warranty (so I guess they'll try swapping it at which point I'll get my money back).
Click to expand...
Click to collapse
I have only had my phone overheat once, was a hot room on charge and was using a saga emulator lol. Most of the time it sits around 48c when playing games on charge.
Sent from my HTC One X using xda premium

treebill said:
The battery is limited to 1a so 2a won't charge faster also charging and doing stuff makes the phone hot, you'll know when its to hot while on charge as the notification flashes red and green.
If your rooted mount your system as r/w and go to /sys/kernel/debug/tegra_hotplug open max_cpu and change it from 4 to 2 and save, that will make your phone only use two cores till you reboot. That should help with overheating.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thank you very much, this seems to be (at least temporary) solution for me. I follow your advice just now trying some (promising) stability/stress tests.
But, it would be great to have something like "one-click" setting via home screen shortcut...

kolargol said:
Thank you very much, this seems to be (at least temporary) solution for me. I follow your advice just now trying some (promising) stability/stress tests.
But, it would be great to have something like "one-click" setting via home screen shortcut...
Click to expand...
Click to collapse
If you install es bookmark, works with the es file manager you can create a short cut icon on your home screens to take you right to the hotplug folder, I running my phone on 2 cores most of the time testing battery life on 2 cores.atm.
Sent from my HTC One X using xda premium

Tasker solution
Just FYI: I just defined four different tasks in Tasker (CPU1 to CPU4), each containing only one "Run Shell" action (with root privileges):
CPU1: echo "1" > /sys/kernel/debug/tegra_hotplug/max_cpus
CPU2: echo "2" > /sys/kernel/debug/tegra_hotplug/max_cpus
CPU3: echo "3" > /sys/kernel/debug/tegra_hotplug/max_cpus
CPU4: echo "4" > /sys/kernel/debug/tegra_hotplug/max_cpus
Then I created home screen Tasker widget for each task and everyhing works just fine with single click.
Thanks treebill for initial idea and MrPhilo for further explanation.
EDIT: I'm on LeeDrOiD One Xtreme V4.0.0 ROM

[Q] HOX w/ possibly semi-dead battery

We had a power surge in this house while my HOX was charging... I'm guessing that's what caused the problem.
Unfortunately I bought it outright, 2nd hand, about 7 months ago. So can't get it replaced or repaired for free. It's been trouble-free until about a week ago.
Phone is rooted, has been upgraded/running Jellybean ROMs successfully; originally an Optus branded HTC One X (Australia).
The Problem:- so by default, if I charge it (with solid red LED on) while it's off, at random intervals with no user intervention, it'll boot to the boot screen, and then turn itself off to a black screen a few moments later. This will continue at random intervals of say... 30 minutes or so. Strange huh. Oh yeah, and when I try to boot the phone manually, it does the same thing. Annoying.
I can still get into HBOOT/Fastboot using power+voldown... and from there recovery. So I thought - okay... I can fix this. But upon booting, no matter how long I charge it while it's off, it complains that the battery is too low to flash. So I've been charging it in recovery for hours before flashing successfully.
So I've flashed a couple of different JB ROMs (such as Ordroid/Black Pearl) with their associated boot.img files properly (the way I always had before, i.e. before flashing the ROMs, and w/ fastboot erase cache etc), and each time it'll boot up into the newly flashed ROM fine, then I'll charge it up to full (green LED). But upon rebooting the phone, it goes back to it's initial behavior of going to the boot screen, then a few moments later going to the black screen and staying there (with red LED on). And then when I boot it with power+voldown... it complains the battery is too low to flash, even though fully booted and working it was saying it was 100% charged just a few moments before (having previously left it for hours to charge up to full). I've tried 2 genuine HOX chargers and cables, with no change in behaviour, and have searched threads about this kind of thing in this forum, to no avail.
I suspect the power surge has killed the battery somewhat , though I really don't know for sure.
Or is this a PEBCAK problem... could easily be... I'm sure I could've stuffed up somehow without realising.
Fixing this phone isn't critical, as I'd already moved on to a Nexus 4, however I had been intending to give this phone to my brother before it started misbehaving... so if anyone knows how I should proceed, I'd most appreciate any guidance.
Thanks.

It's a bit difficult to say whether it's the battery or the actual mainboard which got damaged.
There's only one way to find out, purchase a new battery and see. You can sell the battery if it doesn't work.
Sent from my One X using xda premium

[HELP] Reboots & Screen Issues

Okay everyone here is a hard one...
My son cracked my screen on my S3. It works and functions I put a screen protector on it for now, don't ask why I haven't fixed it yet -- it's irrelevant.
A few nights ago I was sleeping and I woke up to my phone super hot, couldn't even hold it in my hands, but it was okay and was working fine I let it sit out overnight and cool off then charged it back up. All seemed fine, until a day or so ago.
For some reason the phone completely shuts off AS SOON as it loads the rom (ANY ROM) I even went back to full stock and SAME thing happens. I do mean FULL stock. (Hours of work went into that fun process).
WHAT'S WRONG
- Phone shuts off once it loads into any rom then reboots and repeats the cycle
- Phone DOES NOT shut off if plugged into a power source, stays on without issues and works fine
- I can't use my phone without it being plugged in (battery works fine and charges fine)
WHAT I HAVE TRIED
- I tried cleaning the power button and internals by taking the whole phone apart.
- I checked to see if it was bricked in any way
- I tried different roms and android versions including stock (Yes with factory resets)
I have not tried deleting the entire phone internal memory (formatting it essentially) and re-installing android files back to it.
Any ideas?

Scath said:
WHAT'S WRONG
- Phone shuts off once it loads into any rom then reboots and repeats the cycle
- Phone DOES NOT shut off if plugged into a power source, stays on without issues and works fine
- I can't use my phone without it being plugged in (battery works fine and charges fine)
WHAT I HAVE TRIED
- I tried cleaning the power button and internals by taking the whole phone apart.
- I checked to see if it was bricked in any way
- I tried different roms and android versions including stock (Yes with factory resets)
I have not tried deleting the entire phone internal memory (formatting it essentially) and re-installing android files back to it.
Any ideas?
Click to expand...
Click to collapse
I suggest changing the battery to see if it still behaves that way. I also suggest you to completely start with a clean slate (format everything, including the internal SD, external not necessary) to discard possible issues. Those are the only ideas coming up right now.

I'll try and see if its either of those. I also noticed the power button is super sensitive. Light touch sets it off or on. Like capacitative button "light touch " how gentle those are pressed is how gentle I am tapping power and screen responds.

Sounds exactly like a faulty power switch, but it could potentially be the battery itself too though.
When you put the battery in, does it try to turn on by itself? If so it's almost certain to be a bad power switch.
Be very careful flashing in this scenario. ESPECIALLY flashing firmware via Odin. If it reboots during the flash it can be very bad news.
This can cause a brick on its own too btw, so i highly recommend getting it fixed ASAP. People have reported having this happen and at some point it just stops powering up at all. Upon further investigation it would show to be hard bricked, sometimes fixable, sometimes not. Basically the constant resetting (like power is permanently pressed) ultimately causes corruption on some of the partitions. It is possible there is already some data corruption present which could cause processes to hang, eat up battery and cause excessive heating.
If you want to be sure it's not the battery itself causing problems though, find someone with another S3 (go to a Tmobile store if you don't know someone) and borrow a battery to test with.
A bad battery can also cause reboots and overheating, but this is much less common than the bad power switch.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Sounds exactly like a faulty power switch, but it could potentially be the battery itself too though.
When you put the battery in, does it try to turn on by itself? If so it's almost certain to be a bad power switch.
Be very careful flashing in this scenario. ESPECIALLY flashing firmware via Odin. If it reboots during the flash it can be very bad news.
This can cause a brick on its own too btw, so i highly recommend getting it fixed ASAP. People have reported having this happen and at some point it just stops powering up at all. Upon further investigation it would show to be hard bricked, sometimes fixable, sometimes not. Basically the constant resetting (like power is permanently pressed) ultimately causes corruption on some of the partitions. It is possible there is already some data corruption present which could cause processes to hang, eat up battery and cause excessive heating.
If you want to be sure it's not the battery itself causing problems though, find someone with another S3 (go to a Tmobile store if you don't know someone) and borrow a battery to test with.
A bad battery can also cause reboots and overheating, but this is much less common than the bad power switch.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Sounds like I have three possible causes then... So I will first wipe and format internal memory and re flash everything. Oddly enough it does not reboot when plugged in and sometimes doesn't reboot at all but if I open camera or similar apps it then reboots and won't fully boot just tries to load everything and I get signal and texts come in but then it turns off and reboots again.
Then I'll go to my local spot with an S3 in display lol check battery and see.
Last I'll try and look closer at this power switch, don't think its the cause though. Ill place Collin different positions and see.

Even stranger...
So I reformatted my ENTIRE phone internal and external memory. Using multiple devices. Then re formated inside recovery to add the correct folders and files and stuff.
Here is my question.... Previously stated was "Battery could be an issue or Power Switch" -- If these were both the issue why would the phone never turn off in recovery mode? Why would it stay on during boot for long periods of time after flashing?
How can the battery or power switch be the problem when recovery mode keeps the phone on, and I tested this by leaving it on for an hour without it turning off.
The ONLY time it turns off is when the OS is about to boot up Android. If I keep it plugged in, then it boots up fine. What the hell?

A faulty power switch may not always constantly reboot. I've seen some that do, some that stayed on in Download Mode only, some that only rebooted when held a certain way, some that simply just had an extremely sensitive button, etc. In each case, replacing (or sometimes cleaning/fiddling with it) seemed to fix the issue.
I have also seen problems due to an old or defective battery. As it gets older, it doesn't just lose its ability to hold a charge, but it also gets weaker in that it cannot supply a stable or strong enough level of output. So, for example, it could seem to run ok, but as soon as you try to do something requiring more power, such as using the camera, it can crash because the battery can't provide enough power.
In a case like that, it could easily be able to supply enough to run recovery as its power requirements will be much lower than when you are booted up normal.
You did say it works just fine when plugged in though, and that it only reboots when you try to boot normally. But you also said opening the camera will cause it. This is why I suspect it could be the battery.
You also mentioned that the power button is extremely sensitive though. That is not normal and faulty power buttons happen frequently on this device.
All I'm saying is it could be one, or even both, of those causing your problems. It is possible too though that it's suffering from memory failure, which can result in any number of strange problems.
I am just giving you the most likely possibilities based on past experiences in these forums. I'm not saying it's definitely one or more of these. It could be something else entirely.
Did you ever try the test I asked you about? Remove/reinstall battery. Does it try to turn on by itself when you put it back in?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
A faulty power switch may not always constantly reboot. I've seen some that do, some that stayed on in Download Mode only, some that only rebooted when held a certain way, some that simply just had an extremely sensitive button, etc. In each case, replacing (or sometimes cleaning/fiddling with it) seemed to fix the issue.
I have also seen problems due to an old or defective battery. As it gets older, it doesn't just lose its ability to hold a charge, but it also gets weaker in that it cannot supply a stable or strong enough level of output. So, for example, it could seem to run ok, but as soon as you try to do something requiring more power, such as using the camera, it can crash because the battery can't provide enough power.
In a case like that, it could easily be able to supply enough to run recovery as its power requirements will be much lower than when you are booted up normal.
You did say it works just fine when plugged in though, and that it only reboots when you try to boot normally. But you also said opening the camera will cause it. This is why I suspect it could be the battery.
You also mentioned that the power button is extremely sensitive though. That is not normal and faulty power buttons happen frequently on this device.
All I'm saying is it could be one, or even both, of those causing your problems. It is possible too though that it's suffering from memory failure, which can result in any number of strange problems.
I am just giving you the most likely possibilities based on past experiences in these forums. I'm not saying it's definitely one or more of these. It could be something else entirely.
Did you ever try the test I asked you about? Remove/reinstall battery. Does it try to turn on by itself when you put it back in?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Well Doc, I think everything you just said wrapped it up for me and made a ton of sense.
Sounds like the battery. It overheated prior to this and when I checked the logic board there were no signs of heat stress points I remember when I took the phone casing off when it got hot, the battery was the hottest part that I couldn't touch. I think the battery just gave out finally after all these years of use.
Install and reinstalling the battery the phone does NOT turn on by itself. Not ever. ONLY when it tries to boot the OS does it go into a boot loop where it tries to boot fully then restarts, similarly when you have a very low battery and the phone shuts off right as the OS boots.
Think the battery is the culprit here. :fingers-crossed: I just bought a new glass screen kit for the phone as well, $6 bucks isn't too shabby on ebay. Even though it may suck really bad and be flimsy glass, it's still something! So now the battery will be purchased next -- any suggestions?

I just got a new battery on ebay too, but it's got problems. They sent a free replacement but it's worse than the first. They might be fake "oem" batteries so i dont want to recommend them.
They appear to be from the same lot though, so it could be just bad luck and a bad lot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

If you want an OEM battery you're probably better off buying it from Samsung or T-Mobile. I've also heard zerolemon is a good alternative