Hi team,
First post so be kind.
I did post this on an andriod forum and someone suggested I come here.
I've had a HTC Sensation for a while, since first released. After around 2 weeks of getting it I was experiencing an issue with the screen not being very responsive. Difficult to unlock, text, answer calls! It's sooo annoying. Luckily I had my phone swap not problem by Vodafone. Now it's been around 4 weeks now since getting my replacement and just yesterday I've started with the same f-ing problem!
I've tried the usual stuff, clean screen, clear cache, kill programs, remove battery.
Anyone else having problems like this?
I can't bloody answer calls !
Dan
DanoBoyo said:
Hi team,
First post so be kind.
I did post this on an andriod forum and someone suggested I come here.
I've had a HTC Sensation for a while, since first released. After around 2 weeks of getting it I was experiencing an issue with the screen not being very responsive. Difficult to unlock, text, answer calls! It's sooo annoying. Luckily I had my phone swap not problem by Vodafone. Now it's been around 4 weeks now since getting my replacement and just yesterday I've started with the same f-ing problem!
I've tried the usual stuff, clean screen, clear cache, kill programs, remove battery.
Anyone else having problems like this?
I can't bloody answer calls !
Dan
Click to expand...
Click to collapse
Hmm, difficult to be gentle but i'll try.
http://forum.xda-developers.com/showthread.php?t=1129272&highlight=touchscreen+problem
http://forum.xda-developers.com/showthread.php?t=1154532&highlight=touchscreen+problem
http://forum.xda-developers.com/showthread.php?t=1141963&highlight=touchscreen+problem
http://forum.xda-developers.com/showthread.php?t=1141352&highlight=touchscreen+problem
And that's only a few using search.....
My advice, discharge till it dies, put it on charge from USB port, don't touch it till it's fully charged. Might fix it.
Oh, btw, welcome to XDA.
I noticed the same problems. I am getting the same issue i had on my Droid Incredible where if i am not holding the device and its on a table, i cant seem to unlock it. I've been draining the battery down to 2% or less before recharging it each night i've had the phone and nothing has changed relating to this issue. I think it's just something that if a lot of people complain about, HTC will try to make some software changes in an update to address the issue somehow.
Excellent thanks. Can't stand this thing for much longer!!
Hi All,
I wanna start this thread to see how many people had a sudden bricked with their sensations. This thread will help us in defining what "might" caused our phones to suddenly brick itself.
Here are my symptoms.
-No LED
-No LED on charge
-Doesnt show any sign of life
Whats my phone has before it bricked.
-s-off with wire trick no htcdev unlock
-3.33x
-viper rom
-sebastianfm kernel
If bricked users can share this little.information or more, maybe we can compare and trace where it all began.
Thanks!
Sent from my HTC Sensation Z710e using Tapatalk 2
The computer is detecting your phone?
Try remove battery for about hour.
Thanks for wanting to put a thread like this together but others as well as myself have tried to do threads like this. But the problem is that the issue is so random that when other users experience the issue the thread is pushed way back. Or the user is vainly thinking that their device is not suffering the same issue and is recoverable. The truth is it is a hardware defect of some kind. Exactly what defect I do not know as know one with the knowledge has ever taken apart on of the faulty devices to investigate it. My best guess is something happens to the CPU and it becomes unusable. I say this because all the devices I have read users post about that this happens to all report the same as you. They get no led when connected to a charger, phone sudently became unusable without warning, and they usually get QHSDQualcomm as the device if connected to a computer, but some have reported nothing when connected to a computer. If you click on the link to the thread I started you will read what happen to my device and also I have a link to another thread with people that have had it happen. If you still have warranty on your device make HTC replace or repair your device. And so you know if they repair it that means they replaced the main PCB board as that is the only fix for it. Do not waste your time or money on JTAG cause like I said this is a hardware issue.
Radolex said:
The computer is detecting your phone?
Try remove battery for about hour.
Click to expand...
Click to collapse
Thanks for your concern in helping me Radolex, but I had this problem and has been fixed by replacing the motherboard.
T-Macgnolia said:
Thanks for wanting to put a thread like this together but others as well as myself have tried to do threads like this. But the problem is that the issue is so random that when other users experience the issue the thread is pushed way back. Or the user is vainly thinking that their device is not suffering the same issue and is recoverable. The truth is it is a hardware defect of some kind. Exactly what defect I do not know as know one with the knowledge has ever taken apart on of the faulty devices to investigate it. My best guess is something happens to the CPU and it becomes unusable. I say this because all the devices I have read users post about that this happens to all report the same as you. They get no led when connected to a charger, phone sudently became unusable without warning, and they usually get QHSDQualcomm as the device if connected to a computer, but some have reported nothing when connected to a computer. If you click on the link to the thread I started you will read what happen to my device and also I have a link to another thread with people that have had it happen. If you still have warranty on your device make HTC replace or repair your device. And so you know if they repair it that means they replaced the main PCB board as that is the only fix for it. Do not waste your time or money on JTAG cause like I said this is a hardware issue.
Click to expand...
Click to collapse
Thanks for the reply and info, So lets just assume now that sensation has some freaky ways to die. I agree with the CPU being not stable, I was on 1.5ghz with Vipers and looks like there are some "processors" like mine cant handle that **** or also maybe Im in Asia which we have a hot weather. hot weather + OC made the cpu die.
Hello,
I have searched and searched this forum to find any threads or posts that describe this problem. I have found lots of similar ones, but none like this, so that is why I have started a new thread. If I missed this topic somewhere, I apologize for not having found it.
My wife and I both have Skyrockets (GSII - I727). Stock AT&T ROM (not rooted), but both unlocked. Mine got partially wet last week (toilet incident, would rather not elaborate, but I will answer the first question everyone asks - yes it was a "clean" toilet ) Anyway, I immediately liberally rinsed all ports with alcohol and warmed gently with a hair dryer. After drying I powered up, and everything worked, except the battery percentage display (with a variety of completely fresh and fully charged batteries), would only show in the 50 - 68% charge range, and the phone seemed to die at about the rate one would expect commensurate with those numbers. Put it in a bag of rice for 2 days. No better.
So, after reading here and watching several YouTube videos, I completely disassembled the phone. cleaned all ports, ribbon connectors, mother board, etc. with CRC electrical contact cleaner spray using the spray tube and a very gentle toothbrush. I paid special attention to the micro USB charging port, and all other contacts and circuits that seemed to be related to charging, though I am by no means an electrical engineer or technician, so a lot of it was guesswork. I made sure all was dry and new looking. All contacts intact, no visible corrosion or bridging, and reassembled the phone perfectly (pretty proud of myself for not breaking anything in the process!)
The phone still works great, except for the battery percentage display issue. I have tried everything I've read on this forum about recalibrating the battery meter - discharging fully and then charging up. With the phone on, with the phone off, every permutation I can think of. I tried clearing the cache and rebooting. Still, the maximum the display will read is 68% and that's it, and the phone behaves and dies like it has a battery that is only 68% full, even though I know I am putting 100% charged batteries into it. I have verified this by putting the same batteries into my wife's identical phone and it displays 100%.
If my phone we're lasting as long as it normally would with a fully charged battery, I wouldn't be so bothered by the display being inaccurate, but that is not the case. I've downloaded CPU SPY and some other apps to see if my phone is using an unusual amount of battery resources, but it is not. So, that's the story.
I am not afraid of rooting the phone, and I have no warranties left so I don't care, it's just that from what I've read here on the forum, people with somewhat similar issues have not benefitted from rooting and then running apps or programs that are only available to rooted phones, so I would prefer not to go down that time consuming route, if all I'm going to do is hit another dead end.
So, any suggestions or comments would be greatly appreciated! Thanks in advance.
Best regards,
Ron M.
This may sound dumb, but did you try a factory reset?
sireniankyle said:
This may sound dumb, but did you try a factory reset?
Click to expand...
Click to collapse
Thank you for your post sireniankyle. Not a dumb question at all, and actually the answer is no. I have certainly considered it, but I haven't done it yet for 2 reasons.
The first is that from all the research I've done, trying to find others who had similar experiences (I have yet to find anyone with the IDENTICAL problem), they have all without exception reported that factory reset did not solve their problem.
Second, because of my previous experiences with doing a factory reset, it seems that no matter how well I am backed up, that it turns into a very time consuming process in getting the phone tweaked and with all the applications and setting back to where I had them. So, I've been holding out and saving factory reset as one of the last resorts.
The other last resort is to root the phone, because apparently there are some apps that might be able to reset the battery counter that will only work on a rooted phone. However, again in my research thus far, I haven't identified anyone with a rooted phone with a similar problem who has had succeeded in solving the problem.
Perhaps this weekend if/when I have the time and patience I will attempt one or both of the above. It's just that I have such low expectations of success that am reluctant to start down those paths.
If you, or anyone else on this forum can point to any experiences where these methods actually worked for someone in this same or similar situation, I would very much appreciate if you could direct me to the appropriate thread.
Thanks again very much for your input, and your further assistance and suggestions would be most appreciated.
Best regards,
Ron
No problem. I just try to help out where I can.
I can't say that I have had any of these issues. I understand the issues with backing up, but if you install twrp, you can create an entire backup of your phone. I've done it many times before without issue, and if resetting it doesn't work, you can still go back to your original set up.
It seems like you may be a pioneer in this particular issue. I hope you figure it out. Both for yourself, and for others who have this problem in the future.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
sireniankyle said:
No problem. I just try to help out where I can.
I can't say that I have had any of these issues. I understand the issues with backing up, but if you install twrp, you can create an entire backup of your phone. I've done it many times before without issue, and if resetting it doesn't work, you can still go back to your original set up.
It seems like you may be a pioneer in this particular issue. I hope you figure it out. Both for yourself, and for others who have this problem in the future.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again sireniankyle!
I used to like being a "pioneer", but as I get older now I just want my stuff to work, and don't have the time or the patience to go where no man has gone before Nevertheless, I absolutely hate to admit defeat, and now that you've turned me onto twrp (do I have to root first to use it?), then perhaps that will make the experiment less time consuming, so I may try this weekend if time allows.
In the meantime, the phone continues to function normally in every other way. I simply carry a couple fully charged batteries in my pocket throughout the day, which are of course 100% charged via my wall charger, but show as 58% as soon as I put them in the phone, and then die at approximately the rate one would expect from a 58% charged battery! Weird huh?
Best regards,
Ron
Was given a Skyrocket the other day which suffers from the same kind of problem (had massive water damage), but the battery percentage is stuck at 0%. So of course it will not even boot up. (Fully charged the battery in a wall charger.) Only thing the power button will do is vibrate the haptic feedback given at first power on, no screen activity. Funny thing is it'll go into Download mode perfectly normally and sit on the Odin mode screen till I assume the battery dies. However it will not go into Recovery mode. Plug in a USB charging cord to charge block or a port on a PC and the phone powers on and works perfectly fine, though forever stuck at 0% battery.
So the only thing I can think of to quickly get around this is without solving the problem, if in fact it can be, is to get a charging case. Like such, for example. http://http://www.ebay.com/itm/XPAL-Galaxy-S2-Skyrocket-PowerSkin-Case-i727-Extended-Battery-Gel-Cover-OEM-New-/310903753323 Had one similar before for another model and when installed it shows as if the phone is charging. So in theory will work for me, though powered strictly by the cases battery. Should work for you even better as you'll get the cases battery life then your own 58% worth of battery life. Edit, just realized when the last post was made, you probably have a new phone and moved on by now.
**I'm going to try to craft myself a homemade powered case yet, have tons a batteries kicking about.
I know, it's an old device but it still works (mostly). It's a hobby.
Having owned one of these devices some years back I've never encountered this particular issue and finding no joy through Google search (of course this tiny lagging arse netbook doesn't help) I thought I'd try the Q&A thread and hope there's enough old timers that still tinker with this device paying attention.
* Having this issue on two separate batteries, one new (considering however long
it was on the shelf) and the one that came with the phone. Both fully charged when powered off
over a period of approximately 8 hours.
* Have the OEM Samsung USB charger and cord.
* Running SlimLP 5.1.1
I've read on a Droid forum that a similar issue on their device was due to the phone not actually powering off completely. Any other skyrocket folk ran into this? With apologies if this is a duplicate question hidden somewhere within the many pages of this forum of which my crappy netbook cannot fathom the depths of.
Thanks!
Update: I suspect I have a faulty USB port or some other hardware issue. No reason to believe it would be software related with the power off. The phone was purchased "remanufractured" and I noticed a crack in the plastic frame near the volume keys that may be a telltale sign.
Hello!
Out of the blue a couple months back my 7 pro turned off while charging. I have read multiple posts of other people with a similar issue but mine seems to be different.
I also experienced my battery wasnt doing too good after a few years so I decided to change my battery and my usb c port in case that was causing the issue but even with the new port it keeps happening.
What could it be? is there any way to fix it? I just did a factory reset using the system assistant but if there is any other way that cleaner deeper I would. I just dont think my device will be recognized by adb so if anything it would be via wifi.
Please I would love any insight to keep my phone alive a bit longer, other than that its in a pretty good shape with a new working battery!
THANK YOU IN ADVANCE!