Good info. I re-restored and it hasn't come back, but I'm still using SPB backup 1.5.
At least I know that it's not some bonehead thing I did with the registry editor(which was my #1 suspect) Interestingly enough I mentioned it in a support call to sprint and they suggested taking it in and getting a replacement.....hmmmm maybe a Mogul? I can only hope....

** after reading up that thread I confirmed that my registry that the lock code was set to 0, and backed it up. Thanks, DopeWeasel for the help.

Same problem, but I don't use SPBBackup... =( Any ideas?

badkarma, are you still using the kirvin kitchen? I noticed you posted in that thread and it was a known bug in that kitchen. If so give the standard 1.0.4 kitchen a shot and see how it works for you.

I'm using the recently deleted kirvin kitchen C&S+. Except for this one bug, it's working perfectly. I guess I'll have to move to a different kitchen :(

HKLM
 

You may need to change it at HKEY_LOCAL_MACHINE/ControlPanel/Backlight/ACTimeoutCheck too...

I'm pretty sure a search of the Forums will turn up the details as I've read and written about this at least a couple times before...

:?

Think I found the fix. I found it on pdaphonehome forums. Basically set to 30sec or whatever, then rename HKCU/ControlPanel/Backlight/LockLevel folder to LockLevelx or something else. Soft reset, and your backlight should stick!

Do your research peeps... this subject has been discussed to death. It is a very annoying problem which seems to have multiple solutions for some and no solution for others. locklevelx does not work (think about it... windows is just gonna recreate locklevel based on its own needs and locklevelx just looks like a completely different key). As well, the problem happens to people without spb backup although certain progs might contribute. Near as I can figure it does have something to do with locklevel and here is what I believe happens.... if u have the owners screen set to display, but you do not have the password screen pop up after clicking on the owners screen (no password set), then locklevel generates and somehow interferes with the backlight setting. This can be corrected by making sure you have your password set. Another possibility is that this could also be some other software that stops the bootup process (as the owner screen does) but there is no password set.

The next thing it may be is if the battery icon was taken out of the lower right hand corner by some program (try returning it). Lastly, one other possibility is installing cabs that existed prior to the new roms. You should not have installed any of them. That's what I narrowed it down to as I had the same problem when I picked up the 1.04 kitchen, but the problem went away after applying the aforementioned so I didn't keep on it, but my phone is flawless now and believe me I was ready to go back to aku 2.0 to get rid of this nuisance. Happy hunting and keep us posted on what worked for you.

I was skeptical about LockLevelx trick, but works for me. I have no idea why it recreates the LockLevel entries properly, but when I tried setting the key to 0, a soft reset would reset to 1. Renaming the LockLevel folder and resetting, the phone recreated the entries and it now sticks to 0.

Well I used spb backup and had the same problem before. But now i have spb backup without that problem. The way I solved it is by installing phonealarm and having it set the backlight to what you want. It overrides all other applications and the system settings to what you have configured. Plus it looks awesome!