Digitizer not responding on lock screen

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Wake - No response on lock screen from Digitizer  
2. Reboot / Power up - no response 
3. Wipe/Clear Cache and re-install - no response 

What is the expected output? What do you see instead?
Can not get beyond locks screen, digitizer non responsive 

What version of the product are you using?
aospX-1.0.0-BR2-DHD

Please provide logcat ouput and any additional information below.
(required)
1. Upgraded from AR13 directly to AR21 and the issue became sporadic
2. Currently, can't get past the lock screen     
2. On/Off power and Vol up/down function properly 

Original issue reported on code.google.com by rodub...@gmail.com on 4 Jun 2012 at 12:09

[GoogleCodeExporter]

Correction: I upgraded from AR13 to BR1 not BR2

I had no issue with digitizer/lock screen prior to upgrade AR13 to 1.0.0-BR1

Original comment by rodub...@gmail.com on 4 Jun 2012 at 12:11

[GoogleCodeExporter]

Are you flashing anything extra? ie another kernel..etc..? But I recommend a 
full wipe/factory reset, then dont flash anything else..then see how it 
responds on a clean boot. This is something thats specific to your device, if 
it was something rom specific it would be happening to everyone. So a little 
more info is going to be needed (ie logcat log). But have you done a full wipe? 
Or just flashed one on top of another? Because theres been quite a few versions 
that require a full wipe, no exceptions, otherwise it will cause alot of 
problems.

If you are flashing another kernel, such as Lords, I cannot support anything 
that I dont compile myself. So if it doesnt work after a full wipe/factory 
reset and clean install only, get me a logcat log along with a dmesg log (Click 
the Issues tab to see instructions on how to provide a log)

Original comment by robbe...@gmail.com on 4 Jun 2012 at 12:25

[GoogleCodeExporter]

I've done a full wipe/factory reset, same issue.  I'm not flashing
anything else...  I will work on getting you the logcat log (Need to
figure out how).

Thanks so much for the quick reply!

PS. Had the screen/digitizer replaced last November after a drop,
wonder if it's failing?

Original comment by rodub...@gmail.com on 4 Jun 2012 at 12:36

[GoogleCodeExporter]

Its very possible. With something like this driver, it either works or it 
doesnt..usually theres nothing else needed to trigger it (ie a certain setting 
or whatever) that would vary from user to user, especially right after a clean 
wipe/install...it would just flat out work or not work and would happen to 
mostly everyone. But with the logs I can check to see if something is erroring 
out or crashing or whatever. 

But are you able to install and run other roms without issues?

Original comment by robbe...@gmail.com on 4 Jun 2012 at 12:53

[GoogleCodeExporter]

So happens,I'm running Windows 8 on the laptop I brought home this
weekend (No Android USB Driver support yet).
The only ROM I have on my SD is BR1, figures...  I'll try another ROM
tomorrow and let you know.

Thanks so much!

Original comment by rodub...@gmail.com on 4 Jun 2012 at 1:16

[GoogleCodeExporter]

Going to close this ticket for now, as it seems to be specific to your device 
only. If you are able to try another rom and the issue is not present, but 
still happens with latest aospX, then feel free to reopen another ticket along 
with debug logs. 

Original comment by robbe...@gmail.com on 7 Jun 2012 at 10:33

• Changed state: WontFix