Backlight reverting to 10 seconds - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

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.

Related

WM6 goes to sleep and won't wake unless soft reset

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.

Backlight Goes Off in 10 Seconds Using Phone

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

Problems with S2U2 on Wizard

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

Which Regisrty Entry?

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.

[Q]Screen does not work unless I use auto-brightness

All of a sudden today, my screen turned off after like 4 seconds. I pressed power and it just flashed momentarily and turned off immediately. Every time I pressed power, it did the same thing.
I rebooted. The ASUS startup screen showed fine. Then as soon as it booted in, same thing.
I tried wiping all data, and then rebooted. Same problem.
Since it only does this when booted in, I'm thinking it's a software issue. But how the hell do I fix it if I can't get the screen to do anything more than flash on for less than 1 second?
When I'm plugged in, the screen works fine. I'm so confused...
UPDATE: For some reason, when I turn on automatic brightness, the problem goes away. But the second I turn off auto brightness, the screen immediately shuts off and the problem repeats. And auto brightness keeps the screen on a really low setting.
Urrghhh
Chief85 said:
All of a sudden today, my screen turned off after like 4 seconds. I pressed power and it just flashed momentarily and turned off immediately. Every time I pressed power, it did the same thing.
I rebooted. The ASUS startup screen showed fine. Then as soon as it booted in, same thing.
I tried wiping all data, and then rebooted. Same problem.
Since it only does this when booted in, I'm thinking it's a software issue. But how the hell do I fix it if I can't get the screen to do anything more than flash on for less than 1 second?
When I'm plugged in, the screen works fine. I'm so confused...
UPDATE: For some reason, when I turn on automatic brightness, the problem goes away. But the second I turn off auto brightness, the screen immediately shuts off and the problem repeats. And auto brightness keeps the screen on a really low setting.
Urrghhh
Click to expand...
Click to collapse
This is a well known and well documented issue that could have been easily found by searching. Your thread adds to the 3 or 4 that already exist regarding this issue.
Sent from my TF Decepticon
b1ackplague said:
This is a well known and well documented issue that could have been easily found by searching. Your thread adds to the 3 or 4 that already exist regarding this issue.
Sent from my TF Decepticon
Click to expand...
Click to collapse
I do recall reading similar reports earlier, but from my memory, there seemed to be some differences. If I'm wrong, I'm sorry for inconveniencing you for a whole 5 seconds
Side question: have you ever tried to get decent search results? It's extraordinarily difficult given that terms are used for multiple purposes, and not all the language is universal.
After going back, and reading a ton of threads through manual forum-browsing, it seems that I was correct about most other problems being distinction from this. Only really found one other mention of this (http://forum.xda-developers.com/showthread.php?t=1078331). So perhaps YOU should search before telling people they should search.
Anyone have thoughts?
Chief85 said:
After going back, and reading a ton of threads through manual forum-browsing, it seems that I was correct about most other problems being distinction from this. Only really found one other mention of this (http://forum.xda-developers.com/showthread.php?t=1078331). So perhaps YOU should search before telling people they should search.
Anyone have thoughts?
Click to expand...
Click to collapse
I do search and I am subscribed to other threads that I check daily regarding your same issue. Ill come back to this thread and post the links to those other forums so as to keep the TF general thread from being overpopulated. And even if your problem IS unique its still very closely related to others in the forum link you posted and would still be more appropriate to post there rather than creating another thread.
I have the same exact problem as you and I want it solved just as much as you but I would I also like the ability to easily navigate this forum and that's only possible by keeping related threads from happening.
Sent from my TF Decepticon
For now the only solution seems to be to keep hard resetting your device (hold power for 10+ seconds) several times and keeping a manual brightness. I had to hard reset my device 8 tines before the screwn would stay on. The reason that your backlight is shutting off when you turn AB off is because of where your manual brightness is set and chances are it's set too high which seems to be the common cause. Keep hard resetting your device until manual brightness is allowed then set MB to a lower level. This issue happens on AB as well when in a bright area and it sets the brightness to high on its own.
Sent from my TF Decepticon
I wonder if it can be fixed if you use the dock's brightness adjustment keys?
b1ackplague said:
I do search and I am subscribed to other threads that I check daily regarding your same issue. Ill come back to this thread and post the links to those other forums so as to keep the TF general thread from being overpopulated. And even if your problem IS unique its still very closely related to others in the forum link you posted and would still be more appropriate to post there rather than creating another thread.
I have the same exact problem as you and I want it solved just as much as you but I would I also like the ability to easily navigate this forum and that's only possible by keeping related threads from happening.
Sent from my TF Decepticon
Click to expand...
Click to collapse
Hate to jump in you but do you see the inherent contradiction in that statement? If the search tools are adequate then the number of similar threads should not matter as they can sorted by relevance. If they are not, as your desire for single threads suggest, then asking a new person to use them to find an answer is not appropriate as it isn't going to be successful. I've found that the bulk of the posts aren't technical so a search for the appropriate terms is pointless and a simple question is more likely to get results. For example, when calling on webcore, lcd brightness is being set to 0. This is in the logcat I took when testing and I get nothing when searching for it. If I search for 'black screen', I get something.
Let's remember we're here to help each other. Being inclusive and welcoming to newcomers is a much more positive way for us to find results.
Cheers,
Todd.
frosty5689 said:
I wonder if it can be fixed if you use the dock's brightness adjustment keys?
Click to expand...
Click to collapse
I have this problem and the dock is the only way I can get the screen back on. I have to press the auto brightness button then press the power button to get the screen on.
If I manually increase the brightness from 0 in steps I can get to half way but then the screen goes off. Similarly I can reproduce this by using the slider to increase the brightness. I am trying other ROMs to see if I can get rid of this issue but so far it happens on Stock & Paul O'Brian's with full resets on both. sigh.
After endless reviews of the logcat files, resets and roms, seems I can't find a solution. Going to rma it unfortunately!
Sent from my HTC Desire using XDA App
So RMA is the answer?
Yes I rmaed mine to Asus. Only took them a a few days to fix and ship it back to me.
Thanks. I better unroot mine and get it sent.
Having this problem.

Categories

Resources