screen goes dim after 5 sec. no matter what

pacijent · 03-15-07, 02:12 AM

every time I start my x51,check mark is automatically switched to 5 sec. dim option,so I have to change it.after that it works properly.soft reset doesn't help,if you restart it again it will dim after 5 sec.?????if you uncheck dimming same thing (this is brightness option in battery power menu).please help,I've got A12 rom version.

purcy · 03-15-07, 09:18 AM

Can you try a hard reset, which will probably show a default to the same settings, but then you can uncheck the dim option, and see if it sticks. I have mine set to dim the screen after 3 minutes on battery, but unchecked to dim on A/C power and it never reverts back to default. I have ROM A12 also.

03-15-07, 09:27 AM

This problem has happened to a lot of people. A hard reset seems to be the only way that it gets cleared up. It might be a program that is messing it up but I tried to figure it out and ended up doing a hard reset and then re-installed everything I had on it originally and it is still ok a couple of months later. It seems like the cause is related to doing a restore with eithe SPB backup or Sprite backup.

xless · 03-29-07, 02:56 PM

Argh - I was hoping to find a response to this which would help me out... but I'm glad (I think) to know that I'm not the only one this is happening to. When you adjust the brightness on the power control panel, does that write something to the registry? If so, is it that the reg value isn't being "saved", or that it's being overwritten by something at startup? Just thinking out loud.

zhaoyun · 03-29-07, 10:11 PM

Originally Posted by xless

Argh - I was hoping to find a response to this which would help me out... but I'm glad (I think) to know that I'm not the only one this is happening to. When you adjust the brightness on the power control panel, does that write something to the registry? If so, is it that the reg value isn't being "saved", or that it's being overwritten by something at startup? Just thinking out loud.

Yes indeed. But the reason and solution is still unknown. You could however search here and find more discussions here and some temporary workaround.