Posts by chewitt

  • Retrospect addon

    LE already moved master branch (future LE 9.0) back to OpenSSL but there are no plans to move 8.0.x releases as it requires a load of additional rework to add-ons and there isn't the appetite for that. Current milhouse builds (with Kodi Leia code) are available. If/maybe we opt to create an LE 8.2 release to bring a kernel bump and other new hardware changes before Leia (as it's a long way off) we will do it then, but there's no guarantee we'll do that.

  • openpht port?

    If you combine the S905 build project from @kszaq's github repo and the WeTek Hub or Play2 projects in the OpenPHT-embedded repo you probably get a working image. Some of the OpenPHT folks actively contribute and collaborate with LE and their version of the OS is deliberately not too different.

  • RB pi3 WIFI

    Code
    connmanctl
agent on
scan wifi
services

    leave 10 seconds between scan and services; this will list the networks in-range assuming the drivers are loaded and the wireless device is working

  • Few problems with LE 8 on Asus Chromebox

    "SMB" encompasses multiple not-quite-compatible versions of a shitty designed networking protocol that is implemented via a third-part integration library (smbclient) that is wrapped in Kodi code that hasn't seen much love in aeons. Somewhere in that list resides a mess of problems. The current resurgence in reported issues (which may or may not be your issue) is largely due to Microsoft changing things in their SMB server stack. I forget what changed and thus what might be required to coerce things to work again; but it probably involves registry hacking to downgrade features on the Windows end. Best solution is to get a NAS because this will run "Samba" with an older SMB protocol version which is more widely supported (and powered on permanently which solves other silliness) or use NFS on the server side to sidestep SMB completely. Sorry if that sounds a bit shitty-worded, but Windows networking has been a complete turd since Windows '95 and I'm struggling to work up the enthusiasm for it today..

  • Wrong RPI Model after upgrade from RPi 2 to RPi 3

    RPi3 and RPi2 are essentially the same device but RPi3 uses a newer generation of the core SoC that runs at higher clock speeds. As the hardware is so similar we can use a common kernel/OS image that supports both devices. One quirk of the Pi firmware in this configuration is that 64-bit RPi3 hardware reports itself as a 32-bit RPi2. It is possible to make RPi3 run a 64-bit image and report CPU etc. correctly but this requires you to run a different kernel configuration, and then Kodi doesn't run as nobody 64-bit ported the mountain of very highly optimised 32-bit video code that Kodi depends upon. TL;DR - it's a cosmetic issue and there's nothing to see, move along please :)

  • Migration attempt ends in hard reset and factory default config

    Kodi sometimes fails to retrieve addons.xml from Kodi server(s) which leads to 'get more' etc. not showing anything. If you context click on the repo and "check for updates" manually that forces it to be retrieved and Kodi now has a valid list of whats available.

    The hard reset process is triggered by /storage/.cache/reset_oe being present in the filesystem. There is no logging on that process so you're not missing anything useful from the logs being nuked as part of the reset.

    The only scenario that I can come up with for this happening is that you've hit "hard reset" and then said "no" when it prompts to reboot (assuming it does prompt, it probably does) and then you've taken a backup of the system. This would lead to reset_oe being present in the backup.