Running CROMI 3.1 with no problems since it came out.
This morning, I unplugged it from it's charger, (it's in a leather case, with out the dock attached) & brought it with me to work as usual.
a couple hours later, I opened the cover, & found that it was on, & warm. (at the home screen)
checked & had no apps running.
Battery useage page showed that WiFi, & Bluetooth were the top two processes using the battery, with Screen next on the list.
In less than 3 hours, it went from a freshly charged battery, to 53%
I've always left WiFi & Bluetooth on before, & never had them use my battery like that.
I'm assuming they were going mostly due to the screen being on, but I can't figure out why the screen would stay on like that. It's never done that before.
Anyone seen anything like this before?
Could be a rogue app, or service, as the Android battery report is pretty bad. Install BetterBatteryStats from here and let it cycle for a bit. I suspect it won't happen again all that often, but at least you'll have something to work with when it does to perform some amateur forensics on.
Any specific installs you have done lately?
Related
First day of a new job so I put my phone on a Work profile using PhoneWeaver (paid). Had the phone vibrate a few times telling me I had emails, and then one last time telling me the battery was almost dead, then it died. Had 6 hours of life out of it, not even joking.
Once I got to the car to charge it and head home, the phone went into the display where the battery icon shows up and the phone is off, but flashed a yellow warning triangle with a red thermometer next to it on the right side of the battery. Wish I had a camera on me to take a picture, but I immediately pulled the battery door off and placed it on an A/C vent on the car, and the phone died again since it wasn't connected to the charger anymore.
When I finally got the phone home and charging, I went to the battery status screen to see what was draining the battery, and even though it was showing what was going on since the power cycle, it showed the Display was accountable for 94% - still not convinced, I went to my PhoneWeaver settings to see if the Work profile had Wifi or GPS on the whole day, and it didn't have anything out of the ordinary. Only thing I can come up with is that when the emails and texts came in and I didn't check them, my phone unlocked in my pocket and left the screen on the whole day.
Has anyone else seen the overheating / temp warning screen on the battery status level display when the phone is off? What caused it in your situation? I have a hard time believing that if I wear heavy khaki shorts as I've been doing since I got the phone on the 19th, the phone won't unlock and in turn won't overheat, but when I wear dress pants on my first day of work at a new job, the phone unlocks, runs the display all day, and my lightweight slacks make the phone overheat????
sorry for the long narrative, I just wanted to give all the details of what happened in case anyone has any advice or similar experiences.... thanks in advance!
never, i recommend restoring factory settings and using it as is for a day and see if this happens again. It could be something you installed. If you have a similar experience, return your phone and get a replacement.
make sure they replace your battery incase it got fked from the overheating caused by the phone.
well, day two of work and my phone is just now at 20 percent, 14 hours later, lots of texts and emails and everything else
On Sunday evening my phone was at about 60% battery from a full day, which was pretty impressive considering I had been played some games, responding to texts constantly and checking email. I decided to not plug in my phone that night to see how much battery life I could actually get continuing into the next day. I woke up the next morning and my battery had not dropped a %. At first I was ecstatic because I finally thought my battery woes were over....I was wrong.
As soon as I left the house Monday morning on my way to class, while streaming pandora, my phone alerted me of 'low battery'. I checked my battery again and it now said 58%. I assumed this was normal because streaming pandora does consume quite a bit of battery. Less than a minute later my phone shut off completely. I did not have a charger with me so I was not able to plug the phone in again til later that afternoon. When I did plug it in, the battery was was completely drained, at 1%. I'm assuming for some reason the status of my battery was not being updated correctly via my battery widget and through settings -> about phone -> status.
I fully charged my phone that same day and had no problems using it last night or even this morning. But on my way home today from class, my battery was at 70% which is normal for me, but for some reason it just completely shut off. No battery warning or anything. When I arrived at home today I tried pulling the battery and plugging it in the the charger and everything else I could think of. Even charging via my laptops usb. Nothing seems to be working.
The phone is not rooted and everything is completely stock. I don't any apps that effect the performance of the phone or anything of the sort. Just stock running adw.
Any suggestions before I call up T-mobile?
Thanks in advance for those who read this whole thing and provide useful feedback
EDIT: Also, I have not used any HDMI cables on this device. I read some people are experiencing similar issues when using HDMI, that is not the case here.
Call TMobile.
I'd say call t-mobile like ^
I did just that.
I was hoping someone could have provided a solution to this but I believe this is due to hardware failure. Lost lots of important photos/texts :\
I went to the T-mobile store today and even tried a new battery but the phone still wouldn't power on. They will be sending me a new one within the next week.
Which leads me to believe that T-mobile is in fact not "out of stock" as they claim to be in all of their stores and on their website. Definitely some quality control going on as they are holding back on selling this phone til the GB update.
Ok I have searched and not found anything like this yet so I am going to ask. I know the phone has battery problems all around for a lot of people. Mine seems to be fine when it is on. It can sit and idle powered on all day locked and stay at full charge. It runs about 10 hours with minimal use and maybe 8 hours with some data use and a few calls and texts. Now I am experiencing a wired problem. When I go to work we cannot have cell phones. I leave my phone in my locker and power it off. After my 12 hour shift is up at work I come back to the phone with a dead battery? What could be causing this? And has anyone else noticed this issue?
defective battery? pull the battery and see if it still does it. If it does, gotta be a defective battery.. if it doesn't do it when pulled, you're not shutting off the phone maybe?
Yesterday I tried leaving the battery out. I took the battery out and let it sit 12 hours and it still had full charge when I put it back in. When I go to work I long press on the power/lock button and choose Power off then I watch it shut down and it just dies before I come back. I wish I could watch it the whole time. Today I left the phone off for around 6 hours and came back and it was fine though. Maybe it gets turned on some how at work. I have no idea. Or when I go to power it on it is just the issue where the phone isn't reading battery % correctly and it just says 0%
Seems like a battery driver issue or a defective battery? definitely call t-mobile and check if it's the battery. I've had some issues as well, but not that bad.
Weird.
So the phone powers off after you turn the screen on and it won't come back on? Try putting the phone in airplane mode.
Also, I'm assuming you are running the stock roms?
Might also want to check into a battery monitor to see if any 1 thing is pulling it down.
I think it might just be the battery driver. Sounds like the phone is in suspend so it doesn't power off properly until the screen is turned on and is revived, updating the battery % status, seeing 0%, and turning off.
CM7 fixed the wonky battery issue a few nights ago. Right now, I think a current CM based rom is the best bet as it has most of the drivers fixed. I'ved used mine pretty heavily today, unplugged at 8am and I just got a 15% battery warning at 11:30pm. It will usually last until I go to bed at midnight but I might want to play with it some more.
Today I had my sensation in my backpack for an hour or two. When I took it out, I realiezd it was VERY hot (Maybe 40 degrees, but not just in one place, all around the phone...) and the screen wouldn't turn on. I then opened it, removed battery and reinserted it. Then the device booted. I checked my battery status, and it had dropped by about 40%. Also, the battery usage shows that WiFi was turned on until the point where the battery dropped. But I'm pretty sure I had turned it off (Using the HTC widget). Have you experienced anything similar yet? Do you think this problem could be WiFi-related? I hope it doesn't happen again... Phone is only two weeks old. I didn't try any overclocking or the like.
never heard of this problem before
I got this phone about a week ago and I am noticing two major issues with it. First, the phone sometimes gets really warm in my pocket. Second, when it gets warm it starts to kill the battery. Interestingly, last night I unintentionally left it under an unused pillow. The battery was at 100%, but this morning when I got up the battery was down to 1% and the phone was really warm.
As you can see in the attached screenshot there wasn't much running, the phone wasn't awake much, and I had good signal. Any ideas what might be going on here?
I'm just spit-balling here. These are some basic things I'd look at for a start:
A) use cpy spy to see what states the cpu is in
B) See what apps are running while this is going on. Anything weird?
C) check your data usage. It should list apps. Perhaps you have something sending a crap-load of data?
D) Turn off GPS, BT, WiFi, etc all/one at a time.
Thanks, UberSuber.
I was waiting for it to happen again, but it hasn't so far, so I am going to chalk it up as a fluke.