[Q] Display initialization: 'white' at startup, normalized after initialization - ONE Q&A, Help & Troubleshooting

Strange behavior with my opo in 11.0-XNPH44S, build KTU84Q:
Phone starts up with nearly white display and switches back to normal backlight after some seconds.
On reboot it will talke app. 1 second. On initialised android running it takes up to 6 seconds until display is initialised correctly.
Any idea? Might this be a wrong backlight default setting, missing initial output port initialization or will it be a damaged hardware (defect capacitor or something like this)?

Related

WM6 screen goes off after 5 Sec

hi got Tornado imate sp5m i ve flashed the rom with WM6 Perfect English after flashing i seems corrupted it gets freeze if i dont use it for several hours and when use it the screen goes off every 5 seconds with an annoying chime and tried Vanila aswel but getting the same problem.
Note: After Clear Storage it works fine again for sometime. i have T9English and Sp5m Buttons Installed nothing else
Any Solution
i ve format my phone installed GSM update and then WM6 and followed step by step.
Same problem here with Vanilla Edition.
Screen goes off after 7secs no matter what time-outs are set under power management. If I cange values in power management, it works fine again, but after some time it starts cutting off screen after 7secs, that is very annoying.
yes it doesnt care about time management it got its own time well much annoying thing is it hangs sometimes and i found no call is recieved when it seems hang
did u Clear the storage ? the problem seems solve but for a while
Set these registry settings and you'll be fine:
Code:
[HKEY_CURRENT_USER\ControlPanel\Power]
"Display"=dword:0000003C
[HKEY_CURRENT_USER\ControlPanel\Power\LockLevel]
"LockLevel"=dword:00000000
The display will go off after 60".
pauliusba said:
Same problem here with Vanilla Edition.
Screen goes off after 7secs no matter what time-outs are set under power management. If I cange values in power management, it works fine again, but after some time it starts cutting off screen after 7secs, that is very annoying.
Click to expand...
Click to collapse
screen goes off after 7 seconds only after the keypad is locked (that's the best i can do to prevent screen from lighting when the joystick is accidentally toggled inside your pocket for example). but if it is not locked, (in my experience) it corresponds to the timeout set under power management. but still i will check on that.
This display timeout behavior is normal for WM5/6.
In [HKEY_CURRENT_USER\ControlPanel\Power] there is usually only one key when the keypad is unlocked. The "Display" key stores your normal timeout setting in seconds. When you lock the keypad, the "Display" key is set to 7 seconds and your normal timeout setting is set to a new key called "TimeoutSaved". When you unlock the keypad, the "TimeoutSaved" is deleted and the "Display" key is set to your normal timeout setting. So far so good...
But, there's also another key in [HKEY_CURRENT_USER\ControlPanel\Power\LockLevel] called "LockLevel". It seems that it controls the normal Display/TimeoutSaved behavior. It's normal value is "0". But some times it is changed (I think AutoKeyLock and LowLevel have something to do with it) and set to "3" or "4". All you need is reset it to "0".
That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...
Just to point out, Nitro's registry settings appear to be in hex, whereas most ROMs I've used show it to me in normal numbers (is that binary? because I thought binary was only 0 or 1).
Either way, 0 is 0. I wonder if it's possible that this key should be in hex and the keylock programmer used the wrong way to enter info, or maybe vice versa but still wrong data?
pauliusba said:
That value keeps restoring back and 5-sec time-out problem remains. There is no workaround here...
Click to expand...
Click to collapse
It's actually 7 seconds and you have to power off your phone, wait a minute (or two) and start it up again.
This is a really common problem/question. If you had used the search you wouldn't have had to post and wait.
Look at this. This is solution for your problem
Possible cause
I think I may have found what is causing this issue. I noticed that if I let the keylock program run, it changes the backlight, etc to timeout and go black in about 5 seconds. I have to go into config and change it to a higher number, then back down to what I want it to be.
It got to the point that just had to disable that keylock program, otherwise, I have to constantly reset the power management settings.
When I don't have the keylock program running, the timeouts all work as advertised. Strange, eh?
Quakie
I had this, I found a solution, delete the LockLevel key with a registry editor, reboot and the problem has never occurred again

How to turn off screen dim after 5 secs

Apologies if this has been answered before, I've done plenty of searches, and can't find out how to do it.
On my stock HTC Touch Pro, if I don't touch the screen or keyboard for about 5 seconds, then the screen goes to a dimmed state. Is there a way to turn this behaviour off?
Cheers,
Steve.
Settings - System - Power - Advanced tab. All of the options are there...
There are no relevant settings there. There's only the "Turn off backlight if device is not used for x min" and "Turn off device if not used for x min" for both battery power, and external power.
I'm not talking about the screen going off all together, I'm just talking about it dropping to minimum brightness after a few seconds of inactivity. I've tried the "Auto adjust backlight" and "Dim the backlight if the device is locked" settings, and they make no difference.
Cheers,
Steve.
Settings>Power>Advanced>Walla
StevePritchard said:
There are no relevant settings there. There's only the "Turn off backlight if device is not used for x min" and "Turn off device if not used for x min" for both battery power, and external power.
I'm not talking about the screen going off all together, I'm just talking about it dropping to minimum brightness after a few seconds of inactivity...
Click to expand...
Click to collapse
Steve,
You should be adjusting the "Turn off backlight if device is not used for..." setting under 'on battery power'. This setting relates to the dimming of the screen (backlight). It's most likely that this is set to 10 seconds or something short on your device. Increase this to the longer duration that you would like.
FYI, the "Turn off device..." setting relates to turning off the screen completely.
Hope that solves your problem.
xzibitB
Thanks for the responses. I was being a little confused by the fact that a) it's not turning off the backlight, it's just dimming it, b) it was doing it while sat in its cradle, and those settings were unchecked, and c) it was doing it after 5 seconds, and not the 1 minute it was set to.
Fiddling with those settings seems to have resulted in the behaviour I'm after.
Thanks again.
Cheers,
Steve.
I have exactly the same issue, as does my g/f's Diamond. The screen dims after 7 seconds of inactivity. I know this because I've timed it. I have all of the advanced settings turned off so the device should not ever turn off the backlight or power off. I'd really like to be able to stop this as it makes reading or watching video on the device extremely annoying.
Steve, what settings did you change?
Thanks.
I *think* what sorted it out was changing the settings to new values, then selecting [OK], and then going back into the Advanced tab, and setting them to what I wanted in the first place - it was almost as if the changing the settings didn't stick until I had changed them to something else, and gone out of the page.
I hope this helps.
Cheers,
Steve.
Having the settings not "stick" is a problem I had with my Apache/XV6700 under WM5. There was a fix out there for this problem that I could never get to work, either. It finally got fixed with a custom ROM and stayed fixed under a WM6 custom ROM.
But now I'm pretty dismayed to see the problem back with the stock Fuze ROM and a slew of tweaks/installs -- just when I got the phone how I wanted it. Anybody have any new ideas on getting the change to stick? A registry edit or something?
i am having the sameissue as leeJS, i had none of the boxes set to dim or turn off, it would dim after 7 seconds. i tried multiple settings even checking all the boxes with over 2 minutes, the screen will still dim. any solutions?
On another fourm I came across a fix that works for me - I had similar frustrating problems
In HKCU\Control Panel\Backlight rename the folder Locklevel to Locklevelx (or something).
System recreates the locklevel folder with the correct locklevel key inside it (and doesn't keep changing it back)
S2U2 has a setting that dims the screen after 7 seconds... Do you have that loaded as well? If so, check you s2u2 settings...

[Q] Touch HD Display corrupt

New WM 6.5 ROM on starting uses only blue and yellow in v low resolution.
Display technically OK - shows 3 colours on bootloader, and on Hardware Info it says 64k colours - just legible in its 2 lo-res colours.
After some duration 5-15min, using screen off/on h/w button, display suddenly clears to full colour and display resolution.
Free storage 169.15MB, free program 67.12MB, no change with cleanRAM.
Goldlocke's v1.2 WWE: OS 5.2.21913 Manila 2.6.20183025.0
Ideas? -and thanks in advance
This is most probably faulty lcd screen, so you might have to replace it with a new one.
Thank you, yes, tho it's odd that this onset only after flashing (and there was no mechanical damage).
Have clarified that switching screen off at any stage in the start-up will resolve it (gives normal screen) so I'll not try buying a new screen just yet.
May it be relevant that the first flash was interrupted by my PC's BSOD (first in months!); perhaps a voltage spike damaging a memory address?
Have you tried flashing it with the same rom, or the origional, to check if it is a faulty system file?
No, I'm nervous about flashing it again in case there was some hardware damage to video locations of memory during the BSOD - is that possible?
Have more detail on the fault sequence after soft-reset:
1. "smart mobility" logo displays normally (white text , black background) for 3s
2. red pixels disappear from this logo when Device ID data displays in red at lower R corner.
3. HTC splash screen displays in v low res in blue & yellow without red
4. start-up proceeds to desktop, display no change - unless
5. power off-on anytime after splash screen seems to re-start the display in full res and normal colours.
Sorry for delayed reply due to holiday....
fixed
fixed by flashing an early HTC ROM
perhaps others can understand why?

[Q] Touchscreen registers random Y axis starting position every time LCD awakened

I replaced the cracked LCD. Every time time the screen is awakened the touchscreen seems to randomly choose a different Y-axis starting position. Sometimes it is correct sometimes it is a little off and sometimes way off. Is this a defective replacement or is it an android issue.
Thanks
Same issue...
I am having the exact same issue. I replaced the screen and now the y-axis is off. Every time I shut off the screen and turn it back on, it is in a different position. One thing I have noticed is there is a little blip when I turn on the screen, like a horizontal line that briefly appears, like the screen is re-initializing or something. When this happens, the y-axis is correct.
Anyway, has there been any progress on a resolution?

Touchscreen consistently (and completely) unresponsive on wake up

Hi guys,
This problem has me stumped, so I figured I'd consult the hive mind.
The touchscreen works fine after the phone is turned on - be that for a continuous period of 30 seconds or 30 minutes. However, if/when it goes to sleep, the touchscreen becomes completely unresponsive on wake up. The screen turns on, rotates, and the physical buttons work fine. I figure no touch input is acknowledged, because if I tap the screen after it dims nothing happens; but if I press a physical button, then full brightness is restored.
I have been looking around for a solution for some time, but none of the three I found appear to be working, ie:
- Ensuring the Wi-Fi's set to be permanently on (no change on any of the settings)
- Changing the ROM (problem appeared in stock ROM, it now sports LineageOS)
- Changing the digitizer (problem is the same on old or salvaged screen)
At this point, I am not sure what else I can try. Any ideas would be most welcome.
Maybe charger? Some cables/chargers make touch panel go crazy (it used to happen to me with bad chargers) so try to change charger and USB cable.

Categories

Resources