Related
Hey all,
I've got a Orange branded e650/HTC Vox flashed with Dr Gonzos 6.1.1.1 which is much much MUCH better than the standard orange OS which constantly crashed and locked up, so top work there
Now, I have a bit of a problem, today I woke up to see my Vox had turned itself off, which was a little unusual, i turned it back on and it worked fine, however later at work it decided to start vibrating constantly, the orange charge light and the blue bluetooth lights at the top of the screen where on constantly, the screen had its backlight on but no information was being displayed, i took the battery out and left it for a minute before plugging it back in, it did this twice more during the day, the last time i left the battery out for a good 15 minutes or so before plugging it all back together and now its booted and working properly.
My question is this, is my phone on its way out? Is this going to be a regular occurrence? or is there anything I can do to stop it?
Thanks in advance
-pete-
Well, maybe you should try to redownload and reflash the ROM. Maybe it didn't flash properly?!
It was flashed a good few months ago now (around march/april time if I remember right) and its being fine since I did it until now :/
Oh, then you might just try a hard reset!
I really don't know if this is possible or not.... but I might need to get some new corduroys after a case of the brown adrenalin with my new sensation.
Got it Friday as could see progress on the rooting and sure enough Revolution came up with the goods same day. Rooted it Saturday.
Fully charged it, switched it off and went back to the HD2 - flip case and car kit arriving today. Really don't wanna damage my new boy toy by pocketing it with car keys etc.
Stone me though I thought I bricked it. Wouldn't switch on this morning - just a dark flicker of the screen. Sweat pouring off my forehead. Never bricked a device and flashed my HD2 & TP2 a million times and my £450 unlocked handset is 3 days old and dead..
Long and the short of it is plugged in the charger again and a few minutes later it powers up - 3% battery.
Is it possible it could drain switched off? Or should I blame the kids for messing with it and deduct my dry cleaning bill from their pocket-money?
After I rooted, I had to do a battery pull until I was able to turn my phone on again, although this doesn't really replicate what problem you had...
The battery does not drain if the phone is turned off.
Question is, was it definitely turned off?
Even if it wasn't, there's no way a full charge is going to drain overnight... Unless you had a Satnav running...
Sent from my HTC Sensation Z710e using XDA Premium App
You're right - it SHOULDN'T... I'd rebooted no problems several times after the rooting. Some OTA update came over and didn't install successfully though.
It'd be very odd (and a warranty issue, get ready to go into rooting reverse) but for now I'm inclined to just blame the kids. Unless anyone else has has similar experiences.
I guess time with it will tell.
EDIT: Apparently it's a known issue and has been fixed with the new CWM update! See: http://forum.xda-developers.com/showthread.php?t=1192300
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
EDIT: Good man. Thanks for the update. Better get onto that right away.
Yup.. that's the same experience... except I'm still on stock rom with tweaks.
What do you reckon - flash back to stock and see if it still happens? Really don't want it turning into permanent paperweight with an iffy bootloader for someone at warranty to find with their JTAG.
Morsolo said:
Ah ha, looks like it's not just me!
This just happened to me today and I had to change my pants because I thought I bricked it. I rooted it and installed InsertCoin no problems!
Today, as it jumped off my WiFi and onto the mobile network it got stuck on "Disconnecting from Morsolo's WiFi" and just sorta froze there (the phone still worked, but it wouldn't fully disconnect from WiFi, so I got no mobile data).
I turned the phone off via normal methods (40% Battery)... Then it wouldn't turn back on. The phone was a little bit hot at this point, but it does heat up so I thought nothing of it.
For a good 30 minutes, nothing happened. All that I could see happening when I attempted to turn the phone on was, the screen backlight would turn on, fade off, turn on, fade off. No boot, no recovery, nothing.
I tried charging it and it would show the indicator for 2 seconds and stop charging (but this is a known issue, apparently it continues to charge regardless).
After numerous times pulling the battery, trying to start, charging, battery, start... I finally managed to get it to boot and it said the battery was at 3%... After the phone was STONE COLD DEAD for a good 30 minutes to 1 hour.
...I just got home (with a dead battery, of course) and now that I've plugged it in again, it wont boot, again.
I think we've discovered an issue.
Click to expand...
Click to collapse
My HTC was working fine yesterday until it froze at one point and it wouldn't respond to any buttons including the lock button (which has never happened before except occasionally during incoming calls). I did a battery pull and at first it would only vibrate and remain a black screen, though I could see that it did light dimly when I pressed the power button. After about 20 battery pull attempts it went back to showing the splash and screen and the phone turned on succesfully. After about 10 minutes it froze again, I did a battery pull and now it only showed the splash screen and froze, occasionally showing a red light in the top left corner. My phone was already on low battery so this process went on for another 25 minutes or so (vibrate + screen, freezing on splash screen, or booting then freezing) until I gave up. I came home and charged it overnight while it was off, and it was fully charged this morning, but now it won't turn on at all, it only vibrates once with the screen lighting very dim for a moment then just has a black screen.
I've been searching for a solution for the last 3 hours, seems it could be a range of things but nothing I've tried has worked. I'd appreciate the help, I already spent £90 on getting the screen repaired a couple weeks ago, I don't really want to spend more especially if for some reason HTC decide it can't be repaired under warranty.
Are you s-off and running a custom Rom? It so can you provide details on Rom, kernel and firmware?
There were threads a few weeks back about sensations randomly dying.
Thanks
s-off?
No I'm not running custom ROM.
Came acrosss a few other threads with similar threads but my problem seems to be a combination of everyone else's problems, so I'm a bit lost
are you under warentee? Your stock so there should be no reason at all for HTC to deny your warentee. I'm curious, have you tried to put a different battery in? To see if possibly your battery has gone bad? Worth a try? Even though it says full charge maybe its gone bad? Wouldn't hurt to try. If not and new battery won't work I'd definitely look into warentee repair. You have not altered your device so they definitely should honnor repair.
Sent from my HTC Sensation Z710e using xda premium
Hey I have a sensation 4g. All has been well until today. I was at work and got an email. Went to check it but the screen wouldnt turn on. This has happend several times since using Viper rom, which is why I switched to energy. I pulled the battery and went to turn it back on.
Since than all I get out of it is a brief lighting of the screen followed by a boot vibration. After that the screen stays off and it "boot vibrates" at regular intervals never displaying anything. Attempts to get into the boot loader for recovery are met with the same.
If I plug a charger into it the charge indicater lights for about 15 seconds than turns off. Occasionally I can see a red light in the upper left hand corner.
I have used a htc g2 battery held against the pins as a known good battery so I have eliminated my battery as bad.
It is rooted, was running ICS Energy rom.
adb does not detect the device nor does linux or windows, but thats not too unusual since it technically doesnt turn on.
I am assuming that the thing is totally dead for whatever reason, but on the off chance someone has any ideas Im all ears, I love this phone.
azethoth said:
Hey I have a sensation 4g. All has been well until today. I was at work and got an email. Went to check it but the screen wouldnt turn on. This has happend several times since using Viper rom, which is why I switched to energy. I pulled the battery and went to turn it back on.
Since than all I get out of it is a brief lighting of the screen followed by a boot vibration. After that the screen stays off and it "boot vibrates" at regular intervals never displaying anything. Attempts to get into the boot loader for recovery are met with the same.
If I plug a charger into it the charge indicater lights for about 15 seconds than turns off. Occasionally I can see a red light in the upper left hand corner.
I have used a htc g2 battery held against the pins as a known good battery so I have eliminated my battery as bad.
It is rooted, was running ICS Energy rom.
adb does not detect the device nor does linux or windows, but thats not too unusual since it technically doesnt turn on.
I am assuming that the thing is totally dead for whatever reason, but on the off chance someone has any ideas Im all ears, I love this phone.
Click to expand...
Click to collapse
Maybe it was a hardware failure. how many times does it vibrate? there is something called qualcomm diagnostic mode that htc phones sometimes get happens when the hboot gets corrputed/damaged. depending how many vibrations you get some people have had luck attempting to blind boot a pc58img.zip to the bootloader to flash a ruu. but since your phone isnt being recognised by the pc as anything i wouldnt hold out to much hope how many vibes do you get?
You might be in diag mode, as heavy_metal_man said.
Does QHSUSB_DLOAD come up in Device Manager?
neither windows nor linux recognize the device at all.
as far as the vibration. I call it a boot vibration, as it is the same intensity and duration of the normal boot vibrate you get on power up.
Its a single vibration of about one second. After that every about 30 seconds it vibrates again.
I did try to shove a P58IMG.zip onto the sd card but I figured that was a long shot anyway and of course nothing happened.
Just out of curiosity have you tired another battery? I know you did check it but one time I was charging my device with a perfectly good battery, it wasn't low, and my device made a weird noise like a high pitch noise then went black. I had no charging light, no life what so ever. I thought I was completely screwed thinking something fried my device. Out of desperation I put another fully charged battery in. Then my device sprang back to life and I haven't had any trouble since. I never figured out what happened. But I was so Glad it worked. So just for curiosity do try another battery. It can't hurt to try it. In my weird case it worked. Like I said earlier the weird part was my battery was good! Not dead! So it won't hurt to just try. You have nothing to lose. I do hope it helps. Good luck and best wishes!
Sent from my HTC Sensation using xda premium
sadly I have no other battery, I have a g2 battery that I can hold in as a substitute but still the same result. I will try to throw that img back on the sd card and see if I can blind install it.
Appreciate the help guys.
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
RomanKasp said:
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
Click to expand...
Click to collapse
ICS may just have battery stats that don't work for your batteries. Try calibrating the battery:
http://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en
If I remember the instructions properly, install the app, charge to full (or half hour past full), open the app to press the button, run it dry, and charge it fully with it turned off (note the LED on mine turns green at the 90% mark, so leave it plugged in and off for about an hour past the time it turns green).
I found with the app, it takes forever to get that last 1% after using it, and it takes a while before dipping below it again, but it seems to be more accurate than CM thinking I had the stock battery installed (I have a couple Ankers now). Hope this helps.
Thank you but doesn't work
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
RomanKasp said:
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
Click to expand...
Click to collapse
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
joel.maxuel said:
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
Click to expand...
Click to collapse
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
RomanKasp said:
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
Click to expand...
Click to collapse
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
joel.maxuel said:
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
Click to expand...
Click to collapse
I tried everything, including wiping data/cache/Dalvik cache, then installing the file, I even tried to install the GApps too. Nothing seems to happen. It just gets stuck in the bootloop. When you first turn it on, it stops at "Starting apps", then if you reboot it, it stops working at CM logo (bootloop). I waited for 10 minutes or more, no result. Luckily, I did a full backup so I went back to CM 9. Seems like my phone is simply incompatible with this mod. No luck for me here .