Related
I have owned a JasJam for almost 3 weeks. the device was a little quirky during the first week or so but no major repeatable issues. Then my big issues began. 4 hard resets later I'm trying to decide if it's worth it.
I began having random lockups. that is if I turned the device to standby with the top right side button then when I tried to turn back on the device would be locked up. if I pushed the button more than once it would cause a soft reset or I would have to soft reset to get back on. the problem mainly happens with a micro sd card in place. Mainly happens when some sort of notification ocurrs or if the device is in fringe reception area.
the second weird problem is that the screen backlight will just come on even if I have manually put the device into standby, very much like the 6700 problems with another HTC device. Often I can put the device back to standby with the side button and within 3 - 4 seconds the backlight will come right back on. the only way to break the loop / cycle is to soft reset.
I have Phone Alarm but I have disabled it and the problems still ocurr.
I've tried everything! any ideas?
I ran MemMaid to make sure that there weren't duplicate notifications.
I currently am trialing an 8525 to see if it s possibly hardware (or atleast ROM) related.
Similar issue
I too also experience this issue with my JasJam. I am on the Optus Network (which causes problems unto itself) I have a a 1Gb ULTRA SD card in it also. And yes periodically I need to reset the device by pulling the Battery as it dosen't respond to anything.
Strangely I have a Dopod 838Pro (No SD Card and on Vodafone) and it does not suffer these problems.
Let me know if you find out anything as it would help me with getting the JasJam properly Operational.
Thanks,
Paul.
at this point I am sending mine back to iMate for repair
I think it may be a ROM issue in that the 8125 that I am trialing has not locked up in the first 36 hours a single time!
So i've only had my mogul for 2 days now and so far there have been about 4 occasions where the phone was in standby and when i tried to bring it out of standby (by hitting the power button) nothing happens. The screen stays blank and no buttons work.
On one of those occasions the screen did pop up after a really long time (maybe 20-30 seconds) but still the buttons did not work.
Each time i've ended up having to soft reset the phone (using the pinhole button on the bottom.)
Is this a common/known issue and is there a fix? I've tried searching but haven't found quite what i'm looking for.
Did you buy the phone new or used?
Did you attempt to install any ROM upgrades or a new bootloader?
The Same Thing
I have that very same issue and my phone was brand new!
I have the same issue too. My phone is almost a year old. I flashed it with the Sprint 3.35 ROM and thats when I norticed it. I've never unlocked or put any cooked ROM on this particular phone.
Sometimes I have to tap the standby rapidly like about 10 times before it wakes up.
When I first purchased, same--solution
I was ready to return mine, but what fixed the problem for me was installing a task manager that really closes the programs when the "X" in the corner is tapped, your problem is most likely lack of memory. You have many programs open then activesync automatically starts up it drains memory so far the device locks up. There are many different task managers just do a forum search. Get rid of stock rom, it consumes too much ram as it is.
I have the XV6800 and my first phone had this issue. After removing all added software, still had issue. Did hard reset, and had to call Verizon to re-program the phone. Left phone as stock and still had issue. It seems as though it is a memory/bluetooth problem. Verizon swapped my phone for a new one and have not had problem since.
Now my work got me a XV6800 and am having the same problem with it. I am trying to get them to let me return the phone while within the first 30 days. Good luck and if you can, have your carrier swap your phone.
I had the same issue after putting the latest rom on..after a while it would seem to lock up alot as well. I just recently put on dcd's rom and it seems loads better now!
same thing happening with me. it only happens when i keep the phone on for like 2-3 days without a soft reset. then when i soft reset, it freezes at the windows mobile splash screen and the only way to fix it is by doing a soft reset while plugged in. i am using key's 1.3.1 rom
sorry, i completely forgot i made this thread. I've deduced what's causing the phone to hang in standby.
If i leave any java app running and let the phone go into standby for some time (atleast 10 minutes) then that's when it will have problem not coming back.
I've just made it a habbit of completely closing any java app before putting the phone down. Doesn't happen anymore.
I had this issue a while back but it was because I was low on memory after using the phone 3 days in a row.
Ever since then I soft reset once a day or once every other day.
Other then that the last time I had issues with my phone not getting out of standby was when I was using the stock rom and my alarm clock wouldn't go off because of some weird power settings.
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
Over the last two days my phone is rebooting repeatedly upto 20 times in a row before booting correctly (keeps halting on initial td2 boot screen). Also the phone is locking in standby mode, and will not re-activate until i take the battery out. One other issue I have seen is an error message "the charging current is not enough for device power consumption. Please shut down unused applications or switch to AC power" - when the phone is charging. Has anyone else had any of these issues, or know whats wrong or if it is fixable. Any help would be appreciated!
Thanks.
I had the same problems with the TD2 that a had to remove the battery and restart the device because it wouldn't get out of stand-by or maybe the device went off and i couldn't get in on until the battery was removed and replaced.
Also i had problems that my device automaticly goed out of standby in standby en asking if i want to turn the device off. Already did 4 hard resets. Nothing seems really solved the problem.
Already send the device to HTC with all these problems, and guess i get it back with same problems.
Now my device is working great. A did a hard reset and after installing a program i reboot my device. It may sounds a little stupid but it works for me. Also i installed framework 3.5 on the device now and not on the memory card
sorry about my bad english
I had this problem on the Tytn II when I first got it, and I have only had my Touch Diamond 2 for 4 days and I have had the same problem.
Its called the Standby of Death or SOD by those in the know, the phone fails to respond to a power button press and come out of standby.
I found a workaround for the Tytn II which was soft resetting it everyday, then found a better solution by not running the owner ident screen, disabling 3G and making sure no data connections were active in standby.
On my Touch Diamond 2 I've not been running the owner ident screen but have had 3G enabled over the last few days so my guess is its something to do with that, I have now disabled 3G and hopefully this solves the problem and I will have much better battery life too.
I've tried hard resetting and re-flashing different roms - it makes no difference. Also now noticing today severe battery drain, even when the phone appears to be locked up - battery has gone in around 3 hours. No idea if it is a battery issue, or hardware in the phone though
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
EDIT: Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
I hit problem when reboot the device, it stuck in the green WM startup screen.
Nothing can do, except keep trying press the reset button....very trouble to remove the back cover.
I am suddenly having the "charging current is not enough for device power consumption" issue. It started tonight. I've had the phone 1.5 weeks, and am on my 3rd ROM...have had it running for a few days without this issue. I haven't really been having any issue with SoD...but I have been having SMS issues (after an indeterminate amount of time, I unknowingly lose the ability to send/receive SMS until I SReset).
Could this be SIM related? I don't store anything on the SIM...but it has been in 3 devices over the last 15 months. I have a brand new one here. I'm going to call ATT tomorrow and switch to the new SIM and see if that resolves anything.
I'm in between surgery so thought I'd post a quick question where the answer is puzzling me.
Basically, I'm in wonder if this has happened to any other soul?
Picked up my HD2 when I came out of Theatre and it simply would not switch on.
Thinking it may be the battery that had run down I connected it to a power source to charge and noticed the Orange charge indicator did not light up.
Next I took out the battery and reinserted, then pushed the power button......
Still nothing.
Thinking was it a problematic battery (although it still should have switched on when connected to a power source) I exchanged the battery for the spare I take around with me.
Still nothing.
Finally, I reinserted the first battery and once again pressed the power button.
This time it fired up and loaded without any issue.
I checked the battery level ~ that indicated 56% still remaining.
So I am in puzzlement as to what may have caused it's temporary death.
Has any other had a similar experience?
Edit 01 ~ 24 Feb 2010
It would seem that to some (myself included) there is a fix that does indeed cure the problem and that is by using the software application MemMaid.
Others have tried SKTools but MemMaid seems to operate much better at terminating the freezes.
Unfortunately MemMaid is not free and seeing as HTC will not budge from this being a 'users personal settings' that is causing the freeze our only course of action at the moment is by using MemMaid.
However, please do note..... Not everyone has benefited from using MemMaid; why that is the case could be down to some individuality ~ a different setting, installed software, routine notification, etc. etc.
In other words first try the free trial version of MemMaid and if it seems to cure the the problem then do consider investing in it.... besides all this it is a great piece of software.
You can get hold of MemMaid here.
Word of Warning.....
Ensure you set up MemMaid correctly. I spent ages with member wacky banana throwing many personal messages between the two of us like fervid lovers until finally wacky came up with a setting we could use.
Below is the settings to apply to MemMaid:-
In your programs section you should see 2 icons, one called Memmaid Quick Clean and the other is Memmaid.
Click on the Memmaid icon and a window opens.
At the top left corner it should say Quick Cleaner but this is not relevant for now.
Put a tick in the the following options (the list is scrollable):
- compact ram
- windows temp files
- temp files
- ie cache files
- ie history files
- opera cache
- dead shortcuts
- duplicate notifications
- dangling notifications
- invalid notifications
- rebuild notification queue
- recycle bin
- google maps cache
Press the CLEAN button and wait for the tool to do its job then press the close button.
Next, on the bottom right of your screen, click the Tools option. From the drop-down menu choose CLEAN SCHEDULE.
Tick the following items:
- on soft reset
- daily (here you need to scroll to the right to select the icon with the 3 dots in it to set your schedule)
- show report (optional)
- show progress (optional)
Click DONE on the bottom left corner on your screen and job's a good 'un!
Edit 02 ~ 24 Feb 2010
Member jonbaker76 came up with a few extra tips to help alleviate the problem:-
1). Install MemMaid and follow settings provided by Beards & WB
[*]2). Disable the alarm (use G-Alarm maybe)
[*]3). Turn off Facebook updates
[*]4). Turn off Weather updates
[*]5). Turn off Internet Time Sync
[*]6). Wait a while before carrying out a soft reset, your Phone may just wake up
Edit 03 ~ 25 Feb 2010
Guys,
We are starting to find a pattern building up here relating the problem with Sense.
Some users don't have problems with ROM 1.48 but others Do/Did (I used to) so we can't say v1.48 was okay.
However, it's the later ROM's which seem to have the greater of the problem which could relate to an issue with Sense.
i.e. Although evident in v1.48 it was not as strong but with either Cooked ROM's or updated ROM's the problem has been magnified.
A few Guys have now tried using their HD2 without Sense and report a stable platform.
What I am saying here is if you have the problem and you can afford not to use Sense then try running your Phone without it for a trial and see how it performs...... With enough info we can pass this on to HTC.
I had a situation where I switched the phone back on (from standby/power saving mode) only to find it was dead. To get it running again I had to perform a soft reset and, like you, I found that I had plenty of battery remaining. This happened only once in three weeks of usage and I'm not sure what caused it.
James
I had a similar issue a few days ago.
I picked the phone up and pressed the power button, but nothing happened. I did the same as you and assumed that it was flat (despite me being a charging maniac!) I plugged it in and got no charging light, so I popped out the battery and put it back in. It turned on first time then.
I wasn't really concered as it's only happened once in over 3 weeks, and I'd only recently upgraded the ROM so I was ignoring any little foibles like this.
Maybe it's a little more common than I thought?
this has happened to me twice since upgrading to the new recent rom.
Beards said:
I'm in between surgery so thought I'd post a quick question where the answer is puzzling me.
Basically, I'm in wonder if this has happened to any other soul?
Picked up my HD2 when I came out of Theatre and it simply would not switch on.
Thinking it may be the battery that had run down I connected it to a power source to charge and noticed the Orange charge indicator did not light up.
Next I took out the battery and reinserted, then pushed the power button......
Still nothing.
Thinking was it a problematic battery (although it still should have switched on when connected to a power source) I exchanged the battery for the spare I take around with me.
Still nothing.
Finally, I reinserted the first battery and once again pressed the power button.
This time it fired up and loaded without any issue.
I checked the battery level ~ that indicated 56% still remaining.
So I am in puzzlement as to what may have caused it's temporary death.
Has any other had a similar experience?
Click to expand...
Click to collapse
May be a warning from HTC for your now very famous camera thread,if I were you would be carefull LOl!!
hagba said:
May be a warning from HTC for your now very famous camera thread,if I were you would be carefull LOl!!
Click to expand...
Click to collapse
....
Big brother watching us...
Beards,
Did you have any diary appointments or alarms set on the device today that you did not immediately cancel on notification or multiple alarms set/going off? If you did then this is probably a notification queue issue locking up the phone, forcing a reboot.
This symptom was very common with the TYTN when it first came out and drove me absolutely bananas!
Long shot but let me know.
WB
No... nothing was left to tie the Phone up.
I remember checking everything before I went down to Theatre earlier this morning.
In a way I'm pleased it's not an isolated case and that others have experienced something similar (sorry Guys, I don't wish it on you ~ just a little relieved I'm not the only one).
I know HTC monitor the 'Camera Problem' topic (they've told me this directly). Maybe they have some super-duper exra-terrestial monitoring machine that can achieve the Dynamics of masspoint collections..
Yep, I too have had this issue.
Was using phone normally, left it on stand by by pressing the power key. Wanted to make a call, it did not turn on. Opened back cover to do soft reset, did not turn on, started sweating..., swore at the phone and took battery out and then replaced battery and pressed power button and what do you know, booted up like nothing happened.
Am using original shipped UK ROM. Have not upgraded.
You should check this as well (first 2 might be from the same poster):
http://forum.vodafone.co.uk/index.php?showtopic=41974
http://forum.xda-developers.com/showthread.php?t=591226&highlight=freeze
http://forum.xda-developers.com/showthread.php?t=595646&highlight=freeze
I had the same problem - it happened only 2 times for a week, but it was nasty enough (and in combination with the camera problem) to make me finally send my phone back for a refund.
Basically the symptoms were similar - I would leave the phone somewhere for more than a couple of hours only to find it somehow switched off or something. The buttons light up when clicked, but the screen remains black - only battery removal helps and after that runs like normal...
I have quite a number of calendar notifications etc. - this might be a good clue!
I have the feeling that this thread might grow as big as the camera thread. Perhaps HTC fix that with a software update as well ...
A friend of mine had this problem with his HD2 on Sunday morning. He was surfing the web with it when it froze up. When he took the battery out/in again it wouldn't turn on.
He called HTC and they came to pick up his handset on monday. I guess he'll have to wait to get it back repaired Maybe he should have tried taking it out a few more times first.
deyanp said:
You should check this as well (first 2 might be from the same poster):
http://forum.vodafone.co.uk/index.php?showtopic=41974
http://forum.xda-developers.com/showthread.php?t=591226&highlight=freeze
http://forum.xda-developers.com/showthread.php?t=595646&highlight=freeze
I had the same problem - it happened only 2 times for a week, but it was nasty enough (and in combination with the camera problem) to make me finally send my phone back for a refund.
Basically the symptoms were similar - I would leave the phone somewhere for more than a couple of hours only to find it somehow switched off or something. The buttons light up when clicked, but the screen remains black - only battery removal helps and after that runs like normal...
I have quite a number of calendar notifications etc. - this might be a good clue!
I have the feeling that this thread might grow as big as the camera thread. Perhaps HTC fix that with a software update as well ...
Click to expand...
Click to collapse
I had something similar this morning, I have been using the alarm for the last 2 weeks with no problems. this morning the screen lit up, i saw the notification on the top but there was no noise. as a veteran of WM i dismissed it as "typical". however, the screen then went blank, the buttons would light up but nothing happened. I reset the phone to no avail, button still lit up but no screen - mild panic. removed and refitted the battery and all has been well since.
won't be too chuffed if it happens again....
rivets
Beards,
Notwithstanding that this may be some kind of new software or hardware problem, I just wonder about the notification queue.
I would try using a copy of SKTools to clear the notification queue ( I think you can do other tweaks as well but it's been a while since I used it) and see what happens.
Did you have any missed calls you did not answer today (another possible culprit, linked into auto screen lock = disaster).
I am simply putting ideas out for you to try to narrow the problem down. Don't know if any of this will work.
WB
PS: Just had another thought; have you installed an application onto your SD card that is on-screen? Used to have this issue with a weather application, sat on screen but installed to the SD card.
If the phone went into sleep mode and the application polled the weather servers then it would die a horrible death. De-installing and reinstalling to phone memory solved the problem.
Again its a long shot but you never know.
WB
Ive had that same problem twice last night within th space of 1/2 hour and the today i ran fine up until about 5pm today, where it froze, I updated the rom on sunday from O2 1.43 hope this is not gonna be a problem, anyone know where to get O2 1.43 rom just in case I have to return
wacky.banana said:
Beards,
Notwithstanding that this may be some kind of new software or hardware problem, I just wonder about the notification queue.
I would try using a copy of SKTools to clear the notification queue ( I think you can do other tweaks as well but it's been a while since I used it) and see what happens.
Did you have any missed calls you did not answer today (another possible culprit, linked into auto screen lock = disaster).
I am simply putting ideas out for you to try to narrow the problem down. Don't know if any of this will work.
WB
PS: Just had another thought; have you installed an application onto your SD card that is on-screen? Used to have this issue with a weather application, sat on screen but installed to the SD card.
If the phone went into sleep mode and the application polled the weather servers then it would die a horrible death. De-installing and reinstalling to phone memory solved the problem.
Again its a long shot but you never know.
WB
Click to expand...
Click to collapse
Even though my profession is based on absolute accuracy in detail, when it comes to finding out why the HD2 died I'll try any long-shot.
There were no programs loaded though and I know nothing was paged to make the Phone send any notifications.
I'll have a good check at possible programs/dll's later though.
Thanks.
I've had the same a few times. Probably the reason was overloaded main memory. I removed some mp3 files, but the situation wasn't change.
htc touch pro2 vs hd2... just got the answer!
a day ago... i was unsure about the upgrade. i had posted tis msg in xda but was advised by a senior member tat it was worth the upgrade n i culd find all my answers to the query here. here was my msg...
"hi all. with all the hypes surrounding htc hd2... n my htc touch pro2 fast losing its crown of being the best winmo device in the market... shuld i upgrade to the hd2? n watz wif the glass screen? wuldn't it crack easily? it's glass! appreciate everyone's take on this. the only selling point tat is tempting me away frm my pro2 is abt the speed... 1ghz vs my miserable 528mhz... sad. everyone's talking abt its blazing speed. is it tat obvious?!
then again there's tat camera issue... the infamous pinkish spot, which htc support claims it's related to the 1ghz dragon fella... software related... n restricted to only a selected few?! so it's like going2 the lottery n c who gets the infected piece is it?! bottom line is... my pro2 seems like a honda civic... n the hd2 is purportedly a nissan skyline, but wif so many question marks hanging over its head, shuld i still go for the upgrade? thnx!"
guess wat, after reading most of the threads here... i think i'll stick with the htc touch pro2. the hd2 has way too many issues... even worse than the camera thingy tat i knew abt... but the number of issues tat r highlighted here abt the hd2... is enuf2 make me say no to hd2.
This thread here reminds me to some issues with WinMo 6.5/Manila 2.5 ROMs for the Xperia X1: Over there in the forum, you can find quite some postings describing the "standby of death" problem.
Just very close to some of the other issues we now face with the "real" Leo, too. In fact, there are more "similarities" like the stand-by issue, and nobody was really able to clearly reproduce the problem as there seems to be no pattern. The same problems are not existing in WinMo 6.1/Manila 2.1 ROMs for the Xperia - but some in a WinMo 6.1/Manila 2.5 version, when I follow the thread correctly.
I do strongly believe that there are, underneath the hood of Leo´s operating system, quite some nasty bugs in WinMo as well as Manila. I cannot imagine another explanation why 2 totally different devices with very different hardware (parts) would show the almost exact same issues.
Of course, porting the Leo ROM to something like Xperia may bring some issues, but most apparently, most bugs are coming from MS and HTC, not the talented chefs here. (One more reason to look forward to custom ROMs for the Leo. No good sign for HTC though, frankly spoken...)
mine die this morning too ... alarm didnt go off
but press and hold the power button wake the phone up and alarm start ringing. Then I power it off, and all the other buttons does not turn on the phone other than press and hold power button = soft reset ... weird
Camera patch is out today
waiting for new ROM release
Same thing happened to me this afternoon. The phone wouldn't start up when I pressed the power button so I tried holding the power button down to force a soft reset. At one point all the buttons lit up but nothing more happened. Eventually I pulled the battery out, stuck it back in and then the phone started.
First of all, sorry if this thread is out of place, but I'm not sure where else to turn.
My HD2 worked terrifically with FroyoStone 3.2, Hastarin 7.6 up until last Wednesday (5 days) ago. Then I started to experience, and have not been able to fix, serious TS lag issues.
Symptoms: I hit the unlock button, swipe to unlock, and the touchscreen will be responsive if I KEEP using it...if I pause for up to 3 seconds, the screen is no longer responsive. I have to relock the phone, unlock, and then swipe again to get it to work.
The touchscreen works perfectly fine in Windows Mobile 6.5. (Energy 2361X)
Attempts to fix: I've formatted the SD Card inbetween trying all of the following items-
1) Switch to MDJ ROM with MDJ kernel
2) Switch to Bluetopia ROM (0.5, 0.6 & 0.6.1) with Hastarin 8.0 OR 8.1
3) Switch back to FroyoStone 3.2 with kernel that comes with it
4) Update Radio ROM
5) Update to new Energy WinMo ROM -- after running Task 29 first.
Today, I purchased a new SD Card, loaded it with a clean install of Android, still have issues.
Also tried:
1) Turning off all LED notifications
2) Disabling Auto brightness in WinMo and Android
3) Disabled Screen Auto-Rotate
Honestly, I'm all out of ideas, and I hope someone in the community has a way to help out. I find it so odd that the touchscreen works great right after a "wake-up" as long as I keep it constantly stimulated...then fails to respond if I let it sit for more than three seconds. Is this a polling issue?
All ideas are appreciated. Thank you
UPDATE:
Followed another thread that suggests using the exact same WinMo ROM as the Builder -- matched my ROM with cmylxgo's WinMo ROM (author of Bluetopia) after another Task 29...no fix.
More Information
UPDATE 2:
Also tried 32K clusters and 64K clusters when formatting the card. Problem exists with either size.
There are G-Scripts to disable the G-Sensor and then re-enable it without rebooting.
If you want to jump to the extreme and want to remove all the sensors entirely.
Code:
su
rm -rf /system/lib/hw/*.sensors.so
Terminal
Thanks for your quick reply.
Unfortunately, I'm not the best with working with Linux/Terminal commands -- I tried typing in your code, and it returned that there was no such file/folder as -rf, and then I removed that section, and it said that it could not find the system/...
So obviously, there's something I'm missing, or an error in the syntax, that I cannot debug.
Any help is appreciated.
Are you having any data freezes or are you on an area with poor to no signal? I get really bad system lag when I loose signal while my phone is trying to download. Ppp will freeze and the phone will be unresponsive till reboot. Only way I avoid this is to turn off data if I got into a building I know I will loose connection in.
Sent from my HTC HD2 using XDA App
Updates
Thank you for your reply --
I checked into the disconnects being an issue by enabling Airplane Mode and seeing if I still had the same results, and unfortunately I do. I tried by disabling the Wifi and Mobile network separately, and still same issues.
But, here's an update on the issues:
Installed TYTUNG's NexusHD2-FRG83 V1.6, and this thing is very, very lightweight. Great battery life, great data (went to sleep, woke up, and not only was my phone still on...but I didn't have to reset data to check email...nice). The issues still remain. These are the newest things I've tried:
1) Remove Boxwave screen protector
2) Run from Airplane Mode.
I did however notice something really, really important: when the screen freezes, if I simulate a multi-touch gesture (pinch to zoom, etc), sometimes it wakes up! This is not a guaranteed thing (like 60%), but definitely something to work with.
Also, I noticed that one time that the touchscreen stopped responding, I tried the multitouch, no help...but I stayed on it. Multitouch tapped like crazy for a solid 6 seconds...then tried to shut the screen off -- and that button didn't respond. It was as if I saturated some bus of some sort that it had to clear out before it could finally shut the screen off.
Finally, I've noticed that the screen just needs to shut off for the touchscreen to unfreeze -- not go into a full lock situation. So, if the screen goes black, and I hit the lock key immediately, it'll unfreeze the TS.
Thanks to everyone who is trying to think of an idea!
i seem to be having the same issues as you right after i wake the phone up to unlock it. locking the phone is a habit for me to try and save as much battery as possible and also to not press any buttons while in my pocket.
im running a cyanogen rom and i changed the setting to allow me to unlock the phone by pressing the center windows key. i noticed that when the phone will not allow me to unlock it i can press the menu key and unlock it but i cannot use the touchscreen at all until i relock and unlock.
sometimes i have to do this a few times before the touchscreen comes back. i was thinking it could be my sd card but this started to happen today. i have been using android on my hd2 daily for the past 12 days without any problems. its weird that it started all of a sudden.
so it seems we still dont have a fix for the touchscreen freeze yet, right ?
Same problem here
Hi, I am experiencing the same problem.
Tried few versions of Android, The same problem repeated itself.
So I had to return to WM6.5 - there it works good. Only I have to reset the phone twice a day :-(
Hope someone will find brilliant solution for the sad problem that prevents using Android...