plegdroid

blank screen after turn phone off and on.

49 posts in this topic

Afternoon, well I got my new LCD, the problem I've now got, is the screen works ok from boot, but when the screen turns off, or I turn it off, when I return the phone back on, the screen stays blank which is not good :( .

Does anyone have any ideas?

F.I.A :)

0

Share this post


Link to post
Share on other sites

Different screen driver maybe? I'm sure I previously read something about that. You may need a kernel that fully supports it.

1

Share this post


Link to post
Share on other sites
Different screen driver maybe? I'm sure I previously read something about that. You may need a kernel that fully supports it.

thanks, I'll have a scout around, I've tried ceco's staraddict kernel, it's boots ok and the screen works until it turns off, then black screen. :)

0

Share this post


Link to post
Share on other sites

Try normal S Series kernel. Not the sfr one. Might do the trick.

So you replaced the screen yourself or service did it?

Didn't they flash appropriate stock rom?

1

Share this post


Link to post
Share on other sites

You could also post output of "adb shell cat /proc/kmsg" done while booting.

1

Share this post


Link to post
Share on other sites

afternoon, yam tried all kernel and prox fixs, I fitted it myself, it could be the LCD itself,it flickers at high brightness and when on charge with the phone off with the big green battery,the whole screen goes on and off . I'll try and grab adb shell. :)

0

Share this post


Link to post
Share on other sites

Regarding phone-off-charging animation.

I already had such a case with one Skater from Uzbekistan.

I found out that the bootloader that is stored in appsboot.mbn of TPTs we normally use for repartitioning was snot compatible with his model.

See here.

1

Share this post


Link to post
Share on other sites

evening, ive tried to grab cat/proc/kmsg, but get

C:\zteadb>adb shell

[email protected]:/ $ cat/proc/kmsg

cat/proc/kmsg

/system/bin/sh: cat/proc/kmsg: not found

[email protected]:/ $

also, how can i start log with the phone off, as it dosnt recognize the device until turned on? :)

0

Share this post


Link to post
Share on other sites

You're missing space after cat

Log is not possible while phone's off.

1

Share this post


Link to post
Share on other sites

please delete

Edited by plegdroid
0

Share this post


Link to post
Share on other sites

I can't see any problem here.

kmsg is more important to see since there we can see the initialization of screen hardware.

0

Share this post


Link to post
Share on other sites
I can't see any problem here.

kmsg is more important to see since there we can see the initialization of screen hardware.

thank you, I'll grab on the morrow. :)

0

Share this post


Link to post
Share on other sites

please delete

Edited by plegdroid
0

Share this post


Link to post
Share on other sites

please delete

Edited by plegdroid
0

Share this post


Link to post
Share on other sites

Essentialinfo is missing,though.

You need to cat kmsg immediatelywhen it starts booting.

You should see info on cpu freq table being initialized.

1

Share this post


Link to post
Share on other sites
Essentialinfo is missing,though.

You need to cat kmsg immediatelywhen it starts booting.

You should see info on cpu freq table being initialized.

evening, I'll get it right yet :P, I'll grab on the morrow again :( gotta get the kid's to sleep.

thanks Ceco :)

0

Share this post


Link to post
Share on other sites

No problem.

Gotta get myself to sleep :)

1

Share this post


Link to post
Share on other sites
No problem.

Gotta get myself to sleep :)

lol,i retried. re adb,is there a quick command that can be used?

than having to request adb shell untill the device is found,request adb shell,let it grant shell,type su,wait for that to be granted,then type the proc/kmsg request. or must i just need to type quicker?

:D

0

Share this post


Link to post
Share on other sites

Try this single-line command

adb shell cat /proc/kmsg

su is not needed to read kmsg. Well depends on rom.

but in that case just do

adb shell su; cat /proc/kmsg

1

Share this post


Link to post
Share on other sites
Try this single-line command

adb shell cat /proc/kmsg

su is not needed to read kmsg. Well depends on rom.

but in that case just do

adb shell su; cat /proc/kmsg

thanks Ceco,will try when get home :)

0

Share this post


Link to post
Share on other sites

please delete

Edited by plegdroid
0

Share this post


Link to post
Share on other sites

evening, I've put skatie rom on and that dosnt require the su command <img src='http://www.modaco.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />

hope this has grabbed it early enough <img src='http://www.modaco.com/public/style_emoticons/<#EMO_DIR#>/smile.png' class='bbc_emoticon' alt=':)' />

Edited by plegdroid
0

Share this post


Link to post
Share on other sites

please advise if I need to grab earlier still than this ?

with much thanks :)

0

Share this post


Link to post
Share on other sites

Still not enough...

Prepare the command, turn on the phone and execute it. If it gives error about device not present execute immediately again until it catches (keyboard up key will get you last command so you don't need to type it again).

1

Share this post


Link to post
Share on other sites

And be sure your command prompt has enough scroll buffer set so it doesn't trim the very first lines when output exceeds the buffer

. Or you can redirect output to a file

Edited by C3C0
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.