Database Users

HTC Home Screen after WakeUp

Heys guys,
have a question.
I hope someone of you have a hint for me.
When i power on / wake up (from standby) my HD it switches directly to the HTC Home Screen. I prefer wake up to last screen i was before.
Is that possible?
Thank you for all your hints.
F2

me 2
I have the same issue, any ideas?

Which rom? How long is it in standby?

BLAC|6.5|ROM|WWE| ★ EnergyROM HD (21812) ★ || Build date 2009/6/20
anything between 1 and 15 min - it doesn't look like it makes a difference.
think its the ROM? hope not - digging it

Hi guys,
thanks for responding.
I'm running the Dutty Extreme Rom at the moment.
And there is no time delay... when i switch the HD into Standby and next second i wake it up .... Home Screen...

I am using Black Perl v3 and none of this happens. The device wakes up on the screen it went to sleep. Maybe you should try and ask the people with the same ROM as yours (the specific ROM thread is my best bet) and see if it is ROM related and if it is not... i don't know... maybe it is the screen locking application (if you use any - I am with LockMeLite 1.3 and it doesn't cause this) or some tweaks you made... If it is not a problem for someone with this strange issue to make a hard reset and install all applications he has installed now and see which one causes it.

I'm using the EnergyROM and it doesn't happen? Strange I admit I only tried after a few minutes but If I have something open like explorer its still there when I turn it back on.

good morning....
thank you all for your response.
So, i think it is my ROM i use.
I will try anotherone.
Thank you all !!!!

hello,
yesterday i switched from DuttyExtreme to EnergyRom.
Works fine. WakeUp to my last used screen.
So it must be the settings from ExtremeRom.
Once again, thank you all.

Well that is strange as I have had only had NRGRom.
Any idea if there is a reg setting for this? Actually, @tkolev - I will try a hard reset, was hoping to avoid.

Are you using an auto lock or locking it each time before this wakeup? If you are then that is the source of your problem

My device locks itselfs after 30 mins.
It 's an exchange server setting of our company.
But EnergyRom works also after device locked.
Dutty Extreme not.

Walking dead.... I can't be the only one

Ok I'm using newest energy cht rom radio 2.12.50 and shubcraft froyo android build with 384 zimage....
Heres the problem that I have had all week my phone works fine when I am stationary minimal screen freezes great speed but when I get up and walk with my phone and try to use it the screen freezes almost every time then the entire phone freezes. I have also noticed this on elevator and when I step out of my car.. this is weird and I know it can't be just me as its been going on for a week now.
So to sum it up stationary best phone ever...walking phone dead and I wanna slam it on the ground.
Sent from my HTC HD2 using XDA App

try the desire v5's zimage, no freeze at all

Im having same issues,with all the version i have tried, including V5 aparently this screen freezing is a known issue and makes the use of Android in our HD2 very very frustrating.
ive upgraded my SD to a class 6 and still suffering from it
Im wondering if there is a program that causes it or its just the OS...
in any case We have to be patient ,im sure pretty soon the amazing developers will come with a solution.

might be a screen rotation issue

Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..

miko3d said:
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
Click to expand...
Click to collapse
I've just learned to deal. Its better than SoD's or being in Winmo and having to pull the battery out.

I actually noticed it today as I went from a dark room to a very well lit room so Im with u guys it seems its either rotation issue or light sensor issue andvi have no doubt in my mind the devs will have it fixed in no time just didn't see it mentioned anywhere else so figured it was worth a mention. Thanks all I'm so glad I'm not alone on this one.
Sent from my HTC HD2 using XDA App

when in windows mobile make sure to disable all battery and back light settings and in android change blacklight settings and sleep setting to stay on

I am having the same issue - using ChuckyDroidROM + shubCRAFT CM6RC2, basically when I start moving or even moving the phone the touch screen becomes very unresponsive and sometimes even the hardware buttons don't function properly. At first I thought it was just my device until I saw this post...

Think its a bug with manusfreedoms 384mb ram enabled Zimage dident get this problem using past images.
sure it will be sorted next image release.

I thought i was alone in this case too !
We are not a lot with that screen touch lag, so maybe we did something wrong. Here is what i found so far :
-Changing build don't rix the problem
-tried another radio, another rom...nothing.
I tested 27/07 03/08 cotulla zimage, now manufeeedom 382mo zimage-nopc, the problem is still here.
changed from a class 2 to a class 4 and seems to be worse. (!)
You are right, it seems to be worse when i am moving from one room to another so maybe it is gsensor related.
Right now it is hard for me to type that text,
Don't know what to do... buy a class 10 sdcard ?

I just got my HD2 today and got android set up. I'm noticing the same thing as everyone else with the unresponsive touchscreen. It happens every time I tilt the phone to try to change the screen rotation. Usually hitting the hardware button allows it to respond once again, but it happens quite often.

hey hey hey first and formost i see u guys all hav the same issuse what i dont see is ur device info along with the rom, radio, android verison, and the location ur android is stored ... i have the lates verison of droid v5 also energy with cookie full and my radio is 2.8 i believe android is on the sd card and running smooth ... now that the intro is out of the way hav u guys read what was needed , reason askin i found the thread where the question and answer is... and yes u guys are the only ones... now please do a search go up to the first thread of android on hd2, and good day to u all

Wingtytn, can you be more precise in your answer ? I am a quite long user in Xda, always try to help when i know and i never ask a question wich have been answered somewhere. I don't think i have the noob profile you seems to write. If you think about formatting sdcard, of course i did. I have a 2.08 radio, latest shubcraft build with manufreedom 382mo zimage. My rom was changed to a light android dedicated one, the latest chuckydroid rom. Just don't know what else to do and waste a lot of time trying to fix that from myself.
Sent from my HTC HD2 using XDA App

The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App

shu8i said:
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks a lot shu8i, i will try an older zimage than the 27/07's cotulla.
Edit : Mmh exact same problem with the 23/07 zimage Cotulla_zImage_CABDET_NOSPEEDDY. That is weird.
I will order a clas 10 sdcard and see what happen...

Try the game ”Runners”. It uses both the camera and the g-sensor and freezes mad anytime, anywhere. Huge affirmation to the idea it's a bug of the g-sensor's or otherwize the screen's drivers.
DuperMan

Me too with screen freezes, i had tried all builds and same result. I think this is a problem with SD access because i noticed more freezes as more apps opened in backgroud.

Try to calibrate the g sensor

Found something ...
try disabling auto-rotation feature (settings -> display)
It works perfectly for me now.
Can you confirm that works for you too?
Did you dind a way to calibrate g-sensor on froyo?
Why the auto-rotation feature hangs so much for us?
Sent from my HTC HD2 using XDA App

Touchscreen issue may have found temp fix.

Sorry if this should be posted here but Ive been switching around with all the builds and I have found that with all the builds if I disable auto rotation in system setting I do not get the touchscreen issues ever and Ive been running them for like 3 plus days with heavy texting. However, when I turn it on I get occasional freezing. Just putting this out there so others can try it and see if it works for them too.

Interesting, I've seen other people reporting similar things, going to try it! Thanks!

What is the fix?
Sent from my HTC Desire using XDA App
Edit: didn't read post fully..

Post findings please

sorry i have the auto rotation off since i hate home screen flipping around but i always had the screen freeze problem...

evolutionqy7 said:
sorry i have the auto rotation off since i hate home screen flipping around but i always had the screen freeze problem...
Click to expand...
Click to collapse
Maybe its a rom and build combo plus the auto rotate that makes it work similar to the robot voice

Wow, this one actually worked for me! My screen had stopped registering fast swipes, but I checked this off and now it is! It's even working when I put auto-rotate back on. (It'll probably crap out again, but we'll see).
EDIT: I just noticed that this is the HD2 board :O I have a Sensation. It still worked though. Thanks!

[UPD][Tracking] Andriod HD2 Open Issues

Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.

Hi depakjan, This is great, thanks for tracking these issues.

can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.

i think the bsod is fixed with 2.12 radio and above..

Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...

depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2

hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem

Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..

Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.

Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.

Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.

badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).

Led Notification is not functioning, especially on Sense build.

backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen

jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2

hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!

Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.

hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.

Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy

Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto

[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.