Some Android Devices Are Having Problems With Notifications

Aadhya Khatri - Jun 05, 2019


Some Android Devices Are Having Problems With Notifications

Some Android users reported notification issues when they connect other devices to their smartphones via Bluetooth

As the wireless connection is becoming more common, users now have to pay attention to what is connecting to their devices via Bluetooth. Recently, some people using Android reported that there was a bug with notifications appears when they use Bluetooth.

Bluetooth-problem
Users should pay attention to what they are connecting their smartphones to

According to Android Police, a number of people notice many different types of issues with the notifications. While the problems vary depending on the user, there are three main issues. The first one is the sound, which sometimes plays several times at different volume levels. When a notification arrives, the device usually rings one time only, but for some users, it repeats two more.

The second issue is with the volume. Some users reported that when their devices are connected to another one via Bluetooth, the alerts will ring even when users have set Do Not Disturb or Vibrate.

The last one is notifications surface again after users have swiped them away. For now, it seems like the issue is limited to Instagram and Facebook, but some other apps are also under its influence. No one can prove that this one is related to Bluetooth, but it might be, given the time when it was reported.

Android-Facebook-notification
The notification problem is on Facebook and Instagram

So far, we have no idea what causes the bug as it seems to appear on several Android devices and also Bluetooth accessories. One of Android Police’s employees had the notification issue when using OnePlus 6T. Other smartphones that have the same problem include Galaxy S8, Galaxy S9, Galaxy S10, and Google Pixel. Apart from phones, the Bose QC35 is believed to be in the list of affected devices too.

Google support has been aware of the problem and provided the solution to one of the users, which includes unpairing your devices and rebooting them. So far, the company has not issued any official announcement about the cause of the bug.

Comments

Sort by Newest | Popular

Next Story