I was trying to resolve some issues with my new B30 and saw in another post new firmware. I upgraded from 1.0.6 to 1.1.0 and this went successfully. However, now with PC1 input (USB-C) I have a flickering / line appearing on image, at about a 10 second interval. I have tried different cables and two different USB-C laptops and it is still persisting. I also tried lowering the resolution and refresh rate and it still occurs.
Hello Kingzen,
Thanks for getting back to us and does another firmware file also has been upgrade thru the “Kinetic” tool?
Hello, yes I have updated the firmware both through the ProAVManager tool (using micro USB) and the Kinetic tool (using USB-C) and the updates completed successfully.
I have the exact same problem - flashing lines on the screen every few seconds on 1st input via USB-C. The only difference is that I have upgraded to firmware 1.1.0 via micro USB but have not upgraded with Kinetic tool via USB-C because my laptop that is connected via USB-C is a MacBook and the upgrade tool is a Windows executable. I tried connecting only the USB-C cable to my desktop (it has no display output via USB-C though) and the Kinetic tool was simply not showing any connections available so I couldn’t upgrade…
Hello Kingzen,
Where you purchased this device and what is your order number?
Maybe we can try arrange the new replacement to you for a check.
Hi there,
Where you purchased this device and what is your order number?
Maybe we can try arrange the new replacement to you for a check.
I have purchased via your official Europe store, my order number is #23729.
I have upgraded the firmware just because my M1 Mac Mini (which is connected via HDMI) was not outputting at 85Hz (I have an ultrawide, 3440x1440 monitor) - the screen was turning black in like 10s intervals, but it is totally fine at 60Hz and so I thought that the firmware upgrade might help but it didn’t and now I think that it is Mac’s problem that the HDMI on Mac mini is just not capable on outputting this refresh rate at that resolution… I didn’t have any other problems with the previous firmware (my device had 1.0.6 originally) - I would be happy to just downgrade it back to 1.0.6 as the USB-C screen line flickering issue was not present on that one. Is that possible?
Hello,
Thanks for your clarifying.
Our device can only work with 3440x1440@60hz.
and here is the V1.0.6 firmware version download link: iDock B30 V1.0.6 firmare
If you would like and please help snap a video about the problem so we can transfer to our engineer for a check why new version have this issue.
Many thanks.
Well it actually does work at 3440x1440@85Hz on my Windows desktop and my Macbook via USB-C - it’s just the M1 Mac Mini that does not seem to like running at 85Hz 
Here’s a video where you can see lines flashing on the screen:
Just a quick update - I have downgraded to 1.0.6 now and the flashing lines on the USB-C output are now gone.
Hi,appreciate for your update and the video.
Have a nice day~
I was also able to downgrade to 1.0.6 and the flicker has gone away. However, now the USB-C PC1 input maxes out at 1920x1080. Could this be because I separately updated via Kinetic and USB-C? Do I need to downgrade that side as well?
The behavior, which I didn’t see before the firmware upgrades and subsequent downgrade back to 1.0.6, is that the B30 is seen as a “2CH 1080” on the USB-C input, instead of the actual monitor. As a result, it is limited to 1920x1080, and cannot go up to 4K.
Hello Kingzen,
Upgrade the firmware(V1.0.6) via the ProAVManager not related to the USB-C port.
Could you try test with other USB-C cable for a check？
Yes I have tried with many cables. The one that came with the hub, other USB-C 3.1 Gen 1 and Gen 2 cables and some TB4 cables.
Sorry Kingzen,
When your device update to V1.1.0 version and the two monitors can work with other higher resolution,right?
Just back to V1.0.6 and only work with 1080P?
I had the same thing after downgrading - I tried multiple things but what worked for me was switching to input 2 of my monitor. Then I switched back to input 1 and everything is OK now. It seems like the dock was not reading the EDID from the monitor until I plugged it into a different port or something
The changing HDMI input and then back fixed it for me too. Thank you.