TK · Oct 14, 2013 at 07:00 pm

Thwart Those Nexus 7 (2013) Multi-Touch Issues

The Nexus 7 (2013) has been out since the late July, and many have enjoyed the device, which features numerous improvements over last year’s model. That said, many users have reported multi-touch issues right out of the box, and Google tried to address the issue back in August with the JSS15Q update. Sadly, this update didn’t fix the issue for all users, and it even brought on new touch issues for some who previously had none.

XDA Recognized Contributor sfhub came up with steps to fix the multi-touch issues for a purported 75% of the Nexus 7 (2013) users.

 Don’t you hate it when you have a workable system, then an update comes along which fixes something, let’s say GPS, but then your touchscreen goes down the tubes?

Never fear, I’ve put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units.

Since you’re going to be flashing images, you need to unlock the bootloader and root your device first. You must also be comfortable using ABD and fastboot.

To learn more about the process and lock in the working “fix” so that no future update impacts your screen responsiveness in the future, check out the original thread.


_________
Want something on the XDA Portal? Send us a tip!
Pulser_G2 · Feb 1, 2015 at 11:30 am · no comments

ITaaS – Identity Theft as a Service with FileThis

It's not often I look at a product or service and say "I really really hope this isn't real, and it's an elaborate fake". Alas, this day has come. It's time for a look at something which cropped up on my radar today, namely a service called FileThis. I won't do them the search-engine-ranking honor of providing a direct link to their site, but a quick search will find them, and their app on the Play Store and iTunes store....

XDA NEWS
Emil Kako · Jan 31, 2015 at 02:59 pm · 2 comments

Do You Prefer Physical or on Screen Buttons?

More and more smartphone manufacturers have been moving towards on-screen buttons, with Google really pushing for it over the physical button alternative. However, there are still a few OEMs (we're looking at you, Samsung) that have preferred to keep things a bit more traditional. Tell us which way you prefer and why.

DISCUSS
Pulser_G2 · Jan 31, 2015 at 02:08 pm · 1 comment

New AOSP Branch Details Potential Build System Upgrades?

While there are frequent unexplained changes and pushes to Google's AOSP repositories, an interesting-looking new branch has been pushed out recently, called "master-soong". Taking a look at the changes made to the manifest repository (which is used to specify the repositories to be downloaded when building Android), it appears there are some new repositories making an appearance. Of note here are new prebuilt repositories for Go, and Ninja. Go is a programming language, created by Google, which compiles to produce...

XDA NEWS