Posts: 444
Joined: Jan 2013
Reputation:
14
Try Skifta as well and see if that works.
Posts: 113
Joined: Jun 2014
Reputation:
1
I tried Skifta about a year ago and never felt comfortable with it. But anyway.....
So I finally just said to heck with it. I did a recovery on the Chromebox by restoring to Chromium to get the Legacy BIOS back. Then did a Recovery to the original Chrome OS like it was a brand new box.
Followed Matt Devo's guide for standalone OpenELEC.
Whatever the issue was, it's gone. Fired up Mezzmo Android, refreshed the devices and there it is.
Matt, thanks for all of your assistance on this.
Posts: 113
Joined: Jun 2014
Reputation:
1
ACK!!!!
Worked for about an hour, now it has dissappeared from the list of devices again.
I think I might just chalk this up as a lost cause. It wouldn't be a frequently used feature anyway.
Posts: 113
Joined: Jun 2014
Reputation:
1
So, just for kicks I installed XBMCbuntu on my Chromebox today to see if that had any affect.
Just like the install for OpenELEC, it seemed to work fine for awhile (about an hour) and then it just stopped identifying itself as a UPnP device.
Guess it just isn't meant to be.
Is it possible that the skin, Aeon Nox, could cause this?
Posts: 4,512
Joined: Nov 2008
Reputation:
224
Sounds like it might be an XBMC / UPnP issue rather than a ChromeBox one