I was at some location A, with GPS, then traveled to location B, then C, then D.
Timespan: A few days; device connected to charger in between, GPS switched off and on from time to time; GPS fixes and correct map display were acquired in A, B, C and D and during travel.
In D the device did power off due to empty battery.
After powering on, the location is given near location B (Hannover), not the last known location. (GPS disabled, blue dot is at B, when pressing <R> in the map view the map centers to there). (I actually have not been on the location shown, but maybe 1..2 km away; given the inaccuracy of T-Deck's GPS with bad reception it looks feasible that there was a time when it thought it has been there.)
I think the last known location should be saved and used, or as a fallback no location, but not some location known at a random time in the past.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.10
Regards!
I was at some location A, with GPS, then traveled to location B, then C, then D.
Timespan: A few days; device connected to charger in between, GPS switched off and on from time to time; GPS fixes and correct map display were acquired in A, B, C and D and during travel.
In D the device did power off due to empty battery.
After powering on, the location is given near location B (Hannover), not the last known location. (GPS disabled, blue dot is at B, when pressing `<R>` in the map view the map centers to there).
*(I actually have not been on the location shown, but maybe 1..2 km away; given the inaccuracy of T-Deck's GPS with bad reception it looks feasible that there was a time when it thought it has been there.)*
I think the last known location should be saved and used, or as a fallback no location, but not some location known at a random time in the past.
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
v0.9.10
Regards!
<!-- github-sync-id:4005105130 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I was at some location A, with GPS, then traveled to location B, then C, then D.
Timespan: A few days; device connected to charger in between, GPS switched off and on from time to time; GPS fixes and correct map display were acquired in A, B, C and D and during travel.
In D the device did power off due to empty battery.
After powering on, the location is given near location B (Hannover), not the last known location. (GPS disabled, blue dot is at B, when pressing
<R>in the map view the map centers to there).(I actually have not been on the location shown, but maybe 1..2 km away; given the inaccuracy of T-Deck's GPS with bad reception it looks feasible that there was a time when it thought it has been there.)
I think the last known location should be saved and used, or as a fallback no location, but not some location known at a random time in the past.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.10
Regards!
i am on it to fix this issue.
I think it is fixed in 0.9.11.