No. I primarily used 1080p for the Home UI resolution. I think I only switched to 2160p upon upgrade after noticing that the 1080p resolution kept oversizing in the Home UI.
Ok, bit strange but still oversizing is a problem of a wrong TV setting (assuming that you have reset all calibration settings in OSMC).
BTW, just tried here to set 4k GUI and it remains set after playing movies and also after reboot.
You still need to share the URL of the log upload if you want someone to figure out why it switches to 1080p.
If I reboot Vero 4K, the sizing is fine. It’s when I switch on my TV & AVR that it doesn’t. I’ve just set my CEC setting to put the Vero in ‘Standby’ when powering off the TV. That seems to fix it.
How can I share the log URL privately as I presume it will include my share details which has passphrases?
Click on the name here and you should see a Message button.
Passphrases should normally be given in a separate file to avoid them being part of the shared info.
Hi Sam,
I think, we talk about the different add-on. The One I ment is following kodi-pvr/pvr.vuplus: Kodi’s VuPlus client addon (github.com) . They are continuosly working on Kodi binary repo.
With the beta releases, I’ve noticed a recurring pattern where the Vero 4K+ box not outputting video signals/sync to the TV via connection through the sound bar when playing 4K content with resolution and frame rate matching enabled (i.e. movie playback begins, no video on TV, sound coming out of the sound bar).
A temporary “solution” is to stop and re-start playback to regain video output, which can usually take 2-5 tries before successful.
The issue sometime goes away with an a new testing release but will usually regress with the subsequent update - In this case the most recent update have made the issue more persistent than the release prior.
Hopefully this debug log is helpful - This 4K movie took a few tries before it started playing properly on the last try.
I think my latest tweaks have made it to the current build. Please check the OSD brightness. It ought not to be very different but I have also added some adjustment, using the new display maximum luminance setting in Settings->System->Display. On my LED Panasonic that setting doesn’t make much difference but I’d be interested in what you find on a better TV.
I can’t test HDR10+. Maybe @fzinken can check?
Thanks, looks good!
1 Like
Currently doing some minor remodeling om my Home theater.
Will let you know later tonight or tomorrow 
1 Like
I am not simenh1 but to me the OSD brightness incl subtitles is now at a much more comfortable level when playing HDR10 material. I use a LG OLED CX.
Although I don’t see much difference between the luminance values (found in settings) in HDR content, is that expected?
Am I right in that this setting will not affect SDR content?
Just to know what to look for.
TBH, I’m not sure what to expect. I just threw that in to get some feedback, so thank you for that. According to my maths, you should see a difference.
That setting doesn’t affect SDR content. It does affect HDR-SDR tonemapping - I just re-used the control on the assumption those with HDR displays would not be needing HDR-SDR conversion 
OK, cool.
I tried switching between the extremes (50/350) but nothing notable happened.
Could try messing with it more when I have less ambient lighting going on.
I see. I’ll focus on the HDR side.
You have to stop/start the video to get any difference. It doesn’t take effect on the fly.
That’s what I did. It was quite tedious
I know I sound like a choosing beggar but would it be possible to get 2 subtitle color selections? SDR/HDR?
It’s a struggle to get it looking right when switching between content.
The skinning engine doesn’t have anything to do with the subtitles, I’m afraid. 
I’ve given this some more thought and my logic was somewhat flawed.
I think what we (me?) are trying to accomplish with a setting that can adjust the HDR (overlay?) brightness should get the same desired effect as 2 subtitle colors IMO.
If the brightness between SDR/HDR can be matched the OSD/subtitles should look near identical between the modes.
What I now have noticed (on my setup) is that the issue is now inversed. HDR OSD is now dimmer than SDR. E.g. subtitles with same color now appears darker on HDR despite changing the available setting.
So while this is a big improvement it swings a bit too much the other way.
I think the available user setting is important in this case since this probably will vary between displays.
[EDIT]
The above obviously doesn’t apply if people would like i.e. Yellow for SDR and Blue for HDR.
Well I’ll be damned.
The Vero4K crashed waking up from a screensaver so I rebooted it.
Now SDR/HDR OSD/subtitles has a very similar brightness level between modes.
Currently at the maximum 350 setting.
Sorry for the feedback spam.
Should we have problems executing armV6 code? I had no issues with this with kernel 3.14
root@90c5694f58fa:/AirConnect/bin# ./airupnp-arm-static -h
Illegal instruction (core dumped)
root@90c5694f58fa:/AirConnect/bin# readelf -A airupnp-arm-static
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "6J"
Tag_CPU_arch: v6
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-1
Tag_FP_arch: VFPv2
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_rounding: Needed
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_HardFP_use: Deprecated
Tag_ABI_VFP_args: VFP registers
Tag_CPU_unaligned_access: v6
root@90c5694f58fa:/AirConnect/bin# readelf -A /usr/bin/readelf
Attribute Section: aeabi
File Attributes
Tag_CPU_name: "7-A"
Tag_CPU_arch: v7
Tag_CPU_arch_profile: Application
Tag_ARM_ISA_use: Yes
Tag_THUMB_ISA_use: Thumb-2
Tag_FP_arch: VFPv3-D16
Tag_ABI_PCS_wchar_t: 4
Tag_ABI_FP_rounding: Needed
Tag_ABI_FP_denormal: Needed
Tag_ABI_FP_exceptions: Needed
Tag_ABI_FP_number_model: IEEE 754
Tag_ABI_align_needed: 8-byte
Tag_ABI_enum_size: int
Tag_ABI_VFP_args: VFP registers
Tag_ABI_optimization_goals: Aggressive Size
Tag_CPU_unaligned_access: v6