
Rita El Khoury / Android Authority
TL; Dr
- Android 16 Beta 4.1 delivers fixes for a handful of extant bugs.
- Beta 4 itself arrived again on April 17.
- With plans to hit secure in June, Google doesn’t have lengthy left to complete prepping Android 16.
Earlier at this time, Google drew the curtain again on Materials 3 Expressive, its newest design language revision that’s set to debut later this 12 months following the secure launch of Android 16. Whereas we’re understandably just a little bummed that we’ll have to attend only a bit longer to go hands-on with all of the modifications (regardless of the various early previews we’ve already seen), Google nonetheless has one thing new for us to take a look at at this time, as the corporate shares the newest level launch of its Android 16 Beta.
It’s been nearly one month since Google printed Android 16 Beta 4 for Pixel gadgets in its testing program. Not solely was this our second large Platform Stability launch, bringing us that a lot nearer to the day Android 16 secure would can be prepared for enterprise, however that was our first likelihood to attempt the software program out with the brand new Pixel 9a.
Google has simply launched Android 16 Beta 4.1. In the event you have been already testing Beta 4, simply chill and wait on your replace notification to reach. Like different current level releases, this one is all about bugfixes:
Haptics have been an actual thorn in Google’s facet with Android 16, and this isn’t the primary time we’ve seen a patch making an attempt to set issues proper. The battery drain drawback additionally seems like a difficulty we’ve seen pop up in growth earlier than, so hopefully Google is attending to the underside of issues now.
With the Beta 3 cycle, it was solely a matter of days between the preliminary launch and the primary 3.1 replace, itself swiftly adopted by 3.2. The truth that it took this lengthy for Google to go from Beta 4 to 4.1 may simply recommend that we’re near the tip of the street in terms of these fixes. With June proper across the nook, Google doesn’t have lengthy left to place all of the ending touches on Android 16.