OSMC broken after TV being off

This has always been the case, at least for me. Rebooting has always fixed the problem. But it’s incredibly annoying to reboot every time you want to watch something…
Another thing that works is shifting to 720p before you turn off. Then, when you turn back on, the 720p signal is just fine. But if you want 1080p, you have to change your settings every single time and remember to change them back to 720p before you turn off your TV. Just a little bit less annoying than rebooting…

Guys, please provide proper debug logs and explain EXACTLY what you are doing and what is going wrong.

As far as we were aware the most recent updates should have fixed the mode setting issues on the Vero so if there are still some problems we need to know about them and with as much useful detail as possible. We can only fix problems we’re aware of that are properly documented.

Thanks.

I was a bit hasty with the previous post. It is sometimes still the same as before, but not every time.

I have two example cases, in both I got the broken 720p signal after tv and amp being off:

  1. I gor the appropriate 1080p signal immediatelly after reboot, logs here: http://paste.osmc.io/liluhodequ
  2. I got no signal after reboot and left tv there, 7 minutes later TV received the signal wit studder and colorful noise distortion, logs here: http://paste.osmc.io/liluhodequ I this case the logs last timestamp is the time of the reboot, so there is no logs about the signal recovering. EDIT: oh there is!

I have noticed that it doesn’t help to reboot it multiple times. I just have to leave it there when there is no signal and it is recovered in 5-10 minutes. If I get the broken signal, it won’t recover.

DBMandrake - The situation is this:
My TV+Receiver are connected to the Vero via HDMI. No control or anything. TV is connected to the receiver, and the receiver to the Vero. The TV is 1080p capable and so this is the setting on the Vero. When I turn the TV+receiver off and then back on, the signal from the Vero is completely garbled. It seems like the signal has also changed to 480p. At this point, it’s nearly impossible to do anything via software (including generate a debug log) as you can’t really see what’s going on in the screen. The only real option is to unplug the Vero and then plug it back in. If I do that (with the TV+receiver on), OSMC will come back up fine, in 1080p.
Additional comments:

  1. I have made sure that I update the OSMC daily and have also manually updated every single time via the little utility.
  2. When I go into the resolution settings, I see 1080p twice - Once on the top of the list and once towards the bottom of the list (recently a 1080i was added to the list below it). I’ve tried using both settings but neither solves the problem.
  3. If before I turn off the TV+receiver I go into the resolution settings and convert to 720p, then turn off the TV+receiver, then the next time I turn them back on the screen comes up fine (in 720p of course). I can then go into settings and convert to 1080p, but if I don’t convert back to 720p before I turn off the problem reappears.

When would you like me to generate the debug logs? Obviously I can’t do it when the problem actually occurs because the screen is completely garbled. Will a debug log after the forced off/on help?

I received my vero last week. I have the exact same issue, to the letter, as yrvero. I did not have this on raspbmc which the vero is replacing.

Just wondering if this is still being looked at? I can try and ssh into the vero tomorrow to get the logs if it would be helpful and someone can provide the relevant instructions. I can’t get these through the front end as it is impossible to navigate.

@DBMandrake @sam_nazarko Hi Guys, any update on this? Anything I can help you with regarding logs? One additional thing to add is if I play a movie the resolution returns to 1080p. I have the change resolution to match movie setting to on so that makes sense to me and is easier than rebooting the device each time I want to use it. Still don’t understand why the Vero won’t hold the last good resolution even when no display device is active.

Hi

Are you up to date? My understanding is we squashed this a while ago. As an aside, I am also looking at adding an option to force EDIDs, so it should be possible in the near future to just force a 1080p output permanently.

Sam

@sam_nazarko hi, yes I am up to date but the same issue is still occurring. I’d be interested in the edid fix to force the resolution to 1080p.

I am on holiday at the moment, so I can only work for a couple of hours a day and even then do not have access to all my equipment.

Sam

@sam_nazarko no problem, enjoy your holiday.

hi. i am also up to date. i do so religiously as this issue is driving me crazy. the best workaround i’ve found so far is: before i turn my tv off, i go into vero’s settings and change the resolution to 720p; then, when i turn the TV back on, i go into vero’s settings again and turn the resolution back to 1080p. not fun! it also means that my wife just can’t use the vero…
the issue is most definitely not “squashed”.

@sam_nazarko Hi Sam - any update on this? I updated OSMC yesterday but this still isn’t resolved.

@sam_nazarko Hi Sam - any update on this? The Vero reverting to 720p as the default resolution is becoming a pain.

I have only got back from holiday yesterday

Sam

@sam_nazarko my apologies Sam I thought you were away for only a week.

@sam_nazarko any news on this?

This has been fixed, it will come with the Isengard update.

Sam

@sam_nazarko many thanks!

Hi there, I waited a while before participating in this discussion because I hoped the problem eventually would be solved. Unfortunately… after upgrading to the latest software this morning the problem (as described by yrvero perfectly) still exists. Could you please dig a little deeper into this and solve this once and for all? It’s so annoying to pay a fair amount of money for a device that’s not working properly. Every time you want to use it, you first have to reset it. That couldn’t be right.

Many, many thnx!

We have not released the update that fixes this issue yet.

Stay tuned

Sam