Related
Hello Guys,
I am posting here because I have this strange bug for a couple of weeks now.
I'm hoping someone had the same bug and could identify where it comes from. Or which app may cause this?
* Sometimes, when I want to make a phone call, my HD2 freezes.
* It apparently makes the phone call, but the screen is blocked, I can do nothing, and I cannot hear the callee. I cannot end the phone call.
* The callee can hear me.
* After 10 seconds my HD2 shuts down by itself and restarts automatically.
* Everytime it restarts this way, the Time is changed and is wrong.
It happened to me around 10 times already.
If any one of you had the same bug and could help this would be greatly appreciated.
Could any third app cause this. Actually it happens even if no application is running!
Thanks in advance.
My ROM is Miri WM 6.5.x v17.
Significant third party applications or Tweaks are :
Co0kie's Home Tab 1.8.5 and CHT Editor,
Ameba + Ameba Launcher + Ameba Settings
Kinoma Play, CorePlayer, Ruttensoft Cloudfiles,
AE Button Plus, SK Tools
Batti, Skyfire, CSMI,G-Alarm, SPB Time
Some Touch-X tweaks (power management, Wifi N, speed up scrolling, Opera max memory, smoothness, 6 tabs, etc...)
The problem is recent and the only apps I added recently are Ruttensoft and G-Alarm.
friendly bump
I've got the same problem on mine with Dutty's HG v.2.9 & 3.0. I've only noticed it on Bluetooth with a Motorola H17 headset... I've recently updated to HG 3.1 and will not use that particular Bluetooth anymore... Hopefully that fixes it
I have the same problem. This phone (hardware) is the best phone on the market but you know what. Windows Mobile frickin blows. I get so upset cause my phone always freezes and I have to turn it off and on, or even take the battery out.
I honestly may ditch this hunk of junk and get a my touch slide, that is how unhappy i am with this operating system. How anyone could like windows mobile is beyond me.
If it's any help I'm on Dutty's 3.1 HG, with Cookie's HT and Editor, with Microsoft Voice Command installed, Coreplayer, Omarket, Def's Taskbar, Chris middle lock screen slider, Total Commander and PHM installed... (with other things that escape me now)
I'm currently on a call on BLUETOOTH with the BlueAnt S4 right now and going on 16minutes and received 5 emails and checked the weather and played around on my home screen and it has not frozen at all... I honestly believe it may be the Motorola Bluetooth that is messing it up.
The only other thing it can be is my car stereo's USB connection for music might be corrupting it as well... we'll see about that
(17 minutes now!!! *CROSSES FINGERS**)
Lasabar said:
If it's any help I'm on Dutty's 3.1 HG, with Cookie's HT and Editor, with Microsoft Voice Command installed, Coreplayer, Omarket, Def's Taskbar, Chris middle lock screen slider, Total Commander and PHM installed... (with other things that escape me now)
I'm currently on a call on BLUETOOTH with the BlueAnt S4 right now and going on 16minutes and received 5 emails and checked the weather and played around on my home screen and it has not frozen at all... I honestly believe it may be the Motorola Bluetooth that is messing it up.
The only other thing it can be is my car stereo's USB connection for music might be corrupting it as well... we'll see about that
(17 minutes now!!! *CROSSES FINGERS**)
Click to expand...
Click to collapse
Scratch that... froze @ 20'00'' on the dot... frick
Thanks All for your answers and feedback.
I am not using Bluetooth. So I guess this is not the cause.
Apparently it is not ROM related (Miri roms are knows to be very stable and the problem also appears on Dutty's Roms)
So I have the feeling that it may be caused by a 3rd party application.
Ameba ? Co0kie's Home Tab ? I don't know...
I keep my fingers crossed. Maybe someone has the solution
There's a thread on the boards now about phone freezing/hard resetting and they reference Task29.exe...
I've not know about this and just performed it and put back on Dutty's Rom and we'll see...
S... It happened to me again this morning.
Don't know what to do. Could this Task29.exe. procedure really solve my problem? Gonna try.
Hi, in the past i've this problem :
when an incoming call, the phone freezes and suddenly forced to make a soft reset.
have you installed HD2 tweak?
For my part, this problem due the option of the phone's response time before an incoming call, it should not modify.
i 've done a hard reset because impossible to call or receive a call, even having given the option as original.
Perhaps, that would resolve you're matter
hi... same problem as here..
my phone restart once in coreplayer, next time in igo, next time in settings tab... i dont know what is it..
i flash back the stock rom ... but dont help...
i belive its not device bug or bad sector in phone...
maybe its can do same appl. waht we installed..
i think its can be chainafaier driver or leocpuspeed...
but its only id...
thanks for the feedback and tips.
actually i am not using BSB tweaks, Leo CPU speed or Chainfire driver.
so the problem probably comes from another application.
Are you using Microsoft Voice Command?
I'm racking my brain as to why mine can't make a call..
I've installed the STOCK ROM 1.66 and it's stable as all get out, but I've installed nothing else... and my phone just got done with a hour and fifteen minute conference call no problem
no, I didn't....
if only i could discover what creates the problem
freezing
Dont know if you have the same issue, i got mine sorted (shutting down fm radio properly and not just pulling the head set out) after reading this
http://forum.xda-developers.com/showthread.php?t=618621&page=2
Guys are you sure you have the right radio flashed?
I've had this problem too, and a new radio/reflash of the radio fixed it.
I flashed back to the stock telstra rom/radio and couldn't get past a call in 5 minutes
I flashed another Radio.
And so far the problem did not occur again.
May work . Thanks lonelykatana.
Unfortunately, the problem is still here.
I make a phone call and my phone freezes
Cannot believe I'm the only one
arturobandini, you are not the only one. I just got my HD2 4 days ago. I have gotten like 10 freezes already during calls. The phone wont let me unlock. This phone and with windows mobile must be the worst phone on the market. I cam from iPhone that thing has never failed me for 2 years. I HATE WM6.5 but i am stuck on T-Mobile for 2 years sigh...
Didn't see a megathread for the Froyo release I'm on, but I have the HD2 release from August 18th.
Problems:
1. Screen backlight will turn on, backlight to buttons comes on, but no image is displayed.
2. Screen almost totally stops responding, when it does it's acting as if I'm holding down on something. I try and turn off the screen, and it takes a few minutes to turn off.
Solutions? Don't know. I tried hard resetting, but that doesn't do anything. I'm using the suggested Miri ROM. I tried Energyrom, that didn't do anything different.
I have exactly the same problems..
agentfazexx said:
Problems:
1. Screen backlight will turn on, backlight to buttons comes on, but no image is displayed.
2. Screen almost totally stops responding, when it does it's acting as if I'm holding down on something. I try and turn off the screen, and it takes a few minutes to turn off.
.
Click to expand...
Click to collapse
1. It's a common problem. Try latest builds and you could have a fastest response during wake up...but the problem persist.
2. It's a problem caused by G-Sensor. Try disabling Auto Rotation and probably this problem go away.
P.s.: Next time read some post. It's a problem already know and posted
stalvatero said:
P.s.: Next time read some post. It's a problem already know and posted
Click to expand...
Click to collapse
I did. And I'll try what you said.
So yeah that didn't fix it. And just now it randomly rebooted itself.
everybody has had these issues and got passed them the fact you say you couldnt find it lets us know you didnt search to well
I've done what people have suggested and had no results. I have searched for a good half hour, using the search feature. Perhaps you could link me to a resolved thread someone posted with the same problem? That'd be helpful. I'm not trying to aggregate anything here, I just want to be able to use this.
You don't disable the g sensor by disableing the auto rotate. Try using a kernal with the g sensor disabled. Its around here somewhere.
Sent from my HTC HD2 using XDA App
Don't I have to start from scratch if I do that?
Haven't been able to find decent solutions to this slow wake up problem. I disabled auto-rotate, and am running the latest shubcraft (1.5).
I would appreciate a helpful link too!
This isn't a slow wake up problem...
Take a look at the how to disable g sensor thread. I used the gscript route and I'm loving it. No screen freezes at all. There's no auto rotate either but with to clicks I can enable or disable it.
Sent from my HTC HD2 using XDA App
same problem
i got the same problem with my phone. after flashing two diff roms Kumar Premium and Miri's i still get SOD. what did you guys do to fix this?
I've disabled the G-Sensor using GScript but I'm still having lag before the screen wakes up (sometimes 10 seconds or more), too!
Any other fixes/patches?
Running Miri's ROM + FroyoStone v2 with Sense on a T-Mobile HD2.
ananthb said:
I've disabled the G-Sensor using GScript but I'm still having lag before the screen wakes up (sometimes 10 seconds or more), too!
Any other fixes/patches?
Running Miri's ROM + FroyoStone v2 with Sense on a T-Mobile HD2.
Click to expand...
Click to collapse
Don't derail my thread with another topic. Make a new thread.
ddgarcia05 said:
Take a look at the how to disable g sensor thread. I used the gscript route and I'm loving it. No screen freezes at all. There's no auto rotate either but with to clicks I can enable or disable it.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Link? Can't find it.
Disabling the g-sensor does not fix the problem. I used the gsript "trick" with renaming the folder and killing a process. Didn't help.
Help me with this, somebody!
Bump......
When you first start up Android it needs some time to initialise. My experience is that when you wait like 5 minutes after Android has booted the SOD's hardly occur and if occur it will wake up after you'll try a few times.
So... Let it boot and leave it alone for five minutes or so?
Again, I disabled the gsensor with Gscript lite.
That's what works for me. I'm using andriod for Desire HD and I'm using it daily.
hey guys.. I found a true SOD/CHARGING FREEZE SOLUTION!!
before, I'll explain this thing :
willy and some other friends said that reflashing stock ROM before flashing a custom ROM, and then never do task29, is also true to avoid SOD.
but, I always do task29, and my ROM never SOD/charge freeze for more than two weeks..
here it is :
- use S2U2, then set to lock the device when Backlight turns off (s2u2 settings-> power)
- NEVER use the power button to sleep device. Instead, You can assign left or right softkey, or the X-panel button to execute s2u2, if you want to lock the device before keeping it in pocket.
- you can set the S2U2 to power off the device after 5 seconds (s2u2 settings-> power), so after executing s2u2, the device will be powered off after 5 seconds
how can S2U2 prevent SOD/charge freeze?
- the main idea to prevent Sense SOD/charging freeze is to change to another screen before sleeping the device. So, Sense services will not run (because it is in the background), even when waking the device, because S2U2 is now the foreground. SOD/charging freeze occured by Sense services.
- in another post, Willy said that using the original autolock (on power button) can prevent SOD, but I think that's not true.. because the lock screen comes AFTER the device WAKES, NOT BEFORE the device SLEEP
try it guys.. but I NEVER face the SOD/charge freeze for 2 WEEKS, even when charging the device overnight
(Screen freezing or phone hang still also a problem, but they are seldomly happened.. yes, because Sense is rather heavy for X1 CPU)
Please correct me, Master Willy or friends, if I'm wrong.. I'm using Willy's latest ROM for now.. (see 826x.blogspot.com)
Pretty old solution. I've been using lock screen to prevent freezes on bad hardware revisions-phones for almost year now. I've told willyung to use such thing a long ago but as I remember he uses another service/app to open lock screen. May be that's the reason why it freezes...
Btw, better to say "workaround" than "solution". IMHO.
nice try.
but i wonder if the myths about SoD will ever stop to prosper...
you see, this is not true:
duke_dreadmoore said:
SOD/charging freeze occured by Sense services.
Click to expand...
Click to collapse
you can get SoD in a rom without sense as well. thus the whole "theory" about S2U2 fails. and you can get SoD with sense 2.1, with winmo 6.1 (very rare, but possible), with sense 1922, with sense 2021, etc etc etc.
SoD is caused by power management. and how to fix it - search. there's already a thread about it.
caliban2 said:
nice try.
but i wonder if the myths about SoD will ever stop to prosper...
you see, this is not true:
you can get SoD in a rom without sense as well. thus the whole "theory" about S2U2 fails. and you can get SoD with sense 2.1, with winmo 6.1 (very rare, but possible), with sense 1922, with sense 2021, etc etc etc.
SoD is caused by power management. and how to fix it - search. there's already a thread about it.
Click to expand...
Click to collapse
Well, that's hardware-related in some way. I am using sense 2.5-roms for almost a year now and I haven't ever encountered freezes at all. Some of my friends do. I have a pretty early retail phone.
interesting...
thanks for solution. but I never had charging freeze with my device.
i'm always using Spoon Charge app when charging. it gives me all the battery and charging infos...
ultrashot said:
Pretty old solution. I've been using lock screen to prevent freezes on bad hardware revisions-phones for almost year now. I've told willyung to use such thing a long ago but as I remember he uses another service/app to open lock screen. May be that's the reason why it freezes...
Btw, better to say "workaround" than "solution". IMHO.
Click to expand...
Click to collapse
you mean the original lockscreen? I always encounter SOD/charge freeze using that.. because I think the auto-lockscreen comes after the device wakes.. so Sense is still on foreground when device sleep
caliban2 said:
nice try.
but i wonder if the myths about SoD will ever stop to prosper...
you see, this is not true:
you can get SoD in a rom without sense as well. thus the whole "theory" about S2U2 fails. and you can get SoD with sense 2.1, with winmo 6.1 (very rare, but possible), with sense 1922, with sense 2021, etc etc etc.
SoD is caused by power management. and how to fix it - search. there's already a thread about it.
Click to expand...
Click to collapse
I've been using a non-Sense ROM (xperia unoff, willyung with sense disabled, twinge rom) for about 6-9 months.. never encounter any sod/charge freeze.. only hangs sometime, that's normal for WM..
orkhanahmadov said:
interesting...
thanks for solution. but I never had charging freeze with my device.
i'm always using Spoon Charge app when charging. it gives me all the battery and charging infos...
Click to expand...
Click to collapse
I found that the application is buggy.. s2u2 also give u battery info when charging..
duke_dreadmoore said:
I've been using a non-Sense ROM (xperia unoff, willyung with sense disabled, twinge rom) for about 6-9 months.. never encounter any sod/charge freeze.. only hangs sometime, that's normal for WM..
Click to expand...
Click to collapse
well, and others encountered them the first night when charging with sense disabled or a non-sense rom right away. what does that tell you?
i garantee you: sooner or later someone will try your "solution" and report back with SoD. you have no idea how frustrating the period from sept 09 to april 2010 has been - it was the "height" of SoD. testing, trying, getting frustrated, oversleeping because the phone was dead in the morning...
"using roms 6-9" months - i'm longer SoD-free than you are a member on this board... and so are others - if they're still using the x1 that is, looks like knowhow gets lost. ^^
"wm hanging is normal": yes - and no. it depends heavily on the rom you're using. longest streak without restart i had were 3 weeks - and i only had to break that because i installed ultrashot's volume-control.)
maybe this can shed some light on it:
http://forum.xda-developers.com/showthread.php?p=7459349#post7459349
this is the way that got everyone SoD-free sooner or later. problem is: you may have to find your perfect settings first. (settings around 40 secs seem to do it for the majority.)
duke_dreadmoore said:
you mean the original lockscreen? I always encounter SOD/charge freeze using that.. because I think the auto-lockscreen comes after the device wakes.. so Sense is still on foreground when device sleep
Click to expand...
Click to collapse
I use my own service to lock device during charging. Actually, it locks before going to suspend
caliban2 said:
well, and others encountered them the first night when charging with sense disabled or a non-sense rom right away. what does that tell you?
i garantee you: sooner or later someone will try your "solution" and report back with SoD. you have no idea how frustrating the period from sept 09 to april 2010 has been - it was the "height" of SoD. testing, trying, getting frustrated, oversleeping because the phone was dead in the morning...
"using roms 6-9" months - i'm longer SoD-free than you are a member on this board... and so are others - if they're still using the x1 that is, looks like knowhow gets lost. ^^
"wm hanging is normal": yes - and no. it depends heavily on the rom you're using. longest streak without restart i had were 3 weeks - and i only had to break that because i installed ultrashot's volume-control.)
maybe this can shed some light on it:
http://forum.xda-developers.com/showthread.php?p=7459349#post7459349
this is the way that got everyone SoD-free sooner or later. problem is: you may have to find your perfect settings first. (settings around 40 secs seem to do it for the majority.)
Click to expand...
Click to collapse
I don't know brother, maybe SoD is more complicated than I think
previously, I stay using xperiaUnoff ROM for 5 months.. never sod, hang, freeze..
after that, using Willy's ROM, encounter SoD every 2 days..
then I try s2u2 with that settings, never Sod.. I can believe my phone again
ultrashot said:
I use my own service to lock device during charging. Actually, it locks before going to suspend
Click to expand...
Click to collapse
do you have forum link for that service? will be nice to try thx..
Till now I only had SoDs when using a ROM with native 6.5 kernal. Has anyone a SoD problem using a ROM with a 6.1 kernal? Maybe this is the solution?
I would agree with ultrashot that sods and charging freezes could be hardware related.
I always got sods and charging freezes with my lost phone, however autolock prevent the charging freeze. With my current phone, I never had any single sod, charging freezes and any other freezes. One thing can be noted, I never task29 and flashed radios with this phone.
maybe. but there has to be a sw-/driver-component as well.
i always got SoD with this phone since 6.5 came on (summer 2009; preventable with resumingsuspend-keys) with roms from different cooks (including yours ). but since i made my own rom based on ultrashot's kitchen not one SoD occured. sure, over the weeks i changed more and more stuff in sys and oem, but SoD was gone from the beginning when i was just playing with ext-folder. same hardware all the time.
Been using my own 6.5 rom with sense for more than a year (nothing new to WM that interest me to update it anyway) without SOD. Never task29 and I don't believe SOD related to Sense (maybe some bad implementation would).
I think find the solution & what program causes it
the cookie home tab program cause to SoD
u can test manila without this program & u will see no SoD
i'm happily using cht and experience no SoD's at all...
really!!!
whats ur ROM ???
my own (look at my sig...)
but using ultrashot's kitchen as a base. his roms are sod-free too, i think.
j j said:
I think find the solution & what program causes it
the cookie home tab program cause to SoD
u can test manila without this program & u will see no SoD
Click to expand...
Click to collapse
I don't use CHT and get SODs
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.
I have a problem with Sleep of Death in WinMo. When i put my Mini in sleep mode and I'm trying to wake it up - nothing happens. Does anyone know how to resolve this problem?
Hello, did you manage to resolve your problem? I just started having the same problem. Hard reset did not help. I am going to reload latest official ROM.
I wait for your expressions after reloading ROM. I've hard reseted WinMo and even in Android - nothing happens. I'll reflash ROM after work.
I reaolved the problem on my mini by disabling htc lockscreen.
if u search how to disable it u will find it
PeGie: I re-loaded the latest shipped ROM (1.36). It works (so far). I'll add additional software one by one to see if there is some relation.
bruce2728: Thank you for the tip. However, I cannot disable it. I am using the device also for company e-mail synchronizing by using ActiveSync. The company policies force to use the screen lock and I am not able to change it.
ace960 said:
PeGie: I re-loaded the latest shipped ROM (1.36). It works (so far). I'll add additional software one by one to see if there is some relation.
bruce2728: Thank you for the tip. However, I cannot disable it. I am using the device also for company e-mail synchronizing by using ActiveSync. The company policies force to use the screen lock and I am not able to change it.
Click to expand...
Click to collapse
if you disable htc lockscreen in the registry it defaults to the windows 6.5 one, so you will still have a screen lock
edit: forget lockscreen it happened again after a few hours
Shake'n'Wake
Have you try the Shake'n'Wake application?
13alexandro13 said:
Have you try the Shake'n'Wake application?
Click to expand...
Click to collapse
Seems to work but only a temporary solution.
I think the driver that controls the power button goes to sleep when phone in standby
I'll investigate tonight and report back if I have any succes
Guys, thanks for help. I tried today to turn off lockscreen, but it doesen't worked. I'll try to figure it out tommorow. I'm waiting for results of investigation of Sleep of death.
I uninstalled CleanRAM first and hard reset and I have no more problem SOD
(last 10 hours is normal) I do not know if I will again have the same problem, now works ok
HTC HD mini German ROM: 1.41.166.1
I mentioned that hard reset did not help. That may not actually be true. When I did hard reset then I immediatelly installed all my applicatiosn and changed all the settings I used to change. Some of the software or config change may cause the problem. However, it is strange that it began just few days ago. I was using the device almost 1 year without this problem.
Anyway, as I mentioned before, I re-loaded the 1.36 ROM today. Then I left all settings at defaults. I did not install any application. It is working correctly so far. I'll add app/config change one by one to track the root cause. It will take some time of monitoring but I need to identify the cause. My suspect #1 is my company security policy. That would explain the problem appearance beginning.
I already had some problem caused probably by my company security settings.
ace960 said:
However, it is strange that it began just few days ago.
Click to expand...
Click to collapse
and to me it's strange because the last few days, so to say I did not use mobile phones, nothing new installed or changed settings.
I have this problem too. Since yesterday - started from failing to wake me in the morning. It's kind of weird, all of the sudden phone stopped to work correctly.
At last (judging by more people having problem as well) is not the hardware problem.
Anyone has any idea: this problem was known before, or it started in last few days?
I'm also having this problem. I've changed nothing on my phone since months and since yesterday it has this problem. I'm thinking of sending it for repair and wait what they will say about it.
I was using my HD mini for 10 months without problems. But today I was faced the same problem as you mentioned. I removed my battery and left my HD mini without battery for ~30 minutes. Then I put battery back and turn on the phone and everything works now ...
It sound really weird that this problem is popping out suddenly to a number of users, while before there was no symptom.. it would seem as crazy as a time-driven issue or something..
Before reading here, my 1st step would have been removal of lockscreen, then 2nd one going back to clean original installation, but looks like those moves are not of help..
Fact is that the only new software i installed is bsb tweaks whose changes may affect registry and corrupt system configurations.. do you all guys have bsb installed?
Let's try to figure this out together, missed wakeup and calls are really annoying, as well as removing the battery to make a phone call...
No, I don't have bsb.
And people are using bsb without much problem for the last year.
Some kind of millennium bug? Someone programmed end of the world in our phones?
Brighty1982 said:
No, I don't have bsb.
And people are using bsb without much problem for the last year.
Some kind of millennium bug? Someone programmed end of the world in our phones?
Click to expand...
Click to collapse
Next frontier of marketing development, a built-in countdown ticking for a faster & continuous phone replacement...
i don't have bsb on my mini
I do not have BSB installed (actually, I have idea what it is). My Mini is stable 16 hours after ROM reload. It survived the night! I believe hard-reset would help too. I'll re-test hard-reset if I see the problem again after some app/cfg install/change.
My next step is to install HTC updates:
PHO03869.exe
PHO03880.exe
_HTC HD Mini_PHO03611.exe
Then I will install/configure (not ordered):
home WiFi - hidden SSID, WPA-PSK, AES, ASCII key
CorePlayer v1.3.6 Build 7427 - directdraw output
TomTom 7.916.9192 QVGA with one map
ActiveSync - for company e-mail
IMAP e-mail - for Gmail account
turned off HTC Sense
turnd off weather (Application Data\HTC\databases -> deleted the file forecast_cache.db, restarted Sense (uncheck/check in today settings)) - this is sometimes required to stop the weather to be updated from web
system settings change - bluetooth, regional settings, etc.