Re: Subsurface-mobile support request

[Dirk Hohndel]

Not a dive computer I'm familiar with -- maybe someone on the User Forum can help.

/D

On Sep 17, 2025, at 08:18, Kevin Dawson  wrote:

Please describe your issue here and keep the attached logs.

Hi,

All my dives are now being recorded as at a depth of 642m and a water temperature of over 6,000 degrees.

I am using a Deepblu Cosmiq+ computer. The first 11 dives of this trip uploaded without issue, but now the data is way off.  All dives appear correctly on the computer itself.

Any assistance would be great.

Thanks,

Kevin

[Michael Keller]

Hi Dirk, Kevin.

On 18/09/25 03:36, 'Dirk Hohndel' via Subsurface Divelog wrote:

Not a dive computer I'm familiar with -- maybe someone on the User Forum can help.

/D

On Sep 17, 2025, at 08:18, Kevin Dawson  wrote:

Please describe your issue here and keep the attached logs.

Hi,

All my dives are now being recorded as at a depth of 642m and a water temperature of over 6,000 degrees.

I am using a Deepblu Cosmiq+ computer. The first 11 dives of this trip uploaded without issue, but now the data is way off.  All dives appear correctly on the computer itself.

There's a discussion of exactly this in https://github.com/subsurface/subsurface/issues/3548

The upshot is it's likely a bug in the dive computer firmware rendering the logs useless, and there does not seem to be a fix on our side that can recover the data in the log.

Ngā mihi

  Michael Keller

[Jef Driesen]

On 17/09/2025 22:03, Michael Keller wrote:
>>> On Sep 17, 2025, at 08:18, Kevin Dawson  wrote:
>>> All my dives are now being recorded as at a depth of 642m and a water
>>> temperature of over 6,000 degrees.
>>>
>>> I am using a Deepblu Cosmiq+ computer. The first 11 dives of this trip
>>> uploaded without issue, but now the data is way off. All dives appear
>>> correctly on the computer itself.
>
> There's a discussion of exactly this in
> https://github.com/subsurface/subsurface/issues/3548
>
> The upshot is it's likely a bug in the dive computer firmware rendering the logs
> useless, and there does not seem to be a fix on our side that can recover the
> data in the log.

The log doesn't contain the communication with the dive computer, but based on
the description it's indeed the Cosmiq problem. The invalid depth and
temperature values are fixed with this commit:

https://github.com/libdivecomputer/libdivecomputer/commit/1c7b28fbde7e498ceb481ea0cc3ad9264c97b621

In most cases, the entire profile is affected and will get discarded. Only the
basic info (date/time, max depth, dive time, etc) will remain available. The
profile data is lost and can't be recovered.

This is probably caused by a firmware bug. The worst part is that once you hit
this bug all future dives will have corrupt profiles and I'm not aware of a
workaround to get out of this situation. The Deepblu company no longer exists,
so this bug will probably never get fixed.

@Kevin: Do you happen to have around 100 dives on your cosmiq? Most people seem
to hit the bug around that number of dives.

Jef