Posts by chewitt

Quote from bubblegum57

Alas, still can't get BBC iPlayer here..

I have the same issue, even if I use a UK connection, so I go into the settings to disable vpn with iplayer

If you resolve an IP to the ASN block that owns it you can tell (with reasonable accuracy) whether an IP is domestic or used for hosting, and similar to Netflix the BBC has started to routinely and aggressively block IP ranges associated with commercial hosting services. Combined with basic source IP monitoring (so you can see concentrations of connections coming from the same VPN exit nodes) it's quite simple to block VPN service providers.

The remote conf will go in /storage/.config (which is writable) not /etc/ which is part of a read-only filesystem.

No support. LE supports the hardware which RK targets for mainline kernel development: http://opensource.rock-chips.com/wiki_main_page

RK3066 is an older chip that is not listed, so no support, and IMHO it's unlikely mainline kernels (and thus LE) will ever have support.

There's nothing we can do about the original Slice theme as it wasn't maintained by Five Ninja's (or anyone else, largely because it contained fonts that were not licensed for open/public distribution) and Kodi moved on so the old skin is incompatible and missing things. Estuary has some alternative colour options though, and IMHO the dark blue (almost Slice-blue) "midnight" colour scheme is nicer than the default. If you're desperate for something more Slice-like during boot you can run "mount -o remount,rw /flash" and copy the file dropbox linked below to /flash/oemsplash.png. It's a simple tweak that will survive upgrades. It's the original 'noobs' boot splash that Slice used, but with the "press to enter recovery mode (=)" blanked out as we don't ship noobs as part of our OS images.

Dropbox - slice_1080p.png

From now on you can update from the Kodi GUI using the LE settings addon. See

- the skin and settings addon layouts will change a little in LE 9.0 from what's in the video but the core idea/process remains the same. No need to flash the CM3 card again unless something goes bad and you deliberately want to do it.

Connman (the connection manager) supports hotspot/tethering on Ethernet in addition to WiFi although this is not enabled by default or exposed in the settings addon GUI at all. If you "cp /etc/connman/main.conf /storage/.config/connman_main.conf" and edit the /storage file you can enable it (reboot to take effect). Then use connmanctl to activate the tether against Ethernet, and connect a laptop/desktop via Ethernet. Now if you connect the RPi to the Xfinity WiFi the tethered device on Ethernet will share the same connection which allows you to complete the login process from a normal browser.

YouTube

^ T820 (S912) on mainline kernel with panfrost. It's still a long way from useable, but there's a light at the end of the long dark tunnel

Two requirements:

a) The remote presents itself as a USB keyboard

b) The USB port it's connected to remains powered during whatever S3/S4 state the laptop enters

If neither of the above are true, the "keyboard" won't be able to wake the hardware. The alternative is the laptop has IR hardware that's designed to support remote wake events, but that's unlikely.

Probably because git is just a basic thing. Add any container based on a conventional distro and install git.

There are no script hooks in the 'wake' process where you can add a delay, so basically the answer is no. First question would be whether updates to NUC firmware (if any) and newer LE/Kodi make a difference?

Not natively supported or via any known add-on. Go docker.

Your definition of easier requires a multi-hour compile of a new image vs. 2 minutes work copying the oemsplash.png file. Unless you're doing some kind of bulk changes to many boxes (which means you're some kind of dodgy pirate box seller and you should go suck lemons) it's a sledgehammer to crack a walnut.

Manufacturers are dumb about this kind of thing. They know kernel maintainers will give them work so they sit on their kernel changes until they think everything is perfect. Then eventually they submit and the kernel maintainers still pick everything apart and send stuff back for rework. Instead they should just submit early, get the feedback, then incorporate the feedback and resubmit. Sometime it takes 3-4 iterations to get everyone on-side and the kinks worked out, but persistence pays dividends - because once you get stuff upstream other people start caring about maintaining it.

WireGuard is nice and something I'm looking into .. but I doubt we'll add anything formally into LE until it gets merged into the Linux kernel. It requires a kernel module so it's not going to be an add-on.

1. Solved by using Ubuntu or Fedora etc. - LE is intentionally not a Desktop using OS

2. Depends on the Skin .. Estuary is intentionally simple and not too customisable

3. Kodi web interface has a remote control function, as do numerous phone 'remote' apps

4. Nothing's directly supported today on LE, but rsync + cron can solve most cloudy backup things

It's an RK3399 device so if the manufacturer submits the device-tree to the mainline kernel it can picked up in future RK builds reasonably easily. If they don't .. well nothing will happen.

Get a Synology NAS for local storage and use one of the integrated backup services which has inexpensive and generous storage. Online backup only gets expensive once you want direct real-time access to the data (e.g. for streaming). If online is just an archive store things are a lot cheaper.

No debug log = no problem.

1. /storage represents one of several probable partitions on the internal emmc

2. depends on the kernel, but /dev/mmcblk0 or /dev/mmcblk1 - check with blkid

3. if booting from emmc it's on emmc .. and if using sdcard it's on sdcard

4. it looks exactly the same, because it's exactly the same OS, only installed to different storage media

5. uboot splash isn't easily changed, oemsplash.png in /flash will change the LE splash, kodi splash is separate again

If the whole point of all those questions was changing the splash, all you need to do is boot the box after install and remount /flash rw and copy oemsplash.png to /flash. No need to edit the read-only installtointernal file unless you deliberately want to make everything complicated.