GeoBridge OS
Release notes · Version 2.5.2

A closer look at
what has changed.

Cumulative improvements since version 2.4.26

This update brings a redesigned dashboard, improved diagnostics, safer configuration changes, independent extensions, temporary remote support and a revised OTA upgrade process.

Dashboard & Appearance

  • Refreshed dashboard layout with clearer separation between station status, system resources, cooling, network access, software protection and service activity.
  • Dark and light modes with a shared sun/moon switch and remembered theme preference.
  • Improved light-mode colours, text contrast, logo visibility and readability across the dashboard and extension pages.
  • Updated GeoBridge branding, signal-path icons and processing animations.
  • Animations and indicators respond to available operational data rather than simply implying that everything is running.
  • Improved spacing, typography, button sizing, password-visibility controls and contextual help.
  • Simplified headings and removed unnecessary decorative numbering.

Mobile Experience

  • Revised responsive layouts and bottom navigation.
  • Extensions are accessible from the mobile navigation instead of crowding the top of the screen.
  • License information, software version, contact links, Support & access and Sign out are available at the bottom of mobile pages.
  • Improved chart and satellite-view rendering stability during live updates and scrolling.
  • Reduced unnecessary element replacement and layout changes.
  • Improved handling of narrow screens, long labels and card spacing.

Live View, Graphs & History

  • Live signal-path presentation distinguishes receiver input, RTCM processing and delivery.
  • Onocoy upload graphs use acknowledged delivery-byte progress, not receiver input speed.
  • Added a shared 10-minute upload history and five-minute receiver-throughput and signal-quality trends.
  • Short live histories remain available when refreshing the browser or moving between pages; they reset when their producing service or device restarts.
  • Added bounded operational history covering receiver availability, RTCM, internet connectivity and delivery, retained for up to seven days.
  • Missing or stale observations are shown as unavailable or gaps rather than invented zero values or assumed outages.
  • Clearer separation between host uptime, service uptime and network-link duration.

Station Map

  • Added a station map based on valid receiver reference coordinates.
  • Station identity is reflected in the map marker and browser title.
  • Added an Open in Google Maps action when valid coordinates are available.
  • The map does not request browser geolocation or infer the station position from its public IP.
  • Map loading and caching are bounded to avoid unnecessary downloads.

Receivers & Rtcm

  • Improved receiver-mode handling and recovery around supported USB and network/AP configurations.
  • Added HYFIX receiver-interface discovery while retaining USB as the station’s data source.
  • Discovery runs only when requested and uses bounded concurrency, duration and network scope.
  • Manual IP entry becomes available when automatic discovery cannot find the receiver.
  • Help explains that the receiver must be reachable on the same local network.
  • Improved receiver-interface access controls and clearer distinction between the data source and a receiver’s web interface.
  • Added supported MGW310 Ethernet/profile handling.
  • Added manual antenna metadata handling for RTCM 1033 output.
  • Corrected GLONASS MSM4 time-field decoding.
  • Improved AP verification and timeout handling without treating missing evidence as a successful verification.

Network Changes & Rollback

  • Added guarded trial-and-confirm workflows for supported Wi-Fi, owner remote-access and receiver-mode changes.
  • Unconfirmed trials can restore the previous configuration instead of leaving a remote change permanently applied.
  • Added recovery handling for interrupted configuration trials, including recovery after reboot.
  • Improved Wi-Fi scanning, connection-state presentation and network-interface information.
  • Improved Ethernet/Wi-Fi uplink policy, including handling of an Ethernet connection that has no working internet route.
  • Receiver-only interfaces remain distinct from internet uplinks.
  • Existing explicit network-profile settings are respected.

Ota Updates & Recovery

  • Version 2.5.2 supports a single-package upgrade from 2.4.26 through the normal OTA process, without a separate SSH preparation step.
  • The package contains the required transition and activation components.
  • Updated version reporting prevents a partially activated installation from being reported as complete.
  • Post-install activation checks verify core readiness, recent RTCM and progressing delivery acknowledgements before recording successful completion.
  • Signed package and component verification remain enforced.
  • Failed installation health checks use the updater’s rollback mechanism to restore the previous files and configuration.
  • Activation state distinguishes completion, failure and rollback instead of presenting all outcomes as success.
  • Improved startup coordination between activation, service recovery and SSH security policy.
  • The direct 2.4.26 upgrade path and subsequent reboot recovery were verified on a pilot device before general rollout.

Security & Root Access

  • Standing SSH access is closed, including persistent service/socket activation.
  • Owner Tailscale SSH is disabled under the support-only access policy.
  • Root is not exposed as a permanent direct-login account.
  • Authorized elevated maintenance is available through a temporary support session.
  • Signed integrity checks cover system components and the required access-security posture.
  • Corrected a startup-state inconsistency that could leave SSH inactive but persistently enabled, triggering a security failure after reboot.
  • Dashboard access on the owner’s normal network remains separate from temporary support access.

Remote Support

  • GeoBridge Support operates alongside the owner’s existing Tailscale connection; opening support does not require leaving the owner’s tailnet.
  • Support access is temporary and can be closed by the owner.
  • Added a password-protected dashboard entry through the isolated support connection.
  • Support authentication is separate from the owner’s normal dashboard login.
  • Session expiry and closure remove temporary access and associated authorization.
  • Added a problem-description field when requesting support.
  • Clearer distinction between Owner remote access and GeoBridge Support.
  • Improved support-action deadlines and status reporting.

Offline License Continuity

  • Signed offline authorization allows licensed operation for up to seven days after the last successful renewal, subject to license validity.
  • Cached authorization is verified locally and refreshed when connectivity is available.
  • A temporary licensing-server outage does not immediately invalidate an otherwise valid cached authorization.
  • This does not provide offline access to internet-dependent services: Onocoy and other remote destinations still require connectivity.

Memory, Cpu & Background Work

  • Added automatic low-memory resource profiles for smaller boards, including Raspberry Pi Zero 2 W.
  • Dashboard and history processes use lower Go-runtime memory budgets on low-memory systems.
  • Reduced repeated inventory work and added bounded caching.
  • Automatic maintenance jobs can be deferred when a small device has insufficient available memory.
  • Security updates are not permanently disabled, and already-running package operations are not forcibly terminated.
  • Optional work is bounded so it does not compete unnecessarily with core station functions.
  • Added targeted containment for a repeatedly detected systemd-logind stall, without restarting networking, GNSS or the entire device.
  • These safeguards reduce resource pressure; they do not make every combination of optional workloads suitable for a 512 MB device.

Independent Extensions

  • Helium, Wingbits and Mastchain are managed separately from the core system.
  • Extensions can be downloaded, installed, updated and removed individually.
  • Uninstalled extensions do not run their optional receiver services or background observers.
  • Added a signed extension catalog and package-verification flow.
  • The catalog can introduce additional compatible extensions without requiring a core update solely to list them.
  • Installed extensions remain usable if the catalog is temporarily unavailable.
  • Improved module-local recovery and separation from dashboard, GNSS and Onocoy operation.
  • Removal distinguishes module software from retained settings and identity.
  • Existing custom installations are not silently replaced or taken over.
  • Extension pages identify the selected module and provide clearer install/manage actions.

Cooling & Health Status

  • Updated fan graphics and rotation behaviour based on fresh fan-output information.
  • Improved automatic-cooling controls and hardware information.
  • Added compatibility handling for boards that do not support the relevant fan configuration.
  • Improved health aggregation: historical or unrelated failed-service records do not automatically override verified current station health.
  • Genuine critical failures and missing critical evidence still remain visible.
  • Clearer distinction between active operation, startup, unavailable data and conditions requiring attention.

Rollout Information

  • Version: 2.5.2
  • General stable OTA package: approximately 22.4 MB.
  • Devices receive the release according to their update-check schedule and automatic-update settings.
  • Existing owner exclusions, explicit device targets and separate hardware channels remain respected.
  • A brief interruption to station services can occur while the update restarts and verifies them.

Please keep the station powered and connected while installation completes. Check that the reported version is 2.5.2 and that receiver activity and data delivery have resumed before considering the update complete.