Source :-Gadget360,android authority,xdadevlopers,9to5google,and Many More
Android 12
Google May Be Going to Unveil Andoird 12
Next Month Only For Devlopers
Credit: Robert Triggs / Android Authority
- Google could revive Android 11โs double-tap feature for Pixel phones.
- Codenamed Columbus, the gesture could be headed to Android 12.
When Google released the first developer preview for Android 11, it introduced a double-tap feature to Pixel phones. Essentially, you could tap the back of your Pixel twice to perform actions like launching the camera, snoozing alarms, controlling media playback, and more. Sadly the gesture never made it to the stable Android 11 release. Now, it looks like Google is ready to revive it and release an improved version.
According to information reviewed by 9to5Google, Google is working to include the double-tap gesture, codenamed Columbus, on Android 12. The publication reports that youโll be able to perform the following actions with it:
- Activate the Google Assistant
- Grab a screenshot
- Control media playback
- Open the notification shade
- Open the recent apps view
Smartphone audio is important, and hereโs what it takes to build the best
Looks like Columbus will be a handy feature for Pixel users and it would be great if Google could make it programmable for more actions. The good news is that the feature is reportedly becoming better than what it was on Android 11. Apparently, itโll only register firm taps to avoid any false touches. You should also be able to disable it altogether if you donโt fancy double-tapping the back of your phone.
You can expect to know more about double-tap and other Android 12 features very soon. Google released the first developer preview for Android 11 in February last year so we should be hearing about the new OS in just a few weeks. Until then, you can also check out our article about how to get the double-tap gesture on any Android phone.
Google adds a Restricted Networking Mode in Android 12
With the first Android 12 Developer Preview expected to go live next month, thereโs still a lot we donโt know about Googleโs next major OS update. Digging through the Android Open Source Project can only reveal so much given that the bulk of Android 12โs codebase isnโt public. Still, we sometimes see evidence for new Android features in AOSP, though theyโre often not very exciting. The latest feature we spotted, internally called โrestricted networking modeโ, sadly does not provide the configurable firewall that we were hoping to see, but it does have some interesting implications.
A handful of commits merged to AOSP describe the new restricted networking mode feature. Google has created a new firewall chain โ a set of rules that the Linux iptables utility follows to allow or block network traffic โ to support restricted networking mode. When this mode is turned on via a setting, only apps that hold the CONNECTIVITY_USE_RESTRICTED_NETWORKS permission will be allowed to use the network. Since this permission can only be granted to privileged system applications and/or applications signed by the OEM, this means that network access will be blocked for all applications installed by the user. Effectively, this means that youโll still receive push notifications from apps using Firebase Cloud Messaging (FCM), as these notifications are routed through the privileged Google Play Services app that holds the requisite permission, but no other app โ excluding a handful of other system apps โ can send or receive data in the background.
We donโt quite know where Google will place a toggle for restricted networking mode in Android 12. We know it can be toggled at runtime and programmatically queried via shell command, much like Androidโs Data Saver feature, but we donโt know if Google plans to let users make their own allowlist/blocklist of apps. It would be huge if Google added a user-facing settings page to restrict Internet access on a per-app basis so users donโt have to rely on apps like NetGuard that use Androidโs VPN API; thereโs nothing wrong with the way these apps operate, but thereโs little preventing them from being killed by bad OEM software.
