[VU+ Duo4K SE] Video Semi-Crash

[JerryK132]

What type of support thread are you creating?

Possible bug

What OpenViX Image build number are you using?

6.7.012 (Release)

Have you tried re-flashing WITHOUT settings restore?

NO

Have you tried re-flashing WITH a settings restore?

NO

Image was lost, replaced by distorted negative colors reminiscent of the actual image. Sound ok. Changed channels -> same image (orig channel) sound changes to new channel. request standby and re-enable -> distorted colours. Request deep standby, re-enabled and OpenVix appears to restart ok-> image and sound fine. Restart was at approx 17:29 today. Debug logs attached. Larger one is leading up to restart. Other is at 17:31 after restart from deep standby.

I had noticed sound and video dropouts earlier, but once the video had frozen, changing channels from terrestrial French to 28.3 UK channels, the image did not return/reset. Despite this I suspect that the loss of image data may have been responsible for the video hanging in this way.

Notes:
This has only happened once...
The STB timestamps on FileZilla suggest that the SBC clock is an hour ahead of us here in GB.

With reference to my recent posts on various crashes, this one does not seem related. In fact previously reported crashes have no recurred at all since the latest changes were updated.

 

[twol]

That sounds/looks like reception breakup….. something I get on 28.2E in the Summer evenings as I am in a marginal reception area

 

[twol]

Deleted"………..

 

[twol]

so problem occurred before 1st log posted.
16:30:50.3393 [eFilePushThreadRecorder] Warning: All write buffers busy
16:30:50.3393 [eDVBRecordFileThread] cancelling
16:30:50.3394 [eDVBRecordStreamThread] failed to cancel, killing all waiting IO

.. and timer looks as if its still trying to start recording(s)

.. and all this webif stuff (to do with Kodi???) I have never seen before ... can you explain where that is from (how is it enabled??) and what its trying to do??

16:30:07.8083 "::ffff:192.168.50.120" - - [21/Jun/2025:15:30:04 +0000] "GET /web/currenttime HTTP/1.1" 200 82 "-" "Kodi/21.2 (Linux; Android 9.0; AFTKA Build/PS7699.4894N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.2-(21.2.0)-Git:20250115-d1a1d48c3c"
16:30:14.2399 [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/20250621 1459 - Sky Arts - Celine Dion Taking Chances World Tour.ts
16:30:14.2486 "::ffff:192.168.50.120" - - [21/Jun/2025:15:30:07 +0000] "GET /api/moviedetails?sref=1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3A%2Fmedia%2Fhdd%2Fmovie%2F20250621%201459%20%2D%20Sky%20Arts%20%2D%20Celine%20Dion%20Taking%20Chances%20World%20Tour%2Ets HTTP/1.1" 200 429 "-" "Kodi/21.2 (Linux; Android 9.0; AFTKA Build/PS7699.4894N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.2-(21.2.0)-Git:20250115-d1a1d48c3c"
16:30:14.5321 "::ffff:192.168.50.120" - - [21/Jun/2025:15:30:14 +0000] "GET /web/tunersignal HTTP/1.1" 200 167 "-" "Kodi/21.2 (Linux; Android 9.0; AFTKA Build/PS7699.4894N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.2-(21.2.0)-Git:20250115-d1a1d48c3c"

 

[JerryK132]

so problem occurred before 1st log posted.
16:30:50.3393 [eFilePushThreadRecorder] Warning: All write buffers busy
16:30:50.3393 [eDVBRecordFileThread] cancelling
16:30:50.3394 [eDVBRecordStreamThread] failed to cancel, killing all waiting IO

.. and timer looks as if its still trying to start recording(s)

.. and all this webif stuff (to do with Kodi???) I have never seen before ... can you explain where that is from (how is it enabled??) and what its trying to do??

16:30:07.8083 "::ffff:192.168.50.120" - - [21/Jun/2025:15:30:04 +0000] "GET /web/currenttime HTTP/1.1" 200 82 "-" "Kodi/21.2 (Linux; Android 9.0; AFTKA Build/PS7699.4894N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.2-(21.2.0)-Git:20250115-d1a1d48c3c"
16:30:14.2399 [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/20250621 1459 - Sky Arts - Celine Dion Taking Chances World Tour.ts
16:30:14.2486 "::ffff:192.168.50.120" - - [21/Jun/2025:15:30:07 +0000] "GET /api/moviedetails?sref=1%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3A0%3A%2Fmedia%2Fhdd%2Fmovie%2F20250621%201459%20%2D%20Sky%20Arts%20%2D%20Celine%20Dion%20Taking%20Chances%20World%20Tour%2Ets HTTP/1.1" 200 429 "-" "Kodi/21.2 (Linux; Android 9.0; AFTKA Build/PS7699.4894N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.2-(21.2.0)-Git:20250115-d1a1d48c3c"
16:30:14.5321 "::ffff:192.168.50.120" - - [21/Jun/2025:15:30:14 +0000] "GET /web/tunersignal HTTP/1.1" 200 167 "-" "Kodi/21.2 (Linux; Android 9.0; AFTKA Build/PS7699.4894N) Android TV/9.0.0 Sys_CPU/armv7l App_Bitness/32 Version/21.2-(21.2.0)-Git:20250115-d1a1d48c3c"

Hi Twol - sorry - me again!

No. Time is really 17:30 ...not 16:30...

The webif stuff comes from my kitchen FireStick (192.168.50.120) running Android Kodi Enigma2 PVR plugin. This FireStick is powered down when I am not using it. I had used it earlier that afternoon - possibly at 16:30 UK time. Could Kodi and enigma be set to different time zones, perhaps?

Installing the Latest Kodi Enigma2 PVR plugin enables the Kodi webif calls - only obviously when the Firestick is powered up. Which I don't think it was when the problem occurred

 

[twol]

@JerryK132 - so bear with me!!
When you are in the Kodi Enigma2 PVR plugin, it generates the WEBif lines that are interrogating/playing movies on the firestick??? or ...?

 

[JerryK132]

@JerryK132 - so bear with me!!
When you are in the Kodi Enigma2 PVR plugin, it generates the WEBif lines that are interrogating/playing movies on the firestick??? or ...?

In case I've not quite understood your question: Kodi is installed on the Firestick, along with the K/E2 PVR Plugin. This sends what I think are WebIf (or perhaps WebIf-like) commands to my Vu+ box. I'm assuming WebIf is a documented API that Kodi developers are using - but that's just an exploratory guess on my part since I am not familiar with this particular dev environment

Sorry @twol - I only just spotted your reply just now!

I think the various underlying (timeshift related) crashing problems I was experiencing have all been resolved, so this may be somewhat academic but perhaps useful in highlighting a recent change (a rewrite, even!) in the Kodi - Enigma2 interface methods for other users/devs...

Thanks