Comment by peterleinchen
okay If it is a Jolla middleware then they might easily add those few lines according to the phone model. I was afraid it is a more global middleware. Now we only need Jolla's attention/willingness!
View ArticleComment by atlochowski
it's from IRC from 21 Apr: **mal** maybe that could be solved using some hack to add a constant value in the gps middleware to the timestamp coming from gps hardware 21:22 **mal** atlochowski is the...
View ArticleComment by peterleinchen
And agreed Jolla should fix this but I do not believe they care and I am not sure they could. GPS time is delivered from GPS firmware, no chance for an update middleware is QT? above fix is a...
View ArticleComment by peterleinchen
Sorry to be klein-kariert hier. But it is an okay workaround. The rollover date was 2019-04-07 00:00:00 GMT (1554595200). The fix would be: ts = gps.time // now t0 = 315964800 // GPS zero time tR =...
View ArticleComment by atlochowski
It's a good fix. If gps timestamp is before 2020-04-21 it gets device timestamp if gps time stamp is newer then 2020-04-21 it gets gps timestamp. Yes, but Jolla should add this missing weeks in gps...
View ArticleComment by peterleinchen
Which is then not the GPS timestamp but the device timetamp (which might be also totally off ;). You just need to add 1023 weeks to the timestamp :) Or was it 1024? oh, leap years ... But, to be...
View ArticleAnswer by atlochowski for Wrong date from GPS on Jolla 1
The newest version of OSMScout brings us workaround for this bug. lastUpdate.getTime() < 1587448500800){ console.log("GPS event timestamp is not valid!"); lastUpdate = new Date();
View ArticleAnswer by atlochowski for Wrong date from GPS on Jolla 1
@jiit can you report that? I know it's an old phone, but It would be nice any comment. For example "it's an old phone so we don't want to invest our time to fix that." or "we do our best to fix it"
View ArticleComment by Vesa.S
xtra_server connecton should use https https://wwws.nightwatchcybersecurity.com/2016/12/05/cve-2016-5341/
View ArticleComment by atlochowski
thanks for info. mal has some idea: **mal** maybe that could be solved using some hack to add a constant value in the gps middleware to the timestamp coming from gps hardware 21:22 **mal** atlochowski...
View ArticleComment by martonmiklos
I have managed to get this working by the following: NTP_SERVER=time.google.com #XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin #XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin...
View ArticleComment by peterleinchen
Did you shut down, waited a few seconds and booted up again? I would do so **with** taking out battery...
View ArticleComment by martonmiklos
If you look at this patch: https://gitlab.com/HardStyl3r/android_device_lge_g3-common/-/commit/208f79c790e97def2e57dfc6385b2823bf2b4aa0 they switched to xtrapath4-5-6 I bet the info came from here:...
View ArticleComment by atlochowski
I wrote about that on SailfishOS IRC channel and mal noticed that so will se what happen.
View ArticleComment by atlochowski
Jolla C uses different binary path than Jolla 1 Jolla C XTRA_SERVER_1=http://xtrapath1.izatcloud.net/xtra2.bin XTRA_SERVER_2=http://xtrapath2.izatcloud.net/xtra2.bin...
View ArticleAnswer by martonmiklos for Wrong date from GPS on Jolla 1
It seems that the Lineage OS folks are faced with the similar issue: https://gitlab.com/LineageOS/issues/android/issues/1446 It seems that some Qualcomm AGPS related binary paths needs to be updated:...
View ArticleAnswer by olf for Wrong date from GPS on Jolla 1
Related / duplicate of: https://together.jolla.com/question/201585/j1-gps-week-number-rollover-on-6th-april-2019/
View ArticleAnswer by atlochowski for Wrong date from GPS on Jolla 1
So it's clear now https://github.com/jdrescher2006/Laufhelden/issues/164#issuecomment-616813592
View Article