[Q] Screen not unblanking

Search This thread

fropmontois

New member
Jul 10, 2014
3
0
Hi,

I bought a ZR 6 weeks ago, updated to android 4.3 with official Sony releases. It did not fall nor jump to water.

Everything ran fine, but it happens more and more that the screen suddenly turns black.
At the beginning, switching the phone to sleep and waking it up used to reactivate the screen; it tends not to work any more.
Under a low light the display can be guessed, but the screen itself brings absolutely no light.

I managed to enable the debug link under a low light, and here is what logcat shows me:
I/PowerManagerService( 772): Waking up from sleep...
I/QCOM PowerHAL( 772): Perflock released.
D/SurfaceFlinger( 320): Screen acquired, type=0 flinger=0xb7475150
D/qdhwcomposer( 320): hwc_blank: Unblanking display: 0
D/lights-module( 320): led 'backlight' opened 34 times
E/lights-utils( 314): Unable to write '1': Invalid argument
D/qdhwcomposer( 320): hwc_blank: Done unblanking display: 0
W/qdhwcomposer( 320): Excessive delay reading vsync: took 11728 ms
D/SurfaceControl( 772): Excessive delay in unblankDisplay() while turning screen on: 169ms


I could find no information about this light-utils stuff.

What do I have to check or do?

Thanks a lot

--
Matthieu
 

fropmontois

New member
Jul 10, 2014
3
0
Hmm, looks like the light does not respond on i2c, here's what the boot sequence logs when the brand's logo isn't even displayed:

I/illumination-service( 320): Started
E/lights-core( 320): assign_theme: No led 'backlight' found
I/leds-dogo( 320): lights_init
E/lights-lm3533_als( 320): intf_open: unable to open '/sys/bus/i2c/devices/0-0036//als_result' (-2)
E/lights-lm3533_als( 320): add_lm3533_als: Device '/sys/bus/i2c/devices/0-0036/' not found.
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms': No such file or directory
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms' (-1)
E/lights-lm3533( 320): set_rates: write error (No such file or directory)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness' (-1)
E/lights-core( 320): LED 'backlight' is not of type 0
E/lights-core( 320): LED 'battery' is not of type 0
E/lights-core( 320): LED 'notifications' is not of type 0
E/lights-core( 320): LED 'button_rgb' is not of type 0
E/lights-core( 320): LED 'pattern_2' is not of type 0
E/lights-core( 320): LED 'pattern_3' is not of type 0
E/lights-core( 320): LED 'pattern_1' is not of type 0
E/lights-core( 320): LED 'attention' is not of type 0
E/lights-core( 320): LED 'button_2' is not of type 0


Any possibility to locate the hardware problem and fix it?

--
Matthieu
 

gurinderhans

Member
Jul 28, 2013
39
9
Surrey
Hmm, looks like the light does not respond on i2c, here's what the boot sequence logs when the brand's logo isn't even displayed:

I/illumination-service( 320): Started
E/lights-core( 320): assign_theme: No led 'backlight' found
I/leds-dogo( 320): lights_init
E/lights-lm3533_als( 320): intf_open: unable to open '/sys/bus/i2c/devices/0-0036//als_result' (-2)
E/lights-lm3533_als( 320): add_lm3533_als: Device '/sys/bus/i2c/devices/0-0036/' not found.
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms': No such file or directory
E/lights-utils( 320): Unable to open '/sys/bus/i2c/devices/0-0036///rt_rate_ms' (-1)
E/lights-lm3533( 320): set_rates: write error (No such file or directory)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-red/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-green/brightness' (-1)
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness': No such file or directory
E/lights-utils( 320): Unable to open '/sys/class/leds/lm3533-blue/brightness' (-1)
E/lights-core( 320): LED 'backlight' is not of type 0
E/lights-core( 320): LED 'battery' is not of type 0
E/lights-core( 320): LED 'notifications' is not of type 0
E/lights-core( 320): LED 'button_rgb' is not of type 0
E/lights-core( 320): LED 'pattern_2' is not of type 0
E/lights-core( 320): LED 'pattern_3' is not of type 0
E/lights-core( 320): LED 'pattern_1' is not of type 0
E/lights-core( 320): LED 'attention' is not of type 0
E/lights-core( 320): LED 'button_2' is not of type 0


Any possibility to locate the hardware problem and fix it?

--
Matthieu

Not sure about hardware problems but maybe it could be a software problem?? Have you tried factory resetting or reflashing the rom you are using?? Maybe that will fix. Also when your phone boots up and the Sony Logo shows is that bright?? OR is that really dark as well. Either way I would reflash the rom and see if the problem goes away otherwise contact Sony Support. Thanks!!
 

fropmontois

New member
Jul 10, 2014
3
0
Not sure about hardware problems but maybe it could be a software problem?? Have you tried factory resetting or reflashing the rom you are using?? Maybe that will fix. Also when your phone boots up and the Sony Logo shows is that bright?? OR is that really dark as well. Either way I would reflash the rom and see if the problem goes away otherwise contact Sony Support. Thanks!!

Yep, I did a factory reset. The boot logo is sometimes bright, but more often dark.
I've returned the phone to my local dealer, I'm expecting it back within 2-3 weeks.

Thanks

Matthieu