MagneFire

> > @I-asked I've been testing your PRs, great work! But I'm wondering what kind of performance we can expect? Currently pinging seems to take some time: > > ```...

We already prompt to disable battery saving. Maybe this isn't enough on Samsung. Or maybe it's something with newer Android devices? What phone did you test this with?

There appears to be no difference when I use WiFi or cellular. I've slightly altered your version before the dbus library change and the additional dbus services as there have...

Here are some logs with a little more debug information. There are clear *large* gaps visible when looking at the timestamps. Maybe it's some retry logic that has a different...

Not entirely sure why but it seems that on the Samsung phone the SlirpService freezes in one of the `synchronized` blocks. Removing these blocks results in a segfault, which is...

Hmm, after more testing it seems to be related to MTU. The app requests 247 (which is initially also used for libslirp). But once connected the MTU changes to 515....

This is intentional, see the following for more context: https://github.com/AsteroidOS/meta-smartwatch/commit/85e529c615f87f4cd8c923116b6d37e0059b2f12

Hmm, seems logical. But this then begs the question why this is only required for `hoki` and `beluga`. Other watches do not seem to be affected by this.

For what it's worth I've done some work upgrading to `scarthgap`: - https://github.com/MagneFire/asteroid/tree/f/scarthgap - https://github.com/MagneFire/meta-asteroid/tree/f/scarthgap - https://github.com/MagneFire/meta-smartwatch-1/tree/f/scarthgap - https://github.com/MagneFire/meta-asteroid-community/tree/f/scarthgap In summary, a lot is broken: - dbus seems non-functional -...

I've finally made it all work. The issue seems to originate with `libhybris` and compatibility issues with 64bit time_t support (introduced in https://github.com/openembedded/openembedded-core/commit/b9e0c5e750c3097e176fdc18b3b58b622f716e71). For now I've added a workaround by...