Posts by lumpi

    I'm having a similar x92, the correct image should be the box version, that uses the vendor uboot loader of the box (Android and probably also CE?) I'm in the meantime running my box with the vim2 image of manjaro linux and can tell that linux on a current mainline kernel works quite well on the s912, so id guess also this image should work reasonably well.


    P.S. running mine of a SD card, so no risk at all.

    jernej I wrote today's image on a new SD (zeroed the first 10MB) and everything works perfectly, shutdown and restart by the original remote, sleep and wake up by the remote, both working as expected.


    Thank you very much for your development and your support, now it feels like a readymade bought STB.


    It's really cool!

    Of course, that is already implemented, it just acts up on Beelink X2. It works reliable for me on OrangePi Plus2E and BananaPi M2+ (speaking about H3 boards).

    Wondering if it's the X2 or user problems...


    Could you please explain to me how exactly I should trigger a shutdown that will stop the cores and hands over to the arisc? The shutdown dialog triggers a shutdown only to a halt with hdmi on, like old PCs with AT powersupplies.

    Then I'm positive things will improve over time.


    jernej is it technically feasible to not just send the SOC to sleep, but in fact shutdown Linux and power off the ARM cores and use the ARISC core to power them on via remote or button and perform a proper boot from scratch? That would be much more useful in my opinion. That would also eliminate the need for power cycling to start after a shutdown.

    Hmmm Sorry, as I don't have the stick I can't help you more, but if you can try a different TV...


    I hope someone of the devs will see this thread and jump in to help ;)

    Привет. Форум на английском языке. Пишите на русском и английском языках (гугл переводчик).

    Now I had to use gugl perevodchik to find out what your answer was...


    Im using an LG WebOS TV from 2020 with LE nightly release on Allwinner platform and raspberry pi 3 with regular LE release and sound works on both, I never had to set anything for it to work.


    Does audio work with the software that was preloaded on your stick, just to confirm it is no hardware or compatibility problem...

    jernej todays version works only thing confusing a bit is that you land back in the shutdown dialog.


    Tested only with the button, not the remote.

    Pressing the button while running will bring up the shutdown dialog, a second press hides it again.


    Edit:

    found my original remote, no effect, when pressing the button on the x2 it didn't come alive again, like yesterday.

    I think the difference was that my first triel let it asleep only a very short time, I reactivated before the TV showed no signal, the second time, when it didn't come back it took a bit longer due to reying the remote


    Edit 2:

    My assumption was wrong, while doing some further tests I realised that actually the remote's red power button, when pressed while in sleep, triggers the freeze of kodi, not the duration of the sleep.


    Also interesting fact is that SSH keeps alive but is frozen the whole time the box is asleep, no reconnection necessary after waking up, it then even parses whatever I was typing while x2 was sleepin.


    Edit 3:

    I think it's at random if it's working or not...


    Would it also be possible to gracefully shutdown Linux and restart it by the button? If I'm shutting down it's not powering off, but shows "reboot: System halted", waking it back up is impossible, except by power cycling.


    I don't mind waiting for a full boot, bit getting up and connecting power is annoying, sleep is not my concern, it sleeps also well if all playback is stopped and tv switcjed to different input...

    if you execute "systemctl restart kodi", does it work? Also, do you have plain Kodi or do you have any addons, especially PVR ones? There were some suspend/resume issues with Kodi discovered and fixed. Kodi was just updated today in LE, so please re-try with tomorrow image. Suspend/resume is complex, every driver must work correctly...

    As per above editafter kodi restart all is ok,


    I'm having the rbuehlma zattooo pvr addon not surewhat version

    Will try again soon

    Thanks

    Original, NEC 0x8051

    Not sure I will fimd that again...


    Now I tried it and get the following:

    - setting to standby by remote

    - screen goes off, blue LED is off

    - pressing power button

    - screen comes back nearly immediately, no reaction to remote or anything else, screen is ddimmed, power menue is still displayed, round blue waiting symbol is visible, but not turning

    - Linux is accessible via SSH


    Edit: after "systemctl restart kodi" all back to normal

    lumpi What is your test case exactly? If you boot up Kodi normally and then select through power menu suspend or shut down, you should be able to revive box either with power button press on the box or on the remote.

    Ok good

    As my daughter is occupying the TV I tried to send the box to sleep by the button...

    Will try properly once she's in bed.


    What scancode is it expecting from the IR? The original remote's or MCE?

    Before I updated my X2 today, it had image from 2019. Update went through without any problem.

    Cool will try it in the evening.


    If that's working we only have to wait for a stable kodi/le release and addon authors to stabilise on python 3 for a daily driver. Incredible what your port achieved in the recent years.


    Still remembering my first time installation of debian/fedora on my A10, what a catastrophe ;-)

    Support for that just landed and it will be in tomorrow nightly image. However, it's unreliable on my Beelink X2, but it works just fine on other boards. Please test it on your X2. I have problematic version of that box (hard to boot from SD card), so chances are that it will work reliably on non-problematic.

    Cool will test it, didn't use the X2 in a while updates shouldn't be a problem if the last update is a couple of months ago i suppose?