Here are my first impressions of the new ROG Phone 8 Pro:
* It feels so much lighter, thinner, and better in hand than the previous models!
* The bezels are also much smaller, and the back has this nice textured layer that you can see but not feel underneath the glass.
* The corners are not nearly as sharp anymore! Holding the phone on a corner no longer hurts my palms.
* There's a neat AI wallpaper feature like on the Pixel 8 series. Like Google's version, you can choose from a few preset topics and also edit the prompt a bit (change the background, tone, and "inspiration"). Unlike Google's version, ASUS' AI wallpaper generator runs on-device using a Stable Diffusion model on the Snapdragon 8 Gen 3. Here's a video demo.
* Another neat use of AI on the ROG Phone 8 is semantic search. This also runs on-device and helps you search through your photos, settings, and apps. Here's a video demo.
* If you aren't a fan of the AOD but still like getting subtle notification alerts, the new "custom effect" option is for you. This displays notification icons on the AOD in the top left when the phone is charging. The ROG Phone 8 doesn't have a notification LED anymore, so this is useful if you don't want to use the full AOD.
* Contrary to some rumors, the AirTriggers feature hasn't been removed.
* It feels so much lighter, thinner, and better in hand than the previous models!
* The bezels are also much smaller, and the back has this nice textured layer that you can see but not feel underneath the glass.
* The corners are not nearly as sharp anymore! Holding the phone on a corner no longer hurts my palms.
* There's a neat AI wallpaper feature like on the Pixel 8 series. Like Google's version, you can choose from a few preset topics and also edit the prompt a bit (change the background, tone, and "inspiration"). Unlike Google's version, ASUS' AI wallpaper generator runs on-device using a Stable Diffusion model on the Snapdragon 8 Gen 3. Here's a video demo.
* Another neat use of AI on the ROG Phone 8 is semantic search. This also runs on-device and helps you search through your photos, settings, and apps. Here's a video demo.
* If you aren't a fan of the AOD but still like getting subtle notification alerts, the new "custom effect" option is for you. This displays notification icons on the AOD in the top left when the phone is charging. The ROG Phone 8 doesn't have a notification LED anymore, so this is useful if you don't want to use the full AOD.
* Contrary to some rumors, the AirTriggers feature hasn't been removed.
Here's the new ROG Tessen Mobile Controller, their new telescopic gaming controller that's compatible with all Android phones!
The neat part: it can be folded, making it much easier to carry. Hands-on video.
The neat part: it can be folded, making it much easier to carry. Hands-on video.
Wow - Google may be planning to ship a major kernel upgrade to all its (Tensor-powered) Pixel phones!
Current Tensor Pixels may be upgraded to Linux kernel 6.1, according to comments left on an AOSP patch by Google engineers. Tensor G1 and G2 Pixels currently run on Linux 5.10, while Tensor G3 Pixels run on Linux 5.15.
Tensor G4 Pixels (ie. the Pixel 9 series) may release with Linux kernel 5.15 but will also be upgraded to Linux 6.1.
Major kernel upgrades are rarely ever done for Android smartphones, even for Google. Google has had test branches for newer kernel releases for its Tensor Pixels, but you had to compile a kernel based on those branches yourself if you wanted to upgrade the major kernel version.
One big benefit of performing a major kernel version upgrade is it will make long-term support better in the future, plus it'll introduce new features.
(Thanks to akes29 on Twitter for the tip!)
Current Tensor Pixels may be upgraded to Linux kernel 6.1, according to comments left on an AOSP patch by Google engineers. Tensor G1 and G2 Pixels currently run on Linux 5.10, while Tensor G3 Pixels run on Linux 5.15.
Tensor G4 Pixels (ie. the Pixel 9 series) may release with Linux kernel 5.15 but will also be upgraded to Linux 6.1.
Major kernel upgrades are rarely ever done for Android smartphones, even for Google. Google has had test branches for newer kernel releases for its Tensor Pixels, but you had to compile a kernel based on those branches yourself if you wanted to upgrade the major kernel version.
One big benefit of performing a major kernel version upgrade is it will make long-term support better in the future, plus it'll introduce new features.
(Thanks to akes29 on Twitter for the tip!)
The rumors were true: Google is rebranding Nearby Share to “Quick Share” to better align with Samsung’s P2P file sharing service of the same name. Google collaborated with Samsung to integrate the experiences and bring “the best of [their] sharing solutions together into a singular cross-Android solution under the Quick Share name”.
The updated Quick Share branding will start rolling out to current Nearby Share-enabled devices next month.
The blog post is a bit vague, but my understanding is that Samsung’s existing Quick Share client now runs Google’s Nearby SDK in addition to their own. This would allow Nearby Share-enabled devices to appear in Samsung’s Quick Share menu, while also retaining support for sharing with existing Quick Share-compatible devices like Samsung PCs.
Speaking of PCs, Google says they’re working with OEMs like LG to bundle Google’s Quick Share Windows client.
The updated Quick Share branding will start rolling out to current Nearby Share-enabled devices next month.
The blog post is a bit vague, but my understanding is that Samsung’s existing Quick Share client now runs Google’s Nearby SDK in addition to their own. This would allow Nearby Share-enabled devices to appear in Samsung’s Quick Share menu, while also retaining support for sharing with existing Quick Share-compatible devices like Samsung PCs.
Speaking of PCs, Google says they’re working with OEMs like LG to bundle Google’s Quick Share Windows client.
Finally: Fast Pair support is coming to Google TV devices, starting with the Chromecast with Google TV. This will make it much easier to pair Fast Pair-enabled Bluetooth accessories with your Google TV device. You’ll see a big pop-up on your TV with a “Connect now” button when you put your Fast Pair-enabled accessory into pairing mode.
This is coming “in the next month” to the Chromecast followed by more Google TV devices later this year.
This is coming “in the next month” to the Chromecast followed by more Google TV devices later this year.
LG TVs and select Google TV/Android TV OS devices will soon be able to act as Thread border routers for Google Home. This will let them act as a hub for your Matter-enabled smart home ecosystem, making it easier to add new Matter devices to your home network and control them from within the Google Home app.
Google didn’t share any details on which Google TV/Android TV OS devices will support this, but I previously discovered code in AOSP that suggests that a Thread network stack will be added in Android 15 but is being specifically backported to Android 14 as well for TV devices. So, it’s possible only some TVs running Android TV 14 will support this.
Google didn’t share any details on which Google TV/Android TV OS devices will support this, but I previously discovered code in AOSP that suggests that a Thread network stack will be added in Android 15 but is being specifically backported to Android 14 as well for TV devices. So, it’s possible only some TVs running Android TV 14 will support this.
This media is not supported in your browser
VIEW IN TELEGRAM
Android’s media output switcher has gotten an upgrade in Android 14. The new Output Switcher 2.0 adds improved volume controls (such as the ability to tap the volume icon to quickly mute the media), device categories (“suggested devices” followed by “speakers & displays”), and support for picking up devices with custom protocols.
The last tidbit is the most interesting, since last CES, Google said Spotify Connect devices would soon show up in the output switcher; meanwhile Android 13 devices with GMS picked up support for showing Google Cast devices in the output switcher.
Developers interested in enabling Output Switcher support and features like background casting and remote-to-local playback should check out the Google Cast developer guide and Media router docs.
The last tidbit is the most interesting, since last CES, Google said Spotify Connect devices would soon show up in the output switcher; meanwhile Android 13 devices with GMS picked up support for showing Google Cast devices in the output switcher.
Developers interested in enabling Output Switcher support and features like background casting and remote-to-local playback should check out the Google Cast developer guide and Media router docs.
This media is not supported in your browser
VIEW IN TELEGRAM
Google’s new “cast to devices nearby” feature lets you seamlessly transfer media playback from your Pixel Pro phone to your Pixel Tablet when it’s docked. All you have to do is bring your phone close to the docked tablet to transfer media from phone to tablet or vice versa. This feature works with Spotify and YouTube Music, but Google says it should work with other media apps that integrate Output Switcher support.
Note: You’ll need a Pixel 6 Pro, Pixel 7 Pro, or Pixel 8 Pro as only those models support ultra wideband (UWB), which is the radio technology this feature uses to determine when your phone is close to your tablet and pointed directly at it. The Pixel Tablet has a UWB radio, but it wasn’t really used for anything before this feature’s arrival.
Some of you might remember my posts about an Android 13 feature called “media tap-to-transfer”. To recap, Android 13 introduced UI elements (such as the indicator chips shown in the embedded video) that tell you when your phone is too close/far or you’ve successfully transferred media. The actual media handoff here is handled by Google Play Services.
Note: You’ll need a Pixel 6 Pro, Pixel 7 Pro, or Pixel 8 Pro as only those models support ultra wideband (UWB), which is the radio technology this feature uses to determine when your phone is close to your tablet and pointed directly at it. The Pixel Tablet has a UWB radio, but it wasn’t really used for anything before this feature’s arrival.
Some of you might remember my posts about an Android 13 feature called “media tap-to-transfer”. To recap, Android 13 introduced UI elements (such as the indicator chips shown in the embedded video) that tell you when your phone is too close/far or you’ve successfully transferred media. The actual media handoff here is handled by Google Play Services.
Google Cast is getting better support for short form content, fixing a common problem, and expanding to new devices.
A new “auto-play” button can appear when you’re casting a short form video, giving you the option to cast just that specific video or automatically continue playing the next video after the current one ends. Speaking of short form video, you can now cast TikTok content from your phone! In the near future, you’ll also be able to cast live videos from TikTok.
A new “Persistent Cast icon” ensures the Cast icon will appear whenever users need it, even when no nearby Cast devices are detected. This is because users have complained that the Cast icon is missing, so now the Cast icon will persist to help explain why a specific device might not be visible. Developers are generally recommended to place the Cast icon prominently on every screen with playable content in the top right corner.
New devices with Google Cast support include LG’s 2024 TV series, and later this year, LG Hospitality and Healthcare products such as those in hotel rooms. Google says there are now over 220 million monthly active Google TV and Android TV OS devices (which all ship with Chromecast built-in).
Lastly, for Web Receiver apps streaming HLS content, Google is asking developers to migrate to Shaka Player for playback, since the current player (MPL) won’t get any feature updates. The Cast Web Receiver SDK has gained increased support for HLS playback using Shaka Player on cast device targets and has added an opt-in flag to enable it.
A new “auto-play” button can appear when you’re casting a short form video, giving you the option to cast just that specific video or automatically continue playing the next video after the current one ends. Speaking of short form video, you can now cast TikTok content from your phone! In the near future, you’ll also be able to cast live videos from TikTok.
A new “Persistent Cast icon” ensures the Cast icon will appear whenever users need it, even when no nearby Cast devices are detected. This is because users have complained that the Cast icon is missing, so now the Cast icon will persist to help explain why a specific device might not be visible. Developers are generally recommended to place the Cast icon prominently on every screen with playable content in the top right corner.
New devices with Google Cast support include LG’s 2024 TV series, and later this year, LG Hospitality and Healthcare products such as those in hotel rooms. Google says there are now over 220 million monthly active Google TV and Android TV OS devices (which all ship with Chromecast built-in).
Lastly, for Web Receiver apps streaming HLS content, Google is asking developers to migrate to Shaka Player for playback, since the current player (MPL) won’t get any feature updates. The Cast Web Receiver SDK has gained increased support for HLS playback using Shaka Player on cast device targets and has added an opt-in flag to enable it.