[TESTING] Kodi 17 (Krypton) builds for Raspberry Pi (continued)

The latest build (161) should fix the addon issues - see first post.

16.8-160, 15 Sept 2016: Based off OSMC commit d55270and newclock5 (60260bd7)

Build Details

  • Fixed missing addons
  • CMake fixes

XBMC:
cmake cosmetics (PR:10437, 2 commits, 6 files changed)

1 Like

I’m have some trouble here: For me, the last update broke Kodi. It will no longer start - or, more correctly, it will attempt to start, but then only show me a blue screen with a sad face on it, before trying to restart, repeating ad nauseam. Any way I could help debug this?

Nice with new updates! Working just fine here.

I’m also having it crash on boot after upgrading.

http://paste.osmc.io/jazigicere

The new update worked for me and looks like it fix the PVR issue, alright. So far everything’s working fine for me.

Fails to update for me.

http://paste.osmc.io/julonuzemi.vhdl

That’s not an error – you have updated successfully.

Please forgive me as I am a noob with testing builds for OSMC, bear in mind I am tech savvy
couple of questions

  1. Why can’t I see the new OSMC theme? I don’t like the Kodi theme

  2. How come in MY OSMC it says September 2016 2016 9 1 build but there is an October build posted. I tried to “sudo apt-get update” and “sudo apt-get dist-upgrade” but says there is not upgrade

any help would be fantastic

The builds here (also the 4th octobre build) are test-builds.
Also take a look on top of the topic:

To get these builds, you will need to add @gmc’s Debian repository. This can be by editing /etc/apt/sources.list, and adding the following:

deb Index of /osmc/osmc/download/dev/gmc ./

To install a test build, run the following command to update the apt cache:

sudo apt-get update

And then issue the following command to install a test build for Raspberry Pi 2 or 3:

sudo apt-get install rbp2-mediacenter-osmc

After done this succesfully you later can now update to the latest build when it is published with the following commands:

sudo apt-get update
sudo apt-get dist-upgrade

I also got the sad face bootloop while upgrading from build 160 to 161. I reverted to build 160 and everything works fine again. This was on my Rpi3

Do you keep getting the sad face? I got it once after the upgrade and then has been stable since.

16.8-161, 04 Oct 2016: Based off OSMC commit d55270 and newclock5 commit 058e7a5e5

Build Details

Loads of issues fixed as its been a few weeks since the last build.
Various PVR add-on fixes
VideoPlayer: allow change of resolution before renderer has been configured
[pvr] attempt to fix crashing and general failure in ChannelExists() (@MikeKL please test/confirm)
rework cmake build system and adjust build variables (clean build)
Start of Kodi 17.0 beta3 cycle

XBMC:
[cmake/win32] Bump minimum CMake version to 3.6 (PR:10396, 5 commits, 3 files changed)
[estuary] check if fanart pack is selected (PR:10556, 1 commit, 6 files changed)
settings: provide descriptions for color management settings (PR:10296, 2 commits, 1 file changed)
[paplayer] remove no more needed virtual CAEChannelInfo GetChannelInfo() (PR:10559, 1 commit, 3 files changed)
[epg] fix mouse focus (PR:10558, 1 commit, 1 file changed)
Add possibility to get information from both .nfo and scraper (PR:10259, 1 commit, 5 files changed)
[paplayer] fix codec deinit for audio decoder add-on (was never called) (PR:10557, 1 commit, 4 files changed)
Some improvements (PR:10522, 5 commits, 5 files changed)
Add “userrating” so Player.GetItem can return user rating value for currently playing song (#10561) (d51d4ae9)
splash text improvements (PR:10560, 2 commits, 4 files changed)
[gui] fix header on sort dialog (PR:10578, 1 commit, 2 files changed)
[estuary] misc fixes (PR:10579, 1 commit, 12 files changed)
[GUIWindowSystemInfo] - allow one more label/row to be displayed (PR:10568, 1 commit, 1 file changed)
[gui] fix some fallback icons in Art selection dialog (PR:10576, 2 commits, 1 file changed)
[PVR] Fix: pvr client addons must be reloaded on profile switch to re-read addon config etc. (PR:10577, 1 commit, 1 file changed)
VideoPlayer: notify gui on speed changes (PR:10581, 4 commits, 1 file changed)
minor keymap change for tempo up/down (PR:10584, 1 commit, 1 file changed)
[gui] change fallback icon for “New playlist…” entries (PR:10590, 1 commit, 1 file changed)
[videoplayer] Remove codec name extraction from the codec fourcc field (PR:10588, 2 commits, 1 file changed)

newclock5:

New commits in this build:

VideoPlayer: drop some outdated comments (04532e80)
VideoPlayer: make omx alternative code path more obvious (18449f5f)
VideoPlayer: coding style fixes (a165e9c3)
VideoPlayer: notify gui when a change of playback speed occurs (c7d04a49)
VideoPlayer: allow change of resolution before renderer has been configured (058e7a5e)

Commits no longer in build:

VideoPlayer: drop some outdated comments (04532e80)
VideoPlayer: make omx alternative code path more obvious (18449f5f)
VideoPlayer: coding style fixes (a165e9c3)
VideoPlayer: notify gui when a change of playback speed occurs (c7d04a49)

Yes, I waited for about 5 minutes and then some time while I looked up what build number to install trough ssh from my phone. OSMC kept restarting.

See if 162 fixes the issue - should be up within the hour.

There is no October build of OSMC at this time.

The new theme is not available for testing yet, you can read the September post for more information

I just installed 162. Same problem, bootloops infinitely.
Reverted to 160 again and that still works.

Same for me on my pi3. One sad face after installing build 161 followed from one automatic restart and stable function since then.

Some debug logs would be good in identifying the problem. It would also be good to know if moving your ~/.kodi directory to ~/.kodi-backup helps resolve the issue.

Sam

It works when I rename ~/.kodi.
When I rename ~/.kodibackup to ~./kodi en restart kodi, the bootlooping start again. This is my log: http://paste.osmc.io/mixecezigu.coffee

That likely means that you have an add-on or skin that is not compatible with Kodi Krypton.

That’s not a debug log, so there’s nothing useful in there unfortunately