The Pixel 2 XL has another screen issue: unresponsive edges

It looks like Google still isn’t done fielding complaints about the Pixel 2 XL’s display. While some users are experiencing premature screen burn-in and seeing a bluish tint, others are apparently having trouble with its responsiveness. Comments posted on the Pixel 2 community website have revealed that some units are having issues getting their phones to register touches near the edges of the screen. One poster even conducted a test and found that while the edges on his display can recognize swipes just fine, they can’t always recognize taps.

Here’s a video of the experiment:

According to Android Police, this happens because the device’s accidental touch protection feature is just bit too effective. The good news is that it’s a software issue, and Google is already working on a fix. Orrin, a Pixel 2XL Community manager, posted on the thread to inform people that the Pixel team is already investigating and addressing the problem in an upcoming over-the-air update.

In an effort to preempt similar complaints about bluish or greenish tinted screens and burn-ins, Apple recently updated its support page to explain that those are perfectly normal for OLED displays like the iPhone X’s and Pixel 2 XL’s. Nevertheless, iPhone X’s screen seems to come with its own set of issues. Some of them have a nasty green line going down their edges, while others stop responding to touches in cold temperatures.

Source: Android Police

Engadget RSS Feed

Recommended Reading: Netflix has another winner with ‘GLOW’


Feeling the ‘GLOW’
Mairead Small Staid,
The Ringer

Despite recent news of Netflix cancelling a few of its high-profile originals, the streaming service hasn’t missed a beat. One of its most recent, GLOW, debuted last week and critics seem to agree that it’s worth your time. Heck, we even recommended it in our monthly roundup. The Ringer offers a look at the series and the actual women’s wresting promotion from which the show gets its name.

How HBO’s ‘Silicon Valley’ Built ‘Not Hotdog’ with Mobile TensorFlow, Keras and React Native
Tim Anglade, Hackernoon

If you’ve been wondering how that ridiculous Not Hotdog app from Silicon Valley came to be, well, wonder no more.

The iPhone Was Inevitable
Alexis C. Madrigal, The Atlantic

The idea of putting a handheld computer in your pocket came about long before 2007.

How ‘Game of Thrones’ Has Changed TV For the Better
Rob Sheffield, Rolling Stone

HBO’s pride and joy broke the mold for a TV show in so many different ways it will be hard for other series not to take note.

This Engineer Is Using Old Cell Phones to Stop Illegal Logging
Jeremy Deaton, Popular Science

The story of a trip to Indonesia and one engineer’s idea to re-purpose old tech to stop illegal logging.

Engadget RSS Feed

The FBI wants to crack another iPhone after Minnesota stabbings

The FBI and Apple might be headed for another fight over the case of a locked phone. Last night, FBI special agent Rich Thorton confirmed that the agency is trying to crack an iPhone belonging to Dahir Adan, a 20-year-old Somali immigrant who stabbed 10 people in a Minnesota mall last month. Per Wired, Thorton said the bureau was already sifting through some “780 gigabytes of data from multiple computers and other electronic devices,” but unlocking Adan’s phone could shed valuable light on why he did what he did and help figure out who (if anyone) helped him on his path.

But cracking the phone isn’t a matter of course — the FBI’s currently weighing its “legal and technical” options to get inside the unspecified device. A lot of the FBI’s work here depends on what kind of iPhone they recovered, too — the introduction of iOS 8 two years ago meant not even Apple could decrypt the contents of a locked device running that software.

“Unlike our competitors, Apple cannot bypass your passcode and therefore cannot access this data,” the company wrote in 2014, referring to photos, messages, contacts and more. “So it’s not technically feasible for us to respond to government warrants for the extraction of this data from devices in their possession running iOS 8.”

Still, that didn’t stop the FBI cracking from iPhone 5c owned by Rizwan Farook, one of the San Bernardino shooters who killed 14 people in late 2015. The road to that crack was a winding one — the FBI originally pushed Apple for support to unlock the iOS 9-powered device, and got court orders compelling the company to assist. Apple resisted, but the FBI ultimately found a way to crack Farook’s iPhone without Apple’s assistance, a move that apparently cost the bureau a tidy sum. At the time, FBI director James Comey said he hadn’t decided if the bureau would reveal that crucial backdoor to Apple out of concerns it would be closed.

While the FBI might still have that particular ace up its sleeve, the process of sifting through Adan’s data might be way more difficult. Farook’s iPhone 5c lacked the secure enclave that was baked into newer models with the A7 chipset and beyond. It’s unclear at this point how much progress the FBI has made — only time will tell if it’ll try to force Apple to help somehow, or how Apple will response if the government comes knocking.

Source: Wired

Engadget RSS Feed