Hi all,
I read through a lot of threads and downloaded tons of ROMS for my TyTN II. Most of them were from dutty's or no thrills. Problem however is that everything seems to work, it is also very fast.
However after a while my (hardware) keyboard and also the buttons (e.g. sliding wheel and keypad on the front) does not respond anymore. When I click any of the hardware buttons the light goes on so it does react on the buttons, however it just doesn't do anything...
Did anyone else experience this issue? I will no try to switch back to the original HTC rom (6.0) since I have no choice but if anyone knows how to fix this?
P.S. I just noticed that all my buttons do not work, it is no hardware issue since It does work after a hard reset, might be caused by incompatible applications? (e.g. SPB phone or SPB theme)
Kind Regards,
Nico van der Linden
If a hard reset fixes your problem each time, then it sounds to me like a bad flash. I would try reflashing the ROM you are currently running. Make sure to hard reset immediately after the flash also.
ok thanks, I'll try to download the ROM flash again , and perform an hard reset directly after the flash. Hopefully this times the ROM update will go better.
Regards,
Nico...
Just my 0.02$:
I think this is related either to WM6.1 builds or to a hack/fix/setting that most custom ROMs use.
I flashed Dutty's Apr 01 ROM and i had this issue. Then i flashed Mobile Vista 1.3 and it happens again . So it's not present in just one ROM, or just in ROMs cooked by a certain chef.
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
EDIT: Oh, and i got flamed and ignored whan i reported this here: http://forum.xda-developers.com/showthread.php?t=385080
EDIT2: I have a feeling this will get a lot of attention soon, just like the time i noticed the Tytn II is underperforming, and the fact that's it's missing 3D HW support
RPG0 said:
By "issue" i mean every once in a while the touchscreen stops responding to clicks and the keys stop working (but the keys backlight comes on, so HW seems ok).
During this unusual behaviour i noticed that the device is NOT frozen - BatteryStatus updated it's CPU usage while the keys and touchscreen didn't respond, so only the input stops working, the system is ok.
I have a feeling this is a common issue, but people see it as a freeze, and think their processor is too loaded, and they don't report it.
Click to expand...
Click to collapse
The quickest way to get out of that situation is turn off the backlight and turn it back on again, aka power button...and your screen will work again.
Also I noticed that if I flash the radio again my screen taping problems go away.
Also sometimes flashing to the original shipped ROM and then flashing back to a WM6.1 ROM also works.
Well I do not have an problem with the touch screen, this always keeps working (although the device does get VERY slow sometimes) . 'Only' my hardware buttons do not work anymore (including the hardware keyboard). It is strange that it does work after a hard reset or an install of another ROM. However, also then it stops working after half a day or so.
It might occur as soon as I change the hardware button assignment but I am not sure about this yet.
However, if anyone knows a ROM where this does not occur (e.g. an original HTC WM6.0 ROM dutch or english) then please let me know which one. I just want a working Tytn II back and I do not care anymore which version .
Kind Regards,
Nico...
Ah by the way, when this problem occurs it does not go away anymore when I turn of the device. I also tried removing SIM, memory card and battery but after it is started again the problem remains. Only a hard reset solves it....
But I am a bit confused? Is there nobody else who get these issues???
yeah...
i can confirm all of your bug...
with Vega R8 italian ROM from UDK
Related
It's actually an older problem.
The joystick on SPV C600 with any non AKU 2.0 Orange rom just doesn't work as it should.
In WM5 and say.. a rom from I-Mate the joystick still works.. very bad.. but it still works.
In WM6 it's like almost completely dead (tried all the current cooked roms)
One stupid thing that I found is that actually pressing and holding a random key makes the joystick work.
Yup.. holding 6 or 2 or VOLUME DOWN actually makes the joystick work. What the?!
Has anyone encountered this problem?
on1x1 said:
It's actually an older problem.
The joystick on SPV C600 with any non AKU 2.0 Orange rom just doesn't work as it should.
In WM5 and say.. a rom from I-Mate the joystick still works.. very bad.. but it still works.
In WM6 it's like almost completely dead (tried all the current cooked roms)
One stupid thing that I found is that actually pressing and holding a random key makes the joystick work.
Yup.. holding 6 or 2 or VOLUME DOWN actually makes the joystick work. What the?!
Has anyone encountered this problem?
Click to expand...
Click to collapse
I have the exact same problem. With the original C600 ROM from Orange, teh joystick will work. I tried several WM6 rom and Joystick is performing like yours. Cannot move up, hradly move down, but pressing the volume or any other key while moving the joystick will make it work perfectly.
Like you, I am at loss. Anyone has a clue on this behavior and how to fix it?
I have already observed this problem in this thread.
If someone ever bothers to reply to it, we may have a solution.
Wow, thanks - i thought my joystick is almost dead, as it sometimes takes like 3-4 moves to one direction for system to actually recognize one keypress of joystick, if the problem is only caused by softwware, there is still chance! (as the tornado is practically unrepairable in my country )
keff said:
Wow, thanks - i thought my joystick is almost dead, as it sometimes takes like 3-4 moves to one direction for system to actually recognize one keypress of joystick, if the problem is only caused by softwware, there is still chance! (as the tornado is practically unrepairable in my country )
Click to expand...
Click to collapse
tilt & spray the joystick with deodorant (i've used denim )
Hi there DSF, I know about that fix for the hardware failure of the joystick but we're talking here about a faulty software.
Joystick failure related to software
In my case, the joystick problem is not a hardware failure
How do I know that? Simple:
I installed the original C600 Orange ROM and have no problem with the joystick. I then try back any of the WM6 out there and unfortunately, on all of them, my joystick will have issues. I even extracted the Keyboard.dll from the Orange Rom and incorporated in one of the WM6 rom but it did not fix the problem.
Is there more than one Joystick file that needs to be copied?
What is strange (and as stated in the first posting) pressing other button while moving the joystick will work fine
In the meantime, I reverted back to the original Orange Rom.
My belief is that by adjusting the keypad backlight timeout, this problem could be fixed.
The new joystick driver disables the joystick when the phone is locked, or when the screen shuts down for powersave. I think that the keypad powersave causes this too.
There was a Tornado ROM out for a really brief period that I read had the ability to tweak the keypad timeout, but I can't find it for download.
Exitao said:
My belief is that by adjusting the keypad backlight timeout, this problem could be fixed.
The new joystick driver disables the joystick when the phone is locked, or when the screen shuts down for powersave. I think that the keypad powersave causes this too.
Click to expand...
Click to collapse
Wow, I have just tried turning Light sensor off (settings-power management), and it seems to do miracles so far - joy works as new (on WM6 V4 from this forum)!
EDIT 2 hours later... it doesn't anymore at least i know it's because of software... Seems to be connected with keyboard power management.
keff said:
Wow, I have just tried turning Light sensor off (settings-power management), and it seems to do miracles so far - joy works as new (on WM6 V4 from this forum)!
EDIT 2 hours later... it doesn't anymore at least i know it's because of software... Seems to be connected with keyboard power management.
Click to expand...
Click to collapse
Yes.
For some reason, my keypad backlight has stopped turning on. And the stick gives me no problem at all now.
No idea how that happened. But I'm fine with that.
Still having Joystick issues
It seems that very few of us are having that joystick issue. I tried the backlight trick, which did not help. There is definitely a driver issue with a combination of hardware. However, even if I try the Keyboard.dll from the original rom and cook a rom with it, I am having that issue.
My question is: does anyone know what other drivers will need to be extracted from the original C600 Rom and cooked on the WM6 to make the joystick behave as it should?
Thank you
I've the same problem.
WM6 v.3.4
Same problem as i have ....but if i press the volume button it seems to b working just fine ...
Exitao said:
My belief is that by adjusting the keypad backlight timeout, this problem could be fixed.
The new joystick driver disables the joystick when the phone is locked, or when the screen shuts down for powersave. I think that the keypad powersave causes this too.
There was a Tornado ROM out for a really brief period that I read had the ability to tweak the keypad timeout, but I can't find it for download.
Click to expand...
Click to collapse
Not sure about some of the other cooks (I'm using vjgrace's 3.4) but on mine it's:
HKLM/SOFTWARE/HTC/KEYPAD/KB_LIGHT_TIMEOUT
It's in milliseconds - roughly. I set my display timeout to 30 seconds and the keypad light timeout for 30,000 milliseconds (30 seconds) and the keypad turned off just before the display. Keypad timeout at 30,069 milliseconds turns the keypad off at the same moment that the display dims.
That was way off topic, but if editing the keypad timeout helps fix the joystick problem, that's how to do it.
djsleepwalker said:
Not sure about some of the other cooks (I'm using vjgrace's 3.4) but on mine it's:
HKLM/SOFTWARE/HTC/KEYPAD/KB_LIGHT_TIMEOUT
It's in milliseconds - roughly. I set my display timeout to 30 seconds and the keypad light timeout for 30,000 milliseconds (30 seconds) and the keypad turned off just before the display. Keypad timeout at 30,069 milliseconds turns the keypad off at the same moment that the display dims.
That was way off topic, but if editing the keypad timeout helps fix the joystick problem, that's how to do it.
Click to expand...
Click to collapse
If it is a fix, I don't see how it's off-topic at all. It's bang-on. I'll experiment w/this over the weekend and see how it goes. Thanks.
seeing this with 3.4 rom from vj and cingular 2125. I can move down/right pretty easily with joystick. However, up/left are sticky. Sometimes they don't respond and you have to try a few times. Really kills usability of the phone on WM6, feels slow and clunky.
I've changed it to 60,000
I'll report back later.
So, I got fed up with joystick problem, and ordered a new keyboard part form ebay - here for $20: ebay link
Should arrive in a week or two, will write how it worked (i expect joystick to work as new after that )
omszz said:
seeing this with 3.4 rom from vj and cingular 2125. I can move down/right pretty easily with joystick. However, up/left are sticky. Sometimes they don't respond and you have to try a few times. Really kills usability of the phone on WM6, feels slow and clunky.
Click to expand...
Click to collapse
Mine too, maybe nitro will have that fixed with his new build
HHHRRR. Yesterday i have bought my third HTC Tornado. Today i have installed the WM6, and found, that joystic doesnt work when trying to get to the top, or left.. Now i've found this thread, and tryed to move joystick while holding the "6" or "2" - then it works fine! Guys, dont want to roll back to the original ROM..
question
not all the keys on my htc s710's keyboard are working all the time. for instance the dot, the letter b and letter k do not always work. strangely enough, sometimes all the keys work for a while, and then for no apparent reason the same keys do not work anymore (always the same keys) i tried several roms, with all the problem exist. when i do a cold restart, and try the keys most of the times the will work for a while, but after a while they stop working. same if the power drops (battery drops below a certain percentage), the problem is more persistent and the keys fail more often than with a fully charged battery. i already checked the connection cable on the mainboard, that appears to be seated fine.
any idea's and suggestion (no warranty off course, since i opened it up myself)
Not working
Ive got same problem here.
Cap/Sft and fn isnt working in text message mode.
they work in home screen though..
Please help us out!!
thats why i dont open my phone ...
anyway... if u think u are good with hardware and breaking things apart an take them back together... u can try the htc vox service manual...
i dont recommend anything...
but here it is
http://www.maritime-billeder.dk/uploads/file/VOX_SM_A01 _GENERIC_.pdf
read before u do anything and remember if something dont work, stop, think.. DONT use violence
oh.... opening the phone works in the case some buttons dont work anywhere... otherwise its software.. maybe hard reset, reflashing?
Its definately not hardware.
Because when I Updated from orginall Vodafone Rom to WM 6.1 the keyboard started to decline.
So does someone has a solution for this?
I dont have much knowledge of this, but managed to update my HTC S710 to WM 6.1.
(sorry for my english)
Hi,
I just received my Touch Pro and I tried to use the camera! The app version is 6.01, but it seems to have a few bugs like:
1-When I touch to center button to focus, nothing happens! To make it work, I need to hard press it to take the first picture, after that, the touch focus starts to work!!
2-If I take too many pictures or try to focus a lot of times, the auto focus stops to work and show a red X. The only way to make it work again is to soft reset the phone!
My ROM version is:1.90.405.1 WWE
Could you confirm this behavior on your phones? Or maybe my phone is faulty?
nickba said:
Hi,
I just received my Touch Pro and I tried to use the camera! The app version is 6.01, but it seems to have a few bugs like:
1-When I touch to center button to focus, nothing happens! To make it work, I need to hard press it to take the first picture, after that, the touch focus starts to work!!
2-If I take too many pictures or try to focus a lot of times, the auto focus stops to work and show a red X. The only way to make it work again is to soft reset the phone!
My ROM version is:1.90.405.1 WWE
Could you confirm this behavior on your phones? Or maybe my phone is faulty?
Click to expand...
Click to collapse
sounds very strange......
I think the only thing that may help is a hard reset....
If that is not working...ya probably have to send it back...:S
But I hope I'm wrong and somebody else has a good idea/solution 4 you! good luck with it!
1. Settings -> Advanced -> Page 3/5
Shoot Option = Touch and Press
Hi,
Thanks everyone for replying.
My setup was already in touch and press.
But like I said. If I soft reset the phone, the first time I use the camera I have to hard press the button and take a dumb picture, as the touch doesn't work. After that the touch button works forever(till the next soft reset).
Seems to be a software bug, but I am not sure. If someone can test it on his/her phone it would be great!
Soft reset the phone and try to use the camera. If the touch button doesn't work, take a dumb picture with hard press the button, after that the button starts to work.
My Touch Pro with stock ROM also does this.
Hi Mike,
Thanks for replying! So seems to be a software bug! Let's see if they will release a fix for it!!
Hi. My touch pro has the no go first time but work afterwards until next soft reset problem too.
But recently I noticed if I push in the button(doing anything or nothing as long as it was pressed) before I enter the camera app, it always work.
EDIT oh stock rom 405.1 WWE
Humm, so seems that the problem with the button is with the device driver that controls the touch part of the button, not the camera application itself.
Well I'm hoping its the software but fearing its the physical button.
I also have exactly the same problem! Stock ROM.
Never experienced this problem since I first bought it. Same goes with my Diamond. Anyway, try hard reset your device. If the problem is still there, it would be best to send in for warranty claim.
Can't we just update the ROM?
Mine it also v. 405.
I think I'll update today.
programatix, what is your ROM version? Could you try to do the soft reset test I posted? So you can see if the problem happens.
Mike, will you updade the ROM to a newer version? Which one? After you do that, please tell us if it solves the problem.
I have the same problem with mine :-(
Sometime the autofocus works, in most cases not and after a while after pressing the button I get an very unsharp picture.
I have the latest german ROM Version 1.90.407.4 GER so other users with this actual version might have that problem too...
I also have this problem but my auto-focus just plain never works...EVER. Has anyone tried a hard reset and had it fix the problem? I would like to know before I try it.
+1 - sw bug for def
405.1 WWE - stock UK rom.
so, it has been a few days, has anyone tried a hard reset or found any other solution to these camera bugs? Or is everyone just trading in for a new pro?
Strange. My AT&T Fuze w/ stock rom doesn't have this problem. After a soft reset, I open the camera and press the center button, it auto-focuses just like it's supposed to. Must have been fixed for the AT&T rom.
Apparently not many people have this problem on sprint either since nobody seems interested in it.
I've been mucking about with mine since I thought the touch/auto focus feature wasn't working either.
What I discovered was that the button doesn't really respond to your touch very well and so you end up pushing the button all the way down which ends up focusing and taking the photo all in one step. At least this was the case with mine anyway.
Instead of just touching the button softly, try 'stabbing' at it with your thumb a little instead. I don't mean forcefully, just kind of tap and hold as opposed to just lightly touching it.
That's the best way I can describe it. It may not be your problem however...
I have spent hours searching to see if someone else has had this problem and haven't been able to find anything.
My lower D-pad and its buttons/touch panel have stopped working properly. The touch part of it doesn't work at all and the buttons have reduced functionality. Only the up/down and the home buttons work. From what I can tell this was after flashing Tael's latest Sense2.5 ROM.
I have reset the phone back to standard, using an original HTC Rom, going back to standard SPL, and standard radio. This has not fixed the problem.
The only thing I can find that seems to be related, is when I go into the bootloader there is a line that says "PSOD-wrong platform". I'm guessing that a code somewhere has changed somehow telling the phone that it doesn't have a touchpad, possibly because the phone the ROM was ported from didn't have the touchpad. It might be a longshot but that is my best guess.
I have no idea how else to troubleshoot this and any help would be great.
Thanks in advance.
Craig
Hello, I have recently discovered a very annoying problem with the touchscreen on my Motorola Defy:
I have noticed that the touch screen acts strange sometimes, so I have installed a touch test application(Touchtest by Hermit). In this application I have noticed that if I touch the screen in two different points in a fast succession, a line appears between these two dots. This makes a lot of application that require multitouch pretty much useless, because I have to restart the application to have the touch screen working again.
Is there any solution for this? I have heard that this may be a software issue, so I have e-mailed Motorola, but they have not answered yet.
I have attached two pictures to illustrate what I am saying, one taken before this strange error, and one after pressing on two spots very fast. You can see the line connecting the dots in the second picture. I can make a video if you still can't figure out what I am saying.
Thank you.
Im having a very similar problem here on my defy. When I play games on psx4droid and when I keep pressing x key, it stops working for a while then I have to release the button and when I press it again, it stops working and it continues
I encounter similar problems with my Defy.
When for instance using slide to unlock , 1 / 5 sildes fails. I have to slide 2 - 3 times until it unlock.
It also scrolls very slow in applications and the same thing happens when typing a message.
Solution : Unse lock button.
It currently runs Pays ROM, but the situation appeared since I installed 2.2.1.
I don't remember having this problems on 2.1.
Don't know if the situation is only related to software but it is really annoying.
Found this info regarding touchscreen slowness, but I am using the original charger so it doesn't apply for me.
Motorola Defy Touchscreen Problem
I recently got my Motorola Defy,my Defy's touchscreen acts sometimes really weird, on keyboard it's hard to enter 'r' or 'b' and some other characters, it takes little while to unlock the phone, it automatically opens applications, I don't know if it's due to faulty handset or software, I am considering it returning to Phone4U and get a replacement handset.
What version of Android are you using ?
Same problems here, but I think it is a software issue.
I'm having the same problem on my Defy.
After a while, the multi touch stops. I posted on the Motorola Forums
https://supportforums.motorola.com/thread/44733
but no response.
I used YAMTT and when having two touches, after 20 seconds, one of them disappears
This is repeatable
2.51.1 UK with 2.1 Android
Well, it is clear that this is a problem that affects many Motorola Defy users. But I wonder if someone could fix this thing?
Looks like the new software version 2.51.1 did not fix this bug. I haven't tried it yet, but I see some of you have.
So it looks like our only solution could be a developer from XDA. Could someone help please?
This is ridiculous...i've sent my phone to motorola only because it was giving this problem and basically what i think is that their own software is causing this problem so i'll be waiting for 3 weeks and when i get my defy...it'll still have that problem...Ridiculous...
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
efpob said:
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
Click to expand...
Click to collapse
Defy doesn't support cynogen mod and 2.3
I was messing around today and even the single touch disappears after a while
30 seconds or so
Mine sometime stop response after few seconds
really wierd
Tell me who is on stock rom and is having problem..because im on 2.2 leaked..so i cant really say if u hv this problem on 2.1...
I got this response from a Motorola employee. Anyone know of a way around this?
Motorola Employee said:
If you touch the screen and don't move for a long time, the screen will eventually try to ignore that touch as it'll be considered invaild. That's what you're seeing. If you continue to move your finger(s), touch will continue to work. Also, when you release the screen, it acts to clear the invalid touch region that you generated earlier.
Click to expand...
Click to collapse
https://supportforums.motorola.com/thread/44733
have simular problems............100 procent hardware problem..... if i twist phone a little it will go back to normal for a while
any ideas for disable it?changing some parameter or something?
I have the same problem. screen sometimes go crazy. i am using stockrom eclair SEA 2.59. sometimes it seems that it tap icons or part of the screen even without I actually tap on something. and it seems it affect the capacitive button under the screen. I am not touching the search button but the search box suddenly appear.
I have to push the power button and unlock the screen to make it normal.
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
brjshshrma said:
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
Click to expand...
Click to collapse
i returned my defy months ago but what you can do is, try to flash cyanogenmod on your defy...that should fix the problem.
Hi, I've registered myself just a minute ago, reading the link that efpod left here and I've remembered that I charged my Defy with a Galaxy S i9000 charger friday (I've charged it once the batery was drained later with my original charger) and today it is failing A LOT, it's really anoying.
I got Cyanogen Mod (latest) installed on my phone so that doesn't fix the problem.
I'm uncharging it with "StabilityTest - CPU / GPU Test" and when the battery drains out I'm gonna charge it with the original one, after that, I'll test it during the day and I'll leave a messege to keep you informed.