[7.0.3.3d] LibreELEC 7.0 for S805

Hello.

I've been using OE on a Beelink MXQ for more than a year without any issues. Now, I want to switch to LE.

The problem: I tried a SD installation and I found that LE does not recognize my MCE remote. It has its own IR receiver and it works "out f the box" with OE.
Is there anything I can do? I really don't want to use LE with the MXQ's basic remote (I mean, who in their right mind makes a media player remote without play\pause\stop buttons? )

Thanks for your help and the great work you're doing.

Quote from minimoe

I found that LE does not recognize my MCE remote. It has its own IR receiver and it works "out f the box" with OE.

I believe you must have a USB port not working that the ir receiver is plugged into.
Swap it around and see what happens. I'm not sure what MCE remote is but the remotes with receivers usually
learn when plugged into a WORKING usb port.
Sorry that is all i can help with at this stage.

Quote from kostaman

Hi Fellow s805 Flashers.

I am just posting an issue that may or may not be known as i haven't had to do a fresh install NAND on my
MXQ.arm 7.0.2.5 from Nand on All Alack MXQ, board number: 'AM_MXQ_A 20150825 for a long while.

I Downloaded zip file from NAND release folder.
Unpacked downloaded file to a FAT32-formatted SD card - there were 3 files as a result:
aml_autoscript, factory_update_param.aml and a zip file with an update.
Tried to Install ROM using "toothpick" method. FAILED to boot into LE. It booted to Android.
Tried 4 times with same result. I tried the Update App in Android but same thing.
I then took out the SD Card and tried to boot into recovery but no go. Just booted into Android.

I then added the factory recovery image to the LE sd card files to make it 4 files and Toothpicked.

The Android Robot appeared and started installing. The box rebooted with a fresh NAND LE .

Just putting it out there as this never was the case with this box previously way back.

Display More

Coincidentally! I was doing this Saturday evening and had the same issues. I went a different route and installed 7.0.2.1 and then applied the 7.0.2.5 update to get it working.

Also worth noting here that I kept a backup of my custom remote-control settings and simply copied the files into the relevant folder via Samba once I had the install sorted. Worked fine.

Why did I do a clean install? Just wanted to make sure I didn't have loads of crap slowing my box up! I now only have 2, legal, addons and doubt I'll be adding anymore.

Quote from PatrickJB

Why did I do a clean install?

Good to hear from you again PatrickJB
I did the clean Android Install and Clean LE because of the Blue Light "ON" all the time.

I now have Suspend with remote. Blue Light Comes On.
Turn back on from Suspend . Red Light Comes On.
Suits me.

I couldn't remember what the hell I had on this box as far as Boot Loader and U-Boot .

Flashed so many roms on this box.

Anyway , Good to get this out as i'm sure it is going to come up again.

Quote from kostaman

Good to hear from you again PatrickJB
I did the clean Android Install and Clean LE because of the Blue Light "ON" all the time.

I now have Suspend with remote. Blue Light Comes On.
Turn back on from Suspend . Red Light Comes On.
Suits me.

I couldn't remember what the hell I had on this box as far as Boot Loader and U-Boot .

Flashed so many roms on this box.

Anyway , Good to get this out as i'm sure it is going to come up again.

My LED has always acted that way, but I have a sticky over the LED so I can hardly see it, just too bright in a dark room.

I shudder thinking about the old days of the S805 builds!! I figure that's why I'm sitting back on the S905 builds, well and I'm a bit thick, err and I don't have a box!!

Once I get my finances sorted, probably next year, I'll grab an S905 and join the party.

We all remember the old days and trust in what Master Jedy Kszaq said, Mxq S85 and Mk808b + will come back! Yeahhh!

Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

Quote from kszaq

If you want my opinion... if you don't use 4K, there is no reason to buy S905. Actually I consider S805 builds to be more stable and mature than S905 - also due to more mature yet older kernel - and this is why I don't replace my parents' and home S805 box with S905. There will be at least one small LE 7.0 update for S805 and when I start working on Krypton, S805 and S905 will be developed in parallel.

Good to know.

Not sure if I like the new Krypton skin/GUI but if there are playback improvements then I'll certainly update. Does anybody know if the Confluence skin will still be available for Krypton? I like it's simplicity.
[hr]

Quote from vn800art

We all remember the old days and trust in what Master Jedy Kszaq said, Mxq S85 and Mk808b + will come back! Yeahhh!

Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

They're both great as home servers. I often think about buying a third one (MXQ) and sitting it on a shelf somewhere with a couple of drives plugged in and forgetting about it!

Don't know if in LE this could be relevant ( I do not think so ), but for SD installation when one want to use a Kodi installed on Android, have a look here:
Kodi V17 Beta 3 - Interesting changelog entry for AMLogic Lollipop users - FreakTab.com

Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

Quote from kszaq

There were some playback issues after video refactoring in Krypton but thanks to Codesnake's efforts it's improving. At this point I can't say whether it's better or worse than Jarvis as haven't used Krypton much. And yes, Confluence is available as an add-on for Krypton.

For a home server maybe you should consider buying an Odroid? They are only a bit more expensive than Chinese boxes yet much more flexible OS-wise and with great manufacturer and community support.

So at this stage it looks likely that Krypton will run fine on the 805 chipsets? Kodi 17 won't be the kryptonite for these boxes? [emoji23]

Sent from my EVA-L09 using Tapatalk

Thanks for the responses guys.

Quote from kszaq

minimoe Which version of OE were you using before? Can you post a log from both OE (if you still have a backup) and LE? In my LE builds I switched media drivers are built from media_build sources and maybe there's something missing.

OE is version 6.95.3.1 7.0 and LE is the latest from the LE release thread. I'll post the logs tomorrow.

Quote from kostaman

I believe you must have a USB port not working that the ir receiver is plugged into.
Swap it around and see what happens. I'm not sure what MCE remote is but the remotes with receivers usually
learn when plugged into a WORKING usb port.
Sorry that is all i can help with at this stage.

My remote is Microsoft's MCE Remote (the one with the teletext buttons). I tried to plug the eHome receiver into both the USB and the microUSB ports but no luck.
It works with Openelec when I plug it into the microUSB port using an OTG cable and it worked with OE on my old HTPC.

Quote from kszaq

minimoe Which version of OE were you using before? Can you post a log from both OE (if you still have a backup) and LE? In my LE builds I switched media drivers are built from media_build sources and maybe there's something missing.

Here are the logs. I hope you can find a way to use my Microsoft remote with LE

First, I made a new LE SD installation. The remote does not work Log

Then I installed OE. The remote works reliably when connected to the OTG port but it does not work all the time when connected to any other port. Log

Finally, I upgraded the OE installation to LE using LibreELEC-S805.MXQ.arm-7.0.2.5.tar. The update went fine but I lost the remote again. Log

OE and LE see the eHome receiver as "Bus 002 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver".

Everything else (CEC, power LED, original remote) work fine with both elec's.

Quote from kszaq

minimoe Please collect the logs according to the sticky thread: LibreELEC Kodi logs alone tell me nothing about your hardware.

OK, I'll do that as soon as possible.

Hello,

I also have an MCE remote, and tried it with the wetek hub running your latest devel version. Works fine out of the box, all keys mapped properly.

lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0471:0613 Philips (or NXP) Infrared Transceiver
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

(note the different device ID compared to the other user)

dmesg after pulling and re-inserting dongle

[ 2373.286408@3] Disconnect cb-Host
[ 2373.387812@1] usb 2-1: USB disconnect, device number 2
[ 2375.547469@2] dwc_otg: Indeed it is in host mode hprt0 = 00041901
[ 2375.727453@2] usb 2-1: new low-speed USB device number 3 using dwc_otg
[ 2375.728299@2] dwc_otg: Indeed it is in host mode hprt0 = 00041901
[ 2375.933659@2] usb 2-1: New USB device found, idVendor=0471, idProduct=0613
[ 2375.933672@2] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2375.933680@2] usb 2-1: Product: MCE USB IR Receiver- Spinel plus
[ 2375.933687@2] usb 2-1: Manufacturer: PHILIPS
[ 2375.950134@0] input: PHILIPS MCE USB IR Receiver- Spinel plus as /devices/dwc2_a/usb2/2-1/2-1:1.0/0003:0471:0613.0002/input/input6
[ 2375.951091@3] hid-generic 0003:0471:0613.0002: input,hiddev0,hidraw0: USB HID v1.00 Keyboard [PHILIPS MCE USB IR Receiver- Spinel plus] on usb-dwc2_a-1/input0

lsmod with dongle inserted:

Module Size Used by
hci_uart 21997 1
dhd 714223 0
btsdio 3178 0
bluetooth 243164 4 btsdio,hci_uart
8021q 18309 0
cfg80211 359903 1 dhd
6lowpan_iphc 5895 1 bluetooth
mceusb 10459 0
rc_core 18225 1 mceusb
wifi_dummy 806 0
mali 195991 5
aml_nftl_dev 82924 0
fbcon 37385 0
bitblit 4508 1 fbcon
softcursor 1200 1 bitblit
font 7295 1 fbcon

[hr]
Hallo,

even my old X10 remote works out of the box...

[ 3090.481978@3] Disconnect cb-Host
[ 3090.637795@3] usb 2-1: USB disconnect, device number 3
[ 3099.801691@3] dwc_otg: Indeed it is in host mode hprt0 = 00041901
[ 3099.981644@2] usb 2-1: new low-speed USB device number 4 using dwc_otg
[ 3099.982324@2] dwc_otg: Indeed it is in host mode hprt0 = 00041901
[ 3100.186921@2] usb 2-1: New USB device found, idVendor=0bc7, idProduct=0006
[ 3100.186934@2] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3100.186942@2] usb 2-1: Product: USB Receiver
[ 3100.186949@2] usb 2-1: Manufacturer: X10 Wireless Technology Inc
[ 3100.251759@3] Registered IR keymap rc-medion-x10
[ 3100.252171@3] input: X10 Wireless Technology Inc USB Receiver as /devices/dwc2_a/usb2/2-1/2-1:1.0/rc/rc0/input8
[ 3100.252412@3] rc rc0: X10 Wireless Technology Inc USB Receiver as /devices/dwc2_a/usb2/2-1/2-1:1.0/rc/rc0
[ 3100.252556@3] usbcore: registered new interface driver ati_remote