At this point, we've got some really amazing technology in our smartphones, and not just on the inside. Corning's continued work on their Gorilla Glass has made phone screens amazingly resistant to scratches, and as soon as someone manages to figure out how to make synthetic sapphire faster and cheaper, they'll be even better. But no matter how tough your screen is, it's still glass, and dropping it on the pavement is an almost inevitable recipe for a broken screen.
It has only been a couple of weeks since I wrote about the troubles with multi-touch (well, touch in general) on the 2013 Nexus 7. At the time, Paul Wilcox of Google's Product Support forum stated that the issue was being examined, and about a week later he confirmed that the JSS15Q update addressed the problem. While many people are reporting that the OTA has completely cleared up any touchscreen glitches that had been present, some people haven't seen any improvements, and still others are complaining that the problem has grown significantly worse.
Since the launch of the refreshed Nexus 7, there has been quite the rollercoaster of good and bad news. Some stores jumped the gun on the release date, which inspired Google to get an early start, as well. That was followed by the revelation that the device would never be able to support Google Wallet. Then came the really shocking news that factory images may never be published, which was almost immediately resolved after JBQ announced he was leaving his station with AOSP.
Touchscreen recoveries are all the rage these days. From TeamWin's TWRP, to unofficial variants of everyone's favorite, ClockworkMod Recovery. This morning, though, Koush himself took to Google+ to tease his very own blend of touchscreen controls for the recovery running on millions of devices.
While there's no release available for download yet, the work already looks promising. All the swiping, tapping, and touching we've all grown so used to is there.
TeamWin, the developers who originally developed CyanogenMod's WiMax compatibility, have been working on TWRP (Team Win Recovery Project) for a while now, and have just released the second iteration of the custom recovery.
TWRP 2.0's most notable new feature is without a doubt its touchscreen-centric GUI -- while this isn't a first, it certainly is extremely convenient: gone are the days of "scrolling" through lists with super-stiff volume buttons and selecting items with a click of the power button; with TWRP 2.0 you can simply tap and be there!
Shortly after the HTC Sensation was released, we covered a seemingly random issue with the touchscreen. Not all Sensation owners experienced this issue, and it's still relatively unknown what the exact cause of the problem is.
However, one of the theories formed on XDA is that it's a grounding issue on some devices. On others, though, the issue seems to be completely software related. If you can easily solve the problem by rebooting or a factory reset, then the fix outlined below will not work for you.
Having had the HTC Sensation in-hand for about a week, our unit has developed some troubling issues with its touchscreen. Namely, the panel often misses first presses, and also struggles with fast brushing movements.
The first issue results in great frustration when typing, as auto-correction of words does not work without the first letter. It also means you often have to tap several times on icons on the homescreen to launch an application.
A couple of days ago, French company 3qubits unveiled their unique take on what they imagined touchscreen keyboards of the future would look like. Starting with the notion that a full QWERTY layout could never fit properly on a handheld touchscreen device, they set about creating something entirely different. What they came up with is 8pen, which was released to the Android Market moments ago.