Android Lollipop introduced screen pinning: a way for you to lock your device into one app until a specific shortcut was tapped to take you out of it and let you switch to something else.
In Lollipop, a screen is pinned by going to Recents and tapping the green pin button at the bottom right of any app card, and it is unpinned in one of two ways: short tapping Recents and Back simultaneously if no Accessibility service is enabled in your Settings at all, or long tapping Recents if at least one Accessibility service is switched on. That created several problems:
- the confusion over which shortcut to use depending on whether you have some Accessibility service enabled,
- the automatic switch to Recents each time you unpinned (you were pressing Recents after all...), which meant that you had to tap the app again to go back to using it,
- and more recently, the conflict with Multi-Window on N, which requires the same long-tap on Recents action to get triggered.
Google's commitment to Android in the form of monthly updates for its own branded hardware is pretty great... until it's not. That's the case with the May security and stability update for the top-of-the-line Pixel C tablet, which has created some serious headaches for owners. Some (but by no means all) owners of the Pixel C are reporting more or less random reboots of the tablet, usually occurring every five to thirty minutes when the Pixel C is off its charger. Read More
If you've flashed Android N's second developer preview and ventured into the battery section of the settings, you may have noticed something odd happening with the History details screen (the one what shows up when you tap the graph) which normally has the expanded battery drain graph with the different components' usage. The latter part is nowhere to be seen in Dev Preview 2.
The graph is still there, but it's stretched across the screen and there's none of the information below it. No cellular signal, no GPS, no Wi-Fi, no device awake, no screen on, and no charging. All of it is poof, gone. Read More
An update to Google's Messenger application rolled out yesterday afternoon. Like a lot of other updates lately, this one appears to be centered around clearing up bugs and issues rather than adding new features. For regular travelers or those that have some compatibility issues with their local carriers, there is now an option to override the automatic country detection the app currently performs. Those users on Android N can also look forward to a fix for a pretty critical bug that could cause Messenger to crash with a simple YouTube link.
Bug Fix: YouTube Links No Longer Crash Android N
For those people living on the edge with the Android N Developer Preview running on their primary (or only) phone, there can be some pretty critical bugs that tend to break things in really unexpected ways. Read More
Well this is frustrating. The bug that caused the "Until Next Alarm" function of Android's Do Not Disturb mode to disappear, which manifested itself in late December on a number of Android phones running Lollipop 5.1 and later, is back. The timing of the month seems more than coincidental. Since the problem manifested late in December, presumably Google didn't have time to implement a fix in the latest round of scheduled Android updates.
It looks like this will keep occurring at the tail end of the month until Google fixes it - hopefully in the latest round of Nexus updates. Read More
Since the release of Android 6.0 Marshmallow, Gmail users have been reporting some syncing problems on their app that appeared simultaneously with their update to Android's latest flavor. (Very few users mentioned being affected on Lollipop, but it's worth pointing out.) The problems seemed to be divided in two categories: one that specifically stopped Hotmail accounts from being synced inside the Gmail app and another that caused a lot of delays in syncing and notifications regardless of the account type.
Gmail 5.10, which started being pushed to users on January 20, fixes the first issue. A Google employee explained on the corresponding Help Forums thread:
I can confirm that upgrading to the Gmail Android app 5.10 should fix this issue, however it's rolling out slowly so is only available for a small number of people right now.
If you've been experiencing some intermittent problems getting timely email alerts on your Nexus phone, you're not alone. According to lengthy threads on both Google's official Nexus Help Forum and the AOSP issue tracker, quite a few Android users running Android 6.0 and later builds on Nexus hardware are seeing similar issues. The problem seems to result in late or missing notifications for Gmail and Inbox, as well as less frequent alerts for other apps, and less definable errors with some Google services like Google Now.
The issue tracker entry has been starred by 140 people at the time of writing, indicating a fairly widespread problem, though it isn't universal. Read More
What the hell? After many users were happy to see the "until next alarm" option return to Android's somewhat nebulous "Do Not Disturb" mode after upgrading to the cutting-edge 6.0.1 build of Marshmallow, several have now reported that the feature is once again gone. What's going on here?
Android Police readers have alerted us to the odd change, and Android users on Reddit are also scratching their heads. Read More
Before YouTube Red launched at the end of October, a number of folks signed up to take part in the YouTube Music Key beta. Starting last week, a number of them have been getting hit by a particularly frustrating bug. They've been switched to YouTube Red, but they've lost access to their Google Play Music subscriptions. To make matters worse, YouTube Red charged them $7.99 as though everything were in working order. Read More
Are the people you call with your shiny new Nexus 6P saying that they can't hear you? Then you might want to check out several threads on the Google Product Forum and XDA-Developers. A common problem among early adopters seems to be weak and spotty voice quality - that's the voice of the Nexus 6P owner, not the other call party. At the time of writing, several dozen owners across the two sites are reporting very similar problems, both in standard call mode and when using the speakerphone. Google representatives have responded on the official forum, and say that they're looking into it. Read More