LightBlog

lundi 18 avril 2016

Potential fix for touchscreen dead zones after MHC19J

Background:

There is a well documented problem for some charger/device/voltage combos where the touchscreen will become unresponsive when connected to the stock charger. Ultimately the problem is with the charger design but it appears Google made some attempt to mitigate the problem with software in the MHC19J release.

See this thread for the power adapter touchscreen not responsive details
http://ift.tt/1qSB5A8

Unfortunately in doing so it seems they may have put out a Synaptics touchscreen firmware that introduced a brand new problem for folks who've never had any touchscreen problems before, affecting them during *normal* usage rather than the more isolated case of only during charging.

Basically the symptoms are you start getting dead zones when you leave your device untouched for a couple of seconds. You can cycle the screen on/off to reset the touchscreen but the problem eventually comes back again. It even occurs upon startup when you need to enter your lock code or pattern, making it difficult to get into your device.

My theory is Google put out a new synaptics touchscreen firmware that adjusted the sensitivity of the touchscreen to compensate for the "noise" being generated by the bad power adapters. The change may have been too aggressive as it seems to have had a side effect of being too insensitive for some folks' touchscreen variations resulting in dead zones.

See these threads for the touchscreen dead zones after MHC19J details
http://ift.tt/1qSB5Aa
http://ift.tt/1qSB5Ac

So normally you'd just flash an older factory image and everything would be back to normal. Unfortunately for touchscreen firmware, flashing older factory images will have no effect. Once you have the new touchscreen firmware it will stay in place until a newer one comes out. Thus you can't actually get back to "true" factory by flashing the MDA89E factory image.

There is a way you can force a touchscreen firmware flash if you are rooted. This will be described in the next post.

I do NOT know for sure if the touchscreen firmware is definitely the cause of this issue. The symtoms really point to it, but it is just a theory right now. I really don't have the flexibility to break my touchscreen to test a potential fix, so folks who are affected will need to try this out and confirm.


from xda-developers http://ift.tt/20Pz3gH
via IFTTT

Aucun commentaire:

Enregistrer un commentaire