While the experience isn't felt across the board, many OnePlus One owners have been plagued by touchscreen issues since making the decision to never settle. As a result, the company has pushed out update after update aimed at alleviating an issue that seems to have a tendency to resurface.
One of the more persistent and frustrating issues with the OnePlus One has been its touchscreen, which saw a spat of problemsandfirmware fixes late last year. A software update in November seemed to have fixed the glitches, but in the last few weeks dozens of users on the official OnePlus forums have reported a resurgence of touchscreen issues. Perhaps it has something to do with the new Android updates, perhaps it's because of the rising temperatures as spring hits the northern hemisphere.
LG continued the resolution war last spring when it announced the LG G3 with a 2560x1440 LCD. The display had good sharpness, but the brightness and colors were not great. LG says it has a new and improved 5.5-inch LCD ready to go, and it's going to be used in its "forthcoming flagship smartphone," meaning the G4.
The new panel has the same 1440p resolution for a whopping 538 pixels per inch.
Since launch, some OnePlus One owners have encountered issues with the phone's touchscreen. The complaints center around the display being unresponsive, causing it to miss certain touches and provide a generally frustrating typing experience. Sometimes it resulted in taps while dragging or swiping.
Now a firmware upgrade is in testing that takes care of this problem entirely. It's expected to go out to users soon in an upcoming over-the-air update.
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.
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.