updated to OSMC 2017-02.02 using “apt-get update + dist-upgrade + final reboot”
rechecked whether surging video issue still there (yes)
whenever I start a choppy video the dmesg cmd shows 2 new entries [ 1430.068742] mxc_vpu 2040000.vpu: Physical memory allocation error! [ 1430.068768] mxc_vpu 2040000.vpu: Physical memory allocation error!
Installed Sam’s fix (wget + dpkg + reboot)
But it did not improve anything. Also after the installation of the fix I can see the dmesg entries
====================== systemd =================== 86JFGfNO
total 756
-rw-r--r-- 1 root root 403 Jan 7 05:13 -.slice
drwxr-xr-x 19 root root 12288 Mar 13 19:32 .
drwxr-xr-x 8 root root 4096 Jan 1 1970 ..
...
That “-.slice” is a typical signature of the Lavasoft trojan horse.
Could you log in as osmc (with putty or ssh) onto the Vero, then execute the command: “top”
and take a screenshot.
If they have replaced the programs etc. (top) it will hide itself so you won’t see it.
Then please provide a: cat /proc/loadavg
which will output the load actually handled by your vero CPU.
Please make sure Kodi is not running. sudo service mediacenter stop
Wait 5 Minutes, then check the load of the vero again.
and drop us the data returned.
You can also use: top -d 1 -b -n 1
Will show all running apps and their respective load and mem usage.
You got me there. When looking for slice, the most things I did find were hints on the lavasoft trojan.
Reason I asked also for top output. Gives an indication on what is running most and causing high CPU load, which is also one of the reasons the Vero 1 can playback video in choppy mode…
@sam_nazarko: Is there still a need of video clips to reproduce the issue?
If yes, I could try to generate a bunch of scene video clips out of a lot of films identified with the problem.
Sorry – it’s quite busy around here. I wanted to reply when I had some further information. I’ve been watching TV on my Vero 1 for a couple of days and didn’t have problem with the content I was playing (typically 1080p H264, with a passthrough track). I understand that’s not helpful for your situation, but wanted to see if I could typically reproduce this here.
If you PM me some sample clips that cause problems, I will take a look. Unfortunately there seem to have been some changes to VideoPlayer that have caused regressions for i.MX6. I’ll do my best to look at them and see if I can find a way to resolve them.
A debug log using the new build would also be helpful.
@sam_nazarko Just to make sure: Did you ever check the test-clip (choppy.mp4) that I sent you on Feb12? It plays choppy for other Vero 1 users on Krypton as well and I pasted debug-logs to pastebin.
So I tried the update to because for some people it worked. It didn’t change anything but it killed my settings ( lost language, video, audio, etc)
Checked my network speed and it is active on fast ethernet (100Mb).
In the debug window the skips where very high with 1080p
content so maybe that info can help.
If I can help any other way let me know.
Still hoping on a fix soon
@leurb: Can you confirm with your environment that the skip rate goes to 0 (means counter does not grow anymore) if you set the zoom amount to 0.9 and below when using full HD material (1920 x 1080 with NO (!!!) black bars at top and bottom? See
@JimKnopf: Yes I can confirm that that the skips rate does not grow anymore with the 0.9 Zoom amount.
I tested exactly as you mentioned with orgininal NO black bars.
Looks like a good point in the direction of the cause.
For now also a workaround to at last watch 1080 content.
I also can confirm that this is working. I finally have hope that my Vero 1 is still usefull. Don’t know how you came up with this solution, but THANKS! @sam_nazarko I presume that you are still working on a fix? Your original fix did nothing for me. Hopefully, this will help you figure out what is going on.