latest
Read update
- According to reports on reddit in an unofficial changelog posted by /u/ThisIsTechToday, DP2 fixes this problem. If it's driving you mad in the meantime, you've got two options. You can either move up to DP2 via the Beta Program, or wait for a stable update later that includes the fix.
Stop me if you've heard this one before: The Pixel 2 XL has another screen issue. Just a few days after we posted about the screen flashing when some owners unlock or lock their Pixel 2 XL, some of the device's owners are having difficulty with touch responsiveness near the edges of the screen. The good news is that Google has acknowledged the issue and will sort it out in a future OTA update.
At a post-Thanksgiving potluck yesterday, a friend and I were sharing our enthusiasm for Android with someone who recently switched to the platform. One of the first things I always tout in these conversations is Google Opinion Rewards, the app that gives you free Play Store credit in exchange for answering survey questions. As I was talking through it, I took out my phone and opened the app to show my reward history (a shade under $90 since 2014).
An altogether very well-received phone, the Pixel 2 XL has gotten mostly glowing reviews for its minimal bezels and standout camera. Its display, however, has been widely criticised for a host of reasons, including washed out colors, significant blue shift when viewed at an angle, lines of dead or colored pixels, graininess, and light bleed, just to name a few. Now, reports are surfacing of yet another issue with the screen — as if the current ones weren't already enough.
If you keep an eye on Android news, and particularly if you have any interest in Google's latest hardware, it won't be news to you that there's some controversy surrounding the screen on the Pixel 2 XL. While almost every other aspect of the phone has received universal praise, the LG-made POLED display panel has seen plenty of criticism.
Bugwatch season is in full swing here at AP and Google Voice is the latest culprit. It was only in June when we last heard of issues with the service, which was to do with broken notifications. This time people are reporting that they aren't receiving text messages to their Google Voice accounts.
Nougat had its fair share of Bluetooth issues, particularly on Google's Pixel devices, but you'd be forgiven for hoping that Oreo would avoid similar problems. Sadly, it seems that Pixel and Nexus owners are experiencing a number of different issues after installing the final version of Android 8.0, and Google is trying to gather user feedback in order to address the matter.
Not all app updates are created equal and while most usually fix bugs, add features, and make things better, faster, smoother, more stable, and more enjoyable, it is not the case of the latest Android Wear app update. Google giveth and Google taketh away.
The following is a guest post and an open letter to Google from Simply Applied, the makers of apps Sign and CritiCall. It was written by Chris H and Peter V, the developers on the Simply Applied team.
On September 14, Sprint revealed that an update to Android 2.3 (Gingerbread) was rolling out for the LG Optimus S. Seems like a good thing, right? Not so fast, actually - it turns out there are some fairly substantial bugs that weren't worked out before rolling out the update. Sprint is aware of the keyboard issue but has yet to acknowledge the other problems users seem to be experiencing, such as issues charging and using USB storage.
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.
Though Google may have fixed two infamous SMS issues via the recent Android 2.2.2 and 2.3.2 updates, it appears at least one bug is still unconquered. Namely, some users are reporting that when they tap on the "New Message" alert in the notification bar, all their SMS conversations get deleted.
Nothing's perfect, and it looks like the T-Mobile G2 is no exception - according to the latest batch of complaints coming from users who received their devices ahead of the scheduled release date, units are shipping with only 2GB of internal storage, whereas HTC's G2 website lists it at 4GB. Since this just so happens to be the same amount of internal storage offered by the G2's international cousin, the Desire Z, Engadget speculates that a mix-up may have occurred somewhere along the line, a theory which, I am sure, is not far off. Hopefully T-Mobile will be able to replace these phones or provide larger microSD cards to make up for it, because if there's one thing us Android fans do well, it's causing a riot.