General AML S802 Device release discussions

no_spam_for_me replied

05-12-2014, 21:15
Originally posted by reddragon72 View Post

Pass through must be supported by the hardware as a "transport" mechanism only.
:
So the reason we are only seeing XBMC performing passthrough today is because it is the only app that people have tested that can do the software decode and pass that through to the hardware.
:
remember you decode then pass through. Decoding must be supported in the either hardware or ROM/APP. And pass through must be supported VIA the hardware, ROM and APP.

Generally good explanation, but I'm a little bit confused by this last two point...
Because at pass-through the receiver have to do the decoding and the software only have to know to do pass-through (and maybe how to do)...
Leave a comment:
no_spam_for_me replied

05-12-2014, 21:02
Originally posted by roolmapool View Post

Thanks, but stock kernel doesn't support nfs... i have already get a try, and i had an error ... no such device. No more chance to load a ko module, i forgot error message returned.

I think i have to wait for a custom kernel

Only for minix (I think you use e.g. wasser kernel)
not for aml at the moment
Leave a comment:
roolmapool replied

05-12-2014, 20:25
@reddragon ... Thx for precisions.
I wish Mx player devs fix passthrough after software decoding
Leave a comment:

05-12-2014, 20:21

Originally posted by no_spam_for_me View Post

If the nfs-support is build into the kernel, you can use this initd-script

Code:

#!/system/bin/sh
# *************
# * NFS mount *
# *************
# copy to /system/etc/init.d
# change permisions to "755" "rwx r-x r-x"
# reboot
# -------------------
# using this -> cmd-install-NFS.cmd <-
# adb remount -oremount,rw /
# adb push 05nfs /system/etc/init.d
# adb shell chmod 0755 /system/etc/init.d/05nfs
# adb remount -oremount,ro /
# adb shell ls -al /system/etc/init.d/
# adb reboot
# pause
# -------------------
while [ ""`getprop dev.bootcomplete` != "1" ] ; do sleep 1; done
mount -o rw,remount /
mkdir /mnt/XPFilme
mount -o ro,remount /
sleep 2
busybox mount -t nfs 192.168.2.1:/XPFilme /mnt/XPFilme -o ro,intr,soft,udp,nolock,rsize=8192,wsize=8192
# done

but you have to change the mount-name and IP to yours, and if not build into the kernel you have also to load the ko inside the script...

Thanks, but stock kernel doesn't support nfs... i have already get a try, and i had an error ... no such device. No more chance to load a ko module, i forgot error message returned.

I think i have to wait for a custom kernel

Leave a comment:

reddragon72 replied

05-12-2014, 19:38
No_spam did a great job of explaining what I explained before.

Decoding and pass through are two separate items.

Pass through must be supported by the hardware as a "transport" mechanism only.

Software decoding within an application must be supported by the app and the app must have it's own software codec and know how to call it. MX player had to drop DTS support due to a licensing agreement but you can find a work around all over the place.

Hardware decoding is where the actual firmware within the SOC has a "standards" based codec. This does not mean every application can use it. The application must know how to call the codec to do the decoding. in this case MX player knows how to do that, but it is still lacking the ability to call the pass through.

So the reason we are only seeing XBMC performing passthrough today is because it is the only app that people have tested that can do the software decode and pass that through to the hardware.

remember that we are in an area of Android that has been in a state of hold for a long time. No media player creator is putting time and effort into multi-channel decoding and pass through handling because there is simply not a stable market for it. XBMC is all about that and it primarily designed with all that in mind as it is not meant for phones with one maybe two speakers.

And to reference the difference between software and hardware decoding SW decoding can use several sources for codecs but all of them must adhere to the standard or run the risk of not decoding properly. HW decoding guarantee's that if you encode it with the standard that it will play flawlessly. Remember that a secondary codec MUST following the guidelines or run the risk of loosing end users and possibly being sued by the codec owner.

remember you decode then pass through. Decoding must be supported in the either hardware or ROM/APP. And pass through must be supported VIA the hardware, ROM and APP.
Leave a comment:

no_spam_for_me replied

05-11-2014, 13:39

Originally posted by roolmapool View Post

So for my x5 or x7 devises, i mount nfs folder with busybox command because kernel permit that.

If the nfs-support is build into the kernel, you can use this initd-script

Code:

#!/system/bin/sh
# *************
# * NFS mount *
# *************
# copy to /system/etc/init.d
# change permisions to "755" "rwx r-x r-x"
# reboot
# -------------------
# using this -> cmd-install-NFS.cmd <-
# adb remount -oremount,rw /
# adb push 05nfs /system/etc/init.d
# adb shell chmod 0755 /system/etc/init.d/05nfs
# adb remount -oremount,ro /
# adb shell ls -al /system/etc/init.d/
# adb reboot
# pause
# -------------------
while [ ""`getprop dev.bootcomplete` != "1" ] ; do sleep 1; done
mount -o rw,remount /
mkdir /mnt/XPFilme
mount -o ro,remount /
sleep 2
busybox mount -t nfs 192.168.2.1:/XPFilme /mnt/XPFilme -o ro,intr,soft,udp,nolock,rsize=8192,wsize=8192
# done

but you have to change the mount-name and IP to yours, and if not build into the kernel you have also to load the ko inside the script...

Attached Files

NFS.zip (738 Bytes, 84 views)