Sony is starting to roll out its Android 14 update, starting with the Xperia 1 V in Europe. The 1.3GB update has a build number of 67.1.A.2.112 and the October 2023 security patches. The kernel version is 5.15.74-android13 (the chipset is under GRF).
Here's what's new:
* Improved Bokeh mode from the Xperia 5 V. This improved mode adds the ability to decrease focus in the background to emphasize objects at the foreground. Available on 24mm lens and 48mm focal length.
* Video Creator app from the Xperia 5 V is now preinstalled. This app enables the quick and easy creation of short videos with advanced editing features. You can compile a range of short clips with the ability to add music and effects with Auto Edit.
* Lock screen shortcut customization. Android 13 on Xperia already had lock screen shortcuts, but the Android 14 release implements AOSP's lock screen shortcut customization feature. This is available through the ThemePicker. The lock screen clock styles as seen on Pixel phones running Android 14 are not available, as those are Pixel-exclusive. However, Sony's existing slate of lock screen clocks are still there.
* Other Android 14 features. See my past posts for more info😃
Thanks to Redka for the screenshots!
(As you can notice, Android on Xperia allows you to have two shortcuts on each side. AOSP's lock screen shortcut feature actually allows for this, but it has to be configured by the OEM)
Here's what's new:
* Improved Bokeh mode from the Xperia 5 V. This improved mode adds the ability to decrease focus in the background to emphasize objects at the foreground. Available on 24mm lens and 48mm focal length.
* Video Creator app from the Xperia 5 V is now preinstalled. This app enables the quick and easy creation of short videos with advanced editing features. You can compile a range of short clips with the ability to add music and effects with Auto Edit.
* Lock screen shortcut customization. Android 13 on Xperia already had lock screen shortcuts, but the Android 14 release implements AOSP's lock screen shortcut customization feature. This is available through the ThemePicker. The lock screen clock styles as seen on Pixel phones running Android 14 are not available, as those are Pixel-exclusive. However, Sony's existing slate of lock screen clocks are still there.
* Other Android 14 features. See my past posts for more info😃
Thanks to Redka for the screenshots!
(As you can notice, Android on Xperia allows you to have two shortcuts on each side. AOSP's lock screen shortcut feature actually allows for this, but it has to be configured by the OEM)
👍51🔥10❤4👏2🤮2
Mishaal's Android News Feed
Google is rolling out an OTA update that fixes this issue on affected Pixel devices (all Tensor-powered Pixels running Android 14). The update has a build ID of UP1A.231105.00X and brings with it the November 2023 security patches as well as other bug fixes…
It seems that the multi-user bug that caused some users to lose access to their data is due to a bug in F2FS, the file system Google uses for the Pixel's data partition.
First, the only Pixels that were affected by this bug were the Pixel 6 and later, ie. Tensor-powered Pixels. However, this bug has nothing to do with the Tensor chipset but rather the kernel version and the file system in use. Although 5th gen Pixels also use F2FS for the data partition, their kernels are based on Linux 4.19, while 6-7th gen use kernels based on Linux 5.10 and 8th gen on Linux 5.15.
In their upstream submissions, Google didn't pinpoint exactly which prior commits were faulty, so we don't know exactly which Linux versions are impacted by this, though.
Second, the bug seems to be triggered by a corrupted
The Google Play System Update that Google pushed out to "help prevent this issue from being triggered on additional devices" seems to have been a patch to
Third, Google's solution to fix this problem is to run
Given that this bug is F2FS-related, that means it shouldn't be Pixel-specific. Samsung uses F2FS for their flagships like the S23, which recently got updated to Android 14 as well, for example. However, hopefully this issue won't impact other devices since Google pushed out a Mainline update to prevent it from triggering in the only way we know it can right now. Plus, I'm sure other OEMs will be picking up Google's kernel patches soon as well.
Thanks to Daniel Micay and Juhyung Park for sharing their inputs!
First, the only Pixels that were affected by this bug were the Pixel 6 and later, ie. Tensor-powered Pixels. However, this bug has nothing to do with the Tensor chipset but rather the kernel version and the file system in use. Although 5th gen Pixels also use F2FS for the data partition, their kernels are based on Linux 4.19, while 6-7th gen use kernels based on Linux 5.10 and 8th gen on Linux 5.15.
In their upstream submissions, Google didn't pinpoint exactly which prior commits were faulty, so we don't know exactly which Linux versions are impacted by this, though.
Second, the bug seems to be triggered by a corrupted
xattr (extended attribute) entry that occurs when a secondary user is removed and the file system is F2FS. The Google Play System Update that Google pushed out to "help prevent this issue from being triggered on additional devices" seems to have been a patch to
MediaProvider to disable the removal of xattr on a secondary user's removal.Third, Google's solution to fix this problem is to run
fsck (file system consistency check) upon mount of the data partition. This is only run after the first boot and not any subsequent boots. Google patched fsck under f2fs-tools to address corrupted xattr entries. These patches were submitted and merged upstream quite quickly, which is no surprise given the severity of the bug.Given that this bug is F2FS-related, that means it shouldn't be Pixel-specific. Samsung uses F2FS for their flagships like the S23, which recently got updated to Android 14 as well, for example. However, hopefully this issue won't impact other devices since Google pushed out a Mainline update to prevent it from triggering in the only way we know it can right now. Plus, I'm sure other OEMs will be picking up Google's kernel patches soon as well.
Thanks to Daniel Micay and Juhyung Park for sharing their inputs!
👍53
Here's a look at Bluetooth LE Audio's broadcast audio feature on Android 13!
User aborne25 on Twitter put together a demo of broadcast audio (Auracast) using their Sony Xperia 5 V connected to Sony's INZONE Buds and LinkBuds S, which all support LE Audio. Since Sony's Android fork is quite close to stock, this gives us a look at what broadcast audio will look like on Pixel in the future!
In order for this to work, you need an Android smartphone with a Bluetooth chip that supports LE Audio and a software stack that supports it (Android 13 or later). You also need audio products that support LE Audio, of which there aren't many right now. Further, all products need to support the Public Broadcast Profile (PBP). As shown in the video, "LE_AUDIO" as well as "Receive shared audio" need to be toggled on in settings.
To start a broadcast, open the media output switcher from the media player notification and tap the "Broadcast" button in the bottom left. A QR code is shown at the top which lets other devices quickly join the broadcast. Below that, the broadcast name and password can be edited. When you're broadcasting, the device name in the media output switcher changes to "broadcasting".
To join the broadcast, you either go to sound & vibration settings or open the expanded volume slider and then tap on the broadcast icon. Then select "find broadcasts" and select the broadcast from the list. Tapping "leave broadcast" will leave the broadcast but it'll continue in the background until you tap "stop casting".
Hopefully more audio products with LE Audio broadcast support get released, because multi-device audio sharing is something a LOT of folks want but something only a few devices with custom Bluetooth stacks offer!
User aborne25 on Twitter put together a demo of broadcast audio (Auracast) using their Sony Xperia 5 V connected to Sony's INZONE Buds and LinkBuds S, which all support LE Audio. Since Sony's Android fork is quite close to stock, this gives us a look at what broadcast audio will look like on Pixel in the future!
In order for this to work, you need an Android smartphone with a Bluetooth chip that supports LE Audio and a software stack that supports it (Android 13 or later). You also need audio products that support LE Audio, of which there aren't many right now. Further, all products need to support the Public Broadcast Profile (PBP). As shown in the video, "LE_AUDIO" as well as "Receive shared audio" need to be toggled on in settings.
To start a broadcast, open the media output switcher from the media player notification and tap the "Broadcast" button in the bottom left. A QR code is shown at the top which lets other devices quickly join the broadcast. Below that, the broadcast name and password can be edited. When you're broadcasting, the device name in the media output switcher changes to "broadcasting".
To join the broadcast, you either go to sound & vibration settings or open the expanded volume slider and then tap on the broadcast icon. Then select "find broadcasts" and select the broadcast from the list. Tapping "leave broadcast" will leave the broadcast but it'll continue in the background until you tap "stop casting".
Hopefully more audio products with LE Audio broadcast support get released, because multi-device audio sharing is something a LOT of folks want but something only a few devices with custom Bluetooth stacks offer!
👍37🔥19❤6
The Pixel 8 series are the first Android handsets that allow you to enable ARM's MTE (Memory Tagging Extension), a feature of Arm v9 CPUs that helps protect against memory safety bugs by providing detailed information about memory violations. This feature can help developers more easily discover memory safety issues in their applications.
Like the Tensor G3, MediaTek's new Dimensity 9300 also supports MTE, and it can even be switched on or off in the bootloader. Tensor G3 integrates support for MTE only within Android's developer-facing toggle. Qualcomm's Snapdragon 8 Gen 3 does not support MTE.
MTE can be enabled on compatible devices running Android 14 by going to Settings > System > Developer options > Memory Tagging Extension.
Do note that MTE is disabled by default because it's highly likely you'll encounter issues with apps crashing or failing to run correctly. There shouldn't be any "noticeable performance issues", though, according to Google's Mark Brand writing for the Project Zero blog.
Google's Sanitizer Test App (available on Google Play) can be used to check whether MTE has been enabled in the bootloader.
With shell commands, you can configure the MTE mode (async, sync, asymmetric), but note that certain system processes (like system_server, NFC, SE, Bluetooth) are excluded. Chromium doesn't support MTE yet, either.
Like the Tensor G3, MediaTek's new Dimensity 9300 also supports MTE, and it can even be switched on or off in the bootloader. Tensor G3 integrates support for MTE only within Android's developer-facing toggle. Qualcomm's Snapdragon 8 Gen 3 does not support MTE.
MTE can be enabled on compatible devices running Android 14 by going to Settings > System > Developer options > Memory Tagging Extension.
Do note that MTE is disabled by default because it's highly likely you'll encounter issues with apps crashing or failing to run correctly. There shouldn't be any "noticeable performance issues", though, according to Google's Mark Brand writing for the Project Zero blog.
Google's Sanitizer Test App (available on Google Play) can be used to check whether MTE has been enabled in the bootloader.
With shell commands, you can configure the MTE mode (async, sync, asymmetric), but note that certain system processes (like system_server, NFC, SE, Bluetooth) are excluded. Chromium doesn't support MTE yet, either.
👍44🤔5😁2
Many were wondering if Xiaomi was going to remove the ability to unlock its phones' bootloaders, and it seems that the answer is no.
However, at least for Chinese units, there are new requirements, including that you have to "achieve level 5" on the CN Xiaomi community, that bootloader unlock permissions are time-sensitive, and that you can only unlock three devices a year.
Xiaomi told Android Authority that, if you unlock the bootloader of a device running HyperOS, you will no longer receive OTA updates. That's not a big deal since most users who unlock the bootloader do so to install a custom ROM. Many users who stay on the stock ROM modify boot partitions to achieve root access, too, so it's safer to sideload a full update package anyway.
Unlocking the bootloader of a device running MIUI has always required some additional steps, including binding your device to a Xiaomi account and waiting a set amount of time. But having to become a "level 5" community member is even more restrictive, and I imagine a lot of users are going to just spam the forums to achieve that.
—-
I don't have any new information/updates to share regarding the status of bootloader unlocking on ASUS phones, sorry!
However, at least for Chinese units, there are new requirements, including that you have to "achieve level 5" on the CN Xiaomi community, that bootloader unlock permissions are time-sensitive, and that you can only unlock three devices a year.
Xiaomi told Android Authority that, if you unlock the bootloader of a device running HyperOS, you will no longer receive OTA updates. That's not a big deal since most users who unlock the bootloader do so to install a custom ROM. Many users who stay on the stock ROM modify boot partitions to achieve root access, too, so it's safer to sideload a full update package anyway.
Unlocking the bootloader of a device running MIUI has always required some additional steps, including binding your device to a Xiaomi account and waiting a set amount of time. But having to become a "level 5" community member is even more restrictive, and I imagine a lot of users are going to just spam the forums to achieve that.
—-
I don't have any new information/updates to share regarding the status of bootloader unlocking on ASUS phones, sorry!
🤡85👍21🤣6❤3❤🔥1👏1
Google has formally announced that the Home app's "home panel" feature, which gives you "quick access to your Spaces and Favorites directly from your lock screen", is coming to other Android devices with Android 14.
Shown above is the old Device Controls UI on a OnePlus Open running Android 13 (left) versus the new Device Controls UI on a OnePlus 11 running Android 14 (right). This new home panel UI has also appeared on Galaxy S23 series devices and the Nothing Phone 2 running Android 14, among others.
The "home panel" is accessed by tapping the Device Controls shortcut on the lock screen or in the Quick Settings panel.
The "home panel" takes advantage of a new API called
With Android 14, the API is now public and third-party apps, like Home Assistant, can utilize it to show a custom activity in the Device Controls panel as well.
Shown above is the old Device Controls UI on a OnePlus Open running Android 13 (left) versus the new Device Controls UI on a OnePlus 11 running Android 14 (right). This new home panel UI has also appeared on Galaxy S23 series devices and the Nothing Phone 2 running Android 14, among others.
The "home panel" is accessed by tapping the Device Controls shortcut on the lock screen or in the Quick Settings panel.
The "home panel" takes advantage of a new API called
ControlsProviderService#META_DATA_PANEL_ACTIVITY that lets apps embed a custom activity in the Device Controls interface. When Pixels added support for the home panel in the June 2023 Pixel Feature Drop (Android 13 QPR3), the API wasn't public and could only be used by the Google Home app.With Android 14, the API is now public and third-party apps, like Home Assistant, can utilize it to show a custom activity in the Device Controls panel as well.
👍46❤4
Android 14 finally lets apps show content on both screens on a foldable! Thanks to new Jetpack WindowManager APIs and a new WindowManager Extension, apps can now use both the inner & outer display on a foldable.
Here's my article for Android Police that explains how this new feature works.
Oh, and I would also appreciate if you check out the article I wrote for Android Central over the weekend, which explains what reviewers actually mean when we say many apps aren't "optimized" yet for foldables.
Here's my article for Android Police that explains how this new feature works.
Oh, and I would also appreciate if you check out the article I wrote for Android Central over the weekend, which explains what reviewers actually mean when we say many apps aren't "optimized" yet for foldables.
Android Police
Android 14 finally lets apps show content on both screens on a foldable
Android 14's dual display mode could spur creative third-party development for foldables
👍37❤12
Google has announced that "developers with newly created personal Play Console accounts will soon be required to test their apps with at least 20 people for a minimum of two weeks before applying for access to production."
More specifically, Google says developers with personal accounts created after November 13, 2023, have to "run a closed test for [their] app with a minimum of 20 testers who have opted-in for at least the last 14 days continuously." By "continuously", Google means that they "won't count testers who opted in, tested for less than 14 days, and then opted out."
Certain features in the Play Console, such as Production (Release > Production) and Pre-registration (Release > Testing > Pre-registration) will be disabled until these requirements are met. Google will ask developers "some questions to help [them] understand your app, its testing process, and its production readiness."
More specifically, Google says developers with personal accounts created after November 13, 2023, have to "run a closed test for [their] app with a minimum of 20 testers who have opted-in for at least the last 14 days continuously." By "continuously", Google means that they "won't count testers who opted in, tested for less than 14 days, and then opted out."
Certain features in the Play Console, such as Production (Release > Production) and Pre-registration (Release > Testing > Pre-registration) will be disabled until these requirements are met. Google will ask developers "some questions to help [them] understand your app, its testing process, and its production readiness."
👍37👎18🤔18