Google started offering free VPN by Google One access starting with the Pixel 7, but they’re taking things a bit further with the Pixel 8 series!
VPN by Google One will now appear as a “built-in” VPN under Settings > Network & Internet > VPN. This will improve discoverability of the VPN that Google provides freely to Pixel 8 users and also make controlling its settings feel more native.
Under the hood, this integration is made possible by a new pre-installed app called
VPN by Google One will now appear as a “built-in” VPN under Settings > Network & Internet > VPN. This will improve discoverability of the VPN that Google provides freely to Pixel 8 users and also make controlling its settings feel more native.
Under the hood, this integration is made possible by a new pre-installed app called
AdaptiveVPN, system overlays that flip the config_advanced_vpn_enabled and config_pixel_vpn_enabled flags, and new code in settings added in Android 13 QPR1.👍37🔥10❤🔥4🤡4😁1😱1
Android 14, at least its source code, was supposed to be released on September 5 instead of today. Don’t believe me? The draft for the “Android 14 is live in AOSP” article actually linked out to another blog post with this URL: feature-drop-september-2023. So why the delay?
According to a source, Google discovered a nasty memory leak that caused performance issues. This issue was actually fixed in the last-minute Android 14 Beta 5.3 release that rolled out on September 5.
The relevant line from the Beta 5.3 changelog is this: “Fixed issues with SurfaceFlinger that were causing a loss in system performance.” Now that the source code is going live, we’ll be able to find out what this bug was about.
Also, I was partially wrong about something I said last month: OEMs (at least some of them) were informed about the delay. Their biggest partners were told about this, which makes sense since it affects their own release schedules.
According to a source, Google discovered a nasty memory leak that caused performance issues. This issue was actually fixed in the last-minute Android 14 Beta 5.3 release that rolled out on September 5.
The relevant line from the Beta 5.3 changelog is this: “Fixed issues with SurfaceFlinger that were causing a loss in system performance.” Now that the source code is going live, we’ll be able to find out what this bug was about.
Also, I was partially wrong about something I said last month: OEMs (at least some of them) were informed about the delay. Their biggest partners were told about this, which makes sense since it affects their own release schedules.
👍43🔥19👏1
This media is not supported in your browser
VIEW IN TELEGRAM
What happened to Android’s predictive back gesture? We finally have an answer!
ICYMI: Android 13 started work on a predictive back gesture system that would let you see whether the back gesture would exit the app back to the home screen. This was expanded in Android 14 to let you see what screen the back gesture would take you to within the app or whether the gesture would take you to the previous app in the back stack. Android 14 also added a new back gesture arrow icon.
Now, the issue is that these back-to-home, cross-activity, and cross-task system animations aren’t enabled by default. You have to go to Settings > System > Developer options and toggle “predictive back animations” to enable them.
It’s not as if apps get to support the predictive back gesture system for free, though. The amount of work that’s required to support it depends on the app, but Google has been working to add robust library support for the feature. It’s enabled in the Material Design Components library for BottomSheets, SideSheets, and SearchBar on v1.10.0+ as well as for Compose with v1.8.0-alpha07 of the Jetpack Activity library.
Google is giving developers more time to adapt their apps to the predictive back gesture system, so we should hopefully see it be enabled by default in Android 15!
ICYMI: Android 13 started work on a predictive back gesture system that would let you see whether the back gesture would exit the app back to the home screen. This was expanded in Android 14 to let you see what screen the back gesture would take you to within the app or whether the gesture would take you to the previous app in the back stack. Android 14 also added a new back gesture arrow icon.
Now, the issue is that these back-to-home, cross-activity, and cross-task system animations aren’t enabled by default. You have to go to Settings > System > Developer options and toggle “predictive back animations” to enable them.
It’s not as if apps get to support the predictive back gesture system for free, though. The amount of work that’s required to support it depends on the app, but Google has been working to add robust library support for the feature. It’s enabled in the Material Design Components library for BottomSheets, SideSheets, and SearchBar on v1.10.0+ as well as for Compose with v1.8.0-alpha07 of the Jetpack Activity library.
Google is giving developers more time to adapt their apps to the predictive back gesture system, so we should hopefully see it be enabled by default in Android 15!
👍70💩25😐18👏2❤1
The Pixel 8 series launches with Android 14 and will get 7 years of software support, including annual OS updates, monthly security updates, and quarterly Pixel Feature Drops. This means they'll be supported till 2030.
I can't emphasize enough how big of a deal this is.
Google didn't offer much detail on how they were able to expand software support so significantly (up from 3 years OS + 5 years security on previous Pixels). They only said this: "to make this possible, we’ve been working to secure long-term commitments from partner teams, and put the necessary testing infrastructure in place."
Also, Google basically confirmed that you shouldn't expect updates to roll out on the same day as the Android Security Bulletin (they've missed that target for a while now anyway).
"We also dug into how we can deliver the highest quality, best tested updates to Pixel users on a consistent basis. As part of this effort, our security updates, bug fixes and feature updates won’t roll out on a specific day each month. Instead, we’ll deploy updates as soon as they’ve completed the necessary tests to ensure they improve the experience for all Pixel customers."
I can't emphasize enough how big of a deal this is.
Google didn't offer much detail on how they were able to expand software support so significantly (up from 3 years OS + 5 years security on previous Pixels). They only said this: "to make this possible, we’ve been working to secure long-term commitments from partner teams, and put the necessary testing infrastructure in place."
Also, Google basically confirmed that you shouldn't expect updates to roll out on the same day as the Android Security Bulletin (they've missed that target for a while now anyway).
"We also dug into how we can deliver the highest quality, best tested updates to Pixel users on a consistent basis. As part of this effort, our security updates, bug fixes and feature updates won’t roll out on a specific day each month. Instead, we’ll deploy updates as soon as they’ve completed the necessary tests to ensure they improve the experience for all Pixel customers."
❤91🤯19👍14🫡8🔥5🏆4😱3🥰1
Face Unlock on the Pixel 8 series is now classified as a Class 3 (formerly Strong) biometric, which allows it to be used for BiometricPrompt (ie. authenticate within apps) and the Android Keystore.
This means you'll be able to use the Pixel 8's Face Unlock in banking apps and for payment apps like Google Wallet.
By the way, if you want to learn more about how biometric sensors are classified and how Google enforces/verifies these classifications, I made a post for subscribers that dives into this.
This means you'll be able to use the Pixel 8's Face Unlock in banking apps and for payment apps like Google Wallet.
By the way, if you want to learn more about how biometric sensors are classified and how Google enforces/verifies these classifications, I made a post for subscribers that dives into this.
👍61🔥29👏11🥱4❤2
Besides all the new features in Android 14 I already talked about, here are some of the other new features for Pixels in the October 2023 Pixel Feature Drop:
* Dual Screen interpreter mode in Google Translate for the Pixel Fold
* You can now choose to automatically open RAW images in your favorite RAW editor directly from Google Photos. Works on Pixel 6 and newer phones as well as Pixel Tablet. (Below image via Nail Sadykov.)
* Pixel 6 and newer phones as well as Pixel Tablet will now notify you if your power adapter or USB cable is charging your device slowly or not at all.
* Battery Saver is getting a new design in Android 14 that lets you see exactly what is being restricted on your Pixel to extend battery life and select essential apps that can continue to run when you toggle Extreme Battery Saver. You can now also turn on (Extreme) Battery Saver with automatic notifications at 10% and 20%.
* Google Kids Space on the Pixel Tablet now has a "streamlined navigation bar" that makes it easier for kids to explore, switch apps, and return to the home screen. (This is the "kids mode" navigation bar I discovered in Android 13 and which Google accidentally showed off in marketing materials back in June.)
* Dual Screen interpreter mode in Google Translate for the Pixel Fold
* You can now choose to automatically open RAW images in your favorite RAW editor directly from Google Photos. Works on Pixel 6 and newer phones as well as Pixel Tablet. (Below image via Nail Sadykov.)
* Pixel 6 and newer phones as well as Pixel Tablet will now notify you if your power adapter or USB cable is charging your device slowly or not at all.
* Battery Saver is getting a new design in Android 14 that lets you see exactly what is being restricted on your Pixel to extend battery life and select essential apps that can continue to run when you toggle Extreme Battery Saver. You can now also turn on (Extreme) Battery Saver with automatic notifications at 10% and 20%.
* Google Kids Space on the Pixel Tablet now has a "streamlined navigation bar" that makes it easier for kids to explore, switch apps, and return to the home screen. (This is the "kids mode" navigation bar I discovered in Android 13 and which Google accidentally showed off in marketing materials back in June.)
👍60👏5
Google touts the ability to use your phone as a webcam as an Android 14 feature.
However, the DeviceAsWebcam app wasn't in any of the Android 14 DPs/Betas and was only added in the Android 14 QPR1 beta. This means that the feature will likely only be available in the upcoming December 2023 Pixel Feature Drop.
As I previously said, the DAW app isn't included by default when compiling the initial Android 14 release from source, but the source code for the app is there. It's built by default when compiling Android 14 QPR1, though.
The Android 14 landing page says that "you can soon use your Android phone as a beautiful webcam on a video call simply by connecting a USB cable between your Android phone and any Windows, MacOS or Chrome OS computers" (emphasis mine). The footnote says that this is "available on compatible devices in available countries coming soon."
Compatible devices right now include the Pixel 6 and Pixel 7 series on the Android 14 QPR1 beta. I don't know if the Pixel 8 on the UD1A build has it, nor do I know if the Pixel 6/Pixel 7 stable update rolling out today has it either. I also don't know why it's seemingly limited by country? That doesn't make much sense to me.
Here's the source code for Android 14's webcam app.
However, the DeviceAsWebcam app wasn't in any of the Android 14 DPs/Betas and was only added in the Android 14 QPR1 beta. This means that the feature will likely only be available in the upcoming December 2023 Pixel Feature Drop.
As I previously said, the DAW app isn't included by default when compiling the initial Android 14 release from source, but the source code for the app is there. It's built by default when compiling Android 14 QPR1, though.
The Android 14 landing page says that "you can soon use your Android phone as a beautiful webcam on a video call simply by connecting a USB cable between your Android phone and any Windows, MacOS or Chrome OS computers" (emphasis mine). The footnote says that this is "available on compatible devices in available countries coming soon."
Compatible devices right now include the Pixel 6 and Pixel 7 series on the Android 14 QPR1 beta. I don't know if the Pixel 8 on the UD1A build has it, nor do I know if the Pixel 6/Pixel 7 stable update rolling out today has it either. I also don't know why it's seemingly limited by country? That doesn't make much sense to me.
Here's the source code for Android 14's webcam app.
👍42❤12
Ohh, here's the actual statue for Android 14, not the astronaut one that was previously spotted!
Can't wait to see the statue for Android 15 Vanilla Ice Cream 😁
Photo credits: Dave Burke on Twitter
Can't wait to see the statue for Android 15 Vanilla Ice Cream 😁
Photo credits: Dave Burke on Twitter
👍64🔥17😁4😱4🤔3
BEFORE YOU UPDATE TO ANDROID 14, PLEASE DO THE FOLLOWING!
I want to know how long it takes for your device to apply the update. I'm ESPECIALLY interested in seeing how long it takes for it to "optimize apps". So after the Android 14 update finishes downloading, tell me how long it takes to install the update and then optimize apps.
I don't need an exact time, a rough estimate is fine! So in summary, I need to know:
a) How long it took to "optimize apps"?
b) What device you have.
c) How many apps you have installed.
I'm trying to collect some data so we can get Google to speed up the OTA update process (I've heard some folks at Google are interested in this as well, but they need a push to get the ball rolling!)
I want to know how long it takes for your device to apply the update. I'm ESPECIALLY interested in seeing how long it takes for it to "optimize apps". So after the Android 14 update finishes downloading, tell me how long it takes to install the update and then optimize apps.
I don't need an exact time, a rough estimate is fine! So in summary, I need to know:
a) How long it took to "optimize apps"?
b) What device you have.
c) How many apps you have installed.
I'm trying to collect some data so we can get Google to speed up the OTA update process (I've heard some folks at Google are interested in this as well, but they need a push to get the ball rolling!)
👍93❤17🔥5👌2
I wonder if Assistant with Bard (1:04:13 to 1:08:31 in the keynote) will be what Android 14 QPR1's new screen search gesture will launch. It would actually make a lot of sense given what Google showed it can do.
👍28🔥8❤3❤🔥1
Mishaal's Android News Feed
Google touts the ability to use your phone as a webcam as an Android 14 feature. However, the DeviceAsWebcam app wasn't in any of the Android 14 DPs/Betas and was only added in the Android 14 QPR1 beta. This means that the feature will likely only be available…
chrome_2023_10_04_13_51_2315.jpg
42 KB
Okay, I was wrong. The Manifest for the android14-release branch includes the DeviceAsWebcam app. If you update your Pixel 6 or Pixel 7 to the stable Android 14 release, let me know if you see the webcam feature!
Edit: A Pixel 6a, 7, and 7 Pro user in the TG group said they don't see it.
Edit: A Pixel 6a, 7, and 7 Pro user in the TG group said they don't see it.
👍21🤔3
The Pixel Watch 2 launches with Wear OS 4 based on Android 13, which brings support for the new Watch Face Format, enhanced Tile support, cloud backup and restore, and seamless data transfer to a new phone!
Watch Face Format is a declarative XML format that lets you design the appearance and behavior of watch faces. No executable code is involved in making a watch face. Wear OS handles the logic of rendering the watch face, so you don't have to worry about code optimizations or battery performance.
Version 1.2 of the Jetpack Tiles library adds support for platform data bindings and animations.
I'm most excited for cloud backup and store and seamless data transfer, though.
Cloud backup and restore: "On devices that support cloud backup—including Pixel Watch 2 and Pixel Watch—users can transfer data from one Wear OS watch to another using a cloud backup and restore process. You can customize the set of files in your app that the system should include in a cloud backup, so that users only restore app data that’s meaningful to them."
Seamless data transfer: "Additionally, Wear OS 4 allows users to transfer their watch to a new phone without needing to perform a factory reset on the watch. They complete this process when setting up the new phone, as shown in the following flow below."
Other changes:
* Wear OS 4 removes the system UI for granting the SYSTEM_ALERT_WINDOW permission, which was available on some devices running Wear OS 3 and lower.
Wear OS 4 will arrive for the first-gen Pixel Watch later this year, and it's already available on Samsung's Galaxy Watch 4 and later. The updated Wear OS 4 emulator available through Android Studio Hedgehog doesn't support native 32-bit code, as Google wants developers to prepare for upcoming 64-bit only devices.
————————————————————————
Prepare your app for behavior changes in Wear OS 4 | Explore features in Wear OS 4
Watch Face Format is a declarative XML format that lets you design the appearance and behavior of watch faces. No executable code is involved in making a watch face. Wear OS handles the logic of rendering the watch face, so you don't have to worry about code optimizations or battery performance.
Version 1.2 of the Jetpack Tiles library adds support for platform data bindings and animations.
I'm most excited for cloud backup and store and seamless data transfer, though.
Cloud backup and restore: "On devices that support cloud backup—including Pixel Watch 2 and Pixel Watch—users can transfer data from one Wear OS watch to another using a cloud backup and restore process. You can customize the set of files in your app that the system should include in a cloud backup, so that users only restore app data that’s meaningful to them."
Seamless data transfer: "Additionally, Wear OS 4 allows users to transfer their watch to a new phone without needing to perform a factory reset on the watch. They complete this process when setting up the new phone, as shown in the following flow below."
Other changes:
* Wear OS 4 removes the system UI for granting the SYSTEM_ALERT_WINDOW permission, which was available on some devices running Wear OS 3 and lower.
Wear OS 4 will arrive for the first-gen Pixel Watch later this year, and it's already available on Samsung's Galaxy Watch 4 and later. The updated Wear OS 4 emulator available through Android Studio Hedgehog doesn't support native 32-bit code, as Google wants developers to prepare for upcoming 64-bit only devices.
————————————————————————
Prepare your app for behavior changes in Wear OS 4 | Explore features in Wear OS 4
👍36❤7👏2
Since I'm not gonna have my own Pixel 8 for a while, I might as well put this out there so someone else can test it ASAP:
You might be able to enable DisplayPort Alternate Mode (ie. display output over USB-C) if you root the device. That's because it seems to be disabled at a software, not hardware, level unlike previous Pixels.
You can see here from a dump of husky (code-name for the Pixel 8 Pro) that the property
This property is read by the
Thus, if you root the phone and override this property (eg. via
There's even a separate display config for when DisplayPort is enabled, under
Anyway, if you manage to get display output working using what I said, please let me know! If it does work, then that means Google can enable display output via an OTA update.
I'm aware that current carrier store models don't support display output, and that some are reporting that it doesn't as well (eg. below). However, it's true that they don't support it right now, but that doesn't mean it can never be enabled.
You might be able to enable DisplayPort Alternate Mode (ie. display output over USB-C) if you root the device. That's because it seems to be disabled at a software, not hardware, level unlike previous Pixels.
You can see here from a dump of husky (code-name for the Pixel 8 Pro) that the property
persist.vendor.usb.displayport.enabled is set to 0.This property is read by the
init.zuma.usb.rc file, which is the USB config file for the Tensor G3-series devices (zuma). Since this property is set to 0, then DisplayPort is disabled.Thus, if you root the phone and override this property (eg. via
setprop persist.vendor.usb.displayport.enabled 1), then this may be enough to enable DisplayPort Alternate Mode.There's even a separate display config for when DisplayPort is enabled, under
/vendor/etc/displayconfig/display_port_0.xml. Anyway, if you manage to get display output working using what I said, please let me know! If it does work, then that means Google can enable display output via an OTA update.
I'm aware that current carrier store models don't support display output, and that some are reporting that it doesn't as well (eg. below). However, it's true that they don't support it right now, but that doesn't mean it can never be enabled.
👍43👎2❤1