Firmware 19.3_20211010 update discussion

old timer · Post by **old timer** » Mon Dec 20, 2021 15:28

Thanks for the prompt reply Peter.
I agree and understand your reply. In the standby mode there are two ways of turning the clock off.
1. Brightness Standny slider to off or
2. Switch Show in Standby Clock/Nothing to Nothing.
But there seems to be no way to have a Led (colour selectable) on alone in Standby to let you know that the V2 actually has power connected and in Standby mode if you don't want the clock visable.
The Front Panel is completely dark and you have to go to the machine and peer into the top slats to see some internal Leds to check if the power is connected. As you suggest possibly a bug.
Thanks for your help.

prl · Post by **prl** » Mon Dec 20, 2021 15:39

old timer wrote: ↑
Mon Dec 20, 2021 15:28
2. Switch Show in Standby Clock/Nothing to Nothing.

Do you mean "Display state in standby"? Otherwise I'm not sure what you mean.

old timer wrote: ↑
Mon Dec 20, 2021 15:28
But there seems to be no way to have a Led (colour selectable) on alone in Standby to let you know that the V2 actually has power connected and in Standby mode if you don't want the clock visible.
The Front Panel is completely dark and you have to go to the machine and peer into the top slats to see some internal Leds to check if the power is connected.

If I set "Brightness (Standby)" down to zero (no bar showing), and set "LED state in standby" to, say, "violet" (the default), then in standby, the 4-digit 7-segment display is off, and the power button LED is on and violet (its physical red and blue LEDs are both on).

old timer wrote: ↑
Mon Dec 20, 2021 15:28
As you suggest possibly a bug.

The only bug I mentioned is that the "LED state in standby" setting seems to have no effect.

old timer wrote: ↑
Mon Dec 20, 2021 15:28
Thanks for your help.

No problem

DaveJ · Post by **DaveJ** » Mon Dec 20, 2021 16:22

Hi all. Long time user/lurker - very infrequent poster.

Just advising my T4 announced there were updates available ... And I've today allowed the machine to do them. All's well.

More detail:
Networked T4. I'm on the "Public release", not in beta releases. Despite the displayed caution about it being a big update and "ya orta use a USB", I set the auto download/update going. It ran it's course and after a bit with the closing reboot ... it all worked exactly as it should and exactly how one hopes things will go.

At a brief lookie, I see a few minor interface things changed already - and a few new channel icons/titles added, have not yet seen anything fail. All timers, settings, etc carried through. Good to notice the optional add-ins were also sorted automatically (like the EPG refresh). I'm sure there's lots under the hood" altered too.

Thanks all - for me it was a smooth and pretty painless update.

serpeantoz · Post by **serpeantoz** » Mon Dec 20, 2021 18:22

I can't see my NAS drive after this update.

Can someone remind me how to find the settings on the Mount Editor? Is this on the PC or the Beyonwiz? I can't remember how I did this before?

I think I need too delete the "vers=2.1" in "Mount options: rw,utf8,vers=2.1"

MrQuade · Post by **MrQuade** » Mon Dec 20, 2021 19:53

serpeantoz wrote: ↑
Mon Dec 20, 2021 18:22
Can someone remind me how to find the settings on the Mount Editor? Is this on the PC or the Beyonwiz? I can't remember how I did this before?

It's on the Wiz.
MENU->Setup->Network->Mount Manager->Mountpoints management

Then select your NAS mount.

serpeantoz wrote: ↑
Mon Dec 20, 2021 18:22
I think I need too delete the "vers=2.1" in "Mount options: rw,utf8,vers=2.1"

Maybe. The new mount system will automatically use the highest SMB protocol version that the Wiz model supports.
You want to change the "SMB protocol version option". If your NAS is an old one, then you would want to set that to "1.0".
Leave the "options" field alone if it doesn't already have vers=2.1 in it.

netmask · Post by **netmask** » Tue Dec 21, 2021 15:56

MrQuade wrote: ↑
Mon Dec 20, 2021 15:04

netmask wrote: ↑
Mon Dec 20, 2021 14:54
Maybe Beyonwiz should supply a small piece of neutral density film to glue over it.
I ordered some of these off Amazon:
https://www.lightdims.com/index.php

Great bit of info - I've forwarded it onto a friend who does equipment service. But as this seems to be a universal gripe one would think design engineers would find a more elegant solution rather than "retina burning bright, extremely bright and "still painful" or Off.

Agropyron · Post by **Agropyron** » Wed Dec 22, 2021 06:53

netmask wrote: ↑
Tue Dec 21, 2021 15:56

MrQuade wrote: ↑
Mon Dec 20, 2021 15:04

netmask wrote: ↑
Mon Dec 20, 2021 14:54
Maybe Beyonwiz should supply a small piece of neutral density film to glue over it.
I ordered some of these off Amazon:
https://www.lightdims.com/index.php
Great bit of info - I've forwarded it onto a friend who does equipment service. But as this seems to be a universal gripe one would think design engineers would find a more elegant solution rather than "retina burning bright, extremely bright and "still painful" or Off.

I've been using LightDims for some years and have found them excellent for dimming annoyingly bright LEDs on clocks, other LED displays, powerboards, etc. The film is easy to apply, adjust and remove although it becomes a bit dog-eared at the corners when you peel it off to adjust it. They even produce small 'dots' for application to single LEDs such as on powerboards. The only thing I haven't used it on is my V2 as it's in a TV stand behind smoked glass doors.

Thanks to all for the excellent advice and recommendations on flashing the firmware - thanks to this and the how-to video, the firmware on my V2 upgraded via USB without a hitch.

BigbobOz · Post by **BigbobOz** » Wed Dec 22, 2021 17:56

serpeantoz wrote: ↑
Mon Dec 20, 2021 18:22
I can't see my NAS drive after this update.

Interesting, I can see my NAS drive but not my T4. I can see it when browsing for network mounts but it fails to connect. Any suggestions anyone?

2nd issue, I can't get the timeshift to work on my SD card. Not gone well for me.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Wed Dec 22, 2021 18:14

BigbobOz wrote: ↑
Wed Dec 22, 2021 17:56

serpeantoz wrote: ↑
Mon Dec 20, 2021 18:22
I can't see my NAS drive after this update.
Interesting, I can see my NAS drive but not my T4. I can see it when browsing for network mounts but it fails to connect. Any suggestions anyone?

2nd issue, I can't get the timeshift to work on my SD card. Not gone well for me.

What are the Mount options for the T4's mount?

What is specified for timeshift location in MENU>>Setup>>TV>>Timeshift settings?

BigbobOz · Post by **BigbobOz** » Thu Dec 23, 2021 19:21

T4 connectin most urgent:
Mount using <FSTAB (mount at boot)>
Active <yes>
Server IP <unchanged and I can connect via samba on windows to this IP address>
Server share <Movie>
Use as HDD replacement <Yes>
Mount options <rw,utf8>
SMB protocol version default
Username <guest>
Password <blank>

The T4 shows up in the mount browser, just doesn't connect...

Since yesterday, the T4 now shows up under dlna

Grumpy_Geoff · Post by **Grumpy_Geoff** » Thu Dec 23, 2021 19:31

BigbobOz wrote: ↑
Thu Dec 23, 2021 19:21
Mount using <FSTAB (mount at boot)>
Use as HDD replacement <Yes>

Change those to -
AUTOFS (mount as needed)
Disable "Use as HDD replacement"

edit -
Oh wait, you're using the T4 as a recording destination.
I'm not sure prl got the "Use as HDD replacement" changes working to his satisfaction.
Perhaps change the MENU>>Setup>>TV>>Recording settings>>Default movie location to /media/autofs/{T4_share_name}, with Timer and Instant recordings locations at their <Default movie location> defaults.

MrQuade · Post by **MrQuade** » Thu Dec 23, 2021 20:43

Grumpy_Geoff wrote: ↑
Thu Dec 23, 2021 19:31

Change those to -
AUTOFS (mount as needed)
Disable "Use as HDD replacement"

Better to delete the old mount and recreate it fresh if switching between fstab and autofs.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Thu Dec 23, 2021 23:03

MrQuade wrote: ↑
Thu Dec 23, 2021 20:43

Grumpy_Geoff wrote: ↑
Thu Dec 23, 2021 19:31

Change those to -
AUTOFS (mount as needed)
Disable "Use as HDD replacement"

Better to delete the old mount and recreate it fresh if switching between fstab and autofs.

Oh yes, that's right, I'd forgotten about that.

prl · Post by **prl** » Fri Dec 24, 2021 09:54

Grumpy_Geoff wrote: ↑
Thu Dec 23, 2021 23:03

MrQuade wrote: ↑
Thu Dec 23, 2021 20:43

Grumpy_Geoff wrote: ↑
Thu Dec 23, 2021 19:31

Change those to -
AUTOFS (mount as needed)
Disable "Use as HDD replacement"

Better to delete the old mount and recreate it fresh if switching between fstab and autofs.

Oh yes, that's right, I'd forgotten about that.

That was part of what I was working on. None of that work has made it into the firmware yet. The mount manager is still pretty flaky. And definitely delete/rebuild a mount if you want to turn "Use as HDD replacement" on (or off). Also delete/remake for any other things that change the mountpoint name.

Minibus · Post by **Minibus** » Fri Dec 24, 2021 18:16

On my V2 unfortunately I too have been struck down by SMB Fails after upgrading,

The OS says it created the CIFS Mountpoint, they have a Green/blue Circle but when I try to go to the location the error reads
'/media/autofs/{Location name}' does not exist,
when I look in the 'Wiz through Filezilla, the directories exist, contains folders for the two discrete locations,
I Create two separate mount-points for subfolders on my SMB1 only Dlink Nas....

anyway, the folders are empty in the structure of the 'Wiz.

Prior to 19.2 this was working and I had access to the content, but now no matter how hard I've tried I cannot get the mount-points to work.

The real question is where are the rest of the mount-point information kept in the file structure, I'm looking to completely remove the previous info held by the V2 to see if this helps restore mount-point issues for me.

any assistance here is greatly appreciated in advance.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Dec 24, 2021 18:28

Minibus wrote: ↑
Fri Dec 24, 2021 18:16
Prior to 19.2 this was working and I had access to the content, but now no matter how hard I've tried I cannot get the mount-points to work.

The real question is where are the rest of the mount-point information kept in the file structure, I'm looking to completely remove the previous info held by the V2 to see if this helps restore mount-point issues for me.

The GUI uses /etc/enigma2/automounts.xml, and writes the data to /etc/auto.network (which is used for the mount).

You may need to add a ,vers=1.0 to the SMB1 mount definition.

MrQuade · Post by **MrQuade** » Fri Dec 24, 2021 18:40

Grumpy_Geoff wrote: ↑
Fri Dec 24, 2021 18:28
You may need to add a ,vers=1.0 to the SMB1 mount definition.

Or from the GUI interface, there is a SMB version parameter that can be set to "1.0".

I agree that this is the most likely issue.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Dec 24, 2021 20:08

MrQuade wrote: ↑
Fri Dec 24, 2021 18:40

Grumpy_Geoff wrote: ↑
Fri Dec 24, 2021 18:28
You may need to add a ,vers=1.0 to the SMB1 mount definition.
Or from the GUI interface, there is a SMB version parameter that can be set to "1.0".

Ah yes, the new "SMB protocol version" setting.

Minibus · Post by **Minibus** » Sat Dec 25, 2021 00:03

Thanks for the prompt responses.. when I get a chance after the fatman will probably have another go,using the above

Minibus · Post by **Minibus** » Sat Dec 25, 2021 00:10

Thanks for the prompt responses.. when I get a chance after the fatman will probably have another go,using the above. I did try using ver=1 and vers=1 but not 1.0....

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sat Dec 25, 2021 00:22

Minibus wrote: ↑
Sat Dec 25, 2021 00:10
I did try using ver=1 and vers=1 but not 1.0....

Yes, "1.0" ¬= "1"

MrQuade · Post by **MrQuade** » Sat Dec 25, 2021 01:27

Minibus wrote: ↑
Sat Dec 25, 2021 00:10
I did try using ver=1 and vers=1 but not 1.0....

Don't worry about the "options" field. Delete the vers= from there, and use the "SMB protocol version" option to select either 1.0 or 2.1 as required by your NAS.

Minibus · Post by **Minibus** » Sun Dec 26, 2021 19:07

Gents I Humbly accept all suggestions, I have had success by setting the version portion as "vers=1.0" and it came straight up, no more mucking about.
The Green Dot stayed green...

The biggest key for everyone else that has the same or similar problem, is how quickly the Updating of the Mount-Point is completed, It will inevitably fail if the Notification countdown timer starts at 8 seconds, and if it takes nearly a full second starting the countdown at 9 (no I didn't time it) to come up after updating the Mount-point it will also fail.

But if the notification of completion is almost instant then it will work, and this is consistent with my historical experience when I had trouble with the mountpoint at the start-up of the V2. I don't remember who I spoke to in Beyonwiz on the helpdesk when I had this trouble, but they understood the SMB Version basic setting of 2.1 was the issue, and when this happened again I thought it would be the same fix, but well a new version and new rules.

Thanks again for your help getting this back and working again for me!

carljh · Post by **carljh** » Mon Dec 27, 2021 11:13

Since installing this latest firmware, the front display stays on all the time on my V2 even though in the settings I have it set to off as it always has been. I also have to turn the blue power light off manually to put it into standby. Anyone else struck this problem? I tried setting it to on but made no difference.

MrQuade · Post by **MrQuade** » Mon Dec 27, 2021 11:43

carljh wrote: ↑
Mon Dec 27, 2021 11:13
Since installing this latest firmware, the front display stays on all the time on my V2 even though in the settings I have it set to off as it always has been. I also have to turn the blue power light off manually to put it into standby. Anyone else struck this problem? I tried setting it to on but made no difference.

This has been mentioned earlier in this thread, and on Whirlpool. It looks like it is a bug. On the Whirlpool thread, prl mentions that he's dug into the code a little, and there doesn't seem to be anything wrong in the open source bits.

I know that in the past, adoxa has woven some magic code to work around weird behaviour on the front panel over the last two years of the beta. This might be a leftover side effect...

In the meantime, prl has suggested trying a backlight level of 0 to work around this.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Dec 27, 2021 11:57

carljh wrote: ↑
Mon Dec 27, 2021 11:13
Since installing this latest firmware, the front display stays on all the time on my V2 even though in the settings I have it set to off as it always has been.

Try disabling the "Use LED for power & recording" setting.

carljh wrote: ↑
Mon Dec 27, 2021 11:13
I also have to turn the blue power light off manually to put it into standby. Anyone else struck this problem? I tried setting it to on but made no difference.

I don't understand the issue, can you explain this a bit more?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Dec 27, 2021 12:05

MrQuade wrote: ↑
Mon Dec 27, 2021 11:43

carljh wrote: ↑
Mon Dec 27, 2021 11:13
Since installing this latest firmware, the front display stays on all the time on my V2 even though in the settings I have it set to off as it always has been. I also have to turn the blue power light off manually to put it into standby. Anyone else struck this problem? I tried setting it to on but made no difference.
This has been mentioned earlier in this thread, and on Whirlpool. It looks like it is a bug. On the Whirlpool thread, prl mentions that he's dug into the code a little, and there doesn't seem to be anything wrong in the open source bits.

I'm not sure if it's the same thing, but I can have the display off and LED showing as violet in standby -
LED state in standby = violet
Show in standby = Nothing

netmask · Post by **netmask** » Mon Dec 27, 2021 13:59

Same here. In standby purple light is on even though it was off before firmware update.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Dec 27, 2021 14:34

netmask wrote: ↑
Mon Dec 27, 2021 13:59
Same here. In standby purple light is on even though it was off before firmware update.

If I set "LED state in standby = off" then I can get nothing at all showing in standby (with Show in standby = Nothing) -
"LED state in standby"
"Choose the standby LED colour or turn it off."

BigbobOz · Post by **BigbobOz** » Mon Dec 27, 2021 15:28

prl wrote: ↑
Fri Dec 24, 2021 09:54

That was part of what I was working on. None of that work has made it into the firmware yet. The mount manager is still pretty flaky. And definitely delete/rebuild a mount if you want to turn "Use as HDD replacement" on (or off). Also delete/remake for any other things that change the mountpoint name.

Thanks all but still no joy. Have tried (deleting the original each time):
1. network browser
- when browsing it shows "Movie" but has a red cross - is this right?
- Should it be SMB via the network browser? Adding manually, the options are CIFS or NFS
2. Manually adding
- AUTOFS (mounted as needed)
- Mounting manually removes the red cross but I still can't connect
- have tried movie, media, hdd and various permutations for the server parth

DLNA works but isn't ideal as I can't record from the V2 to the T4

Any other suggestions?
Thanks,
Rob

prl · Post by **prl** » Mon Dec 27, 2021 15:34

Grumpy_Geoff wrote: ↑
Mon Dec 27, 2021 14:34

netmask wrote: ↑
Mon Dec 27, 2021 13:59
Same here. In standby purple light is on even though it was off before firmware update.

If I set "LED state in standby = off" then I can get nothing at all showing in standby (with Show in standby = Nothing) -
"LED state in standby"
"Choose the standby LED colour or turn it off."

To have the front panel off in standby, either:
Set "Brightness (Standby)" to 0 (no white bar showing) (and the settings "Display state in standby" and "Show in standby" are irrelevant),
or set "Display state in standby" to "on" and "Show in standby" to "Nothing" (and then the "Brightness (Standby)" setting is irrelevant).

The description text for the "Display state in standby" setting, "Choose to have no display in standby" is pretty much wrong: at best it's highly misleading.

The default for "Display state in standby" is "off", and the default for "Show in standby" is "Time". The front panel display is off in standby if "Show in standby" is "Nothing", independent of whether "Display state in standby" is "off" or "on", but, "Show in standby" can only be changed if "Display state in standby" is "on".

Is that all confusing enough for everybody?

The code that handles this was last changed in June 2019, and so should be unchanged since the previous official firmware (20191106).

The power button LED colour can be set to "off" for all of running, standby and shutdown in the "LED state ..." settings.

Some of the differences in behaviour from the previous versions that users were using ("different from what it was before I updated" isn't all that helpful a description if anyone wants an explanation of the changes) may be because a user has done a USB update and then manually re-done their settings, but hasn't made the necessary changes to the front panel settings, or have done a USB update and restored quite old settings (which is pretty much never a good idea).

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Dec 27, 2021 16:22

BigbobOz wrote: ↑
Mon Dec 27, 2021 15:28
Thanks all but still no joy. Have tried (deleting the original each time):
1. network browser
- when browsing it shows "Movie" but has a red cross - is this right?
- Should it be SMB via the network browser? Adding manually, the options are CIFS or NFS
2. Manually adding
- AUTOFS (mounted as needed)
- Mounting manually removes the red cross but I still can't connect
- have tried movie, media, hdd and various permutations for the server parth

Here's what I have on our V2 for the "Movie" share from the T4 -

Code: Select all

root@beyonwizv2:~# grep T4 /etc/auto.network
T4_Movie -fstype=cifs,user=guest,pass=,rw,iocharset=utf8,cache=loose ://192.168.1.62/Movie
root@beyonwizv2:~#

... so (i) Mount using AUTOFS, (ii) SMB protocol version = default

Note there were occasions where some of my mounts had to be specified as FSTAB to work; but I've not needed that for a long time now.

BigbobOz · Post by **BigbobOz** » Thu Dec 30, 2021 22:53

Ok reporting back on what worked after trying a million different things.

Changing Samba to 1 from default fixed my problem. There only seems to be two Samba options 1 or 2.1, so no idea what default is, as my Synology needs 2.1 to work and the T4 1, soooo what is default!?

Thanks for the suggestions on how to fix, hope this helps someone else.

Thanks,
Rob

MrQuade · Post by **MrQuade** » Fri Dec 31, 2021 13:46

BigbobOz wrote: ↑
Thu Dec 30, 2021 22:53
Ok reporting back on what worked after trying a million different things.

Changing Samba to 1 from default fixed my problem. There only seems to be two Samba options 1 or 2.1, so no idea what default is, as my Synology needs 2.1 to work and the T4 1, soooo what is default!?

Default is the highest version (most secure) of SMB that the Wiz itself supports. (The T3 for example uses an older kernal that doesn't support 2.1 client connections itself)

1.0 and 2.1 are two widely supported versions that may be useful when capping capabilities.

I am surprised that your T4 SMB server doesn't work with 2.1 though. It should!
One reason that it may not is if you have manually fiddled with the SMB configuration files to limit it's server protocol version.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Dec 31, 2021 15:42

MrQuade wrote: ↑
Fri Dec 31, 2021 13:46
I am surprised that your T4 SMB server doesn't work with 2.1 though. It should!
One reason that it may not is if you have manually fiddled with the SMB configuration files to limit it's server protocol version.

Possibly /etc/samba/distro/smb-secure.conf which has min protocol = SMB2_02 specified by the firmware, which I understand that value to be "The earliest SMB2 version.".

BigbobOz - you should check for an updated copy of the above file with an -opkg suffix.

BigbobOz · Post by **BigbobOz** » Sun Jan 02, 2022 17:19

I wouldn't know how to muck around with any files so don't think I changed something I shouldn't have but MrQuade, the HDD in the T4 did come out of the T3, carry over?

T4 details:
System OE: OE-Alliance 3.4
Firmware version: beyonwiz 16.1.20170310 (2017-03-10)
Kernel / Drivers: 3.14.2 / 20160405

Looks old, need to do a USB update?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Jan 02, 2022 17:30

BigbobOz wrote: ↑
Sun Jan 02, 2022 17:19
Firmware version: beyonwiz 16.1.20170310 (2017-03-10)

Oh! You should've lead with this.

BigbobOz wrote: ↑
Sun Jan 02, 2022 17:19
Looks old, need to do a USB update?

Yes, and you'll have to re-do your settings.
You can print them out first though - see viewtopic.php?f=8&t=14084&p=186376#p186376
Check the front panel firmware version too.

BigbobOz · Post by **BigbobOz** » Mon Jan 03, 2022 10:09

Ok thanks, I think I now remember why I didn't previously update the T4. Any downtime on the T4 won't be popular in this household.

No idea what I'd get to replace it if it died. V2 in theory can do it with extra USB tuners, external drive etc but I like the T4 with it all being internal and proper display.

Edit: So the box needs to be set up as if all new? Channel scan the lot?

Gully · Post by **Gully** » Mon Jan 03, 2022 11:16

BigbobOz wrote: ↑
Mon Jan 03, 2022 10:09

Edit: So the box needs to be set up as if all new? Channel scan the lot?

Yes, though as posted you can do some manual backups to help.

prl · Post by **prl** » Mon Jan 03, 2022 11:48

BigbobOz wrote: ↑
Mon Jan 03, 2022 10:09
Any downtime on the T4 won't be popular in this household.

I've been running firmware 20211010 on our in-use T4 since a few days after it was released as a beta back in Oct 2021. I haven't had any issues.

BigbobOz · Post by **BigbobOz** » Mon Jan 03, 2022 22:28

Hi Peter, not concerned on the quality of the firmware! I'm concerned on me f@#king something up!

I'll get it done, thanks all.

Rob

jk2outcast · Post by **jk2outcast** » Mon Jan 10, 2022 09:34

Hi prl,

I just updated my T4 to the latest firmware the other day via the traditional USB Stick method and restored my backed up settings and everything went perfectly well, however I have noticed that there are some icons missing next to the Dolby Digital and HD Info bar that appears on screen, its where the HbbTV icon used to be, is this normal?

I have attached a jpg image of the info screen I'm referring to as I haven't used any image uploading services previously.

Could this be as a result of me restoring my backed up settings, or this something that has changed on the new firmware? Everything seems to be same as previous including the EPG and Media and Timings Screens.

Appreciate your help.

Zac

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Jan 10, 2022 09:50

jk2outcast wrote: ↑
Mon Jan 10, 2022 09:34
I just updated my T4 to the latest firmware the other day via the traditional USB Stick method and restored my backed up settings and everything went perfectly well, however I have noticed that there are some icons missing next to the Dolby Digital and HD Info bar that appears on screen, its where the HbbTV icon used to be, is this normal?

Yes, see - viewtopic.php?f=66&t=14606&p=194361#p194361

jk2outcast · Post by **jk2outcast** » Mon Jan 10, 2022 11:12

Thanks for the reply Grumpy_Geoff at least I now know that there's nothing wrong with my unit after the update.

Must admit that it looks pretty odd with that massive gap between the Update available icon (which I assume is the up arrow) and the Dolby Digital Symbol on the right. Oh well as long as it still functions correctly I guess!

prl · Post by **prl** » Mon Jan 10, 2022 14:25

The reason for that choice are given in the post that Grumpy_Geoff linked to.

The "downloads available" icon is really not part of the status of the channel you are watching, like the other icons up in that corner. That's why it's now separated from them.

jk2outcast · Post by **jk2outcast** » Tue Jan 11, 2022 12:25

Hi prl,

I read through the post that Grumpy_Geoff linked to and understood the reasoning behind it, but I still think it looks odd and unfinished.

Has the gap been left for some upcoming features/icons?

Also whilst I have your attention, previously I've always changed the settings and retuned the tuners after every firmware update, this is the first time I've backed up and restored the settings, is this ok to do after a firmware update? Or should I have just set everything up from scratch?

I know it's been mentioned in the past that you shouldn't restore settings after a major firmware update, is that correct?

Thanks in advance
Zac

Paul_oz53 · Post by **Paul_oz53** » Tue Jan 11, 2022 13:13

Hi Zac,

Restoring a backup is normally fine if everything is working OK before the update. If after the update something isn't working as expected and we can't find an easy fix, then we recommend doing a clean install as you obviously know.

For simple installations there's not much effort involved in doing a clean install and so it's quite reasonable to do that. However, if you have a lot of customisations then restoring a backup is a good option.

prl · Post by **prl** » Tue Jan 11, 2022 16:07

jk2outcast wrote: ↑
Tue Jan 11, 2022 12:25
Hi prl,

I read through the post that Grumpy_Geoff linked to and understood the reasoning behind it, but I still think it looks odd and unfinished.

Has the gap been left for some upcoming features/icons?

There aren't any planned that I know of. I removed some redundant and irrelevant ones at peteru's suggestion.

The download icon is where it is because it doesn't really belong grouped together with the icons that represent the channel state/features, and it also is on the left-hand boundary of that area of the infobar. The channel state icons start at the right-hand boundary of the area and are ranked leftwards from there. This was done as part of adjusting the alignment of parts of that area so that the boundaries of all the items in the area line up with the boundaries of the area.

jk2outcast · Post by **jk2outcast** » Mon Jan 17, 2022 09:25

Hi Paul_oz53 and prl,

Thanks so much for both your replies and apologies for my late response.

In response to Paul_oz53, mine is a fairly simple installation so in future I might stick to doing a clean installation after a firmware update, that way you eliminate any chance of conflicts. Besides as you said it doesn't take long to retune and re-setup the unit.

In response to prl thanks for clarifying the feature icon layout changes, makes sense now once you understand how they are grouped.

I must admit the infobar is one of the best features of the GUI for me and I use it quite a lot, the fact that it displays so much info but doesn't take up as much of the screen is what appeals to me, we have several tvs in the house and I can honestly say the GUI interface of the T4 is miles ahead of any of our tvs and we have an LG, Sony and a Samsung. So well done to you all that have worked on it.

Thanks again for both your replies

About the Forum

Join us