Hi guys,
after November update I’ve started to get a strange view on my Vero (multiple views of the vero, one right to another):
It happens after some time after restart. I’m using that once a day, so I don’t know exactly when.
Of course when I turn on debugging nothing happens.
Should I do something? Or just wait for December update?
Thanks
We haven’t seen any other reports of this problem, so it’s unlikely to get magically fixed if we’re not even aware of it.
Can you post a full debug log after the problem occurs ? What resolution and refresh rate is the screen set to ?
I’m first, wow!
Of course I can provide logs, but I need to find how to turn on debugging from shell and get the file from Vero, w/o sending it to cloud - as I can’t literally see anything with so many screens 
You can enable debug logging permanently but without the text on the screen using loglevel 1 in advancedsettings.xml:
http://kodi.wiki/view/Advancedsettings.xml#loglevel
Make sure you also go into Settings->System->Debugging and make sure that “component-specific logging” is turned off.
I would leave this in place until you see the problem happen. You can then upload all debug logs from an SSH command line using:
grab-logs -A
Do this without rebooting first.
The output of these two commands when the problem is present would also be useful:
cat /sys/class/graphics/fb0/modes
cat /sys/class/graphics/fb0/mode
Ok, I’ll do that, maybe today but if not I’ll do it tommorow.
all i see is the trakt addon popup a windows for you to rate what you just saw.
I guess you use that for the salts addon?
If the popup window for media rate bugs you go to the trakt addon, addon settings and disable rating
Problem is that I have several screens, not whats on them
Hi,
I’ve got this at least.
Unfortunaltey I’ve run OSMC too long and logs are to big to upload:
http://paste.osmc.io/{“message”:"Documentexceedsmaximumlength
I’ll try again
@DBMandrake I don’t know what happened, but today logs aren’t uploaded as well - the same problem. I’ve tried, after your guide if it works and it worked, but today it isn’t. I’ll restart and try again, but maybe there is another way to get logs from Vero?
Ok, I’ve got them:
logs
osmc@osmc:~$ cat /sys/class/graphics/fb0/modes
v:640x480p-60
d:1920x1080p-60
d:1280x720p-60
s:1920x1080i-60
s:720x480p-60
s:720x480p-60
s:1920x1080p-24
s:1920x1080p-30
U:1152x864p-60
S:1440x576i-50
S:1920x1080p-30
S:1920x1080p-25
S:1920x1080p-24
S:720x576p-50
S:720x480p-60
S:720x480p-60
S:1920x1080i-50
S:1920x1080i-60
S:1280x720p-50
S:1920x1080p-50
S:1280x1024p-60
V:1024x768p-60
V:800x600p-60
U:720x400p-70
D:1280x720p-60
D:1360x768p-60
D:1920x1080p-60
V:640x480p-60
And:
osmc@osmc:~$ cat /sys/class/graphics/fb0/mode
D:1920x1080p-60
I think, maybe the problem could be with changing resolution, because I didn’t setup 1080p for menu, I have only 720p. And when everything works results are as:
osmc@osmc:~$ cat /sys/class/graphics/fb0/mode
D:1280x720p-60
But the resolution change is automatic, as I’ve never changed that.
Hope that helps
@DBMandrake
If you want to drive the Vero in 720p, you can edit 1080p in uEnv.txt to 720p. This may rectify the issue
Sam
I could, but I’ve configured 720p in menu and before November update it worked fine. Now something is changing that, causing my problem with multiple screens.