Related
Hi all
I bought a JasJam about an year ago, and it has been working fine.
About 5 weeks ago, I flashed it with HardSPL 7, Radio 1.50 and Schap's 3.60a.
It worked fine till yesterday when suddenly following buttons stopped working: IE, Messaging, Left & right soft keys, start, ok, green & red buttons. Rest of the buttons, keyboard etc are fine. There was no impact, no "sudden movements". The buttons just stopped working! I mean, one minute they were fine and the next minute, they were screwed.
I have done following to fix this (in order)
1. Soft reset
2. Hard reset (which shows that there is no problem with the hardware)
3. Flashing with Schap's ROM again
4. Flashing with 3des ROM
5. Flashing with Sleuth's ROM
6. Flashing with Cingular (WM5)
And still, no use! Buttons still don't work.
Any help would be highly appreciated.
Does the silence says: You have to live with it.
???
More Updates :s
Now I am not able to delete anything I type. :s Not even while using the onscreen keyboard! I can see that when i tap on the backspace button, it highlights, but the text doesn't get deleted! I have tried this in almost any place which allows you to enter text. :s
I think I will go back to my original shipped ROM and bootloader. :S
Strange stuff happening! Downgrading to olipro 1.10 has solved the backspace problem. How can a bootloader affect a function like that? :s
Back to shipped bootloader and ROM (not the radio) Still the buttons are not functional.
I also opened up the phone and cleaned the buttons, made sure all connections are properly in place. Put everything back together, and no, the buttons don't work.
What do I do?
I have tried a thousand other bootloaders, radios and ROMs... But these buttons wouldn't work?
Where are the geniuses like oli?
I have the exact same issue.. I have pretty much tried all SPL/Radio/ROM/App combinations, including the 1.01 IPL, original SPL, and WM5 that ships on the Tytn from HTC... And, just like you, the keys sometimes work, and then suddenly they stop. Restart or hard-reset seldom brings them back. I know it's not hardware issue because holding down the "-" and "-" keys while resetting always works. I also observe the LEDs on the front panel go all whacky. Sometimes the power LED, which normally blinks on battey power turns on and stays that way; sometimes it doesn't come on at all.
My guy feeling is that this is not ROM related, and somewhere along the line while I was enjoying the "flash-o-palooza", something got corrupted in the flash memory.
I am now looking for a method to do a "harder-reset" that will clean out the whole thing, reflash the bootloader and build it from scratch.
I think the buttons are not properly passing interrept requests to the OS, which as you correctly mentioned is a flash memory / bios problem. (I don't know a lot about hermes architecture)
HTC provides a diagnostic sd card in which you can check if the buttons work fine. I will try to get my hands on one of those.
Did you try going back to Wm5?
whistler4ever said:
Did you try going back to Wm5?
Click to expand...
Click to collapse
Yep.. Many times.
any luck with this? can u get to bootloader mode with the keys?
not believing that it would be hardware problem, I disassembled already some times my TyTn and I did not have sucess. If someone have sucess, post here please
the only obvious thing is that the keybddr.dll driver is not be loaded properly. how do u normally load the rom's? do u let the software boot the phone, or do you put it in bootloader mode first?
as I use a Windows Vista, the ROM upgrader have to be done in the Bootloader Mode
But, Sometimes the buttons works, and in next minute, they die again
its a misterious
Hardware buttons also not working
I am also experiecing this problem. Occasionally the hardware buttons will work, then if I open the slider they stop working. I have also tried updating firmware etc.. but it hasn't helped. The buttons will work if i press the left and right keys while pressing the reset key to do a hard reset. They work every time doing this, so it seems like a software problem. But I don't understand how a s/w problem like this can remain there even after firmware update and hard resets.
I have opened the phone up several times, because I have another problem, or two. As much as I love the phone it has been totally unreliable. It shipped with the LCD not working, I diagnosed that as a faulty ribbon cable, which I replaced, that made the LCD work. But then the earpiece speaker and the front camera didn't work. Now this problem... this is starting to drive me crazy.......
Hi, I have the same problem, I think. Sometimes when I play games, browse the phone or slide down the keybord the buttons below the screen just stop working. I have also tried to flash different roms, but to no good. There is a temp fix thou but it work slow sometimes, if I scroll with the wheel for a bit(the scroll time varies) the button seem to work, but only for a little while.
Does anyone have any news on this issue, cause i can't use any program that need these buttons.
I also have this problem, I guess I'll have to send it in to get it fixed :|
Problem Solved
I have managed to resolve the problem. It started compounding which made me think that it had to be a hardware problem. The first symptoms were that the front bottom hardware keys stopped working. Then the LCD would not align properly after sliding the keyboard, so I would have a white bar at the top and/or left of the screen.
Next the top hardware buttons stopped working, and then finally all I had was a white screen with nothing on it.
I replaced the flex cable that connects the front of the phone to the main board and it has solved all of my problems. I had already replaced this cable when I first got the phone because the one that came was with it was faulty. Now after just a few months of use the replacement one wore out as well. It seems to be the weak link in the build of these phones.
crajoh said:
I have managed to resolve the problem. It started compounding which made me think that it had to be a hardware problem. The first symptoms were that the front bottom hardware keys stopped working. Then the LCD would not align properly after sliding the keyboard, so I would have a white bar at the top and/or left of the screen.
Next the top hardware buttons stopped working, and then finally all I had was a white screen with nothing on it.
I replaced the flex cable that connects the front of the phone to the main board and it has solved all of my problems. I had already replaced this cable when I first got the phone because the one that came was with it was faulty. Now after just a few months of use the replacement one wore out as well. It seems to be the weak link in the build of these phones.
Click to expand...
Click to collapse
I don’t think you got the same problem as us, if you check almost all the other button problem threads they are about the white screen but since we in this thread have not gotten any white screens or some of the other symptoms I'm quite sure it’s not the same. Also some with our problem have tried to change the flex cable but it has not fixed the problem.
*edit - I did not put the angry smiley on this post.
Me too!Anybody can soleve it?I found that when they aren't woring,we can touch on screen or press ok button on the left once or twice,they work again!
After upgrading to WM6, every works perfectly. But then, it seemed randomly, the display is blank/ all white, but I can the phone is still functioning, because i can tap on the screen and get the tap sound. Soft reset and hard reset doesn't work. I'm doing the hard reset blindingly since the display is showing nothing, guessing the key push (i pressed record-camera 3x then mail button). I'm pretty sure it did the reset because after about 30 secs I get the beep that comes on when the screen is showing Tap to setup your device.
I figured it might be a loose lcd cable, but if go into the bootloader, power+record+reset. The display works fine! Showing Serial V 2.07.
I took apart the BA anyways and made sure the lcd cable is firmly attached. It didn't work.
Sometimes the phone would go back to normal randomly, or if I let the backup battery drain, but not always. When it goes back to normal, the clock is always reset to 2004 12:00 AM.
Can anyone help me? Is it possible to have a loose LCD connector which won't be able to show normal display, but can show the bootloader normally? Or is it caused by something else?
Here are other things about my BA that may or may not be related to the problem:
-Can't use DOC_Repart to resize storage, I'm getting the FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed as described here http://forum.xda-developers.com/showthread.php?t=255585
-When upgrading the upgrade program can't detect my current OS version (showing blank under "Your device is about to be update from:"), but otherwise the upgrade works fine.
-I tried Helmi R0, PDA Viet , and xplode's 6.00 roms. They all give me the same problem
Thanks.
I am also experiencing the same issue... currently phone is at white scren, but using My Mobiler i can see my desktop and see that the phone is fully functional, just white screen so cant use...
Mine too. I can see the display working perfectly using SOTI pocket controller pro. So the phone seems to be functioning except for some reason the screen is showing all white screen.
cubangt, are using an extended battery or the standard battery that comes with the phone?
Have you tried flashing with a different rom??
Sorry, I fear my message won't be useful at all for you, but I'll post it just for the record. I hope you can find the solution to your problem anyway!
My BA now can't show anything but a white screen because of what I think is damage to the screen cable (while sliding the display the backlight goes on and off...).
But the cable is not loosely connected, it is sort of strongly bent at one point, and maybe some contacts got kind of cut. Now it does not work anymore, but some time ago switching it off and the on again used to do the trick: the display would be readable again (even though with annoying colours, stripes and so on). I don't think this is your case, but I'd like to warn the newbies like myself that they should care not to lose any piece while changing the LCD on their BA: I think I probably forgot about some sort of protection which could avoid damages to the cable in its movement.
As for the missing version number when upgrading, the same has always happened to me.. I think.
Ok, sorry for my English, I would have had some troubles with exposing these few silly things even in my mother tongue... bye... and good luck.
I tried 3 different WM6 roms. And if I remembered correctly this also problem also occurred for a brief while I downgraded to WM2003SE while trying to resize the storage(which failed).
Yeah I'm not sure if mine is a hardware problem, since I can always go into the bootloader and the display works fine there.
I have new info to add though. I found out I can reliably get rid of the problem by draining the backup battery. Now I have a new question, since draining the battery takes a while, is there a way to reset the phone as if the backup battery is emptied (and return my display to normal)? If I can find a way to simulate this, then I can actually use my phone again, even if I have to do this once a day.
Obviously soft reset doesn't work. And I don't wanna do a hard reset either. Maybe the experts here now what kind of data is reset when all batteries are completely drained.
Thanks for the help
hmmmm
quick thinking.....i was working on my phone tonight and came across this thread.....if not grounded properly it could be that you statically fried a component in the process?
17/9/2010 EDIT: With a lot of feedback from this thread and other threads, it has come out that, waking up the phone with the YES/CALL/SEND green button is BETTER than waking up with the NO/END/POWER red button for SOD reasons.
----
Hello guys,
You probably know I am actively in the Android HD2 porting community.
I am having the strangest touch screen problem. I am really experienced into winmo and android stuff. Please read carefully.There is a surprise at the end.
BOTH under Android AND Winmo my touchscreen works just fine after bootup.
It first started like this:
At first my touchscreen stopped responding when I hold no button to make a reboot/power off. I thought it was from the usual Android touch screen freeze related to g sensor. Then I realized that it was the same in Winmo! Holding no button ALSO caused touch screen to die even under winmo.
Then it started loosing touch after sleeping. My touch is ALWAYS working when I boot winmo OR android and works for hours if not put to sleep. But it stops working after putting it to sleep.
Frustrated,
I restored with spb backup. Didn't work.
I reflashed my winmo rom. Didn't work.
I made a hard reset. Didn't work.
I removed sd card. Didn't work.
I removed sim card. Didn't work.
I changed the date. Didn't work. (this was a strange fix for some blackberries)
I flashed original 1.66 Turkish rom, 2.07 original old radio, even original 1.42 SPL which makes this hd2 fully stock the day I bought it. Even made another hard reset. Still didn't work!
By this time it's obvious this is a hardware problem and needs warranty.
OK
THEN I FOUND THE STRANGEST THING:
If I wake up the phone with ANY hard button other than the NO/HANGUP button touch screen WORKS!!! (Yes/Send button under Android)
BELIEVE ME, I HAVE TRIED FLASHING REFLASHING RESETTING AND TESTED 100 TIMES and YES it is ALWAYS the same. This is not a random thing.
If I wake up my phone with No button under ANDROID OR WINMO, my touch doesn't work. But if I wake up with back button windows button home button yes button, the phone wakes up properly AND touch works. Android of course doesn't work with the original radio, so I wasn't launching Android with the last test.
HOW IS THIS POSSIBLE AT ALL?? It looks like hardware fault, but touch loss IS related to NO button!
I will send my phone to warranty anyway but it will happen after the holiday (not before mid september)
IF ANYONE have an issue like this, PLEASE post.
I just want to make sure this issue isn't related to Android porting. If it is, this might be an important info. Maybe it may help devs fixing the general touch screen and wake up problems. Also everybody TRY waking up Android with the yes/send button to see if it helps with your wake up or sod issues and provide feedback. Also it may help with the phone not responding after hangup in Android. There is something hardware going at the background with the no/hangup button. I know this issue is hardware fault but still may shed light to our problems with touch screen and wake up issues. Maybe there is something hardware or firmware inside the phone waking up the digitizer. I know that hangup/no/end button is internally different than the other buttons, something like it shares the power button function that is usually on the top of the device with other htc devices. (Mine is a european hd2 and the hangup button is not red) I also wasn't using an overclocking kernel.
Please think twice before posting, and don't post anything useless. I am absolutely no noob, you can search my previous 200+ posts. I wouldn't post anything unless I am definitely sure. And I have a feeling that this thread has the potential to help or make something come out. If it doesn't, no harm done.
since most of the time inwinmo or android the no or yes button pop up generally on the same side in both os's and , taking in consideraton it might be a hardware issue , i would say you issue might be a harsware issue undr the screen when you touch no...wild guess
I was the same problem.... but it is even worst for me now...
Before, at least work touch others buttons... now my touchscreen DON'T WORK. :-(
I suppose that it's a hardware problem :-(
memin1857 said:
Hello guys,
You probably know I am actively in the Android HD2 porting community.
I am having the strangest touch screen problem. I am really experienced into winmo and android stuff. Please read carefully.There is a surprise at the end.
BOTH under Android AND Winmo my touchscreen works just fine after bootup.
It first started like this:
At first my touchscreen stopped responding when I hold no button to make a reboot/power off. I thought it was from the usual Android touch screen freeze related to g sensor. Then I realized that it was the same in Winmo! Holding no button ALSO caused touch screen to die even under winmo.
Then it started loosing touch after sleeping. My touch is ALWAYS working when I boot winmo OR android and works for hours if not put to sleep. But it stops working after putting it to sleep.
Frustrated,
I restored with spb backup. Didn't work.
I reflashed my winmo rom. Didn't work.
I made a hard reset. Didn't work.
I removed sd card. Didn't work.
I removed sim card. Didn't work.
I changed the date. Didn't work. (this was a strange fix for some blackberries)
I flashed original 1.66 Turkish rom, 2.07 original old radio, even original 1.42 SPL which makes this hd2 fully stock the day I bought it. Even made another hard reset. Still didn't work!
By this time it's obvious this is a hardware problem and needs warranty.
OK
THEN I FOUND THE STRANGEST THING:
If I wake up the phone with ANY hard button other than the NO button touch screen WORKS!!! (Yes button under Android)
BELIEVE ME, I HAVE TRIED FLASHING REFLASHING RESETTING AND TESTED 100 TIMES and YES it is ALWAYS the same. This is not a random thing.
If I wake up my phone with No button under ANDROID OR WINMO, my touch doesn't work. But if I wake up with back button windows button home button yes button, the phone wakes up properly AND touch works. Android of course doesn't work with the original radio, so I wasn't launching Android with the last test.
HOW IS THIS POSSIBLE AT ALL?? It looks like hardware fault, but touch loss IS related to NO button!
I will send my phone to warranty anyway but it will happen after the holiday (not before mid september)
IF ANYONE have an issue like this, PLEASE post.
I just want to make sure this issue isn't related to Android porting. If it is, this might be an important info. Maybe it may help devs fixing the general touch screen and wake up problems. Also everybody TRY waking up Android with the yes button to see if it helps with your wake up or sod issues and provide feedback. Also it may help with the phone not responding after hangup in Android. There is something hardware going at the background with the no button. I know this issue is hardware fault but still may shed light to our problems with touch screen and wake up issues. Maybe there is something hardware or firmware inside the phone waking up the digitizer. I know that hangup/no/end button is internally different than the other buttons, something like it shares the power button function that is usually on the top of the device with other htc devices. (Mine is a european hd2 and the hangup button is not red) I also wasn't using an overclocking kernel.
Please think twice before posting, and don't post anything useless. I am absolutely no noob, you can search my previous 200+ posts. I wouldn't post anything unless I am definitely sure. And I have a feeling that this thread has the potential to help or make something come out. If it doesn't, no harm done.
Click to expand...
Click to collapse
BIt strange this one to be honest I think it may just be your device as there are now hundreds of users of android on the hd2 and this is extremely rare. Hopefully a dev will look into and find a possible solution but I doubt it. If I was you I would put it back to stock and send it off to HTC for a new one. Even if a dev manages to find the problem you will have a new or as new hd2
I have been trying and I must say that I sort of do share your experience. The most left button (referred to as yes) awakes the phone just right as where the most left (No) takes its time to start the phone. I haven't had any noticable touch issues that could be related to these hard buttons yet.. (I think)
But I do think you have a point.
Interesting, I had something similar. I was using elegancia rom v1 for the longest time, with all my android builds, no problems. Then I went to chunkydroid rom, and had a few issues, with multiple android installs (one of which was my original that was working before.)
Then I rebooted into chunkydroid, (windows), and had the same issue. It was strange. I tried a few other roms, same problem. Turned off the phone, next day, reflashed chunky again, and hyperdroid 1.1, no issues since. (Only difference, which I don't know if it's related, but again, might help, is that I was overclocking. I have since not let anything go above 998 in setcpu, and even removed all builds that were overclocking. I though it might have had something to do with it (and the phone wasn't warm at all.)
I have not been able to duplicate the problem since though (even with overclocking just to see). So I'm pretty stumped. I'm sure the devs will work it out.
I have taken to pressing the yes/send key to wake up my phone as it seems more consistent than pressing the end key. My theory is that multiple wake up/sleep messages are being sent on the end key and the system gets confused. Some sort of debounce might help.
Just my thoughts.
Running shui8 realstock rmnet with micyprima r9.
It seems waking up the phone with the Yes/Send button somehow seems better with current builds and kernels.
I am asking everybody reading this thread to try waking up their Android devices with the yes/send key and share their experience if it is making their Android wake up quicker with less SODs.
Note: I am still using yes key wake up as a workaround for my hardware touchscreen fault. Still absolutely works everytime. I found out that if I accidentally try to wake up with the no/hangup key I need to wait about 10-15 seconds before yes/send key does its magic again.
well, i tried there is absolutely no difference between any hard button. if i have sod, none of them solves... actually its not sod i think, when you try to put standby and wake up several times quickly, screen stops responding for a while. you need to wait at least 15 seconds between each standby and wake up. can i fix this? or this is the sod?
Waking up with the yes/send button would not make any difference if your phone can wake up good with the no/hangup button already. But we are trying to find out if yes/send button wakes up better in long term usage. (no/hangup button sometimes can't wake up and that is the sod refers to)
SOD happened to me few times too with the NO/Hangup button and if/when that happens, if you press NO/Hangup button for long(for the menu with the turn off the phone,reboot,plane mode,...etc options) screen comes back BUT sometimes it locks the screen brightness to lowest possible setting(with %0 actually it doesn't completely turns off as you know).
Other than that "bug" NO/Hangup button works fine for me but as the OP, YES button is more stable and no SODs happen with the YES button...
Btw there is no difference for me YES button vs NO/Hangup button by means of quickness... Both works the same speed unless of course there is no SOD with the NO/Hangup button...
Just wanted to share my experience...
This thread is awesome
Thanks for this thread. I have been trying to use any android build for at least a full day with no success. Ive used different winmo roms and radios such as chucky and miri roms. I still ran into sod's. After waking with the yes/button i have had no sod issues since then, Once again awesommmmmmmme thread.
After some time my digitizer died almost completely. (Issue became worse) It is currently being handled under warranty. (digitizer is replaced)
But at least with a lot of feedback from this thread and other threads, it has come out that, waking up the phone with the YES/CALL/SEND green button is BETTER than waking up with the NO/END/POWER red button for SOD reasons.
any solution to this issue yet because i just started having this exact same problem w/ my HD2 yesterday before that it was perfectly normal and all the suddon the Power/END/NO button wake up cause the screen to not respond to the touch at all however wake up w/ home,back,menu,call button the touch screen works is back to normal
still can't figure out if its a hardware or software problem cause i also tried flashing bunch of roms/radios/and android roms as well and even went back to stock rom in hope for a solution
waking with green is about 2s faster for me.
Same thing happens to me before 2 days.I tried many hard resets,roms,radios and my screen didnt work.I couldnt even login in wm.
My screen was completely dead.The last thing i did,before my screen goes unresponsive was to push no/hangup button in android to open it
At first also i thought it was a g-sensor issue,but then realise that it was much more than it.
Until the moment i read this thread
The way it worked for me
I open the device with no button of course,made a soft reset from red hole and i wait until the device goes to standy itself.Then i open it from send button and voila touch is back !!!!
Strange thing but it works.Thank you very much you are a genius
sure the touch comes back when it wakes up using all other buttons except the power/end button so why is that all the sudden the power/end button causes the screen to go unresponsive
like for say when i hold the power/end key to open the pHONES OPTIONS in windows or android once the PHONES OPTIONS shows up and i try to click on power off or reboot on the screen the touch doesn't respond so the only way to reset or power off the device completely is the either use the reset button in the back or pull the battery out
i'm going to be sending it under warrenty/insurance to t-mobile and hopefully get a replacement cause i'm so use to the power/end button to wake up my device...
Guys be extremely carefull when using hard buttons in android.Finally my problem with screen is not the end button but the back arrow button.This button is necessary for using android and i have pushed it many many times the last months as i am using android.Νοw every time i pushed it my touchscreen stops responding.Τhe last time i pushed it my screen stopped responding(i thought for ever) and didnt knew the exactly reason that this happens.Because i didnt want to send the device to htc (firstly i must send it to expansys in france and they will send it to htc) and take it back at christmas i decided to go to a local mobile service.I wasnot mind for warranty cause i wouldnt be able to live 4 weeks without hd2.I was ready to give 600euros to buy desire hd
Result from service
At firstly he said to me that hd2 have no touchscreen problem and it works ok
I paid 20euros for opening the device and took it back.At first 5 minutes my screen stopped responding again and didnt knew the reason.For my good luck i leave the device untouched 10 minutes and the screen come back again.Then i used it and the time i pushed the back button the screen stopped working,fortunatelly for little seconds.Now i know.My screen stop responding when i push back button.So i change the keylayout to my android build and now i push send key instead of back and volume up key for menu and volume down for power on-off and hd2 works perfect after 24 hours without touching the back button
Also in monday i will go to service again to fix the button problem
Same issue with me
Exactly same issue with me. I have been using Winmo and Android on and off in my HD2. couple of weeks back, touch didnt respond after waking up the device from standby by pushing endkey.
tried everything - flash/stock rom/removed SD card/ hard reset/clear storage/custom rom/ battery pull out etc...
touch worked suddenly and only when i slightly touch the end key instead of pushing it fully, the start menu opened..this happened for few days and when ever i push the end key...screen goes unresponsive. all other hardware buttons are working fine and if at all i push end key the issue starts.
unfortunately my friend pushed the end key once and the screen never responded after this....now am using my old p3450 htc touch...
i think if we change the AP BOARD (Flex ribbon-keyboard chip) everything will go back to normal coz its not the problem with digitizer or the lcd of the software for sure.
trying to order one in ebay, we can change this ourselves...no need to send it to service centers and waste money on it.
if any of you have done this already...let me know if it worked for you.
guys dont know if it is allready known but there is a app called sidebar style swkey
http://forum.xda-developers.com/showthread.php?p=9726110#post9726110 which puts software buttons in the screen.This app is definitely button saver
this is a new problem for me. I have been using the most recent Dutty ROM together with Mdeejay Android ROM without any problems. All of a sudden, when I try to unlock the screen after STANDBY, it just wont register my touch, as if I am not touching it. It boots up fine, and on the first unlock works fine, but when the screen lock goes on again (after every standby) it just wont unlock. So I am stuck (I use Exchange and our policy forces the lock after standby, so I have to use it - and its worked fine for ages).
If I boot into Android, it works fine, the unlock works fine, yet strangely when I try to shut the power down, THAT screen also doesnt register me touching it.
I have hard reset but even before I load an app or do anything, the problem exists.
I also reflashed a DUTTY ROM. Same problem.
I tried CHT lockscreen - same issue. After Standby, screen doesnt register my touch.
Anyone have any ideas?
Same problem for me.. Restoring a backup image after being forced to hard reset this morning and now suddenly my HD2 won't wake up after sleeping. Pressing my end key only lights up my buttons but I have to pull the battery to reset. I'm thinking it's related to me having CHT installed, yours however might be a different problem.
I had something similar. It was right after I had installed CHT 2.0 and was looking to make the top and bottom bars transparent. I found a cab that claimed it would do this and installed it. Sorry, I don't recall what cab it was and I have deleted it. When I rebooted Sense would hang and if it got into a lock it would only move the slider a little where it would stop. Luckily, I had done a backup that morning right after I installed CHT 2.0 with Sprite so I restored and all was well.
I don't know if this is of help but I figured I'd throw it out there.
it wakes up, but wont register when I try to swype the unlock screen.
ekerbuddyeker said:
it wakes up, but wont register when I try to swype the unlock screen.
Click to expand...
Click to collapse
Your lucky you get that far lol.. I don't get any waking up. Plus I now uninstalled S2U2 and still no change. Disabled all locks of any kind and still frozen with sleep of death with in 1 min of hitting power to sleep it. I REALLY don't want to to a hard reset and install everything from scatch.. UGH.
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
ekerbuddyeker said:
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
Click to expand...
Click to collapse
bump this is horrid
same
im having the exact same issue. I have flashed 3 different roms and flashed to the newest radio (2.15).
I started out using energy rom, didnt help. Flashed a newer energy rom, didnt help. Now im using the dusk rom, same issue.
SOMEONE PLEASE HELP!!!!
It's a quite common digitizer problem lately... it seems the HD2's digitizer is failing on some units, possibly because of usage with android? my father's device acted the same way, only it sometimes did register touch and other times, not.
My device doesn't have these problems, yet. But seeing that a lot of people here are experiencing these issues, and with the notion that I use android pretty much all the time since I first booted my device, i'm pretty sure i'll experience it soon as well..
Make no confusion thou, the assumption that android effects the digitizer are purely my own thoughts on this matter, no such thing has been proven and the conclusion that android is effecting our HD2s is based purely on the statistics of touch screen failures in the last few months since android has been made publicly available in a working form.
EDIT:
Those seeking A solution, as far as I know, the only solution is sending your unit to HTC for repairs, you'll get it back with a note that says that they replaced your digitizer or your screen, at least these are the reports I heard from the other folks whom followed this procedure.
Good luck.
HTC HD2 Screen Lock
I have only used Android a few times on this 'phone and it has a standard HTC/O2 ROM installed so it must just be a problem with the top part of the digitiser. With android running the unlock is at the bottom and is unaffected.
Is there any way of testing the digitiser before deciding whether to get a repair sorted,
Ta,
link:
htcphones.net/htc-hd2-problems-with-touchscreen
short version :
change digitizer
ekerbuddyeker said:
weird update...
It has something to do with which key i witch the device on with. If I use the phone key, I can swype the unlock. If I use the power key, it doesnt register.
Another related issue: when i hold the power key to switch off, it wont register me touching power off or reboot etc. so I have to take the battery out to switch off. Its the same in Android.
Anyone know? Hardware issue?
Click to expand...
Click to collapse
A friend was complaining to me about something like this since last week. I could not figure it out so I went ahead and installed Android cm7 and still have the same issue.
Until I read this post after searching through the forums all over Screen now unlocks perfectly fine but only using the green Phone icon. If I try to wake the screen with the red Power button, the screen is unresponsive.
Thanks for the info.
Already happened tome its a hardware issue can't be fixed so if you still have warranty on ur phone send it to htc for repairs b because it tends to get worse n worse soon other keys will start to give in I think that's one reason why most android phone been switching to capacitive buttons because hardware causes this sorta issues and send it in for repairs to get it fixed
Sent from my SGH-T959 using XDA App
the same issue with me , is there is any solution for that .
Wakeup the phone using the send button.it will work
My phone is SM-N900V running Android 5.0. It has recently gotten very temperamental. When I swipe to open it, I can feel the vibration as if I can tapped to open an app, and then s finder opens automatically. I can try to close it, but then it just reopens...I can go through this many times and sometimes it will settle down and behave normally for awhile...sometimes for quite awhile. Sometimes, I will get a reaction similar to doing a long press on the screen when at the home page, bringing up a smaller version of the pages, allowing easy movement between pages...and all this with me doing nothing. I have done factory resets (power off...hold home, volume up and power button to get to recovery and select factory reset), and this seems to work for a short while...maybe days, but then the automatic opening of s-finder is sure to return. Not sure if this is a reflection of the touch screen going bad, or home key, or ???? If someone has a thought on this or what might be the part most likely having gone bad, I can try to obtain a replacement and see if it can be fixed, but I really have no idea what might be the most likely culprit or how to better narrow down the problem. I'm wondering if this maybe was related to a recent update??? Is it possible to roll back to an earlier version of Android to see if this solves the problem? Any help is most appreciated.
Regards.
Uninstall last apps or try to remove screen protector or magnetic flip cover. If not good try to open phone and reseat display flex cable.
Sent from my Limited Edition Note 3 LTE using Super Tapatalk
When it happens, try to dial *#111*# and choose LCD test. (you may need to power it off or remove battery to exit that mode)
See if there are ''ghost touches'' appearing, or when you secure on it, if appears some touching marks. If so, note if the screen is hotter on that zone. If so too, then your screen has a defect.
If not, it's a screen cleaning problem, or software problem.