• 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7
Android Audio Passthrough gone after Shield Sleep.
#16
(2018-07-11, 20:57)bokkoman Wrote:
(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.  
 Arm64: http://mirrors.kodi.tv/test-builds/andro...64-v8a.apk
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.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#17
(2018-07-11, 20:25)fritsch Wrote:
(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 ...

Sorry for that. I was just giving as much info as i could. Thank you for helping with this.

I just installed that "atevent" version (arm64) and it seems to work now. I'll give it some more testing the next few days and will give you an update then.
But for now, thanks a lot!
Reply
#18
Yeah - no problem. I need the log never the less, please. (I am only freetime volunteer Android developer without Android hardware)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#19
(2018-07-11, 21:41)fritsch Wrote: Yeah - no problem. I need the log never the less, please. (I am only freetime volunteer Android developer without Android hardware)
 That seems rather tough! Coding for something you can't actually test.
Well, here is the log: https://paste.ubuntu.com/p/FDjCphg2nP/

Let me know if it is of any help or if you want me to install something else again or try some settings.
Or if you see any errors in the log that I can fix easily (without new versions of kodi) Big Grin
Reply
#20
(2018-07-11, 21:49)bokkoman Wrote:
(2018-07-11, 21:41)fritsch Wrote: Yeah - no problem. I need the log never the less, please. (I am only freetime volunteer Android developer without Android hardware)
 That seems rather tough! Coding for something you can't actually test.
Well, here is the log: https://paste.ubuntu.com/p/FDjCphg2nP/

Let me know if it is of any help or if you want me to install something else again or try some settings.
Or if you see any errors in the log that I can fix easily (without new versions of kodi) Big Grin 
I have the Debug Log which is information enough :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#21
Btw. the log looks horrible :-) Did you press stop / start lots of time?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#22
(2018-07-11, 21:58)fritsch Wrote: Btw. the log looks horrible :-) Did you press stop / start lots of time?

Well a few times. Started playing, stopped, sleep. Play again. Rinse and repeat a few times. maybe 3-4 times sleep even with receiver off one time and waking shield up and then turn on receiver.
Reply
#23
Cool. Thx. The log is not yet good, but the information I see is very valuable!

I shared the information with @peak3d  - so that we can find a good working solution. There are still other flaws in there, e.g. handling of DISPLAY_RESET event vs. Android' intent for hotplug. That's not yet as clean as it could be. The "hack" I gave you just ignroed "Off" Events and asked AE to rescan for sinks on "On" events, which is not safe as well.

Thanks again for helping to test.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#24
(2018-07-11, 22:07)fritsch Wrote: Cool. Thx. The log is not yet good, but the information I see is very valuable!

I shared the information with @peak3d  - so that we can find a good working solution. There are still other flaws in there, e.g. handling of DISPLAY_RESET event vs. Android' intent for hotplug. That's not yet as clean as it could be. The "hack" I gave you just ignroed "Off" Events and asked AE to rescan for sinks on "On" events, which is not safe as well.

Thanks again for helping to test.

No problem! Glad I could help out with Kodi somehow. Hope you can fix it in the next alpa/beta/final build.

So should i stay on this "hack" version? Or what do you recommend?
Reply
#25
For now yes. We are looking into that during the next days. I can rebuild the hacked version from time to time if other important fixes reach master ... Currently I am on holidays - limited to my mobile phone :-) quite hard to write code.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#26
What works here: http://mirrors.kodi.tv/test-builds/andro...64-v8a.apk ?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#27
(2018-07-14, 16:35)fritsch Wrote: What works here: http://mirrors.kodi.tv/test-builds/andro...64-v8a.apk ?

What do you mean by what works here? With the same audio problem?
I'll try to test it out soon and post a log. Currently not home because of nice weather Wink
Reply
#28
Jep :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#29
(2018-07-14, 17:26)fritsch Wrote: Jep :-)
Audio seems to work. But starting a video has been quirky since the previous atevent version. By quirky i mean when i start a movie, i see the loading circle flash really quickly (appearing and disappearing quick).

But biggest problem with this version is that my videos are fully stretched out top to bottom.
For example black panther and ready player one both have black bars, but with this version they don't (stretched to full screen). This didn't happen in the previous version.

Here's the log: https://paste.ubuntu.com/p/sNcb2WCbrr/

Hope it's useful again.
Reply
#30
@bokkoman
The forum moderators have determined that banned addons (wiki) are present on your system. To receive assistance here, these banned items must be removed. If a clean log is not submitted within 3 days, then the relevant post(s) will be removed after this time.
Reply
  • 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7

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