Openelec Build for OPI PC and 2 now with HW decoding

Red-Z

G'day,

I have some trouble with the latest build on OPi PC. After booting a fresh installation, the screen is completely striped /distorted over HDMI, the TV shows that the resolution is 576p, never had this problem before with other distros / devices.

Is there a solution for this special problem?

TY @ all,
Red-Z

(I know, the TV is very old...)

Dima

jernej replied at 2016-5-1 23:10
I'm not so sure that lircd is the main reason. Could you test it with closed kodi (you must stop i ...

Ok, I just tested a bit more extensively and this is sooooo strange! I've narrowed it down even further.
First a few remarks:
1) Even without running lircd, when killing kodi using systemctl, standby doesn't work anymore. However, it's important to note that when killing kodi, the last "screen" of kodi remains on the screen. So it isn't completely killed to a black screen.
2) I did indeed have a typo, KEY_POWER and KEY_SLEEP does put the Orangepi into sleep, which is good.

Narrowed down reason of not working standby:
When lircd is started manually from putty, it works perfectly: power button works, you can put the box into standby using the remote (wakeup only through button).
However, when lircd is started from autostart.sh (see below in code), the standby function breaks. On the other hand, when any other command than lircd is run from autostart.sh, it doesn't break the standby function.

1. #!/bin/sh
   
2. lircd /storage/.config/lircd.conf

Copy code

So this is a real mystery: what happens differently when lircd is run from autostart compared to run from putty.

jernej

Dima replied at 2016-5-2 07:34
Ok, I just tested a bit more extensively and this is sooooo strange! I've narrowed it down even fu ...

When kodi is stopped, you must use "systemctl suspend" command. Can you please try this. Kodi always renders directly to framebuffer, which mean that latest image will always stay. Maybe lircd issue can be explained with different environment at that point?

Dima

jernej replied at 2016-5-2 14:56
When kodi is stopped, you must use "systemctl suspend" command. Can you please try this. Kodi alwa ...

So, with autostart.sh lircd (the buggy combination):
The systemctl suspend command worked, however, power button didn't work to put it to sleep.

slaine

I have a problem with deinterleacing on pvr client (PVR VNSI). When the deinterleacing is on the horizontal lines appears on screen and I have problem with channel switching. When the deinterleacing is off the problems disappear.

jernej

Could you post some kind of image for horizontal lines? HW deinterlacing is known to be buggy. I have a long term plan to fix this. However, few things must be done before.

jernej

Red-Z replied at 2016-5-1 17:21
G'day,

I have some trouble with the latest build on OPi PC. After booting a fresh installation, the ...

It seems that Kodi wants to switch resolution on the fly due to some error in resolution detection. Maybe your TV doesn't support EDID (I'm not sure if that is possible). However, resolution switching on the fly isn't yet supported due to bug in Mali driver and workaround is needed. I have a long to do list but unfortunately this is not very high.

Dima

Quick update after even more testing: systemctl suspend also works without killing kodi.  And KEY_POWER also puts it into sleep. So there is something that breaks the power button to suspend when lircd is run from autostart.sh

Last one thing I tested: I put sleep 20 in autostart.sh code:

1. #!/bin/sh
   
2. (
   
3. sleep 20; \
   
4. lircd /storage/.config/lircd.conf;
   
5. ) &

Copy code

This breaks initial function of the remote (don't know why), but the power button works. After waking up from a power button suspend, the remote works again!

So my suspicion is that Kodi does something wrong when lircd is running when it starts up.

I there's anything else that I could help to debug, let me know. I've tested every possible scenario I could imagine.

jernej

Dima replied at 2016-5-2 10:23
Quick update after even more testing: systemctl suspend also works without killing kodi.  And KEY_PO ...

I think there might be more than one issue, so we need to sort some things out. First of, which board do you have? Plus? When you said that suspend works, do you mean that also resume works? Do you have any kind of USB device like, but not limited to, mouse or keyboard connected during suspend/resume?

Dima

jernej replied at 2016-5-2 17:44
I think there might be more than one issue, so we need to sort some things out. First of, which bo ...

I have the Orangepi PC.

Resume always works. It's the suspend that doesn't work for me using the power button.
At this moment, I do have the mouse plugged in. However, without the mouse it's the same result.

Actually, for me: I can live with this. I don't actually need the power button suspend, as long as resume works. I just try to help out as much as possible to find the "root cause" of this problem.