If you're a developer, you may have noticed one bug in the latest Android 7.0 and its various Developer Preview releases: the option to "Show CPU usage" under Developer Options in the settings only shows the com.android.systemui process.
This means that if you're using the CPU usage overlay to monitor whether any of your app's processes are waking up at the right time, and not waking up when they shouldn't, the overlay is pretty much useless to you now. All you see is the systemui process and its usage and there's no detailed list of all the running processes and their load like before. Read More
Earlier this month, we reported an issue with both Chrome Beta and Dev on Nougat. Despite both apps being installed on your phone, they didn't show up in the list of My apps & games in the Play Store, which meant that they were never automatically updated and you had to manually search for them, open their listing, and then see if an update was available or not to download it.
The issue, as we rightfully suspected, was related to the change of the signature keys in Chrome. As Googler Alexander Mineer explained to us in the comments on the original post, the keys had to be changed due to Chrome's new ability to act as a WebView provider in Nougat. Read More
Calling all hackers and security researchers: Google wants to pay you money. Quite a lot, in fact. The top prize for finding a new critical flaw in Android in the new Project Zero Prize competition is a whopping $200,000, with the second prize at $100,000 and $50,000 split among additional entrants. The contest is being run by Project Zero, the company's own internal team of security researchers that documents critical flaws and bugs in wide-reaching software. Read More
If you own a Nexus device and have updated to Android Nougat, and you use Chrome Beta or Chrome Dev, you may have noticed something. Alright, maybe you didn't notice it because you don't have the eagle eye of Artem. Regardless, the issue is there and it's not a matter of #ArtemsLuck: I was able to replicate it on my Nexus 5X too.
Both Chrome Beta and Chrome Dev do not appear under My Apps in the Play Store on devices running Nougat. Even when they're installed on your device, you won't see them in the Installed list, which means that they won't detect updates and download and install them automatically when all of your apps do. Read More
And here's reason number 249 not to install beta software onto a device that's critical to your everyday life. Android Auto users who have upgraded their Nexus phones to the latest version of the Android N Developer Preview are reporting that Google Maps navigation is no longer working in the car interface. (Remember, Android Auto isn't an independent system - it needs a powered-up and connected phone in order to work.) The Maps app is simply crashing on launch and returning users to the Auto home screen. Read More
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
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.
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