Kodi Community Forum

You are in the right place.

(2015-11-02, 04:56)Matt Devo Wrote: [ -> ]

(2015-11-02, 04:37)maynard64 Wrote: [ -> ]doh, thank you... I'll get started reading.

I'm current running an amazon fire stick and I also have some kind of a box with "MX" on it, tried them both from time to time. ... with these two I am very disappointed with picture clarity (quality) and I'm looking for something better..

Am I heading in the right direction?

An Intel GPU coupled with the new OE EGL/development builds are pretty much the best you'll find. My setup script will be getting updated with OE 6.0 final later tonight, and have the EGL dev version as an option as well.

Thanks for the heads up, 6.0 installed!

(2015-11-02, 05:39)maynard64 Wrote: [ -> ]Matt... yer killing me. remember, I'm a noob. Is there some kind of device I can buy and have good TV quality without Cable?

Kodi is just the application/platform for content playback; it doesn't provide or provide access to any content. While there are numerous addons which do provide streaming content, the vast majority are of low quality, and are not allowed to be discussed here because of their legality (or lack thereof). Legal addons can be discussed in the various addons subforums.

That said, the ChromeBox will provide you with one of the best Kodi platforms available for the price.

Also, sending you a PM

(2015-11-02, 04:56)Matt Devo Wrote: [ -> ]My setup script will be getting updated with OE 6.0 final later tonight, and have the EGL dev version as an option as well.

script updated to OE 6.0 final. EGL dev version will come later

(2015-11-01, 04:17)Matt Devo Wrote: [ -> ]Trick or Treat!

posted a workaround on the wiki for the high fan speed on resume from suspend on OE 5.95+. Still investigating the root cause to see if a firmware change is required, but this will do for now

This and OE 6.0 final released is great! NICE!

(2015-11-02, 04:03)Matt Devo Wrote: [ -> ]

(2015-11-02, 00:50)rodalpho Wrote: [ -> ]Matt, this should probably be added to your wiki page. I'm happy to do it if you want, don't want to step on your toes.

Turning off ACPI is kinda like killing a fly with a sledgehammer. I'd prefer it be used temporarily just to boot/install and the new a fixed/working kernel installed. But if you want to throw it up there for now that's cool

I added it with your caveat that this should be removed when 4.3 releases.

Don't ever turn off acpi ... not matter what happens. This will crash / burn your device and if you are unlucky one cpu will be left when run in that mode. modern system don't work without ACPI at all.

(2015-11-02, 06:31)Matt Devo Wrote: [ -> ]

(2015-11-02, 04:56)Matt Devo Wrote: [ -> ]My setup script will be getting updated with OE 6.0 final later tonight, and have the EGL dev version as an option as well.

script updated to OE 6.0 final. EGL dev version will come later

script updated to use fritsch's custom Intel-EGL OpenELEC build as the default option. Also updated the wiki with info/links on the Intel-EGL builds

I have standalone Openelec install, and now i want to try dual boot (Openelec/Chromeos).

My problem is that I get serious errors when try to go back to stock firmware.

THIS WENT WELL:

Boot the Linux live USB(Ubuntu 14.04.3 LTS) then open a terminal/shell window (ctrl+alt+f2)
Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):

AND NOW START THE PROBLEMS:

curl -L -O https://goo.gl/1hFfO3
sudo bash 1hFfO3


all i get after sudo command is error:

line 24: ./functions.sh No such file or directory
line 27: prelim_setup: command not found
line 29: return: can only ´return´from a function or source...
line 33: menu:fwupdate: command not found

What went wrong? And is this the only way to get back to stock, and then reinstall openelec and chromeOS?

Thankyou.

Matt,

Could you provide a link to fritsch's custom Intel-EGL OpenELEC build?

I will be updating manually and want to make sure I install the right version...

Also, once this build is installed, will minor updates have to be done manually as well? I assum if there is an official update from the OE guys, these will not be compatible with fritsch's build...is this correct?

Thanks in advance!

Tried several time but i get:


Reading current firmware

Downloading coreboot firmware
curl: Remote file name has no length!
curl: try 'curl --help' for more information

coreboot firmware download checksum fail; download corrupted, cannot flash.
OpenELEC:~ #

thank you

(2015-11-02, 21:22)Suolikaasu Wrote: [ -> ]I have standalone Openelec install, and now i want to try dual boot (Openelec/Chromeos).

My problem is that I get serious errors when try to go back to stock firmware.

THIS WENT WELL:

Boot the Linux live USB(Ubuntu 14.04.3 LTS) then open a terminal/shell window (ctrl+alt+f2)
Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):

AND NOW START THE PROBLEMS:

curl -L -O https://goo.gl/1hFfO3
sudo bash 1hFfO3


all i get after sudo command is error:

line 24: ./functions.sh No such file or directory
line 27: prelim_setup: command not found
line 29: return: can only ´return´from a function or source...
line 33: menu:fwupdate: command not found

What went wrong? And is this the only way to get back to stock, and then reinstall openelec and chromeOS?

Thankyou.

looks like curl didn't download anything. What's the output when you enter the curl command?

(2015-11-02, 21:22)Suolikaasu Wrote: [ -> ]I have standalone Openelec install, and now i want to try dual boot (Openelec/Chromeos).

My problem is that I get serious errors when try to go back to stock firmware.

THIS WENT WELL:

Boot the Linux live USB(Ubuntu 14.04.3 LTS) then open a terminal/shell window (ctrl+alt+f2)
Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):

AND NOW START THE PROBLEMS:

curl -L -O https://goo.gl/1hFfO3
sudo bash 1hFfO3


all i get after sudo command is error:

line 24: ./functions.sh No such file or directory
line 27: prelim_setup: command not found
line 29: return: can only ´return´from a function or source...
line 33: menu:fwupdate: command not found

What went wrong? And is this the only way to get back to stock, and then reinstall openelec and chromeOS?

Thankyou.

your network connection died, and the script wasn't able to pull the required files needed to run. Fix your network connection and try again. You can certainly do everything the script is manually, but flashing back the stock firmware is the only way to be able to run ChromeOS (securely, with automatic updates)

(2015-11-02, 21:23)jmhenry5150 Wrote: [ -> ]Matt,

Could you provide a link to fritsch's custom Intel-EGL OpenELEC build?

I will be updating manually and want to make sure I install the right version...

Also, once this build is installed, will minor updates have to be done manually as well? I assum if there is an official update from the OE guys, these will not be compatible with fritsch's build...is this correct?

Thanks in advance!

link is on the wiki. subsequent updates are manual. Any further updates will require an updated Intel-EGL build; you will be able to use the standard OE updates, but then you'll lose the benefits of the Intel-EGL version. If fritsch doesn't do any further builds, I'll do them myself.

(2015-11-02, 22:09)Roby77 Wrote: [ -> ]Tried several time but i get:


Reading current firmware

Downloading coreboot firmware
curl: Remote file name has no length!
curl: try 'curl --help' for more information

coreboot firmware download checksum fail; download corrupted, cannot flash.
OpenELEC:~ #

thank you

a space got eaten somehow in the latest.version file, fixed

Worked, thank you again

Hi Matt:
Updating to OE 6/ Kodi 15.2, I noticed when I play 24p material, when I press the O key, the audio delay is displayed as -.175 even though in the OSD audio menu it's set to zero. When I play 60p material it's all zeros.

Audio seems to be in-sync with both sources. As a former Kodi--Windows user, that delay value seems familiar. :-)

I never really noticed this before, is this correct? Thanks.