Nightly images for A64, H3, H5, H6 and R40 boards

  • Hello

    I'm having trouble with logging in to the YouTube add-on:

    LoginExcepiton: [401] deleted_client ...

    The OAuth client was deleted


    What can I do to fix it?

    • Official Post

    Please test latest OrangePi PC2 (H5) image:

    LibreELEC-H5.arm-9.80-devel-20200308081621-cfb1324-orangepi-pc2.img.gz


    If it is good enough, it will be merged into official LibreELEC git repository and nightly images will become available soon thereafter.


    I'm having trouble with logging in to the YouTube add-on:

    LoginExcepiton: [401] deleted_client ...

    The OAuth client was deleted


    What can I do to fix it?

    Only current solution for YT plugin is to create your own keys. Just follow Personal API Keys · jdf76/plugin.video.youtube Wiki · GitHub I think default keys were revoked by Google. Note: If you did that already some time ago, it's possible that you have to re-create them. My 2017 keys didn't work. Additionally, I had to update to 6.7.0-beta1 due to sign in issues.

  • Hello

    Unfortunately, my OrangePi is PC (H3) and not PC2 (H5)

    Creating a new API key and entering data into the add-on configuration did not change anything

    When logging in to YouTube, the same information still appears - although the site always reports correct login ... I will wait for the new version - maybe the problem will go away ...

    My board is OrangePC and system was installed yesterday from GitHub (2020 03 07)


    Maybe I can install the image you propose on my board?

    • Official Post

    Maybe I can install the image you propose on my board?

    no, it won't work. You have right image already. Part above quote was target to OrangePi PC2 owners in general. I guess I should make two separate posts, sorry for the confusion. YT addon is pain to set up currently, I spend few hours yesterday. Just try python3 6.7.0 beta1 from here: Release 6.7.0-dev · jdf76/plugin.video.youtube · GitHub

  • Decided to give the nightlys another go after 6 months on my OPI3. All hardware seems to work nice, however most videos have a shudder, like they're going at maybe 15fps.. Is there current problems with video decoding on the OPI3?

    • Official Post

    Is there current problems with video decoding on the OPI3?

    No. Press "o" during playback and check which codec it is and if it is HW or SW decoded. Chances are that you're using unsupported codec and it's decoded in software. That can happen with YouTube plugin now that more and more video streams are VP9 coded. While H6 technically supports HW decoding VP9, it will take a while before it becomes implemented.

  • Yes, I wired rx and tx crossed over looking at the label on the pin. Anyways, I switched the rx tx over and it works! I guess it is either the label on my usb serial is wrong or I was just too tired after coming back from work.


    Ok, attached is the log from serial log from Orange Pi One. I compared the log from the one that fails to boot and the one that boots (the image from dejan_).


    jernej It seems like in both cases uboot managed to reach "starting kernel ...". There seems to be not enough info for this from the serial console log I collected. Will removing "quiet" from extlinux.conf make it more verbose?

    jernej This is continuation of the Nano Pi (and Orange Pi One) failed to boot unless u-boot: update to v2020.01 is reverted reported by dejan_ and natumbri . I have tried to capture the output from serial console using usb serial with "quiet" removed from extlinux.conf to get more verbose info. However, it seems like removing "quiet" produces no extra info. It still stops at "starting kernel". Do you have a suggestion on how to proceed next to investigate this issue?

  • jernej Do you think an Opi Lite 2 image is possible now that the Opi 3 and One Plus are supported? The only differences I can think of are the different WiFi chip (AP6255 vs. AP6256 on the Opi 3) and only one USB 3 port (without hub chip, I think).


    I'm sure those differences can be solved using DT bindings, but I have no idea on how to use those on the LibreELEC compilation stack (I would also be thankful if someone could lead me to a wiki or give me advice on that).

  • Hi,


    as far as i understood, the tanix-tx6 image should work with the Eachlink H6 Mini regarding to my resarch here and elsewhere.

    Is this supposed to work ootb or are there any tweaks necessary to get it work? I simply flashed my SD-Card with the image and fed it to my Eachlink H6 Mini, but i get nothing on HDMI. The device isn't reachable via network, too.

    If i misread it and the Eachlink still needs some work, i will probably try to implement it...

    Thanks for any hints :)


    Regards

    rellla

  • Dear Jernej,


    Many thanks for your work! I am new here, so hello everyone! :);)

    I would like to test your build on my Orange Pi Plus 2E. I have installed it fine but I were unable to find any suitable PVR IPTV Simple Client neither in repository, nor from the Web. I have tried to install lots of different versions from ZIP files (3.8, 4, 4.1.1 etc.) but the Kodi just said there were problems and the Add-on hasn't been installed.

    Perhaps, you could provide me a working IPTV Simple Client, so I was able to test the video acceleration on my board? Any help would be highly appreciated!!!

  • Hi, I’m using an image for my “orange pi one-plus”.

    (LibreELEC-H6.arm-9.80-nightly-20200311-097260a-orangepi-one-plus.img.gz)

    The board is connected via HDMI to the TV, the OS boots, but there is no image.

    The TV writes “there is no signal at the input”, BUT in the TV speakers, through the crackle, the sound of moving through the menu items is heard. (I press enter on the keyboard)


    With Other images from the site orange (all sorts of armbian) normally output the image and sound ...


    what could be wrong?



    • Official Post

    rellla Please check with serial console what's going on, note that you should remove "quiet" kernel argument from extlinux.conf. Eachlink H6 is known to have issues with mainline U-Boot and Linux - with DRAM initialization and with HDMI plug in detection. There are workarounds available as described on Armbian forum, but it would be good to know which one of these two issues you experience (or both).

  • So those come from armbian and mainline kernel, as I expected. As far as I understand I could fetch the commits from that pull request, do I need to also make an specific "target" for the Orange Pi Lite 2? Where are the target files for the supported devices located in the git repo?