yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] d33ps1x:
GPS will use triangulation of cellular tower signals to get it's initial ballpark fix. It's possible that you are seeing your first vector of the triangulation being estimated. It's a phenomenon that can be seeing here as well but I believe it's likely purpose is to get you in the ballpark world-wise to help choose the right agps data to narrow the range and then move to acquiring sats.

Are you finally settling on your proper location after a while or is it stuck in that offset location even after acquiring sats and triangulating you?
[HTC Wildfire S] realaaa:
to confirm - the latitude and longitude values in GPS status are not changing at all! When I run the application the values are empty then it quickly refreshes and returns the same values as I posted before. They are rock solid and do not change at all even when I move/run around.

So it's not actually offset but rather the _same_ data returned by GPS every time which seems very strange, like those values had been stored/cached somewhere, and got stuck somehow.

Is there any cache like that in GPS implementation in Android? I have disabled "allow mock locations" in settings-applications-development but it did not change anything...
[HTC Wildfire S] d33ps1x:
Playing with it now. Checking out some factory confs, lib files, etc.
[HTC Wildfire S] realaaa:
thanks for your help mate! should you need any additional info just let me know.

UPDATE I think I fixed it! so I thought that I'd verify that those dreaded coordinates are really coming from the GPS sensor so I looked around and downloaded a small and very simple app - GPS view by Oliver Knabe.

It simply shows you raw data from GPS sensor, that was exactly what I wanted to verify. I am not sure what it did, but it FINALLY showed me my correct location, and after that the GPS status (and Google maps) started to return correct and up-to-date locations as well!

I have confirmed that now the latitude/longitude data in GPS status is dynamically updating, so everything seems to be working now!

To summarise:

from what I have observed the GPS status (and Google maps etc) were stuck for some reason

they were returning exactly the same location as if it was cached/saved somewhere and they simply extracted it (rather than querying GPS sensor)

after running GPS view it actually queried GPS sensor and showed actual location

apparently it changed something in the system, which made all other GPS applications to show actual coordinates as well

so - does anyone want to step in and explain what the hell was that all about?? :)

my theory is that indeed the location was cached somewhere, and because of some glitch the GPS applications refused to get new data from the GPS sensor, and simply used this stored location. This could happen due to time mix-up (at some stage because of NTP my date was reset to 1980, but then I corrected that).

Cheers everyone, now lemme think - what did I want to break next? :)

UPDATE 2 just tried a quick real life test with runkeeper and it was really not good but at the same time maps and GPS status lock in very fast, probably fault is on the runkeeper app side? Will keep an eye on how it all goes and post back here.

UPDATE 3 well MapMyFitness did not perform well too. But what I noticed just now - "GPS status" was hanging for a long time (more than two minutes) and could not fix on the satellites at all, so then I tried to run "GPS view" again which acquired location very fast, and after that "GPS status" starting locking in fast again. So it seems that GPS got stuck again and GPS view kick-started it again? hmm, to be continued...

UPDATE 4 ok it's not fixed yet... now "GPS view" has started to return the same weird location (-27°, 133°) AND it shows incorrect time as well (07.01.1980) - also see the screenshot. This confirms that there is some screw up with the time, BUT the system time is correct, so I'm a bit lost now. Anyone, any ideas please??

UPDATE 5 seems like I have killed this topic haven't I? :) GPS still broken :(

UPDATE 6 ok now after couple days (I have not done any changes) the GPS status and GPS view are unable to lock anymore, and do not return any coordinates at all, but interesting part is that applications can use GPS now! E.g. Google maps etc can get the location. Did not have much time yet to dig further into it, but will keep an eye on it.
[HTC Wildfire S] Saftpackl:
Hey, I'm also still stuck on this one.

Installed the latest nightly of CM7 yesterday, installed the fix -> showed the wrong location in maps.

In gpsview, i got the static latitude and longitude, but I get 6+ satellites sometimes (Height and Speed is "not available" however).

Still any ideas? :-)
[HTC Wildfire S] realaaa:
not yet, for me there is no change yet, now the GPS more or less (slowly) works (maps, navigation, etc), but both GPS status and GPS view are unable to return any coordinates.

will need to do some more research on it, but don't have much time lately (and also because it yes slowly but works it is not so critical anymore)

as I have any news will post it here
[HTC Wildfire S] careylui:
How to set permission?
[HTC Wildfire S] miguelca:
In first place I want send a BIG THANK YOU to d33ps1x for his restless work. :cool:

I've just edited my gps.conf manually and replaced NTP Servers with 3 Portuguese active ones. Installed GPS Status and rebooted, went to one of the rooms with sky view (2nd floor appartment) and after downloading AGPS data I managed to fix 8 satellites in a snap. :D

Sygic immediately found its position, which took ages before this fix. I have to comment that the rom I use already has a GPS fix "onboard".

It already worked fine with Google Navigation and NDrive, until yesterday when the NDrive GPS app started exiting for no apparent reason.

So I installed Sygic which I already knew as an excellent GPS solution because I had used it before.

I guess that the first (until a few minutes ago only) NTP Server and XTRA_SERVER_1 could be suffering from too much traffic.

So now I configured three NTP servers and setup the XTRA_SERVERS like in your patch. Needless to say that I'm very happy now. :D

No more endless waiting for satellites to fix. ;)

Thanks again for your help, mate. :)
[HTC Wildfire S] d33ps1x:
Cool stuff. Thanks for the positive feedback.

Sent from my cm7.2 Wildfire S
[HTC Wildfire S] nour111:
thanks i well try it
[HTC Wildfire S] scott_doyland:
I have had various GPS issues with CM7. Tried the GPS fix in the original post but it seemed to put my location miles away. I did various fiddling with gps.conf etc. Eventually reverted to original CM7 files and then wiped cache partition via cwm and gps sprung into life. Did a few reboots, wiped cache again and dalvik cache just for good measure.

GPS is still fine, locks in seconds by the window.

Why wiping cache worked I don't know but it seems to have helped.

No harm in trying, it may help. Put CM7 files back first to start from a clean slate though.

Scott
[HTC Wildfire S] kp.nikhil:
Gps doesn't work after I install this :-(

HTC WILDFIRE S

ROM:CM7 nightly

290 mb internal+1gb s2e
[HTC Wildfire S] d33ps1x:
Just did two nightly fresh upgrades on a row and applied this and works great.

Sent from my cm7.2 Wildfire S
[HTC Wildfire S] scott_doyland:
Hi, do you mean wiping cache worked for you, or the gpsfix?

Regards

Scott
[HTC Wildfire S] QQboss:
does not work for me, after that patch, its telling me im a half country away :(
[HTC Wildfire S] gauravjuneja01:
Working fine...

I am using cm nighlies.....

Some days ago, I flashed this patch, But not working me....

But after installing latest nightly from eoghan.......

It is working very well..... in all applications....

Thanx a lot for it...:cool:
[HTC Wildfire S] Barjo_MLS:
I tried it on CM 7.2 and it's work well. Thank you man
[HTC Wildfire S] kp.nikhil:
Can I have 1.0 version download link?
[HTC Wildfire S] d33ps1x:
You can have 1.2. Will put it together tomorrow.

Sent from my cm7.2 Wildfire S
[HTC Wildfire S] kp.nikhil:
Thank you :-)
[HTC Wildfire S] kp.nikhil:
Update?
[HTC Wildfire S] QQboss:
I tried reflash the ROM twice, but still no success with GPS. It didnt show me anything at all sometimes... now just the same as before, it shows me that im half country away :(... can someone help?

Im running CM 7.2 by Alquez, the latest nightly from 26.2.2012...

I did change in the GPS conf file like it was written here. And I cannot show it to you right now cuz its sayin that new users cannot post outside links lol...:mad:
[HTC Wildfire S] d33ps1x:
New version 1.2 GPS fix!

New updated version 1.2 of GPS fix in first post!

Be patient with initial false locks and give it a few minutes to lock up your initial location!
[HTC Wildfire S] eoghan2t7:
Lol 1.2 makes my phone think its in England when I'm really in northern Ireland ;)
[HTC Wildfire S] d33ps1x:
Well maybe you spent a drunken night in Dublin and ended up in Gallway Bay? :P

Still working on the initial lock setting. It smoothed out after a while though?
[HTC Wildfire S] QQboss:
sss agendadi

No change after updating to 1.2 version. I changed the servers from pool.ntp.org and added my country. Still showing me im half country away. No change after while as i waited for fix... what can be wrong here?
[HTC Wildfire S] kp.nikhil:
Gps not working
[HTC Wildfire S] QQboss:
I just found out that, the GPS is showing position, but thats all even when its totally wrong. When I was goin home from school its 30 minutes trip so I turned on GPS. The marker was not moving at all. It was just pinned down to that one spot that was showing me all the time.

Maybe it helps figure out whats wrong :)
[HTC Wildfire S] d33ps1x:
Do me a favour guys and wipe your cache partition in Mounts and Storage, reboot and try again. Curious.

I did so and it removed whatever cached starting position it had for me.

Back again today though. Going to remove and edit some settings for intermediate positioning and see if I can't get it to function like a well behaved GPS...
[HTC Wildfire S] QQboss:
I wiped twice, didnt help its still the same
[HTC Wildfire S] d33ps1x:
Definitely to do with the initial reference location. Watching the debug info fly by

50.1.430 lat

97.1358 long

Accuracy 0.00000

Tell me something I don't know.

No worries. I'll figure this.
[HTC Wildfire S] Saftpackl:
Yay, GPS is working now =)

I made a backup of my CM7, installed a ROM where GPS was working before, let the GPS lock, recovered the backup, opened GPS Test, updated the AGPS data and let it lie around outside for a few minutes :)

Only thing is, that when I have WLAN activated, it still locks on the same wrong position as before, but I mostly won't need GPS in situations where I have WLAN.
[HTC Wildfire S] ultrablu3:
can i use this tutorial for htc chacha?
[HTC Wildfire S] QQboss:
well... im having issues with my gps since i flashed this fix. I cant get a fix to my possition and I have already reflashed my ROM 3 or 4 times. Via GPS status I can see that i get a lock on satelites, but just cant get my possition. It says "your possition is temporarily unavailable".

just to be clear here... i flashed this fix, it didnt work so i reflashed new clean ROM. It doesnt work anymore even without the fix.
[HTC Wildfire S] 07blackwater:
Before you flashed your ROM did you wipe dalvik cache, cache partition and factory reset?
[HTC Wildfire S] QQboss:
yup I did... I will try to flash another kernel, but thats the last thing i can think of :confused:
[HTC Wildfire S] gauravjuneja01:
GPS is fixed for CM users...

GPS is fixed for CM user... just read this post and apply no need to flash any zip....

It is amazing...

http://xdaforums.com/show...&postcount=234

Thank You...
[HTC Wildfire S] greavous420:
Link Not working.

http://xdaforums.com/showpost.php?p=23949139&postcount=234
[HTC Wildfire S] gauravjuneja01:
Try

http://xdaforums.com/showthread.php?t=1560984
[HTC Wildfire S] realaaa:
hey @d33ps1x thanks for continuing your work on this! well guess what - I'm back and I have the same problem! :)

today I updated to the latest Update-CM-7.2-RC1-marvel-03_24_2012.zip (with data and cache wipe). After that GPS kinda worked in applications (maps etc) but GPS status could not return any coordinates (bottom of the screen with parameters empty).

so I installed d33ps1x_Wildfire_S_GPS_Fix_1_2.zip and after rebooting and running GPS status it locked in and returned coordinates quite promptly BUT again it is wrong - and AGAIN it's the same Latitude 27°6.437'S and Longitude 133°7.152'E (as before rock solid and does not change)

after that I set NTP_SERVER to oceania.pool.ntp.org, did reset in GPS status, rebooted and tried again - no luck, it still shows the same coordinates!

And I'm quite sure it won't be consistent and it will work in applications in the next couple days (as it did before).

mate what can I do? any specific information that I can provide you so we could understand what is happening? I know it works sometimes and sometimes returns those weird coordinates, but so far I fail to see any system in this behaviour.
[HTC Wildfire S] intel007:
After installation of cm7 I normally flash this gps fix, then in manage applications settings I clear data for network location.

Then it should work.

first lock could take upto 10 mins although it might show its locked just keep waiting till it shows your correct location, after that it should lock very fast each time.

PS I'm using copilot and in its settings it shows which satellites are locked.
[HTC Wildfire S] honda_hany:
cm7

i have done this update but when i run maps it show location 50 km away any help ?
[HTC Wildfire S] greavous420:
Use the solution posted by gauravjuneja01. I had that problem but now get a pretty much perfect lock inside a house just through GPS.
[HTC Wildfire S] gizmolek:
Solution posted by gauravjuneja01 doesn't change anythink in my last CM7nightly. I must wait few minutes to have a gps fix.

---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------

Each time I run any sports GPS apps (or maps) at the beginning I see a dummy GPS location, and after a few minutes location change to real location. Than everything is OK.
[HTC Wildfire S] greavous420:
Fair. I'm finding it quicker to get a fix myself(Nightly from 24th) and it gets a more accurate fix as well.
[HTC Wildfire S] d33ps1x:
Works with CM9
[HTC Wildfire S] RiesVLD:
Thanks m8, i can use a tool like this :p
[HTC Wildfire S] balakrishnan111:
Will this work on JikantaruROM????? or only for Cyanogen????
[HTC Wildfire S] krishnanms:
Working great on cm7.2 .. 12 locks in 10 secs ....the location was initially less accurate and later when it locked fully it was extremely accurate ...
[HTC Wildfire S] caihooligan:
Hello there,

I live in Italy and I'm trying to update the gps.conf to my country's servers.

Can anybody check if I'm doing it right so I can proceed to flash the patch?

Default gps.conf settings are:

# Network Time Protocol Server: #

#################################

NTP_SERVER=north-america.pool.ntp.org

NTP_SERVER=pool.ntp.org

#####################################

Servers for Europe and Italy are respectively:

NTP_SERVER=europe.pool.ntp.org

NTP_SERVER=it.pool.ntp.org

This is what I've done.

# Network Time Protocol Server: #

#################################

NTP_SERVER=europe.pool.ntp.org

NTP_SERVER=pool.ntp.org

#####################################

I'm wonder if adding a third NTP_SERVER specific for Italy will enhance my locking speed even further. Would this be correct?

# Network Time Protocol Server: #

#################################

NTP_SERVER=europe.pool.ntp.org

NTP_SERVER=it.pool.ntp.org

NTP_SERVER=pool.ntp.org

#####################################

By the way I'm running Unofficial CM 7.2-RC1 on a HTC a510e (not UMTS)
[HTC Wildfire S] abhi8569:
Thnx.....now my gps working fine.....just changed port to 76 and added asia server....
[HTC Wildfire S] caihooligan:
I'm having problems editing the file with European and Italian Servers.

Can you have a look at the post just above yours? Otherwise, do you mind if I PM you?

Thanx
[HTC Wildfire S] Tordenflesk:
nevermind, fixed it.
[HTC Wildfire S] king_lud:
I am having trouble editing gps.conf. Running 920 Text Editor as root, it says 'saved' but the file is not updated. Script manager says I only have read permissions when I try to edit it (as root) and in terminal emulator, after typing su <enter> then 'chmod 755 gps.conf', it returns 'gps.conf read-only system'.

Does anybody have any tips on how to edit this file?

EDIT: Installed Root Explorer and changed the permissions - got a really quick gps fix indoors after I had edited it to my local servers, so a great tool!
[HTC Wildfire S] modpunk:
d33ps1x: Please read http://blog.cryptomilk.org/2012/07/12/android-cyanogenmod-and-the-gps-fix/
[HTC Wildfire S] sikander3786:
I have no doubt in saying that installing this GPS fix has messed up my phone's GPS. Yeah it locks in less than 2 sec but the off-set is as big as 1000 KM. Damn!

Before installing this, I was getting slow locks but at least it was accurate. I am on latest CM 7.2 by alquez.

So, the bottom line, it doesn't work for me as some others also mentioned in the middle pages of this thread. Can't say how it worked for so many other people.

Probably there is a problem with the SuplRootCert or something else which I am unable to figure out.

The only way to revert back to my previous state is probably to re-flash. Or if any one could please provide me with the default CM 7.2 SuplRootCert and agps_rm files so I can give it a try. I couldn't find these in the CM 7.2 zip archive.
[HTC Wildfire S] sikander3786:
Success!

For all of those running CM and having off-set problem with this script, try installing FasterGPS from the Play Store.

https://play.google.com/store/apps/...ult#?t=W251bGwsMSwxLDEsIm9yZy5mYXN0ZXJncHMiXQ..

That is all I did and now everything is working as fine as it should be. Locks are fast, and most importantly, it is accurate.

@d33ps1x:

There wasn't much difference between your gps.conf and the one from FasterGPS. However, the latter removes the agps_rm file provided by you. May be that is the problem? Probably you can spot the differences and further update this script.

Thanks for all you work. ;)
[Samsung Galaxy Nexus] alai.jmw:
First, 4.0.2 is the latest version for the GSM GNex, right?

I thought it was... anyway. I got my phone yesterday and unloced the bootloader and rooted, but didn't install CWM or do anything else that actually required root. The phone did apply an OTA update, but I don't remember if it was before or after I rooted.

Anyway, it is now saying 4.0.1 and 'check for updates doesn't find anything'.

...so, that's wrong, isn't it? Any idea why? I thought rooting didn't mess with OTA (unless you start messing with things too much, of course).

Thanks in advance!
[Samsung Galaxy Nexus] alai.jmw:
Oh, and it is yakju.
[Samsung Galaxy Nexus] Dr Tone:
No only updated builds of 4.0.1 have been pushed to the GSM version.
[Samsung Galaxy Nexus] joshnichols189:
4.0.2 was for the Verizon version.
[Samsung Galaxy Nexus] alai.jmw:
Ah ha!

Thanks guys!
[Samsung Galaxy Nexus] mcgon1979:
Just thought I'd mention that I am on a GSM GN and got asked to update to 4.0.2. today. There is a thread in general about it. I took screenshot too. But the update didn't apply right. I downloaded it and hit install and restart but nothing happened. hmmm...

Maybe I was offered it by mistake...

The thread is here http://xdaforums.com/showthread.php?t=1395047
[Samsung Galaxy Nexus] krohnjw:
Given that JBQ posted factory images of 4.0.2 for the Maguro/Tuna build I think it's safe to say it's going to OTA. Multiple GSM owners have received the update notification.

Updates roll out SLOWLY and are flagged by IMEI. If your IMEI isn't flagged to get the update yet there is no number of checkins that will prompt you to download it. Normally updates have rolled out over a few weeks. This process was explained by someone at Google a while back. The OTA goes to a small group during which time they can ensure that it isn't causing issues. If that goes well it's expanded to a larger group and then subsequently all devices as it scales up.
[Samsung Galaxy Nexus] qwerp_:
GSM version has 4.0.2 update, but not pushed over.

i have manually downloaded the stock image from google and manualy flash it.

i am now running 4.0.2

http://code.google.com/android/nexus/images.html

what i did was,

backup my system (just incase).

Factory Images "yakju" for Galaxy Nexus "maguro" (GSM/HSPA+)

(all file extract from the 4.0.2 (ICL53F) image)

flash bootloader

flash radio

flash recovery

flash system

and reboot, and presto. you are on 4.0.2.

my experience, this does not remove all your data.

just similar to a upgrade for me.

a side note. i am running everything stock..
[Samsung Galaxy Nexus] misso4:
Hey guys ,

The gray color on the setting panel is not good enough :(

Hope someone can replace it with black color .... it will be amazing :)
[Samsung Galaxy Nexus] samizad:
I have a black theme, including plain black wallpaper. It looks amazing on the Super AMOLED. It would be great if the settings could be turned black.
[Samsung Galaxy Nexus] mrvirginia:
that background is likely going to be part of the framework. i wouldn't imagine it would be xml code since it's gradient, but i could be wrong...

edit: it's called within the Settings.apk so i'll break it apart and take a look really quick.
[Samsung Galaxy Nexus] vapotrini:
I meant to come here and ask the very same thing. Would be nice if someone could change it. Would be even better if they could add in even more things lol.

That said, I have to ask. Why would you want to limit yourself to just black? Transparent ftw.
[Samsung Galaxy Nexus] mrvirginia:
i have no clue. i've been poking around in both framework and settings and can't seem to find the call in =/

edit: it's bothering me because i've changed this on accident within the Settings.apk on Gingerbread
[Samsung Galaxy Nexus] pukemon:
my question is "where is the Blackout Rom?". black and/or transparent all the way across the board and rom ftw. and who is doing black gloss painting for the nexus mod?
[Samsung Galaxy Nexus] ock:
It should be under framework-res.apk

res\drawable-nodpi\background_holo_dark.png
[Samsung Galaxy Nexus] misso4:
its super amoled display :p which is black is the best color ever ;)
[Samsung Galaxy Nexus] pukemon:
transparent with black blackground for wallpaper achieves the same thing and lets you kinda see what's going on behind that window sometimes.
[Samsung Galaxy Nexus] mrvirginia:
thanks mate! i just saw that someone confirmed my thoughts, that it was indeed pulled in from framework. i figured this was the case, though, since you see this background in other non system apps.

i don't have my environment set up here at work, but as soon as i get back home i'll figure out where this is in Settings.apk and change it to black for you guys and post it here as a flashable (if no one beats me to it :p)
[Samsung Galaxy Nexus] misso4:
Waiting u ....
[Samsung Galaxy Nexus] misso4:
Still waiting......
[Samsung Galaxy Nexus] misso4:
Still waaaaaaiting :(
[Samsung Galaxy Nexus] vapotrini:
lol! Dude... give the guy a chance to breathe. He doesn't owe us anything.
[Samsung Galaxy Nexus] [hfm]:
Seriously. No one is doing this for a living, need patience.
[Samsung Galaxy Nexus] misso4:
Lol I know ,but I`m soooo excited
[Samsung Galaxy Nexus] [hfm]:
You're this excited for a color change on settings? How often do you use that?
[Samsung Galaxy Nexus] CBConsultation:
I think you should take your 6 posts and go to the waiting room and let our devs breathe.
[Samsung Galaxy Nexus] misso4:
I think its not your buisness !
[Samsung Galaxy Nexus] CBConsultation:
It is my business when people are hassling the devs in here. You kids need to learn some respect. The devs are here for free and don't need to be rushed with their work. Too many kids just expect things to be handed to them just as fast as they can ask for them.

Grow up and act like an adult. You're not entitled to anything.

And remember, this is a PUBLIC forum. When something gets posted it is EVERYONE'S business. Silly internet kids!