Related
This sucks... out of the blue my touch screen went all kinds of screwy on me. I'm gonna list everything that is going wrong...
1. When sending a text I can see the letters along the bottom of the keyboard scrolling back and forth really fast, as if I'm dragging my finger across it.
2. When on any of the home screens, it's acting like I'm pinching it, like the new sense screen selector thing keeps zooming in and out but I can't select anything.
3. I can't select items on any of the home screens, it is action like I have my palm resting on it or something...
4. When I select something on a menu, it acts like the input is a couple of inches below my finger (i.e. I select power off, it selects turn off mobile network)
If I press the power button to turn off the screen, I can press it again and ulock it, I have full functionality for about 5 seconds, then it freaks out again. This seems to be consistent, however annoying to have to do this all the time to send a text message.
This first happened while using the latest ChronosDroid ROM (CronosDroid_2.1.2), I reflashed with VillainROM 12.0.0 twice, and once with the newer RCMixV10, the symptoms are the same accross all ROMs, the only similarities is that they're all v 2.1 with Sense. I did a wipe of everything before each install.
I am going to try going back to v2.0 with some other ROM (probably SenseHERO-2.1-090610-B5, cuz I liked that interface...) I'll post back if that fixes it... If it doesn't, what can I do? I really like this phone, I hope it's not busted...
***Edit***
Purchased new digitizer and replaced it, all is back to normal.
I had this problem with cronos froyo, wiped everything and flashed fusion rom 6.1.1 and hey presto, everything was fine. Try it it may work for you aswell if not, something more sinister may be at work :$
Sent from my HTC Hero using XDA App
I'll give that a try. I had flashed to that version before to test it out, but that was before the screen was all messed up. I used the hard OCed version to 710, I'll try the SOC version this time and see if I have better luck.
I did flash with the aforementioned sense hero, and it is still a little bit messed up, but it doesn't seem as bad... I wonder if the OC from the Froyo is partly to blame. This is just so random... That is the only link I can think of. If the Fusion 6.1.1 is the cause, how can I make sure the CPU is back at it's default frequency? I never use any OC tools...
K, response is a little better but still jacked. I think I have a nand backup thing from before I installed Froyo, I've never had to restore a backup before, is it a bad idea to restore a backup from v2.1 on a 2.2 ROM? Or should I restore the backup and reflash to something else?
Restoring to a 2.1 from 2.2 will be fine mate, which Rom is the 2.1 you have as nandroid restore?
Sent from my HTC Hero using XDA App
Unfortunately this is a hardware problem. I have the same problem and after searching for a solution, I understand that this is something about display's touch part and you have to return it to HTC to change it.
In my country there is no valid HTC center and I cannot trust lcal repair shops so I have to deal with it and change my beloved hero in near future.
But for now, after installing different ROMs I find out that the best keyboard is default HTC sense keyboard and I dont know why. Currently I've installed Froydvillain 1.2.2 and use HTC_mod keyboard and it almost works for me with a bit struggle.
daashali said:
In my country there is no valid HTC center and I cannot trust lcal repair shops so I have to deal with it and change my beloved hero in near future.
Click to expand...
Click to collapse
Just do this yourself. You can buy the touch window off eBay for £25, and replacing it will take 20 minutes - see youtube for videos.
Have had same problems which then lead to the bottom 1/2 to 1cm of my screen becoming completely unresponsive. I managed to get my screen back to perfect working order without replacing it at all as this seems to be caused by the screen slightly coming away from the frame.
I detailed how i sorted it in this thread:-
forum.xda-developers.com/showpost.php?p=7710742&postcount=99
I had this problem with CMH-1.4.3 (Vanilla). I did a nand restore to VR12 but the same happened. Then I realised that the screen was a little up from his "standard" position let's say, if the screen is normally like this
______ <-screen
mine was slightly up (diagonally) at the top
_____-
I pressed the two upper corners of the screen with my fingers and everything went back to normal
Try this first, and then if you want, the Hairdryer solution
to all guys having the same issue, did you guys try to fully wipe & re partition your sdcard? try it & let see it still having same issue. best try do a clean flash of rom.
wrong forum
this is about developpement
thantos2024 said:
Have had same problems which then lead to the bottom 1/2 to 1cm of my screen becoming completely unresponsive. I managed to get my screen back to perfect working order without replacing it at all as this seems to be caused by the screen slightly coming away from the frame.
I detailed how i sorted it in this thread:-
forum.xda-developers.com/showpost.php?p=7710742&postcount=99
Click to expand...
Click to collapse
Interesting indeed. I did not see that my screen was raised at all. I have formatted, used a new microSD thinking it could be anything. When the screen goes wonky, I can set it on the table and it will continue to type in random characters until I hit the power button.
This isn't isolated to one area of the screen though, and pressing the phone together making sure the screen isn't raised does nothing to fix it. I think the digitizer is just going on vacation. Laying it down, it will keep typing in letters, if I hover my finger about 1 cm from the screen it will sense that my finger is there and interrupt the auto imput fuction that has been enabled, but doesn't stop it permanantly until I press the power button and unlock it again, then it all starts over.
I've taken the device apart and reseated everything and it didn't help. I think I'm going to take a chance and order a new digitizer from eBay. I really like this phone, don't want to have to get a new one.
zorxd said:
wrong forum
this is about developpement
Click to expand...
Click to collapse
I didn't see a support forum. Is there a better place to ask about this kind of thing on the Hero? I thought it was a software problem, which is why I posted here.
p0wd3r said:
I didn't see a support forum. Is there a better place to ask about this kind of thing on the Hero? I thought it was a software problem, which is why I posted here.
Click to expand...
Click to collapse
Maybe this section:
Hero, G2 Touch Q&A
For all your questions concerning the HTC Hero, T-Mobile G2 Touch
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=511
[FIXED]
zorxd said:
Maybe this section:
http://forum.xda-developers.com/forumdisplay.php?f=511
Click to expand...
Click to collapse
Ah, thank you. Again wasn't sure if this was a bug in the rom, or I screwed up the hardware or something.
On a lighter note, I ordered a new digitizer from eBay for $65, got it in today and replaced it and it's back to 100% functionality!!!! w00t!! Thank you all for your help and suggestions, XDA is the best thing to hit mobile phones since the wheel! I'll update the title of the first post to notate that it is fixed.
Hello xda friends!
Yesterday i left my optimus battery go to a full discharge, later when it was on full charge i noticed that the search physical button backlight was gone...just the menu, home and back physical buttons are lit.
I`m on LOL v2, but i don't know if it's a rom related issue.
Also the touchscreen have one stuck pixel, and the anoying dust problem.
Someone has experienced to lose physical buttons backlights?
Time to ask for Warranty?
Uhhhh , I think you should first reinstall a stock firmware through KDZ ( that should also get rid of custom recovery me thinks ... not sure , you might want to considers asking other about this as well ) .
But either way , yeah I think you should go into warranty with your phone. But don't forget to send it in it's most stock form
So I was using my camera LED as a flash light yesterday for a really really long time. Like 80% battery to 3%. Toward the end my power button quit responding so I had to pull the battery to even wake up the phone (could have called it but I didn't know it was the power button). Anyways it's still under warranty but it's rooted and I have Phone Bricker 2.7 installed. I don't mind sending it in to Samsung for a warranty (I got it late September or whenever the I777 came out last year) but I think I need to order a jig first and reset the flash counter and reflash stock OS (which I can find on the forum).
I was seeking alternatives to make it usable because I'm going to AZ this weekend and would prefer not to have to temporarily return to my old Nexus One while I order my jig and stuff. I found an app called like AnyLock or something.. (I removed it already). It would allow me to use the volume rocker to wake up the display but it seemed like it only worked if the phone just recently went to sleep. After 10 minutes or so the button wouldn't wake up the phone and I'd have to plug in a charger or something.
I purchased WidgetLocker which claimed to allow this sort of thing too. Set it all up and it did the same thing.. wouldn't respond after some intermittent time after the display timed out. Well that and it's also waking up the display automatically (even sitting here on my desk, not even touching the phone) a three or four times a minute.
Any suggestions on something to allow for temporary wakeups? I was running CM7 on my nexus 1 and I was able to wake using the trackball. Phone Bricker doesn't seem to give me any options like using the volume rocker.. I should be able to use the CWM app to reboot into recovery mode without having to do the power button thing to flash a different mod if maybe CM has a volume rocker option.. or any other mod.
I don't have much help for but can tell you that aokp has volume rocker to wake screen option.
Jemack said:
I don't have much help for but can tell you that aokp has volume rocker to wake screen option.
Click to expand...
Click to collapse
That is exactly the kind of help I'm looking for! I love Phone Bricker but it's the only mod I've tried on this phone.. I'd much rather flash the OS than mess around with the N1, I'll save that for when I'm ready to ship it in for warranty.
Same thing happened to my old i777. Temporary fix is to use go launcher and go locker. Go into setting for go locker and set screen wake when volume is pressed. Att gave me a new phone with no issues
Sent from my SGH-I777 using xda premium
You guys purchased them as new, rip them off, beat them up, flash/install custom ROMs/kernels. Screw up big time then return them and get the new ones.
LOL
No wonder why those providers just keep increasing the fees and fares.
votinh said:
You guys purchased them as new, rip them off, beat them up, flash/install custom ROMs/kernels. Screw up big time then return them and get the new ones.
LOL
No wonder why those providers just keep increasing the fees and fares.
Click to expand...
Click to collapse
I didn't drop it or anything! I might have shaken it up some using it but nothing terrible.. Anyways if it was getting the phone too hot by running the flashlight app too long, I could have done that with the stock OS and a flashlight app from the market so I'd still warranty it I just wouldn't have to do more work to cover my warranty voiding tracks. I just wanted to post all info I thought could have been relevant because who would help me if they had to ask me a ton of questions first? But you know, I just did the go locker solution jthatch12 suggested and it's working fine.
I don't know a fix, but I have a potential workaround. CM7 and CM9 both allow you to wake up the phone with the volume keys. An app called Virtual Button Bar will allow you to put the phone to sleep from any screen (as long you're rooted). It costs a couple bucks but it works really well.
Sent from my SGH-I777 using Tapatalk 2
o8oedo8 said:
I didn't drop it or anything! I might have shaken it up some using it but nothing terrible.. Anyways if it was getting the phone too hot by running the flashlight app too long, I could have done that with the stock OS and a flashlight app from the market so I'd still warranty it I just wouldn't have to do more work to cover my warranty voiding tracks. I just wanted to post all info I thought could have been relevant because who would help me if they had to ask me a ton of questions first? But you know, I just did the go locker solution jthatch12 suggested and it's working fine.
Click to expand...
Click to collapse
When you get around to unrooting your phone, do the mobile odin reset back to stock. That'll put your phone back to stock and in a bootloop. Then take your phone back to att and tell them something failed during the update to ics. Worked for me. My power button stopped working randomly one day for no reason. My phones are babied. Always kept in a case
Sent from my SGH-I777 using xda premium
I just bought a used Rezound and activated it. ESN was clean and the phone is near mint.
I came from an Incredible and the capacitive buttons on it were very responsive.
The ones below my "new" Rezound's screen hardly respond at all. I have tried using more of my finger and pressing in different places, but I can't seem to get the home, menu, back or search key to work when I want it to on the first press.
It's really frustrating to have to set up my accounts and stuff when I have to press the back key 5-15 times to get it to react once.
Is this normal? Did anyone else experience this learning curve or is my phone broken?
I have searched and searched and others have mentioned similar issues on other phones with custom roms. This phone has been S-OFF and flashed with stock RUU 3.14.605.12.
Could reflashing the RUU or maybe even another ROM help?
Thanks for your help!
blazin_phattys said:
I just bought a used Rezound and activated it. ESN was clean and the phone is near mint.
I came from an Incredible and the capacitive buttons on it were very responsive.
The ones below my "new" Rezound's screen hardly respond at all. I have tried using more of my finger and pressing in different places, but I can't seem to get the home, menu, back or search key to work when I want it to on the first press.
It's really frustrating to have to set up my accounts and stuff when I have to press the back key 5-15 times to get it to react once.
Is this normal? Did anyone else experience this learning curve or is my phone broken?
I have searched and searched and others have mentioned similar issues on other phones with custom roms. This phone has been S-OFF and flashed with stock RUU 3.14.605.12.
Could reflashing the RUU or maybe even another ROM help?
Thanks for your help!
Click to expand...
Click to collapse
what i would do, seeing's how its a used phone, is to ruu to the latest release (global) and test before flashing anything custom.
if its not working on a completely stock rom, then its going to be a H/W failure.
test it out and report back please.
Worst comes to worst, you can use AOKP which has a onscreen navbar.
Sent from my HTC Rezound
Or use Button Savior from google play
Sent from my ADR6425LVW using xda app-developers app
Hello XDA,
I apologize in advance if this topic has been covered, but I cannot seem to find any threads describing the problem I have.
Please read below the post that I have put in the Noob Guide thread... After attempting to root my Note for the first time, somehow during the initial process the touch-buttons have completely stopped working
"I don't know how or why, but the touch buttons on the bottom of the phone are no longer working. Is it broken? I was using the stock ICS version on the Note, decided to root it using your guide. I followed the steps, but it locked up on the Samsung logo on bootup. So I then went to restore the phone to stock and try again, and now the buttons are not working at all??? What happened??
By the way, the touch screen is working totally fine. I just cannot press the home, menu, back and search buttons. Also, when I followed the process to bring the phone back to stock, the phone would hangup during boot as well. It would freeze this time on the ATT white and blue logo screen. I followed the advice by Da G and did a factory wipe, and then it finally booted up, but no buttons!!! How do I fix this??
So I've been experimenting as much as possible to try and figure out where I went wrong in this process to break the capacitor buttons. I've tried flashing the stock rom through Odin several times, still no buttons. Without the use of the buttons, I've been able to flash CWM and root the phone, and then was able to flash a rom with no problems at all (since CWM only uses the volume and power buttons to function). I chose a random rom and flashed it, Novena (Alliance Rom), and that process went smoothly. But I still have no touch buttons!!!! What happened??
Is this an unfixable problem? Considering I've been able to do anything with the phone except for touch the buttons, it doesn't seem like it would be a software problem.. But what could I have done to break the buttons? I'm so frustrated.. am I going to have to claim a new phone through insurance? If so, I'm pretty damn scared of trying to root the phone again!"
I would take a look at the ussd codes and see if there is one to test this specific setting!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Thank you for the reply! I looked through all the USSD codes on this thread: http://forum.xda-developers.com/showthread.php?t=1953506&highlight=ussd+code
I could not find anything that would help me. In CWM boot menu, there is a "Key Test" feature in the Advanced section. When I choose that, it registers "Key: 114, 115", etc. when I press the volume up, down and power buttons, but there is no reaction when I touch the capacitive buttons. It says that you have to press "Back" to get out of this test mode, so I'm stuck in the mode and have to reboot since the stupid button doesn't work. >_<
I'm so frustrated. Has anyone ever had this problem?? It seems so bizarre...
that happen to me with my brand new skyrocket.something went during root process.i couldnt fix it.i tried everything.i end up calling att .they replaced it with refurbished unit.good luck.you must have done something wrong while rooting.because samsung phones are hard to ****up.i know what i did.i ran a app from playstore to unlock sim after i rooted it.thats what messed up my buttons.
mintu123 said:
that happen to me with my brand new skyrocket.something went during root process.i couldnt fix it.i tried everything.i end up calling att .they replaced it with refurbished unit.good luck.you must have done something wrong while rooting.because samsung phones are hard to ****up.i know what i did.i ran a app from playstore to unlock sim after i rooted it.thats what messed up my buttons.
Click to expand...
Click to collapse
Aw man, that's discouraging. I can cough up the $200 and get a replacement phone through insurance, but now I'm scared to root it again! I don't know what I did wrong.. I followed all the steps I was supposed to as far as I know.
If I get a replacement phone and try to root it, if this happens again the warranty is void right? So I'd have to go through insurance again to get a new one?
only time i have seen this happen was with a friends epic touch. he flashed a rom for different galaxy sii device. it booted and only problem was buttons not working. you do have a note i717? just checking. you could flash a rom that you can enable navigation bar with onscreen buttons. i am running eclipse and it has this feature and i dont have any problems with rom.
s89281b said:
only time i have seen this happen was with a friends epic touch. he flashed a rom for different galaxy sii device. it booted and only problem was buttons not working. you do have a note i717? just checking. you could flash a rom that you can enable navigation bar with onscreen buttons. i am running eclipse and it has this feature and i dont have any problems with rom.
Click to expand...
Click to collapse
Thanks for the reply.. That is actually a good idea, I will have to try that if the buttons break again. I say "again" because **update** the buttons are magically working now!! Wtf?? I received a phone call and talked for a bit, set the phone down and when I picked it up again the buttons are all working like nothing was ever wrong.
Of course, they magically started working AFTER I called Assurion and ordered a replacement... Ugh. That is the second time I've ordered a replacement and cancelled it.
Another update...
They're broken again. UGH. No idea why or why they started working for a few minutes. I'm getting that replacement phone and I'll try again. I really hope it doesn't happen again...