It started going back to 15 seconds again. I have now done a hard reset and carefully loaded back only the programs that I really use. So far it is working perfectly. I will slowly load everything else back over the next few days and see if i can isolate what is causing this.
I found my LockLevel value at 48! I have to change it again every time after a soft reset - it always goes back to 1. Thanks for the info on Mortscript - will try.
I knew my backlight problem was due to backup/restore, but I didn't know other people were having the same problem. Interestingly, in my attempts to try to fix the problem without having to hard reset and manually reload everything, I even tried making a backup and restoring with the built-in Data Backup, and the exact same problem happened. The backlight dim setting stayed at 30 sec for a few hours at most before reverting to 15 sec no matter what I did.
I found my LockLevel value at 48! I have to change it again every time after a soft reset - it always goes back to 1. Thanks for the info on Mortscript - will try.
I knew my backlight problem was due to backup/restore, but I didn't know other people were having the same problem. Interestingly, in my attempts to try to fix the problem without having to hard reset and manually reload everything, I even tried making a backup and restoring with the built-in Data Backup, and the exact same problem happened. The backlight dim setting stayed at 30 sec for a few hours at most before reverting to 15 sec no matter what I did.
I am still discussing this with spb backup team on this. The progress is rather slow as they could not reproduce the problem on their own and need me to upload my backup for their testing. Would report if a fix was found. BTW, you have problem after soft reset, do you have the same problem after suspend?
New workaround suggested by spb backup team. It works but I don't think it is better than the mortscript fix anyway.
The fix is very simple, just disable the password lock and ownership info screen at startup. You may consider completely disabling dimming and soft reset on the same go and set the dimming setting after the soft reset.
Personally, I don't recommend this fix unless you are very sure that your axim won't ever get stolen. :)
New workaround suggested by spb backup team. It works but I don't think it is better than the mortscript fix anyway.
The fix is very simple, just disable the password lock and ownership info screen at startup. You may consider completely disabling dimming and soft reset on the same go and set the dimming setting after the soft reset.
Personally, I don't recommend this fix unless you are very sure that your axim won't ever get stolen. :)
thanks for the "recommendation"....only one small problem....
Had the same problem after restoring with Sunnysoft Backup Manager. Thanks to you, guys, managed to solve it.
For those, who still have the problem, here is the text for MortScript, just copy to Notepad or something and save as LCD_dim.mscr (only extension matters). Or download the file below and rename it to LCD_dim.mscr.
Than place it to Windows/Startup directory. You should have MortScript for this, of course. You can find the latest version here: http://www.sto-helit.de/forum/viewto...1080&start=100 It is freeware.
The first line,
, sets LockLevel to "0" after soft-reset. After setting it to "0" manually, dim-setting does not resets after each power-off. But LockLevel resets to 1 after each soft-reset, and than the problem with dim-setting occurs again. The script fixes this. Than, the second line sets BatteryTimeout to 30 seconds. You can change it to 60 or more.
Had the same problem after restoring with Sunnysoft Backup Manager. Thanks to you, guys, managed to solve it.
For those, who still have the problem, here is the text for MortScript, just copy to Notepad or something and save as LCD_dim.mscr (only extension matters). Or download the file below and rename it to LCD_dim.mscr.
Than place it to Windows/Startup directory. You should have MortScript for this, of course. You can find the latest version here: http://www.sto-helit.de/forum/viewto...1080&start=100 It is freeware.
The first line, , sets LockLevel to "0" after soft-reset. After setting is to "0" manually, dim-setting does not resets after each power-off. But LockLevel resets to 1 after each soft-reset, and than the problem with dim-setting occurs again. The script fixes this. Than, the second line sets BatteryTimeout to 30 seconds. You can change it to 60 or more.
Please note that this apply to cases that only involves full power off or soft resets. There are cases that involves suspend mode too. In that case I use an infinite loop in mortscript to check the registry every 15 seconds and rewrite the registry if required.
Please note that this apply to cases that only involves full power off or soft resets. There are cases that involves suspend mode too. In that case I use an infinite loop in mortscript to check the registry every 15 seconds and rewrite the registry if required.
I had the problem each time I used suspend mode or soft reset. I do not use full power off at all. After changing manually "LockLevel" to "0" (I had "16" or so before), problem has gone, but only until next soft reset. So, the script above fixes this. It works fine for me.
I think that infinite loop in mortscript, especially every 15 seconds, loads processor and drains battery a bit, so this is not the best variant to solve the problem.
I had the problem each time I used suspend mode or soft reset. I do not use full power off at all. After changing manually "LockLevel" to "0" (I had "16" or so before), problem has gone, but only until next soft reset. So, the script above fixes this. It works fine for me.
I think that infinite loop in mortscript, especially every 15 seconds, loads processor and drains battery a bit, so this is not the best variant to solve the problem.
You are luckier than me. In your case the problem won't happen on suspend mode. For my case, the dimming settings got reset every time I resume it after suspend, so the infinite loop method is the last resort, unless there is a way to tell mortscript the device is awaken from suspend.
I know that is not good to the power consumption and overall performance, but there is no better alternative yet.
For my case, the dimming settings got reset every time I resume it after suspend
May be I writing a bit unintelligible, so you misunderstood me. I had absolutely the same problem. Every time I resumed my Axim from suspend mode I got 15 sec. in "Dim if device is idle for more than" line ("Battery power" page of "Brightness" settings).
As recommended above, I tried to set "LockLevel" to "0" using registry editor. After doing this, "Dim if device is idle for more than" setting stopped resetting after each resume from suspend mode. But after each soft reset "LockLevel" goes from "0" to "1". And problem with resetting of "Dim" setting to 15 sec. returns. That is the problem I had. So I just made the script to set "LockLevel" back from "1" to "0" after each soft reset and to set "Dim if device is idle for more than" setting to 30 sec. automatically. And it works. Now I can say that the problem do not disturb me anymore.
Have you tried the script? May be it can help you too?
May be I writing a bit unintelligible, so you misunderstood me. I had absolutely the same problem. Every time I resumed my Axim from suspend mode I got 15 sec. in "Dim if device is idle for more than" line ("Battery power" page of "Brightness" settings).
As recommended above, I tried to set "LockLevel" to "0" using registry editor. After doing this, "Dim if device is idle for more than" setting stopped resetting after each resume from suspend mode. But after each soft reset "LockLevel" goes from "0" to "1". And problem with resetting of "Dim" setting to 15 sec. returns. That is the problem I had. So I just made the script to set "LockLevel" back from "1" to "0" after each soft reset and to set "Dim if device is idle for more than" setting to 30 sec. automatically. And it works. Now I can say that the problem do not disturb me anymore.
Have you tried the script? May be it can help you too?
Well, I guess I haven't misunderstood your case. My case is, the Locklevel resets to non-zero after each suspend while yours doesn't, so I need to constantly check the registry and set it back to zero rather than doing this one-off during startup. That's why I wrote the infinite loop mortscript.
That is a really difficult case.
One more idea. May be you have tried it already. As far as we can see, backup programs cause this bug to happen. May be you should check your startup folder and try to move resident module of backup program somewhere, make soft reset and see what happen then. It is possible, that it some how connected to Locklevel change. When you need to make backup, you can always move it back manually.
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
