Here a a few things that I miss from OsmAnd:

• adding more than a handful of routing points is tedious
• you cannot plan partially or fully independent from existing roads
• no way to save and restore a planned trip
• no overlays for hill shading or incline visualization. Very useful for assessing the effort of a route.
• no public transport support. Very useful for planning a trip with transitions.
• no rain radar
• satellite view

Organic Maps is my goto solution for car navigation because it is very quick, responsive and does not require an high end phone. It just works. However for anything more advanced than that (e.g. live location sharing or recording, planning a hiking trip, navigating mountain bike trails, contributing to OpenStreemMap), OSMAnd is still without contender.

Availability still very limited:

https://support.garmin.com/en-US/?faq=QssFZHtIOfAYNSSmzXNwY9

Garmin’s ECG app is currently available in the following regions:

United States
   American Samoa
    Commonwealth of the Northern Mariana Islands
    Guam
    Puerto Rico
    US Virgin Islands
Hong Kong
Philippines
Singapore
Taiwan
Vietnam

Be careful with those, they can interfere/kill your or your neighbors DSL connection. Terrible to diagnose these.

Antennapod supports syncing with podder.net and gpoddersync

Have you tried https://github.com/jeena/fxsync-docker? It is a docker compose for selfhosting the new Firefox sync server rewritten in Rust.

Credits: https://lemmy.world/post/5839867

The reported tracker is ACRA, a crash report library (https://github.com/ACRA/acra).

I digged a bit into the source code and the apk. From looking at the code alone one can’t tell if the crash report is actually enabled, the build configuration depends on some unpublished file. But looking into the apk allows to reconstruct it. These are my findings:

• the usage is implemented here: https://gitlab.futo.org/alex/voiceinput/-/blob/master/app/src/main/java/org/futo/voiceinput/CrashLoggingApplication.kt
• the crash handler is compiled in and also enabled (BuildConfig.ENABLE_ACRA=true)
• the crash handler is configured to dialog mode. According to the ACRA documentation (https://www.acra.ch/docs/Interactions#dialog) that means that user interaction is required for sending (a popup dialog with a cancel button).
• the upload domain is crash.sapples.net
• the dialog can’t be disabled via settings
• the usage of ACRA is missing in the licenses and about dialogs (https://gitlab.futo.org/alex/voiceinput/-/blob/master/app/src/main/assets/license-list.html)
• the privacy policy is correctly stated (https://voiceinput.futo.org/VoiceInput/PrivacyPolicy)

  4.1. If the app crashes, you may be asked if you wish to submit a crash report. If you accept, your device information and crash details will be sent to us for the purposes of investigating the crash and improving the software.

Thank you, I’ll look into it.

Can you give more details of the scan result? Exodus only lists the Play store version. I installed the F-Droid version but Exodus app reports it as “same version” and just shows the clean Google Play Store results. This is obviously wrong, the SHA1 listed for the Play Store version on the Exodus website is different compared to the F-Droid .apk I have installed. Sadly the Exodus website does not support scanning F-Droid apps from third-party repos so I have no idea how to scan it.

That being said, according to the privacy policy (https://voiceinput.futo.org/VoiceInput/PrivacyPolicy), the F-Droid .apk version should have some kind of crash report build-in. So I could imagine that this might get flagged.

Keepass on phone, desktop and tablet. Sync serverless via Syncthing.

• completely private
• always available when needed
• no dependency on services which may go away
• all open source software
• maximum security