Bluetooth Notification interruptions
2 posters
Page 1 of 1
Bluetooth Notification interruptions
This may have been answered somewhere else or may not be a feature. I have the pro version and was wondering how to set the app up so only phone calls come through while listening to music via bluetooth, and to block out all incoming notifications as well as phone calls while listening to music.
moodyda- Posts : 5
Join date : 2014-04-11
Re: Bluetooth Notification interruptions
Sorry, sometimes I don't see the messages on time.
This depends on the headset. If the headset supports both Bluetooth A2DP and Bluetooth SCO (phone calls), what happens is that the Bluetooth SCO part of the headset will probably have its own ringer (not phone ringtone). Then the phone rings, Android, and any app, can detect the incoming call and react. SoundAbout can alter the audio, but it can't block Android from sending the "ringing" AT command to the headset. When the headset gets this AT Command it will beep, ring...(different on various headsets). The only way to block this would be to completely disconnect the headset Bluetooth connection which means you would be able to use it for a phone call until reconnected (which can take a few seconds).
If you are listening to music using Bluetooth A2DP, the new Beta Version can block notifications when Bluetooth A2DP is connected (won't know if music is actually being listened to or not).
Get the latest Beta here:
https://soundabout.forumotion.com/f8-download-beta-versions
1] Open SoundAbout
2] Press "Alert behavior"
3] Press Bluetooth (A2DP) Behavior
4] Change "Notifications to:" setting to one of the "neither settings"
5] There is a setting for "Ringtones to:", but as the explanation above states, the behavior all depends on the Bluetooth SCO part of the headset and how the manufacturer designed it to ring.
This depends on the headset. If the headset supports both Bluetooth A2DP and Bluetooth SCO (phone calls), what happens is that the Bluetooth SCO part of the headset will probably have its own ringer (not phone ringtone). Then the phone rings, Android, and any app, can detect the incoming call and react. SoundAbout can alter the audio, but it can't block Android from sending the "ringing" AT command to the headset. When the headset gets this AT Command it will beep, ring...(different on various headsets). The only way to block this would be to completely disconnect the headset Bluetooth connection which means you would be able to use it for a phone call until reconnected (which can take a few seconds).
If you are listening to music using Bluetooth A2DP, the new Beta Version can block notifications when Bluetooth A2DP is connected (won't know if music is actually being listened to or not).
Get the latest Beta here:
https://soundabout.forumotion.com/f8-download-beta-versions
1] Open SoundAbout
2] Press "Alert behavior"
3] Press Bluetooth (A2DP) Behavior
4] Change "Notifications to:" setting to one of the "neither settings"
5] There is a setting for "Ringtones to:", but as the explanation above states, the behavior all depends on the Bluetooth SCO part of the headset and how the manufacturer designed it to ring.
Similar topics
» Notification and bluetooth audio silent after connecting to bluetooth headset
» notification volume not working on bluetooth
» Bluetooth (media) mono shuts off after a phone call, or notification comes in.
» Australian S5 Bluetooth Notification no sound through any output
» Notification Access and SA Notification Listener
» notification volume not working on bluetooth
» Bluetooth (media) mono shuts off after a phone call, or notification comes in.
» Australian S5 Bluetooth Notification no sound through any output
» Notification Access and SA Notification Listener
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|