+xWe will not be doing that, sorry. If a customer has a buggy GPS or device, it is not our job to try to cover that up, and I am not sure that it would be a helpful thing to do anyway.
You didn’t get the point.The filtering is not related to the bug. It’s just because the heading line has some kind of instability with SkyDemon in comparison of other Aviation navigation App running on the same device at the same moment trought shared screen (i.e. Helios, SdvfrNext and VFRNav have a more stable/smooth heading than SD that is like a raw data)
This is not related to a bug, but in the way data are processed by the app.developer.
Second point, about the goggle "position" bug, you may have more Android customers affected in the future.
So far I just regret that you don’t advice your customers that (at least) Samsung devices with UI8.0 and Android 16 are not compatible with SkyDemon.
I paid 149€ and so far SkyDemon will not grant any refund.
Samsung is not in rest, I paid 399€ for this "new technology", and Samsung also claim’s ungulty. GPS is working, no internal hardware failure.
Goggle said ?... we are the champions of innovation and merging technology !
Victims lose their money .
End of the story.
Today, I partially counteracted the issue.
I use SD as a moving map -only- and Helios as navigation tool, both on the same device with splitted screen.
A second device (different brand/manufacture/O.S.) is running VFRNav as navigation traking, and backup moving map in case of failure of the first device.
So far I'm good, but just disappointed that the most expensive one is the less reliable one since Android 16.