Openelec Build for OPI PC and 2 now with HW decoding

jernej · Published in 2016-10-19 12:50:35

andrzejm replied at 2016-10-19 00:03
Ok I've tested image.
First thing I noticed is that Kodi window resized - in my case it was zommed i ...

Thanks for testing. I forgot to say that it would be better to test image referenced in #1487. Image that you tested is known to be unstable - it is for meant to test non 16:9 resolutions. I guess that you will get similar issues...

andrzejm · Published in 2016-10-19 23:51:54

Ok I'll check another one, but #1487 is my post - which image should I test?

jernej · Published in 2016-10-20 00:00:56

andrzejm replied at 2016-10-19 16:51
Ok I'll check another one, but #1487 is my post - which image should I test?

Sorry, I meant #1483 http://www.orangepi.org/orangepi ... &fromuid=198504

andrzejm · Published in 2016-10-20 01:27:49

Ok I did not see cedar crashes anymore (the one restarting Kodi interface)

However I was able to freeze kodi twice - both GUI, console and ping are not responding. There is no additional trace visible in console at the moment of freeze (green light on board).
Is there any way to make console more verbose? I've got this in my autostart script: "echo 8 > /proc/sys/kernel/printk"
Console printouts from both tests: https://paste.ubuntu.com/23349664/ https://paste.ubuntu.com/23349690/

jernej · Published in 2016-10-20 01:35:45

There is one way. Do this:

systemctl stop kodi
/usr/lib/kodi/kodi.bin

Copy code

along your printk loglevel adjustment.

That way kodi will print a lot of CedarX debug messages, but it won't restart automatically in case of crash. I hope messages will be helpful.

andrzejm · Published in 2016-10-20 03:45:59

Edited by andrzejm at 2016-10-19 19:47

Ok, I've reproduced freeze after starting Kodi as you proposed and now crashes are visible in console: https://paste.ubuntu.com/23350288/Crashed around line 3148

jernej · Published in 2016-10-20 04:43:23

andrzejm replied at 2016-10-19 20:45
Ok, I've reproduced freeze after starting Kodi as you proposed and now crashes are visible in consol ...

Thanks, that should give me a better understanding of the issue. Unfortunatelly, currently I don't have enough time to track it down, but it is high on my todo list.

andrzejm · Published in 2016-10-20 06:47:30

I'm glad I could help!

gforcecro · Published in 2016-10-20 22:35:20

darqoq replied at 2016-2-10 04:09
You don't record any IR code, your section codes is empty !!!. Example:
GUIDE for DUMMIES:
http://w ...

Simillar problem.NOt working.Please help..

begin remote

  name  /storage/.config/lircd1.conf
  bits          32
  flags SPACE_ENC|CONST_LENGTH
  eps          30
  aeps       100

  header    8560  4236
  one          559  1567
  zero       559 510
  ptrail       560
  gap       175529
  toggle_bit_mask 0x0

   begin codes
      KEY_SUBTITLE          0xC53A9966 0xF50A6C93
      KEY_PLAYPAUSE          0xC53A7986
      KEY_POWER             0xC53A9966 0xF50A3DC2
      KEY_PAUSE             0xC53AF906
      KEY_REWIND             0xC53A9966 0xF50A57A8
      KEY_RIGHT             0xC53A9966 0xF50A26D9
      KEY_BACKSPACE          0xC53A9966 0xF50AA758
      KEY_CANCEL             0xC53A9966 0xF50A2FD0
      KEY_DOWN                0xC53A9966 0xF50ACF30
      KEY_ENTER             0xC53A9966 0xF50AF708
      KEY_EXIT                0xC53A9966 0xF50A6D92
      KEY_FORWARD             0xC53A9966 0xF50A9768
      KEY_FASTFORWARD       0xC53A39C6
      KEY_SCROLLDOWN          0xC53A9966 0xF50ACF30
      KEY_SCROLLUP          0xC53A9966 0xF50A4FB0
   end codes

end remote

cat /storage/.config/autostart.sh
#!/bin/sh
killall lircd
lircd devinput

jernej · Published in 2016-10-20 23:02:28

Edited by jernej at 2016-10-20 16:03

gforcecro replied at 2016-10-20 15:35
Simillar problem.NOt working.Please help..

begin remote

You are reading obsolete tutorials. Please read FAQ topic. For one, you shouldn't have lircd commands in autostart.sh anymore.