Latest news with #Android16
Forbes
9 hours ago
- Forbes
Google Pixel's Unstoppable Android Updates Suddenly Stop
Has Android just changed? Google rarely surprises Android users, especially those with its own Pixels. But that's what has happened this month. The awkward optics of Pixel owners being first amongst equals compared to the vastly bigger Samsung user base has taken a sudden twist. As I reported earlier in the month, Android's July security update was not a security update at all. 'There are no Android security patches in the July 2025 Android Security Bulletin,' Google said, with 'no security patches' for Pixels either. The disparity between Pixels and Samsungs was becoming a real thing. Google's phones received Android 15 more than six months before recent Galaxy flagships, and then just as Samsung's phones saw that upgrade, Pixels were already moving to Android 16. But that same pattern has also been seen each month. A fast, efficient and 'seamless' Pixel monthly security update versus the fragmented, labored Samsung equivalent. But this month Samsung's security update looked like business as usual, whereas Pixel's was anything but. This is the first time in almost a decade — since August 2015 — that Android's monthly security update has drawn such a blank. The reality is somewhat different. There were Android updates for July making their way onto Pixel phones as part of an Android 16 update, but for users on older versions of the OS or with older devices, this doesn't help. There are now more than 1 billion Android devices that fall foul of Google's cutting off security updates for Android 12 and older phones, and also from its tweaking its Play Integrity API to disfavor apps running on these unsupported versions of the OS. If you own a phone running Android 12 or older, you should really stump up for an upgrade. Per Security Week, 'this is the first month without security updates since Google started rolling out monthly Android fixes in August 2015, looking to make the mobile operating system safer for both users and vendors.' And that also feels like a 'thing.' But as for whether this is just a blip in the Samsung versus Pixel stakes, we'll know soon enough. Google's phone is racing ahead with Android 16 and new security and privacy features, while Samsung awaits its own rollout. It's likely nothing has really changed.
Time of India
a day ago
- Business
- Time of India
Google is merging ChromeOS and Android, and this is what it means for users
Google is finally merging ChromeOS and Android into a unified operating system . Sameer Samat, president of Google's Android ecosystem, revealed the merger during an interview with TechRadar, stating: "We're going to be combining ChromeOS and Android into a single platform." Samat, per TechRadar, expressed particular interest in understanding how users interact with their laptops, suggesting the merger aims to enhance productivity across devices. The exec's comments are Google's most direct acknowledgment of the platform consolidation, which industry observers have anticipated for nearly a decade. The merger is expected to streamline development resources while creating a more cohesive user experience across smartphones, tablets, and laptops. This unified approach mirrors Apple's integrated ecosystem , where devices seamlessly work together through consistent software experiences. What changes for ChromeOS and Android users The merger isn't entirely surprising given Google's recent strategic moves. In June 2024, the company announced that ChromeOS would be "developed on large portions of the Android stack," effectively beginning the integration process. Chromebooks already support many Android applications, creating a foundation for the unified platform. Meanwhile, Android has been adopting desktop-friendly features, including improved window management, external display support, and a desktop mode reminiscent of Samsung's DeX interface. So, one could say that these developments in Android 16 have been signal to Google's preparation for the merged platform. While nothing major changes for users, especially Android users, ChromeOS users could benefit from a larger app library. Developers won't have to develop separate apps for ChromeOS anymore, and Android apps should work seamlessly on ChromeOS devices. Google's move could significantly strengthen its position in the large screen devices market, where both ChromeOS and Android currently lag behind Apple 's macOS and Android on Tablet. AI Masterclass for Students. Upskill Young Ones Today!– Join Now
Android Authority
2 days ago
- Android Authority
Android's new design is bouncy and I'm all for it
Joe Maring / Android Authority From blobs to bounce to bright colors, your phone is about to look and feel a lot different, with Google bringing more of an opinionated approach to its design than we've ever seen before. In the world of software design, many are used to looking to Apple for inspiration, but Google's Material Design bucks that trend with its boldest and most daring design strategy yet. Is Google's more playful approach going to be a hit and entice an entirely new type of consumer to give Android a try? Or is it just going to alienate longtime Android users? In my time with the latest Android 16 beta, I've encountered some of these new design elements, while some are not yet implemented. Let's dive into a few of my favorite interactions. Bringing Android to life with a bounce There's a new bounce throughout Android as a whole. That's the best word I can think of to describe how it looks and feels, and it makes the OS feel more functional, playful, and interactive, bringing it to life in a way that previous versions did not. The changes are subtle but important, adding up to an overall design that feels fluid and fun. The most obvious example of this is the new notification panel. Swiping to dismiss an alert now feels like you're peeling the notification away from the stack, in the best possible way. Swipe slowly to really see all the different aspects of this seemingly simple interaction all come together. The corners morph from slightly squared off to more round, the surrounding notifications move ever-so-slightly in the same direction as your swipe, and just at the right moment — about 10% of the way into your swipe — haptic feedback signals the point at which your chosen notification detaches from the stack, all while the remaining notifications bounce gently back into place. All of that comes together to create a really satisfying swipe gesture. Before this change, a notification dismissal felt independent of the surrounding notifications. You'd swipe, the box would fly off the screen, and the stack would collapse together to fill the space. While it worked fine then, the whole experience just feels more cohesive and intentional now. And again, that snap — or haptic feedback, rather — when the notification detaches from the rest of the stack is super satisfying. There's a new bounce throughout Android as a it makes the OS feel more functional, playful, and interactive in a way that previous versions did not. Another example of Google's move toward motion is the increase in shape shifting with Material components. Google's updated design documentation now contains a ton of new tools and guidelines to create a more animated UI, like button groups, where the selected button morphs into a more oval-like shape, while the unselected buttons remain more squared off. You can already see this shape shifting in the new Quick Settings panel. When you turn on the flashlight, for example, the button goes from a rounded oval to a rounded square. This is a nice way to quickly visualize which buttons are activated and which aren't. And of course, there's that bounce again. The surrounding buttons animate with a bounce with each tap of the flashlight button, again leading to a more cohesive experience. Since we're still in beta, there are still a lot of new design elements on the way. You can check out the full list of Material 3 Expressive components in Google's documentation. It only matters if Google cares enough Google is making it clear: it wants Android and apps on the platform to come alive. And it means it, too, so much so that it includes an entirely new motion physics system in M3 Expressive, designed to allow developers to customize the physics of their apps more easily than previously possible. This is something I'm particularly excited about, and I really hope Google and third party developers alike implement this in tasteful ways, leading to apps that feel right at home in this new evolution of Android. That's a really important point, though. All of this sounds great — and so far, from what I've seen, looks great — but will developers buy into this new design language? Will Google itself implement it into their own apps, thus taking the lead and setting the example for what M3 Expressive is all about? There are already traces pointing to some of Google's main apps implementing the new design language, but only time will tell if other developers will follow suit. Based on what you've seen, do you like the added animations in Android 16? 1 votes Yes, but I hope Google doesn't overdo it. 0 % Yes, and I hope they continue to add more throughout the OS. 100 % No, Android is already animated enough. 0 % I don't use Pixel launcher, so I'll probably never see this anyway. 0 % I've used Android for a long time now. Pixel 2 XL was my first Android device, though, so I know many of you have used Android a lot longer than me. This has me wondering what more tenured Android enthusiasts think of this design direction. Historically, Android didn't use nearly as much motion, which may be preferred by some longtime users. With the new direction, it appears Google is going for a more mass market appeal, and I'd argue this is the right move, positioning Google to appeal to a generation of users who are used to, say, the fluidity of iOS, but maybe they're looking at trying Android thanks to Google's promising AI features. Google is making a huge bet here with Material 3 Expressive. The motion adds a fluidity that was lacking in previous versions of Android, a cohesiveness that now feels obvious, and a whole new way for developers to make their apps more beautiful and more functional. The goal is seemingly in the name itself — Material Design — and all these new animations definitely make your device seem more like a material you can feel.
Yahoo
4 days ago
- Yahoo
Google releases Android 16 QPR1 Beta 2.1 with a fix for your broken back button
Beta testing for Android's biggest redesign in years is humming right along, with Google already having released Android 16 QPR1 betas 1, 1.1, and 2 in June alone. The new version isn't expected to hit the stable channel until September, but Google is already back with yet another update to the firmware that will eventually become the next Pixel Feature Drop. Google announced Android 16 QPR1 Beta 2.1 on Reddit today, and the update is already rolling out to enrolled devices. This new build clocks in at about 5MB in size, so there's nothing earth-shattering involved here, but it does bring a few important fixes, as outlined in the release notes. Android 16 QPR1 Beta 2.1 (June 2025) This minor update to Android 16 QPR1 Beta 2 includes the following fixes: The "Approve" button in the Device Admin settings is transparent and invisible (Issue #419144521) The lockscreen sound toggle shows as off, but sounds still play (Issue #423985494) The Android back button intermittently fails to function (Issue #412691179, Issue #417434626, Issue #420283260) Fix for a launcher crash when swiping up from the bottom All eligible devices enrolled in the Android Beta for Pixel program will be offered an over-the-air (OTA) update to QPR Beta 2.1. The biggest fix here resolves an issue where the back button and swipe gesture were refusing to register, forcing affected users to restart their phones to get things working again. This has also been a problem for users on the Android 16 stable release as well, though people running that version will have to wait a bit longer for the fix since today's update is only being made available to devices enrolled in the Android Beta Program. Google had previously acknowledged the back button bug and promised that a fix was on the way. For anyone on the stable channel, we're expecting that update to come alongside the July security patches within the next couple of weeks. We're already seeing the update on multiple Pixel devices. It has a build number of BP31.250523.010, and as mentioned earlier, it's a smaller download at roughly 5MB. For once, it doesn't take very long to optimize after downloading, so you should be able to get it fully installed in under 30 minutes. The update is being made available to all of Google's phones, tablets, and foldables dating back to the Pixel 6, provided they're enrolled in the beta program. To see if it's available on your device, head to Settings → System → Software updates → System update → Check for updates.
Yahoo
4 days ago
- Yahoo
Android 16's back button bug is fixed, but you'll still have to wait
It's been nearly a week since Google rolled out the stable Android 16 build for Pixel devices. While the update brings a few cool features and has been mostly stable, it also introduces a couple of issues. Soon after Android 16 began rolling out, users reported the back navigation gesture becoming unresponsive. Earlier today, reports surfaced of Tap to Wake not working on some Google Pixel devices after updating to Android 16. Thankfully, Google seems to have fixed the former. Earlier this week, multiple users noted that the back gesture had stopped working properly on some devices, leaving users with no choice but to restart their phones to restore functionality. There were also reports of the 3-button navigation bar freezing and not working correctly, particularly on Pixel 8 and Pixel 9 series devices. But it appears Google has found a fix. Google reached out to Android Police co-founder Artem Russakovskii, confirming that the company has already fixed the bug affecting the back gesture. However, the update with the fix hasn't rolled out yet. It appears Google will include the patch in the next Android 16 update. While the issue doesn't seem to be widespread, if you're still facing it, restarting the device is currently the only workaround. Some users noted that the bug surfaces more often when using third-party launchers, and switching back to the Pixel Launcher might help. Still, it's frustrating that Google has addressed the bug internally but hasn't released the fix. We don't yet know when the next Android 16 update will arrive, but the best guess is sometime next month alongside the July security patch — meaning users might wait another two weeks for the fix to arrive. In addition to the back gesture issue, some users have also reported problems with scheduled dark/light mode not working, though Google has not yet commented on a fix for that.
