Don't use GenericDataLocation on Android

That's the regular file system outside of the app bundle, which needs
extra permissions to write to.

src/lib/models/locationhistorymodel.cpp

@@ -16,7 +16,12 @@ using namespace KPublicTransport;
 
 static QString basePath()
 {
-    return QStandardPaths::writableLocation(QStandardPaths::GenericDataLocation) + QLatin1String("/org.kde.kpublictransport/location-history/");
+#ifdef Q_OS_ANDROID
+    constexpr auto dataLoc = QStandardPaths::AppDataLocation;
+#else
+    constexpr auto dataLoc = QStandardPaths::GenericDataLocation;
+#endif
+    return QStandardPaths::writableLocation(dataLoc) + QLatin1String("/org.kde.kpublictransport/location-history/");
 }
 
 LocationHistoryModel::LocationHistoryModel(QObject *parent)

[Nicolas Fella]

What's the use case for not using AppDataLocation always? Sharing recent locations between apps?

[Volker Krause]

Yes, exactly. The idea is to allow for the same recent/favorite locations in e.g. KTrip and Itinerary.