search

rrathi / adamICS

This is adam ICS port
33 stars 14 forks source link

Screen completely locked on boot #93

Closed arnauvp closed 1 year ago

arnauvp commented 12 years ago

Hi, My Adam (PixelQi+3G) can't run ICS. I've tried installing all possible ROMs, even the one given by NI. There are 2 possible outcomes: it gets stuck in the boot with the color animation (a circle of red-blue pieces - CM9-ADAM-BETA-AIO) or it gets to the unlock screen (beta3, beta4 ) and I am left there with the screen ignoring almost all my touches. It's not the same issue as others have reported on the threads: it's not that the circle moves but doesn't unlock. It's just as if it wasn't a touchscreen anymore, but the physical buttons work and I can press on "power down" and "cancel" (but not on OK). I've been struggling with this since the first alphas came and now I want to give it a last chance before throwing the device out of the window :)

Is there anything I can investigate (boot logs) to track this down?

Borkata commented 12 years ago

I have experience a similar issue even on Froyo rom. Touchscreen stops responding when I am on Edge network and only reboot fixes. You can try to remove the SIM and see if something changes. Also logs are always welcome - try doing also: logcat -b radio

arnauvp commented 12 years ago

Hi Borkata, thanks for replying. I am using Adam with no SIM, wifi only. I never get past the unlock screen so I can't configure wifi. Could you elaborate a bit on how to get the logs? The logcat would be issued in a Linux terminal while the device is connected in APX mode?

Borkata commented 12 years ago

Thats indeed interesting. Have you done cache wipe from recovery. Also you can boot till the lock screen and connect cable and use adb logcat command to take the log.

arnauvp commented 12 years ago

Yes I have done even the 3 wipes recommended in some places. I managed to get the log from the boot, I'll analyze and upload soon. Also I remembered that I could plug a mouse in the tablet and it worked! I could unlock the screen and do anything properly, but touch still doesn't work. I activated "track touches" in developer menu but I didn't see any feedback. Tablet reboots in less than 3 minutes every time (using mouse).

arnauvp commented 12 years ago

Here are the full logs: http://pastebin.com/xGLw5Wpv I'll be away for the weekend, but I'll get back to this next week and try to bring more info (stack traces, etc)

arnauvp commented 12 years ago

I think the problem lies in these lines: W/InputReader( 168): Invalid value for touch.size.calibration: 'normalized' W/InputReader( 168): Touch device 'at168_touch' did not report support for X or Y axis! The device will be inoperable. I/InputReader( 168): Device added: id=1, name='at168_touch', sources=0x01001513 I/InputReader( 168): Reconfiguring input devices. changes=0x00000004 W/InputReader( 168): Touch device 'at168_touch' did not report support for X or Y axis! The device will be inoperable.

arnauvp commented 12 years ago

The result of cat /proc/devices and cat /proc/bus/input/devices: http://pastebin.com/ujPJC2hT

Borkata commented 12 years ago

Indeed it seems your touchscreen is not operating normally. Have you got such issues on Froyo roms?

arnauvp commented 12 years ago

Nope, nor even on HoneyComb. Touchscreen always worked.

On 9 July 2012 08:51, Borkata < reply@reply.github.com

wrote:

Indeed it seems your touchscreen is not operating normally. Have you got such issues on Froyo roms?

Reply to this email directly or view it on GitHub: https://github.com/rrathi/adamICS/issues/93#issuecomment-6839631

Borkata commented 12 years ago

HoneyComb is using the old kernel. Will try to look at at168 driver if I have time.

arnauvp commented 12 years ago

Thank you man. No hurry :)

On 9 July 2012 08:53, Borkata < reply@reply.github.com

wrote:

HoneyComb is using the old kernel. Will try to look at at168 driver if I have time.

Reply to this email directly or view it on GitHub: https://github.com/rrathi/adamICS/issues/93#issuecomment-6839672