With Android V11 and probably other versions, the operation of Owntracks (OT) is not satisfactory.
At least that’s the case for me.
OT works well in the background, but sending the position in payload no longer works after a few minutes of use. This is also the case as soon as the phone is in standby.
I have disabled battery optimization for OT but it doesn’t change anything.
I followed the advice found here and installed NextTracks via F-Droid. It has the same interface and the same functions as OT and there is no longer any problem with position refresh.
@VonOx In my case, with OT, it was only a few minutes of operation, so completely unusable as is
Yes, it’s OSM, but that doesn’t change anything for Gladys.
I don’t have enough experience with Nexttracks, installed only since tonight, if I have any issues after several days, I’ll let you know.
Personally, I had already noticed this with Gladys v3 a few « years » ago..
Since then, I have abandoned Owntrack in favor of a scene in tasker, I sometimes have a few misses, but the advantage is that it triggers automatically when I get in/out of the car, so every time, it resets the scene, no need to restart anything in the end.
Yes, that’s it, but I still see failures… I don’t know if it’s due to the GPS chip (yet Waze tracks me well…), if it’s Android or Tasker that doesn’t follow… but the position is not always up to date.. which is still quite disabling..
For me, NextTracks works very well with zero missed tracks over several days, the only downside is that it’s very battery-intensive.
I’m trying to optimize a bit by increasing the refresh time. Has anyone else noticed the same problem?
Is this specific to iOS? I couldn’t find nextTracks on the store.
My Tasker-based solution still has issues. I don’t know if it’s related to my phone, but it struggles to get the correct GPS values, so it often sends an « outdated » position for a long time…