Openelec Build for OPI PC and 2 now with HW decoding

jernej

roblad replied at 2016-4-30 06:49
Hi,

Almost. Opi2 and plus needs script.bin fix which will be commited today. As mentioned above, driver for deinterlacing crashes after resume, but otherwise, its should work.

EDIT: Or maybe not. I must test few things first on OPi2 and OPiPlus, but this will take some days. OPiOne and OPiPC should have working suspend/resume according to some reports.

Dima

If you don't use lircd, it does indeed work. I tried again with various addons and stuff. Only lircd is the one thing that breaks suspend. Also power command of the remote doesn't work. So I really think there's something wrong in the lircd code.

jernej

You mean power off with remote? Because power on with remote will be hard to support unless you have remote which is compatible with original allwinner's IR driver.

Dima

jernej replied at 2016-4-30 18:39
You mean power off with remote? Because power on with remote will be hard to support unless you have ...

Yeah, KEY_POWER doesn't do anything.

c0013r

Dima, IR KEY_POWER always work, as power_off, i use this manual:
http://www.orangepi.org/orangepi ... thread&tid=1177

Dima

Oh, strange, will have to check my config, maybe I made a typo (I edited the file manually afterwards)

jernej

Dima replied at 2016-4-30 10:19
If you don't use lircd, it does indeed work. I tried again with various addons and stuff. Only lircd ...

I'm not so sure that lircd is the main reason. Could you test it with closed kodi (you must stop it through systemd) and lircd running?

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?