Bug: U4s change screen size depending on boot order (T2 doesn’t).

[sub3R]

Our Panasonic TX-32LXD600A TV doesn’t have the facility to change overscan or screen position/size, so this has always had to be adjusted on the T2. This has worked flawlessly on the T2 irrespective of which device was turned on first (the T2 or the TV).

With either of our two U4s, the screen position overscans if the U4 is turned on before the TV, but displays correctly if the TV is turned on before the U4.

If the U4 is turned on before the TV (which can happen if the U4 wakes up from deep standby to timer record), the display can be corrected by toggling back & forth once of either the ‘Move Left/Right’ or the ‘Move Up/Down’ in ‘Setup > AV setup > OSD position’. This gives a large jump in the screen displayed on the TV & corrects the displayed position & size.

Note that the OSD Position settings in ‘Setup > AV setup > OSD position’ always show my same modified settings irrespective if the TV or the U4 is started first. The U4 just doesn’t seem to take any notice to these if the U4 is started up before the TV.

The OSD & Video settings on the T2 & both U4s are identical:

• T2 or U4 connected directly to the TV via HDMI.
• Video output: 720p 50Hz.
• Display 4:3 content as: Pillarbox.
• Display >16:9 content as: Just Scan.
• OSD Position: User interface visibility: 255, Move Left/Right: 18, Width: 684, Move Up/Down: 13, Height: 548.

The U4 has had the above bug with 17.5 20190207 f/w, 19.3 20190630 f/w, 19.3 20190704 f/w & 19.3 20190706 f/w. So the bug didn’t just appear in 19.3 series f/w, it was also in the 17.5 20190207 f/w.

The T2 has worked flawlessly in regards to the above OSD with all 17.5 series f/w from 17.5 20180417 f/w through to 19.3 20190630 f/w & also 19.3 20190706 f/w.

I have attached two screen captures; one with the correct OSD using OWIF & one with the incorrect OSD. Unfortunately OWIF doesn’t show the incorrect different screen size when the U4 boots before the TV (it shows the correct size), so I took a photos with a camera & attached the reduced size image.

The images are with the U4 running OverlayHD 1.70 skin. The easy-skin-au-hd skin also shows the wrong size OSD when the U4 boots before the TV, but it isn’t as noticeable as OverlayHD (it shows it mainly with some letters cut off on the RHS).

I have attached three log files that were downloaded after the following:

• U4 booted from deep standby. TV switched on. Media List opened to verify the incorrect OSD. Exited from Media List. Cancelled on-line f/w update popup. In Setup corrected the OSD by toggling Move Left/Right in OSD Settings. Exited then opened Media List to confirm it showed the correct OSD.

The U4 was running 19.3 20190706 f/w in all the above test results with OverlayHD 1.70. The second newer U4 was also tested on this TV with that f/w version.

The U4 waking up from deep standby to record, then later turning the TV on to use the U4 while it is still recording is when this bug is most inconvenient. Note that the T2 doesn't have this bug.

U4 with correct OSD

U4_02_OSD-correct_Pana-TV.jpg (429.98 KiB) Viewed 1138 times

U4 with incorrect OSD

U4_02_OSD-incorrect_Pana-TV.jpg (465.46 KiB) Viewed 1138 times

Enigma2-2019-07-08_14-20-11.log

(61.08 KiB) Downloaded 49 times

messages.txt

(48.22 KiB) Downloaded 39 times

dmesg.txt

(23.42 KiB) Downloaded 36 times

[prl]

I have seen this happen on my test U4, which sometimes gets turned on before the TV is turned on. The TV overscan always on, and can't be removed.

I never got annoyed with it enough to investigate it properly.

[Grumpy_Geoff]

This has been brought up previously. If I remember correctly, it's a "tough titties" situation with the HDMI (re-)negotiation.
On the U4, I just press TV-OUT about 8 times to cycle back to the required resolution.
On the T4, I adjust via a resolution change, reply to "no, it's shite" and then voilà it's back correct.
It's roughly the same number of key presses either way.

[sub3R]

I have seen this happen on my test U4, which sometimes gets turned on before the TV is turned on. ...

Thanks for confirming. At least I know it isn’t a setting I’ve changed in the U4s.

If the U4 hasn’t turned on to timer record we’ve got in the habit of turning the TV on first.

Whatever triggers it happens very early in the U4 boot stage. If I turn on the U4 & then immediately turn on the TV I still get the OSD issue. The TV definitely has to beat the U4.

[sub3R]

On the U4, I just press TV-OUT about 8 times to cycle back to the required resolution.
On the T4, I adjust via a resolution change, reply to "no, it's shite" and then voilà it's back correct.

So you get it on the T4 as well?

Have you seen it happen on your T2? I haven't on ours.

If you haven't I would just like our U4 to work like the T2 does. That is, to negotiate correctly.

[prl]

On the U4, I just press TV-OUT about 8 times to cycle back to the required resolution.
On the T4, I adjust via a resolution change, reply to "no, it's shite" and then voilà it's back correct.

So you get it on the T4 as well?

I think I've seen it on my test T4, too. I fpn't think I've ever seen it on our in-use T4, but it's always turned on the same way using our Harmony.

[Grumpy_Geoff]

On the U4, I just press TV-OUT about 8 times to cycle back to the required resolution.
On the T4, I adjust via a resolution change, reply to "no, it's shite" and then voilà it's back correct.

So you get it on the T4 as well?

Have you seen it happen on your T2? I haven't on ours.

If you haven't I would just like our U4 to work like the T2 does. That is, to negotiate correctly.

Yep, the T4 and U4 are attached to the same tele (the next series from yours, a TX-32LXD700). The T2 is attached to a full-HD tele.
Lots of discussion in the first two pages and also in a couple of links from it - viewtopic.php?f=56&t=12441

[sub3R]

Thanks Peter & Geoff. From the link that you posted Geoff, & the links from that, there seemed to be resolution & OSD issues over HDMI with some of the T2, T4 & U4 Wizzes.

I must be missing something in all that I’ve read. Our 32” Pana TV only has one HDMI input connected & that is from the U4. If the TV started before the U4 & the OSD then incorrectly changed I could understand that, but not the other way round like it is doing.

When I get some time I’ll try some settings at 1080í with the OSD adjusted for that & see what happens. But I think I have tried that in the past.

Assuming our T2 is doing the correct thing, unless it is a driver creating the issue on the U4/TV combination, could that part of the f/w be incorrect on the U4?

I also wonder if having an EDID check enable/disable option would overcome the issue I have with the U4.