Posts by GDPR-2

  • [8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

    Most S912 boxes is q200, if it doesn't boot then use q201

  • [8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

    Quote from kostaman

    Name your Box/Remote to compare to others.

    My TX3 Mini lags in receiving command presses. There is a delay.

    Official Kodi Remote via my phone works perfect.

    CEC is perfect with my Sharp TV Remote.

    You can try playing with remote delay and period with ir-keytable, no need to stop kodi or eventlircd, just enter command in SSH and test

    ir-keytable -D 500 -P 100

    You can then add to autostart.sh to make it permanent

  • [8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

    This command will be executed automatically on future releases when using p281 dtb projects/Amlogic: disable deinterlacing on S905W · LibreELEC-AML/LibreELEC.tv@4ed503f · GitHub it has been noted that deinterlacing is an issue on S905W for some months now, this may have been fixed with the newer nougat kernel but we are still using the older one for now because it works the best.

    Quote from RayW

    Thanks Adam for your usual helpful response. Yes I fully understand and of course as always support and respect your good work here.

    I was just making a point here as these days there seems so may so called updates in so many walks of life that I find end up being downgrades and was worried this might end up the same way. Sure I fully understand these are early test releases only and you are right to comply with the new default system for remote mapping. I will try to adapt my really nice Beelink MXIII II remote.conf file I use in LE8 to this new mapping system when I get my head around it. The key allocations I currently have mapped and use with LE8 I find very user friendly with all keys on the Beelink remote being mapped for useful purposes. If I succeed when and if I get time to try, I will indeed post it wherever is appropriate here for the LE9 remote mapping files. I will also do the same for my TX7 box too. Just finding the time as retirement can be so busy hmm :)

    It's really not a hard thing to do if you follow the instructions to the letter, it is very easy, even easier than making a config the old way. You view it as a downgrade because what you are used to no longer works but this is not the case, you can now use ANY remote and any config you create can be used on any device be it an amlogic box or a rockchip based box or even an x86 box. Your TX7 remote should work out of the box because I already added the config for this remote into the build.

    Like it or lump it but this is what official LE9 releases will be using so you will have to get used to it whether you like it or not if you want to use the latest versions of LE, sorry to be blunt.

  • [8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

    Quote from zbigzbig20

    GDPR-2 , as other user said something wrong is with tvheadend . Tvh 4.2 or Tvh4.3 does not want to connect and also tvh webif does not work . I did clean installation on new msd card on my wetek play 2.

    Regards

    I will look into this later, most likely it's just an add-on issue as there has been a number of tvh changes upstream recently.

    Quote from rajawaqas

    I m eagerly waited Kszaq based 9.0 plus version because I am not programmer just simple user I can’t understand keymap based method to work my nexbox remote that’s why I also can’t use and test adamG’s 8.94 ( because of no remote). My last tested build was 8.93 which is best. I m going back to 8.2.

    If kszaq decides to do another community based release then it will be the same, this is a LE9 change. If people create remote configurations and share them then they can be added to future builds for the benefit of all, the instructions are not rocketscience and I have tried to make them as easy to understand as possible.

    I want to align this community release as close to LE/master so people are getting a pure LE experience and with each release the differences are getting less and less.

  • [8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

    Quote from RayW

    Thanks for the heads up Adam. I find more and more upgrades these days actually make things worse and harder to configure so I have to call them unnecessary downgrades. ALL upgrades should be improvements and make life easier, not harder. Sounds like I will stick with Krypton unless I see any real reason to change to Leia, and no NetFl;ix is not enough reason. Just my two pence worth.

    So can someone list the actual real user benefits of Leia over Krypton ?? Netflix we can take as read, once that is we can use HW acceleration. Sure I know early days yet, but so far I see nothing to get folk excited about and no promise of any real user beneficial improvements. I would rather we kept what we have with Krypton and just build on it to make it better and better, like adding Netflix capability with HW acceleration to it. Why do they need to keep changing KODI so often ? The old adage comes to mind in that if it aint broke don't fix it, and that certainly stands true today as it always did.

    I hope I can be proven wrong, time will tell.

    That's your prerogative if you wish to stay with LE8.2, these builds are purely for testing and have never been marketed as final and so should be treated as such.

    The IR changes are global across all Amlogic based devices for LE9.0 and they are an improvement because people should be able to use their Pioneer AV remote or any other remote if they want to, I knew this change would be troublesome for some users but I want to keep these builds as close to the official LE source as possible and not deviate from it.

    LE8.2 development has stopped, all developers are now solely committing to LE9.0.

    Quote from bhwsyd

    I use a Minix A2 airmouse on my Beelink Mini MXIII-II.

    Will this remote work out of the box with the .4 upgrade with no keytable required?

    Yes

  • [8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

    The only thing I can think of is a formatting error in your file, but it looks fine to me, you can also scan other protocols with

    ir-keytable -c -p lirc,rc-5,jvc,sony,nec,sanyo,mce_kbd,rc-6 -t

    -c clears all saved or loaded keymaps

  • [8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

    8.90.4 is now live

    Please note there is a big change in this release in how infrared is handled, releases will no longer use amremote remote.conf and will use ir-keytable.

    A short guide on how to create remote configs is shown below

    External Content pastebin.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
    there is also the LE wiki page Infrared Remotes [LibreELEC.wiki]

    Remote configurations for WeTek/Mecool/Minix/Tanix (mini remote) have already been baked into the image. I can include remote configs for other devices in future builds.

  • [8.2.3.1] LibreELEC 8.2 for S905/S905X

    Quote from cwgsm3v0

    Did anyone get this working? The 8.2.3.1 in my living room keeps getting the 00:15:18:01:81:31 MAC and none of the fixes I found perusing threads (udev, system.d, etc) work. However, I am running an older Nofan Tasi aarch64 build in my bedroom and it generates a random MAC each boot. Both boxes are identical h/w && manufacturer otherwise (and it's not a Realtek LAN adapter) - I knew about this ages ago but for some reason, it bit me in the rear today. I also booted the GDPR-2 Leia builds in Amlogic off USB and noticed it's generating the 00:15:18:01:81:31 MAC -- Anyone have a surefire method that works? I can generate a random one using dbus-uuidgen and even try to write to via fw_setenv but no luck.

    I tried everything mentioned in this thread:

    How to change duplicate MAC Address

    But the stock kszaq build and GDPR-2 build still default to that MAC. Only the aarch64 build (it's an older 8.2 from Nov 04 2017) generates a new MAC each reboot.

    Really looking for a hail mary here... I may end up building my own aarch64 build again to test with.

    Mac address is generated from your CPU serial number if one is not burned to the board.