In addition to supporting Google Assistant, Samsung’s smartphones also include their own voice assistant, that is Bixby. As part of competing with Siri, Google Assistant, and Amazon Alexa, Samsung launched its own voice assistant. It is still pre-installed on many Samsung devices even though it hasn’t been as popular as any of the three assistants.
With just your voice, you can carry out any number of functions with Samsung’s own speech assistant, Bixby. By speaking, you can play a Spotify album, text a friend, or access pictures from a recent vacation.
The Galaxy S22’s side button wakes up Bixby by default, but if you don’t use the voice assistant, that could be a little frustrating as it’s simple enough to mistakenly click.
In short, the service functions in a similar way to other AI products like Google Assistant or Amazon Alexa in that it listens to your voice interprets the information and then returns the action.
Bixby is contextually aware, which enables it to recognize the app’s current status and respond appropriately to your requests while allowing you to mix voice and touch.
How to stop Bixby in Samsung
Go to Settings > Advanced features > Side key to disable Bixby from launching whenever you click the side button. When you push and hold down the side button, you can then select to enter the power off options (power off, restart, and emergency mode). Additionally, you can modify what happens when you double-press the side key or disable it entirely.
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.