2018-07-11, 21:02
(2018-07-11, 20:57)bokkoman Wrote:Arm64: http://mirrors.kodi.tv/test-builds/andro...64-v8a.apk(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.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.
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.
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.
Arm: http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk
Both might need to sync a bit.
Yes. MrMC uses Audiotrack - but it might not react on HDMI hotplug - therefore nothing will change whatever you do with external devices. Additionally it does not probe the formats, but just assumes depending on API that they work properly. Might even be more funny when you just plug in headphones ... but better don't. I see the issue in kodi.log to fix it properly. Now let's see what your Debug Log tells with the above builds.