[Q] touch screen couldn't come out of sleep? - HD2 Android Q&A, Help & Troubleshooting and Genera

Here is my setup.
WM: stock hk rom 1.72.831.1
Radio: 2.08.50.05
Andriod: MDJ Froyo Sense Clean v2.4
Telstra HD2 T9193
Initial it seemed worked pretty well. I didn't reboot for > 11 days. However, as I used it more. I found more problems.
The touch screen sometimes wasn't able to come out of sleep after idling. I tried to press some button to bring up the screen, the buttons lighted up but the screen stayed blank. I think the backlight was on too.
I found that some people have the same problem just no explanation nor solution. Can anyone help me? I want to switch to android for good but this seems to come up randomly hindering the migration.
I am looking for a stable android build too. NAND, RAM, SDCard are fine with me. Any suggestion? Thanks!

Related

screen blacking out

Hi new to hd2 android. I have tried multiple roms and and droid builds ,but the problem I am having is after I format my sd card with the sd formatter that I was recommended I transfer the android build to it let it boot up. After that I reboot it and set everything up ,and 99% of the time I will set the phone down and when I go to pick it back up I hit the power/end button to turn on the screen and I get no screen I just get buttons lighting up. Is there anything that I am not doing or doing that is causing this. Please help. I am no stranger to electronics as I modify about everyone of them that I own ,but I can't crack this one. I've been working at it for over a week keep getting the same result. If anyone can help me I would greatly appreciate it. Thanks in advance
vdubbri said:
Hi new to hd2 android. I have tried multiple roms and and droid builds ,but the problem I am having is after I format my sd card with the sd formatter that I was recommended I transfer the android build to it let it boot up. After that I reboot it and set everything up ,and 99% of the time I will set the phone down and when I go to pick it back up I hit the power/end button to turn on the screen and I get no screen I just get buttons lighting up. Is there anything that I am not doing or doing that is causing this. Please help. I am no stranger to electronics as I modify about everyone of them that I own ,but I can't crack this one. I've been working at it for over a week keep getting the same result. If anyone can help me I would greatly appreciate it. Thanks in advance
Click to expand...
Click to collapse
It would help if you added your WinMo ROM/Radio and the Android build this is happening with?
Sorry I am running the elegancia gtx right now with the froyostone sense 3.1.7 and the 2.10.50 radio ,but it has done it with numorous builds
Me too
I have the same problem and i have tried several different builds and am running chuckyRom
I have tried the chucky rom and the ozdroid rom as well with almost every single android build that is half way decent. This sucks I would love this phone to be up and running good. Now I did have the combo of chucky rom with the same radio I have now with the hyperdroid 1.6 and it ran for a few days with no problems ,but the darn battery died quick. I haven't been able to get it to work properly since.
Hit the phone button it will wake up faster
Sent from my HTC HD2 using Tapatalk
The problem is its not turning the screen on at all. No matter what button I hit.
vdubbri said:
The problem is its not turning the screen on at all. No matter what button I hit.
Click to expand...
Click to collapse
U have advanced task killer installed?
Sent from my HTC HD2 using Tapatalk
I'm having the same issue, and yep, Advanced Task Killer is installed and running.
same here
i am having all those same problems and i have tried it with and without ATK
I do not have task killer installed not any version of any of the task killers. If a android build has it in it I go in and uninstall it.
Try changing your sd card. I saw some cards (such as team branded) exhibit that behaviour.
Same problem here tried changing the SD card and same thing happens.
Might have found a fix for this for now. All I did is turn auto rotatescreen in android display settings hope it works for you guys.
I have just started using the newest Energy rom with tmobile usa radio and I was getting the black screen of death. After a bunch of messing around I set it to the compact start menu and turned off sense in windows mobile home options and now the problem went away. YMMV
In the middle of reading all the posts here yestarday I glanced at motoman234's sig and I decided to try his setup and so far twelve hours later still no black screen of death. I don't know if it was my winmo rom that was causing it for me or the radio I was using ,but so far so good. The touch screen seems a little laggy which I wish wasn't there ,but again happy to have a setup that is stable.

[Q] Serious Touchscreen Lag Issue

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
This probably belongs in the Q&A forum, not development.
Moved.
For future Googlers and the sort who are researching this issue, the thread has been placed here:
http://forum.xda-developers.com/showthread.php?t=833068
Thanks.

[Q] Desire HD Build Problems

Ok, so ive been using android since around july from the stock nexus one builds, and then found my sweetspot with the Froyostone series with darkstone, after trying several Desire builds(which all worked very well). But after reading about all the advantages of the desire HD builds i went ahead and tried MDJs Froyo HD build. After booting into android, it worked well for about 30 seconds, untill it completely lagged up and was barely usable, so i continued with the setup anyway and got to the home screen (which took about 20 mins), then restarted, but this did not help at all.
Hoping that it was just this ROM, i tried several others, MCCM SE v3.4 and phiremod ACE, all with the same problem.
I never had these issues with any previous builds, any help would be greatly appreciated!
(Also has this happened to anyone else? I didnt see any other posts..)
UPDATE: I changed my radio from 2.15.50.14 to 2.12.50.02_2 and it seems to be running a lot smoother. Will report back, if this is a proper fix...
Did you create a HTC Sense account?
If yes, then your phone will be synced with HTC Sense (means: all your settings like games, apps, whatever will be backupped).
This can take a while and causes lags on your HD2. Otherwise you can disable it in the sync-settings.
Try it. I use the Desire HD build and its the smoothest i ever had.
Yeah I used the sense account on the first desire hd build i tried, then on the second, i skipped all the sync settings, still really laggy
On the m-deejay build I noticed that my cpu was at 100% constantly....
I've seen that RADIO version makes a difference. I am not sure what it is though as it isn't consistent and related probably to RIL version.
Right now I am back to 2.15.50.14 with MCCM 1.2b3 and it's been playing nice.
summoner said:
I've seen that RADIO version makes a difference. I am not sure what it is though as it isn't consistent and related probably to RIL version.
Right now I am back to 2.15.50.14 with MCCM 1.2b3 and it's been playing nice.
Click to expand...
Click to collapse
thnaks for the heads up, im gonna try this radio
After a night of testing, and a radio change, its still REALLY laggy, i really have no clue what is wrong, because using that radio which you are using, "2.15.50.14" it is pretty much unusable.
I never had this problem with the regular desire builds,
I'm on duttys V8 WM rom if that helps? Whould that affect it in anyway?
try with defragmenting your mem.card..
try with Restore Factory Data from SD & Storage menu (it will not erase your data actualy)
format your sd card with SLOW formatting, 32kb clusters
install & boot android
when on lock screen, dont touch the phone for 10 minutes
reboot
when on lock screen, wait 5 minutes, then unlock and do the wizard
after the wizard dont touch the phone for 10 minutes
reboot
when on lock screen, wait 5 minutes, then unlock and wait 10 minutes
reboot
when on lock screen, wait 5 minutes, then unlock, wait 10 minutes and then.. enjoy your fast android.
Yes, it takes time, but it works.

[Q] screen turns white - loses colors! why?

have you got the same problem?
the screen loses colors and get like white - but you still see the android theme, but in extreme white/pink-ish theme.
how to fix that, exept turning on and off the phone? and why does it do like that?
I have the same problem, buy it happens from time to time
im using radio 2.10.xx, witch ver do you use?
Same here.Radio 2.15,using NexusHD2 V1.9G.
Every couple of weeks.
Android in general is like that for us. Remember android wasn't "meant" for our device so there are still some things to work out.
Just restart your HD2s.
also got it from time to time...
it happened when the screen turn off and on too fast.
the only way to bring the color back is a reboot.
exactly the same to me....what's happening?
i use on hd2 the 2.2 froyo nand rom
Ive had (and posted) about this issue in past, its happened only about3-4 times to me so nothing really for me to get worries about. Just curious on what actually causes it and is it a sign of anything other then a driver/software failure?
got this problem ,too. but it started on my device with winmo6.5 cwf´s. i dont think, its a problem with android. iam on radio 2.10...
Same here ... more frequently though ... maybe once or twice a day.
Android HyperDroid GBX v11
Like a previous poster said this happens for me when the screen is turned off and on very quickly, especially while in a call. I think, for a moment, proximity sensor tries to turn on the screen and then off again.
Leo 512 only ?
Yes, system too big or big ! get other build
Me to had this problem using MIUI rom
Decided to do a full phone erase and SD format.
Seems to have fixed it

[Q] andriod on htc hd2 struck on black screen after a call

Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?
I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port
It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english
I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.
Bump!
Anyone? :/
I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13
Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.
Your setup works for me as well - until we`ll see a fix for it this will do
Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat
with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make
try to change the kernel. that works for me
hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired
Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.

Categories

Resources