48 replies to this topic

[plegdroid]

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

[H3ROS]

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

[plegdroid]

H3ROS, on 15 October 2012 - 04:04 PM, said:

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.

[C3C0]

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?

[C3C0]

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

[plegdroid]

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.

[C3C0]

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. http://www.modaco.co...60#entry2024491

[plegdroid]

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

C:\zteadb>adb shell
shell@android:/ $ cat/proc/kmsg
cat/proc/kmsg
/system/bin/sh: cat/proc/kmsg: not found
127|shell@android:/ $

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

[C3C0]

You're missing space after cat
Log is not possible while phone's off.

[plegdroid]

please delete

Edited by plegdroid, 19 October 2012 - 10:07 PM.

[C3C0]

I can't see any problem here.
kmsg is more important to see since there we can see the initialization of screen hardware.

[plegdroid]

C3C0, on 16 October 2012 - 08:54 PM, said:

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.

[plegdroid]

please delete

Edited by plegdroid, 19 October 2012 - 10:08 PM.

[plegdroid]

please delete

Edited by plegdroid, 19 October 2012 - 10:08 PM.

[C3C0]

Essentialinfo is missing,though.
You need to cat kmsg immediatelywhen it starts booting.
You should see info on cpu freq table being initialized.

[plegdroid]

Quote

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 , I'll grab on the morrow again    gotta get the kid's to sleep.

thanks Ceco

[C3C0]

No problem.
Gotta get myself to sleep

[plegdroid]

C3C0, on 17 October 2012 - 09:01 PM, said:

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?

[C3C0]

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

[plegdroid]

C3C0, on 18 October 2012 - 03:40 AM, said:

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