2019-11-02, 16:12
do you think it's okay to have both nfs and samba sharing the same drive? I'm fine trying nfs for my shield but I still need to copy my ripped movies to the drive from my win10 box.
thanks
thanks
(2019-11-02, 16:18)std_ren Wrote:(2019-11-02, 12:56)Klojum Wrote: As far as I can tell, it's an Android <-> SMB fight.
As far as NFS is concerned, browsing is the 'only' problem. File streaming itself is fine.
Could pls point me to some description on how to find and update the sources.xml on the Shield TV? thx
(2019-11-02, 16:18)std_ren Wrote: Could pls point me to some description on how to find and update the sources.xml on the Shield TV?
(2019-11-02, 17:12)std_ren Wrote: Thanks Klojum...got the built-in SMB server up, can't find the Kodi profile folder, I'm giving up...going back to my Apple TV 4K / Infuse Pro for my movies.do a search for Kodi, I found that many things are hidden. I did that for my Kodi log because I could not find it
(2019-11-20, 16:38)Zak11 Wrote: still get the same issue with the 2nd hotfix applied, back to Firestick 4K which doesnt have the issue
(2019-11-21, 22:31)Zak11 Wrote: Hi, so user on Nvidia forum kindly helped and suggested the following and it seems to have solved the issuethat was me...lol glad it worked. I've confirmed that ifx is for the old model and new and using your share inside the shield. It is not a client fix for shares inside Kodi.
yes same as you, I have a ticket into nvidia support. I guess the dev team is looking at it. You can create the share in the shield from the storage part of the menu. There it says mount share. Usually it scans for shares but you can manually do it as well. Once that is connected you can enable the caching by enabling developer options. You do that by clicking many times on the version under the about section of the shield. It is logger cache. I tested it at max 16mb. After that you create your sources inside Kodi the only difference is now you will see the mount from the shield. Try it and see if we get the same results. thanks