With the 5.1.1 upgrade, Media volume is now separate from System/Notification volume. I suppose that's ok. My phone has 4 separate volumes, 5 if you count blue-tooth. One side effect though is it seems that an app needs to request or somehow inform the device that it is running media. If it does not, the volume controls on the side simply don't work at all, neither for notification nor media. Is this just a bug, or is there some new setting we should specify on the app submission page in order to allow the volume control to work? When running my app in Silk, things work correctly - the volume control affects the Media volume setting as expected. The bug occurs both with my existing live app, and testing the app in the Web App Tester. thanks, Joe app: SubFire Player Message was edited by: Joe, adding details about web app tester. Joseph Shelby
I'm not the only one. My Plex app also will not react to the volume control, forcing me to have to pause it, drag settings down from the top, dig to find the volume, set it, and hope i get it right...and don't have to change it again.
I'm not sure if there was a minor O/S update, or just a change in how html5 apps are packaged, but as of now, with my latest version of my app (submitted yesterday morning, approved early this morning), the volume control correctly changes media when my app is running. Thanks, Joe
Thanks Joe, the issue has been fixed internally, and if you have any other apps affected by this, you can simply resubmit them, and the issue should be resolved. For that just go into your app and click 'Add Upcoming Version' and resubmit. Thanks!
Another thing of note: If "Do Not Disturb" is on, the media volume doesn't work, no matter which app (Plex (native) or SubFire (html5)). It pops up the notifications volume dialog, at 0, and doesn't adjust anything. Easy workaround is to turn DND off temporarily, of course. Just letting you know. I'm not sure that's best practice, as certainly none of my non-Fire Android boxes have done it like that. :) Thanks again for fixing the original issue. I only have one other html5 audio tag issue, but I'm aware it is a Chromium-Android problem that FireOS inherited in the WebView, and they're fixing it in Chromium 50 or 51.
https://bugs.chromium.org/p/chromium/issues/detail?id=584562 - My current workaround is working ok for me in most environments, so I'm not worried. Joe