Hello everyone,
Lately I'm having a lot of issues with my HTC TyTN while in the past I didn't have any. I believe they all started when I upgraded to WM6, but the thing is I don't want to downgrade. However, what makes me think twice about it is the fact that I dropped it down few weeks back and there's a major scratch down at the bottom of the screen where touch screen there doesn't work and when you press there it goes a bit to the left or right accordingly...! The screen needs calibration like all the time because it's not accurate.
Moreover, sometimes the hardware keyboard doesn't work and I need to make my phone sleep and then wake it up again and it would work. Last night I also got a key locked.. and it wouldn't work until I made my phone sleep and then work again.
Additionally, if my phone is locked, and I receive a phone call, and while talking to the phone I receive a message, when the phone call ends the phone is like crashed and I need to make it sleep and wake up so that it works well again.
Anyone who can give me any kind of suggestions or advices on how to solve or decrease the problems please?
Thank you.
None of those problems are WM6 problems.
You said you dropped your phone so i think its a hardware fault? Coz for me WM6 save's my HTC 8525 from bricked and now works fine.
You think? I think the screen alignment problems might be due to dropping the device on the ground once but I doubt the rest are. I believe they are driver bugs from WM6.
Do you think I should take it to get fixed? Would my warranty cover that?
Anymore have an opinion on the matter, please reply. Thanks.
Moreover, sometimes the hardware keyboard doesn't work and I need to make my phone sleep and then wake it up again and it would work.
Click to expand...
Click to collapse
I had the same, when I used WM 5.0 (it happens on three diffrent devices - all of them comes from T-Mobile UK) - after upgrade WM 6.0 (Schaps) it's still happens, but very rarely.
Drivers might be part of the problem, but I think dropping it has played a big part.
If it was me I'd downgrade to the original setup (follow MrVanx's guide) and try that. If the problems persist they are hardware related, but you are in a position to try for warranty because of original set-up. If the problems go away, upgrade again and try to isolate which bit of software caused the problems.
But the reality is that if you've dropped your phone hard enough to scratch the screen that's probably the root of the problem which is probably not covered under warranty anyway...
Well it wasn't that hard hit on the ground, it's the fact that there was a tiny rock on the ground and that's where the screen hit...!
I have the same problem. Dropped it for about six months ago. The problems started just a couple of weeks ago. Strange. I'm gonna try the waranty. Even if I have a few scratches. Also my speaker doesn't work anymore.
Any more suggestions/ideas?
My first response is the definitive response.
If you are still concerned that WM6 is the problem, then go back to WM5.
Related
Hi again,
so i recently fixed my keyboard issue and to lighten up darkness: it was not a software-issue.
after playing with the thought of returning the phone to tmobile, i flashed the "new official" tmobile-DE rom, and the tmobile service center told me, that this would void my warranty because the rom hasn't been downloaded from the offical tmobile-DE website... so i discarded the option of returning the phone in the next few month
toda i woke up and retried my hardware-keyboard on the vario 2, i recognized something which was: the reason for the vario dropping so much keypresses, was a bad contactivity... i mean: i can hear the key i press "clicking" but no char appeared on the screen... so i disassembled the vario 2 todays morning, and searched for a way to fix this, a way to give the keyboard a better fitting, or somewhat like that. the difficultest thing was to remove the "void"-label without tearing it... took me about 15 minutes to remove this damn label, but it remained intact
after that, i systematically disassembled the phone, and i did the following things to the keyboard-parts:
removed the white label which was on the "contact-side" of the keyboard-circuit
realligned this label and put it back on the circuit
then i put the keys and the circuit back into the housing, and got a piece of paper
i cut this to be as long an high as the circuit itself is, and put 3 of those paper-sheets onto the back of the keyboard-circuit, then fixed the 3 sheets a little with the flex-cable connecting the keyboard to the main-circuit.
then put the phone back together an tested it
my keyboards working like a charm right now, i'm so happy that my phones completely working again, without returning it
i thought this might help someone who has got same problems, perhaps my keyboard got this malfunction after the first drop, i do not remember when this problem occured the first time, and actually... i don't have to anymore
greetings from germany
garfield
this is the orignal post said:
hellow to all
so i'm using my hermes (MDA Vario II) for as much as two months now.
I dropped it two times, first time 20cm onto carpet, second time 40cm onto the street -.-
but as far as i can see, not much damage, some scratches, nothing to worry about.
since i have this phone, i flashed several roms onto it. Black/Faria/Schaps/t-mobile_shipped/dopod wm6/black wm6 final/and many others... even some of my own roms got tested in there
i wasn't able to test the shipped status for very long, because i flashed the first custom rom about five days after hardware-arrival
the one thing driving me insane at the moment is the f**king hardware-keyboard. sometimes the "red dot" (for the second assignment of the keys) gets locked, without me wanting this. or i press "space" and nothing happens, or even worse, it adds some crazy special symbols to my sms wich then extends to four or more sms...
the e and w keys sometimes do not respond, and worst case ever had: keyboards gets fully locked up... had to soft-reset.
during the testing of the many custom roms, which were pre-finals, (in contrast to wm6-release versions), i thought: "yes everythings working, and the keyboard driver is producing crap". but even with the dopod rom (wm6) now active on my hermes, i have problems described above.
may it be the 1.50 radio? should i go back to 1.47?
or is it an hardware issue? should i return the phone to my loval mobilcom-store?
its driving me insane, i have to recheck every word two times... and i have to correct many things... actually i'm typing very fast, and this lowers my typing speed by, lets say 2000%
looking forward to hear your ideas,
will be grateful for every idea, which gets me some closer to a solution...
greetings
and keep up all your good work
garfield
(sorry for typing bad english (if i did so), at least im german)
Click to expand...
Click to collapse
There can be software issues that cause freezing and perhaps laggy behaviour on the keyboard. However, from what you describe, I tend to think it's primarily a hardware issue. (Possibly made worse or even more annoying by software slow downs for unrelated reasons.
If having used different ROMs, key behaviour is still largely the same (eg the same keys respond poorly or require harder presses) then I suggest you have the not uncommon hardware keyboard issue:
Keyboard dismantling pics:
http://forum.xda-developers.com/showthread.php?t=319315&page=2
If changing ROMs leads to varying issues with the key board, but the behaviour of the keys changes ie different keys cause problems then it could either be software or the keyboard ribbon cable is poorly connected.
Mike
thanks for the link,
actually i thought about disassembling my hermes, but then again thought about warranty because its just 2 months of age...
i'll test the keys some more, especially the space, e, w, and "reddot" seem malfunctional... will keep an eye on the keys, and if original WM5 rom does not help, i will reflash the phone to factory default, and return the phone to my nearest store... they will have a solution and if it will be a replacement i'll be happy with it either
greetings
garfield
hi @ all...
sorry for digging this thread out
but recently i recognized my keyboard to be malfunctional again.
with "again" i mean, i thought it worked quite good for some time (lets say a month or so) but for some tome now, i assume 3weeks now, my keyboard throws the same annoying malfuntions as it had done the time i opened this thread. perhaps i ignored them for a while, so i haven't recognized the malfunction, but maybe my phone was really "cured" for some time.
Note: i've been running on the official dopod wm6 rom all the time since i opened this thread. WM% and WM5 original didn't help me, so i decided to stick to WM6. i've just tried 3 different roms, and two pandora self-cooked-roms in the last hour, and tested my keybard very much.
but it seems to be faulty... it lags some keys (in fact "reddot", e, w, space, colon (as a result of the reddot hang) and sometimes i get the "reddot" locked with only pressing it a single time. three words later i recognize that i am writing crap
so... any remainig ideas? or should i return it back to t-mobile?
i tried wm5/6 several roms
also tried various radios, at the moment running on 1.54...
if i want to return it, what do i have to look out for? should i flash it back to original t_mob_101_shipped_rom? and should i restore the original SPL?
i've simunlocked the phone... but did'nt SUPERCID it... always used the Hard-SPL 2.10. Is there any way to bring my phone into a state in which it would be possible and safe to return it?
greetings
garfield
fixed my problem (see first post)
hi all, i bought a tytn at ebay, but
the after a short time of using the bottom buttons, they stop working.
touch screen and buttons on the side are stíll working, but the bottom buttons are dead.
sometimes after turning off amd turning on they are working for a short time again. a restart also helps to make them work.
but its not funny to restart every 10 minutes.....
it is an e-plus tytn from germany with wm5.
do u guys think that it is a hardware or a software error?
I seem to have this problem on and off myself and think it's related to either the rom on the phone or the radio rom but am not sure which. It seems sometimes I have this problem and it seems to come and go depending on what combination of rom/radio rom I have installed. If I was smart I'd find a combination that works well for me and stick to it but I always like to play with things so typically every day or two I'm reseting
yeah, i have the same problem.... i hate to restart the phone every now and then, but I need to figure this out sometime soon, or I'm gonna upgrade to WM6 to see if that solves my problem. lol...
did anybody else have an idea to solve the problem?
crutav said:
did anybody else have an idea to solve the problem?
Click to expand...
Click to collapse
http://cnn.cn/shop/8525tytn-flex-cable-p-1732.html
I opened up my tytn, to find out the problem, and I found a small crack in the flexcable mentioned above.
Before it was never opened nor did anything strange happen with it, so this seems to be yet an other production problem/fault..
More and more people seem to have the same problem, time to presure htc for a repair....
Ok for me this is too late, but all for the good cause.. will just order myself a new cable and try to swap it..
Any ideas where to get the flex cable these days? Not finding it at the link above and internet searches aren't panning out either.
FYI:
Just got back my HTC TyTN from service under warranty, sent for exactly the same problem.
The technician I spoke to directly said that maybe about 90% of the lower keys malfunctions are caused by the lower keyboard board behaving erratically and it is a well-known hardware problem.
A board replacement solved it, my TyTN is working perfectly again, they also replaced the stylus holding rubber (which was broken already from the early days) and, surprise, they upgraded my WM5 device (I had to revert everything to the initial versions before handing it to them) to the latest official HTC WM6 Rom. Even bigger surprise, although what I gave them was a WWE device, when I got it back they had upgraded it to the localized (official Greek) version. Life is good.
Anyways, seems the only real solution to this is a visit to the repair store, hopefully under warranty and reverted back to the original settings...
My phone doesn't vibrate anymore.
I've had it for 4 months now, and it never really experienced any real severe injurie but for yesterday I droped it in my car. Though I am not really sure it wasn't broken before. Anyway, now I can get it to vibrate sometimes, once to 4 times max, but then nothing.
Has any of you ever experienced such a breakdown ?
Yes i have,
there are 2 tiny screws above the vibrator. Last month one screw came loose and felt into the vibrator of my phone. mabey thats your problem. Do u heare someting inside when you shake with your phone?
Greets
nope, not really.
and I am too scared to open the phone. better wait 'til next week when I come back home and go straight to reseller to use the warranty.
thanks for the answer though, I feel less alone.
actually I am experiencing many problems at the same time...
I never could connect through GPRS or any 3G stuff, but I assume my provider is in fault. And I just installed WM6 by Faman, and can't even connect to GSM now ! I am going to reflash to normal WM5.
Hope they just change me the phone without arguing (and why not give me a P3600i instead ? yes I know, I'm day dreaming...)
Hi, a few weeks I have x8. From the first day I noticed that both his work and touch began to do what you will, that is not where it reacts a touch of disparate places, open your applications which are not adequate to the touch with my finger. To do so, leave a screen with power button and still enable him to become adequate. Began to happen more often, sometimes even after the first minute. How to fix a similar problem? Defect Is? I do not believe any of that is rooted because as I said from day one I made such an impression, even while he was in Android 1.6. The time now is with 2.1 and continues to behave the same way.
Wove problem still is present! Even after a master reset and recover with PC Companion. Everything is back to original i rooted it again, etc. but inadequate behavior of touch is their stay.
How to deal with such a problem any idea?
Sorry for my english. I used google translate.
metejnik said:
Hi, a few weeks I have x8. From the first day I noticed that both his work and touch began to do what you will, that is not where it reacts a touch of disparate places, open your applications which are not adequate to the touch with my finger. To do so, leave a screen with power button and still enable him to become adequate. Began to happen more often, sometimes even after the first minute. How to fix a similar problem? Defect Is? I do not believe any of that is rooted because as I said from day one I made such an impression, even while he was in Android 1.6. The time now is with 2.1 and continues to behave the same way.
Wove problem still is present! Even after a master reset and recover with PC Companion. Everything is back to original i rooted it again, etc. but inadequate behavior of touch is their stay.
How to deal with such a problem any idea?
Click to expand...
Click to collapse
I just feel that you have a factory defective phone.. maybe it is better to check via SE tech. Hope they will accept the warranty.. Goodluck
And I think the problem is the factory. I talked to the shop from where I bought it and they said they would send him to repair (though the phone is 10 days). I hope to fix the problem because their problem.
metejnik said:
And I think the problem is the factory. I talked to the shop from where I bought it and they said they would send him to repair (though the phone is 10 days). I hope to fix the problem because their problem.
Click to expand...
Click to collapse
I hope so.. , if they didn't fix hopefully they will change your unit for better one.. keep your finger cross
better ask for a new one, you bought a new phone, not a repaired one...
me too i had a problem with touchscreen. I sent my phone to SE for repairing in warranty on 5 April, now i don't have it yet
A months ago my phone had another problem with the radio (gsm and 3g) and SE repaired it in 2 weeks
Now I've read about a problem of the hd2 having digitizer problems and that only a replacement will fix the unresponsive touchscreen issue. But why is it that when I can get my touchscreen to work that it works flawlessly until it goes to sleep? Then i have to continually wake and swype and sleep over and over until it responds. It just seems very weird that after it wakes that it never seems to have a problem. I'm using the miui rom right now and have set the screen to never go to sleep. So I want to see how long it will go without this problem. Has anyone else seen this happening with their phone as well?
Make sure the kernel, and Rom are up to date.
I have that too on an AOSP Gingerbread rom. The screen is not unresposive per se but calibration seems off some times, strage for a capacitive screen.
ive had the problem with android before and there were a few different fixes ...
one fix was to turn off compatibility mode
another was kernel
ive also had the problem with wp7 ( nothing a few hard resets and patience couldnt cure )
either way good luck
well since my first post, i hadn't let the phone go to sleep once and it worked perfectly fine. so i decided to turn off compatibility mode and let it go to sleep.... and when i woke it and i slid my fingers down it actually worked. so far it's worked every time. why would compatibility mode mess up the touchscreen though?
i have NO earthly idea! just a little tidbit i picked from a dev. i would speculate but would end up looking and sounding foolish. so im going to quit while im ahead and have actually been of help :-D cheers
Where can i disable compatibility mode?
I get the same problem. I've used a ICS rom for a day or so and suddenly the lockscreen was unresponsive. I thought it was ROM problem, so I flashed Cyanogen 7, but the screen didn't respond as well... I flashed everything to stock (removing magldr and hspl) and the problem stayed... After several restarts the screen started to respond and now it works (sort of). The tricky thing is: sometimes when I go out from some app in android, the screen doesn't respond again. Locking and unlocking the screen fixes this, but only temporarily.
Did this ICS rom screw something (...hardware?!) or is it a pure coincidence that a few people encounters the same problem for the first time in such a short period of time...
And one more thing... my warranty expired 5 days ago... please help!!!
I had this same problem with my phone before my warranty expired; before I flashed any android roms on it, and while it still had stock WM6.5. I called HTC customer support and they had me send in the phone for repair. They replaced the digitizer and I haven't had the same problem since. It was wierd because in my mind is seemed like a software problem because it would respond nicely as long as the screen was unlocked and the instant it was locked the response was very crappy, sometimes it took forever to unlock my phone. So it might somehow be a hardware issue
WaspVL1
Machupichu2 said:
Where can i disable compatibility mode?
Click to expand...
Click to collapse
spare parts!
I repair phone myself and i can say that i get A LOT of hd2's with this problem. For the most part it is the hardware because no matter what software you put on the phone it is just a matter of the luck you have to get it working. My hd2 broke 2 times b4 and it was always hardware. Htc must of messed up with the hd2 digitizer
cmacia06 said:
I repair phone myself and i can say that i get A LOT of hd2's with this problem. For the most part it is the hardware because no matter what software you put on the phone it is just a matter of the luck you have to get it working. My hd2 broke 2 times b4 and it was always hardware. Htc must of messed up with the hd2 digitizer
Click to expand...
Click to collapse
from what ive seen in photos of the leo mobo it looks like the connection for the screen/digitizer (not sure on hardware) is located right behind red end call/power button and from being mashed off,on,off,on,etc loosens/damages connection.
or is the hardware screen issue just a complete shot in the darks chance?
OH ... ive had the software issue (fixed as i mentioned earlier) AND unrepairable (with my limited tools and balls to physically tear into this badboy) hardware issues.
well, it's been a few days and my phone still seems to be fine. it hasn't once locked up on me yet. i don't know why turning compatibility mode would fix this. or maybe the phones connectors were loose and are now miraculously back in at the same time i unchecked compaibility mode. the only bad thing was that this was happening the last couple weeks and i had given up and already ordered a sensation 4g. or well, guess i have 2 phones now
Its seems possible. Every since I replaced my digitizer with a non OEM one its has never failed on me again. And I hope it never does. There dam expensive.
rubledub said:
from what ive seen in photos of the leo mobo it looks like the connection for the screen/digitizer (not sure on hardware) is located right behind red end call/power button and from being mashed off,on,off,on,etc loosens/damages connection.
or is the hardware screen issue just a complete shot in the darks chance?
OH ... ive had the software issue (fixed as i mentioned earlier) AND unrepairable (with my limited tools and balls to physically tear into this badboy) hardware issues.
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
Compatibility Mode
I also have this issue, therefore I just recently flashed my hd2 with Tytung's 4.0 ICS Rom. As expected, this didn't help very much.. What I am now going to try before I send my phone to HTC is to disable compatiblity mode. BUT, I can't seem to find this compatibility mode check anywhere. Could someone please guide me there?
..
Windows 7
I will be flashing my phone with w7 now, to see wether this is an android kernel bug / softare issue or if this relates to hardware. I also see a lot of people saying that after fixing the digitizer it works again, so it might actually be a hardware issue. I will post my feedback when I have tried with w7.