Does anyone know of a resolution to the device going to sleep after a specified time and not re-waking? I tried the Backlight setting and Power setting, but the device seems to go to sleep and not wake up. I have to soft-reset it get it to respond and even phone calls go straight to voice mail.
any help is much appreciated
I had the same problem. It's so random that it's hard to find out a reason
feareddevil said:
Does anyone know of a resolution to the device going to sleep after a specified time and not re-waking? I tried the Backlight setting and Power setting, but the device seems to go to sleep and not wake up. I have to soft-reset it get it to respond and even phone calls go straight to voice mail.
Click to expand...
Click to collapse
What ROM are you running? What radio and ipl/spl do you have? I have to say I've never seen this on any of the WM6 roms I've been on (MBE, mUn, nottoosmart, faria, xplore). I wonder if its some 3rd party app thats misbehaving / conflicting with WM6? Are you running any Spb programs (a couple of those seem to have issues with WM6 in other ways).
Not sure how often it happens, but if possible you should go back to a clean flash of the rom and try using it just that way to see if the problem still happens.
3DES.2 ROM
SoftBank X01HT
Cingular Network
ROM: 3.23.0.2
Radio:1.38.30.10
OS:5.2.968 (B 17736.0.2.0)
Protocol:32.71.7020.12H
HERM200
I am concerned about reflashing, since I already bricked a device trying to roll back to an original rom (and I did read wiki) Any help is greatly appreciated. I boot fresh and do nothing but press the power button to turn off the screen and it happens everytime, the greenlight still blinks but nothing happens.
feareddevil said:
HERM200
Click to expand...
Click to collapse
Well, keep reading this forum and you will probably brick it again! You do realize you are reading the Wizard forum and not the Hermes forum???
If I set the minimum cpu speed to 130mhz or below I get the exact same problem, Are you using battery status or some other omap scalar program?
uugg-- sorry guys, I read the Hermes forum, but clicked the wrong link when I was mobile and posted the first message.
I am not sure if I am running a slower mhz. Is that default on 3DES.2? I will research how to change but if you can tell me quickluy - I will gladely take instructions to test.
The only way to change the speed is if you are running something like BatteryStatus or OMAPCLOCKplus or XCPUSCALER. Those will allow you to set a "min" on your phone and will drop your CPU down to the min when you aren't doing anything. So if the min is set to low, you phone can lock up similar to what you are describing.
You'll have to find out from other Hermes users what a good min is for your device. Personally on my Wizard I set the Min to 143 or 147Mhz. It can go lower, but I don't think it makes that much difference and don't care to find the bottom that works before I have problems. Just like I run a max of 260Mhz. I know I can run 273, but I don't see much difference, and really don't want to have issues by running faster when I can't see a performance gain (but thats just me).
Good luck!
Thank you everyone. I have narrowed it down to the powersave.dll. When I disable this - it no longer causes the lockup issues. I did not try adjusting the min value but it does appear to be the issue as I will assume - that powersave option does exactly as you outlined above.
regards and thanks again.
This is a common problem if you have installed a "Today" application on a storage card (the microSD card). If you did this, reinstall to the main memroy any Today application or any application that is in the "'windows\startup" folder.
Related
When I'm on a phone call, the screen backlight goes off after 10 seconds, even though I have Settings->System->Backlight->Battery set to 4 minutes. Even if I'm using another application while on a phone call, the backlight goes out after 10 sec. If I'm not on a phone call, then the backlight seems to obey the systems setting.
FWIW, this is a Touch Cruise, with the 1.25.405.1 WWE ROM, and WM6 18129.0.4.5.
there is nothing wrong with your phone thats normal. but the fix is a registry change. I can not remember what it is but I am sure the answer was in the the big fixes thread somewhere. I keep seeing it in there but keep forgeting to change mine. If I found it i will post it here.
Thanks. I did a search before posting, but didn't find anything.
Check out tweak #38 here:
http://forum.xda-developers.com/showthread.php?t=355277
This supposedly disables the screen turning off during a call, I haven't tried it myself.
i think it's not a problem at all for me
in fact, it prevents you to ends the call or launch a program if your cheek touch the screen
Yeah doesn't bother me either, it's expected behavior. But to each his own, some people want to turn off that feature.
Fine, it's a feature. How do I turn it off? Tweak #38 extends the time to ~30 seconds, but the display still goes off. That's a real killer if trying to navigate some company's phone menu, or trying to read a reference document while talking.
Well, in S2U2 there's in an option to choose, whether the phone should
turn the screen off during call or not. This option is available seperated
for Battery or Powered device while calling. Maybe this helps. Tested it
and works. Though I hate it, when the screen stays on during call, because
most time when I hang up I recognize, that I started tons of apps with
my fat face So I turned that option back to default for my case.
You may try yourself.
Olioaglio
Thanks. Unfortunately, S2U2 has a whole bunch of other features, which means a bunch of added overhead. It also needs a user manual to explain those features and options
So don't use what you don't need (or don't understand).
IMHO, it's worth it...
\HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
change "1" to "0"
I also found out this one:
Using Pocket Toolman2 (v.2.26.36), go to ''Tools''-->''OS Tweaks''
and there is an option to unchek the box ''Allow phone to go to sleep during calls''
cybernec said:
\HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
change "1" to "0"
Click to expand...
Click to collapse
THis is the better tweak and i have used it for a long time, simple
I am posting this because 1) I don't think this issue is specific to one cooked ROM, and 2) despite searching, I can't find a solution.
The issue is that with all of the ROMs I tried that are based on recent AT&T or HTC 6.1 ROMs, the backlight reverts back to 10 seconds. I can change it through Backlight settings to something else, and go back to the control panel a minute later and see it's back to 10 seconds. Very annoying.
I've seen this with a couple of L26 ROMs, the stock AT&T 6.1 ROM, and the HyperDragon III Pro ROM which I am currently using. I see this whether I have S2U2 or not (I am on 1.22b now). My current set-up: HardSPL 3.56, HyperDragon III Pro Sept-17, S2U2 1.22b... but like I said, I don't think it's ROM-specific.
Calling all experts: is there a fix for this? (If you are planning on posting something like "I don't have this problem" or "Change your backlight setting through the control panel", please don't clutter the thread with your post).
Thanks!
I spent a fair bit of time searching this and testing various suggestions that seemed to work for other people, however I was constantly getting the 10-second reversion, plus the even more annoying dimming backlight when locked.
Anyway I posted this:
http://forum.xda-developers.com/showthread.php?t=425361
And now after removing the registry 'BatteryTimeout' my backlight is working exactly as I want it - i.e. backlight dims afer 30-seconds regardless of whether it is locked or not, plus when locked the backlight comes on when the screen is tapped.
Now wait for the various replies saying 'use the search'.....
Andy
FWIW, I too had this annoying issue, but found that using ROMeOS roms (last version is 4.6) I don't get this issue. Not sure why or what the chef did to fix it.
The chef has now moved onto the Raphael...so he is not working on his Kaiser roms anymore
ADB100 said:
I spent a fair bit of time searching this and testing various suggestions that seemed to work for other people, however I was constantly getting the 10-second reversion, plus the even more annoying dimming backlight when locked.
Anyway I posted this:
http://forum.xda-developers.com/showthread.php?t=425361
And now after removing the registry 'BatteryTimeout' my backlight is working exactly as I want it - i.e. backlight dims afer 30-seconds regardless of whether it is locked or not, plus when locked the backlight comes on when the screen is tapped.
Now wait for the various replies saying 'use the search'.....
Andy
Click to expand...
Click to collapse
Thanks, let's see if it sticks. I've tried quite a few methods I found during my search and those didn't work....
It happened to me also with akadonny's 3.29.DK.10 / SPL 3.56.Hard
I changed SPL in the meantime for a different reason, and I had no backlight issues afterwards, but still I would not link that strictly to SPL cause I changed many other things.
Anyway, I found a power setup that works for me very well:
- for "on battery power" I only use turn off device (uncheck turn off backlight)
- for "on external power" I only use turn off backlight (uncheck turn off device)
P.S. This never happened to me with earlier builds, only with 20748.1.4.0.
Well, the first approach didn't work. I have a setup similar to the previous post, but that hasn't helped. I am on SPL 3.56 Hard. Which SPL did you go back to?
Second approach didn't work either. I see a lot of posts with people reporting the same problem... Has there been a definitive solution?
Im using HyperDragon_III_Omnia_20080818. With this ROM I dont have the issue of the 10 sec backlight. I use Hard SPL 3.29.
Chau Juan
I also have this problem and it is making me sick, at night while in bed I am trying to read an ebook but I have to tap on screen every 10 seconds!!
I am HyperDragon_III_Omnia ROM and I have tried many tweaks no luck.
Edit...
Ok I think the problem is now sorted.
Here's what I did... changed the following registry - HKCU\ControlPanel\BackLight\ACTimeout set the DWORD to 0 and reset the device.
So far it seems to be fine.
Invisible Sense said:
I also have this problem and it is making me sick, at night while in bed I am trying to read an ebook but I have to tap on screen every 10 seconds!!
I am HyperDragon_III_Omnia ROM and I have tried many tweaks no luck.
Edit...
Ok I think the problem is now sorted.
Here's what I did... changed the following registry - HKCU\ControlPanel\BackLight\ACTimeout set the DWORD to 0 and reset the device.
So far it seems to be fine.
Click to expand...
Click to collapse
Hmmm, I'll try this, thanks. This should be for backlight while connected... but worth a shot. I wonder if HardSPL version makes a difference... I'm on 3.56.
Hi All,
I have a wizrad (USA Tmo) with original rom. I have the current version of s2u2 installed on my device and have the following problems. I have searched the forum unsuccessfully. And have tried my best to resolve the issues. I am hoping that I am just missing something painfully obvious. Thanks for the help
1) I have it registered to lock on wake up. But it only works sporadically. I have no idea when it will lock. Most times it won't. I have checked the exemption list and don't have any offending programs registered.
2) I set the clock path in the registry. But every time I restart iLock it erases my set Value data. So I can never get the clock to appear.
Thanks again. Perhaps these are known issues that I have somehow over looked. My eyes have been pretty weary lately- working in front of computer a lot lately. So I apologize if i did miss something.
-P
cameraddict said:
Hi All,
I have a wizrad (USA Tmo) with original rom. I have the current version of s2u2 installed on my device and have the following problems. I have searched the forum unsuccessfully. And have tried my best to resolve the issues. I am hoping that I am just missing something painfully obvious. Thanks for the help
1) I have it registered to lock on wake up. But it only works sporadically. I have no idea when it will lock. Most times it won't. I have checked the exemption list and don't have any offending programs registered.
2) I set the clock path in the registry. But every time I restart iLock it erases my set Value data. So I can never get the clock to appear.
Thanks again. Perhaps these are known issues that I have somehow over looked. My eyes have been pretty weary lately- working in front of computer a lot lately. So I apologize if i did miss something.
-P
Click to expand...
Click to collapse
Ok, 1st this should probably be in the Wizard forum..............but, try setting it to lock when the backlight shuts off, this is how I had mine set up, and it worked fine.
As for the clock, if it is not showing up at all, make sure that you have it set to ClockA (I think) and see if that works.
idbl_fanatic said:
Ok, 1st this should probably be in the Wizard forum..............but, try setting it to lock when the backlight shuts off, this is how I had mine set up, and it worked fine.
As for the clock, if it is not showing up at all, make sure that you have it set to ClockA (I think) and see if that works.
Click to expand...
Click to collapse
i think this should be in the S2U2 forum, that way the creator can try and diagnose the issues.
http://forum.xda-developers.com/showthread.php?t=464695
Thank you both. I will make sure I repost in the correct forum.
Later
I am trying to prevent my TP2 from automatically going on standby mode after calls end. Anyone know which registry entry I need to edit?
Maybe you can have a look at this thread: http://forum.xda-developers.com/showthread.php?p=4430725
Hope that can help....any further helps are needed.
Thanks for the reply. That is to reassign the wake-up key. I do not want it to automatically go on standby after every call. I am severely physically disabled and cannot press the hardware keys.
might be a dumb question to ask, but since I don't know of any setting/software that would make you're phone go into standby immediately following a call, are you sure that...
1) it sleeps IMMEDIATELY after the call....and
2) Tah you're device isn't simply suspending according to you power/backlight options set in Settings / System / Power / Advanced "turn off backlight" & "turn off device" settings?
I know that the backlight will fast sleep DURING a call which can also be changed but it sounds like your issue is different than this.
Post further details for addional help.
mentalee said:
might be a dumb question to ask, but since I don't know of any setting/software that would make you're phone go into standby immediately following a call, are you sure that...
1) it sleeps IMMEDIATELY after the call....and
2) Tah you're device isn't simply suspending according to you power/backlight options set in Settings / System / Power / Advanced "turn off backlight" & "turn off device" settings?
I know that the backlight will fast sleep DURING a call which can also be changed but it sounds like your issue is different than this.
Post further details for addional help.
Click to expand...
Click to collapse
Do you have a TP2? I was told by HTC tech support that this "feature" is to save battery life and cannot be changed in the settings. I am positive it goes on standby immediately after every call. I have been through every setting on the phone and cannot find the cause. I am going to re-flash the stock ROM to see if there's a difference.
If you have a TP2...
1) What ROM are you running?
2) After a call, do not touch your phone. Do not even hit the End key. See if your phone goes on standby.
ok...yes I think the setting ur referring to is the FAST SLEEP on phone calls. Meaning the backlight goes off nearly immediately after RECEIVING a call but while ur still on the phone....right?
I am not sure the registry entry right now but there is a tweak app that should fix that for you. Not sure what that app is on a TP2 but on Kaiser/Tytan 2 it's a kaiser tweak and on my Fuze/Diamond it's the Diamond Tweak app. Maybe someone can comment as to whether the Diamond Tweak app is compatible with the TP2 or maybe google "kaiser tweak for touch pro 2". BTW it is a tweak/hack and not a system setting that you can disable that I know of. So flashing ROMs is pointless u'll still have to tweak unless it's already tweaked n the rom.
Give me a day/so I'll find that and post back
I'll look for the registry hack if someone doesnt beat me to the post.
Hope that helps......
hey try these registry hacks on ur phone to see if that prevents what ur trying to stop. To edit the registry u can install and use total commander
*** Prevent Fast Sleep During Phone Call ***
HKEY_Local_Machine\Drivers\BuiltIn\RIL\EnableFastD
ormantDisplayDuringCall to 0
HKCU\ControlPanel\Phone\Sleep switch value from 1 to 0
******
Hope that Helps!
My device does not go to sleep during calls. ONLY after calls end. I have tried 2 apps, and neither worked.
NoSleep
Power Tweaker 2
Thanks for the suggestions, let's keep trying! I'm sure we can figure this out!
mentalee said:
hey try these registry hacks on ur phone to see if that prevents what ur trying to stop. To edit the registry u can install and use total commander
*** Prevent Fast Sleep During Phone Call ***
HKEY_Local_Machine\Drivers\BuiltIn\RIL\EnableFastD
ormantDisplayDuringCall to 0
HKCU\ControlPanel\Phone\Sleep switch value from 1 to 0
******
Hope that Helps!
Click to expand...
Click to collapse
Just tried these. Still no luck. Any other suggestions?
Any current "device lock" or power related programs currently installed that might have a setting controlling the status/suspend of the phone after a call is hung up? I think Slide to Unlock used to have a setting that did this, so maybe it's another app that is unknowingly causing this behavior.
I will google a bit and see what else I might be able to come up with. Thanks for the clarification on whether it is during/after a call. Sleeping immediately AFTER a call is not a normal behavior with my phone or my previous winmo phone either... so it is a bit puzzling to me.
mentalee said:
Any current "device lock" or power related programs currently installed that might have a setting controlling the status/suspend of the phone after a call is hung up? I think Slide to Unlock used to have a setting that did this, so maybe it's another app that is unknowingly causing this behavior.
I will google a bit and see what else I might be able to come up with. Thanks for the clarification on whether it is during/after a call. Sleeping immediately AFTER a call is not a normal behavior with my phone or my previous winmo phone either... so it is a bit puzzling to me.
Click to expand...
Click to collapse
The only app I have installed currently is Touchtris. I am using EnergyROM StandardM2.5 from Sept 12.
Your continued help is greatly appreciated.
I have somewhat found out what was causing my issue. I was using EnergyROM StandardM2.5 build Sept 12. I re-flashed my TP2 to the stock ROM, and my issue is resolved.
So the problem is either in the EnergyROM or Windows Mobile 6.5. I am going to flash another WM 6.5 ROM to see if the issue returns.
HTC tech support claims that the auto standby is an intended power saving feature, but it is not happening on the shipped ROM.
Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.