X-newa 2.5.2 Release

[mvallevand]

In 2.4.8 you added a 1.2-second delay in emulate.py before sending the CTRL+F5 keypress after playback stop to help with the refresh timing of my plugin. This seems to be missing in the new version so it would be great if you could add it back. Thanks.

Sorry i am not planning on doing on any special processing especially delays since the needs rendering status now triggers a screen refresh. This feature was primarily added so the green watched status would show and it seems to work fine now but if I hear reports on that not working (with logs) I will look into it. Perhaps your plugin neeeds to force a needs rendering.

Martin

[mvallevand]

Small changes to this version now that Krypton RC2 is out.

Code:

- Web client conext menu on DVD button MCE remote
- Web client OK/Select should not change OSD behaviour
- Allow hostname instead of IP

Note there is an unfortunate change in Kodi when the number key is entered on playback, both the NextPVR OSD and Kodi timeline will show. The NextPVR behaviour will normally succeed ie 5 right moves 5 minutes forward channel number tuning works. The only advantage this gives is direct time seeking works ie 4500 OK takes you to 45:00 in a recording. Other than ascetics you now cannot direct tune a channel number in F1 on a recording.

Martin

[johnsonx42]

should we assume that X-NEWA 2.5.1 will be final approximately when Kodi 17 is final? will it continue to support 16.1? Once 17 auto-upgrades on my Nexus Player, if it's as terrible as Beta 2 or whatever beta it was that I tried, I'll have no choice but to side-load 16.1 and hopefully find a way to stop it from upgrading.

[mvallevand]

should we assume that X-NEWA 2.5.1 will be final approximately when Kodi 17 is final? will it continue to support 16.1? Once 17 auto-upgrades on my Nexus Player, if it's as terrible as Beta 2 or whatever beta it was that I tried, I'll have no choice but to side-load 16.1 and hopefully find a way to stop it from upgrading.

Yes I hope to go final with Kodi. There really isn't anything that should be a problem specirfic to any version of Kodi. 16.1 should be trouble-free if it isn't I'd like to know about it.

Martin

[johnsonx42]

I tried Kodi 17RC2, and it's just about as bad on the Nexus Player as the beta was, so I'm going back to Jarvis; there's little reason to imagine that anything will change between now and release. 1080i MPEG-2 seemed better than I recall with beta 2, but it's still not watchable.

Luckily the Nexus Player does have a setting to not auto-update apps, so I'm safe on Jarvis for awhile. Quite disappointing: playback with Kodi 16 on the Nexus Player was a solid improvement over Isengard, and 16.1 seemed to make it better still. I think there were also improvements with Android 7 (now up to 7.1.1), so the Nexus Player has been a very solid playback client for me for the past 6 months. Not being able to upgrade to Krypton is a bitter pill.

[mvallevand]

If you sideload the apk I mention in this post http://forums.nextpvr.com/showthread.php...post511789 are things better? It might bring back h/w decoding.

Martin

[johnsonx42]

I'd not be able to use that APK since it's for ARM and the Nexus Player uses an Intel Atom CPU.

However, does the fact that they've discovered and fixed in a test-build a bug on Android mean that it may make it into the next RC? Or are those kinds of fixes no longer being accepted?

[mvallevand]

I'd not be able to use that APK since it's for ARM and the Nexus Player uses an Intel Atom CPU.

However, does the fact that they've discovered and fixed in a test-build a bug on Android mean that it may make it into the next RC? Or are those kinds of fixes no longer being accepted?

I doubt it the pull request is closed https://github.com/xbmc/xbmc/pull/11318

With no major Android developers on Kodi, little interest in any x86 Android devices and the fact that Nexus Player is dead and it never was a favoured Koldi player anyway I wouldn't hold high expectations.

Martin

[jcjefferies]

Martin

Is it possible to keep the original addon.xml when installing the latest update? At the moment after an update I have to SSH into each client and edit the file so X-NEWA starts at boot time.

Chris

[mvallevand]

Martin

Is it possible to keep the original addon.xml when installing the latest update? At the moment after an update I have to SSH into each client and edit the file so X-NEWA starts at boot time.

Chris

Sorry not really since the addon.xml has the display version number. You could edit the file once and rezip it before installing if that makes it easier..

Martin