[TESTING] Kodi 18 (Leia) builds for Vero 2 & 4K

17.8-423, 23 Feb 2019: Based off OSMC commit (9bb2084ca) and xbmc (d81c34c46)

XBMC:

  • CUtil::ValidatePath fix double (back)slash check (PR:15499, 2 commits, 2 files changed)
  • HTTP2 client support (PR:15195, 2 commits, 5 files changed)
  • [Music]Fix delay of playback on switching song in party mode (PR:15557, 1 commit, 7 files changed)
  • [skins] prefer poster over thumb to match design (PR:15543, 1 commit, 4 files changed)

peripheral.joystick:

  • [cmake] link with tinyxml (PR:163, 2 commits, 5 files changed)
  • switch to new language folder layout (448fcfb)

pvr.dvblink:

  • addon version bump to 4.7.2 (PR:117, 1 commit, 2 files changed)

Includes latest addons:

addons: inputstream.adaptive (9b944a5), inputstream.rtmp (ce7f559), peripheral.joystick (1f4225a), peripheral.xarcade (f09a0e7), pvr.argustv(83aa1e9), pvr.demo (964686d), pvr.dvblink (4ae42fe), pvr.dvbviewer (1ff63d4), pvr.filmon (e850633), pvr.hdhomerun (a9d7309), pvr.hts (dc35ade), pvr.iptvsimple (73feb2f), pvr.mediaportal.tvserver (931afab), pvr.mythtv (9846896, +8), pvr.nextpvr (78c6633), pvr.njoy (4467cac), pvr.octonet (203f800), pvr.pctv(b60b971), pvr.stalker (d0170c5), pvr.teleboy (1956113), pvr.vbox (ea20464), pvr.vdr.vnsi (cbb75ab), pvr.vuplus (bb6babc), pvr.wmc (7b28be3), pvr.zattoo(c6ff1d2, +4), vfs.libarchive (6d39012), vfs.rar (0f56401), vfs.sftp (6749200)[/b]

Did you have a date for Official Release ? i’m very impatient :stuck_out_tongue:

1 Like

Did you seriously not read 2 posts above?

1 Like

It’s covered above.

Hahaha

Are we there yet? Are we there yet?

How about now? :laughing:

2 Likes

What exactly is everyone expecting from a ‘stable’ release that is not in these nightlies?

Stability? Where are the bug reports?

Features? They are already in. Unless I’m missing something, here.

1 Like

so you say there is no risk at all messing up the system by switching to nigthlies right now?

I heard rumors kodi 18.1 has a script that will roll me a smoke and prepare a cup of coffee when I get home. Can you confirm :smile:

1 Like

No, I was assuming everyone in here is on nightlies. If not, stop spamming a testing thread.

1 Like

hehe … well thats a quaint assumption. people are also reading this thread in order to be informed about progress. :point_up:

1 Like

grahamh has a good point. We’re distracting the people who are trying to bring out the new version .

Me again. I still have problems with the suspend mode. Tried newses nightly.
Sometimes it works on the X try - but most often suspend fails. Screen turns black for a moment and the kodi returns. How can I help debug this problem?
I had a look in kodi.log and find these lines regarding suspend:
2019-02-24 12:38:55.992 T:4066746368 NOTICE: Activating standby mode
2019-02-24 12:38:56.002 T:4066746368 NOTICE: CApplication::ToggleStandby – checking for existence of /home/osmc/.kodi/userdata/standby.py
2019-02-24 12:38:56.125 T:4066746368 NOTICE: CApplication::ToggleStandby – checking for existence of /home/osmc/.kodi/userdata/wake.py

But this seems not to be anyway helpful?!

Oh: maybe it is:
root@mediabox:/home/osmc/.kodi/userdata# ls -alh
insgesamt 88K
drwxr-xr-x 10 osmc osmc 4,0K Feb 18 20:36 .
drwxr-xr-x 8 osmc osmc 4,0K Feb 7 15:43 …
drwxr-xr-x 16 osmc osmc 4,0K Feb 8 18:14 addon_data
drwxr-xr-x 3 osmc osmc 4,0K Feb 24 09:56 Database
-rw-r–r-- 1 osmc osmc 198 Feb 18 20:36 favourites.xml
-rw-r–r-- 1 osmc osmc 30K Feb 22 19:39 guisettings.xml
drwxr-xr-x 2 osmc osmc 4,0K Sep 8 22:32 keymaps
drwxr-xr-x 2 osmc osmc 4,0K Sep 8 22:32 library
drwxr-xr-x 2 osmc osmc 4,0K Feb 7 14:54 peripheral_data
drwxr-xr-x 5 osmc osmc 4,0K Sep 8 22:32 playlists
-rw-r–r-- 1 osmc osmc 960 Feb 23 12:31 profiles.xml
-rw-r–r-- 1 osmc osmc 389 Sep 8 22:32 RssFeeds.xml
drwxr-xr-x 2 osmc osmc 4,0K Feb 7 09:53 Savestates
-rw-r–r-- 1 osmc osmc 2,1K Feb 8 19:34 sources.xml
drwxr-xr-x 19 osmc osmc 4,0K Sep 8 22:32 Thumbnails
There are no files called standby.py or wak.py

Debug enabled logs would be the first step.
The standby and wake scripts would be only there if you want to execute functions at standby or wake

It seems the KEY_UP event is triggering wakeup. It doesn’t happen with a USB KB:
https://paste.osmc.tv/sajigepoga.vhdl

Here is my debug log:

2019-02-24 13:41:12.994 T:4060082928 DEBUG: LIRC: - NEW 160 0 KEY_OK linux-input-layer (KEY_OK)
2019-02-24 13:41:13.004 T:4070551552 DEBUG: HandleKey: 11 (0x0b, obc244) pressed, action is Select
2019-02-24 13:41:13.005 T:4028625648 INFO: CActiveAESink::OpenSink - initialize sink
2019-02-24 13:41:13.005 T:4028625648 DEBUG: CActiveAESink::OpenSink - trying to open device ALSA:default
2019-02-24 13:41:13.005 T:4028625648 INFO: CAESinkALSA::Initialize - Requested layout: FL, FR
2019-02-24 13:41:13.005 T:4028625648 INFO: CAESinkALSA::Initialize - set digital_codec 0
2019-02-24 13:41:13.005 T:4028625648 DEBUG: CAESinkALSA::Initialize – unmuting HDMI
2019-02-24 13:41:13.005 T:4028625648 INFO: CAESinkALSA::Initialize - Attempting to open device “default”
2019-02-24 13:41:13.009 T:4028625648 INFO: CAESinkALSA::Initialize - Opened device “default”
2019-02-24 13:41:13.010 T:4028625648 INFO: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2019-02-24 13:41:13.011 T:4028625648 INFO: CAESinkALSA::InitializeHW - Using data format AE_FMT_S32NE
2019-02-24 13:41:13.011 T:4028625648 DEBUG: CAESinkALSA::InitializeHW - Request: periodSize 2048, bufferSize 8192
2019-02-24 13:41:13.012 T:4070551552 NOTICE: Activating standby mode
2019-02-24 13:41:13.012 T:4070551552 INFO: Activating Vero standby mode
2019-02-24 13:41:13.012 T:4070551552 INFO: Toggle standby state is sleeping
2019-02-24 13:41:13.012 T:4028625648 DEBUG: CAESinkALSA::InitializeHW - Got: periodSize 2048, bufferSize 8192
2019-02-24 13:41:13.012 T:4070551552 INFO: CApplication::ToggleStandby – Toggle TMDS clock to 0
2019-02-24 13:41:13.012 T:4028625648 DEBUG: CAESinkALSA::InitializeHW - Setting timeout to 186 ms
2019-02-24 13:41:13.012 T:4070551552 INFO: CApplication::ToggleStandby – Toggle LED brightness to 0
2019-02-24 13:41:13.012 T:4028625648 INFO: CAESinkALSA::Initialize - setting default aud_ch to 0
2019-02-24 13:41:13.012 T:4070551552 INFO: CApplication::ToggleStandby – governor will now be powersave
2019-02-24 13:41:13.014 T:4028625648 DEBUG: CAESinkALSA::GetChannelLayout - Input Channel Count: 2 Output Channel Count: 2
2019-02-24 13:41:13.014 T:4028625648 DEBUG: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR
2019-02-24 13:41:13.019 T:4070551552 INFO: CApplication::ToggleStandby – HPD locking will now be hpd_lock1
2019-02-24 13:41:13.021 T:4070551552 NOTICE: CApplication::ToggleStandby – checking for existence of /home/osmc/.kodi/userdata/standby.py
2019-02-24 13:41:13.022 T:4070551552 DEBUG: ------ Window Deinit (Custom_Overlay_Debug.xml) ------
2019-02-24 13:41:13.023 T:4070551552 DEBUG: ------ Window Deinit () ------
2019-02-24 13:41:13.024 T:4070548208 DEBUG: CAnnouncementManager - Announcement: OnScreensaverActivated from xbmc
2019-02-24 13:41:13.025 T:4070551552 DEBUG: ------ Window Deinit (DialogButtonMenu.xml) ------
2019-02-24 13:41:13.030 T:4028625648 DEBUG: CAESinkALSA::GetChannelLayout - Got Layout: FL, FR (ALSA: none) (CEA: 0)
2019-02-24 13:41:13.031 T:4070548208 DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, message OnScreensaverActivated
2019-02-24 13:41:13.031 T:4028625648 DEBUG: CActiveAESink::OpenSink - ALSA Initialized:
2019-02-24 13:41:13.032 T:4028625648 DEBUG: Output Device : Default (AML-M8AUDIO Analog)
2019-02-24 13:41:13.032 T:4028625648 DEBUG: Sample Rate : 44100
2019-02-24 13:41:13.032 T:4028625648 DEBUG: Sample Format : AE_FMT_S32NE
2019-02-24 13:41:13.033 T:4028625648 DEBUG: Channel Count : 2
2019-02-24 13:41:13.033 T:4028625648 DEBUG: Channel Layout: FL, FR
2019-02-24 13:41:13.033 T:4028625648 DEBUG: Frames : 2048
2019-02-24 13:41:13.034 T:4028625648 DEBUG: Frame Size : 8
2019-02-24 13:41:13.060 T:4060082928 DEBUG: LIRC: - NEW 160 0 KEY_OK_UP linux-input-layer (KEY_OK_UP)
2019-02-24 13:41:13.087 T:4070551552 DEBUG: ------ Window Init (Custom_Overlay_Debug.xml) ------
2019-02-24 13:41:13.110 T:4070551552 DEBUG: ------ Window Init () ------
2019-02-24 13:41:13.136 T:4070551552 INFO: Toggle standby state is waking
2019-02-24 13:41:13.137 T:4070551552 INFO: CApplication::ToggleStandby – Toggle TMDS clock to 1
2019-02-24 13:41:13.257 T:4070551552 INFO: CApplication::ToggleStandby – Toggle LED brightness to 1
2019-02-24 13:41:13.259 T:4070551552 INFO: CApplication::ToggleStandby – governor will now be ondemand
2019-02-24 13:41:13.263 T:4070551552 INFO: CApplication::ToggleStandby – HPD locking will now be hpd_lock0
2019-02-24 13:41:13.263 T:4070551552 NOTICE: CApplication::ToggleStandby – checking for existence of /home/osmc/.kodi/userdata/wake.py
2019-02-24 13:41:13.263 T:4070551552 DEBUG: HandleKey: 0 (0x00, obc255) pressed, action is
2019-02-24 13:41:13.270 T:4070551552 DEBUG: ToggleDeviceState - waking up CEC device…

As @grahamh wrote seems some remote keys (or fake keys) are waking up the device.

@fzinken - thanx for clarrification. I use the Vero 4k+ with original remote (which is maybe a missing information on my topic above)

Yeah, that seems one factor.
While for me it works even with orignal remote when I use the suspend on TV off.
Anyhow @sam_nazarko is now aware about the issue and might find a cause

1 Like