Related
Windows Mobile 6.1 Only
Thought of starting this thread to get an idea of GPS performance on OEM and Custom ROMS with different radios. According to most threads and my personal experience the GPS performance is sub-par on 6.1 and highly unreliable. It would be great if I can get some feedback on the following:
1. ROM Version
2. Radio
3. Time for Cold Fix
4. Time for Hot Fix
5. QuickGPS Version
I think this thread would help lot of members who rely on GPS navigation on a day to day basis to make up their mind on ROM/Radio combo - specially me.
Thanks.
#################################
Here's mine
1. ROM Version - Garmin DK 1
2. Radio - 1.65.17.56
3. Time for Cold Fix - over a minute / @ times under 20 seconds
4. Time for Hot Fix - under 10 seconds
5. QuickGPS Version - Version 1.00 919.717
Tried the official WM6.1: HTC_TyTNII_FRA_3.28.406.0_25.83.40.02_1.65.16.25_Ship
- Cold Fix was > 5mn
Back to the official WM6.0:
HTC_TyTNII_FRA_1.56.406.5_22.45.88.07_1.27.12.17_Ship
- Cold Fix is < 30sec
sebbes said:
Tried the official WM6.1: HTC_TyTNII_FRA_3.28.406.0_25.83.40.02_1.65.16.25_Ship
- Cold Fix was > 5mn
Back to the official WM6.0:
HTC_TyTNII_FRA_1.56.406.5_22.45.88.07_1.27.12.17_Ship
- Cold Fix is < 30sec
Click to expand...
Click to collapse
So you are back on 6.0 permanently? I have been debating on this for over a week now
Have a look at this link - no real answer to this issue but possibly one of the recomendations will work for you
http://forum.xda-developers.com/showthread.php?t=397728&highlight=quickgps
By the way I am on the official Vodafone UK update
ROM Version 3.28.161.1 WWE
Date 05/02/08
Radio Veriosn 1.65.16.25
Protocol Version: 25.83.50.02H
Cheers
Barney
I have tried many different 6.1 ROMs, and the GPS performance is usually about the same. I'll post my 3 most recent below, newest/current ROM at the bottom.
________________________________________
1. ROM: Shogunmark's Death V4.1
2. Radio: 1.58.25.17
3. Cold Fix: Over 1 minute without a jumpstart / 20 seconds using GPS Test (v1.04)
4. Hot Fix: Less than 15 seconds
5. QuickGPS Version - Version 1.00 Build 220.821
________________________________________
1. ROM: Garmin.DK.1
2. Radio: 1.58.25.17
3. Cold Fix: Over 2 minutes without a jumpstart / 45 seconds using GPS Test (v1.04)
4. Hot Fix: Less than 30 seconds
5. QuickGPS Version - Version 1.00 Build 220.821
________________________________________
1. ROM: HyperDragon IIIi (Diamond/Xperia build)
2. Radio: 1.58.25.17
3. Cold Fix: Over 1 minute without a jumpstart / 20 seconds using GPS Test (v1.04)
4. Hot Fix: Less than 15 seconds
5. QuickGPS Version - Version 1.00 Build 220.821
NotATreoFan said:
I have tried many different 6.1 ROMs, and the GPS performance is usually about the same. I'll post my 3 most recent below, newest/current ROM at the bottom.
________________________________________
1. ROM: Shogunmark's Death V4.1
2. Radio: 1.58.25.17
3. Cold Fix: Over 1 minute without a jumpstart / 20 seconds using GPS Test (v1.04)
4. Hot Fix: Less than 15 seconds
5. QuickGPS Version - Version 1.00 Build 220.821
________________________________________
1. ROM: Garmin.DK.1
2. Radio: 1.58.25.17
3. Cold Fix: Over 2 minutes without a jumpstart / 45 seconds using GPS Test (v1.04)
4. Hot Fix: Less than 30 seconds
5. QuickGPS Version - Version 1.00 Build 220.821
________________________________________
1. ROM: HyperDragon IIIi (Diamond/Xperia build)
2. Radio: 1.58.25.17
3. Cold Fix: Over 1 minute without a jumpstart / 20 seconds using GPS Test (v1.04)
4. Hot Fix: Less than 15 seconds
5. QuickGPS Version - Version 1.00 Build 220.821
Click to expand...
Click to collapse
Thanks for the detailed feedback.
If you don't mind me asking are the above results constants or random. I am wondering whether this odd behavior is device or device/radio/rom related. Some don't have this issue at all and some do. Beats me.
It's all very bizarre, I've been watching posts on this for weeks trying to see some kind of pattern, but there just doesn't seem to be one. Some people have serious problems (like me), others have perfect GPS, but not one of them seems to be on quite the same combination of ROM/radio/SPL etc - or rather those that are seem to be split randomnly between the two camps.
It's a very frustrating topic to get into, because you'll inevitably get people telling you the problem doesn't exist (because they've not seen it) or offer some magic bullet that just doesn't work.
For the record I'm using the stock HTC WWE 6.1 rom/radio. Whenever I try to get a lock just walking down the street, or on the bus, it can take up to 20 minutes at times. The other weekend I was actually using it in anger on a roadtrip, relying on it for directions, and it worked brilliantly for two solid days, with lock times mostly under a minute. It just doesn't make any sense. I'd say it was unreliable, but when I actually did need to rely on it, it came through.
1. ROM Based on HTC Official 3.29.707.0
2. Radio 1.65.20.29
3. ColdFix - 20-seconds - (you mean following a soft-reset right?)
4. HotFix - 2-seconds - (hotfix is when you have closed down your GPS App (TomTom in my case) and then restarted it but haven't soft-reset the device right?)
I am counting from after TomTom starts and immediately when it begins to talk to the GPS module (if you go to the GPS Status screen it initially says 'No GPS device!', then a couple of seconds later the little yellow/black circular symbol begins to flash and it says 'Poor GPS reception' - this is when I am timing it from from).
Andy
Boinng said:
It's all very bizarre, I've been watching posts on this for weeks trying to see some kind of pattern, but there just doesn't seem to be one. Some people have serious problems (like me), others have perfect GPS, but not one of them seems to be on quite the same combination of ROM/radio/SPL etc - or rather those that are seem to be split randomnly between the two camps.
It's a very frustrating topic to get into, because you'll inevitably get people telling you the problem doesn't exist (because they've not seen it) or offer some magic bullet that just doesn't work.
For the record I'm using the stock HTC WWE 6.1 rom/radio. Whenever I try to get a lock just walking down the street, or on the bus, it can take up to 20 minutes at times. The other weekend I was actually using it in anger on a roadtrip, relying on it for directions, and it worked brilliantly for two solid days, with lock times mostly under a minute. It just doesn't make any sense. I'd say it was unreliable, but when I actually did need to rely on it, it came through.
Click to expand...
Click to collapse
Agreed 100%.
Just when I tell myself it's working the problem starts again. I used to be so content with the 6.0 GPS performance.
Furthermore, I think the device plays a major role as well. There is no reason for 2 identical phones having stock rom updates to spit out two different GPS lock times. Although I complain about mine the longest lock time for me have been 3 minutes.
ADB100 said:
1. ROM Based on HTC Official 3.29.707.0
2. Radio 1.65.20.29
3. ColdFix - 20-seconds - (you mean following a soft-reset right?)
4. HotFix - 2-seconds - (hotfix is when you have closed down your GPS App (TomTom in my case) and then restarted it but haven't soft-reset the device right?)
I am counting from after TomTom starts and immediately when it begins to talk to the GPS module (if you go to the GPS Status screen it initially says 'No GPS device!', then a couple of seconds later the little yellow/black circular symbol begins to flash and it says 'Poor GPS reception' - this is when I am timing it from from).
Andy
Click to expand...
Click to collapse
That's awesome... I could only wish
kavi said:
Agreed 100%.
Just when I tell myself it's working the problem starts again. I used to be so content with the 6.0 GPS performance.
Furthermore, I think the device plays a major role as well. There is no reason for 2 identical phones having stock rom updates to spit out two different GPS lock times. Although I complain about mine the longest lock time for me have been 3 minutes.
That's awesome... I could only wish
Click to expand...
Click to collapse
I have just tested this again, just to verify...
Soft-reset, wait a couple of minutes for Kaiser to settle down and then start TomTom and open the GPS Status screen, wait for 'Poor GPS reception' to appear and start timing..
1. Cold-Fix this time was 28-seconds.
2. Hot-Fix this time was 6-seconds.
Still quite good though
I am actually sat in the house with the Kaiser next to the window but it is quite a clear day.
Andy
kavi said:
Thanks for the detailed feedback.
If you don't mind me asking are the above results constants or random. I am wondering whether this odd behavior is device or device/radio/rom related. Some don't have this issue at all and some do. Beats me.
Click to expand...
Click to collapse
Constant, give or take 1-2 seconds.
Edit-
To Boinng,
Although I have little issue getting GPS reception, I must say that when I was running Garmin's ROM, and one of Dutty's (don't remember which one of the 1000's), my GPS signal was great, but my software performed really poorly; sometimes only updating in 1 mile increments.
TT7 vs. TT6???
I seem to be getting much slower starts since I converted to TT7. I tried this morning and after 5 minutes, just ended up resetting my quick GPS and then it took about 45 secs.. I've done the change to "other NMEA . . . " and no consistent result.
I also have no idea why the radio would make a difference with this as I've always thought that only dictated your phone reception and that the GPS was in itself its own device. Any clarification would be appreciated.
Breakthrough?
I just posted this in another thread - http://forum.xda-developers.com/showthread.php?p=2393635#post2393635
Basically it looks like my own GPS performance has been improved substantially by switching from the 1.65.16.25 radio (the one which came with the original HTC 6.1 update) to the newer 1.65.17.56, which they seem to have quietly snuck out with a new version of the same ROM (the ROM itself is still 3.28.405 so I just used the radio only version someone posted).
I wouldn't say it was quite 6.0 level, but it's a lot closer, for me anyway.
I did have to install HardSPL 3.28 (to replace the stock HTC SPL 3.28) first before I could change radio, I suppose it's possible that had a bearing too?
Boinng said:
I just posted this in another thread - http://forum.xda-developers.com/showthread.php?p=2393635#post2393635
Basically it looks like my own GPS performance has been improved substantially by switching from the 1.65.16.25 radio (the one which came with the original HTC 6.1 update) to the newer 1.65.17.56, which they seem to have quietly snuck out with a new version of the same ROM (the ROM itself is still 3.28.405 so I just used the radio only version someone posted).
I wouldn't say it was quite 6.0 level, but it's a lot closer, for me anyway.
I did have to install HardSPL 3.28 (to replace the stock HTC SPL 3.28) first before I could change radio, I suppose it's possible that had a bearing too?
Click to expand...
Click to collapse
You hit the nail on the head!!! Worked like a charm for me. Cold sync under a minute and unbelievably IN DOOR syncing!! AMAZING!
ADB100 said:
I have just tested this again, just to verify...
Soft-reset, wait a couple of minutes for Kaiser to settle down and then start TomTom and open the GPS Status screen, wait for 'Poor GPS reception' to appear and start timing..
1. Cold-Fix this time was 28-seconds.
2. Hot-Fix this time was 6-seconds.
Still quite good though
I am actually sat in the house with the Kaiser next to the window but it is quite a clear day.
Andy
Click to expand...
Click to collapse
that was FAST!!!!!
im going to compare
1.58.25.17
1.65.16.25
1.65.20.29
1.65.24.36 ---> downloading .....
Boinng said:
I just posted this in another thread - http://forum.xda-developers.com/showthread.php?p=2393635#post2393635
Basically it looks like my own GPS performance has been improved substantially by switching from the 1.65.16.25 radio (the one which came with the original HTC 6.1 update) to the newer 1.65.17.56, which they seem to have quietly snuck out with a new version of the same ROM (the ROM itself is still 3.28.405 so I just used the radio only version someone posted).
I wouldn't say it was quite 6.0 level, but it's a lot closer, for me anyway.
I did have to install HardSPL 3.28 (to replace the stock HTC SPL 3.28) first before I could change radio, I suppose it's possible that had a bearing too?
Click to expand...
Click to collapse
I have tried this and it works sometimes but not constant - at least on my device. This bug is killing me. I rely on Navi almost everyday and would hate to go back to 6.0.
Also I have noticed that even hot fix times vary with 6.1.
With 6.0 I used to get hot fix under 15 sec. indoor all the time.
My question to all....
Although we blame OS, Radio and SPL can this symptom be device related too?
i am also in the same boat as most of you the GPS just plain sucks ass on my kasier no matter what the radio rom combination it seems. i use the application Seagate which is just like quickGPS and i also use quickGPS sometimes its super fast on cold starts sometimes its more than 25 minutes and i give up because of battery drain for nothing. i dont want to go back to 6.0 period so i hope we can all work on this and get things working properly. i wonder what .dll's are in control of the GPS and what parts of the radio rom also control the GPS that would be a good place to start and see what we can modify a little for better performance.
Using GPS Test:
1. ROMeOS V.3 http://forum.xda-developers.com/showthread.php?t=406346
2. New NEON 1.65.24.36 http://forum.xda-developers.com/showthread.php?t=406995
3. Time for Cold Fix- about 1 minute
4. Time for Hot Fix- <10 seconds
5. QuickGPS Version 1.00 (220.821)
6. AT&T in Central PA
austinsnyc said:
i am also in the same boat as most of you the GPS just plain sucks ass on my kasier no matter what the radio rom combination it seems. i use the application Seagate which is just like quickGPS and i also use quickGPS sometimes its super fast on cold starts sometimes its more than 25 minutes and i give up because of battery drain for nothing. i dont want to go back to 6.0 period so i hope we can all work on this and get things working properly. i wonder what .dll's are in control of the GPS and what parts of the radio rom also control the GPS that would be a good place to start and see what we can modify a little for better performance.
Click to expand...
Click to collapse
It took a few SR's before the GPS and the new radio clicked, but it did make a huge diffrence here in AZ. I had the same 20+min (if ever) fixes on a cold start before and getting an indoor fix was a laugh, hot or cold. I just did an indoor hot fix in under 20 secs! Cold fix indoors is somewhat dependant on where, but after running visual GPS, no issues
Death V.4 plus the latest Kaiser (not neon) radio seems to be the charm for me, but maybe it IS handset/local specific.
I just wish the handset silencing issue was fixed, but I digress . . .
WM 6.1 HTC OEM official
OS 3.02.405.0 WWE
radio 1.58.26.20
coldfix -- about 1 minute
hotfix -- 5-6 seconds
I was surprised to have hotfix this fast. and the battery goes way longer than on 6.0.
great radio indeed.
Hi guys,
I think the subject says it all...
I have a Diamond which suffers from serious GPS lag (not fix!). This means that when I'm driving, my car is always up to 50m ahead of what TomTom or IGO tells me that I am...
I'm thinking about changing my device as nobody seems to know the cause of this...
So, I wonder if Rapheal has the same issue or not...
HastaSSSS
Here's what i tested for you on the way to work...
Using TomTom6 (6.032), driving at 30mph, using the tip if the blue arrow as my position (same as i always used on TytnII) i would say my car was no more than 5m behind were i should be. No issue going down the right road or turn.
Same situation as johnk1973. No 50 meters lag, but aprox. 5 meters.
Same problem here on Raphael, TT7 is 50 meters behind. Will test it tonight if it also occurs with TT6.
Same here with tt7 and igo8....
Now this is going to get complicated....
I had Diamond before and NEVER experienced GPS lag.
I tried almost every official and cooked ROM and had no problems with GPS.
Recently I switched to Raphael....
And guess what... GPS lag !
I used my Diamond and Raphael in identical conditions, with the same app (iGO 8).
I'll try to test it more.
I'll post if I find anything useful to you.
Cheers,
Sh*t...that means Raphael is a "no go" for me...
Unless we solve the problem...whatever it might be...
Please keep on posting your findings about this issue...I like very much Diamond and Diamond Pro....but I'm not willing to have a device without 100% functionality...
HastaSSSS
I have a Touch Pro with iGo8 installed. I realised this "50m lag" on my business trip this Monday but I thought it was due to the speed of the car (I was driving very fast for the most of the time). Now I see the problem might be a little more complicated.
On the other hand the 50m is not so bad - I never had a wrong turn, the acoustic signalization of iGo8 is very good. Nevertheless, I would be glad if this could be fixed...
And another thing - I'm not sure if you are aware of the charging problem while using GPS. My Touch Pro actually stopped charging because of overheating and was running only on the battery. So be aware of this fact too.
But this is a different issue, I'm sure there is a thread for this.
I dont have the problem with TT6.
I second this issue, both with TT7 and IGO8 (haven't tried it with another one yet)
Guys I had GPS lag on TT7 when I fist used it (Only tried it for 5min) it was awful. Mainly everytime I turned a corner whilst driving.
Then I did the following changes:
\start\settings\system\external GPS -> Set GPS Program port COM4; Hardware NONE; Access Manage GPS automatically.
Hit ok, wait 10 secs, switch off the device and then soft reset.
Now go to TT7 change the GPS prefences, to use bluetooth device and selected COM4.
No my GPS is perfect now, no problems at all. Have tried it with two different ROMs and no problems.
I have TT7 installed on the main memory and the maps on an Sandisk 8GB Class 4 SDHC card.
Radio ROM is 1.02.25.19 if that helps? and AGPS is turned on a up-to-date.
BTW it was exactly the same when using google maps.
Did you also try it by just setting tomtom gps to bluetooth? I'll give that a shot anyway before going into the register... tnx for the tip
Please keep in mind that you'll get an update of your past position only once per second. This means: The faster your velocity the more inexact the position will be, because the distance you'll pass in this second becomes longer and longer:
@30kmph: ~8m
@50kmph: ~14m
@80kmph: ~22m
@100kmph: ~27m
@130kmph: ~36m
Additionally there is the inaccuracy which comes with GPS: In good times you may have ~10m divergence on average. But with weaker signal (which one may have driving in a city) it will become even more. So keep in mind that GPS will tell you, where you've been one second ago (plus the divergence).
By the time I get my Diamond Pro, I'll collate this at the same time with my X500, which has a build in Sirf3 receiver.
I am having a slightly different issue with my TP using iGuidance 4. Although the unit aquires a signal faster than any other device I have used in the past, it seems to lag or freeze as I drive. It will not update the time, speed or position unless I press a button or something on the screen. There is another thread on XDA (I think in the Diamond or Kaiser sections) that claims to have solved this issue, but the fix doesn't work on my Touch Pro (in fact it completely freezes my iGuidance requiring a soft reset).
Hi,
I'm using Ndrive and TomTom 7.
on NDrive I don't have any problem, it's fast.
on TomTom is slow..
I thing the problem is on TomTom using this GPS of Raphael.
WizP said:
Guys I had GPS lag on TT7 when I fist used it (Only tried it for 5min) it was awful. Mainly everytime I turned a corner whilst driving.
Then I did the following changes:
\start\settings\system\external GPS -> Set GPS Program port COM4; Hardware NONE; Access Manage GPS automatically.
Hit ok, wait 10 secs, switch off the device and then soft reset.
Now go to TT7 change the GPS prefences, to use bluetooth device and selected COM4.
No my GPS is perfect now, no problems at all. Have tried it with two different ROMs and no problems.
I have TT7 installed on the main memory and the maps on an Sandisk 8GB Class 4 SDHC card.
Radio ROM is 1.02.25.19 if that helps? and AGPS is turned on a up-to-date.
BTW it was exactly the same when using google maps.
Click to expand...
Click to collapse
these settings are the settings that are preset. Hence nothing changed. the lag on the diamond is bad but this is awful.
WizP said:
Guys I had GPS lag on TT7 when I fist used it (Only tried it for 5min) it was awful. Mainly everytime I turned a corner whilst driving.
Then I did the following changes:
\start\settings\system\external GPS -> Set GPS Program port COM4; Hardware NONE; Access Manage GPS automatically.
Hit ok, wait 10 secs, switch off the device and then soft reset.
Now go to TT7 change the GPS prefences, to use bluetooth device and selected COM4.
No my GPS is perfect now, no problems at all. Have tried it with two different ROMs and no problems.
I have TT7 installed on the main memory and the maps on an Sandisk 8GB Class 4 SDHC card.
Radio ROM is 1.02.25.19 if that helps? and AGPS is turned on a up-to-date.
BTW it was exactly the same when using google maps.
Click to expand...
Click to collapse
these settings are the settings that are preset. Hence nothing changed. the lag on the diamond is bad but this is awful.
Using Igo8 very intensively with my TP, no lag at all. Compared it this morning with my VW passat stock nav system, and again, i notice no lag.
I have the settings in the posts above, and have very little lag. I am using QuickGPS instead of AGPS, but all else is the same. My main probklem is how long it takes to get a lock (much longer than on my old Kaiser), but since installing DCS's ROM and doing a hard reset immediately after that does seem to have improved - I often get a lock from cold within a minute now..
Rowan
I believe the reason that some people are getting horrible GPS lag while others get nothing has to do with the Radio ROM versions that came installed with the device. Most custom ROMS don't update the Radio ROM. It's 12am and I'm posting this from my TP, so I'll just tell you that the Radio thread is stickied in the Raphael ROM dev forum.
EDIT: http://forum.xda-developers.com/showthread.php?t=439566
Hi,
HTC has released a new ROM for the Fuze.
Among other things, it contains an "A-GPS Update: Speeds up the time it takes the GPS to get a fix on your location", and "Quick GPS is still recommended for the optimal operation of GPS based applications and services".
Does anyone know whether it's feasible to implement only this part of the ROM in a Tilt?
My GPS reception is variable (using the internal GPS), no matter which ROM or radio I use (some are better, my current combination works best for me). The only way I obtai an extremely fast GPS fix is by using an external BT GPS (I purchased an GlobalTop G66 Plus, and I now obtain a fix within 10-15 seconds).
I have AGPS turned OFF because it doesn't work with IGO8 (had no problems at all with AGPS and IGO6).
I've tried every solution in the book and have carefully read all related threads here. None have worked for me.
So my question *only* refers to the suitability of implementing that portion of the Fuze new ROM.
Thanks.
I would think that you would be restricted by the hardware of the phone and not the software
Well, if you're referring to the incompatibility of IGO8 and AGPS, it's a given.
I really don't know if this is a general issue or there is something wrong with the unit (MTCD GS - Xtrons TL702AP) that i have.
Namely after each hard start (leaving it off overnight), the unit resets clock to 13:00.
I tried disabling GPS and network synchronisation, but to no avail... It boots up with 13:00..
The BATT wire is properly hooked up since the radio stations remain.
The other problem is that also the GPS does a cold start and takes forever to get a fix. Leaving the GPS sync on takes sometimes until "13:30" to correct the time.
Is this normal?
In my case a cold boot repair resulted in a 6:00 time ...but after 2-4 minutes I got gps fixed and therefore time synced.
I think the 13:00 is due to the time zone (you can force the time zone)
With respect to the gps fix....what ROm version do you have? Perhaps you need to upgrade rom
Enviado desde mi D6603 mediante Tapatalk
Yeah, the 13:00 is due to the timezone - it may be 0:00 in China... the date also resets to Jan 1st 2016.
I am running the MTCD GS 1.96a_1 (Nov 8), which came with the unit. Xtrons also sent me the "latest" version, which is the same.
NeoTO said:
Yeah, the 13:00 is due to the timezone - it may be 0:00 in China... the date also resets to Jan 1st 2016.
I am running the MTCD GS 1.96a_1 (Nov 8), which came with the unit. Xtrons also sent me the "latest" version, which is the same.
Click to expand...
Click to collapse
could you find a solution?
Well, never buy a cheap Chinese product again.
In my case, there was basically no real technical support. They did offer to replace the unit, but the new unit is the same. It works, I can't say that, but that's it.
We don't have any metalization on the windscreen and the GPS receiver is positioned directly looking at the sky. It takes forever to get the fix (can take up to half an hour) and even after that, the GPS position quality is sub-par. Navigation software (Sygic) often has problems tracking the roads, GPS speed is reported in m/s without any decimals and the speed in km/h (or mph) jumps in large steps of more than 3 km/h. The unit often crashes while in idle and does a cold restart as the result, resetting GPS and time in the process. Radio reception is bad on these units even with additional signal booster.
Hi All - I have a Joying Intel Sofia head unit (not sure the exact model), but the date is suddenly switching to a 2001 date. This seems to be happening via GPS, and the head unit is prioritizing GPS date over network date. I have tried a few apps from the app store that will switch to NTP date, but the unit repeatedly overrides this. Switching network time/date off in settings doesn't help either. This knocks the head unit offline because of certs. I've seen this a few times on the forum, but no hard fix. Anyone?
Same issue here, the issue is caused by GPS Week Number Rollover (WNRO) issue, it can be fixed in Sofia-1-C9-Server-V1.0.apk but we need a programmer who knows how..
the date is exactly 1024 weeks behind the real date and it can be fixed by calculating 1024 weeks on to the gps date.
for example like this (example code)
JavaScript:
long gpsTime = location.getTime();
// Adding 1024 weeks for chips with GPS Week Number Rollover issue
// 1024 * 7 * 24 * 60 * 60 * 1000 = 619315200000L
if ((gpsTime > 0) && (gpsTime < 1546300800000L))
gpsTime += 619315200000L;
i hope there is anyone here that knows how to implement it in the smali code.
Please try this post from @IG_Vasilich
[ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V9a3 2018-04-22
========================================ACHTUNG=================== =================WARNING========================================== =====================================================PELIGRO======= AS WITH ANY UNSUPPORTED SYSTEM...
forum.xda-developers.com
It's much simpler, although requires the same action on every reboot/cold boot.
surfer63 said:
Please try this post from @IG_Vasilich
[ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V9a3 2018-04-22
========================================ACHTUNG=================== =================WARNING========================================== =====================================================PELIGRO======= AS WITH ANY UNSUPPORTED SYSTEM...
forum.xda-developers.com
It's much simpler, although requires the same action on every reboot/cold boot.
Click to expand...
Click to collapse
That fixes the problem temporarly but it's not a real solution
Dang, I came here looking for a fix for this problem - it took me a while to figure out why I couldn't get internet on some apps, then figured it was certificate date related, which lead to why the time/date isn't getting set properly. Shame there is no easy fix - toggling the network update off/on is only a temporary fix, not a proper solution
No need to take root
localos said:
No need to take root
Click to expand...
Click to collapse
Someone has tried? It works?
Thanks.
I've tried it - it works, about 75% of the time. If it gets a quick fix of the gps before the google service starts, it's ok. But if it takes longer to get a fix and time update, you have to go and restart the (force stop) the google service. It auto starts, then, auto closes - not a bad solution, better than going to the menu, but would be nicer to just update the default date to a more recent start time
localos said:
No need to take root
Click to expand...
Click to collapse
Thanks this works for me, after ages looking for the solution