Posts: 5
Joined: Jan 2013
Reputation:
0
2013-01-18, 16:17
(This post was last modified: 2013-01-18, 22:29 by isotoper.)
Hello guys,
Sorry for my bad English.
It really helped me and xbmc is now launching when i'm running my android app, except I cannot see my extensions on the android app.
I can see the extensions only if I running them from the pc itself, then they are being showen in the android app.
Any suggestion ?
Thanks.
Posts: 5
Joined: Jan 2013
Reputation:
0
Hi,
Sure, I will explain :
I have xbmc installed on my PC.
I have the official xbmc app for iPhone (and for android on another phone).
Using the above wol-launcher v0.1.0 , I can successfully launch the xbmc PC app through my iPhone and it's great.
I'm also able to explore my xbmc library through the iPhone , BUT I cannot see the xbmc extensions on the phone (like radio, etc...) , when I launch the xbmc from the phone with this launcher .
** When I open the xbmc manually from my PC with the mouse, then I can see the extensions on the iPhone/Android xbmc app.
Any idea ?
Thanks!
Posts: 10
Joined: Sep 2011
Reputation:
0
VeeV
Junior Member
Posts: 10
Ok I see. This is totally unrelated to the launcher App. This is simply an XBMC behavior. When you browse your files from the mobile app, the add-on part is in fact a virtual file system populated by the add-on. When first browsing it from the app you won’t see them because the add-on has not yet published them. If you manually access it within XBMC you will kind of “force” the virtual directory to be constructed an it will then reside in memory. From here you will be able to see the add-on folder on the mobile app. This behavior will change as soon as your app will implement the new Frodo’s JSON add-on interface. I my app I used before a workaround (for Eden if you follow me) to have a direct call to the add-on special folder. It seems to force the Virtual directory to be build.
Hope this is clearer.
Posts: 5
Joined: Jan 2013
Reputation:
0
2013-01-21, 10:27
(This post was last modified: 2013-01-21, 10:38 by isotoper.)
Hi VeeV , thanks a lot for your answer .
Your'e saying that in your app you're using a workaround to have a direct call to the add-on special folder. It seems to force the Virtual directory to be build.
Do you mean the Launcher app (v 0.1.1) which I'm already using ?
**( (I do use Eden ).
Thanks !
Posts: 22
Joined: Mar 2014
Reputation:
0
Seph
Junior Member
Posts: 22
Hello,
I've tried to have this app autostart at windows boot, by adding it to my startup folder, but it does not seem to load until I load it manually. Any ideas why? Windows 8.1