#111 Problems running Yaacc on Samsung devices

[Rogério Theodoro de Brito]

Hi.

I have been using Yaacc from F-Droid on my vanilla Android tablet to watch lectures from my NAS (running Debian's minidlna) and it works wonderfully launching VLC.

Unfortunately, my partner has a Samsung Galaxy S3 Mini cellphone (running Android 4.1.x) where I am not able to get Yaacc to correctly browse the contents of said NAS. I get a very quick toast telling me that an error occurred and I am not able to lauch the videos.

Now, with a Samsung Galaxy Tab S 8.4" (running KitKat), I encountered the same problem, and I would love to get this fixed, since Yaacc has the best (in the sense of being simple and to the point) user interface that I found so far among the tools that perform the same tasks.

I am attaching here a photo of when the problem manifests itself when running Yaacc on the phone. If any further details are needed, please let me know and I will do my best to provide them.

Thanks in advance,

Rogério Brito.

[TheOpenBit]

Hi,
thanks for your bug report. It seems you are not using the current release 1.1.5. Please update yaacc and try it again.
Let me know, if the error occurs, too. If so, please send me the log if possible. You are able to view the log via the corresponding menu entry inside yaacc.

Regards,
TheOpenBit

[Rogério Theodoro de Brito]

Hi.

Indeed, the photo was taken with version 1.1.4, but the problem still remains with version 1.1.5.

I researched a little bit about the problem and it seems that the problem (unconfirmed) is that the XML sent by minidlna may (again, I am not sure) be missing a namespace declaration.

What is the recommended way of grabbing the contents sent back and forth between yaacc and the dlna server (short of running a packet capture program on my NAS)?

Regards,

Rogério Brito.

[Rogério Theodoro de Brito]

Some extra information:

At the URL below I saw an explanation of the problem:

http://4thline.org/projects/mailinglists.html#nabble-td4023996|a4024990

It seems that the contribution of the author is in the tree for 4thline's cling:

https://github.com/4thline/cling/blob/master/core/src/main/java/org/fourthline/cling/binding/xml/RecoveringUDA10DeviceDescriptorBinderImpl.java

If that is the problem, then perhaps an updated version of the dependencies of yaacc may allow the problem to be solved...

I am willing to test any builds with this fix on said devices.

Thanks in advance,

Rogério.

[TheOpenBit]

Hi,
that is interesting!
Have a try with the latest nightly build. It is using the latest official release of cling.
Regards
TheOpenBit