(2016-09-19, 23:12)Matt Devo Wrote:

(2016-09-19, 22:56)BB90 Wrote: Hi Matt.

I was planning on updating to the Kodi 17 (alpha 7.90.004) build on the Wiki. I noticed on the first page of this thread there have been a lot of various other updates (for example: coreboot, SeaBIOS, etc,etc) when modding the chromebox for the first time. I originally modded this maybe 1.5 - 2 years ago. Are there any necessary upgrades other than just upgrading Kodi?

Also, the link on the wiki for the Kodi 17 alpha build shows ".img.gz" as the file extension, should it be ".tar" for updates?

Thanks!

looks like I need to update the wiki links, since 7.90.005 is the latest.

since you're running a dual boot setup, the coreboot firmware update doesn't apply. The SeaBIOS legacy boot updates are all minor and have no substantial effect on a dual boot setup.

Given that you originally set things up with an older version of OpenELEC, I highly suspect that the system partition created then (automatically, by the script) isn't large enough for the newer LibreELEC builds. It's probably not a bad idea to do a factory reset and redo your dual boot setup unless you want to boot a Linux live USB and manually resize the partitions (which isn't terribly hard IMO)

(2016-09-20, 06:18)BB90 Wrote: Thanks for that info! I guess I misspoke when I started naming off the boot firmware/bios stuff. I installed the standalone OpenElec originally, but since then now on standalone LibreElec. Since it is not a dual boot, will the partitions still be smaller?

(2016-09-20, 13:09)usamac Wrote: Does that command define the path by default, or was I supposed to adjust it accordingly?

(2016-09-20, 13:19)bbsc Wrote:

(2016-09-20, 13:09)usamac Wrote: Does that command define the path by default, or was I supposed to adjust it accordingly?

Yes, it does. And yes, you were. If you downloaded somewhere else.
dpkg command cannot find the file.
Either you've downloaded it to somewhere else or the filename differs.

(2016-09-20, 15:58)usamac Wrote: If I need to specify the file name outside of what is in the folder, then does that mean I need to unpack/unzip it first? I would think that was part of the process, but in Linux is it merely going into that and looking for the file in sort of a sub folder format?

(2016-09-20, 16:11)bbsc Wrote:

(2016-09-20, 15:58)usamac Wrote: If I need to specify the file name outside of what is in the folder, then does that mean I need to unpack/unzip it first? I would think that was part of the process, but in Linux is it merely going into that and looking for the file in sort of a sub folder format?

You don't need to do anything else. Just download and install.
You definitely need to specify that filename which is in your folder. I only want to say that it may be different, depending on what program you've used to download it. If you use FF you may get teamviewer_11.0.57095_i386.deb, if you use curl you'll get teamviewer_i386.deb
From terminal:

Code:

cd ~/Downloads
curl -L -O https://download.teamviewer.com/download/teamviewer_i386.deb
dpkg -i teamviewer_i386.deb

This will work.

(2016-09-14, 08:06)McButton Wrote: 2nd point: I've been fighting the Chromebox "no audio on restore" issue for a year.
I applied the patch that MattDevo suggested at the time, but it never took hold. On my old TV, it was never an issue. The new TV must register the HDMI ports differently when it idles or something.

That said, is there a new, cool update or fix for this issue now?
Rather than just leave the box ON all the time, I'd rather just use "suspend" and hit a button to restore it from sleep.
Thanks in advance for any advice!

1. Use a suspend/resume script to disable the audio on sleep and re-enable on wake
   
2. leave the Chromebox on all the time
   
3. use the suspend/resume script to reboot the Chromebox on wake
   

(2016-09-21, 07:51)McButton Wrote: The suspend/resume and reboot script would likely work fine. I like keeping everything where I was at, so maybe not this. I think I'm currently using the audio reset method now. My settings are like that in the wiki:

mkdir -p /storage/.config/sleep.d
cd /storage/.config/sleep.d
curl -L -O https://mrchromebox.tech/files/kodi/01-cbox_resume.power
chmod +x 01-cbox_resume.power

I'm using HDMI1 and change the timing a bit too. I set it to like 8 seconds to let my TV warm up before the Chrombox sets, but notta.

Odd that it just isn't working with my TV.

(2016-09-22, 09:13)knives of ice Wrote: ok i finally decided to upgrade to Krypton creating the usb and reinstalling everything.

i have everything back up and running but i am absolutely going insane because my harmony remote will not connect via bluetooth anymore to the libreElec interface. i have no idea what the problem is i keep getting an error message when going through the connection process. has anyone had similar problems and can you offer any tips?

just tried again the error i get each time is bluetooth error did not receive a reply