Posts by jaykass

Quote from 5schatten

valireality

I have no S90X based devices, I can't test anything, so I'm not planning to build the distro for this device.

I have built a repo that will build successfully for pi 2/3/3+ as well as s905 devices (LibreELEC 9, Kodi 18). The goal of my repo is to keep everything as close to stock LibreELEC as possible, only including changes needed to get emulationstation, retroarch, and the various cores working properly. I have borrowed from 5schatten, escalade, and niabi projects in addition to make my own modifications.

I won't be providing any completed builds but I did just push my latest commits to my github:

https://github.com/jaykass/libreelec

edit:

I also only have included retroarch cores that I use so the core select is very limited on my build.

5schatten

Did you do anything special when you built moonlight-embedded? What OS are you using to build? I am using Ubuntu 16.04 LTS. I can't seem to get it to build for the life of me. I have tried in my own project (using the package from yours) but I even tried cloning your repo and ran into a different set of issues. Specifically for Pi2/3/3+.

If you didn't do anything special, I'll revisit what I am doing.

It's for older 8.2 versions but check out

Sx095RE v1.8.2 Emulationstation+Lakka+Kodi

And

LE8 "Remix" (Generic/RPi) Emulationstation/Chrome/Spotify PROVIDE LOGS IF PROBLEMS

I have used both of these and have been toying with integrating some of their work with LE9 but so far I haven't been able to get a few packages to compile. Specifically, emulationstation and/pegasus-fe.

I tried to build from your latest commit (fe3e590) but got 404 errors when trying to get the latest linux kernel from GitHub - kszaq/linux-amlogic-le: the Linux kernel for Amlogic SoC devices

It looks like the latest commit there is still 99798df from 2016.

Reverting the kernel version in projects/S905/options allowed the build to complete.

Quote from kszaq

EngineerOfLife Currently LE 8.2 fails to build on Ubuntu 17.10, there's a WIP PR to fix it: fix 8.2 branch to compile at Ubuntu 17.10 by CvH · Pull Request #2186 · LibreELEC/LibreELEC.tv · GitHub

I knew upgrading last night was going to be a bad idea. Why did I do that?

Thanks for the info.

Looks like my nexbox a95 is no longer finding a bluetooth adapter. I haven't tried to use bluetooth for quite a while but suspect it broke when I updated to 1.7 PR1.

Has anyone else had any bluetooth issues?

Quote from Doroteo

Thanks, is a china gamepad,here the image link

I believe I have this same game pad. On the back, is there a switch to change between keyboard and gamepad mode?

Quote from Doroteo

Hello,

I have a bluetooth gamepad, in kodi all work well similar to mouse, but in emulationstation is recognized like keyboard, so the pads dont function, only buttons.

Any workaround?

Thanks

Which gamepad?

Quote from escalade

Do official .img.gz's work?

I haven't tried an official image yet. When I get some more time I will try an official image and also walking through the init script steps manually.

Thanks for posting the tar file for now.

Quote from jaykass

I haven't fully tested yet but the install was smooth and booted without any issues I could see.

I've found my first issue that I believe is rooted in this build. I am getting an error in an addon that uses libssl. It appears that going from LibreELEC 8.0 to 8.2 there was a change from LibreSSL to OpenSSL.

The addon appears to take this into account but thinks that it is running on LibreELEC 8.0 instead of 8.2. I compared the contents of http://LibreELEC.tv/config/version from your repo and kszaq's repo. His is updated to reflect 8.2, your file still reflects 8.0/8.1. I think this is causing the mix-up with the addon.

kszaq version:

# VERSION: set full version, use "devel" for development version
  LIBREELEC_VERSION="devel"

# OS_VERSION: OS Version
  OS_VERSION="8.2"

# ADDON_VERSION: Addon version
  ADDON_VERSION="8.2"

niabi version:

# VERSION: set full version, use "devel" for development version
  LIBREELEC_VERSION="devel"

# OS_VERSION: OS Version
  OS_VERSION="8.0"

# ADDON_VERSION: Addon version
  ADDON_VERSION="8.1"

EDIT: After posting this, I played around with the version requirements of the addon (I changed the required version from 8.2 to 8.0), and then installed it manually from a zip file. It now functions OK but the root cause is definitely tied to your build not reflecting the updated version.

Quote from escalade

Don't know what's going on with that, no RPi here to test. You could update manually by writing the image to a USB, then copy over SYSTEM/KERNEL to your /flash.

I managed to get the 20170915 update to go through (on Pi 3) by using an earlier tar update file but inserting the updated files from the .img.gz file.

So...definitely something with the img.gz file or how it gets processed during update. This certainly seems like an upstream bug but I cannot find any forum postings about it anywhere. I even tried reviewing the busybox init script (which handles the updating) but could not find anything that I understood to be the root cause.

How annoying would it be for you to continue posting .tar files for the pi 2/3?

I installed 1.7 over 1.6.5 (nexbox a95x internal).

I haven't fully tested yet but the install was smooth and booted without any issues I could see.

I noticed the dark UI until a video is played bug was solved.

Trying to update from 20170823 to 20170826 on Rpi3.

I don't recall ever having an issue upgrading before but now when I copy LibreELEC-RPi2.arm-8.2-devel-20170826.img.gz to the .update folder I get the following:

UPGRADE IN PROGRESS

Please do not reboot or turn off your LibreELEC device!

Found new compressed image file
Decompressing image file... OK
Mounting system partition...
mount: mounting  /dev/loop0 on /storage/.update/.tmp/mnt failed: Invalid argument
Missing kernel.img or SYSTEM!
Cleaning up... done
Normal start up in 10s... NOW

I have downloaded the .img.gz file multiple times and tried to updated at least 4-5 times now.

I've done some searching but thus far haven't found anything relevant in this thread or on other libreelec forums.

Quote from niabi

unfortunately I don't own any bluetooth controller to test but I will see what I can find.

edit: check this comment. Orange Pi - Bluetooth pairings lost after reboot · Issue #83 · libretro/Lakka-LibreELEC · GitHub

...feeling like an idiot.. solution was to use "pair" option instead of "trust and connect" when paired for the first time.

minor issue:

I can get bluetooth controllers to connect but after powering them off and back on again, they will not auto reconnect (8bitdo SNES30 v4.0 firmware, Wii U Pro Controller, Gamestop brand analog controller). I have used other builds of LibreELEC (for my Pi 3 specifically the build by escalade) where these same controllers auto reconnected without issue. Is anyone else experiencing this? I tried looking into it a bit last night but couldn't find any definite reason yet. Thought I'd reach out just in case someone already has solved this. I'll keep looking.

Quote from niabi

Well I am an idiot, it seems I forgot to re-add the service that creates the start.kodi file. I pushed a fix for that and fixed the release.

Sorry about that and thanks for helping me find these errors!

As for the audio this also happens to me on Kszaq's build, I assumed it was my box. not something that bothers me though as once you change it sticks.

Alright...looks like I am going to stick with the 1.6 upgrade now.

It now boots fully into Kodi without manual workaround.

One time audio work around is no big deal.

The dark GUI issue goes away after playing a video (same as kszaq's build).

I was skeptical about the comic theme for ES, but I must say that I ended up really liking it a lot.

Great job!

Quote from niabi

Fixed the release, please let me know if it works for you guys.

Having the same issue with your build that I did when I compiled myself.

When booting, it sticks at the Sx05RE logo. I did some troubleshooting and think I have narrowed down my issue to commit 67fcda1 (Readd condition to kodi.service).

I am commenting out lines in autostart.sh (per your instructions) so that Kodi starts on boot instead of emulationstation. This method worked in v1.5 but no longer works in v1.6 without executing the following:

touch /var/lock/start.kodi 
systemctl start kodi

As a temp workaround I created a copy of kodi.service in /storage/.config/system.d/kodi.service (in effect overriding /usr/lib/system.d/system/kodi.service) with the following line commented out:

ConditionPathExists=/var/lock/start.kodi

With that line commented out, Kodi now starts at boot as it did in v1.5.

2 more things I noticed after resolving the above issue:

1) The default audio device is set to "ALSA: Default (AML-M8AUDIO Analog), PCM" which only produces static when playing. I can change to HDMI and then audio is back to normal. So this is only a minor inconvenience at most though this same setting in v1.5 did not produce static audio.

2) The skin/interface is noticeably darker than before but video playback appears normal.

I am using a Nexbox A95X installed to internal memory.

Quote from Samui

jaykass

I tried to modify the SYSTEM image with xz parameters. It is now around 100mb less. So it would match the partition size. Unfortunately it is also not booting.

Could you forward your image maybe?

Wish I could but after updating, it wouldn't fully boot. I was able to revert successfully back to v1.5 though.

Strange as the only thing I changed was the dependency on one es theme. Maybe I accidentally did something else.

Edit: changed the es theme dependency and the partition size back to 512 (from 612).