Android builds released after December 13, 2023 are now required to preload the Google Meet app on the system image. This means you'll be able to disable but not fully uninstall it.
Google Meet has been part of the regular GMS bundle for a while now, but it was designated a "Flexible" app in the past whereas now it's a "Core" app. Flexible apps have to be made available to the end user out of the box, but end users are allowed to uninstall the app. Core apps, on the other hand, must be preloaded on a system partition, meaning they can't be fully removed (though you can disable them).
This doesn't change much for end users who actually use Meet, but it does mean that if you don't, the app will take up some space that you can't reclaim. However, some devices already preloaded Meet on the system image prior to this change in the GMS geo-availability chart. These devices were likely on a RSA tier that required this.
Google Meet has been part of the regular GMS bundle for a while now, but it was designated a "Flexible" app in the past whereas now it's a "Core" app. Flexible apps have to be made available to the end user out of the box, but end users are allowed to uninstall the app. Core apps, on the other hand, must be preloaded on a system partition, meaning they can't be fully removed (though you can disable them).
This doesn't change much for end users who actually use Meet, but it does mean that if you don't, the app will take up some space that you can't reclaim. However, some devices already preloaded Meet on the system image prior to this change in the GMS geo-availability chart. These devices were likely on a RSA tier that required this.
🤮100👎30👍22👀6🤡2
Mishaal's Android News Feed
The Chromecast with Google TV (4K) seems to be getting a new feature that lets you receive incoming call notifications from select apps on your TV. Google Meet seems to be one app that'll support this feature. I previously spotted hints of this feature in…
And here's a screenshot of Google TV's new "call notifications" feature in action! My tipster, KovacDenis10 on Twitter, saw an incoming call notification from Google Meet while they were in the Prime Video app (that's why the rest of the screen is blank in the screenshot).
👍61🔥10
Mishaal's Android News Feed
Maybe hold off on applying the January 2024 GPSU if you have a Pixel phone and have multiple user profiles? Seeing a lot of reports about internal storage access issues, similar to the ones from a few months ago.
Google has halted the rollout of the January 2024 GPSU following reports of devices having file access issues.
Over the past few days, several users on Reddit, particularly those with Pixel phones, have faced issues with file access. The internal storage isn't being mounted, camera crashes, Files app isn't showing files, screenshots not being saved, etc. Many users have had to factory reset their phone to fix this problem.
On Reddit, the /u/PixelCommunity account said that "our team is looking into this right now", and according a source, Google has halted the January 2024 GPSU as they investigate. They discovered that in some cases, the DCLA Mainline module (
(DCLA [Dynamic Common Library Apex] is a mechanism used by Mainline, which places shared c++ libraries into a separate apex in order to de-duplicate them, with the goal of reducing the overall size of a train.)
Google has decided to disable DCLA functionality for now as they investigate the root cause of this bug. Disabling DCLA functionality will increase the size of some modules but should avoid the dependency issue they discovered and hopefully prevent others from experiencing this bug.
Over the past few days, several users on Reddit, particularly those with Pixel phones, have faced issues with file access. The internal storage isn't being mounted, camera crashes, Files app isn't showing files, screenshots not being saved, etc. Many users have had to factory reset their phone to fix this problem.
On Reddit, the /u/PixelCommunity account said that "our team is looking into this right now", and according a source, Google has halted the January 2024 GPSU as they investigate. They discovered that in some cases, the DCLA Mainline module (
com.google.mainline.primary.libs) rolls back to the base/factory installed version. This causes mismatched dependency issues with other DCLA-enabled modules.(DCLA [Dynamic Common Library Apex] is a mechanism used by Mainline, which places shared c++ libraries into a separate apex in order to de-duplicate them, with the goal of reducing the overall size of a train.)
Google has decided to disable DCLA functionality for now as they investigate the root cause of this bug. Disabling DCLA functionality will increase the size of some modules but should avoid the dependency issue they discovered and hopefully prevent others from experiencing this bug.
👍53🤡32👀11👏3❤1
This media is not supported in your browser
VIEW IN TELEGRAM
Google is preparing to add Ultra HDR image capture support to the CameraX API.
This will allow apps that utilize the CameraX API to output images in the new JPEG_R format used for Ultra HDR, on devices running Android 14.
JPEG_R is a new type of JPEG file that can contain a gainmap in its metadata so that the HDR version of an image can be rendered on HDR displays and the SDR version on SDR displays.
This will allow apps that utilize the CameraX API to output images in the new JPEG_R format used for Ultra HDR, on devices running Android 14.
JPEG_R is a new type of JPEG file that can contain a gainmap in its metadata so that the HDR version of an image can be rendered on HDR displays and the SDR version on SDR displays.
🔥105👍21❤9🆒1
A couple of months ago, I spotted a hint that Wear OS 6 will be based on Android 15, and thus by extension, that Wear OS 5 would be based on Android 14.
I didn't report on it then since there was only one mention and it could've been a typo, but it looks like I was right.
More specifically, what I found was a new compat change in the Android 14 QPR1 beta named
Wear OS 6 being based on Android 15 would be interesting as it would mean that Wear OS 5 would be based on Android 14 (now corroborated by 9to5Google's findings). Wear has been skipping major releases since Wear OS 2:
Wear OS 2 = Android 9
Wear OS 3 = Android 11
Wear OS 4 = Android 13
I didn't report on it then since there was only one mention and it could've been a typo, but it looks like I was right.
More specifically, what I found was a new compat change in the Android 14 QPR1 beta named
WEAROS_WALLPAPER_HANDLES_SCALING with the denoscription "Wear products currently force a slight scaling transition to wallpapers when the QSS is opened. However, on Wear 6 (SDK 35) and above, 1P watch faces will be expected to either implement their own scaling, or to override this method to allow the WallpaperController to continue to scale for them." (emphasis mine)Wear OS 6 being based on Android 15 would be interesting as it would mean that Wear OS 5 would be based on Android 14 (now corroborated by 9to5Google's findings). Wear has been skipping major releases since Wear OS 2:
Wear OS 2 = Android 9
Wear OS 3 = Android 11
Wear OS 4 = Android 13
9to5Google
Samsung and Google are preparing Wear OS 5 based on Android 14
The next generation of Wear OS is coming possibly as soon as this year, with Samsung and Google preparing a...
👍53👀16🥰1
The OnePlus 12 is OnePlus's first smartphone to support Camera2 and CameraX vendor extensions! These extensions allow third-party apps that rely on the Camera2 or CameraX APIs to utilize certain OEM camera effects that would otherwise only be available in the stock camera app.
In this case, OnePlus has provided Bokeh and Night (Camera2 and CameraX) extensions for the main rear camera and a Night (Camera2 and CameraX) extension for the main front camera.
Snapchat, for example, uses the Camera2 extension for Night mode supplied by Google to implement Night Sight support on Pixels. Samsung has been by far the best at implementing support for vendor extensions, but it's good to finally see other OEMs add support.
Thanks to MartinGuayOTT on Twitter for the screenshots!
In this case, OnePlus has provided Bokeh and Night (Camera2 and CameraX) extensions for the main rear camera and a Night (Camera2 and CameraX) extension for the main front camera.
Snapchat, for example, uses the Camera2 extension for Night mode supplied by Google to implement Night Sight support on Pixels. Samsung has been by far the best at implementing support for vendor extensions, but it's good to finally see other OEMs add support.
Thanks to MartinGuayOTT on Twitter for the screenshots!
👍78😁3
Mishaal's Android News Feed
The OnePlus 12 is OnePlus's first smartphone to support Camera2 and CameraX vendor extensions! These extensions allow third-party apps that rely on the Camera2 or CameraX APIs to utilize certain OEM camera effects that would otherwise only be available in…
On the other hand, the new ROG Phone 8 does not support any Camera2 or CameraX vendor extensions, much like previous phones from ASUS.
I reported back in September (for Patrons/X subscribers only) that Google wanted to require that new devices launching with Android 14 support Bokeh and Night extensions for both the primary front and rear cameras, however, it looks like this was never enforced in the end.
(Thanks to murmelito_ on Threads for the screenshots!)
I reported back in September (for Patrons/X subscribers only) that Google wanted to require that new devices launching with Android 14 support Bokeh and Night extensions for both the primary front and rear cameras, however, it looks like this was never enforced in the end.
(Thanks to murmelito_ on Threads for the screenshots!)
👍31😢23🤡12🤝2
Google has announced a "Mint" color for the Pixel 8 series (only available from the Google Store with 128GB storage), alongside a new Pixel Feature Drop for January 2024! This Feature Drop is a bit unusual since it isn't accompanied by a new QPR update, but it does bring some interesting features.
For example, the Pixel 8 Pro's Thermometer app is finally getting the ability to measure body temperature! This means the FDA has authorized the Pixel Thermometer to take body temperature readings. Any temperature results you take can be synced to your Fitbit account.
Both Pixel Watch models now support automatic audio switching, which means your Pixel Buds Pro can seamlessly switch from a Pixel Tablet to your paired Pixel phone.
Also, Quick Share (the revamped/rebranded version of Google's Nearby Share) should be rolling out soon, so you can look forward to that.
A more exciting development is the rollout of the Circle to Search feature Google announced at Galaxy Unpacked. Google reiterates that they'll roll this out to the Pixel 8 and Pixel 8 Pro on January 31, but it's also already available on the Galaxy S24 series. (I shared a method with my Patreon/X subscribers to enable this feature on other Pixel devices right now, but it requires root to spoof the Pixel 8.)
Lastly, Google is starting to more widely roll out the Photomoji and Magic Compose features in the Google Messages app for Pixel users. Photomoji lets you turn any photo into a custom reaction or sticker, while Magic Compose helps you rewrite messages in different styles using generative AI.
Photomoji is available for the Pixel 3a and later, while Magic Compose is only available for the Pixel 6 and later (processing happens on-device in the case of the Pixel 8 Pro).
For example, the Pixel 8 Pro's Thermometer app is finally getting the ability to measure body temperature! This means the FDA has authorized the Pixel Thermometer to take body temperature readings. Any temperature results you take can be synced to your Fitbit account.
Both Pixel Watch models now support automatic audio switching, which means your Pixel Buds Pro can seamlessly switch from a Pixel Tablet to your paired Pixel phone.
Also, Quick Share (the revamped/rebranded version of Google's Nearby Share) should be rolling out soon, so you can look forward to that.
A more exciting development is the rollout of the Circle to Search feature Google announced at Galaxy Unpacked. Google reiterates that they'll roll this out to the Pixel 8 and Pixel 8 Pro on January 31, but it's also already available on the Galaxy S24 series. (I shared a method with my Patreon/X subscribers to enable this feature on other Pixel devices right now, but it requires root to spoof the Pixel 8.)
Lastly, Google is starting to more widely roll out the Photomoji and Magic Compose features in the Google Messages app for Pixel users. Photomoji lets you turn any photo into a custom reaction or sticker, while Magic Compose helps you rewrite messages in different styles using generative AI.
Photomoji is available for the Pixel 3a and later, while Magic Compose is only available for the Pixel 6 and later (processing happens on-device in the case of the Pixel 8 Pro).
👍87❤28🔥11🤔4👏1
Mishaal's Android News Feed
Google has announced a "Mint" color for the Pixel 8 series (only available from the Google Store with 128GB storage), alongside a new Pixel Feature Drop for January 2024! This Feature Drop is a bit unusual since it isn't accompanied by a new QPR update, but…
Google is rolling out the update to the Pixel Thermometer app that enables body temperature scanning on the Pixel 8 Pro, but only if you're in the U.S.
The app checks that the ISO country code using the
This is because Google has only received approval to use this feature in the U.S. so far, but if you're outside of the U.S., modders have already figured out how to forcefully enable this feature. Using the same method used to enable VoLTE/VoWiFi in unsupported regions, @nullby whipped up a quick app that lets you change the ISO country code read by the app to whatever you want, and it doesn't need root access!
So you just grant the app shell-level privileges using Shizuku so it can call the
Update: Here's the app you need. Download version 1.1 from the releases page. Then to set it up:
1) Download and set up Shizuku from Google Play.
2) Open the Carrier Vanity Name app, and in the "ISO Country Code" field (the second field), type "us". (You can ignore the first field.)
3) Click "set".
4) Stop the Thermometer app and clear its data, then open it. The body temperature feature should be available.
5) You can now re-open the CVN app and hit "Reset" to reset the ISO country code.
(Screenshots via @nailsad_eleos.)
The app checks that the ISO country code using the
TelephonyManager.getSimCountryIso() method returns "us", which means your SIM has to be connected to a network in the U.S.This is because Google has only received approval to use this feature in the U.S. so far, but if you're outside of the U.S., modders have already figured out how to forcefully enable this feature. Using the same method used to enable VoLTE/VoWiFi in unsupported regions, @nullby whipped up a quick app that lets you change the ISO country code read by the app to whatever you want, and it doesn't need root access!
So you just grant the app shell-level privileges using Shizuku so it can call the
TelephonyManager APIs and then use the app to set the country code to "us", unlocking the body temperature scanning feature in the Thermometer app. The best part is that this persists even if you reset the country code (as you should) so long as you don't wipe the data of the app or uninstall it.Update: Here's the app you need. Download version 1.1 from the releases page. Then to set it up:
1) Download and set up Shizuku from Google Play.
2) Open the Carrier Vanity Name app, and in the "ISO Country Code" field (the second field), type "us". (You can ignore the first field.)
3) Click "set".
4) Stop the Thermometer app and clear its data, then open it. The body temperature feature should be available.
5) You can now re-open the CVN app and hit "Reset" to reset the ISO country code.
(Screenshots via @nailsad_eleos.)
👍64😐15❤7🔥6🤡5👎2👌2
This media is not supported in your browser
VIEW IN TELEGRAM
Samsung quietly updated the UI of its Bixby voice assistant a few days ago. The updated version (3.3.53.16) is rolling out to Galaxy devices running One UI 6.0 and later.
Here's a demo of the new Bixby UI on my Galaxy S24 Ultra.
(Sidenote: Do any of you actually use Bixby?)
Here's a demo of the new Bixby UI on my Galaxy S24 Ultra.
(Sidenote: Do any of you actually use Bixby?)
🤮61👍30😁8🆒5💩4👎2❤1
Android's eSIM transfer tool is here! This tool was first announced by Google at MWC 2023, and it lets you scan a QR code to transfer eSIM profiles between your Android phones, like between a Galaxy S24 Ultra and a Pixel 8 Pro.
Full details over on this Android Police article.
Full details over on this Android Police article.
Android Police
Android now lets you transfer eSIMs between your phones
Android's long-awaited QR code-based eSIM transfer tool is finally here, letting you move eSIMs between your phones
🔥84👍23❤🔥7❤6
Samsung has heard your pleas: You can now hide the gesture bar in One UI 6.1 on the Galaxy S24!
Samsung is rolling out an update to NavStar, the Good Lock module that lets you customize navigation, that brings back the setting to hide the gesture hint. Here's a before and after with the setting disabled/enabled. Not only do you reclaim space at the bottom, but Google's Circle to Search gesture still works!
Here's how to hide the gesture bar after updating Nav Star:
1) Open NavStar's settings and toggle "enable extra gesture settings".
2) Open the Settings app and go to Display > Navigation bar > More options.
3) You should now see a "gesture hint" option. Toggle this to hide the gesture bar!
Glad to see Samsung address feedback so quickly. The removal of the "gesture hint" setting from One UI 6.1 was one of the changes that I noticed a lot of people complain about, so this should be a welcome addition. Hopefully it's brought out of NavStar soon.
Thanks to @RydahDoesTech for the tip!
Samsung is rolling out an update to NavStar, the Good Lock module that lets you customize navigation, that brings back the setting to hide the gesture hint. Here's a before and after with the setting disabled/enabled. Not only do you reclaim space at the bottom, but Google's Circle to Search gesture still works!
Here's how to hide the gesture bar after updating Nav Star:
1) Open NavStar's settings and toggle "enable extra gesture settings".
2) Open the Settings app and go to Display > Navigation bar > More options.
3) You should now see a "gesture hint" option. Toggle this to hide the gesture bar!
Glad to see Samsung address feedback so quickly. The removal of the "gesture hint" setting from One UI 6.1 was one of the changes that I noticed a lot of people complain about, so this should be a welcome addition. Hopefully it's brought out of NavStar soon.
Thanks to @RydahDoesTech for the tip!
👍94❤19🤡7🤷♂6🤝3🤬1🤮1
Forwarded from Google News | En
Official Google's demo video of Assistant with Bard.
The arrival of Bard on Android seems to be just around the corner, as Google has prepared a special page in the Pixel Tips app to explain the features of the Bard-enabled Assistant. It also features a demo video of the UI in action.
From the video, you can see that Bard will be able to be invoked like a regular assistant, while it will also have a shortcut in the list of apps. Once invoked, you are given a choice of 3 actions: enter a query using the keyboard, speak the query with your voice, or insert an image and complete it with a query.
Since this page already exists in the Pixel Tips app (but is not yet available to users), it looks like Bard on Android will appear as early as one of the next Pixel Feature Drop.
Previously, 9to5Google has already demoed the Bard UI here and here.
😎 Google News | En
The arrival of Bard on Android seems to be just around the corner, as Google has prepared a special page in the Pixel Tips app to explain the features of the Bard-enabled Assistant. It also features a demo video of the UI in action.
From the video, you can see that Bard will be able to be invoked like a regular assistant, while it will also have a shortcut in the list of apps. Once invoked, you are given a choice of 3 actions: enter a query using the keyboard, speak the query with your voice, or insert an image and complete it with a query.
Since this page already exists in the Pixel Tips app (but is not yet available to users), it looks like Bard on Android will appear as early as one of the next Pixel Feature Drop.
Previously, 9to5Google has already demoed the Bard UI here and here.
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
👍68🔥7