Posts by chewitt

Install a current alpha build and test again.

There is a significant difference between rooting a TV to add another application or fiddle with configuration, and rooting it to run a replacement OS on the internal TV hardware. Unless someone would like to donate a bunch of 65"+ 4k OLED TV's to the team for testing and experimentation (we're open to offers!) it's not likely to happen.

The ability to disable lirc from LE settings will probably appear in the next alpha build.

I've no objection to a sample systemd .service file being included as we do for some other things (and some wiki documentation) but VLAN's are a niche requirement so there's no need to complicate the GUI for the other 99.99% of users.

It's originally intended to show an X.X.X format number so once we pad it with "blah blah (community) X.X.XXX blah" it overflows. It's not an issue once we arrive at 8.0.0 (official) so it's known but not very high on the priority list

Find something that uses the Atheros ath9k driver, it's probably the best written one.

That's the one that only works for 50% of users due to the hard-coded config file. Mediatek need to get their sh1t together and write a driver against the proper (modern) kernel interfaces. Drivers like that one went out of coding fashion c.2004.

It's not really needed with LE as most (all but one) of our images boot directly into Kodi where the first-run wizard guides you through connecting to a network. All you'd do is replace one typing opportunity (password) with something earlier in the boot process where you'd need to input two things (password and SSID) and from experience it's better to reduce the opportunities for user input; too many fat fingers on keyboards

It's not the panacea you are seeking. Amazon changed the widevine security level on their streams and now require decryption of video in addition to audio, and this effectively kills the capability as it's not possible to software decode the streams on all the low-power ARM devices which make up the majority of our (and Kodi's) userbase.

It's not a dead topic, but right now we're back to the start and have to figure out another approach.

No debug log or factual/technical information to investigate from = Not our problem.

Sorry, our crystal ball is broken. In the absence of any factual detail we will not be investigating anything further.

17:49:08 T:3035529792 NOTICE: ADDONS: Using repository
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository repository.ytplugin
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository plugin.video.ZemTV-shani
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository repository.whitecream
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository script.video.F4mProxy
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository plugin.video.f4mTester
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository
17:49:08 T:3035529792 NOTICE: ADDONS: Using repository

Official:Forum rules/Banned add-ons - Official Kodi Wiki

No further support.

Official:Forum rules/Banned add-ons - Official Kodi Wiki
It's always a sunny day when repo's that are full of pirate sh1tware fail to install.

It's the same keymap as 7.0 but Kodi changed/renamed some stuff and so the keymap needs to be adjusted. If you wait for us to do every tiny detail we'll get there, but fiddling with a keymap is currently low on the to-do list. So this is where our users can help, or not.

This was merged/included in the v7.90.008 build.

The skin you're using is Estuary not Confluence, and it will be a remote key mapping issue, which means you (our users) can make experimental keymap changes and then tell us what needs to be changed.

There are no plans to confuse people with multiple boot methods as RPi3 hardware does not support the feature without updates first, and we prefer to avoid 5000+ "flashed a USB stick and it doesn't work" forum posts. At some future point when RPi4 comes along with USB-boot support from the start we'll entertain the idea.

Running "find / -name remote.conf" will find it in OE, if it exists. Any OE build for thoses boxes is likely to be a custom build with it embedded rather than something user-configured.