[pglover19]

Matt,

I have followed your instructions and successfully installed the dual boot option. Now I just want to have the standalone option. What process do I need to follow to start over and install the standalone option? Please advise.

just follow the standalone setup instructions. If you're running OE, you can back up your config using the OE backup function (Settings/OpenELEC/General), copy the backup file to another PC, and restore after completing the standalone setup,

I don't have a need to save the old OpenELEC configuration file. I want to start fresh with the standalone option.

[Matt Devo]

just follow the standalone setup instructions. If you're running OE, you can back up your config using the OE backup function (Settings/OpenELEC/General), copy the backup file to another PC, and restore after completing the standalone setup,

I don't have a need to save the old OpenELEC configuration file. I want to start fresh with the standalone option.

ok? so don't backup/restore then

[pglover19]

Matt,

I have followed your instructions and successfully installed the dual boot option. Now I just want to have the standalone option. What process do I need to follow to start over and install the standalone option? Please advise.

just follow the standalone setup instructions. If you're running OE, you can back up your config using the OE backup function (Settings/OpenELEC/General), copy the backup file to another PC, and restore after completing the standalone setup,

I don't have a need to save the old OpenELEC configuration file. I want to start fresh with the standalone option.

Do I need to execute these steps again for the standalone option? Please advise...

•Put the ChromeBox in developer mode
•Open the ChromeBox and remove the write-protect screw

[Stereodude]

I'm going to wager you haven't read the wiki / applied the full-range output setting as noted?

No, I didn't know there was such an entry in the wiki.

That's not specific to the Chromebox, it's the expected and default behaviour for Intel GPUs. They default to the standard consumer 16-235 level (which all HDMI gear accepts as default levelspace - and is often the only levelspace output from boxes like DVD players and Satellite/Cable boxes), at least they do when you are running a "TV" resolution like 720p, 1080i or 1080p. (16-235 is the 'normal' level space for digital video - it's what Blu-ray, DVD and broadcast digital TV uses)

That's not exactly correct. Consumer electronics gear uses YCbCr 16-235. If you send YCbCr it has to be 16-235. That's the format. CE devices don't use RGB 16-235. RGB is supposed to be 0-255. RGB 16-235 is like a redhead stepchild of video formats. It shouldn't be used, and certainly shouldn't be the default.

[Matt Devo]

Do I need to execute these steps again for the standalone option? Please advise...

•Put the ChromeBox in developer mode
•Open the ChromeBox and remove the write-protect screw

no, just re-run the script. Your ChromeBox is already in developer mode and the WP screw is already removed, there's nothing to redo there.

[kenz]

I picked up an Acer CXI Chromebox. Will the dual boot script work with this? If so does anyone know how to turn off the firmware write protect? Thanks.

cmon dude, did you even bother reading the first post?

Sorry Matt. I've read most of this thread including the first post and the link to the wiki. I missed the fine print and thought the motherboard photos were just the two sides of the ASUS box not the Acer. I had also done a search on Acer and there was a thread that the last post was you replying that there was probably some issue with the Acer and your ezscript. Thanks for the help.

[kenz]

Ok just finished everything to setup Chrome/OpenELEC bootup and it all seemed to go well. Problem is I don't get any kind of boot options. I tried changing the delay to 30 seconds thinking I might have missed it but no difference. When it boots all I see is a black screen for a couple seconds then straight into Chrome. I saw someone else with the same issue a few pages back post# 2581 but didn't see a solution. I did do the factory reset before the ezscript. Any ideas?

[Matt Devo]

Sorry Matt. I've read most of this thread including the first post and the link to the wiki. I missed the fine print and thought the motherboard photos were just the two sides of the ASUS box not the Acer. I had also done a search on Acer and there was a thread that the last post was you replying that there was probably some issue with the Acer and your ezscript. Thanks for the help.

one or two people with the Acer ChromeBox had issues because they ran the standalone setup / firmware update without having the (correct) write protect screw removed, which corrupted the portion of the firmware that is normally writable. I have since added a check to the firmware to ensure that the write-protect is disabled, so there's shouldn't be any further issues.

please let me know if there's anything I can add/change to the documentation to make things more clear (short of adding model numbers, which vary by region)

---

Ok just finished everything to setup Chrome/OpenELEC bootup and it all seemed to go well. Problem is I don't get any kind of boot options. I tried changing the delay to 30 seconds thinking I might have missed it but no difference. When it boots all I see is a black screen for a couple seconds then straight into Chrome. I saw someone else with the same issue a few pages back post# 2581 but didn't see a solution. I did do the factory reset before the ezscript. Any ideas?

do you see the white developer boot screen prior to ChromeOS loading?
what boot options setting did you select in the script?

[kenz]

I actually already had the screw out before I did anything so wasn't an issue.Never did a standalone/firmware update. Just did the Chrome/OPen dual made my 9 GB partition. Did reboot and Chrome repaired itself. I then reran the script then selected Chrome /Open dual boot from script again. It went through and did the openelec install and I set the boot option to 30 seconds.

[kenz]

Going to start over from the beginning again and see if that helps. One thing I'm not clear on is once all the setup is done are you supposed to leave it in developer mode forever?

[teki4u]

Thanks. Was able to install OE5.0 and added the recommended adjustments to the settings. However I'm still struggling with videos freezing while subtitles and audio continuing. Was hoping this issue would disappear after the update.

Is this the dreaded Intel bug? If so the workaround in the wiki isn't working for me.

in kodi OE5.0 you need to uncheck the whole "VAAPI hardware acceleration" option, not only the "prefer VAAPI" one. But OE 5.0 was supposed to have the freeze bug fix (confused).

Don't spread any things that are not true. The chromebox works perfectly fine with 5.0 - I let it test by at least 3 different chromebox testers whit a whole lot of different samples. So whatever "freeze" is arround now needs proper logfiles, including kernel logs. It's not a freeze about some "internet streams from somewhere that fell of a truck" or something.

whatever. i was just trying to help as the only freeze bug has been the one we ALL know, so i suggested based on that. Now if it's not related to that then his bad, he will need to troubleshoot, provide log files and so on.

---

btw @matt can you add this keyboard to the WIKI as one that work well with the chromebox http://www.amazon.com/gp/product/B00BTQJ...UTF8&psc=1
that's the one i have and works great in boot menu and CLI when your script is downloaded.
I used to use Openelec standalone but now i use ubuntu server and for everything i've run in it that remote control has worked as expected.

[Matt Devo]

I actually already had the screw out before I did anything so wasn't an issue.Never did a standalone/firmware update. Just did the Chrome/OPen dual made my 9 GB partition. Did reboot and Chrome repaired itself. I then reran the script then selected Chrome /Open dual boot from script again. It went through and did the openelec install and I set the boot option to 30 seconds.

there's two 30s options - ChromeOS and OpenELEC - I assume you chose the former? Do you not have 30s to press [CTRL-L] and boot into OpenELEC?

Going to start over from the beginning again and see if that helps. One thing I'm not clear on is once all the setup is done are you supposed to leave it in developer mode forever?

since we don't know what the problem is, there's no guarantee simply repeating the same steps again will result in a different outcome. As for your question, section 1.2 of the wiki is pretty clear:

The developer boot screen, shown above, has a warning about OS verification being off. Do not hit [SPACE] to re-enable OS verification, as it will return the device from developer mode to standard/verified boot mode. The ChromeBox must remain in developer mode, else you will have to redo the setup from the beginning.

whatever. i was just trying to help as the only freeze bug has been the one we ALL know, so i suggested based on that. Now if it's not related to that then his bad, he will need to troubleshoot, provide log files and so on.

---

btw @matt can you add this keyboard to the WIKI as one that work well with the chromebox http://www.amazon.com/gp/product/B00BTQJ...UTF8&psc=1
that's the one i have and works great in boot menu and CLI when your script is downloaded.
I used to use Openelec standalone but now i use ubuntu server and for everything i've run in it that remote control has worked as expected.

fritsch's point is that many different problems can manifest in the same symptoms, so without providing logs you can't be sure the cause. The Intel GPU hang bug -- which caused the video to pause while audio continued, and was mitigated by the 'Use SW Filter/Prefer VAAPI Renderer' settings -- was definitively fixed in OE 5.0.0. If people are still seeing those symptoms, it's caused by something else entirely, and the issue needs to be investigated. But assuming it's the same problem as before with the same workaround is not correct.

As for the keyboard, I'm not listing working ones on the wiki currently, but there is another thread which is collecting that info. I'll likely add a link in the wiki to that thread in the near future.

[kenz]

Ok so I think I have it working. It comes up with OS verification is off screen and I get a few firmware messages up in the left corner. So from there I can let it go and it boots into Chrome or hit Ctl-L and it will boot into OpenElec. Is that what I should see? That's not real clear from the wiki.Maybe a screen shot would help. I guess I was looking for a command prompt dual boot menu. Question though. This is for my daughter's room. If she accidentally hits the space bar and turns OS verification back on does screw everything up? Thanks for all your help

[Matt Devo]

Ok so I think I have it working. It comes up with OS verification is off screen and I get a few firmware messages up in the left corner. So from there I can let it go and it boots into Chrome or hit Ctl-L and it will boot into OpenElec. Is that what I should see? That's not real clear from the wiki.Maybe a screen shot would help. I guess I was looking for a command prompt dual boot menu. Question though. This is for my daughter's room. If she accidentally hits the space bar and turns OS verification back on does screw everything up? Thanks for all your help

the black text in the upper corner of the developer boot screen simply indicates that the boot flags have been set to a non-default value; from there you must use the keyboard shortcuts to boot whichever OS is not set as the default. I'll add something to make it more clear on how one selects the OS in a dual boot setup.

If developer mode is exited by hitting space, ChromeOS developer mode is exited, and all ChromeOS user data is erased. The dual-boot setup is not affected, outside of being inaccessible. You would simply need to re-enter developer mode, at which point the boot flags and dual boot setup would be as they were previously.

[rodalpho]

1) there is no dreaded intel bug anymore, it is fixed

It's only fixed in OE5, right? For stock ubuntu, users need to patch their own kernel or wait for ubuntu to update, as I understand it.