Superb quality and spec AB-Com PULSe 4K SE. Crazy offer! Only £129! FREE UK DELIVERY! 4K UHD, Enigma 2, Multiboot 4 images & more!...
Superb quality and spec AB-Com PULSe 4K Rev II Twin Satellite tuner only £179! FREE UK DELIVERY! 4K UHD, Enigma 2, SATA HDD facility, Multiboot 4 images & more!...

XBMC Plugin

Hi,
This worked, strange though is wasin in the extensions.
did you install it? It is not installed by default it is a plugin that must be installed. With this line it is installed but this could also be done with the remote.

ciao
 
I installed XBMC Launcher on image vix image build 142 (vu+ duo2) and when I pressed it to run it, the screen went black, nothing happened for 5 seconds, and it just returns to the plugin browser page.
Yes I rebooted after I installed it but it just did not work, tried numerous times.
I uninstalled it and after a reboot its still there in the plugins section even tho when I press the remove plugins button its not there,
So it must be removed but its still showing on the plugin browser page
Am I missing something?
 
I installed XBMC Launcher on image vix image build 142 (vu+ duo2) and when I pressed it to run it, the screen went black, nothing happened for 5 seconds, and it just returns to the plugin browser page.
Yes I rebooted after I installed it but it just did not work, tried numerous times.
I uninstalled it and after a reboot its still there in the plugins section even tho when I press the remove plugins button its not there,
So it must be removed but its still showing on the plugin browser page
Am I missing something?

Try installing it with the telnet command I posted earlier and see if that works, and was your image a fresh flash to Build 142 (with or without a settings restore) or a online update from a previous image ?. all of this information however trivial it seems is vital to us when looking into possible bug reports.
 
Try installing it with the telnet command I posted earlier and see if that works, and was your image a fresh flash to Build 142 (with or without a settings restore) or a online update from a previous image ?. all of this information however trivial it seems is vital to us when looking into possible bug reports.

Installing with telnet command had the same results. It was an image upgrade from build 138 with a setting backup,
unfortunately I won't be doing a clean install just to see if it makes a difference, haven't got the time or interest.
Hope that info is of use.
 
Just to confirm I have done a fresh install of 142 with no settings/plugin restore and XBMC is all good here. [emoji106]
 
But does it actually play your films back? I've scraped my collection on my NAS and it has found information for them all, all my films are 1080p blu-ray ripped mkvs mostly with DTS core audio, none of them play, the player just sits at 0:00 and does nothing, it doesn't crash because if I press stop it takes me back to my list.
It looks like xbmc but if it can't play films then it ain't.
 
i got loads of 1080 blurays rips mkv with dts core audio and most work fine
 
i got loads of 1080 blurays rips mkv with dts core audio and most work fine

Well none are playing back on my solo2 from my nas.
I have just mounted my NAS via SMB directly in the solo2 and all Mkv files play fine so defo a bug with xbmc media playback.
As soon as I reload xbmc and try to play the same files they don't play.
 
Last edited:
unfortunately I won't be doing a clean install just to see if it makes a difference, haven't got the time or interest.

Don't expect much support so. Haven't got the time or interest.
 
On a DUO2 , installed the plugin via Telnet after remote control install from plugins gave 5 second error that everyone is talking about.


Error when starting the plugin is that the Gui can't start

xbmc_e2.webp

And from the debug log mentioned,

Lots of noise and verbose debug output, but the interesting part looks to be

06:33:49 T:1979449344 DEBUG: LoadMappings - loaded node "CEC Adapter"
06:33:49 T:1979449344 DEBUG: LoadMappings - loaded node "Pulse-Eight CEC Adapter"
06:33:49 T:1979449344 DEBUG: LoadMappings - loaded node "iMON HID device"
06:33:49 T:1979449344 DEBUG: CPeripheralBusUSB - initialised udev monitor
06:33:49 T:1978971280 NOTICE: Thread PeripBusUSBUdev start, auto delete: false
06:33:49 T:1979449344 DEBUG: UDisks: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UDisks was not provided by any .service files
06:33:49 T:1979449344 DEBUG: DeviceKit.Disks: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.DeviceKit.Disks was not provided by any .service files
06:33:49 T:1979449344 DEBUG: Selected UDev as storage provider
06:33:49 T:1979449344 NOTICE: InitWindowSystem: Using EGL Implementation: dvbbox
06:33:49 T:1979449344 ERROR: InitWindowSystem: Could not get native display
06:33:49 T:1979449344 FATAL: CApplication::Create: Unable to init windowing system
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1370008 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1389dd0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x135bd90 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1386e18 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1360818 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x13014e8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x13015a8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x13701f0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x12b6930 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1398f78 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1378538 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1366ef8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1346e38 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x12a6df8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1303238 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
06:33:49 T:1979449344 DEBUG: PVRManager - destroyed


############### END LOG FILE ################

############ END XBMC CRASH LOG #############
 
Last edited by a moderator:
I've not done a fresh flash however from what everyone else has said I'm guessing that it would work, as all others who had the same issue it would appear that a fresh install fixed it for them.

Is the official answer then that to use XBMC a fresh install is needed?.
 
Hi,
btw. XBMC and Solo2. Make sure that you have a lot of free flash. I installed it yesterday on my Solo2s with around 45MB of free flash and both installations stopped with device full.

To the play problem. Mount your NAS through E2 and navigate in XBMC to /media/autofs or /media/net NFS and CIFS inside of XBMC are still not perfect.

ciao
 
Last edited:

OpenViX Feeds Status

Back
Top