With the release of Android Q Beta 5, Google announced to host a Reddit AMA to answer our burning questions about Android Q and almost everything else with Android. This AMA took place this afternoon, and the Android development team provided entertaining and interesting information about Android Q and the topics potentially related to Android R, among others.
In the early versions of Android Q Beta, it was possible to enable a handy, integrated screen capture interface with just a slight change of settings. Unfortunately, this paperless recorder was short-lived and disappeared in the third beta outside a change over ADB.
A redditor asked when the built-in screen capture should be available again outside of "super-sketchy apps" said the product user for the Android interface, Allen Huang, that the screen capture is only part of what we for Android R should expect.
Given Dave signed us up for scrollable screenshots AND how many times users make screenshots – we'll look at how we can improve the entire screen – [X] for R. We're certainly of the opinion that these feature types should be core elements of the operating system.
Dark Theme Enhancements
One of the hottest themes of Android Q was the support for native dark mode. Of course, it was used several times in today's Android Q AMA version. In particular, some editors asked if the dark mode could be triggered automatically.
A model that Google had previously considered for switching to and out of Dark Mode was based on the time of sunset and sunrise, accurate location data. It is considered to allow users to set the dark mode based on the time of day, however this is apparently not possible in stock Android, Charmaine D & # 39; Silva, shared an interesting statistic. You may recall that Google made a significant change last year, restricting Android call and text log permission to almost all of the primary phone call or SMS app on your device. While this change was controversial at the time, D & # 39; Silva shared the benefits of this privacy change:
For example, last fall, we introduced the SMS and Call Log policies, which restrict the types of apps that can request these permissions. As a result, the number of apps accessing this sensitive information has dropped more than 98% today. The vast majority of developers were able to move to an alternative or eliminate minor features.
Open Source Wear OS?
As you may know, Google's Wear OS, once called Android Wear, is heavily based on on Android. However, unlike Android, Wear OS is not an open source operating system meaning OEMs and developers can not read the code to gain a deeper understanding of the system or even make changes.
When asked if Wear The operating system will always be open source. Jeff Bailey, Tech Lead Manager of the Android Open Source project, had "nothing new to share at the time".
Changes to the Future Development of Android
As you may know, Google has a public bug / issue tracker that lets users and developers share problems with Android and certain other Google products more or less directly with Google can. However, while some of the published issues resonate with the public, many are ignored for months or confusingly denied – this was the case with the original request to scroll screenshots earlier this year.
Affected redditor has raised the possibility that Google will take issues that are addressed by developers and the public more seriously in the future. Jeff Bailey first addressed this question by pointing out that the Issue Tracker has a high potential for overpowering as more and more tech-savvy people become aware of it. However, he did not conclude the idea on the grounds that it is possible that some teams will work directly with "external" bugs in the future.
Our developers are currently working on internal bugs only. There are some teams who have expressed interest in direct external work and we are trying to figure out how to do that.
For more news, visit 9to5Google on YouTube: