Blank-Of-Death(?) Still seems to be an issue

[jjsullivan5196]

#24

Not sure if it's exactly the same issue, but sometimes when I have a disconnected call or lock and unlock the screen fairly fast, the screen either:

1. Doesn't turn back on until successive unlock(But at that moment IS unlocked) or
2. Starts to have this weird video glitch where some groups of pixels move to strange positions and some color layers pop in-and-out. I guess the most apt description is that it looks like a broken CRT.

The second issue is only solvable if the battery is removed.

I can post video, pics, or syslogs if someone can instruct me how to do so. I'm currently running build "cm_apexqtmo-userdebug 4.3 JSS15J eng..20130806.185815 test-keys" with cwm recovery 6.0.3.5 both from infernix's jenkins build service and JB stock boot and modem from http://forum.xda-developers.com/showpost.php?p=41209211&postcount=1

Currently it doesn't seem to persist, but it did happen only a few minutes ago. It happens mostly when the phone is taken off the charger or a call is dropped.

[infernix]

Can you post your 'cat /proc/cmdline'?

[jjsullivan5196]

androidboot.hardware=qcom user_debug=31 zcache sec_log=0x80000@0x88d00008 sec_dbg=0x40000@0x88d90004 sec_debug.reset_reason=0x1a2b3c00 etb_buf=0x4000@0x8fffb9c0 androidboot.debug_level=0x4f4c sec_debug.enable=0 sec_debug.enable_user=0 androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_debug=0 cordon=c60f2aeda0ed91eec49998c0bb7bf2f7 sysscope=0xff000000 loglevel=4 samsung.hardware=SGH-T699 androidboot.emmc_checksum=3 androidboot.bootloader=T699UVBMC5 androidboot.nvdata_backup=0 androidboot.boot_recovery=0 androidboot.batt_check_recovery=0 level=0x574f4c44 sec_pvs=0 androidboot.emmc=true androidboot.serialno=bb0a4452 androidboot.baseband=msm

There you go. Also the glitch seems much more benign as it seems to stop now after a certain amount of time.