MapMyTracks in v7.3.7

[wolfgang61]

I wrote my own Mapmytrack server in python and I noticed a few things:



1. start_activity says  privicity instead of privacy



2. in the configuration, I can set default values for Public/private and Activity type. They are used only for Auto Live Tracking, I would like to see them as default values for manual life tracking start. Otherwise, the text in the configuration is wrong, it should then be "Start auto life tracking in this mode" and "Default activity type for auto life tracking"



3. sometimes the last update_activity only comes after the corresponding stop_activity



4. maybe related: If I start and stop within a short time, say 5 seconds, Oruxmaps sends start_activity and stop_activity. That is fine but it passes -1 as activity_id to stop_activity.



5. repeating step 4 results in some strange messages. The order start/update/stop is wrong, and most activity ids are wrong.

Code Select Expand

  12.5340 POST from x.x.x.x on port 12398 / request=start_activity activity_id=None with 1 points
   13.1273   returning <type>activity_started</type><activity_id>252</activity_id>
   13.1285 POST from x.x.x.x on port 12398 / request=stop_activity activity_id=-1
   13.1876   returning <type>activity_stopped</type>
   35.3846 POST from x.x.x.x on port 12398 / request=stop_activity activity_id=252
   35.3851   returning <type>activity_stopped</type>
   35.3932 POST from x.x.x.x on port 12398 / request=update_activity activity_id=252 with 1 points
return_error: 401 update_activity: Lifetrack(252) was already stopped
   35.4823   returning  <type>activity_updated</type>


For testing, I am emulating a smartphone with android-studio, feeding it a GPX track. On the server side, install https://pypi.org/project/Gpxity/">https://pypi.org/project/Gpxity/ and run

Code Select Expand

gpxity_server --servername my_server.org --port 12398 --mailto="my_mailaddress@test.org" --loglevel info --directory=/var/lib/gpxity_server

[wolfgang61]

I fixed all of this plus the 24h-bug by writing my own tracking app: https://rohdewald.de/gpsforwarder">//https://rohdewald.de/gpsforwarder

[orux]

I fixed all of this plus the 24h-bug by writing my own tracking app: https://rohdewald.de/gpsforwarder">//https://rohdewald.de/gpsforwarder

Some of the problems related should be solved in the next version, I hope,





orux

[joseulm]

Hola, desde hace dos semanas no me inicia el seguimiento en vivo en Mapmytracks. A los pocos segundos de iniciar la grabación de un track me sale, en la parte inferior de la pantalla, la siguiente indicación: "MapMyTracks error: unauthorised" He revisado que esté bien puesto el usuario y la contraseña. Siempre ha funcionado perfectamente, la ultima ruta que me grabó en MapMyTracks fue el día 6 de enero de 2019. Espero tu respuesta si consigues detectar el fallo. Muchas gracias.

[wolfgang61]

Hola, desde hace dos semanas no me inicia el seguimiento en vivo en Mapmytracks. A los pocos segundos de iniciar la grabación de un track me sale, en la parte inferior de la pantalla, la siguiente indicación: "MapMyTracks error: unauthorised" He revisado que esté bien puesto el usuario y la contraseña. Siempre ha funcionado perfectamente, la ultima ruta que me grabó en MapMyTracks fue el día 6 de enero de 2019. Espero tu respuesta si consigues detectar el fallo. Muchas gracias.

I believe mapmytracks does not support http:// anymore, are you already using https:// for the server?