I have noticed two things after flashing my N95 to V12..
The main thing I have eagerly awaited for is the inclusion of AGPS and was one of the first features I have tried out. It has succesfully downloaded from the net with the update (you can see it connecting) and that it had found some satellites for me (all five appear in MAPS as being "found"😉. But none of these are filled and hence the system does not "lock" your position. I have let it go on like this for over 30 mintues and it still does not lock.
This situation happens once every four goes with the GPS now and is quite irritating. I am theorising that the AGPS update did not download the correct information for my part of the Worild for some reason, so that it does not correctly find the right satellites in the sky properly.
The other problem I have is Flash runs like crap these days. I have some childrens songs stored on my phone that I use to play to my 20 month old son and it use to work fine as if it was played from a PC. After the upgrade, the same file will stutter, slow down to a painful speed and have have problems with the sound.
Has anyone else noticed any of this as well?
Thanks,
Have you tried testing agps vs normal gps only?
Stand in one spot and wait for a lock with agps, then go into the GPS data application and go Options > Positioning Settings and untick agps.
Leave it an hour or so for the gps receiver to 'cool off' (for a fair test)
Try again in the same spot with unassisted gps only.
What GPS app and what song reader do you use?
Where are they installed?
Yeah.. no matter which app, its the same - considering that all of them use the underlying Locations API..
I got the feeling either I was sent the wrong AGPS information or something wrong with the code on it.. Dont know..
pa49 wrote:What GPS app and what song reader do you use?
Where are they installed?
No Song reader - just the built in Flash app that plays the Flash SWF files.
GPS app - Any GPS maps - Nokia Maps, Locations etc etc. All seem to be affected.
I assume you have verified in settings that aGPS is enabled (you can't see this by checking that phone connects to internet, this could be the Maps application doing so..).
Verify aGPS in ..Settings\General\Positioning
=> Positioning Methods: 'aGPS' and 'Internal GPS' enabled.
=> Positioning server:
- Access point:. ...an IAP for common Internet access (not sure a WAP configured with proxy ports will do it..).
- Server address: supl.nokia.com
Also if you start N.Maps, have it running for a couple of minutes then Exit and switch to "Log" application => View recent data connections, you should see your prev.selected access point (IAP) => Select it and view how much data that has been submitted and received. If "0" it has not contacted the AGPS service at all! If some 1kb sent and 4kb received it has contacted it and received info.
Regarding "...I am theorising that the AGPS update did not download the correct information for my part of the Worild for some reason, so that it does not correctly find the right satellites in the sky properly."
=> This is not how it works. As soon as the internal GPS has found one or several satellites, has identified them (but hasn't got any lock/fix cause it's waiting for a complete download of datastream with orbit/sat.position info) it sends this info about which satellites it's receiving info from (e.g. which sat's it can "see"😉 to the aGPS server. The aGPS server should then return the orbit information about theese sat's to the phone, hence providing the GPS with the data needed to get a fix.
Superswede:
I havent change any of the standard AGPS settings so all of that recommendation is already there.
The GPRS is working fine and does download AGPS information (I made sure of that before I'd called it a bug)
Finally, about the method of AGPS - I have found that the data connection comes in before a satellite is even "found". From my old days of the HP65/69xx WM 2k3/05 series, AGPS is basically a lookup table that gets downloaded to your phone and that your phone then determines the correct satellites according to a time & position table (which is a few k's in size even for the HP series as well).
If the firmware code is buggy with the correct time/positioning cross referencing, then it can cause this issue whereby it knows where the satellites are, but because it cannot cross reference properly, then it does not establish a proper lock.
Maybe someone from Nokia can be so kind to confirm?