Restore old automatic rewind functionality after notifcation
Automatic rewind after notification should be restored. If "pause upon audio notification" and "automatic rewind" are set, one should expect that to work on any notification. The new "functionality" negatively impacts mobile users of audio books and podcasts, it breaks context of content when responding/reacting to Waze traffic alerts and other general notifications. The settings also do not accurately reflect the current functionality.
Please stop commenting if it's just to repeat the exact same thing. You already explained your point of view and I already have 10 emails with the exact same information.
Now wait for people vote so it can became a popular suggestion.
I will remove new comment that just repeat the exact same thing.
I think everyone got your point
And please stop calling that new behavior a bug. Please go back to my last 10 emails or to my previous comments on this suggestion. I already explain this is the intended behavior, so it's NOT A BUG.
I get it that you disagree, but this is the way I implement it so it cannot be called a bug. Call it a poor choice if you want to, but it's not a bug.
But the application I am using with them, Podcast Addict, worked just fine with those applications prior to a bug being introduced that now no longer honors the settings as described in the application. What applications "should" be doing and what is happening are two different things. I still don't understand the resistance to a toggle or slider to allow both methods of handling automatic rewind to co-exist.
Because the app you're using (Google Navigation/waze) isn't using the correct audio focus request type. The 'ducking' type should only be used for really short audio burst.(http://developer.android.com/training/managing-audio/audio-focus.html#HandleFocusLoss)
Ducking request means other app should keep plaing at a lower volume in the background. I added a setting so the app will stop/resume playback in that case, but it's not the standard behavior.
This kind of ducking behavior is intended for sms, email, ... short notification
That's why I disable this feature. I get it that you're talking about your navigation notigication, I'm just saying it also trigger the autorewind in case of other kind of short notification like SMS and email which is annoying.
No need to keep arguing about this here. I already spend a lot of time explaing over and over by email why I changed it and how audio focus and priority work on android.
I don't intend to continue arguing here.
Now let other users vote for this feature if they think this is a good idea.
Nor will it auto rewind anymore after 10-20 seconds of Google Navigation directions or Waze traffic alerts and numerous other scenarios...as I have explained ad nauseam. 2 things.
1. The options no longer work as described.
2. Why can't both options co-exist with a toggle?
Your complete dismissal of how it is functioning and the use cases described is frustrating. This is NOT about an email alert or another quick notification, etc.
After our 10+ emails exchange I will explain this feature behavior one more time:
Auto rewind still works the exact same way than before EXCEPT in case of 'DUCK audio focus lock' which is google technical term to describe a really short notification (less than 2s)
It means that now the app won't autorewind 10s (or more) every time you got a SMS, email notification or every time you take a picture.
Users were complaining about the previous behavior so I fixed it. I don't think having a 1s notification will make you lose track of your listening.
Anyway now that I explained how it works feel free to vote for this feature if you find it necessary.