Posts by chewitt

Stephan Raue doesn't have a good record or reputation for communication and his refusal to discuss anything is the single largest reason for the split. Persuade him to attend Kodi DevCon in October - then a bunch of us can sit down together in-person over beers and talk. There are some challenges but none of the founding LE team who came from OE wanted to fork; it was an action of last resort after months of exhausting all other options and being ignored.

Read post #2. It will not be an exact copy of the card, but you only need the data on the card, not an image of the card. I never understand why people waste time creating an 8GB or 16GB image of their card when you can have a 1GB (max, it's often a lot less) backup file. Ho hum.

The releases sever does not currently support HTTPS connections. This will change when we complete a server move, which is a little overdue but on the team short term to-do list.

Do not post URL links to that website in this forum please. It exists solely to profit from piracy and its continued existence harms Kodi.

Install the dispmanx add-on. You might need to force-update the repo (context click on it) if no add-ons are listed.

Textedit.app is fine as long as you convert the file to plain text, the default is rich text.

I'm not near a box to check filenames, but just clone the existing nvidia udev rules file to /storage/.config/udev.rules.d/ and add the missing device ID to trigger the match and reboot.

wrxtasy has a community image for the Odroid C1

Use the backup and restore functions in the LE settings add-on to clone the small amount of data on the card instead of cloning the entire card. It will be faster and doesn't hit issues when the sector count on one card is different to the other.

You have an MT7610 device. There is a Linux driver, but it will not be added to this distro until MediaTek (or anyone else) creates a driver that follows kernel driver standards. The current one "works" but does not support a bunch of the cfg80211 framework which will lead to support issues. It also requires users to set the wireless radio configuration via a text file, which doesn't fit with our "it just works" oriented distro.

journalctl --no-pager -b -0 | paste

^ run that after clean boot and the time is wrong, then share the URL so we can see the log.

Are you building the image yourself from our repo, or from one of the community authors' repos?

systemctl stop kodi.service
mv /storage/.kodi /storage/.kodi-old
systemctl start kodi.service

^ You can stop Kodi and move items like Thumbnails, sources.xml and library DB files from the old folder to the new folder and restart. No need to wipe the drive. I forget what all the version numbers are for DB files so start Jarvis once with no config and it will create them, then you know which file versions to copy back.

The device you're using is irrelevant. If you downgrade back to Jarvis some things like libraries will revert to previous state because you resume using the older DB files that are still kicking around in the filesystem, but you now have a hybrid Jarvis/Krypton guisettings.xml file and some of the add-ons installed will have been updated to Krypton-specific versions that either won't work or might not play nice with Jarvis. I'd advocate copying the library DB files and thumbs somewhere safe then starting over with a clean Kodi configuration before moving sources.xml and DB/thumbs back.

Next time make a backup before you start, then reverting cleanly to Jarvis or a previous state is trivial.

The HEVC improvements are mostly achieved between kernel driver and ffmpeg optimisations, so are largely independent of Kodi version.

Not possible. There is activity within the team towards Rockchip support in Kodi Leia (which is months away) but this work is focussed on current generation SoC's like RK3328 that have reasonable (and still improving) mainline Linux kernel and driver support. The new generation devices have become cheap it makes no sense to spend time/effort on older chipsets requiring non-standard Android kernels that contain too much low quality code and bugs.

wget http://sprunge.us/MRPN -O /storage/.config/gpioshutdown
chmod +x /storage/.config/gpioshutdown
wget http://sprunge.us/MgBZ -O /storage/.config/system.d/powerbutton.service
systemctl enable powerbutton.service

^ The first URL has a slightly cleaned-up version of their gpioshutdown script. The second URL has a complete guess at a systemd.service that runs before Kodi startup. I am a novice at systemd things so no guarantees it will work. I also have no clue what other GPIO dependencies are required for the gpioshutdown script to work. You should consider them as a hint at how to do things; they are likely not a complete solution.

S905D are the chips to watch for (devices with them should start to appear soon) as they have the same spec as S905X but with GB Ethernet. There is no HDR support in Linux at the current time but the first patches for HDR support on Intel GPU's were submitted to the Linux kernel last week so that will change in the future. Once things are in-kernel Kodi can start to evolve support. Once Amlogic completes work on a mainline kernel (not the ancient crap we are using today) support can be added there too. Android is a completely different discussion and I'm honestly not aware how good/bad things are there. It's usually a hack-fest of bad though.