I've noticed that whenever my One overheats or gets too warm, the screen will start to tweak and register hundreds of "ghost touches", if I could call them this.
For instance, the home/back, power, volume, and screen will register as being activated, which in turn causes the phone to (a) take a screenshot, (b) switch between desktop and recent apps, launch GoogleNow, etc. These actions happen fast and don't stop. The phone registering even results in the vibration feedback tweaking, so the phone is vibrating, switching screens/activities, screenshotting, and just generally tweaking all at once.
The only way to stop it is to turn off the phone using the soft reset method, hitting the volume down button on reboot to get into quick menu, shutting it down, letting it cool off, then rebooting.
Anyone else having these issues?
Firmware is the latest update, but I've been having this problem since the last build. Hoped update would fix it. OR stay in A/C rooms haha.
TL;DR: When One begins to overheat, the capacitive home/back buttons, side buttons, touchscreen itself become completely unresponsive and registers hundreds of "ghost" touches.
I have the same problem!
Sent from my HTC One using xda app-developers app
Maybe it's the new firmware... When I flashed the firmware, my ROM wouldn't respond on the touchscreen at all but TWRP did so I flashed ARHD and it's fine now.
Sent from my HTC One using Tapatalk 4 Beta
When it's happened (2-3 times) I was using ElementalX 2.4 as kernel, now with the stock one everything seems ok
Sent from my HTC One using Tapatalk HD
EtherealRemnant said:
Maybe it's the new firmware... When I flashed the firmware, my ROM wouldn't respond on the touchscreen at all but TWRP did so I flashed ARHD and it's fine now.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sounds more like the touchscreen driver changes
Related
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
ummm the power button on the nexus one has an incredibly high failure rate, all over the forum here. its a design defect from the factory. that's why it has always been recommended to root the device immediately, and use trackball wake, so you avoid using the power button as much as possible. you have to send the device to HTC for repair, that's your only option...
Thanks for the information. I will have to look into repairs.
You are already running a rooted rom with track all wake. Use it. To reboot the the phone use quickboot. At this stage you really don't need the power button on your phone.
pcflet01 said:
... now that I have installed CM7.
I push the power button and the screen turns on and then back off almost immediate
Click to expand...
Click to collapse
This is a problem with CM7. Most advise turning off the screen off animation if it becomes a big problem for you. Make sure you are using the newest nightly and hope for a fix. I don't know if the RC's have this problem, but I would bet it appears on the 7.0.3 release.
At first glance that seems to have helped. Thanks for the advice!
No problem.
Also you can use widget locker to lock the screen then the trackball to wake, with that and quickboot I don't even touch my power button anymore. Although your problem doesn't sound like a broken power button so in your position I would switch ROMs and see what happens.
pcflet01 said:
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
Click to expand...
Click to collapse
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
As others have mentioned, this does not sound like a powerbutton issue, because the powerbutton still turns on the screen. The problem is that the screen turns off immediately after it turns on.
When you flashed 7.0.3, did you come from a previous CM verison? From stock? My first suggestion would probably be to wipe the /system partition (in CWM, it is under mounts and storage -- with Amon_RA, you need to find a flashable zip to do it) and reinstall CM and gapps. This will not cause any data loss. Sometimes, if you install a new ROM over an old one, the upgrade script in CM can get confused and carry over files that aren't supposed to be carried over. The system wipe fixes that.
I've been using this RC since it came out in late June. Only this week did it start flipping out on me.
Sent from my Nook Color!
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
bassmadrigal said:
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
Click to expand...
Click to collapse
I'm currently using S2E for apps2ext and some data2ext. How would a system wipe and reinstall interact with that? I'm a bit nervous on that front.
A system wipe shouldn't change any of that. It is one benefit of using S2E as it is a standard app that is stored in the /data partition without any changes to the /system partition.
Anyway, to be safe, it is a good idea to do a nandroid backup anytime you are doing something that involves the majority of the features in recovery.
It's a hardware problem for me. Failed completely as of today.
Sent from my Nexus One using Tapatalk
CM7 7.1.0
My power button seems to be in the process of completely failing. The new CM7 update to 7.1.0 has made it possible for me to lock the screen without using the power button using the "Notification power widget" -> "Go to sleep". Now the only times I have to use the power button are to shut the phone down or wake it up, which seems to be easier when the phone is plugged in to a wall charger. Are there any simple apps for shutting the phone down and maybe waking it up at a set time?
The only reliable trick I found to turn it back on was to plug into the wall and take the battery out/in a few times till it vibrated.
I ended up getting a replacement phone and then I sent the Nexus to HTC. They quoted a $55 repair cost off warranty which my credit card insurance would've covered, but when I asked for an invoice they offered to just waive the charges. Finally over a month later it came back fixed.
The app Easy Reboot can shut the phone down.
Sent from my Nook Color!
I also use an app called Lock Screen, which just locks the screen. I have it stored in my dock, because I don't like the space being used in the notification widget.
CM7 has an option for one of the items in the notification tray widget to be a lock screen button.
cmstlist said:
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
Click to expand...
Click to collapse
THANK YOU!!!! This has been driving me crazy. Turning off the screen-off animations did nothing, but turning off the screen-on animation seems to have fixed the issue. My power button is toast (my new power button ribbon cable just arrived... time for surgery), and I've been using the trackball to wake my phone. Before the power button died, it did the same thing. I'm using CM7.2. I installed it after rooting and went straight to cm7.2 from stock, so obviously the cyanogemnod crew haven't fixed the issue since 7.0.3 when this thread started.
I got a confusing issue with my HTC One (T-Mobile Germany). When I sometimes push the power button to turn the device into sleep it directly wakes up by itself. So this issue is at stock (s-on, locked bootloader..) and custom rom (ARHD, TrickDroid , S-Off). It only works correctly on ViperOne with disabled capacitive buttons backligt. If capacitive buttons backlight is enabled, it appears on ViperOne too.
Got anyone a solution how to fix this problem?
bLubhimselF said:
I got a confusing issue with my HTC One (T-Mobile Germany). When I sometimes push the power button to turn the device into sleep it directly wakes up by itself. So this issue is at stock (s-on, locked bootloader..) and custom rom (ARHD, TrickDroid , S-Off). It only works correctly on ViperOne with disabled capacitive buttons backligt. If capacitive buttons backlight is enabled, it appears on ViperOne too.
Got anyone a solution how to fix this problem?
Click to expand...
Click to collapse
I also have this issue with my HTC one.. have posted here b4 but no one replied..
I got that issue on every HTC device I owned. The Sensation, OneX and One. Not even the HTC support can help me with that.
Sent from my HTC One using xda premium
You hit the power button, screen switches off, and then on?
I have that, but I only noticed it recently. Doesn't mean it didn't exist before. I dunno.
Yes I push the power button and the screen switches off and sometime on again. I had that with every HTC device having capacitive buttons. The only solution I found was flashing to Viper Rom and disabeling the capacitive buttons backlight.
Sent from my HTC One using xda premium
bLubhimselF said:
Yes I push the power button and the screen switches off and sometime on again. I had that with every HTC device having capacitive buttons. The only solution I found was flashing to Viper Rom and disabeling the capacitive buttons backlight.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
you said that you had this issue with every htc device you had... well check my phone history, i had many htc devices, and never had this issue, but for you it seems like some app you are installing is causing this issue...... if possible, do a factory reset( I know its hard ), and then check if the problem persists... you can claim a warranty then...
mathrania said:
if possible, do a factory reset( I know its hard ), and then check if the problem persists... you can claim a warranty then...
Click to expand...
Click to collapse
With my Sensation I did that... got a new device two times and it happened again and again. But this is only if capacitive buttons backlight is on. Since I deactivated it in viper rom it never happened again. But I'd like to use Stock Rom.. and I love my One... dont want to claim a warranty again :/
Sent from my HTC One using xda premium
Are u using Juice Defender? I had the same problem after installing JD and it went away after uninstalling it.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developer
looks like i got a lemon, screen will not turn back on however device continues to function. The touchscreen even works but you can't tell what you are clicking on.
Only way to get back to functional is to pull the battery, only happened once last week but in the last two days i've had to pull it 6 times or so.
Just posting this up in case someone else starts having the same problem. I've got a replacement being shipped out this week.
You are not the only one. Mine does it from time to time
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Has any one had problems with maps as well
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I might have had this happen last night. Black screen, buttons lights would only flicker once quickly when pressing the power button. Pressing and holding the power button did not cause a reboot. I did not try any screen action as I could not see anything. Had to pop the battery to get the device back to working.
--pat
I got my replacement, and it still does seem to have this bug to some extent, however, this phone seems to be able to get out of the screen black if something else triggers it.
For instance, I got a phone call, and that brought it out of the black-out. Another time i just kept pushing buttons and it finally woke up.
Hopefully it's just a software bug??
For the second time in a few months, my home button and power button both became unresponsive. This happened previously for about 2 days and put of no where both starting working as normal. Has anyone else ever experienced this and no a solution to the problem? It seems to be a software problem, and this always seems to occur following an OTA update, which AT&T pushed one the other day.
Sent from my SAMSUNG-SM-G920A using Tapatalk
crisg723 said:
For the second time in a few months, my home button and power button both became unresponsive. This happened previously for about 2 days and put of no where both starting working as normal. Has anyone else ever experienced this and no a solution to the problem? It seems to be a software problem, and this always seems to occur following an OTA update, which AT&T pushed one the other day.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
I also find that these buttons occasionally work again, but only for a few minutes then they go back to having no response. Also sometimes when I hit the home button Google app pops up, even tho I have Google Now on Tap disabled.
Sent from my SAMSUNG-SM-G920A using Tapatalk
I have seen multiple other people experiencing this issue on reddit and here on XDA too. What happens is that when I attempt to unlock, there's no icon at the bottom-center of the lockscreen. Sometimes there will be one with an unlocked lock icon, but I'm incapable of swiping to the key-guard or using my fingerprint to unlock the device. During this, the home button has feedback by vibration but nothing happens. A bit later it'll act as if it's catching up and will then unlock automatically. Other times if I push the power button after trying to unlock nothing will happen until after this delay in which would unlock the device (after trying to fingerprint unlock) and then suddenly it acts like I had pressed the power button.
I've tried removing and re-adding the fingerprints. I'd really rather not have to factory reset to see if this fixes the issue. I'm on completely stock rom, not rooted, etc. Completely vanilla.
Any ideas?
Running into the very same issue. Additionally sometimes at the end of phone calls the dialer becomes unresponsive and cannot hit the hang up button. Then the system seems to catch up...
Any help or ideas appreciated.
Phone completely stock, had no similar issues since I purchased it 6 months ago..
Sent from my SGP321 using Tapatalk
Update : Read in a forum that pocket mode may be the culprit. I disabled it under Settings / Advanced. The screen lock issue seems to have disappeared. The dialer issue is also not there any more.
Hope this helps...
Sent from my SGP321 using Tapatalk