White Screen at cm10.1 Build 18.07.2013 (G)

[fredhy91]

Thank u for ur hard theWhisp, I flash ur new build for cm 10.1 but after i lock my device the home button and the power button only show the white screen and after that only reboot the device that i can do, nothing else.

[fredhy91]

my device is jena

[nadigunawan]

i also have white screen problem. hopefully it will fix

[skalteis]

A gist with attached dmesg output for a known good build and the latest malfunctioning 20130818 build can be found here:

https://gist.github.com/skalteis/6288859

[xzertexz]

same problem with me too in my GT-6500T

[TheWhisp]

I already explained here: http://forum.xda-developers.com/showpost.php?p=44751450&postcount=299

There is no possible way to detect which device has the LCD HW version that suffers from this bug. That means, if I add something to fix white screen, it can break something on devices that didn't have that problem in the first place.

There are no error messages whatsoever. I am currently marking this as wontfix

[skalteis]

I see.

But if you'd provide a patch file then users who happen to have this particular problem could patch your kernel sources and build a working kernel themselves... just mentioning. Sort of leaving the error-detection to the human brain instead of coding a test for a certain (nonexistent) HW ID... :-)

Thanks for your efforts.

[sipe]

I have problem too with white screen.

Here is my logcat and dmesg with older build and with white screen bug. http://forum.xda-developers.com/showthread.php?p=44266002#post44266002

Here is my kmsg on stock device. http://forum.xda-developers.com/showthread.php?p=44411143#post44411143

And in kmsg you can find your HW ver. Mine is version 3. Here is part of my kmsg on stock rom. On every device wake up he repeats this line

<7>[ 629.796738] LCD HW rev is 3, apply 3's init sequence <7>[ 629.986323] LCD display on cmd : completed <3>[ 629.989060] ts_power_enable on <6>[ 629.994661] bma222_early_resume <6>[ 629.996733] hscd_early_resume <6>[ 629.997316] late_resume: done <7>[ 629.997380] LCD [BACKLIGHT] : 10 <7>[ 629.999680] LCD [BACKLIGHT] : 20 <7>[ 630.000713] LCD [BACKLIGHT] : 30 <7>[ 630.001743] LCD [BACKLIGHT] : 41 <7>[ 630.003128] LCD [BACKLIGHT] : 51 <7>[ 630.004513] LCD [BACKLIGHT] : 61 <7>[ 630.005910] LCD [BACKLIGHT] : 71 <7>[ 630.007091] LCD [BACKLIGHT] : 82 <7>[ 630.008490] LCD [BACKLIGHT] : 92 <7>[ 630.009886] LCD [BACKLIGHT] : 102 <7>[ 630.011283] LCD [BACKLIGHT] : 112 <7>[ 630.012310] LCD [BACKLIGHT] : 123 <7>[ 630.013705] LCD [BACKLIGHT] : 133 <7>[ 630.015421] LCD [BACKLIGHT] : 143 <7>[ 630.018578] LCD [BACKLIGHT] : 153 <7>[ 630.019586] LCD [BACKLIGHT] : 154 <3>[ 630.421866] [TSP] 0 - P <4>[ 630.580016] [KeyLED] msm_keypad_bl_led_set: gpio124_value=0 <3>[ 632.484146] kgsl kgsl-3d0: |kgsl_pwrctrl_axi| axi on, device 0 <3>[ 632.546826] kgsl kgsl-3d0: |kgsl_pwrctrl_irq| irq on, device 0 <3>[ 632.547963] kgsl kgsl-3d0: |adreno_start| device started status 0 <3>[ 632.547991] kgsl kgsl-3d0: |kgsl_pwrctrl_wake| state -> ACTIVE, device 0 ts 0xfbf <3>[ 633.345297] [TSP] 0 - P <4>[ 633.347231] [KeyLED] msm_keypad_bl_led_set: gpio124_value=1 <3>[ 634.523526] [TSP] 0 - P <3>[ 634.596264] kgsl kgsl-3d0: |kgsl_timer| idle timer expired device 0 On every device wake up he repeats this line <7>[ 629.796738] LCD HW rev is 3, apply 3's init sequence So rom checks every time for LCD HW. Please TheWhisp fix it. If you need logs or anything write it, I will provide every logs you need.

[TheWhisp]

that kmsg is from stock ROM. And the message "LCD HW rev is 3, apply 3's init sequence" prints board's HW version: https://github.com/TheWhisp/android_kernel_samsung_msm7x27a/blob/jb-3.0/drivers/video/msm/lcdc_jena.c#L628

[sipe]

Does white screen applies only to LCD HW rev. 3?

Is there any log you require from stock to try to fix this problem?

[TheWhisp]

idk. I also have rev.3 and no white screens.

[TheWhisp]

Try this: https://www.dropbox.com/s/76pgapyfwqx2y6k/boot.img-jena-mdp-continuous-display.zip I added MDP continuous display support (from stock kernel) Try this only with 18/08 build!

[epsmed]

I have uploaded my log file in http://forum.xda-developers.com/showpost.php?p=44931527&postcount=2064 was unable to attach .txt file here.

Thank you for your great work

[epsmed]

I downloaded the boot.img-jena-mdp-continuous-display.zip and put the boot image file into the cm-10.1-20130818-UNOFFICIAL-jena.zip file. Then install this with CWM recovery. White screen still there. Am I wrong? If yes how I have to install the boot.img-jena-mdp-continuous-display.zip ? Thank you

[TheWhisp]

check the build date of kernel

[epsmed]

Sat Aug 24 10:07:45 EEST 2013

[epsmed]

Version 3.0.93

[sipe]

Here TheWhisp logs with new kernel, still white screen http://forum.xda-developers.com/showpost.php?p=44942704&postcount=2076

[TheWhisp]

well, at least the dithering is fixed :) idk, I have added all Samsung specific code back to display stuff.

[tacsass]

I tried it and don't work... After unlock, still white...

[sipe]

Maybe this helps.

Everytime, I mean 100% after device slept for a longer time (example 20mins or more) on first wake-up there is always white screen.

So after longer period of sleep white screen always appear.

[sipe]

Again me. Tested in a call, also white screen, switched screen off and on multiple times with proximity sensor. No power key hope it shows something up.

http://forum.xda-developers.com/showpost.php?p=44951905&postcount=2083

[sipe]

Posting here because no answer in xda thread.

TheWhisp, I'm sure that update MSM MDP to ics_chocolate in kernel 12.7.2013 cause LCD white screen for part of us.

Maybe just maybe problem is lying here. https://github.com/TheWhisp/android_...ay_lcdc.c#L109

Can you compile me a custom kernel with this two switched mdp_pipe_ctrl(MDP_OVERLAY0_BLOCK, MDP_BLOCK_POWER_ON, FALSE); MDP_OUTP(MDP_BASE + LCDC_BASE, 1);

Line 109 and 110

Can you switch them and compile kernel for me to test it out? Thanks So can you compile me a kernel with lines 109 and 110 switched? Thanks

[TheWhisp]

Of course that change caused the problem. I was saying that right after the first report of the issue. I just didn't want revert that change.

[NaokiXie]

Maybe this one can come with a patch, noting that the patch is for who has white screen issues.. anyways i dont have any problems on the screen.

[sipe]

Yes TheWhisp. But can you make on kernel with that two lines changed?

Why won't we have two kernels one for white screen problem and one for normal devices?

[fbsoft]

Same here, same problem... with CM10, Cm10.1 . If Gapps is installed it does it even faster and more often... Tell me what you need, i can open the phone up in little bits and give you all the info needed to solve this issue :)

[fbsoft]

I found a way to trick it:) you have to be fast but it works, i think it's the graphics that go into standby and they do not come online that fast or smth like it, hardware wise. But you can activate the screen doing the folowing tasks. If phone is locked, open it to the famous white screen, now unlock it ( the touch is responsive at this point ) so swipe by default to right, the click will be heard, then this is the tricky part that activates your screen... Do fast vol up, (listen to the clicks they will be lagging... No matter do these 3 steps fast), vol down, lock the phone and then open it again and voila the screen appears ok cause of the volume control that it is forced to be displayed and it kickstarts the background. I had done this seval times and it worked confirm please if it works

[nadigunawan]

thanks for your information, i have tried to do that..but i need do it again after several minutes because white screen come up again...

[sipe]

Here are logs from last version 30.8.2013 http://forum.xda-developers.com/showpost.php?p=45189241&postcount=2151

fbsoft trick is working. I could get LCD every time, and I see volume bar so it has to do it with something.

Unlock on blind, volume up and volume down and qucik relock. It is working.

Logs are on xda. Maybe The Whisp can find something in logs :)

Thanks fbsoft

[fbsoft]

@sipe hehe glad i could help :) yea you need to do it fast, i had tryed with the gapps installed and the trick worked, same thing... just lock it and unlock it fast, with the volume buttons, of course.... If you leave your phone alone for some time ( 30 mins up to 1h i think ), if you unlock it it displays ok the first time, but if you lock it and then unlock it, the white screen appears again unfortunetly. Also @nadigunawan yea you have to do these steps every time. It's not a full fix, just a ... let's call it "alternative", to wake the display drivers from sleep mode and display properly the screen Also i had tryed to OC the CPU and video, no such luck, i have to do these tasks even faster... If they are at default the "lag" provides the perfect timing to get it out of sleep mode

[TheWhisp]

See what happens with this kernel: https://www.dropbox.com/s/ikbnc8gmlj6fzqt/boot.img-3.0.94.zip

[fbsoft]

@TheWhisp Scratch taht stupid Question :) testing now Uhm from CWM, got a Installation aborted ( Install update from zip file ) Do i need to tar it in Linux to Ustar ?

[fbsoft]

@TheWhisp Managed, got it working, first impression, first screen a little bit slower than the original release, there is a certain lag when typing, and still getting the white screen... :( a lot less, if the phone doesn't do anything else ( like updates ) it displays ok from beggining, otherwise... the screen remains white and if you lock it... wait for it to what ever it does, and unlock it normally then the screen works, no need for the volume keys... An improvement i have to say

[sipe]

Wow, white screen is happening much less this time. I don't even need to use fix, just open and close screen few times and always get to LCD.

New logs maybe you can fix white screen bug. This is nice improvement.

Also when waking device with home button white screen ocurrs less then power button.

http://forum.xda-developers.com/showpost.php?p=45197998&postcount=2153

[fbsoft]

@TheWhisp @sipe true, if you get it started, and then lock it and open it again, the screen goes normally. This time, if you leave the phone alone, you get a white screen. Got any more aces up your sleeve @TheWhisp :)

[sipe]

Also, after longer device sleep I can't get normal lock screen only with using "trick".

So just to known.

[fbsoft]

Yea and i've noticed that that if you only rock the volume down the trick doesn't work, or if your not at the toppest volume. If it at max i don't know why the volume screen sticks a lot longer. Anyway a good improvement. A very good improvement. Also this problem is for CM10 and the most recent build of CM10.1 as well, so there's something persistent here... same fix/trick in those as well

[TheWhisp]

Try: https://www.dropbox.com/s/rnxdbro78isfo61/boot.img-3.0.94-updated.zip

[fbsoft]

I had installed a few stuff on my phone and ... the screen returns to the normal... lagness, when i enter it in the lock mode, with the trick... even the audio is lagging, i press it and after a few seconds even i hear the sound of the vol up or down, or sometimes the sound isn't played at all... as if i've never hit anything although the volume changes

[TheWhisp]

did you try the latest boot.img I uploaded?

[sipe]

Again white screen with power button and home button. When trying to get to normal screen, home button works more often then power button. Every few times with home buttons unlocks normal but there is no pattern.

logcat1.txt> pressed power button until normal screen showed up logcat2.txt> pressed home button until normal screen showed up logcat3.txt> unlocking with volume trick kmsg4.txt> everything combined (power, home button and trick)

http://forum.xda-developers.com/showpost.php?p=45205437&postcount=2154

[TheWhisp]

Post the logs, not on XDA. There is not point posting them in both places. Upload a normal kmsg. Power off the device. Power it on. Don't do anything else. Start taking kmsg. Turn off the screen. Wait at least 15-20 seconds. Turn on screen. Wait 15-20 seconds. Stop taking kmsg. Upload.

[sipe]

Here. Started device, entered pin, started kmsg, turn off device, wait ~20 secs, turned on screen 20 secs, stopped kmsg. Here is log. On dropbox because it's to big to paste it here. http://db.tt/zP1t7Stc

[fbsoft]

so i've started logcat to see the logs, the error seem to have a TAG -> bug 7643792 fitSystemWindows([0.25][0.0]) Adreno200-EGLSUB ConfigWindoWatch:2087: Format RGBA_8888 Adreno200-EGLSUB CreateImage:897: Android Image Adreno200-EGLSUB GetImageAttributes:1106 RGBA_8888 .... After a few times Choreographer Skipped 35 frames! The application may be doing too much work on its main thread Adreno200-EGLSUB CreateImage:897: Android Image Adreno200-EGLSUB GetImageAttributes:1106 RGBA_8888 500 dalvikvm GC_CONCURRENT freed 1400k, 36% free... and after it worked

[fbsoft]

did it again a few more time and i've got lights.msm7x27a write_int failed to open /sys/class/button-blacklight/brightness

after lock screen displayed... again the adreno200 errors and after a few more tryes i got PhoneStatusBar dissable <expand icons alerts ticker system_info back home recent clock* search > PhoneStatusBar setLights0n( true ) Adreno200-EGLSUB CreateImage:897: Android Image Adreno200-EGLSUB GetImageAttributes:1106 RGBA_8888 Adreno200-EGLSUB CreateImage:897: Android Image Adreno200-EGLSUB GetImageAttributes:1106 RGBA_8888 Adreno200-EGLSUB <GetImageAttributes:1092 RGB_565 Adreno200-EGLSUB CreateImage:897: Android Image Adreno200-EGLSUB <GetImageAttributes:1092 RGB_565 dalvikvm.. dalvikvm dalvikvm WAIT_FOR_CONCURENT_GC blocked 52ms audiohardware Routing auto to Speakerphone... and at this step i think it's ok Adreno200 not showing anymore i've got it working

[fbsoft]

When i've left it for 30secs , and then got it back again i've got an error ( the one above mentioned ) lights.msm7x27a write_int failed to open /sys/class/button-blacklight/brightness PowerManagerService-JNI Waking up from sleep... keystore uid: 1000 action z -> 7 state: 3 -> 3 retry: 4 keystore uid: 1000 action z -> 7 state: 3 -> 3 retry:4 keystore uid: 1000 action z -> 7 state: 3 -> 3 retry:4 WindowManager Lock screen displayed! AccelerometerListener enable(flase) Adreno200-EGLSUB CreateImage:897: Android Image Adreno200-EGLSUB <GetImageAttributes:1092 RGBA_8888 Adreno200-EGLSUB CreateImage:897: Android Image Adreno200-EGLSUB <GetImageAttributes:1092 RGBA_8888 PowerManagerService-JNI Excessive delay in autosuspend_disable() while turning screen on: 412ms SurfaceFlinger Screen acquired, type=0 flinger=0xe318

[fbsoft]

@TheWhisp the logs i'm posting here, are from the latest boot.img

[fbsoft]

got my log shared as well to dropbox https://www.dropbox.com/sh/z6p04ph7qbhyfjj/bwF7-mr6Cs

[micsialdracu]

Hi. I have S6500D with CM 10.1 build 30.08.2013. I've tested latest 4 builds and white screen issue was not a problem for me, until today. Phone starts with white screen, when touching volume keys plays sounds with a little lag, home button and power buttons works but white screen remain. But, problem is that i have white screen even in recovery mode ( CWM 6.0.3.3 jena) and download mode. I cannot do anything. I flashed with Odin 3 v.3.04 original rom and white screen persist. After power on, display turn on in white screen and remain on, then phone vibrate 3 times, periodic. With the phone off and on charging, white screen appear and display turn off after few seconds. What do you think ? Is there any chances to repair my phone?

[sipe]

Try this. Install lastest recovery (6.0.3.5) Wipe everything (system, cache, data, emmc, dalvik!) then flash from odin last stock (S6500DXXMF1).