Related
I recently got a Touch Dual/Niki and from time to time when being in standby (the screen turned off) it doesn't respond on any button press, nor does it react when trying to call it, I've got it back up and running only by removing the battery, setting it back and then I can turn on the device again.
I haven't really customized anything and the only 3rd party software that I know that have been running at the time are gmail client and/or live messenger
Anyone else experienced the same problems? ..does this seem like some software bug, or is my hardware faulty?
Rom: 1.31.414.02
Rom date: 11/02/07
Radio version: 1.58.16.27
Protocol version: 25.61.30.03H
Operator Saunalahti/Finland
same problem here!
I'd guess hardware, but just to be safe, you should probably do a hard reset and see if that helps. I had a problem with mine where it would lose random amounts of time every once in a while (the clock would be completly wrong) and the screen would become completely unresponsive for over a minute just after I rebooted the phone. At one point, it just decided it didn't want to boot and just got stuck on the WM loading screen, even after multiple hard resets. I replaced the device and the new one works perfectly.
yup, me too.. happened today after i finished a call. i just left the thing alone for a bit & was ok later
ok, just did the hard reset, if it happens again I'll go replace it
Lord of the Badgers said:
yup, me too.. happened today after i finished a call. i just left the thing alone for a bit & was ok later
Click to expand...
Click to collapse
same here. at the moment I try to live with that, although it's rather annoying. happens 3 to 4 times a day. no response to touchscreen or buttons, but touching the screen makes the backlight going from dimmed to bright. (you know, after quite a while being idle, it dims and after another while it goes to standby)
about half a minute later it's back and executes some (or all) of the inputs at once.
I use some third party programs and tools, but nothing which diggs deep in the system (except AEButton+). So maybe it's one of them. Also I use scheduled IMAP synchronization, which may also play a part in this.
Any one-fits-all solution is deeply appreciated. (Not very impressive to show a frozen device...)
Cheers,
jekk
Ok, it just happened again.. I'll go complain to service.
Same thing here... happens whenever it feels like it. I thought it may have been one of my apps.... particularly Photo Contacts Pro as every now and then that does some strange things, but interesting to know this happens to others as well.
yeah
just happened to me again as well
any solutions?
*bump*
Currently I wonder whether this is a hardware or software issue. So some questions:
did someone flash the problem away?
did someone hard-reset the problem away?
did someone device-replace the problem away?
This would be helpful.
Cheers,
jekk.
Flashed my niki.
I'm getting very regular freeze up's on browsing the internet with a 3G connection. I'm waiting for a new ROM to arrive to determine if the problem is software/hardware (unless both ROM's use the same base Rom )
My old prophet had an easy accesible reset button, unfortunately I have to remove the batterycap now and I have a feeling the mechanisme won't hold for 2 years if I open it every day a couple times.
FWIW, my device is currently sent in for service, I'll report back with the outcome when I eventually get a device back..
Isn't it just brilliant, after a week of "service", they tell me freely translated: "No problem found. Device reset. (Might it be the standby mode from which the device wakes up by pressing the power button?)"
Of course they did not bother to call me to ask for further clarification... Now I'll have to wait until it arrives back at the shop where I sent it in so I can go and send it back..
Oh the joy!
Same freeze problem
Hi guys
I' have same freeze probleme on my niki, i made hard reset without solving nothing.Only solution remove battery and restart.
In my case it always happens while system is in stand by so my phone goes offline and i havent any advice.
Last mornig after a night recharge a foud my niki completely uncharged with red led.I have ordered a new battery hoping the problem may be in my battery.
I had the same problem. Sometimes it wouldn't wake up when I pressed the powerbutton.
Last thursday I flashed my device with Tom Codon's ROM.
http://forum.xda-developers.com/showthread.php?t=364335
I haven't got the problem since
I had never experienced any freezing problems with my niki until yesterday, when I first started using my new 8gb sdhc microsd card. Now it has happened three times! Is it possible that the driver is to blame? We know older devices had some perculiar issues with external storage upon wakeup.
For clarity; I have a 16-key niki from orange using the stock rom and the card is an sandisk class 4.
Let me know if you guys have a similiar setup.
SMYKUL said:
I had never experienced any freezing problems with my niki until yesterday, when I first started using my new 8gb sdhc microsd card. Now it has happened three times! Is it possible that the driver is to blame? We know older devices had some perculiar issues with external storage upon wakeup.
For clarity; I have a 16-key niki from orange using the stock rom and the card is an sandisk class 4.
Let me know if you guys have a similiar setup.
Click to expand...
Click to collapse
I've just hard reset mine .... now seems stable ... before it was freezing every time I tried to use it.
So now I have no SD installed + no apps.
Before
SD with very few apps
Sprite backup HTC version
Informant previuos version
Flex Mail 2007
Copilot 6
Fsecure from Tmobile customisation
So I am thinking SD compatability may have been my issue ... I only had a 2GB Sandisk Premier. Will try a 1GB later
SMYKUL said:
[...] until yesterday, when I first started using my new 8gb sdhc microsd card.
Click to expand...
Click to collapse
That's interesting... I am also using a (4gb) micro sd card. Maybe this really is the reason for the freezes. hard resets (2 till now) didn't solve the problem for me and I have not tried flashing a new rom yet. so this goes well with the possibility of a misbehaving driver thing.
As I wrote I only had freeze up's during browsing the www. After reading that there might be a sd-card driver problem I changed all IE temp directories back from the storage card to the device itself and I now can browse uninterrupted. So it seems that there is a slight driver issue.
Ralph
Changing SD card semed to fix things for me ..... at least for th last few days.
Before I swapped card I had constant problems
Hi everyone. I wanna tell you about something weird happening to my HD2 lately that’s really pissing me off. Every once in a while, when I wake up my device from standby or for instance after receiving a text, I’m not able to unlock my phone!! I try to move the slider all the way to the left or right, but the screen is totally unresponsive. It’s like my fingers aren’t touching the display at all.
I therefore turn the screen off and on again several times and eventually I happen to “resume” the screen sensitivity and reach the homepage. The phone is not frozen since it works fine when unlocked, just the screen.
Even more weird is the fact that if I remove the battery and restart the device, when I get to the PIN Code screen I’m still not able to enter any digit since the screen is still unresponsive and I have to do the whole display off/on routine several other times till it gets sensitive again. This problem is starting to happen more and more frequently and with several ROMs.
At first I thought it was rom related so I switched from “Miri v17.4” to “Energy June,11” and then to “HyperROM Ultimate v12”. Nothing, nada, zip. The problem still remains. Then I tried running Miri v17.5 with no extra apps installed, like BSB or CHT or whatever because I know sometimes programs can have incompatibilities with roms so I tried to keep it as stock as possible, but that didn’t solve the situation either.
I performed a “task 29 by doloop” between each flashing and tried many radios as well (2.10.50.28_2, 2.10.50.26, 2.11.50.20 and now I’m on 2.12.50.02_2).
I’m really desperate because I don’t know what’s causing this. Any help/advice is greatly appreciated!
Sorry for the long post, I tried to describe this issue as accurately as possible.
Thanks.
Many people are having this problem. Many topics about it too, but no final solution.
In my case two things seemed to help: adjusting light settings (turn off automatic adjustment) and taking out SD card and putting it back in, and/or change the SD card to a faster one.
I even reflashed my phone and the problem persisted until I was finally able to put back a stable backup.
First off thanks for your reply. I just checked and automatic backlight adjustment is on. Are you saying this problem might however be ROM related? Some time ago when I was using MIRI v16 this problem occurred just a couple of times and I didn't give it too much attention. I was wondering if the touchscreen might be faulty and therefore in need of assistance..
I don't think it's ROM related, well at least not in my case. I didn't have any problems using stock ROM and an 8 GB card, until I bought a 16 GB card (the exact same day the problem occured for the first time, I just didn't realize it could have something to do with the card, until I read this forum and found my own post about the screen not being responsive dated May 3rd, the day I started using the card ).
I installed Cookie's Home Tab 1.8.5 (on my card) and the screen became unresponsive again and I had a lot of problems uninstalling it, because of that screen problem. So I did a hard reset and the problem still persisted, couldn't even use the wizard because the screen wouldn't respond.
I think it's a combination of hardware and software problems. Hardware meaning SD card and software meaning power settings (automatic light adjustment), maybe the way the software is written to the SD card, I don't know.
I've got it working now, but I'm a little afraid to do any more tweaks and I would very much like to use the light adjustment settings.
So I'm still testing and maybe some day I'll buy a new SD card class > 4. The 4GB card, class 6 seemed to help the last time I hard reset my phone.
Yeah I get your point but still I wonder why has this issue just happened to show recently. With the older ROMs everything was working fine and none of the above ever occurred.
That leads me to 2 conclusions:
1. Newer ROMs (mixed updated packages from different sources) are less compatible with the phone and thus create a new series of problems, mine included (just take a look at some of the latest rom changelogs to see for yourself what I mean). All of this not to mention the extra complications that programs such as CHT have caused..
2. The screen has became faulty. Maybe in the earlier phases the problem just happens occasionally and becomes more and more existent as the touchscreen module “degrades” (or something like that..)
Just yesterday I turned my phone on and the screen was unresponsive (I’m running miri v17.5). I tried removing the SD Card and disabling the auto backlight adjustment but none of these helped.
Anyway, here’s what I’m gonna do in the next days:
I’ll flash MIRI v16 which is a ROM I don’t remember having this particular problem with and I’ll see how it goes. Should the unresponsiveness occur again, I’ll go with a stock ROM (the one the phone came with).
If both of these tests fail then I’ll send it in for repair.
It goes without saying that I’m all ears for any advice/help you guys can give.
Thanks.
http://www.youtube.com/watch?v=VHy_t-DHqq8&feature=related
I did... It's working now...
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
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.
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.