Does anyone else experience unresponsive Messaging, IE, ok, etc, keys?
I know there were brief threads about this a while back, and most were either not conclusive, or someone blamed the hardware.
I did a test, and flashed almost all current cooked and uncooked WM6 ROMs, and every single one of them has this issue.
Then I flashed WM5, and voila! No key problem.
Any ideas, or suggestions to further troubleshoot this?
TIA
Ali -
i have problems with unresponding keys too. I have too push very hard on the qwerty keyboard. Espesially the "U" key. No matter what ROM I use.
Sounds similar to what I'm referring to in this thread:
http://forum.xda-developers.com/showthread.php?t=319516
I can confirm that you're not alone. I have random problems with an unresponsive keyboard as well. It happens occasionally on all WM6 Roms I've used (currently on AT&T leaked rom), and without any discernable pattern. I don't THINK it is a problem with the actual keyboard hardware, but I've not tested this specific issue enough to be totally sure. Only a soft reset will bring the keyboard back, and then it may be fine for days. I haven't tried pressing hard on the keys to try to bring it back, as others have. If normal force doesn't work, then I will just reboot.
I hope this info helps.
Seems to be a common thing. I get this sometimes too. I have found it happened slightly less often with either Faria's super-clean or Black Satin. That could be coincidence thoguh.
Although a physical problem which requires the insides to be cleaned is something that could happen to any unit, there is an issues with Hermes keys failing to respond either quickly or at all in certain situations.
I'm honestly not sure if anyone's done enough testing to ascertain the exact circumstances that this can come up in, but it seems that a Soft Reset will always sort it as you'd expect - except for 'physical' problems of course.
Im also getting this problem now and then.. It just happens when im using the keypad allot, or typing faster then the ppc can put it on screen it seems.. But its almost most of the time when im using java apps and MMS and SMS. Wierd..
I got this problem even worse when i had Black Satin installed.. It will happen as soon as i start typing something..
updates?
I hate to ressurect this old thread, but was there any update to this issue that I might have missed? I am still having the dead keys issue, and I know it's not hardware as the pressing of the keys wakes up the device but doesn't do what the key is supposed to do.
I've had this Happen to Me Since Upgrading to WM6. When On WM5 It never Happened. Usually after a soft reset It's ok on WM6. I say Test out some WM5 for like a Week And if it doesnt' happen then It's the OS. Prolly Software to Hardware issues.
Related
Hello,
First and foremost I should note that I tried searching the forums but I was not entirely sure what to search for. I tried a few different queries and they yielded negligible results for my issue. Now, onto my issue:
8525 with wm6 black 3.01
I have my 8525/hermes/tytn/etc/ set to turn the device off after 3 minutes of inactivity in order to preserve battery life. Sometimes, this poses no issues and I can just hit the power button to turn it back on when I need to. Other times however, and perhaps more frequent, I press the power button and nothing happens. Try as I might and regardless of how many times I press the damned button, it will not turn on. I have to use my stylus to do a soft reset in order to have my phone back in operation. Needless to say, this has gotten very annoying. I have since turned that feature off but now my battery drains far too quickly.
Is this a known issue or has anyone experienced similar issues? If so, is there a fix for this? If not, would ATT accept my phone for a warranty exchange with this greymarket software on it? If not, can I just flash it with an official ATT image and then send it in? Thanks.
It's called Sleep of Death... SOD... I had it and I flashed the official AT&T rom and havent had it since.
thanks.. looking into it!
How many apps do you have running. Where are they installed also. I currently run Black Majik, and NEVER have the SoD, or soft reset, so I think it's the stuff you put in your device that may be causing this. Flashing a new ROM wont always solve this, since you and I have the same phone, I think it's what you put in that may cause this.
ronfin44 said:
How many apps do you have running. Where are they installed also. I currently run Black Majik, and NEVER have the SoD, or soft reset, so I think it's the stuff you put in your device that may be causing this. Flashing a new ROM wont always solve this, since you and I have the same phone, I think it's what you put in that may cause this.
Click to expand...
Click to collapse
running? usually just whatever program I have opened since I have it set up to completely escape the program when I X out. As far as where things are installed, everything is installed on my device sans iGo.. However, this issue arised prior to iGo being put on my SD card.
Try this. After a hard reset, load one app to your device, let it sit, test it, and then do another. take your time. See if something you load is causing this. I did a HR on mine cause I had tons of crap on there, loaded stuff slowly and noticed the ButtonFlo CAB is what screwed my ROM from working good, so got rid of it. Since then, its awesome.
Leave the Black and go with JJ's Majik. Is the only ROM to date that hasn't SOD'ed me ... and I run the same apps, the same way, on all the ROM's.
http://wmblack.info/
is this so? i'm going to try at&t's wm6 for a bit, see howt aht works..
Don't belive so
I read a lot of threads regarding the problem, i tried AT&T and same problem, others had it with black, now i am having it with latest LVSW, may be a software problem, i had it using SPB WEATHER and SPB TIME, i hard reset install all but them, worked fine for two days, installed TWEAK2K2, problem came back, now trying without TWEAK2K2, but i doubt problem can be solved
My Opinion
been running through threads all over, just found out that there is no solution, because when a program pushes the unit to wake up from standby it freezes, this program can be weather, alarm, mail, active sync, and even a CALL can cause this, so it's a permanent bug in wm6 and PPC :-(
Hey all,
I am running the Cingular 8525 variant of the TyTN with WM Black Satin.
Since the days of Black 1.2 I have rarely, but randomly had the keyboard randomly fail while using the device. When this failure happens, the Nav keys and Soft keys on the face of the phone still work, just the slide out keys do not. Also, the screen based "soft keyboards" and other input methods still function.
I am pretty sure this is software related because a SR is all it takes to fix the problem.
What I am wondering is:
1) Does anyone else experience this problem?
2) Does anyone know what specifically causes it?
3) Does anyone know of a way to fix it without a SR? (sometimes I am in the middle of things where resetting isn't an option until I am done my task)
Thanks for taking the time to read this, and thanks for any useful input.
Yeah, yeah, i know, have a lot of it on the forum, but, until now, i didn't find any real answer about it.
Sometimes i read that isn't hardware problem, sometimes i read that is.
Sometimes i read that need to change some keys on registry, but what keys?
The problem is the same of other users: the green and red key, videocall, Windows, Ok, "the left and right software buttons", the IE and Message buttons doesn't work. And the diretional buttons, the first time i press when i turn on the Hermes open the browser.
I don't know what to do anymore. That phone already stayed at the HTC Support for 3 months, and came back with the same problem. BTW, the HTC Support is a @#&ยจ%$$!!!!!
OK, atleast try a different ROM first, ie schaps or pandora naked???
IF it works on the newer ROMs then theres your answer.
Is the device a Tytn, Vario II, 8525 etc..?? ie let us know which brand it is.
I've tried a lot of ROM's, but not the newer ones. I'll try today. I'll try Pandora Naked and Schaps, in this order, and will post the results.
My device is a TyTN.
Tried the both ROM's (Schap's and Pandora) and still have problems with the buttons.
Hardware issue, suggest a 3rd party repair facility??
mrvanx, i've read something about the registry. Changing some keys in the registry i can solve this problem? Is there anyway to be something like that? I think, in a hard reset or a ROM change, the registry goes to the original situation. Therefore, if was a registry problem it'll be solve doing that HR. Am i right?
Like i said, it already stayed on the HTC Support for almost 3 months and they do NOTHING about it.
Anyway, thanx Mrvanx, i think that will be the solution.
Sounds like you're out of luck. I'm using an AT&T 8525 with WM6 and excluding the d-pad, all of the front buttons do not respond. The bug appears to be in the software since I, along with many of the other with this trouble, have attempted the hard reset are able to do so successfully (which requires holding down both of the soft menu buttons under the screen). I have also tried the hardware solution posted by another user and it was not successful with my device. Thanks for the remarks regarding HTC. I'll avoid sending my device to them.
Scg033, good luck. I'm trying to take my friend's TyTN and checking the registry. The seller insists that my problem is not a hardware problem. This is my last chance to try something. I'll try today and will post the results, anyway.
Well, i've tried to look into another TyTN's registry and made mine exacly like that one and... Nothing Happens. Still having problems. I think it's not a software problem.
Here is how it happens :
i slide the keyboard out, write an sms or something , then slide the keyboard back in quickly : it soft resets itself.
It also happen when sliding the keyboard out and in without doing anything else.
This doesnt happens 100% of times of course, but in 2 days, it happened to me twice. And it pretty annoying.
I dont know if its something i have installed or not, but i dont see how it can be related (have tomtom, Batti, skype, Resco File Explorer, CorePlayer)
Am i the only one with this problem?
Thanks in advance if you can help me
Seems like the power cuts off sometimes you slide it. (in other words, it's broken). Return it and ask for another one.
Little chance this is the cause of any software interferrence.
But first try a hard reset... if that doensn't help, than you can consider a RMA
Hi,
I've had exacly the same. It looks like we did get a monday morning device
I've returned it to the shop and got a new one, this one is fine. I would suggest you do the same.
Toolman
hmm, mine is also doing that as well. Hard reset did not fix it. Bought from Techrific in Melbourne. Just negotiating return now.
Although my issue is not really a reboot. The phone just does an ungracefull shutdown. Have to power it back on.
i did a hard reset.
And so far, no unwanted reset... I am crossing my fingers.
FYI : unlike my first time, i didnt install Tomtom 7... i dont know if its related or not. So i just wanted to know if those experiencing those unwanted reset also had Tomtom 7 installed ?
May not be the same issue, but be aware of this problem with TomTom7 on the TP2...
http://forum.xda-developers.com/showthread.php?t=522373
ianjd said:
May not be the same issue, but be aware of this problem with TomTom7 on the TP2...
http://forum.xda-developers.com/showthread.php?t=522373
Click to expand...
Click to collapse
yes i found out this problem with the BT files... I had this problem too.
So i didnt install it yet since my hard reset, so i will wait a little bit before testing it out .
But so far, no more problems with my TP2, i dont regret upgrading from my Kaiser
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App