• 1(current)
  • 2
  • 3
  • 4
  • 5
  • 7
Android Audio Passthrough gone after Shield Sleep.
#1
Like the title says, I loose my audio passthrough when my Shield Tv comes out of sleep. I have to exit app and open it to get it back to work.

This been since android 8 hit Shield. Is there any fix for this?

I'm currently trying latest nightlies, but same problem.

The options for audio passthrough completely disappears (except for the blue title).
Reply
#2
No -> please file the bug with nvidia. We only use Audiotrack (Android's audio abstraction) if it stops to work -> your manufcaturer has to fix it, especially if they broke it with version 8.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#3
(2018-07-10, 17:15)fritsch Wrote: No -> please file the bug with nvidia. We only use Audiotrack (Android's audio abstraction) if it stops to work -> your manufcaturer has to fix it, especially if they broke it with version 8.

But why does it work with an app like Netflix? That doesn't seem to have any problem at all.
Reply
#4
Why did it work before your version 8 update?

And Netflix does neither do DTS-HD nor TrueHD ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#5
(2018-07-10, 18:14)fritsch Wrote: Why did it work before your version 8 update?

And Netflix does neither do DTS-HD nor TrueHD ...

It doesn't matter what kind of audio it is. Netflix uses dolby digital plus, it shows on my receiver, even after sleep. With Kodi when i play something with dd+ it shows that on my receiver. Then i put my shield to sleep and go back to kodi...play the same file and my receiver shows "multi channel in". This happens with every type of audio except for stereo.

I don't know why it worked before on android 7. Maybe something changed with audio in android? I'm not an expert on that. Just letting know my experience right now. It's kinda annoying because i have to exit the app and restart it.
Reply
#6
Then start with a Debug Log showing the problem.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#7
(2018-07-11, 19:02)fritsch Wrote: Then start with a Debug Log showing the problem.
 Alright, here is the log: https://paste.ubuntu.com/p/jD4ZRr7c7h/

I started playing Ready Player One (dts) and Black Panther (dts-hd). Both work after freshly opened kodi. Then I put my Shield to sleep and play those same files again and both give multi channel in.
I just installed MrMC to see if it had the same problem, but there it seems to work fine. After sleep it still gives the correct signal. But I don't like that MrMC app.
Reply
#8
Could you please disable "Adjust Refreshrate"?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#9
(2018-07-11, 20:05)fritsch Wrote: Could you please disable "Adjust Refreshrate"?

You mean Adjust display refresh rate on start/stop?

But i thought that was needed to have 24p on my tv and have my audio in sync.
Reply
#10
I see the problem!

Quote:19:39:14.593 T:204806310320   DEBUG: CXBMCApp::onReceive - Got intent. Action: android.media.action.HDMI_AUDIO_PLUG
19:39:14.594 T:204806310320   DEBUG: -- HDMI state: off
19:39:14.594 T:205390001392   DEBUG: CActiveAE - device change event
19:39:14.623 T:205400659184   DEBUG: Draining Audio
19:39:14.624 T:205400659184   DEBUG: CAESinkAUDIOTRACK:Big Grineinitialize
19:39:14.630 T:205390001392   DEBUG: Previous line repeats 1 times.
19:39:14.630 T:205390001392  NOTICE: Float is supported
19:39:14.630 T:205390001392   DEBUG: AESinkAUDIOTRACK - 32000 supported
19:39:14.631 T:205390001392   DEBUG: AESinkAUDIOTRACK - 44100 supported
19:39:14.631 T:205390001392   DEBUG: AESinkAUDIOTRACK - 48000 supported
19:39:14.631 T:205390001392   DEBUG: AESinkAUDIOTRACK - 88200 supported
19:39:14.632 T:205390001392   DEBUG: AESinkAUDIOTRACK - 96000 supported
19:39:14.632 T:205390001392   DEBUG: AESinkAUDIOTRACK - 176400 supported
19:39:14.633 T:205390001392   DEBUG: AESinkAUDIOTRACK - 192000 supported
19:39:14.643 T:205390001392  NOTICE: Found 1 Lists of Devices
19:39:14.643 T:205390001392  NOTICE: Enumerated AUDIOTRACK devices:
19:39:14.644 T:205390001392  NOTICE:     Device 1
19:39:14.644 T:205390001392  NOTICE:         m_deviceName      : AudioTrack
19:39:14.644 T:205390001392  NOTICE:         m_displayName     : android
19:39:14.644 T:205390001392  NOTICE:         m_displayNameExtra: audiotrack
19:39:14.644 T:205390001392  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
19:39:14.644 T:205390001392  NOTICE:         m_channels        : FL, FR, FC, LFE, SL, SR, BL, BR, BC, BLOC, BROC
19:39:14.644 T:205390001392  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
19:39:14.644 T:205390001392  NOTICE:         m_dataFormats     : AE_FMT_S16LE,AE_FMT_FLOAT,AE_FMT_RAW
19:39:14.644 T:205390001392  NOTICE:         m_streamTypes     : No passthrough capabilities
19:39:14.645 T:205400659184    INFO: CActiveAESink::OpenSink - initialize sink

On Resume we get the event of an HDMI hotplug and probe the audio formats again, as you see here we fail to open _ANY_ PT stream and therefore kodi goes into pcm mode.

Could you try: First power on the AVR - wait 60 seconds and then resume kodi from suspend?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#11
The receiver never went off when i used logging, i only put the shield to sleep for a moment.
And like i said, no problems before and no problems with MrMC.
And isn't mrmc a fork of kodi? This is all so confusing for me right now.
Reply
#12
Also, here is an image after the sleep of audio settings:
https://imgur.com/a/Xk08Xt4

You can see that the passthrouh is completely off. But when i exit app and open again it is back on.
https://imgur.com/a/Z23sRI1
Reply
#13
(2018-07-11, 20:15)bokkoman Wrote: The receiver never went off when i used logging, i only put the shield to sleep for a moment.
And like i said, no problems before and no problems with MrMC.
And isn't mrmc a fork of kodi? This is all so confusing for me right now.
 It does not matter wht MRMC does ... it's totally irrelevant. When your shield resumes it queries for audio capabilities. when the AVR is off it only provides what the TV can do ... MrMC does not do that. Therefore some funny testing for MrMC: Suspend the shield, keep your AVR off and then press play on MrMC with DTS-HD ... hope your TV won'T be killed.

Back on topic: I made you a build, it has "atevent" in name, it will be output in ~ 60 minutes here: http://mirrors.kodi.tv/test-builds/android/ arm64 or arm - choose what fits best. Edit: And don't forget the log please.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#14
(2018-07-11, 20:20)bokkoman Wrote: Also, here is an image after the sleep of audio settings:
https://imgur.com/a/Xk08Xt4

You can see that the passthrouh is completely off. But when i exit app and open again it is back on.
https://imgur.com/a/Z23sRI1
 It told you above WHY it is off ... no need for stating that again and again. The log is fully clear: On Resume DTS-HD opening fails as does every other passthrough format and therefore kodi disable PT for your shield ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#15
(2018-07-11, 20:23)fritsch Wrote:
(2018-07-11, 20:15)bokkoman Wrote: The receiver never went off when i used logging, i only put the shield to sleep for a moment.
And like i said, no problems before and no problems with MrMC.
And isn't mrmc a fork of kodi? This is all so confusing for me right now.
 It does not matter wht MRMC does ... it's totally irrelevant. When your shield resumes it queries for audio capabilities. when the AVR is off it only provides what the TV can do ... MrMC does not do that. Therefore some funny testing for MrMC: Suspend the shield, keep your AVR off and then press play on MrMC with DTS-HD ... hope your TV won'T be killed.

Back on topic: I made you a build, it has "atevent" in name, it will be output in ~ 60 minutes here: http://mirrors.kodi.tv/test-builds/android/ arm64 or arm - choose what fits best. Edit: And don't forget the log please.

I'll try that thing with mrmc. Though when i turn off my receiver, i don't get an image.

So why is mrmc irrelevant? Doesn't it use the same kind of android audiotrack? I'm just wondering and curious lol.

I'll try to installed that special build through the kodi install addon.
Reply
  • 1(current)
  • 2
  • 3
  • 4
  • 5
  • 7

Logout Mark Read Team Forum Stats Members Help
Audio Passthrough gone after Shield Sleep.0