2016-03-13, 09:30
What is the best way to load kodi back to factory settings? I checked the kodi wiki but didn't see anything (or may have overlooked it). Is there an easy way to do this or a tutorial somewhere? Thanks!
(2016-03-13, 09:30)BB90 Wrote: What is the best way to load kodi back to factory settings? I checked the kodi wiki but didn't see anything (or may have overlooked it). Is there an easy way to do this or a tutorial somewhere? Thanks!
(2016-03-13, 02:24)Matt Devo Wrote:(2016-03-13, 02:02)Scratinthehat Wrote: OK I put the OpenELEC-Generic.x86_64-6.94.2.img in the USB and tried the reboot. I still don’t get the ability to point to the USB. After Kodi comes up it says “Mounted removable Hard Drive USB_DISK” in the lower right hand corner. Then it gives an “auto installation failed”.How are you putting the image onto the USB drive? Win32DiskImager as per the wiki? Have you tried another USB stick?
(2016-03-15, 18:57)gene0915 Wrote: I already have my Chromebox up and running with OpenELEC 6.0.0 (not exactly sure on the version but I know it's 6.x) running Kodi 15.2. I don't want to harm that install and was wanting to play with Kodi 17 on this same hardware and this got me to looking into booting OpenELEC/Kodi 17 from a USB thumb drive to test things out. To piggy back off the existing talk about trying out Kodi 17 on a Chromebox, do I have this right:
1) Download the OpenELEC disc image from: http://openelec.tv/get-openelec
2) Burn the disc image with Imagewriter to USB thumb drive
3) To get Kodi 17 on there, grab a .tar nightly build from Milhouses: http://milhouse.openelec.tv/builds/master/Generic/ (create an 'Update' folder on the newly created OpenELEC USB drive and place the .tar file in there)
4) Boot the Chromebox and press ESC to select the USB drive and after it boots from there, it will automagically apply the v17 nightly of Kodi and away I go? (I'm worried about this because not sure there will be enough space on the thumb drive to unpack/apply the Kodi 17 update. When I last played with that Imagewriter program, I seem to remember it writing the OpenELEC image to my 32 gig thumb drive and then I only saw a few hundred megs free when I looked at it in Windows.)
Just wanted to get all my ducks in a row so when I get some tonight, I can give it a go.
Thanks
(2016-03-15, 20:41)boxito Wrote: Hi i'm new
i have wdlive tv but is getting slow, i have kodi on my pc and like to change the wdlive tv for a Chromebox with kodi have one question can i use like a server have HD connected and share to my other devices xbox, roku, pc on the network ?
i saw this on CHROMEBOX-M004U for $150 should i invest more for the 8gb or a new model ?
thanks for all the help
(2016-03-15, 20:46)gene0915 Wrote:(2016-03-15, 20:41)boxito Wrote: Hi i'm new
i have wdlive tv but is getting slow, i have kodi on my pc and like to change the wdlive tv for a Chromebox with kodi have one question can i use like a server have HD connected and share to my other devices xbox, roku, pc on the network ?
i saw this on CHROMEBOX-M004U for $150 should i invest more for the 8gb or a new model ?
thanks for all the help
Yes, with a Chromebox running Kodi, you can point it to where the files are and let it have at it. Same for a PC....just open up the network share and open your media files. (For a PC, I'd recommend VLC for your media player app.)
As for the Roku, might need to set up Plex Media Server on your server since the Roku (I believe) lacks the ability to directly access network shares like how your WDTV can.
(2016-03-15, 18:57)gene0915 Wrote: I already have my Chromebox up and running with OpenELEC 6.0.0 (not exactly sure on the version but I know it's 6.x) running Kodi 15.2. I don't want to harm that install and was wanting to play with Kodi 17 on this same hardware and this got me to looking into booting OpenELEC/Kodi 17 from a USB thumb drive to test things out. To piggy back off the existing talk about trying out Kodi 17 on a Chromebox, do I have this right:
1) Download the OpenELEC disc image from: http://openelec.tv/get-openelec
2) Burn the disc image with Imagewriter to USB thumb drive
3) To get Kodi 17 on there, grab a .tar nightly build from Milhouses: http://milhouse.openelec.tv/builds/master/Generic/, extract the KERNEL and SYSTEM files from the target directory, and overwrite the ones in the root of the USB folder
4) Boot the Chromebox and press ESC to select the USB drive and after it boots the installer, install to a 2nd USB stick
5) Reboot and boot the 2nd USB stick
Just wanted to get all my ducks in a row so when I get some tonight, I can give it a go.
Thanks
(2016-03-15, 20:41)boxito Wrote: Hi i'm new
i have wdlive tv but is getting slow, i have kodi on my pc and like to change the wdlive tv for a Chromebox with kodi have one question can i use like a server have HD connected and share to my other devices xbox, roku, pc on the network ?
i saw this on CHROMEBOX-M004U for $150 should i invest more for the 8gb or a new model ?
thanks for all the help
(2016-03-16, 02:41)robca Wrote: This is probably more of a OpenElec general question that Chromebox-specific, but I'm running it on Chromebox... I see that Kodi 16.0 Jarvis has officially released, but the supported OpenElec build (6.0.x) is still on 15.2 Isengard.I'm not aware of any stability issues with the OE7/Kodi 16.0 build I've posted, and have been using it myself on my main box for a while now. The main "issue" with it would be that Kodi 16 lacks the playback enhancements of the 15.2 EGL builds, and won't get them back until v17 (the preview builds already have them)
How "safe" is it to run OpenElec 7/Kodi 16 on a Chromebox? Since I'm a beginner when it comes to OpenElec/Kodi, should I stick with 6.0.x? I see a few PVR improvements that seem nice in Jarvis, and I plan to use the device mostly as a PVR/playback for recorded OTA TV, but might not be worth the risk if 7.0 is unstable
(2016-03-16, 05:06)robca Wrote: Thanks Matt, very encouraging. Can you please elaborate further on what playback enhancements are missing? Anything impacting 1080P?The EGL enhancements provide better color fidelity and lower CPU usage (among other things), but IMO the average user is unlikely to notice a difference without test patterns or an A/B comparison.