[minixhk]

In Android, even when passthrough is enabled some audios are not output as bitstream (e.g. system notification sounds which may come during a playback).

[minixhk]

Adding one logic may solve this problem - temporarily disabled any changes by volume keys when passthrough is chosen.

but then it requires all manufacturers to add that.

[Koying]

Is there any other android apps of your knowing that steals volume control from the system?
I don't think so. No objective reasons for Kodi to do so, either.

Next step is to also use standard passthrough as defined in Android L & M. As Android progresses in the media aspect, hacks must be removed from Kodi.
Heck, even amlogic will abandon amlplayer to use mediacodec...

[Koying]

Adding one logic may solve this problem - temporarily disabled any changes by volume keys when passthrough is chosen.

but then it requires all manufacturers to add that.

Indeed, that's how it must be done if altering volume during passthrough breaks it.
Kodi still enforces putting the volume at 100% when starting PT playback (and restoring it afterwards), so it's only an issue if users play with volume *during* PT.

[minixhk]

Is there any other android apps of your knowing that steals volume control from the system?
I don't think so. No objective reasons for Kodi to do so, either.

Next step is to also use standard passthrough as defined in Android L & M. As Android progresses in the media aspect, hacks must be removed from Kodi.
Heck, even amlogic will abandon amlplayer to use mediacodec...

I also agree, just many older devices out there may not get updates so...
amcodec will be eventually replaced by mediacodec in future Android releases.

[minixhk]

I raised this question based on a user perspective.

Many users don't know much about the change and may only see the problems happening without even knowing why.

Hope you guys understand!

[Ned Scott]

I believe that Kodi should not touch Android system volume at all, just like on other platforms. I understand why it was done this way, but I think separating the two volumes will have less issues. Android TV-set users can leave Kodi volume at full and then control system volume, like how other Android TV-set apps do, and like how Mac, Win, and Linux do for people who use multiple apps along side Kodi. Those TVs already have a remote control that does direct Android system volume. Other users can opt to leave Android system volume full, and then control Kodi volume only, which is how most Android-box users probably like doing things.

We wouldn't have the double volume bar, it might (maybe?) help this issue, and it seems more intuitive to me. Even before I knew this was an issue, I thought it was strange to have Kodi volume and Android system volume linked.

[Koying]

I believe that Kodi should not touch Android system volume at all, just like on other platforms.

Indeed (besides temporarily forcing 100% for PT).

Other users can opt to leave Android system volume full, and then control Kodi volume only, which is how most Android-box users probably like doing things.

Well, that's contradictory
Unless you mean "...control AVR or TV volume only", where I absolutely agree

We wouldn't have the double volume bar, it might (maybe?) help this issue, and it seems more intuitive to me.

Actually, keeping both bars was a user request. The more I think about it, the more I'm convinced the Kodi one should disappear, really, if we leave control to android re volume.
This is assuming the droid system volume widget is always shown, though.

[Ned Scott]

Other users can opt to leave Android system volume full, and then control Kodi volume only, which is how most Android-box users probably like doing things.

Well, that's contradictory ;)
Unless you mean "...control AVR or TV volume only", where I absolutely agree

No, I mean I specifically control Kodi's volume and not OS volume :)

This is how I've always controlled Kodi on OS X, Windows, Ubuntu, and iOS.

All smartphone/tablet remote app users are forced to do this as well, and don't even have a CEC option to control system, TV, or AVR volume. I typically use a remote with a FLIRC, so my volume keys are not bound to the volume media keys. On Ubuntu you can choose if media keys are OS-wide or Kodi specific.

We wouldn't have the double volume bar, it might (maybe?) help this issue, and it seems more intuitive to me.

Actually, keeping both bars was a user request. The more I think about it, the more I'm convinced the Kodi one should disappear, really, if we leave control to android re volume.
This is assuming the droid system volume widget is always shown, though.

If the user is changing system volume then yeah, Kodi shouldn't show anything. Kodi volume shouldn't also be changing and should always be 100%. Otherwise you have weird situations where someone might turn down "both" volumes using a remote on an Android box, but then try to turn the volume back up with their smartphone remote, which would only turn up Kodi volume, right? Unless I misunderstood.

[Koying]

Other users can opt to leave Android system volume full, and then control Kodi volume only, which is how most Android-box users probably like doing things.

Well, that's contradictory
Unless you mean "...control AVR or TV volume only", where I absolutely agree

No, I mean I specifically control Kodi's volume and not OS volume

This is how I've always controlled Kodi on OS X, Windows, Ubuntu, and iOS.

All smartphone/tablet remote app users are forced to do this as well, and don't even have a CEC option to control system, TV, or AVR volume. I typically use a remote with a FLIRC, so my volume keys are not bound to the volume media keys. On Ubuntu you can choose if media keys are OS-wide or Kodi specific.

Indeed, why not. Not my personal choice, but nothing prevents doing so, indeed.
IIRC, I can do the distinction between system volume callbacks and Kodi vol up/down when it comes to show Kodi's volume bar or not.

That makes 3 ways to control volume. Enough to satisfy everybody, I guess

[Ned Scott]

Any chance this is related? http://forum.kodi.tv/showthread.php?tid=230260

I'm assuming it's not, but since it's another passthrough issue on minix hardware, I thought I would mention it.

[minixhk]

Hello team,

I saw a similar report when I tried google search:
https://forums.geforce.com/default/topic...-15-15-/4/

It's also happening since Isengard so could you please take a look? Thanks.

[Koying]

Yeah, I know. Still nothing we can do if the device allows the PT bistream to be altered by system volume...

Unless there is a way for an app to tell to Android to disable volume control, but I'm not aware of that...

Apparently, the system does it correctly on lollipop when using the API (E)AC3 passthrough (see netflix). Just have to do the same for "direct" passthrough.

Note that I'm looking into api based passthrough, but no dts in sight, so not a proper replacement, yet.

[minixhk]

Yeah, I know. Still nothing we can do if the device allows the PT bistream to be altered by system volume...

Unless there is a way for an app to tell to Android to disable volume control, but I'm not aware of that...

Apparently, the system does it correctly on lollipop when using the API (E)AC3 passthrough (see netflix). Just have to do the same for "direct" passthrough.

Note that I'm looking into api based passthrough, but no dts in sight, so not a proper replacement, yet.

We shall try to "lock" the system volume while PT is in use.
Thanks.

[jclau]

Dear Koying,

I am sorry to report that passthrough does not work at all on my Sony Android TV and I'm getting same noise as reported by OP above but at full blast through my AVR!!! I don't quite understand your explanations above but on my (very smart) SONY TV when set to output to the audio system (AVR) the native Video player passes through DTS and DD 5.1 to my AVR perfectly with the volume level unchanged, and the AVR volume can then be turned up or down with either the TV or AVR remote control.