(2015-01-31, 10:33)pascal31 Wrote: Hello,
I have installed openelec on my HP chromebox following this tuto and it work perfectly except the remote control.
I have tested 2 devices as remote control for kodi, both run but they are not so usable, I will explain:
a) Logitech K400 (wireless keyboard/mouse)
The keyboard and the mouse run but with a lot of latency and sometime some freeze, so it is not really usable.
b) Airstick RF-12G
This is a remote controler with giroscope for mouse emulation.
The remote run, but the mouse is too sensible so it's not usable.
Do you know how to configure or to tune these devices in openelec ?
a) sounds like low batteries, I have a friend who uses a K400 without issue. For b) you need to start a separate thread in this forum, it's a general Kodi/hardware input config issue, not a ChromeBox one
(2015-01-31, 15:10)YippeeKaiay Wrote: Hi I have installed openelec standalone and I when I run the openelec setup flash drive there is an option to update bios. Do I need to run this and is this how we update any fixes you have pushed? Thanks
Absolutely not -- notice it says 'OEM only'; though I believe there's not any functionality implemented there. You don't need to update the firmware unless you're having an issue that the change log at the end of the first post specifically mentions a fix for. But if you were to, you'd use the standalone firmware updater script, also in the first post.
(2015-01-31, 16:54)xi_Slick_ix Wrote: No overnight fixes expected! I was just curious how this was progressing. I won't lie, seeing the HP Stream Mini for $20 more than this Asus hurts a bit on the inside, lol.
The HP is currently unavailable, and who knows what quirks it might have. You have by far the (IMNSHO) best supported Kodi device out there. That's gotta be worth at least as much as HDMI audio in Windows ;-)
(2015-01-31, 17:03)bolmsted Wrote: Amy idea why the chromebox becomes unresponsive via xbmc remote over night on my iPhone? Seems like I need to reboot via openelec ssh to get access again. Hopefully won't be an issue once I get IR sensor to control with my remote. Is the box going asleep or something - wake on lan I have a vpn setup to run via autostart.sh so would like to keep that up or on wol
if it's only unresponsive to your phone app, it might be an issue with your phone app. Test with a kb/mouse to confirm.
(2015-01-31, 19:55)plinkyplonky Wrote: I appear to have bricked my ASUS Chromebox. Having installed the standalone firmware to boot successfully into Ubuntu, which worked fine, I wanted to put the Chromebox back to its original state with ChromeOS on it.
Ran the AMD64OS as stated in section 6.3 of the wiki and wrote the stock firmware back to the Chromebox, which I had backed up before doing the standalone firmware. Rebooted and I just get a black screen. Tried the recovery button, power with the Google recovery USB disk but nothing appears on the screen anymore, just the powerlight comes on with the fan. Tried to boot the AMD64OS again but nothing.
Looks like it is totally bricked. Any other options?
after it powers on, does pressing the power button turn it off immediately, or do you need to hold it? If the former, it is likely bricked. Shoot me a PM and we'll get it sorted