Posts: 6,810
Joined: Jul 2010
Reputation:
198
That was the issue before my fix I pushed today. Either you did not get the updated sources of vnsi or there is still some older binary on your system which gets pulled on load.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
It seems that update via zip does not work, it still loads the original addon binary. If I build entire xbmc with patched vnsi it works. If I only update vnsi it shows the error you posted.
Posts: 9
Joined: Aug 2013
Reputation:
0
Hi,
yes, I've descovered that yesterday, too.
I've moved your new vnsi version manually to OUYA. XBMC showed version 1.8.4. Then I've updated via zip-file and it was back to 1.8.3.
But always the 1.8.3 module was in use...
So, as you said, one solution would be to compile entire xbmc. Another one could be to root the Android-device (OUYA) and get access to the xbmc installation folder.
Thanks for your help!