• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Nexus 4 Touchscreen Problem with 4.2

Great news! My laptop had the RSA key or whatever it's called for ADB approved and I am able to get the logcat and use a program to control my screen!
 
We may be able to figure out what's going on with the touchscreen if you could post the logcat here.
Code: 
adb logcat > cat.log
^ should export the logcat output to your computer. You may want to give it a once through to make sure it doesn't include any personal information (email address in particular) and then attach it here. :)
 
What is the current setup for that log? What ROM, recovery, bootloader, Android version, etc?

Nothing in it jumps out at me as a red flag (but I'm far from a genius at this sort of thing). Would it also be possible for you to pull your dmesg and last_kmsg logs as well?
Code: 
adb shell dmesg > dmesg.txt
adb shell cat /proc/last_kmsg > kmsg.txt

Those are a bit lower level and may give us info about any drivers that fail to load.
 
codesplice said:
What is the current setup for that log? What ROM, recovery, bootloader, Android version, etc?

Nothing in it jumps out at me as a red flag (but I'm far from a genius at this sort of thing). Would it also be possible for you to pull your dmesg and last_kmsg logs as well?
Code: 
adb shell dmesg > dmesg.txt
adb shell cat /proc/last_kmsg > kmsg.txt

Those are a bit lower level and may give us info about any drivers that fail to load.
Click to expand...
I'm using TWRP, CyanogenMod 10.1, stock bootloader, 4.2.2. Getting those logs right now.
 
I'm seeing some pretty obvious touch-related errors in the kmsg:
Code: 
[   15.611816] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

[   15.628692] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

[   15.645751] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

[   15.662902] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

LOTS of them. It does seem that it's loading up the touch driver (as best I can tell), but seems to be ignoring all input because reasons (again, I'm getting a bit out of my depth here!).

Have you tried flashing an alternative kernel to see if that does anything? Just make sure it's built for the same Android/CM version.
 
codesplice said:
I'm seeing some pretty obvious touch-related errors in the kmsg:
Code: 
[   15.611816] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

[   15.628692] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

[   15.645751] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

[   15.662902] [Touch E] [synaptics_ts_get_data 217] Interrupt_status reg is 0. -> ignore

LOTS of them. It does seem that it's loading up the touch driver (as best I can tell), but seems to be ignoring all input because reasons (again, I'm getting a bit out of my depth here!).

Have you tried flashing an alternative kernel to see if that does anything? Just make sure it's built for the same Android/CM version.
Click to expand...
How would I go about flashing a kernel?
Recommendations?
 
Last edited:
Well damn. I'm running out of ideas. I really don't get why it would work with 4.3+ but not 4.2. Very strange.

Maybe a smarter person can get more useful information from the logs.
 
Tried MultiROM, but it broke touch in 4.4 CM when I installed LuneOS. Is it possible that it's a hardware thing?
 
I installed stock 4.3 and was having touch issues, but a reboot fixed it all. Really confusing stuff my nexus 4 is doing :(
 
codesplice said:
I suppose it's possible, but I'd really expect a hardware touch issue to manifest at all times rather than just on older software. :confused:
Click to expand...
Yeah, it really seems like just a software issue, but I have no idea what would be causing it. When I did MultiROM with 4.4 and Firefox OS (based on 4.4), Android wouldn't respond to touch on the base ROM. I've tried AOKP, CM, LuneOS, ColorOS, Sailfish, and stock. Maybe I'm just getting unlucky and there is one ROM that doesn't have this issue.
 
Okay, I finally broke down and opened up my nexus and went adventuring. Did the same with my Optimus G (which somehow got a cracked LCD) and connected the display and digitizer from my nexus to my Optimus G. Then, I connected my Optimus G's digitizer (which still works and isn't broken) to my nexus 4 and got through the LuneOS setup. I then reconnected my nexus 4's digitizer and it worked! Then my smart self did a reboot and now it doesn't work anymore. Hopefully disconnecting and reconnecting the digitizer is a solution. It's a pain, but it's a solution!
 
Holy carp! That's dedication!!

Glad you got it working though!

I still don't understand what would cause the software to act so dumb, but it's awesome that you were able to work past it. :thumbsupdroid:
 
codesplice said:
Holy carp! That's dedication!!

Glad you got it working though!

I still don't understand what would cause the software to act so dumb, but it's awesome that you were able to work past it. :thumbsupdroid:
Click to expand...
So am I. Now I really don't want to mess with it anymore. LuneOS Wi-Fi isn't working right, but I know the fix for when this happens again. :) It might be a thing that Google did too block 4.2 because of the unstated LTE that can be enabled in 4.2, but who knows. Probably not though.
 
achunt said:
It might be a thing that Google did too block 4.2 because of the unstated LTE that can be enabled in 4.2, but who knows. Probably not though.
Click to expand...

I've got LTE on mine with 5.0.1 - and have always had LTE thanks to some hybrid radios ;)

So I don't think that's the issue. Still mega-curious if you do figure it out though!
 
You must log in or register to reply here.
Back
Top Bottom