[giant25]

I don't have a good answer to solve the problems with your receivers, but I use a Flirc with my Harmony 650 and Chromebox OE setup flawlessly. I highly recommend it, way easier to set up. Good luck.

It was very hit or miss for me. There were times when it worked fine, and I liked the flexibility and ease of setup, but lately it had become basically unusable. Hitting keys would result in an endless loop of repeating that key, so things like scrolling through a list of movies would just start cycling through endlessly until I rebooted the box. I tried pretty much every possible combination of settings for interkey delay, repeat, etc in both the Harmony software and the Flirc software, and none of them worked, I'd still get random key explosions

Fair enough. I found that the new firmware on the Flircs is very stable compared to the old days, and the built in profile within the Harmony for Kodi works great. I have zero problems with repeat characters, etc on both my Chromebox and Pi 2 running OE. If you have one, update the firmware and give it another fair shake if you get desperate.

[Matt Devo]

No such luck. Not sure if its a file permissioning problem. I can download and run the ez script but having problems with the coreboot file. Is there another goo.gl link I should try?

whoops, problem was a mismatch between the filename in the script and the one I actually used; the former got updated but the latter did not. Should be good to go now.

[teki4u]

I don't have a good answer to solve the problems with your receivers, but I use a Flirc with my Harmony 650 and Chromebox OE setup flawlessly. I highly recommend it, way easier to set up. Good luck.

I feel like I'm alone in detesting the Flirc, since others seem to swear by it, but I could never get it working reliably (and dislike being limited to a keyboard emulator) whereas the MCE receivers have worked nearly perfectly OOTB for me.

Hi Matt you can also map Multimedia/Consumer Keys (table 12 of USB HID usage table) apart of keyboard keys (table 7) using flirc_utils.exe (Windows) or flirc_utils (Linux/OSX) in CLI.

I used the following tutorial to do so:
http://forum.flirc.tv/index.php?/topic/1...-keyboard/

The usable values he mention are more than enough for most users, I used those and a modified Generic HID plugin for my Inteset INT-422 + Flirc + EventGhost setup, also use keyboard.xml for few special key maps in Kodi.

[teki4u]

I don't have a good answer to solve the problems with your receivers, but I use a Flirc with my Harmony 650 and Chromebox OE setup flawlessly. I highly recommend it, way easier to set up. Good luck.

It was very hit or miss for me. There were times when it worked fine, and I liked the flexibility and ease of setup, but lately it had become basically unusable. Hitting keys would result in an endless loop of repeating that key, so things like scrolling through a list of movies would just start cycling through endlessly until I rebooted the box. I tried pretty much every possible combination of settings for interkey delay, repeat, etc in both the Harmony software and the Flirc software, and none of them worked, I'd still get random key explosions

Probably because you updated software/firmware. I've red many post where people claim their devices worked better with old firmware, but it could be the opposite depending on the remote.

[mpowers]

Hi Matt, thanks for putting this out there, I've used it flawlessly for the last few years but have now run into a problem I can't seem to troubleshoot.

For some reason I seem to be stuck in a boot loop and can't get past the loading screen. The cursor shows up, the logo flashes and then this repeats incessantly. I haven't tried much because I don't know where to start. I've seen some other people post that this was a known bug in a build circa 2014, but it's the first time it happened to me.

I'm running openelec standalone on an Asus chromebox, I don't know the specific build as I can't get in to check.

My first thought is I should try a clean install, but I don't know how to wipe the old version or if I can just stick the USB boot in and it will overwrite and start from scratch.

Thanks in advance!

IIRC, the problem is a corrupted addon/addon data that causes Kodi to to crash and continually reload. Since it's just Kodi that's crashing/restarting and not OpenELEC, you can still access things via SMB or SSH to try and figure out which addon it is and remove it. Or, you can just blow everything away and start fresh, which is as simple as booting updated OpenELEC install media and choosing the quick install option (which partitions/formats the selected drive).

OK don't know what SMB/SSH are so going to have to leave that one alone.... But, another stupid question but what do you mean by as simple as booting updated OpenELEC install media? I should basically imagine I have a clean box and reinstall over it? The thing also turns on so fast that I can't get into any boot menu unfortunately either, just flashes right to Kodi and goes into the boot loop.

[Matt Devo]

OK don't know what SMB/SSH are so going to have to leave that one alone.... But, another stupid question but what do you mean by as simple as booting updated OpenELEC install media? I should basically imagine I have a clean box and reinstall over it? The thing also turns on so fast that I can't get into any boot menu unfortunately either, just flashes right to Kodi and goes into the boot loop.

there's a download link on the wiki for the latest OpenELEC install image, and a link to OpenELEC's wiki instructions for creating the install media. When the ChromeBox is powered on with multiple boot devices available (eg, a USB stick inserted), you have 5s to press ESC and bring up the boot menu; when only a single boot device is found (the internal ssd) the boot menu prompt is skipped.

[rich110]

This may seem like a stupid question, but where is the best place to post troubleshooting questions for these OpenElec builds?

I am using the 6.0.98-fritz build on an Asus Celeron chromebox. Sometimes, seemingly at random, when I change between different video streams {for example changing directly from a live tv stream to a video on my NAS box) the audio in Kodi disappears and can't be restored without a reboot.

I've thought about posting at the Openelec forums but it seems really quiet over there and not terribly active. I would post here at the Kodi forums, but I'm not sure where the best place would be to do it for such a specialised build (plus it is Openelec, not pure Kodi).

Any recommendations?

Cheers, Rich

[Matt Devo]

This may seem like a stupid question, but where is the best place to post troubleshooting questions for these OpenElec builds?

the EGL thread in the linux support forum, however the Kodi v15.2 EGL stuff isn't supported anymore. All the work moved to v17 a while back, and those test builds are what the devs are interested in getting feedback on.

[rich110]

Thanks Matt. I might give the v17 versions a shot when I'm feeling brave. How is the addon support for them?

[jrochet]

I'm currently on like month 7 or 8 of flawless victory with single boot OpenElec on my Chromebox, stumbled a little with finding my favorite remote which is finally the Harmony 350+Flirc and only one custom keymap button (power = suspend). Everything is wonderful!, except I'm considering changing over to Ubuntu so that I can start to use autodl-irssi. Just wondering if anyone has any negative feedback on the Ubuntu front for Chromebox that might persuade me to not bother. Anything based on Flirc and my Harmony specifically with Chromebox and Ubuntu that stands out would be great to hear. Or any other shortcomings in general when comparing Ubuntu on Chromebox to OpenElec on Chromebox.

Thanks in advance!

[michi_jl]

Hey Matt,

maybe you should add the ubuntu path to the troubleshooting sleep.d scripts.
In ubuntu you need to use

Code:

/lib/systemd/system-sleep/

instead of

Code:

/storage/.config/sleep.d

Maybe would help some people

EDIT:

Also in the 01-cbox_resume.power script

Code:

xrandr --output HDMI1...

needs to be

Code:

xrandr --display :0 --output HDMI1...

[Matt Devo]

Thanks Matt. I might give the v17 versions a shot when I'm feeling brave. How is the addon support for them?

unsure, I'm still running 6.0.98 on my main box as I'd have no reason to upset something running without issue.

I'm currently on like month 7 or 8 of flawless victory with single boot OpenElec on my Chromebox, stumbled a little with finding my favorite remote which is finally the Harmony 350+Flirc and only one custom keymap button (power = suspend). Everything is wonderful!, except I'm considering changing over to Ubuntu so that I can start to use autodl-irssi. Just wondering if anyone has any negative feedback on the Ubuntu front for Chromebox that might persuade me to not bother. Anything based on Flirc and my Harmony specifically with Chromebox and Ubuntu that stands out would be great to hear. Or any other shortcomings in general when comparing Ubuntu on Chromebox to OpenElec on Chromebox.

Thanks in advance!

it will take considerable more work to set up Ubuntu and get it close to the same level of stability you have now with OpenELEC, and you likely won't get there. There are lots of alternatives to autodl-irssi that do work well under OpenELEC, perhaps it's a good time to re-evaluate those?

Hey Matt,

maybe you should add the ubuntu path to the troubleshooting sleep.d scripts.
In ubuntu you need to use

Code:

/lib/systemd/system-sleep/

instead of

Code:

/storage/.config/sleep.d

Maybe would help some people

not being a Ubuntu user, I'm not able to provide/test solutions for it. The wiki is open for editing, so you're welcome to create an account and add the info yourself

[jrochet]

Do you have the same disclaimer for Kodibuntu as with Ubuntu (regarding the autodl-irssi)? I know it's not the place but I can't seem to find anything for OpenElec around this other than a dev on OpenElec's forums stating autodl-irssi won't work. I'll continue researching though.

[Matt Devo]

Do you have the same disclaimer for Kodibuntu as with Ubuntu (regarding the autodl-irssi)? I know it's not the place but I can't seem to find anything for OpenElec around this other than a dev on OpenElec's forums stating autodl-irssi won't work. I'll continue researching though.

I'm just talking about overall, nothing specific with autodl-irssi. With OpenELEC, everything works out of the box; with Ubuntu/Kodibuntu etc, remotes, Bluetooth, video drivers, etc will likely need some TLC to get working 100%, that's all.

[Soli]

Been running Kodibuntu a good while now. I find that it suits me better than OE, and easier to tweak. But that is a double crossed sword.. I never got comfortable using OE, and Kodibuntu is for me smoother in use. I found my bluez setup worked better than OE. (Using a ps3 bd remote wakes faster from sleep, and I can set custom timeouts instead of waiting for the screensaver, and I never found out how to change the button maps, although I didn't try that hard since I had a working solution with Kodibuntu)