Hi,
I have an XDA-Orbit which is automatically turning itself on every couple of minutes, which is obviously draining my battery and effectively rendering my device useless.
I have "BatteryStatus" installed which, amongst other things, displays an icon on the today screen that tells you the current power drain on the device in milliAmps. If the device is plugged into the mains, this software tells you the positive current that is being added to the device.
I am almost certain that this program is pointing the the problem I have, since whenever the screen lights up (or when the device turns itself on fully), BatteryStatus is reporting that the consumption has changed from being a negative (drain) on the device to a positive input of current. The icon also changes to a plug, implying that it's been connected to the mains and power is being supplied. For some unknown reason, the device seems to think that it's connected to the mains and is having a positive amount of power being put into it when there's nothing connected to the device.
Has anyone else come across this problem? Can anyone suggest how I might fix it?
The device is NOT plugged into the mains! And there's no power actually going into it.
Many Thanks,
Rob
Related
I have upgraded to WM6 using the AT&T official release. WM5 used to maintain my ActiveSync connection when I turned the screen off (by momentarily depressing the power button - sleep mode). Now WM6 drops the USB connection. I performed a hard reset - no change. I reinstalled WM6 - no change.
It appears that for applications, the 'sleep mode' is acting more like a power-down mode (just doesn't reboot when you power up again).
>>>Follow-up - I tested the bluetooth connectivity and it appears to stay up during sleep mode. So it looks like just USB is affected when going to sleep.
>>>Follow-up #2 - Media Player continues to play (and the speaker is active) when in sleep.
This is normal behavior. Have you experienced otherwise in the past?
Probably normal as when its plugged in via usb its powered and doesn't need to go into sleep mode.
Did you guys not even read his original post at all? He had it working with WM5 and now it's not. Which would mean it is NOT normal. Not to mention you can still use sleep mode while having it plugged into a USB port so I don't know why the last poster would say it doesn't need sleep mode. Of course it doesn't need sleep mode. It's being charged. That doesnt mean he wouldnt still want the screen to turn off while it's plugged in. I charge my phone right next to my bed if I had that damn bright screen on while I tried to sleep I'd go crazy. Point being neither of those posts were worth a damn. sheesh.
Edit: For the record mine disconnects activesync when in sleep mode as well. I don't remember if it did so in WM5 or not but I'm pretty sure it did cause I recall being a bit surprised when it disconnected when I hit the power button. Now we just need some real help with real answers.
surrept said:
Point being neither of those posts were worth a damn. sheesh.
Click to expand...
Click to collapse
And your post really helped to solve this "problem", didn't it.
I'm sure he just didn't want a program to turn his screen off, as anybody with half a brain could find a freeware cab to do that. How about searching google for screen off pocket pc freeware
Call down surret... calm down. No need to take it so personal.
Just because it works in WM5 does not mean it will act the same in WM6. I was not giving a definite answer about sleep mode but maybe an idea as to why.
When I plug my phone into the wall it still charges fine in sleep mode. When I plug my phone into my computer it charges in sleep mode but the usb does not stay connected. I was suggesting that since sleep mode is to save the battery life that when your connected the battery is not being used and hence not really required. Also in sleep mode in order to save battery it needs to turn off as much as possible. It looks like the USB connection is one of them.
There are other options like a screen toggle as per the post above and there is also a setting that you can use to turn off the backlite when the device is plugged in and not put it into sleep mode. I think thats in the power saver settings somewhere.
I do not know of a registry hack or anything to make it work the way you want but I am letting you know that it seems like thats the way it works on WM6.
Thanks to all who responded. I'm relieved to learn that this is normal for WM6.
Since WM5 allowed me to sleep while charging/syncing and WM6 didn't, I was afraid that my 8525 was developing problems.
I will simply have to change my behavior to accomodate WM6. After all, if all WM6 did was add support for SDHC cards, it would justify the inconvienence.
One thing to note too that I noticed...
Even though its in sleep mode and not connected (even though its plugged in) I notice my phone still wakes up and does a sync every now and then. Might want to check that. Maybe it still sync's ona timed interval but doesn't stay connected.
Knockz said:
One thing to note too that I noticed...
Even though its in sleep mode and not connected (even though its plugged in) I notice my phone still wakes up and does a sync every now and then. Might want to check that. Maybe it still sync's ona timed interval but doesn't stay connected.
Click to expand...
Click to collapse
That was one of the annoying things - when put to sleep when it is in the cradle, the 8525 would wake up after a short period, reconnect, and resync.
So even when you put it to sleep it wouldn't stay asleep (if connected to a powered on PC). If the PC is powered off the 8525 stays asleep until you manually wake it up or a event occurs (incomming call, reminder, scheduled backup, etc).
Found a pretty nifty bug on the evo... not sure if it is software or hardware.
* turn wifi on
* plug evo into computer USB port
* start watching streaming video (or any other CPU intensive task)
* eventually the battery will be at 0 and the thing will shut off with a blinking orange light.
The bug:
* the phone never warns you. Because it is "charging" the phone never gives you the low battery warning (quack,quack, orange warning light, etc).
* If you are connected to a power source that isn't sufficient to charge and power a fully loaded phone, it just dies without warning.
* I have no idea what the solution for this would be, it kind of is a catch 22.
Most devices have the same issue and I've found many that don't give the warning either.
Remember, USB through computer or whatnot maxes at 500ma, normal usage of the cpu/phone, etc draws more than that. The AC charger was 1a and should be sufficient.
Does it suck they didn't warn you? Yeah, but now you know and probably won't let it happen again. I suspect you can make your own warning system using something like Locale or Tasker and have a SETCPU profile to throttle down your CPU to save power. That's the nice thing about android, it's open enough that you can find a BETTER way of doing things than relying on the devs of the phone.
I'm hoping some of you wise heads on here might be able to help me out with a problem that has got me totally and utterly stumped!
Last week I was using my One X and noticed the battery was down to aorund 14%. I plugged it into a charger and nothing happened...no light...nothing. I tried various different chargers and cables to pc etc and nothing seemed to do anything.
After leaving the phone plugged into the mains for a few hours, I noticed that a very slow/long flashing red/amber light appeared. It kind of stays on for 5 seconds and then off for the same amount of time. I left the phone in this state for about 14 hours and when turning on it would say battery was somewhere between 0%, 1% and 2% and would promptly switch itself off.
I messed about for hours on end trying many different button combinations, sim in/out and came to this bizarre conclusion.........If I plug the phone into the mains for a few minutes, then press power and volume down to get to the HBOOT menu then hold power in again to reboot, the phone reboots into the OS and is functional. It still reads as having 0% or 1% battery and shows as not charging, but it must be getting some juice for it to be working. If I leave the phone in this state for a while I can then unhook it from the charger and use it as normal, even though battery is displaying as 0%. I can use the phone like this for some time, although the battery does not appear to last as long.
Also, the phone is not recognised at all by the PC when plug in via usb when in android os - nothing at all shows in device manager, but it is recognised from the fastboot menu and tries to install device drivers.
Has anybody got any clue if I can save my HOX or am I without a paddle?? Many thanks in advance
For a few weeks I've had intermittent problems with my phone not detecting the USB connection and randomly turning itself on. After a while, these problems stopped and some new problems appeared. Now the phone is always detected on USB, but refuses to charge saying Charging paused, battery temperature too high. It does this every time I try to charge it. If the phone is off, it shows a yellow triangle with a thermometer. Along with this the softkeys and home button quit working at the same time.
So far I have tried resetting to factory default, a new battery and replacing the USB charging flex port and it still won't charge. Monitoring programs show the temp fixed at 60C and never moves. Is there a replacement I can get for the temperature sensor or some way to disable the check? I am rooted and am willing to try anything. Right now it's looking like I may need a new motherboard.
I have ordered a wall charger so I can at least use the phone and I downloaded a softkey app so I have buttons again.
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.