Related
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.
Hi there,
I have my UNI for about two years now and most of the time I really love the device. It still is faster and has a better screen than most of the other phones out there even today. There is one problem though I really would like to be solved.
I have tried all roms out there and all radio's with varying results however my phone keeps crashing a lot. And when it does soft rebooting it doesnt always help. There are multiple things that can happen and I'll desicribe them below:
- Sometimes it all works just fine
- It can show the bootscreen and then hang on it forever
- It can show a completely white screen forever
- It can show the bootscreen and then suddenly a messy screen filled with random pixels
- It can show the boorscreen and then suddenly a screen with horizontal stripes/beams on it in most of the times two different colors.
- It can show the bootscreen and then the second bootscreen (its mostly green) and then show a fully green screen and stay like this forever.
- Sometimes when it crashes the battery gets really warm
- Often after one of the previous symtoms the phone doesnt do anything anymore when pressing the soft reset butten (expept a small red flash of the left led light)
What sometimes works to get it booted again: get the battery out, put it back in and connect it to the power loader
Also just waiting for a long time seems to help
I always thought it might have something to do with the battery (the original one has the 40% problem) so I bought others. An extended one from dyna, and two others from cameron sino. The crashes and results vary with all batteries. With some it seems to be more often than with others but with none of them it works flawlessly. I have just ordered a new dyna one but somehow I doubt this will solve my problem.
I also have dropped my phone pretty often so there might be something wrong with the main board? I have tried to reproduces a crash by gently (but not too gently) deforming my phone, pressing on it and moving the lid, but that doesnt seem to lead to a crash.
I really would like to know if there is a way to find out why it crashes. Are there diagnostic tools out there with which I can check the hardware? I really would like some help!
Thanks a lot in advance!!
Regards,
Mano3
Hi Mano
Hi Mano,
I guess you are also facing a similar problem like mine. Well you are lucky you are getting an answer since it took me a quite a few hours of searching and nail biting agony to finally realise that, the part of your ROM is corrupted and nothing can be done to get it fixed unless you change the main board.
It suxs but that the truth bro. Hope you can fix it or buy another set.
regards,
techx
Thanks for replying!!
Is there a way to check the integrity of your rom? Then I could check if it is that... I guess I could buy a new main board off ebay or something...
Happy new year!!
Regards,
Mano3
fixed!!
Hey guys,
I solved my problem! So far it is running for two days without any crash! I use the program Pocket Hack Master to set the CPU speed at 312 MHz. Keeping it at this speed keeps my phone stable. When I really need the proc speed I can set it higher to do what I want to do and afterwords I set it back to 312 MHz again. Not the most practical but for most functions the memory is the speed bottleneck anyways.
Hope this helps others!!
Greets,
Mano3
I cheered to early... Problem still there I now bought a new one off ebay, lets hope that works
yesterday i had the problem lots of HD2 owner faced it, my device worked fine, but when i had to soft reset it, it always freezes on the white screen, and never starts up, every many times of taking the battery out, and start again, it finally started up.
i tried to soft reset it again and faced the same problem
i tried to flash the ROM again, but after many tries, i finally got it to flash, but the thing is that the problem wasn't solved, and the unit kept freezing in the start up, but once it started up it worked perfectly until the next soft reset.
but then i tried cooling the device against an AC, and the surprise was that the unis was able to start normally, every time with no problems when it was cooled
any one faced such problem with the device? i will try it again today at noon, when the temperatures are high.
I tried it again now, when the Battery temperature was 38.5, the devise did not start, when i cooled it down, it did start, and when it started the battery temperature was 35.5
can some one with the same issue confirm?
Yes I am having the same problem!
My fone did the same again last night and I'm going to try reflash it today - else the POS is going back to the shop! Not happy!
did you try cooling it down? flashing the ROM did not help me at all
Can this be a Battery problem? that the battery can not provide the required current when it's heated?
ok, i did these two experiments
1- i heated the battery alone on a air heater to almost 45 degree
and cooled the phone, but the phone did boot up normally
2- i heated the phone on the heater and cooled the battery, the phone didn't bootup
so the problem is defiantly with the phone not the battery :-(
khaeid said:
did you try cooling it down? flashing the ROM did not help me at all
Click to expand...
Click to collapse
Yes, onlywhen the phone was cool to the touch again did it boot correctly. However last night it did the same but would not reboot after leaving it for a while. I tried to do a hard reset but the phone hung on the HTC boot screen and would not go further.
This morning the OS booted but was totally corrupt - it looked like booting in to windows 98!! no graphics, no HTC Sense, no usual colour scheme and a whole whole of corrupt file messages. This happened each time I hard reset - and the USB port also failed to recognise any device. I think it's safe to say it is practically bircked and thus, Ireturned it to O2 today to sort out and give me a new handset! I think it is a hardware issue. Infact, I'll put biscuits on it being that vs software.
it is definitely a hardware issue, but the thing is, these are the first few days of summer in my country, the days when the weather is getting really hot, and i guess this is the first summer HD2 will experience, since it was released in the Autumn, so my guess is more and more units will get this issue as the weather get hotter in other countries
Hi guys.
Weird issue you are facing!.. Mine gets very hot on hard use.. today I tried a soft reset while it was hot and it started normally.
When did you bought your HD2?
Crudeoil said:
Hi guys.
Weird issue you are facing!.. Mine gets very hot on hard use.. today I tried a soft reset while it was hot and it started normally.
When did you bought your HD2?
Click to expand...
Click to collapse
i got it like 4 months ago, but i am sure now that there is a hardware issue
had a same problem...
my solution was screawing the middle battery pin under cover...
the hd2 have must have Temperature senzor...
the hd2 have 3 pins under battery cover, 1 = +, 3 = -, and the middle pins is the 2 = ?
i think the middle or the pin nr. 2, is same as ACPI in desktop or notebook, Advanced Configuration and Power Interface,
Operating System-directed configuration and Power Management,
so if your middle pin is screawed, the powermanagement tell to device stop boot!!
or if the pin dont make a contact with battery - the powermanagement canot corectly detect the Temperature and the hd2 owerheat, then randomly restart...
its only my teory, my middle pins was screawed, im take it to the right position and my device worked well... but i want more and more and i broke the middle pin
after that the hd2 boot, and worked but when i want to do restart dont want to boot...
now my hd2 is in service center... so for all i want to say:
warrnig!!! dont youse the power or angry when u want to screaw the pin back
its only my teory, im not the electro technic...
sorry for my english, but i think everybody understand what i want to say
i know sucj hardware issues are unfixable, i am wondering should i get me a new HD2 or another phone
I got mine on contract in March - 1.48 ROM. but also had the issues in 1.66 prior to sending back.
Just awaiting for it to be returned - I'll report back to let you know if sending it away has fixed the issue. I'll be a mite miffed if they just flash the ROM and send it back lol!
had the same issue: overheating / reset loop / stuck on white screen
contacted HTC, sent for repair, received with new mainboard,
now works flawlessly
khaeid said:
i know sucj hardware issues are unfixable, i am wondering should i get me a new HD2 or another phone
Click to expand...
Click to collapse
u can always try i-Phone 4
how hot is summer in Syria btw?
I had the same problem with mine on an UK O2 network. They took it back and flashed it. Sadly that didn't solve the problem. So I sent it back again and they replaced it with a newer model. This seems to have fixed it. Sadly looks like the early ones were crapy and had the same fault.
However mine still gets ruddy hot when connected to the anything in the car.
Bad job HTC :-(
Hi all,
Actually, there is CPU's overheating problem, not battery's. ALLMOST same problem you'll have if you'll remove cooler from your PC's CPU
My LEO shuts down at 38 deg. and cannot start again without cooling. Definitely, it's a price for 1 GHz processor - it should have less power demand or good cooling system.
Hi had the same problem mine also used to reboot on it's own when connected on pc and overheated. Going to contact HTC repair and send it back. I was wondering though is it ok if i send it back with a cooked rom and 2.10 radio or will they not change it cause i've switched that on my own? Any ideas pls?
chapple said:
I had the same problem with mine on an UK O2 network. They took it back and flashed it. Sadly that didn't solve the problem. So I sent it back again and they replaced it with a newer model. This seems to have fixed it. Sadly looks like the early ones were crapy and had the same fault.
However mine still gets ruddy hot when connected to the anything in the car.
Bad job HTC :-(
Click to expand...
Click to collapse
Early model as in what date.month.year?
Regarding getting ruddy hot when connected to the anything in the car, it's the connector, IMHO.
I have problems too. My God, today is the first and really hotest day of the year in Germany.When I will back in Spain at 40 degrees celsius there my hd2 will be a bomb!!
My device is a German o2 hd2...
Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?
thehelios said:
Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?
Click to expand...
Click to collapse
It has been a problem for me with some builds. I suggest you to make a backup with some app like Titanium Backup and reinstall Android. Try with different kernels if you still have the problem. Don't worry for the moment!
I have had this problem a few times. I still can't quite figure out exactly what makes it happen but it seems to be something to do with sleep. My solution is to restart and go into NAND then do a backup apps and then quit. something gets woken up in the screen and it starts to work again. No idea why, it just does. Good luck.
So I guess my touchscreen is just dead. I reinstalled android, reflashed my phone for the froyo rom, and I even flashed a windows rom onto my phone but nothing. I even opened my phone to see if it was connected properly to the mobo but all seems right.
On the windows rom, when it does the screen calibration, I can mash the crap out of my screen and I guess it picks up some sort of signal every now and then because the crosshair moved.
If anyone knows anything about this, please reply. I don't really want this to be the end of my vogue. It's been a good 3 years so far!
http://cgi.ebay.com/Touch-Screen-Di...749473?pt=PDA_Accessories&hash=item439b537fa1
You may just need a new Digitizer.
Can get them pretty cheap on e-bay - just have to wait since coming international mail.
I am having similar problems. Usually when the phone goes to sleep and I wake it up the touch screen is unresponsive. Only way to get touch to respond is to reboot.
I have tried it on my vogue on both the fresh froyo and experimental fat free froyo using both the 10-9 and 9-29 kernel on nand. I have also used nbh editor to change the panel types (vogue uses auto detect so I changed it to Polaris) and still the same problem. I thought perhaps there was a problem with a program but I have no programs installed right now and the problem still persists.
Does anyone have any suggestions? My phone was working fine up to a few weeks ago and I would hate to be forced to use windows again. I have reinstalled windows and it works fine there so I don't think it is hardware related. It seems something happens when it goes to sleep.
Well there might be a driver issue. Try going back to the stock rom for your device and see if the touchscreen works, if it doesn't work, then it's probably broken. Try opening the vogue and disconnecting and reconnecting and then turning your device back on and test it again. if it still doesn't work, then yea you will have to get a new digitizer.
You can also try using other releases/roms with different kernels.
good luck!! and may your vogue live on!!
Thanks, I've installed a windows rom and the touchscreen has no issue there so it leads me to believe it is not the digitizer, especially because it seems to break when it goes to sleep.
I will try even older kernels and perhaps a donut build to see if the problem still exists.
Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.
n2rjt said:
Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.
Click to expand...
Click to collapse
Hi! I had this problem, that was the reason why I put back WM. I experienced it using .32. I think it was from 1-Oct-2010 approximately when it started to fail.
IT'S A CONSPIRACY!!!! Last week my screen broke as well. I was running "not so super froyo" and it would work for a second then just be completely unresponsive... needless to say I now have a droid x *fap**fap*
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.