V3.70~74 Firmware check timed out

Beta testing Venus OS beta testing
1

Hi,

  1. German translation missing at update check message.
  2. Is this message an error message or wants it to tell that I have the latest version installed?

Screenshot_20260120_124032_Chrome
Screenshot_20260120_124032_Chrome2340×1080 148 KB

2

It’s an error message, effectively saying the Cerbo could not find the update server. This happens occasionally, try again. If it keeps failing then this is a problem.

3

I’m not so sure about that, because last night Cerbo found update v3.70~78. After that, the same message appeared again when checking for updates.

4

I’ve the same issue. So, I think it is a problem.

5

Same issue here with 30.70-78.

6

This was an issue in GUIv2, when you already had installed the latest available version. The issue was fixed and will be in a next Venus OS beta version.

7

After updating from 3.70-61 Large to 3.70-74 Large, the click on ‘Check Updates’ under Settings/
./Firmware/Online-Updates in GuiV2 always gives a ‘Firmware check timed out’ error. While Firmware check in VRM works.

3 Likes
Venus OS v3.70~96 available for public testing
8

I have the same issue since updating to 3.70-74. But when a new firmware is released (like 3.70-78 yesterday), it is updating normally. So it seems more like a wrong notification than an actual error.

1 Like
9

I also reported this on Github.

This was also present in 3.70~74.

Using 3.70~81 large image, Update feed/Beta release.

When one tries to do a check for new firmware (Settings/General/Firmware/Online updates/Check for updates), the result is always “Firmware check timed out.” I have tried multiple times, minutes or hours apart, same result.

If I change to Update feed/Official release, the check works quickly, and as expected (and offers 3.67). Going back to Beta release, the problem returns. The only way I’ve found to get past this is to go back to 3.67 and check for a Beta release from there.

Perhaps the check is failing as claimed, or perhaps the message is incorrect and should actually indicate that there is no newer release.

10

FWIW, I get: “no newer version available” on v3.70~81

11

I moved some comments to here, besides the original there was a (likely related issue with dbus-serialbattery as well). Both should be solved now.