Mishaal's Android News Feed
13.3K subscribers
2.19K photos
99 videos
8 files
1.93K links
Android news from an Android nerd
Download Telegram
Here's a first look at Android 15's new "Home Controls" screensaver, a new screensaver that'll have your Google Home device controls always at your fingertips when your phone or tablet is docked.

Details + screenshots can be found in the latest article I wrote for Android Authority.
๐Ÿ‘59๐Ÿ’ฉ13๐Ÿฅฑ8โค7๐Ÿคก2๐Ÿณ2
Depth Effect on Android?

iOS lets you add a depth effect to your lock screen so that subjects in your lock screen wallpaper can be layered over the clock.

Developer siavash7999 managed to get this working on Android, thanks to ML Kit's subject segmentation API!

You can try this out on your own Android device by installing the latest canary version of the "PixelXpert" Xposed module (requires root).

IMO Google should add this to Android. This is so cool!
๐Ÿ”ฅ230๐Ÿ‘35โค31๐Ÿ‘Ž6๐Ÿคฉ5๐Ÿคฎ5โคโ€๐Ÿ”ฅ3๐Ÿ˜ญ2๐Ÿ˜1
Android 15 will let you change the default wallet app! Wallet apps can store your credit and loyalty cards, car keys, and other things to help with various forms of transactions.

More details available in my latest article for Android Headlines.
๐Ÿ‘69โคโ€๐Ÿ”ฅ10โค4
The first Android 15 beta is HERE! Android 15 Beta 1 is rolling out today to users enrolled in the Android beta program. Supported devices include the Pixel 6 and newer, as well as the Pixel Tablet and Pixel Fold.

Hereโ€™s whatโ€™s new in Android 15 Beta 1, according to Google:

* As I first reported, apps targeting Android 15 are now displayed edge-to-edge by default when running on Android 15! This means apps wonโ€™t have to call the edge-to-edge APIs to show content behind system bars in Android 15, though they should call those APIs to do so in earlier releases. To assist app developers in supporting edge-to-edge, many Material 3 composables handle insets for you.

* Another Android 15 feature I first reported on is app archiving, which went live in DP2 but Google is now choosing to highlight in Beta 1. Android 15 includes OS level support for app archiving and unarchiving, making it easier for third-party app stores to support it (Google Play already does since last year). App store developers should check out the new PackageInstaller APIs while launcher developers should check out the new LauncherApps APIs to learn how to handle archived apps.

* The TalkBack accessibility service in Android 15 now supports Braille displays that use human interface devices over USB and Bluetooth.

* Thereโ€™s also now an OS-level API for E2EE of contact keys so users can securely manage and verify other peopleโ€™s contact information, enhancements to the NFC observe mode to allow apps to register a fingerprint so they can be notified of polling loop activity, inter-character text justification support, a new ProfilingManager class to collect profiling info from within apps, and additional changes to prevent malicious background apps from bringing other apps to the foreground.

Android 15 Beta 1 is the first of 4 planned beta releases. Beta 2 will very likely be unveiled at Google I/O on May 14, while Beta 3 will happen sometime in June and Beta 4 sometime in July. Beta 3 is when Platform Stability will be reached.
๐Ÿ”ฅ78๐Ÿ‘27โคโ€๐Ÿ”ฅ5โค2
Android 15 Beta 1 adds a new "allow WEP networks" toggle under Settings > Network & Internet > Internet > Network preferences that lets you disable connections to Wi-Fi networks secured by WEP.

"WEP is an older security protocol that's less secure", the setting warns.
๐Ÿ”ฅ50๐Ÿ‘21๐Ÿ‘5
Android 15 Beta 1 adds a new "cellular network security" settings page under Settings > Security & privacy > More security & privacy with toggles for "security notifications" and "require encryption."

This page controls Android 15's new anti-stingray protection features I first reported on for Android Authority.
โค53๐Ÿ‘24๐ŸŒš4๐Ÿฅด2
Earlier this year, I broke the news that Google is bringing back lock screen widget support in Android 15.

I now have more information: This feature is aimed at tablets, like the Pixel Tablet, and not phones.

Full details plus screenshots can be found in my latest article for Android Authority.
๐Ÿ’ฉ106๐Ÿ˜ข28๐Ÿ‘19๐Ÿ˜ญ14๐Ÿ˜7๐Ÿ‘Ž5๐Ÿ‘€4๐Ÿคก3๐Ÿคฃ2
Mishaal's Android News Feed
Google really doesn't want you to turn off Bluetooth. In light of the upcoming launch of the Find My Device network, Android 15 is adding a Bluetooth auto-on feature that can automatically turn on Bluetooth the next day if you disable it. You should stillโ€ฆ
In Android 15 Beta 1, a description has been added for when you toggle on "automatically turn on again tomorrow" in Bluetooth's Quick Settings dialog. This toggle is for the Bluetooth auto-on feature that I first reported for Android Authority.

There was already a description for when you toggle off this setting, which read "features like Quick Share, Find My Device, and device location use Bluetooth." But now there's a description for when you toggle it on, too, which reads "Bluetooth will turn on tomorrow at 5 AM."

So basically this change just tells us when the OS will automatically turn on Bluetooth if you leave the auto-on toggle enabled.

If you want to see a screenshot of the Bluetooth auto-on toggles, I shared one with my Patreon/Twitter subscribers. Otherwise, read my article on Android Authority for more details on this feature.
๐Ÿ‘48๐Ÿ‘Ž18โค10
Under Settings > Network & Internet > Internet in Android 15 Beta 1, when you open the details for the currently connected Wi-Fi network and tap on "Privacy", Android now opens up a full-screen settings page instead of a small dialog.

The page has the same "use randomized MAC" versus "use device MAC" settings but also adds a new "send device name" toggle. This is enabled by default and "share[s] the device's name with the network."
๐Ÿ‘48๐Ÿ”ฅ7
This media is not supported in your browser
VIEW IN TELEGRAM
Android 15 Beta 1 revamps the system animation for in-app (predictive back) navigation. Here's a look at the updated animation.

The back-to-home animation is unchanged and predictive back gestures are still disabled by default, though.
๐Ÿ‘100๐Ÿ‘Ž26๐Ÿ”ฅ7๐Ÿ˜ญ4๐Ÿ˜2๐Ÿฅฑ1๐Ÿ˜ด1
Android's updatable NFC stack is almost here! Android 15 Beta 1 quietly migrated Android's NFC stack from the system framework to a separate module, paving the way for NFC stack updates to be delivered by Google Play.

More details are available in my latest article for Android Headlines.

By the way, if you're wondering why NFC is broken in Android 15 Beta 1, Google made a mistake in the migration process. The OS is still looking for the NFC system app under /system when it should be looking for it under /apex.
๐Ÿ‘76โค14๐Ÿค”11
Android is finally preparing to support NFC wireless charging!

NFC charging is slower than Qi charging, but it needs much less space. USI 2.0 styluses already support NFC charging, and hopefully future tracker tags do too!

More details can be found in this article I wrote for Android Authority.
๐Ÿ”ฅ80๐Ÿ‘16๐Ÿคฏ16๐Ÿฅฑ2
The Pixel Watch may soon add support for syncing app permissions from your phone!

Back in October, I discovered a new "sync permissions" setting in Android 14 QPR1 Beta 2 that gives your connected Wear OS smartwatch the same app permissions you allowed on your phone.

Today, Nail Sadykov discovered that the Pixel Watch companion app is preparing to add support for this. After flipping a flag, a new 'device details' item appears in the companion app that says "remove watch, sync permissions, share contacts".

Tapping on this opens Android's Bluetooth device details page for your connected Pixel Watch, surfacing the "sync permissions from phone" menu item I previously discovered.
๐Ÿ‘51๐Ÿ”ฅ12๐Ÿฅฑ6
The Pixel Launcher app found on Google's Pixel devices is getting some new animations and quality-of-life improvements in Android 15.

They aren't live yet, but you can check them out in this article I wrote for Android Authority.
๐Ÿ‘81๐Ÿ‘8๐Ÿฅฑ5๐Ÿ‘Ž3โค2
Google had a multi-year plan to migrate the AOSP build system completely over to Bazel, but this project was cancelled late last year.

In a statement to OEMs last year, Google said "in a recent review of our progress, we concluded that the conversion to Bazel would take a lot more time than originally anticipated. After carefully considering our options, we decided to stop working on transitioning Androidโ€™s build system to Bazel, and instead focus on improving the existing system."

At one point, I'm told, Google even aimed to migrate all Make and Soong build files to bazel by Android 16 W. But that obviously won't happen anymore.
๐Ÿค”56๐Ÿ‘16๐Ÿ˜ญ9๐Ÿ‘€6๐ŸŽ‰5โค1
New TVs that launch with Android TV 14 or later on Linux kernel 5.15 or higher will be required to meet Google's Generic Kernel Image (GKI) requirements in order to pass certification!

This means that GKI is now enforced on all major Android form factors with AArch64 chipsets: handhelds, watches, automotive, & televisions.

"The Generic Kernel Image (GKI) project addresses kernel fragmentation by unifying the core kernel and moving SoC and board support out of the core kernel into loadable vendor modules. GKI also presents a stable Kernel Module Interface (KMI) for vendor modules, so modules and kernel can be updated independently."

GKI 1.0 was introduced in Android 11 for devices that launched with Linux 5.4.

GKI 2.0 was introduced in Android 12 for devices that ship with Linux 5.10 or later kernels.

Automotive devices used to be exempt from GKI requirements, but any cars running Android Automotive OS 13 or later on Linux 5.15 or higher are required to meet GKI 1.0 requirements.

Automotive devices are still exempt from GKI 2.0 requirements, though that doesn't seem to be the case for TV devices. The biggest difference between GKI 1.0 and 2.0 is that 2.0 devices ship with a Google-signed boot image.
๐Ÿ‘75๐Ÿ”ฅ10๐Ÿ†’6๐Ÿ‘Ž3๐Ÿค”2