Posts by chewitt

LMGTFY

That's how the Kodi team programmed the Home screen in Confluence. You can change the mapping of the button in the screen to something other than INFO to change the action, but if the mapping remains on INFO the skin will always do the same thing.

That error normally means Xorg fails to start because there is no GPU driver that supports the chip in the box. We don't have any SkullCanyon devices to test locally but there have been public reviews of LE running on that hardware so we assume it works. Have you tried the v7.90.002 build?

/dev/sda2 is a partition on the drive so /dev/sda would be the node for the drive, but you don't show us the failure response of the command so that's just a guess at the problem.

LibreELEC targets HTPC kit which typically uses a remote control not a trackpad, so we are probably (and deliberately) missing the drivers for it. If you tell us the Linux kernel driver module required to make it work we'll consider adding it in a future update. Otherwise LE is working as intended.

Please don't post the same thread twice, ask for it to be moved if necessary, and be patient for replies.

If you are building from master branch we didn't pull any of the recent Kodi Amlogic changes into our branch yet, and I wouldn't expect things to work right without them. Not sure when those changes will get added. We may wait until the official Kodi Alpha 2 appears on/around 1st July before getting everything ready for our LE v7.90.003 release.

It's a long-standing bug in Kodi affecting multiple Linux distro's. If you reboot with the disk inserted the Play menu should be visible.

On the subject of names, it's probably not a good idea to use your email address as your username. PM one of the staff if you'd like it changed.

The meaning of Libré in LibreELEC is personal to the founding team and represents "free of his crap" or "we are free again" and has nothing to do with other interpretations. You are welcome to continue debating the issue (with yourself) but there are no plans to change the name. It's just a name.

I was present when the name was chosen (as the least-worst of several options). I think you are over-thinking things

There was an issue with mtools creating directories in the boot partiion. If you downloaded v7.0.1 in the last ~7 days you shouldn't see the problem as we swapped the download files for fixed ones. If you downloaded v7.0.1 earlier, a clean install with freshly downloaded files or updating to v7.0.2 (this weekend if testing is good) should fix the FSCK.* files mess automatically and correct the issue for you.

If you can find a version of the MT7610U driver that doesn't require a hard-coded config file (which only works for 50% of users) it will be considered for LE 8.0 builds. The driver package I previously created for OE is half-baked and not suitable in its current form.

Our fairly small project will resolve this known (as we first flagged it) issue in LE v7.0.2 which will ship fairly soon; within the next week. In the future you can reach our fairly small developer team of ~50 people via any of the ~10 admin or mod staff here in our forums, or by asking the fairly helpful people in the Kodi or OSMC teams where senior LE team members are all fairly well known. Thanks for the report.

don't expect official dual-audio builds unless Kodi adopt the feature/capability upstream

"It works in Android" does not necessarly mean it works in Linux. It's not currently possible, and due of the amount of development needed it's not very high on anyone's to-do list.

No debug log. No problem

One of the forum staff noticed the same thing the other day so it's on our to-do list. I'll confess it's probably not very high up the list, but we'll get to it at some point during the alpha/beta cycle. Thanks for reporting