Nightly builds

With the latest nightly S912 box (Tanix TX92) keeps rebooting instead of shutting down. I left out a few builds because of traveling so I cannot put a pin on which nightly release it started.

Any idea what might be causing this?

Iā€™ve noticed several times (especially after upgrading from build to build) that my TV setting for aspect ratio is reset. Shifts from ā€œJust Scanā€ to ā€œ16:9ā€.
And on the latest build (April 27), Netflix is not showing image (black screen). When stopping a stream (blind controls) the aspect ratio resets again.
Any hints on what to collect? Debug log?
S912 device + Whitelist for all supported TV modes + Refresh Rate 1 sec pause (no option for On Start/Stop).

Cheers,
anthonws.

EDIT:

Debug log here: kodi.log (2.0 MB)

Looks like itā€™s not all Netflix streams. Some play correctly, others donā€™t.

#1 Iā€™ve updated the Netflix Plugin to the latest from https://github.com/CastagnaIT/plugin.video.netflix (Iā€™ll open an issue in that repository)
#2 Iā€™ve been able to repro the issue where I try to play a couple of streams and thereā€™s a black screen, with sound
#3 On exiting those problematic streams (stop) the Aspect Ratio changes from ā€œJust Scanā€ to ā€œ16:9ā€

Looking into the debug log I didnā€™t find anything eye catchingā€¦

Hereā€™s the summary of errors that I found:

	Line 185: 2019-04-28 14:08:34.782 T:4093684544   DEBUG: DBus method call to org.freedesktop.ConsoleKit.Manager.CanStop at /org/freedesktop/ConsoleKit/Manager of org.freedesktop.ConsoleKit failed: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.ConsoleKit was not provided by any .service files
	Line 187: 2019-04-28 14:08:34.783 T:4093684544   ERROR: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
	Line 187: 2019-04-28 14:08:34.783 T:4093684544   ERROR: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
	Line 187: 2019-04-28 14:08:34.783 T:4093684544   ERROR: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
	Line 190: 2019-04-28 14:08:34.799 T:4093684544   DEBUG: DBus method call to org.freedesktop.UPower.EnumerateDevices at /org/freedesktop/UPower of org.freedesktop.UPower failed: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
	Line 304: 2019-04-28 14:08:34.905 T:4093684544   DEBUG: DBus method call to org.freedesktop.DBus.Peer.Ping at /org/freedesktop/UDisks2 of org.freedesktop.UDisks2 failed: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UDisks2 was not provided by any .service files
	Line 305: 2019-04-28 14:08:34.905 T:4093684544   DEBUG: DBus method call to org.freedesktop.UDisks.EnumerateDevices at /org/freedesktop/UDisks of org.freedesktop.UDisks failed: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UDisks was not provided by any .service files
	
	Line 310: 2019-04-28 14:08:34.916 T:4093684544   ERROR: GetString: error reading /storage/.kodi/userdata/disp_cap
	Line 310: 2019-04-28 14:08:34.916 T:4093684544   ERROR: GetString: error reading /storage/.kodi/userdata/disp_cap
	
	Line 393: 2019-04-28 14:08:36.035 T:4093684544   ERROR: Error loading keymap: special://masterprofile/keymaps/remote.xml, Line 44
	Line 393: 2019-04-28 14:08:36.035 T:4093684544   ERROR: Error loading keymap: special://masterprofile/keymaps/remote.xml, Line 44
	Line 394:                                             Error reading Attributes.
	Line 396: 2019-04-28 14:08:36.071 T:4093684544   ERROR: Error loading keymap: special://profile/keymaps/remote.xml, Line 44
	Line 396: 2019-04-28 14:08:36.071 T:4093684544   ERROR: Error loading keymap: special://profile/keymaps/remote.xml, Line 44
	Line 397:                                             Error reading Attributes.
	
	Line 2645: 2019-04-28 14:09:36.116 T:3552891696   ERROR: GetDirectory - Error getting /usr/lib/kodi/addons/inputstream.adaptive/
	Line 2645: 2019-04-28 14:09:36.116 T:3552891696   ERROR: GetDirectory - Error getting /usr/lib/kodi/addons/inputstream.adaptive/
	Line 2780: 2019-04-28 14:09:39.884 T:3552891696   DEBUG: AddOnLog: InputStream Adaptive: DecryptSampleData: Decrypt failed with error: 2 and key: 00000000393EB83D0000000000000000
	
	Line 2917: 2019-04-28 14:09:40.722 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 2.4 is not allocated
	Line 2919: 2019-04-28 14:09:40.722 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 3.2 is not allocated
	Line 2922: 2019-04-28 14:09:40.722 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 2.7 is not allocated
(....)
	Line 7927: 2019-04-28 14:10:40.883 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] Prediction is not allowed in AAC-LC.
	Line 7930: 2019-04-28 14:10:40.924 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] Inconsistent channel configuration.
	Line 7932: 2019-04-28 14:10:40.924 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] get_buffer() failed
	Line 7935: 2019-04-28 14:10:40.965 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 2.4 is not allocated
	Line 7938: 2019-04-28 14:10:41.006 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 0.2 is not allocated
	Line 7942: 2019-04-28 14:10:41.047 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 2.14 is not allocated
	Line 7945: 2019-04-28 14:10:41.088 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 3.10 is not allocated
	Line 7948: 2019-04-28 14:10:41.129 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 3.3 is not allocated
	Line 7952: 2019-04-28 14:10:41.170 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] channel element 2.9 is not allocated
	Line 7956: 2019-04-28 14:10:41.211 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] Inconsistent channel configuration.
	Line 7957: 2019-04-28 14:10:41.211 T:3458011952   ERROR: ffmpeg[CE1D1330]: [aac] get_buffer() failed
	Line 9727: 2019-04-28 14:10:51.724 T:4093684544   ERROR: Control 50 in window 10025 has been asked to focus, but it can't
	Line 10018:                                             TypeError: 'NoneType' object has no attribute '__getitem__'
	
	Line 10081: 2019-04-28 14:11:05.839 T:3552891696   ERROR: GetDirectory - Error getting /usr/lib/kodi/addons/inputstream.adaptive/
	Line 10081: 2019-04-28 14:11:05.839 T:3552891696   ERROR: GetDirectory - Error getting /usr/lib/kodi/addons/inputstream.adaptive/
	Line 10240: 2019-04-28 14:11:09.567 T:3552891696   DEBUG: AddOnLog: InputStream Adaptive: DecryptSampleData: Decrypt failed with error: 2 and key: 00000000393EB7800000000000000000
	
	Line 10497: 2019-04-28 14:11:10.979 T:4066362160   DEBUG: ActiveAE::SyncStream - average error of 975.563583, start adjusting
	Line 10693: 2019-04-28 14:11:12.857 T:4066362160   DEBUG: ActiveAE::SyncStream - average error 0.598416, last average error: 975.563583
	Line 10693: 2019-04-28 14:11:12.857 T:4066362160   DEBUG: ActiveAE::SyncStream - average error 0.598416, last average error: 975.563583
	Line 10696: 2019-04-28 14:11:13.027 T:4066362160   DEBUG: ActiveAE::SyncStream - average error of -42.350063, start adjusting
	Line 10697: 2019-04-28 14:11:13.028 T:4066362160   DEBUG: ActiveAE::SyncStream - average error -0.016730 below threshold of 30.000000
	
	Line 12297: 2019-04-28 14:11:41.619 T:4093684544   ERROR: Control 50 in window 10025 has been asked to focus, but it can't

The most relevant/related logs that I can see in the above excerpt are:

Line 310: 2019-04-28 14:08:34.916 T:4093684544   ERROR: GetString: error reading /storage/.kodi/userdata/disp_cap
Line 310: 2019-04-28 14:08:34.916 T:4093684544   ERROR: GetString: error reading /storage/.kodi/userdata/disp_cap

Line 9727: 2019-04-28 14:10:51.724 T:4093684544   ERROR: Control 50 in window 10025 has been asked to focus, but it can't
Line 10018:                                             TypeError: 'NoneType' object has no attribute '__getitem__'

EDIT 2:

Created disp_cap file with this command:

cat /sys/class/amhdmitx/amhdmitx0/disp_cap > /storage/.kodi/userdata/disp_cap

File content:

CoreELEC:~/.kodi/userdata # cat disp_cap
480p60hz
576p50hz
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz

Will do some more testing :slight_smile:

On latest ā€œCoreELEC-Amlogic-ng.arm-9.0-nightly_20190429.tarā€ CoreElec Configuration doesnā€™t keep Estuary skin settings for color, background, fontā€¦

Normal for all icons:

Only CE Configuration:

Am I really the only one with this problem? :roll_eyes:

It is a known issue and we know the cause.

1 Like

Okay, then I can stop worrying :wink:

  1. Do you use Wi-Fi to connect?
  2. If first answer yes, than in connection settings please check if your ethernet adapter not enabled? If not enabled, try to enable it.

No, I use ethernet only, WiFi is disabled.

Friend @relkai can resurrect the link that addon.
Iā€™m having a problem sometimes it turns out the tuner, Iā€™ve had the same problem before.
I would like to test the updated addon with an older version of Coreelec.
Well, I think my tuner might be in trouble.

It wasnā€™t a link posted by me and you need to ask @afl1.

1 Like

There still remains the lingering problem with TVheadend that if you select a channel to soon after a reboot it subsequently gets stuck and will not allow any more channel changes. If you however wait for all boot up events to completely finish (about 30 secs) this problem doesnā€™t arise.
I am wondering if it has something to do with the Zomboid VPN addon which is just about the last process to launch and would be responsible for changing the apparent IP address that the TVH server talks back on.

Shoog

My two S905 boxes have started to auto-update nightlies, even though updates are set to Manual. Is this by design?

It is not possible to automatically update to the newest version. You also wonā€™t see any update notifications.

I use this settings. Nightly is auto updating on manualā€¦and I get update notifications too daily.

Can confirm this update behaviour

Yes itā€™s a feature not a bug.

The idea behind nightlies is to keep everybody up to date. That way, if a new issue is introduced, we can detect and fix it quickly without it lingering in the code base for days or weeks until someone accidentally stumbles on it, and then weā€™d have to scratch our heads looking for the problem.
So weā€™ve made the decision to force auto updates to be always on.

Itā€™s not really a feature since the Manual setting is now being ignored.
The reason I select manual is because I donā€™t want to auto-update nightlies but like to be notified of the new update so I can check out the changes.
So is the only way to prevent this to remove the custom channel settings?
What is the Auto setting for?

1 Like

I have to agree that this is not good policy. A setting is now not behaving as expected which by definition make it a bug. As far as I can tell its not even achieving its stated objective since it requires a manual reboot to trigger the update and there is no knowing when the update arrives to know when to initiate that trigger.
I have no problem with this been setup as Auto. However for the longest time the Auto update was broken on my system and never drew in the normal nightlies so I gave up on it and always downloaded the TAR. I only did intermittent updates simply because quite often the changes were not applicable to my system.

So great to have AUTO update working again on mys system - but no to breaking the manual switch.

Shoog

1 Like

This change makes it feel like ā€œYou are the product.ā€

Everyone does not have the time to deal with the bugs/changes introduced by nightlies.

I did not like it when it was introduced with N2. This makes it worse as it is going to be like this for all devices.

The definition of ā€œnightlyā€ builds is using a system thatā€™s on the bleeding edge. New features, changes, updates, regressions, major breakages, anything can happen. We donā€™t have time for chasing problems that were introduced weeks ago because users stay on old nightly builds.
We are currently integrating a new device (and kernel) into the coreelec-9.0 repository. Itā€™s very important to avoid build fragmentation as much as possible. Itā€™s also very important for problems and issues to surface as soon as possible, and not be delayed because you have a problem, and donā€™t have time to report it and simply stay on an old build.

If you want a stable build, use a CoreELEC 9.0.1 Stable.

5 Likes