Categories
Mobile Syrup

Microsoft working to bring Android 13 to Windows

Microsoft is working to bring Android 13 to Windows 11, along with a few new features like picture-in-picture (PiP).

As spotted by Windows Latest, Microsoft’s GitHub page for the Windows Subsystem for Android (WSA) includes a roadmap detailing upcoming plans for the WSA. The roadmap lists Android 13, as well as the following features:

  • file transfer
  • shortcuts
  • picture-in-picture (PiP)
  • local network access by default

The WSA, for those unfamiliar with it, is the foundation for running Android apps from the Amazon Appstore on Windows 11. Unfortunately, it’s not clear what this change will mean for the WSA. Likely, it will enable support for the latest APIs and any Android 13-specific features, but we’ll need to wait and see.

As for the other listed features, PiP is a standout. That should enable media from Android apps to display over other parts of Windows, but it remains to be seen how Microsoft implements the feature. Shortcuts may enable easier access to certain things within apps.

Unfortunately, the roadmap only reveals what Microsoft is working on, not how these things will work in practice. We’ll have to wait to learn more.

In other Android on Windows news, Microsoft recently expanded support to Canada and other regions.

Source: Microsoft Via: Windows Latest

Categories
Mobile Syrup

Pixel phones might get AI call enhancements in Android 13

The latest Android 13 beta rollout has unveiled a new ‘Clear Call’ toggle buried in the code.

The leak comes from notable Android enthusiast Mishaal Rahman on Twitter, where he’s pulled back the curtain on numerous Android 13 updates, including a new ‘Safety Centre,’ Spatial Audio and more.

Clear Calling is exciting since it should make making calls in loud spaces easier. Rahman claims that this feature will lower background noises when people are on a call. This works similarly to Google’s sound isolation techniques in Meet and with the new Pixel Buds Pro.

It’s worth noting that this only works on basic calls. If you’re already using Wi-Fi calling, which is usually much better quality, Clear Call doesn’t work.

As of the time of writing, this feature is still unavailable to most people, but it seems likely to become an official feature in a future update. Perhaps Google will even mention it during its fall hardware event in October.

Source: Mishaal Rahman

Categories
Mobile Syrup

Android 13 QPR1 Beta 1 code reveals more details of Pixel face unlock

Ahead of the release of Google’s Pixel 6 and 6 Pro, rumours swirled that the devices would support face unlock. However, the phones arrived without the ability to unlock with your face and ever since, publications have obsessively followed the software development of a face unlock feature now expected to arrive with the Pixel 7 series later this year.

The latest details come from 9to5Google, which dug into the Android 13 QPR1 Beta 1 software to examine new code related to face unlock. QPR1 is expected to hit stable in December, but the Pixel 7 and 7 Pro will arrive in October. Also, as with any software investigation like this, it’s important to keep in mind that pre-release and in-development features are subject to change. In other words, what 9to5 learned might not be an accurate reflection of the final product.

Anyway, let’s dig into what they found. First, 9to5 says it spotted several strings — snippets of code including text that will be shown on-screen for users — that describe certain aspects of face unlock. One string says that “Face Unlock works best when there’s enough light and you’re not wearing a mask or dark glasses.”

The bright light requirement effectively confirms that the face unlock feature will use the front-facing camera and not special hardware, like the Pixel 4 or Apple’s Face ID-capable iPhones. An important note here is that the Pixel 6 Pro selfie camera supports dual-pixel autofocus (DPAF), which can be used to develop depth maps of users’ faces. The Pixel 6 selfie camera is different, and likely won’t support face unlock based on DPAF, but the Pixel 7 and 7 Pro are expected to use the same selfie camera hardware with DPAF support.

9to5 also found details about how users interact with face unlock. According to details from the code, users will need to hold their phone at eye level to start the scanning process, and face unlock will only support one face.

Plus, 9to5 extracted a new animation for face unlock:

Credit: 9to5Google

Wrapping things up, 9to5 found details about the accuracy of face unlock, with a warning that face unlock is “less secure than a strong pattern, PIN, or password.” Other warnings include that looking at the phone may cause it to unlock when you don’t intend to, the phone can be unlocked if someone holds it up to your face, even if your eyes are closed, and the phone can be unlocked by someone else who looks a lot like you. Face unlock will require users to pick up their phone or tap the screen, indicating that scanning starts at that point.

Interestingly, code related to face unlock is referred to as ‘Traffic Light’ and was found on the Pixel 6 Pro running QPR1 Beta 1. 9to5 says it didn’t find similar references on the Pixel 6 or 6a.

Source: 9to5Google

Categories
Mobile Syrup

Android 13 will let employees open apps in work or personal profiles

Android 13 arrived in August, but a new blog post from Google highlights some improvements for businesses, such as enhanced ‘work profiles’ that make it easier for users to keep personal and work data separate.

Google says Android 13 brought a “smoother experience” to work profiles, making it easier for people to swap between them. For example, employees can now designate whether an app should open in their work or personal profile, depending on where it’s installed.

Google also says that there will be an option to access content through the web browser so it doesn’t impact personal apps — for example, an employee could open a work training video in the browser instead of YouTube so the video doesn’t mess up their personal watchlist.

Android 13 added the ability for employees to switch between work and personal photo galleries when sharing pictures with an app.

Smart dictation features got the work profile treatment on Pixel phones, too. That should prevent work jargon from spilling over into users’ personal dictation results. Work profile apps can now access NFC as well.

Image credit: Google

Google says there are other new features coming to Android 13 soon. The search giant specifically mentions ‘Phone Hub’ and other integrations between Android and ChromeOS, noting employees “will be able to securely respond to and access work information that’s on their phones — including messages, notifications and pictures — from their corporate Chromebooks.” Google says those interactions will be end-to-end encrypted.

Moreover, Google mentioned new features like ‘Lost Mode’ and ‘Stay Private on Work Wi-Fi’ will come to Android 13 in the future. The former allows IT admins to lock down and locate company-owned devices, while the latter can automatically encrypt and route network traffic from personal profiles when connected to company Wi-Fi.

Source: Google Via: The Verge

Categories
Mobile Syrup

Google Play system updates menu vanishes for some Android users

The ability to check for Google Play system updates has vanished for several Android devices from various manufacturers.

As spotted by 9to5Google, devices from Google, Samsung, Nothing, Xiaomi, Nokia, and Motorola have all lost the ability to check for these updates. It’s worth noting that Google Play system updates are separate from Android updates and exist as yet another way for Google to push new software and features to Android devices.

Previously, users could open the Settings app and navigate to Security > Google Play system update to view details about the current version and check if a new update is available. We actually detailed this process last week when outlining the new features available in the August 2022 Play system update.

Now, however, tapping the ‘Google Play system update’ option in the Security menu doesn’t do anything. It doesn’t open the update page, there’s no longer a ‘Check for update’ button; it’s just gone. It’s not clear if this is related to a bug, or if Google intentionally changed the behaviour.

Either is possible — on the bug side, I recall downloading the August Play system update to my Pixel 6a on the 19th after publishing MobileSyrup‘s coverage of what’s new in the update. However, my Pixel 6a says it’s still on the July update and tapping the Play system update doesn’t do anything. Similarly, a Pixel 6 I tested doesn’t let you click the Play system update option either. It’s also on the July update, but I don’t recall manually triggering the August update on it. It’s possible something in the August update caused this, but with both these phones listing the July update as the current one, I’m not sure.

9to5Google posits that Google changed the behaviour only to show the update page when there’s a new update. While possible, I wonder why the phones still show the July update when the August update is available and supposedly installed on my device.

Whatever the reason, it seems a little weird that the only way to manually trigger a Play system update suddenly vanished. Hopefully, Google provides some information about what’s going on.

Source: 9to5Google

Categories
Mobile Syrup

Android 13 brought new security measures, but malware can bypass it

Google rolled out new security measures in Android 13 to protect users from malware, and attackers have already come up with a way to work around the new protections.

ThreatFabric, which seeks to prevent fraud and cybercrime via threat intelligence, detailed a new exploit that builds on top of existing malware (via Android Police). The new exploit effectively disguises itself as an app store to bypass new security measures. However, to fully understand what’s going on here, you first need to look at what Google added in Android 13 to protect users.

According to Android Police, Google added a new security measure that prevents sideloaded apps (apps installed from outside of an app store) from requesting access to accessibility services. Accessibility services are an important part of Android, offering various tools to make smartphones easier to use for people with disabilities (for example, screen readers for people with visual impairments).

However, the nature of accessibility services means they’re vulnerable to abuse, making it easy for malware to snoop on private data, like passwords. ThreatFabric detailed some existing malware, such as the ‘Xenomorph‘ banking malware, which uses accessibility services to view what’s on screen and capture personal information like log-in credentials.

Hence Google’s new security measures, which block sideloading apps from requesting accessibility services (there is, however, a convoluted way to enable accessibility services on sideloaded apps if you need to do so). Given how important accessibility services can be, Google doesn’t want to outright ban apps from using them either. As such, Android 13 doesn’t block accessibility services for apps downloaded from the Play Store or other app stores — this exemption relies on the ‘session-based package installation API.’

Attackers working on malware that acts like an app store to bypass security

The reasoning here seems to be that app store operators vet their store platforms for malicious apps, and so apps installed from these stores are likely safe. However, the session-based package installation API is also the main avenue for bypassing the new accessibility services security measures.

ThreatFabric notes that developers with the ‘Hadoken group’ are developing a two-part malware exploit. The first part involves installing a ‘dropper’ app that acts like an app store. It then uses the session-based package installation API to install another app, which contains the malware. Because of this approach, the second app is able to bypass the security measures and request accessibility services.

Before you panic, ThreatFabric said the malware is still very buggy and likely still early in development. However, it expects the Hadoken group to keep working on it, and it sounds like this style of getting malware onto Android devices could become more common.

Users should be extra careful when granting accessibility services to an app. Android Police describes accessibility services as the “weak link” for a variety of malware. As such, users should only grant access to accessibility services to trusted apps.

Those interested can read all the details in ThreatFabric’s report here.

Source: ThreatFabric Via: Android Police

Categories
Mobile Syrup

Automatic clipboard syncing across devices no longer functioning on Android 13

Android 13 landed on Pixel devices on August 15th and brought a long list of new features and improvements, including app-specific languages, improved connectivity with ChromeOS, expanded Material You colour options, cinematic wallpapers, and more.

On the other hand, the introduction of the new OS has broken some things that worked optimally in the past, primarily, the ability for your clipboard to automatically sync with other devices using applications like Join and Pushbullet, first reported by AndroidPolice.

The Join app, in essence, allows you to sync your clipboard across your phone, your desktop and/or browser, allowing you to send text seamlessly from one device to the other. The feature works perfectly on devices running Android 12 or lower, but seems to be losing support on Android 13 due to a change in permissions that complicate accessing device logs. According to AndroidPolice, the Join app now would have to send a prompt every time it has to read the device logs, and the app needs to be running in the background to function.

Image credit: Mishaal Rahman

The app is still working; that is, it can still send clipboard text over to other devices, but instead of it being automatic, users are currently having to copy the text they want to send over, share it via the clipboard and then share via Join.

While Join developer João Dias has confirmed that he has started working on streamlining the manual syncing process on Android 13, Google has already made it clear via a Google Issue Tracker entry that “Disallowing background access is working-as-intended” and that it won’t revert back to its old ways. “We would discourage any type of automation testing relying on logcat. Trying to communicate with logcat without an interaction with the developer/users are not intended use case,” reads the entry.

Senior Technical Editor for Esper, Mishaal Rahman, did share a workaround using the Shizuku library, to give higher app permissions to applications like Join on Android 13, though it requires you to apply the workaround on every boot. You can read more about it here.

Source: AndroidPolice

Categories
Mobile Syrup

Google’s Pixel Tablet may run 64-bit-only Android 13

Google’s upcoming Pixel Tablet might run a 64-bit-only version of Android when it launches sometime next year.

The search giant didn’t reveal much about the Pixel Tablet when it announced the device at its Google I/O developer conference in May, and we’ve mostly been in the dark about it since. However, new details shared by Mishaal Rahman on Twitter suggest Google’s testing a 64-bit-only version of Android on the device.

Rahman tweeted a link to Google’s development resources, which indicate the company is experimenting with 64-bit-only Android 13 builds on a device with the codename ‘Tangor.’ Tangor, for those unfamiliar with the name, refers to the Pixel Tablet.

Going exclusively 64-bit would have several impacts. On the one hand, Android Police notes that cutting 32-bit support should reduce RAM use, but one downside would be that the tablet couldn’t run 32-bit apps anymore. That shouldn’t be a major issue, though, given that the Play Store has required that apps use a 64-bit architecture for a while.

In fact, Rahman details in a blog post that Google has been working towards 64-bit-only Android for a while, with last year’s Android 12 being the first version of the OS that can be compiled with 64-bit-only components. The same applies to Android 13.

Didn’t Apple do this in 2017?

Naturally, some may look and this 64-bit push and wonder what took Google so long. Apple moved the iPhone to 64-bit in 2017. The thing is, Apple’s iOS and Android are very different — Apple was more easily able to force a change because it has complete control over iOS and the App Store. For Google, Android’s scale and being open-source means the company has to take a slower approach to major changes like this so as not to isolate vendors or markets that still rely on 32-bit. A big example of this, as Android Police points out, is China (although Chinese app stores have agreed to start phasing out 32-bit apps).

Android Police notes that changes from chipmakers may also be a factor in this push. Most mobile phones use chips based on Arm chip designs, with newer designs only supporting 64-bit processes. That has led some chipmakers to include a small number of processors that support 32-bit, resulting in some odd, asymmetrical chip designs.

And presumably, if Google does go 64-bit-only with the Pixel Tablet, the company will likely do the same with its Tensor chip and Pixel phones in the future.

Of course, Google may also just be running internal tests to see how well a 64-bit-only device would perform. We likely won’t know for sure until the Pixel Tablet launches (it’s expected to arrive sometime in 2023). Still, it’d be nice to see Android go 64-bit-only, and if Google made the leap, other manufacturers would likely follow.

Source: Mishaal Rahman (Twitter), Google Via: Android Police

Categories
Mobile Syrup

Google’s Android 13 statue is a swingset that kinda looks like a butt

As is tradition, Google installed an official statue on its campus commemorating the Android 13 release. Except, as Android Police spotted, the statue kinda looks like the Android mascot (called bugdroid by many) grew a big ol’ butt.

The statue is supposed to be a swingset made out of the number 13 rotated on its side. Unfortunately, Google decided to make the crossbar of the swingset blue instead of green to match the sideways ‘3’ seat. Because of this, at a quick glance, it’s not super obvious that the swingset is the number 13 rotated 90 degrees.

Coupled with the bugdroid’s head appearing at the top in the same colour as the 3, it kinda looks like a butt (or perhaps other, more unsavoury parts of the human anatomy, depending on your imagination and where you draw the lines).

For those not able to go to Google’s campus and check out the new bugdroid buttdroid statue for yourself, Google also has an augmented reality (AR) version you can view online. The AR version does make the blue bar a little more prominent, but the butt is very much still there.

Beyond the new buttdroid display, the new statue joins the group of Android statues that don’t feature desserts. Back when Google still leaned into the dessert names for Android releases, we got neat statues that combined the bugdroid with Oreos, pies, ice cream sandwiches, and more. Those statues were fun, and definitely didn’t look like body parts.

Image credit: @tikurahulahul

Source: Twitter Via: Android Police

Categories
Mobile Syrup

Android 13 stable update breaks unified search for beta users

Users making the leap from the Android 13 beta to the recently released stable release may notice that the unified search has reverted to the years-old, basically useless Google search.

While it’s not entirely clear why the update reverted the search capabilities, Google is at least aware of the problem. According to 9to5Google, Google said an “upcoming release” will include a fix. Hopefully, that upcoming release arrives soon, as the improved device search is frankly one of the best parts of Android 13.

For those not familiar with unified search, or search on Pixels in general, well, it’s been a mixed bag for some time. The Pixel launcher has sported a Google search bar along the bottom of the home screen for years, but that bar was just a shortcut to search the web with Google. You could use it to search your phone, but the results were fairly limited.

With Android 12, Google revamped device search capabilities, adding a new search functionality to the app drawer in the Pixel launcher. This new device search was super fast and a great way to find stuff on your phone, including apps (plus shortcuts to things within some apps), contacts, and more. I’d say it felt more like the Spotlight search available on the iPhone. Unfortunately, this revamped search was only available in the app drawer and not from the Google search bar pinned to the bottom of every Pixel’s home screen.

Pixel launcher search

From left to right: Old web search, new unified search (on A13 Beta), device search

Android 13 changed that with a new unified search that offered both the faster device search and web searches right from that Google search bar. Personally, I wish I could turn off the web searches and just get the device search since unified search drops the helpful app shortcuts in favour of web searches. Either way, I loved having a reason to use the search bar on the home screen again.

Unfortunately, after the Android 13 stable update, tapping the Google search bar opens the old web search on my Pixel 6a (you can tell by the lack of Material You styling). However, I can still access the device search from the app drawer. This appears to be the case for any Pixel that made the leap from the beta to stable Android 13 — I have a Pixel 6 exhibiting the same behaviour after the update, while 9to5 says it experienced the issue on its Pixel 4a, 6, 6 Pro, and 6a units.

The search mixup isn’t the only issue plaguing the Android 13 update. Several Pixel users also reported getting an Android 12 update instead of the new Android 13, which has caused some confusion for users.

Source: 9to5Google