Posts by EasySly

kszaq please ignore patch which I have proposed earlier, it's not fully finished (

Take this one please [package][mediacenter-osmc] Support for different hardware keyboard l… by graham8 · Pull Request #395 · osmc/osmc · GitHub

Already tested and finally Kodi understood non-latin keyboard )

kszaq could you please add to next release this PR Fix international keyboard input for Linux input layer by fonic · Pull Request #12762 · xbmc/xbmc · GitHub

kszaq my debug info about remote problem

long press of any button doesn't work
home doesn't work

My sequence of pressing buttons:
1. ok
2. back
3. ok
4. home
5. menu
6. long menu

FFgB
SACU

The same home button doesn't work. Also menu button and long press doesn't work ((((

Quote from theodor

LibreELEC-S905.arm-8.0-devel-20161223194610-r25062-g308adcf
Latest version wont boot anymore MX Plus TV Box Android 5.1.1

I've finally upgrate to it also... Have some issue with dtb.img but after all everyrhing is ok.
Try a few times again, for my MXQ Pro 4k boot after 5 tries (((
[hr]

Quote from wkchick

I also experienced boot issues. I don't want to repeat what was said, Uberduke already did very comprehensive testing on his/her Minix NEO U1 a few posts back. While his/her Minix NEO boot issues seem settled down, mini doesn't.

I thought boot issue only hit 64 bit build, I was wrong. I thought it was the script files and replaced them with older script files, boot issues remained. I thought only arm builds are affected, wrong again. I tested afl1's latest build (aarch) on Mini M8S II, boot issues remain (Yeah, I tested afl1's build for K II despite I don't own that box, his build could not read the CPU temperature, so I believe it is not the cause of boot issue). When boot issue happened, it stays at the boot logo and LibreELEC logo never shown. It look likes the box was waiting for some response from the TV via HDMI to proceed.

For the Mini M8S II (S905X, 2G/8G), the only way I could make it boot is to turn the TV off (Mini M8S II will then turned off by itself because I set it in CEC), Then I turn on the Mini M8S II with the remote (while the TV remains off), then it will boot properly and turn the TV back on (as I also set it in CEC). That is, every time TV was on when the Mini M8S II boots, the latter hang.

I have a TV that doesn't support HDMI-CEC at all. I tested latest build LibreELEC-S905.arm-8.0-devel-20161223194610-r25062-g308adcf.img.gz on Beelink M18 (S905, 2G/16G) with mSD card with this TV, no matter how many time I tried, reboot or boot on power up, it boots right away. The same box, same mSD card, nothing touched, when moved to family room and tested, it just hang at the boot screen (AVR and TV both support HDMI-CEC which I have no idea to turn CEC support off)!

Hope the above information could narrow down the search for solution of the boot issues, whether it was 7.90 or 7.0.3, arm or aarch, 32 or 64 bit.

How you turned off CEC? I want to try it with my box

Quote from lrusak

Did you try using the gui?

Yep, but unsuccessful... "Bluetooth input\output error" error message is appeared..
Should it be worked in UI?

Hi guys,

I've took the rapoo e6300 and with default method I cannot connect this keyboard to the system because this keyboard need to enter passkey on it in "blind" mode to be paired with system.

I've found a lot of information about such problem with OpenElec but for LibreElec nothing. Bluez-tools which exists in the OpenElec doesn't exists in LebreElec.. Sad...

And I decided to try bluetoothctl tool on the system. And I've successes conected keyboard and I've got the pin for paring...

0. Connect to ssh
1. Run bluetoothctl. Interactive shell will run
2. Execute scan on
3. Turn on the keyboard and press for 5 second Connect button on the keyboard
4. On the shell you should find something like this:

[NEW] Device 6C:5D:63:40:04:D3 Bluetooth Keyboard

5. Execute command trust

[bluetooth]# trust 6C:5D:63:40:04:D3
[CHG] Device 6C:5D:63:40:04:D3 Trusted: yes
Changing 6C:5D:63:40:04:D3 trust succeeded

6. Execute command pair

[bluetooth]# pair 6C:5D:63:40:04:D3
Attempting to pair with 6C:5D:63:40:04:D3

During this on the monitor should be appeared message which describe pin which should entered on the keyboard.
7. Enter this pin and press Enter on the keyboard
You should see on the shell something like that

[CHG] Device 6C:5D:63:40:04:D3 Connected: yes
[CHG] Device 6C:5D:63:40:04:D3 Modalias: usb:v099Ap0500d011B
[CHG] Device 6C:5D:63:40:04:D3 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device 6C:5D:63:40:04:D3 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 6C:5D:63:40:04:D3 ServicesResolved: yes
[CHG] Device 6C:5D:63:40:04:D3 Paired: yes
Pairing successful

8. Execute command exit and disconnect from ssh
9. Go to bluetooth settings in the Kodi
10. Click on the your keyboard item (in my case it was disconnected) and select connect.
11. Wait 10-20 sec and try to use keyboard.

In my case keyboard was paired and working as expected

I hope such instructions will helps somebody else except me

Happy Holidays and Enjoy!

Quote from kszaq

Okay, I can now see what's going on. That's a failure with updating device tree and you shouldn't worry if you updated from a previous Krypton build. If you run from SD card, try replacing dtb.img with a device tree for your device.

On the other hand you may be experiencing a booting issue that we recently discovered and I'm still trying to hunt it down... I will be working on it further after Christmas.

Thanks you, I will try it again later...

Happy Holidays, all.

Quote from kszaq

EasySly Unfortunately I can't see any of the pictures you attached.

You can see on it on my share album 4rnaz2MGxYKSXR6q8

Upgrade failed, some of files cannot be found... It very quick was rebooted I don't remember what was exactly appeared...

After clean install cannot be booted, install was successfully done, after reboot nothing...

Let me know what information and from where I should give to you...
[hr]
Performed upgrade again but with camera at this time )

Clean install do nothing stuck during launch

MXQ Pro 4k

It seem issue with bootloader or with process which update them... Any thoughts?

Hi kszaq,

I've noticed that you are using your own libreelec repository, could you please add to it script.moonlight? There is no such package in repository, but in aarch64 build/repo it was.

Thanks, now I'm feeling much better )

kszaq  JoKeRzBoX Great news, thanks a lot!

I have kszaq's build from 11-09 and also I was added mod to have 32bit userspace, thus I have logical question how it was going to be updated?

I have a lot settings and configurations which I was made ((( I don't want to loose them...

I'm noticed that during playing the movie appeared such error in the logs with 11-09 build:

ERROR: Unable to load libamplayer.so, reason: libamplayer.so: cannot open shared object file: No such file or directory

But video with HW decoding is successfully loaded and played...

Is it normal?

Quote from JoKeRzBoX

Good catch
Link was wrong but should be correct now in the first post. Thanks!

Thanks, works like a charm )

Is mod update for 11-09 correct? LibreELEC-Odroid_C2.aarch64-7.90.008_lib32Added

It seems copy past (

Is it possible to include to image lib32 libraries to be able to run arm 32bit executable?

UPD: Confirmed problem with libreelec repository problem. HTTP 403