[1.0.0.70/82][0.7.9]Inaudible volume levels after notification triggers audio ducking

Solved!
Reply

[1.0.0.70/82][0.7.9]Inaudible volume levels after notification triggers audio ducking

RRL
Casual Listener

Since the latest update on the Spotify app the music will no longer get interrupted by notifications. This functionality is far from useful when using other apps simultaneously.

 

Often I use Spotify in the car in combination with my GPS and an app which warns me (legally) for speed traps. Before the update Spotify briefly paused for a GPS instruction or an alarm for a speed trap, which made them clearly noticable.

 

The apps in this case are Sygic and FlitsNav (Dutch). They use respectively the media volume and alarm volume, both are giving problems.
- The media volume is briefly lowered when Sygic has an instruction. Because Sygic uses this volume too, the instruction volume is lowered as well. This makes that the instructions are pronounced on a lower volume than normally and let the music kick in hard again after the barely audible instructions.
- FlitsNav uses the alarm volume, the same as used for the alarm clock. Even though the warnings are noticable, they are far less clear than they used to be. This makes that this app becomes far less affective compared to a total interruption of the music.

 

Is there a possibility to have the music interrupted for notifications again?

 

Phone: Samsung Galaxy SIII Mini
Android version: 4.1.2 (latest)
Spotify version: Latest update (automatically installed on April 10, 2014)
Sygic version: 13.4.2
FlitsNav version: 3.0.4

 

EDIT: I amended the subject/title to distinguish theis thread from http://community.spotify.com/t5/Help-Android/Music-interrupted-by-notification-ring/m-p/235200#U2352...

EDIT: Temporary solution here: http://community.spotify.com/t5/Help-Android/1-0-0-70-0-7-9-Inaudible-volume-levels-after-notificati...

1 ACCEPTED SOLUTION
Solution!

Matze
Roadie
Just got an update from the Play Store (1.0.1.981): at least according to the changelog it should be fixed now. I didn't have time to test it yet.

View solution in original post

286 Replies
SUGGESTED POSTS