Google starts rolling out the Android 14 Beta 2 update for testers using Pixel smartphones. As Samsung’s One UI 6 will be based on Android 14, the development progress and stability enhancements are necessary for a seamless and worry-free One UI Beta Program.
According to the information, Google’s Android 14 Beta 2 update adds support for built-in and custom predictive back animations. With the first Beta, the company introduced a new Back Arrow, which now gained support for predictive back animations.
Adding to this, the latest Beta firmware brings secure full-screen Intent notifications and makes data safety information more visible. Besides, there are a lot of issues been fixed that were reported by the developers’ community and end-users.
Stable Android 14 Release
Google has announced that the stable release of Android 14 is expected in August 2023. The first developer preview of Android 14 was released in February 2023, and subsequent beta releases have been released every few weeks. The final beta release is expected in July 2023, and the stable release will follow shortly after.
Android 14’s a big update for Samsung
Android 14 will bring a number of new features and improvements, including a new design language, privacy features, and performance improvements. Samsung has been working closely with Google to develop Android 14, and it is expected that the update will be well-integrated with its own software features.
What’s new in Android 14 Beta 2
Android 14 Beta 2 includes some new features and changes to try out:
- Add support for built-in and custom predictive back animations
- Secure full-screen Intent notifications
- Data safety information is more visible
Top resolved issues
The following issues have been resolved in Android 14 Beta 2:
- Fixed a platform stability issue that could cause the UI to lag or freeze, apps to crash, or the device to crash.
- Fixed an issue with the fingerprint sensor that prevented new fingerprints from being added for Fingerprint Unlock in some cases.
- Fixed issues with UPI and biometrics that could cause some apps to not work properly.
- Fixed an issue where a device couldn’t be unlocked using a fingerprint after tapping a notification or choosing a notification action on the lock screen.
- Fixed an issue on some devices that caused sound to play through the speakers instead of headphones that were connected.
- Fixed an issue that caused icons on the home screen to appear almost invisible.
- Fixed issues with gesture navigation that occurred when using a custom launcher:
- The Home screen content wouldn’t display and the animation would fail to render when swiping up to go Home.
- The list of recently used apps couldn’t be accessed using the normal gesture.
- Fixed issues that prevented users from interacting with notifications in the notification shade.
- Fixed an issue that could cause a device to crash after finishing audio or video calls.
Other resolved issues
- Fixed an issue where, after entering and exiting picture-in-picture mode, the screen flickered when any apps were launched.
- Fixed an issue where user restrictions set by DPC admins were not being enforced in Settings.
- Fixed an issue where, after taking pictures with the Google Camera app, opening the latest picture from the thumbnail in the app briefly displayed a green-colored shade over the image.
- Fixed an issue that could cause the battery percentage to be displayed as 0% after a device reboot regardless of the actual charge level of the device.
- Fixed an issue that could cause a device to crash, and then when the device rebooted any wallpapers that were selected before the reboot were reset.
- Fixed issues that prevented the Better Bug app from uploading bug reports.
- Fixed issues that caused the back-to-home gesture to stop working.
- Fixed an issue that could cause the system Settings app to crash repeatedly.
- Fixed an issue that prevented users from searching within the system Settings app.
- Fixed issues that sometimes caused null pointer exceptions for input method editors (IMEs).
- Fixed an issue that sometimes increased system-wide memory usage unnecessarily.
- Fixed system issues that could sometimes cause deadlocks.
| Source |
Android 15 may speed up webpages loading for apps
Android 15 is the upcoming major update, which will bring new features and some significant improvements over the current version. One of the changes that Android 15 could introduce is the ability to pin Android System WebView into memory, which could speed up the browsing experience.
Android System WebView is a part that allows apps to display web content without opening a separate browser app. Many apps use WebView to access various features, such as showing login screens, help pages, or full articles.
WebView is based on the same code as Google Chrome, but it is updated separately. To save space on the device, Google created a shared library called Trichrome.
According to information (via AndroidPolice), Google may pin the base APK of the trichrome library to memory with Android 15, which means it will not be removed from memory when the user opens a big-size app. This could reduce the loading time of web pages and make the browsing experience smoother.
The feature is currently enabled in Android 15 Developer Preview 1, but it may change or be removed in future versions. Android 15 is expected to be released later this year, with new features and improvements for Android users.
Google temporarily stops Android 15 DP1 downloads amid device corruption bug
Last week, Google rolled out the first developer preview of its next version operating system – Android 15, and the firm now temporarily stopped DP1 downloads amid a device corruption bug. However, this news may disappoint users who were all set to try the new offerings.
According to the details, Google states on its Android Developers page that we’ve temporarily disabled downloads for Android 15 DP1 OTA images. The reason for this abrupt pause happens to be a known issue that shows a Device is corrupted message, which occurs when sideloading OTA images.
However, an issue with sideloading the Developer Preview 1 build can sometimes cause users in trouble, so to maintain reliability, Google pauses the downloads of Android 15 first developer preview until the firm can further troubleshoot the issue.
To work around this issue, Google recommends developers flash a factory image to test devices instead. Simultaneously, this news primarily impacts developers, as this is an early build, and probably not even that much since developers would probably end up flashing their devices anyway.
However, currently, there’s no information available on when the issue will be resolved and downloads will resume, so all you can do is wait, because it’s better to be late than corrupted.
Android 15 might stop some apps from reading notifications with OTP
The countdown for the next iteration of the operating system has begun, as Google already dispatched the first Developer Preview of Android 15. Therefore, the code within Android 15 suggests that Google might stop untrusted apps from reading notifications with OTP.
The QPR3 Beta 1 update of Android 14 shows a new option named RECEIVE_SENSITIVE_NOTIFICATIONS. This permission has a protection level of role signature, which means it can only be granted to applications with the requisite role or to applications that the OEM signs.
While the exact role that grants this permission hasn’t been detailed yet, likely, that Google doesn’t intend to open this permission up to third-party apps. Hence, Google might be planning to crack down on a known Android security attack method with the upcoming OS – Android 15.
Various apps use passkey or enable two-factor authentication. While some forms of two-factor authentication are more secure than others, some platforms only support the most basic methods, wherein your one-time passwords (OTPs) are sent via email or text.
These methods are convenient since they don’t require additional setup, but they are also less secure since they’re easier to intercept. So, to reduce the risk of data loss, Android 15 might add a new feature that will stop untrusted apps from reading notifications with OTP.
However, currently, it’s hard to describe which apps will count as an untrusted app but we can say that Android will have many ways to protect users from leaking their 2FA codes to third parties. Like the OTP_REDACTION, which suggests that Google will stop users from leaking their 2FA codes on the lock screen.
While the RECEIVE_SENSITIVE_NOTIFICATIONS permission suggests that Android will stop untrusted apps from reading notifications with 2FA codes.