Lockscreen unresponsiveness.

[GoogleCodeExporter]

Ever since the Sweep2Unlock (v0.65), using Incert-Coin Sense 4 RC(4 and 5) the 
phone randomly enters in a state of unresponsiveness in the unlock screen. 
Sometimes after a long period of inactivity, other times not long after I just 
"locked" the screen. It seems to happen a slightly less often since version 0.7 
and 0.8.
What happens is that the phone does not detect any inputs, neither on the 
screen, nor on the capacitive buttons, volume and power keys work fine.

This is the kmsg file I have:
http://pastebin.com/8mM1gfa0

Original issue reported on code.google.com by cassiori...@gmail.com on 11 Apr 2012 at 3:47

[GoogleCodeExporter]

Known and addressed in new beta. (0.85)
When I release it, check if this issue is fixed.

Original comment by showp1984 on 11 Apr 2012 at 4:32

• Changed state: Started
• Added labels: Android-ICS, Device-pyramid, Priority-Critical, Usability, Version-0.8, branch-Sense
• Removed labels: Priority-Medium

[GoogleCodeExporter]

v0.85 uploaded @ http://bricked.de/download_beta.php

Original comment by showp1984 on 11 Apr 2012 at 6:13

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by showp1984 on 11 Apr 2012 at 6:13

• Changed state: Fixed

[GoogleCodeExporter]

The lock just happened again, with Beta 0.851.

kmsg: http://pastebin.com/NF5LRUfJ

Original comment by cassiori...@gmail.com on 12 Apr 2012 at 2:26

[GoogleCodeExporter]

There is a problem with the suspend/resume function of the touchscreen, looking 
into that ;)

Original comment by showp1984 on 12 Apr 2012 at 3:09

• Changed state: Started

[GoogleCodeExporter]

Happened again, on beta v0.856, still have to try it on beta v0.858.
Three times while I was on a party house (bad/zero signal strength, and hot 
conditions), in a time length of 4 hours... I'm under the impression that it 
fixed itself once, but might not be right, my memory is kinda messed up, go 
figure... lol
Well, managed to get just one kmsg... need me to post it up on pastebin again?

Original comment by cassiori...@gmail.com on 14 Apr 2012 at 6:50

[GoogleCodeExporter]

I can actually confirm that it solved itself once again... The screen was 
unresponsive, and suddenly when I pulled the top task bar down, it started 
working again.

Original comment by cassiori...@gmail.com on 14 Apr 2012 at 6:56

[GoogleCodeExporter]

do this: adb shell cat /sys/android_touch/vendor
I bet you have sth like this: CY8CTMA349_[...]

Original comment by showp1984 on 14 Apr 2012 at 9:18

[GoogleCodeExporter]

I got this:
CY8CTMA340_x000B_32

Original comment by cassiori...@gmail.com on 14 Apr 2012 at 10:08

[GoogleCodeExporter]

omfg...
There are more revisions than I initially thought...

Original comment by showp1984 on 14 Apr 2012 at 10:10

[GoogleCodeExporter]

Fixed with 0.9.
Confirm please.

Original comment by showp1984 on 16 Apr 2012 at 3:24

• Changed state: ShouldBeFixed

[GoogleCodeExporter]

Fixed as far as I can see. I'll keep you posted if it happens again. Also, 
great job ;)

Original comment by cassiori...@gmail.com on 16 Apr 2012 at 3:28

[GoogleCodeExporter]

Thanks, closing up here ;)

Original comment by showp1984 on 16 Apr 2012 at 3:57

• Changed state: Fixed

[GoogleCodeExporter]

Not fully fixed. There's no lockscreen unresponsiveness issue now, but after 
call I often can't end it immidiately because the screen is fully unresponsive. 
So I need to off/on the screen to make it work. Version 1.1

Original comment by Olegat0r...@gmail.com on 3 May 2012 at 6:11