I have always used Raspbmc so that I never shut down the machine. I just turn TV/amp off and then back on when I want to watch something. With raspbmc it took couple off minutes to get the signal from RPi (Model B). But now with Vero and OSMC it finds signal fast, but the resolution is 720x576@50Hz instead of 1920x1080@60Hz that I have defined in the settings. And the screen looks like this: https://pbs.twimg.com/media/CBH6QAfVAAAQKAg.jpg:large
It doesn’t even help to reboot. the signal is either the same of no signal at all. I haven’t yet figured out what makes the signal work again, but shutting down Vero, TV and amp in random order usually fixes it at some point.
Is this some common problem or is it just me?
I am having similar problems, sometimes the Vero changes to 640x480 or 720x576 when I switch the amp off and on, or turn the TV off and the projector on. Getting the full resolution options back requires rebooting everything a few times until it works again.
Is there a way to lock the Vero to a chosen video resolution output so it doesn’t get confused?
1 Like
Is there some temporary fix for this before sam gets this fixed for good?
Unfortunately the RC2 did not fix this issue. I still need to reboot the device ~10 times every single time I turn on the TV and would like to start watching something 
Do you have your resolution set to the first (default) choice at the top of the list in Kodi ?
If so you might have noticed that there will be another resolution choice in the list that is apparently the same resolution - usually at the bottom of the list. Have you tried that one ?
The reason for suggesting this is that the top item in the list has special meaning - it is the “boot” resolution, whatever that might be, as detected by the kernel during early boot by querying the TV’s “preferred/native” resolution using EDID.
If the TV is not providing that information at the time (turned off when the Vero boots) then it may end up switching into a weird mode as it won’t know what the TV’s preferred/native mode is.
However if you choose any other resolution from the list (including the “duplicate” one) then Kodi will always attempt to explicitly set this mode - and provided it’s available then it will use it.
One other possible complication is that if you are connecting to your TV via an HDMI AV receiver, when the receiver is turned off it may report different modes being available than when it is on, however choosing a resolution besides the top entry may help with this provided that resolution is still listed as a supported mode by the AV receiver when on standby.
Yeah, I had the resolution in the first option, but today I noticed the duplicate resolution there and selected that. No help. I have an AV receiver in between Vero and TV, but the same setup worked flawlessly with RPI1+Rasbmc.
I checked the selection again and it shows still the first 1920x1080p selected. If I select something else (for example 1280x720p) it changes the resolution and the selection stays there, but if I select the bottom 1920x1080p it changes the resolution, but when check the selection it is again the topmost 1920x1080p.
Most likely caused by: [package] [mediacenter-osmc] vero: re-enable all video modes · osmc/osmc@301f860 · GitHub
Are you able to post a debuglog, enable debugging, then reboot the machine and post the log?
I wasn’t sure which logs you meant, but I selected all: http://paste.osmc.io/ewuvudiqob
I hope someone can make you a kodi build with the other patch reverted and this added: http://sprunge.us/cNeH
Edit: Forgot a little continue 
which is also the above issue.
I am building a new Kodi build now with these changes and this should also improve some issues playing back video in software. As soon as we make it available publicly (post-testing) you’ll be able to get it via:
- My OSMC -> Updater -> Manual Controls -> Check for Updates
@fritsch: the reason that we added these modes explicitly is because on some DVI monitors I believe it was tricky to use slightly less ‘normal’ resolutions. @DBMandrake experienced this so I will be curious how he finds the build.
S
1 Like
Are you sure ?
There were two different changes made - one was to enable the S: modes, (patch above) the other was to avoid doing a mode switch if the current mode already matched the desired mode - I suspect it’s this latter change which causes the issue with 4:3 in default res, not enabling the extra modes. (Can’t seem to find that patch at the moment)
The S: mode patch was because on a DVI monitor many of the resolutions (including native) were not available, so Kodi would switch to the wrong mode.
For example on my 1680x1050 DVI monitor our kernel patches correctly detect and set 1680x1050 for early boot, but when kodi loads it would change res to 1280x1024 because 1680x1050 was an S: mode which was being filtered out. With S: modes enabled it would allow it to remain in 1680x1050 as well as switch to other supported S: modes.
BTW OpenElec has this same problem where Kodi cannot run in the native mode of a DVI monitor. (It also reverts to 1280x1024 on this monitor)
If access to /sys/class/graphics/fb0 is disabled so Kodi cannot change res, it will happily run in 1680x1050 as set up by the kernel.
Yes. Fully sure. The old code accepted only S: modes. See the ! in the condition. Now your users geht unwanted and double U: modes.
That’s why there are now multiple entries with same res. You can test to whitelist D: modes additionally. My patch preferes S: modes, but if non available falls back to D: and U:. This needs proper fixing, they are hidden for a reason.
Edit: Shitty internet (on train). Find out which Mode you need, e.g. if it’s a D Mode or a U Mode. Then merge the preferably D and S modes and only add those, you don’t already have. This way they will be usable without confusing users with multiple full hd modes.
Is there any documentation on what S: D: U: and V: stand for ? I’ve not been able to find any…
S: cae modes
V: vesa
D: digital?
U: user supplied e.g. altered by avr
I also found no docs. S: is what most users should need. D: for dvi users, but not doubled. The Rest only fallback. Can you implementiert that, it’ s not hard with the code I referenced. Curious on your merge though.
Get me also a cat of the modes file in sysfs please.
1 Like
I will capture the mode lists of the two PC monitors and TV I test the Vero on. Here is one, a
Hannspree XM-S 1440x900 HDMI PC monitor
osmc@vero:~$ cat /sys/class/graphics/fb0/modes
U:1280x720p-60
S:720x576p-50
S:720x480p-60
S:640x480p-60
S:720x576p-50
S:1280x720p-50
S:720x480p-60
S:1280x720p-60
V:640x480p-60
osmc@vero:~$ cat /sys/class/graphics/fb0/mode
U:1280x720p-60
The others I will get when I am home. I see duplicate S: modes on this monitor - that must be a kernel thing unrelated to the Kodi patch. Listed modes in Kodi:
1280x720p
640x480p
720x480p
720x576p
1280x720p
Kodi log:
11:51:59 T:1956503552 NOTICE: Initialize - graphics sysfs is writable
11:51:59 T:1956503552 NOTICE: Initialize - 32bpp: configure alpha blending
11:51:59 T:1956503552 NOTICE: InitWindowSystem: Using EGL Implementation: iMX
11:51:59 T:1956503552 NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 60.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 720 x 576 for display 0 with 720 x 576 @ 50.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 720 x 480 for display 0 with 720 x 480 @ 60.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 640 x 480 for display 0 with 640 x 480 @ 60.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 720 x 576 for display 0 with 720 x 576 @ 50.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 50.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 720 x 480 for display 0 with 720 x 480 @ 60.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 1280 x 720 for display 0 with 1280 x 720 @ 60.000000 Hz
11:51:59 T:1956503552 NOTICE: Found resolution 640 x 480 for display 0 with 640 x 480 @ 60.000000 Hz
11:51:59 T:1956503552 NOTICE: Found (1280x720@60.000000) at 23, setting to RES_DESKTOP at 16
11:51:59 T:1956503552 NOTICE: Checking resolution 16
11:52:00 T:1956503552 NOTICE: CreateWindow: Could not create a surface. Trying with a fresh Native Window.
Which S: is there twice? Yeah, want to See that other output. I See 50 and 60 Hz.
Look again 
S:720x576p-50 and S:720x480p-60 are both listed twice, both in /sys and in the kodi log.
Ah, the low ones. One should care for those. Problem is, when they really do sth else as D: and U: would. There is a different infernal kernel mode marching…
Edit: I will be away the complete week with limited internet access during “working hours”. If you read something really strange, this was the auto correction of my mobile phone 
“infernal kernel mode maraching” ← “internal kernel mode matching” 
@DBMandrake Can you please post the modes from your DVI device?
