Calender Entries are Blank (no text only Time) with SFOS-Update 4.5

[FingusDE]

With updating to SailfishOS 4.5 on Tama Community-Port Amazfish only send blank Calender Entries to the Watch (Amazfit GTS).

[FingusDE]

Still there:

[theseer]

I'm having the same problem on my GTS 2.

It appears also that the data transfer for the statistics is broken, as I don't have any history step count or other health data anymore. Not sure if that is related in anyway.

I'll try to debug this a bit maybe later today - maybe I can figure something out ;)

[theseer]

I spent some time over the last days looking into this, but didn't find an obvious culprit as of yet.

Looking at the journal log (journalctl -f) when using the debug "update calendar", I can see the data is complete with title when sending. So it's not a problem with the calendar itself.

I'll debug some more :)

[piggz]

This seems to work Ok on my GTR2

[theseer]

I didn't have much time yet to debug further but given nothing changed in terms of the application itself and the log shows the calendar data is at least received correctly, it must be something related to the OS.

@piggz: Are you using the official bluetooth stack or your patched version despite being on the latest OS version?

[piggz]

Im using the official BT stack ... the change that was in my version is now incorporated into Sailfish

[theseer]

There goes my - currently - last idea :-/

[piggz]

Ive just created 2 test entries in my calender, and both appeared on the phone just fine, except that the time is missing the minutes, so ill certainly look at that.

[theseer]

So maybe that's a regression to my fix with the minutes in #253 ? Even though I don't see how..

[piggz]

Hang on, i may not have restarted my daemon.....

[piggz]

Ah ok, that interesting, since restarting the daemon with the fix in #253, i have the minutes but no text!

[piggz]

Ok, ive fixed it. In addition to the off-by-one, removing the 0x00 on the line below fixes both the minutes, and the missing text.

[theseer]

I have an idea:

The change I suggested for #253 adds a byte to the output, pushing the following \00 by one position. Maybe the additional \00 is now superflous and the culprit, marking the string as emtpy (c-style string termination)?

[theseer]

Yeah, that :-)

[piggz]

Which is strange because that doesnt match GB

[piggz]

Ah no, this is correct, as per https://codeberg.org/Freeyourgadget/Gadgetbridge/src/branch/master/app/src/main/java/nodomain/freeyourgadget/gadgetbridge/service/devices/huami/HuamiSupport.java#L1079 date 0x00 title 0x00