Wrong ETA at the end of the route in LT calculation
Posted: 09 Dec 2019, 14:42Hi, I was flying on Dec 6 and I noted that the ETA at the end of the route showed me 14:40 (LT) that was one hour more than the time I've been calculated. Looking into the ET to the next waypoint I realize the ETA at the end of the route seems was calculated with the wrong time zone (+1 UTC in my case)
Today I made some tests, I checked the date and time on the tablet and they were fine but, using GPS test app, I got the same wrong behavior with the local time, +2 hours from UTC. It was like the data comming from the GPS doesn't include the right UTC offset or the application is misscalculating that offset.
I've got a java error on the GPS test app screen that is supoused to show my location on the earth map.
Then, I made the same tests with my phone, a S8 with a recent version of android (9). All test worked as expected, no weird behavior, everything was fine.
I think this wrong behavor has anything to do witn the way the "modern" applications get data from the GPS if there is such a thing.
This is my tablet information:
Model: Nexus 7 (2013)
Android: 6.0.1
FiF: 24.31
If this is right (the way the modern applications get data from the GPS has changed) is there a way to apply a workaround for old android verions?
Today I made some tests, I checked the date and time on the tablet and they were fine but, using GPS test app, I got the same wrong behavior with the local time, +2 hours from UTC. It was like the data comming from the GPS doesn't include the right UTC offset or the application is misscalculating that offset.
I've got a java error on the GPS test app screen that is supoused to show my location on the earth map.
Then, I made the same tests with my phone, a S8 with a recent version of android (9). All test worked as expected, no weird behavior, everything was fine.
I think this wrong behavor has anything to do witn the way the "modern" applications get data from the GPS if there is such a thing.
This is my tablet information:
Model: Nexus 7 (2013)
Android: 6.0.1
FiF: 24.31
If this is right (the way the modern applications get data from the GPS has changed) is there a way to apply a workaround for old android verions?