0
Under review

connection dropped / Android media server died:extra:0 // android media failure:what:-38:extra:0

thkg00fy 6 years ago • updated by Jona (Lead Developer) 5 years ago 1

Hi again,


here is the next post regarding my second device. It's an ODYS Xelio, an Android 4.0 powered low price tablet.


On this device I have problems using the "Android" stream engine. Regardless which kind of stream I want to connect to (mp3 or aac+): the engine fails!

On aac+ it tells "connection dropped" or (if I push the PAUSE icon at the right moment) "Android media server died:extra:0". If I try to connect to a mp3 source I get "android media failure:what:-38:extra:0"...

Whatever, the "FFMpeg" engine works well on this device, due to the device specs (quite powerful CPU), so I still can use it! it's just sad, that I can't use the "PAUSE" (caching) function of XiiaLive on this device...  :-(


So, is there any way to help you to fix this issues?


Kind regards again

thkg00fy

Answer

Answer
Under review

Very interesting device, never seen it! :P


Well the deal with Android OS across devices is that most companies implement their own media framework and that sucks for us since they don't test as much as they should, and most of the time their stuff is missing bunch of things causing issues like the one you are seeing.


In order to try to figure out what could be going on I would need you to collect the logs when trying to stream aac/aac+ and then another for mpeg.  To collect the logs is really simple just follow these steps.

http://support.xiialive.com/topic/38494-how-to-collect-error-logs/


FFmpeg seeking and caching support is coming soon. I'm already working on it! :)

Under review

Very interesting device, never seen it! :P


Well the deal with Android OS across devices is that most companies implement their own media framework and that sucks for us since they don't test as much as they should, and most of the time their stuff is missing bunch of things causing issues like the one you are seeing.


In order to try to figure out what could be going on I would need you to collect the logs when trying to stream aac/aac+ and then another for mpeg.  To collect the logs is really simple just follow these steps.

http://support.xiialive.com/topic/38494-how-to-collect-error-logs/

Answer
Under review

Very interesting device, never seen it! :P


Well the deal with Android OS across devices is that most companies implement their own media framework and that sucks for us since they don't test as much as they should, and most of the time their stuff is missing bunch of things causing issues like the one you are seeing.


In order to try to figure out what could be going on I would need you to collect the logs when trying to stream aac/aac+ and then another for mpeg.  To collect the logs is really simple just follow these steps.

http://support.xiialive.com/topic/38494-how-to-collect-error-logs/


FFmpeg seeking and caching support is coming soon. I'm already working on it! :)

I am getting the same errors running XiiaLive Pro on my budget tablet running Android 4.0.4. The tablet is identified as SoftwinerEvb and is based on the Allwinner A13 CPU. I have sent a SendLog log file in the hope that you may be able to resolve this issue.


I am pleased to report that XiiaLive Pro works well on my Google Nexus 7 tablet, but I'd really like it to work on my cheap tablet too as one of it's primary functions is as an internet radio tuner!