Latest news with #MishaalRahman
Android Authority
2 days ago
- Business
- Android Authority
Don't panic: Google is still working on splitting Quick Settings, but it'll be optional
Mishaal Rahman / Android Authority TL;DR Google is developing a new, optional split design for Android's Quick Settings and notifications panels, separating them into distinct pages. This 'separate' view will require swiping from the top right for Quick Settings and top left for notifications, contrasting with the current 'combined' view. While the feature's release is uncertain, it's actively being developed and might appear in a future Android 16 quarterly update. Google is set to roll out a major overhaul to Android's user interface this year, introducing the company's new Material 3 Expressive design to the OS. As part of this redesign, Google is revamping Android's Quick Settings panel to add Material 3 Expressive flair and deliver several functional improvements. The company showcased these Quick Settings changes earlier this month, even inviting users to test them in the Android beta program. However, Google didn't reveal that its work on the Quick Settings panel isn't finished, as it plans another significant revamp, possibly slated for an upcoming quarterly release of Android 16. During The Android Show: I/O Edition, Google showcased the Quick Settings revamp slated for release later this year. This updated Quick Settings panel introduces background blur, resizable tiles, one-click toggles for Bluetooth and Modes, a cleaner tile editor, and a redesigned brightness slider. The revamped panel is live in the Android 16 QPR1 Beta 1 update that Google released last week, but this is only part of the picture. Google is actually quietly working on an entirely different version of the Quick Settings panel: one that's separated from the notifications panel. Last year, I uncovered evidence that Google was preparing to separate Android's notifications and Quick Settings panels. The company's goal was to divide them into distinct pages, thereby creating more room for both notifications and Quick Settings tiles. This approach mirrors the design many OEMs, such as Samsung, Xiaomi, and OnePlus, currently feature in their Android builds. In-development notification panel UI in Android 16. Following Android 16's third beta release, we observed that Google's new split panel design had made significant progress. However, several issues persisted. When Google announced Material 3 Expressive earlier this month, many assumed the company had abandoned the split panel design because it wasn't showcased during The Android Show and isn't present in the Android 16 QPR1 beta. However, we've recently found strong evidence suggesting the split panel design is still in active development. More importantly, evidence indicates it will likely be an optional feature. While digging through the Android 16 QPR1 Beta 1 release, we spotted strings indicating Google plans to add a new 'Notifications & Quick Settings' option under Settings > Notifications. This page will allow users to switch the panel design from the current 'combined' view to the new 'separate' view. Notably, the 'combined' view is labeled 'classic.' The 'combined' panel, accessed by swiping down anywhere from the top of the screen, merges notifications and Quick Settings into a single interface, as its name implies. Conversely, the new 'separate' panel divides notifications from Quick Settings, requiring a swipe down from the top right to open Quick Settings and from the top left to access notifications. Code Copy Text Notifications & Quick Settings Panels Separate Swipe down from the top right to open Quick Settings. Swipe down from the top left to open notifications. Combined (classic) Swipe down from the top of your screen to access the classic panel that combines notifications and Quick Settings. The image below illustrates the anticipated look of the new Notifications & Quick Settings page in Android. Note that neither this page nor the split design itself is currently live in Android 16 QPR1 Beta 1. Furthermore, the animation displayed on this page is a placeholder, as Google has yet to develop a custom version. Mishaal Rahman / Android Authority While the rollout timing for this new split panel design remains unknown, we now know it hasn't been abandoned. This feature could arrive with the other Material 3 Expressive changes in the Android 16 QPR1 release, or potentially later, such as in Android 16 QPR2. When it does arrive, its availability across all devices is uncertain. A special footer message, appearing only on foldable devices, notes that the 'combined' panel is limited to the outer screen. Although we haven't seen any indication that this split panel design will be exclusive to foldable phones, this message could suggest that possibility. Code Copy Text Combined (classic) view is limited to the outer screen of your foldable device Furthermore, it's unclear whether this split panel design will be enabled by default. We hope it won't be, considering the negative reaction when Samsung implemented a similar default in One UI 7. We'll be sure to update you if we learn more about Google's split panel design. Got a tip? Talk to us! Email our staff at Email our staff at news@ . You can stay anonymous or get credit for the info, it's your choice.
Android Authority
2 days ago
- Business
- Android Authority
Samsung's One UI 8 beats Google to the punch with new 90:10 multitasking split
Mishaal Rahman / Android Authority TL;DR Samsung's first One UI 8 beta for Galaxy S25 introduces an advanced split-screen feature using a new 90:10 split ratio. This 90:10 split ratio allows apps to occupy a lot of screen real estate, and lets users quickly switching focus between the two apps without reducing productivity. OnePlus pioneered this 90:10 split with its Open Canvas feature, and Google is working on bringing it to Pixels, possibly with a future QPR release. One UI 8 beta program is now live for Galaxy S25 users, allowing us to see what Samsung is developing before the stable update rolls out. With this new Android 16-based update, Galaxy S25 users can now try out the upcoming 90:10 multitasking split, which is scheduled to come to Pixel devices with the Android 16 QPR1 update and probably to the rest of the Android ecosystem with Android 17. One UI 8's changelog mentions the following change under the Multitasking header: Enhanced split screen view: While 2 apps are open in split screen view, you can push one app against the edge of the screen to keep it partially visible while giving most of your focus to other app. Tap the smaller app any time to switch between them quickly. Here's a quick demo of the change, showing two apps in split-screen view: As you can see in the demo above, the split-screen view starts in 50:50 mode, but you can easily resize any app to become the dominant app, occupying 90% of the screen. The dominant app becomes significantly easier to use thanks to the abundant screen real estate. If you want to switch to the secondary app, you can tap on it to quickly make it the dominant app. This way, you can easily use two apps side by side in a 90:10 swappable split, without compromising the user experience as much as you would with a 50:50 split. This change would be very familiar to those following our Android 16 coverage. Google has been spotted improving Android's split-screen mode to support this new 90:10 ratio. Mishaal Rahman / Android Authority Here's a demo of the feature from Android 16 betas: This split-screen implementation is clearly inspired by the Open Canvas feature on OnePlus phones, which functions very similarly to what Google is developing. The feature, as available on OnePlus phones running Android 15-based Oxygen OS 15, is showcased below: Google hasn't officially announced this change, but we expect it to come to Pixel devices with Android 16 QPR1 or a later QPR. Once Pixels get it, the change could be incorporated into the wider Android platform with Android 17. Samsung has beaten Google to the punch here, incorporating the change with Android 16-based One UI 8, though OnePlus remains the first to the party. Either way, we're glad to see that more Android users will very soon get access to improved multitasking capabilities. Got a tip? Talk to us! Email our staff at Email our staff at news@ . You can stay anonymous or get credit for the info, it's your choice.
Android Authority
3 days ago
- Business
- Android Authority
Google Play's latest security change may break many Android apps for some power users
Mishaal Rahman / Android Authority TL;DR Google's updated Play Integrity API is making it significantly harder for users with rooted phones or custom ROMs to access certain applications due to enhanced security verifications. The update, now rolling out by default as of May 2025, enforces stricter hardware-backed security signals for integrity verdicts on devices running Android 13 or later. While this change aims to protect apps from abuse, it negatively impacts legitimate power users and potentially those on older devices lacking recent security patches. Compared to the billions of regular Android users, the number of people who root their Android phones or install custom ROMs is minuscule. While I wouldn't say Google is actively hostile towards these power users, the company's efforts to strengthen Android app security have the unfortunate side effect of negatively impacting their experience. Google's latest update to the Play Integrity API, for example, makes it easier for developers to protect their apps from abusive users while also making it significantly harder for legitimate power users to utilize certain applications. The Play Integrity API is a tool developers can use to verify that inbound interactions and server requests come from an unmodified version of their app binary running on a genuine Android device. Many developers use this API to mitigate app abuse that could lead to revenue or data loss. For example, the API can help prevent users from accessing premium content without paying, or it can help safeguard sensitive financial data by preventing access on devices that could potentially be compromised. Google The problem for power users who root their phones or install a custom ROM lies in Google's definition of a 'genuine' Android device: one running a Google Play-certified build of Android. This definition inherently excludes nearly every custom ROM, prompting many custom ROM users to employ hacks to spoof certified builds. While many people who root their phones don't install a custom ROM, they do unlock the bootloader as part of the rooting process. This step causes their devices to fail the more stringent Play Integrity checks, locking them out of many dining, medical, gaming, banking, and payment apps, as these types of apps often utilize the API's stricter evaluations. Previously, the Play Integrity API and its predecessor, the SafetyNet Attestation API, weren't as much of a concern for power users, as they could often find easy workarounds. However, Google has been moving to enforce hardware-backed security signals. These are significantly harder to bypass because, unlike simpler past methods, they are rooted in the hardware itself. While these hardware-based checks offer more robust security, power users had found some reprieve in the fact that Google wasn't universally enforcing their strictest application. Furthermore, it was up to app developers to decide whether they wanted hardware-backed security signals to be enforced. This gave developers the flexibility to restrict their apps' usage as they saw fit. For example, banking or payment apps often went out of their way to check that devices passed hardware-backed signals, but now, these signals are part of Play Integrity's baseline for all integrators of the API. In December of last year, Google announced a major update to the Play Integrity API that enhances the 'basic,' 'device,' and 'strong' integrity verdicts on devices running Android 13 or later. The 'device' and 'strong' integrity verdicts are the two more stringent verdicts apps can receive when calling the Play Integrity API. The 'basic' verdict, while less stringent, is also not as widely used by developers seeking higher levels of security. Google In the past, only the 'strong' integrity verdict used hardware-backed security signals. Starting in December of last year, however, Google made all integrity verdicts even stricter: the 'device' integrity verdict was updated to also use hardware-backed security signals, while the 'strong' integrity verdict was revised to require a security patch level from within the last year. Meanwhile, the 'basic' integrity verdict was also updated to use hardware-backed signals, though due to its less stringent requirements, it passes even on devices with root enabled or the bootloader unlocked. Google's stated reasoning for this change was to make the Play Integrity API faster, more reliable, and more private for users by reducing the number of signals that need to be collected. These changes also make the API harder and more costly for attackers to bypass. At the time of the announcement, these updated integrity verdicts weren't immediately enforced. Google made them opt-in for developers but stated that all '[Play Integrity] API integrations would automatically transition to the new verdicts in May 2025.' Well, it's now May, and Google is making good on its promise. At Google I/O 2025, the company announced that it had flipped the switch and made all integrity verdicts stronger by default. During the 'what's new in Google Play' session, Raghavendra Hareesh, the Lead of Play Developer and Play Monetization at Google, said that the company is 'rolling out stronger verdicts for all developers with no additional developer work required.' 'The Play Integrity API is a vital tool in any comprehensive security strategy. Helping you defend your entire app experience. It's crucial in preventing abuse that can lead to revenue loss and also harm your users. Developers who have been using this API are seeing over 80% lower unauthorized usage compared to other apps. That means less fraud, less cheating, or data theft. And we are continuing to evolve this Play Integrity API to stay ahead of all the threats that are out there. So today we are rolling out stronger verdicts for all developers with no additional developer work required. This makes it faster, more reliable, and more privacy-friendly to check if a device is trustworthy. Developers can also now check if a device has recently installed a security update, which is very important for apps which are protecting sensitive actions.' Raghavendra Hareesh, Lead of Play Developer and Play Monetization at Google This means that power users who root their phones or install a custom ROM may suddenly find some apps stop working, especially on devices running Android 13 or later. Even users with unmodified Android 13+ devices might face problems if their devices haven't received a software update in a while. This is because apps checking the 'strong' integrity verdict require a recent security patch level to pass. Mishaal Rahman / Android Authority Error message in the Pokémon Go app when the device fails its Play Integrity checks Google's full implementation of hardware-backed security signals has been anticipated for some time. While power users previously found simple ways to bypass earlier measures — often by tricking the Play Integrity API into relying on more easily spoofed software-based checks — these methods were never permanent solutions. It was, therefore, only a matter of time before these users would encounter broken apps. Soon, easy workarounds will likely vanish, leaving users with no choice but to either resort to shady keybox leaks or to restore their devices to stock. So, while Google's primary aim with these changes is to improve app security for everyone, they nonetheless degrade the experience for these power users. Thanks to security researcher linuxct for his inputs on this article! Got a tip? Talk to us! Email our staff at Email our staff at news@ . You can stay anonymous or get credit for the info, it's your choice.
Android Authority
3 days ago
- Business
- Android Authority
Google's getting some new voices on your phone (APK teardown)
Mishaal Rahman / Android Authority TL;DR A few months ago, Google introduced four new voices for AI Mode for Search in a Google app beta. In the latest beta, those voices are no longer limited to AI Mode. You can now hear those same voices when you perform a voice search through the mic icon. Gemini Live offers a wide range of AI voices to choose from, allowing you to find the one that's most pleasing to your ear. Google also recently added voice options for Search's AI Mode. Now there's another area where you'll be able to customize your AI voice preferences. Authority Insights story on Android Authority. Discover You're reading anstory on Android Authority. Discover Authority Insights for more exclusive reports, app teardowns, leaks, and in-depth tech coverage you won't find anywhere else. An APK teardown helps predict features that may arrive on a service in the future based on work-in-progress code. However, it is possible that such predicted features may not make it to a public release. When we discovered earlier this year that Google was planning to add voice search capabilities to AI Mode for Search, we found that users would have four different voices to choose from. At the time, the voice settings page listed these options as Jungle, Lime, Royal, and Sapphire. However, we later found that the names were changed to something more space-related: Cosmo, Neso, Terra, and Cassini. Although these voice options were initially only available for AI Mode, it looks like these voices won't be limited to just that feature anymore. AssembleDebug / Android Authority In our latest APK teardown of the Google app (version beta), we have learned that you'll also hear these same four voices when you perform a voice search through the mic icon. This is the case for the Pixel launcher/widget and for the Google app's homescreen. Previously, this feature only used a single female voice. In the video below, you can hear the Neso voice in action. AI Mode for Search just recently rolled out broadly for users in the US. If you haven't tried it yet, see what we thought of the feature in our hands-on. Got a tip? Talk to us! Email our staff at Email our staff at news@ . You can stay anonymous or get credit for the info, it's your choice.
![[Open Thread] Google may have changed the face of visual media forever, but is it for the good?](/_next/image?url=https%3A%2F%2Fwww.androidauthority.com%2Fwp-content%2Fuploads%2F2025%2F04%2FVeo-2-in-Gemini-on-an-Android-phone-scaled.jpg&w=3840&q=100)
Android Authority
7 days ago
- Entertainment
- Android Authority
[Open Thread] Google may have changed the face of visual media forever, but is it for the good?
Mishaal Rahman / Android Authority 🗣️ This is an open thread. We want to hear from you! Share your thoughts in the comments and vote in the poll below — your take might be featured in a future roundup. I'm going to be real with you: Google Veo 3 is by far the most disturbing product launched by the company this year, perhaps ever. With a simple prompt, anyone can create a short movie, commercial, or some other dystopian brand of visual story that blurs the lines of reality and simulation. My colleague Adamya Sharma collated some of the creepiest and, indeed, coolest examples from people using Veo 3. The results are remarkable, and the characters disturbingly uncanny. Even dogs and cats look lifelike. It's incredible how far we've come with this technology in a few short years. But this begs the question: who needs a video camera, directors, sound designers, animators, editors, set designers, marketing professionals, or even film stars when this tech exists? Hell, you could pay for Google AI Ultra right now and make a documentary about Will Smith's love for pasta. I'm interested to hear how you think developments like Veo 3 will change the face of visual media for better, worse, or some awkward niche in between. So here are the questions: What are your impressions of Veo 3? Impressed? Creeped out? Can you tell the difference between a human-made production or one made by AI? Should there be stricter laws governing the creation of AI media? How would you use a tool like Veo 3 if it was made freely available? Have you used AI to generate videos? 0 votes Yes, I use it often NaN % Yes, I've tried it once or twice NaN % No, but I'm interested in it NaN % No, and I have no plans to do this NaN % 👇Sound off in the comments: What do you think of the future of AI video creation — terrific or terrifying?
