- Correction du double zoom in quand on utilise le bouton de volume
- Correction des cartes basées sur OpenStreetMap
Due to a cascade of unfortunate issues with the server hosting the forum.mytrails.app service, I have lost the server and its data.
It’s inconvenient for me, but to those of you who contributed to the forum, it’s a loss of the time you invested in it, and for that I am deeply sorry.
Sadly, it is representative of a lack of time on my part to adequately maintain MyTrails itself and the infrastructure that underpins it. Which leads me to the painful of decision having to sunset MyTrails…
I started MyTrails over ten years ago, before Android was even released. The Android version itself was started in late summer 2010, almost ten years ago.
In that timespan, Android has gone from clunky keyboard and d-pad phones with weak CPUs and little RAM to all-screen slabs with more RAM than some desktops and blazing CPUs.
When I started MyTrails, the few map apps that existed were slow and laggy because they relied on Android’s then-basic image display technologies to draw map tiles. One of MyTrails’ signature features was that, because it used OpenGL to render images, it was fast even on low-end hardware.
Since then, phones have improved, and other apps (most notably Google Maps) have caught up to MyTrails’ use of OpenGL and stopped using pre-rendered maps altogether, switching to more efficient all-vector data.
Meanwhile, MyTrails went through other technological changes as Android refined its early rough edges and geekish looks, but the application stayed true to its roots: technical, a bit overstuffed with features and sometimes hard to use. And it skipped the white UI fad that Apple spearheaded, followed by Google, and which is finally over now that the latest versions of both systems offers a standard dark-mode.
From a personal standpoint, MyTrails started as a fun hobby (and a way to not get lost while hiking), became my main occupation and revenue stream for a few years, and returned to a hobby as I was unable to make it stand out enough in a crowded market for it to remain my sole revenue stream.
During that time I released over a hundred updates, MyTrails was downloaded over 1.5M times and was used by about 200k users at its peak in 2017. It has also helped me become a full-time developer once more, and the expertise I gained developing and publishing it has allowed me to become a minor expert in Android development and to help found a successful development studio.
So what does it mean for MyTrails?
Basically, not much for now, since I wasn’t actively developing new features. However, I will not be rebuilding the forum, and will prioritize resolving subscription issues over answering questions about bugs and feature requests.
I will continue to update the New maps page to help update built-in maps and make it easier to use new and fun maps that may come to my attention.
I have spent most of my spare time in 2019 dealing with obsolescence driven by Google: shutting down G+, making their geo APIs paid, transitioning from Fabric to Firebase, changing push notifications from Google to Firebase, forcing developers to target the latest APIs, etc.
But Android 11 is just around the corner, and Google will continue to make it harder to store files on our devices, taking Android further down the path of a locked-down iOS-style experience, but lacking its integrated ecosystem. This will make it even harder for MyTrails to support offline maps, since the API that Google wants developers to use (yet it won’t fully support in its own services, like Drive) is too limiting. So expect offline maps to no longer work if you update to Android 11, like some many other useful hacks and customization features.
Aside from offline maps, nothing much should change… but if it does, I may not be able to fix it, so maybe you shouldn’t count on MyTrails too much.
I want to thank early users who helped me shape MyTrails, my partners (OS Opendata, My Trails the track sharing site, VTTrack, Utagawa…), and the team of translators who translated the app to 10 languages (and partially to many more), and all of my dear users. I hope you continue to have fun hiking, skiing, mountain biking, riding, and more (hopefully most of you are environmentally conscious and try to limit your CO2 footprint).
Anyway, back to hiking!
Les cartes IGN seront indisponibles à partir du mardi 3 décembre et potentiellement jusqu’au 9 décembre 2019.
Plus d’infos sur le forum.
- Correction de l’envoi de trace à My Trails
- Tentative de solution pour la carte Kompass
- Correction de l’accès réseau pour la plupart des cartes
- Correction du plantage sur Android 9
- Correction de recherche de lieu, itinéraire, normalisation d’altitude
- Correction de connexion de MyTrails à un compte Google, passage au push Firebase
- Correction de la vitesse verticale dans le HUD
- Correction de la notification Wear après l’arrêt
- Correction de GPSies
- Nouvelle carte: OpenSeaMap
- Correction de la réception de définition de carte depuis le site
J’ai reçu le message suivant de la part d’IGN.
L’ensemble des services du Géoportail seront inaccessibles de 6h à 8h du matin le samedi 8 juin
L’ensemble des services du Géoportail seront inaccessibles de 6h à 8h du matin (les services web ainsi que le site geoportail.gouv.fr). Il est possible que le service reste perturbé le reste de la journée du samedi.
Nous nous excusons pour la gêne occasionnée.
Si vous avez besoin d’utiliser les cartes IGN pendant cette période:
- si vous avez un abonnement hors-ligne, pensez à créer une carte en avance
- sinon, parcourez la carte depuis MyTrails avant l’interruption, elle restera dans le cache (limité)
- Correction du partage lorsque les traces sont dans certains dossiers
- Notifications et icone adaptative pour Android Oreo
- Calcul plus intelligent de la vitesse au-delà de laquelle une position GPS est ignorée
- Remplacement de Google+ par le nouveau forum MyTrails
- Correction de la carte IGN
En raison d’un problème de configuration côté IGN, les cartes IGN (Top25/100, cadastre), ont été inaccessibles depuis MyTrails entre le jeudi 28 février le 3 mars 2019.
Une version de correction (2.1.5) a été publiée pour corriger le problème.
Je vous prie d’accepter mes excuses pour ce dysfonctionnement.
Mise à jour du 4 mars indiquant la correction.
Google some time ago switched all maps-related APIs from free to paid, which requires changes in apps that use those APIs. Because MyTrails can aggregate several similar services, I didn’t immediately realize that some functionality MyTrails relies on was no longer available.
I will be releasing an update that restores directions, POI search and location search functionality. For Pro users, I will test whether MyTrails can keep using the paid Google APIs, but for free users, MyTrails will likely have to switch to free services, such as OSM, and I may have to restrict directions.
You can restore some of the search functionality in MyTrails 2.1.4 by enabling the OpenStreetMap search provider in MyTrails > Preferences > Other.
In the latest 2.1.6 beta, Google search, directions and altitude are fixed.
Due to a Play Store policy change, MyTrails SMS is no longer available on the Play Store. MyTrails can still send out your location as an SMS (because this uses your standard SMS app to do so), but it can no longer receive SMS directly.
In a later update, MyTrails will change the format of sent SMS so that they can be more easily clicked to restore some of the functionality.
You can install the latest version of MyTrails SMS by downloading it here.