yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] strictlyrude27:
It should be INTERMEDIATE_POS, and it should be a single number - either 1, 2, or 3:

INTERMEDIATE_POS=1

I'm pretty sure it's a boolean setting, so it can be either 0 or 1. This basically allows the device to report a location before it has a lock. Essentially we're trading accuracy for TTFF. Not sure what setting it to 2 or 3 would do - I would expect that the setting just checks if it's zero or non-zero, so my guess is it'll have the same effect as INTERMEDIATE_POS=1.

It's used in tandem with ACCURACY_THRESH, although I'm not sure what units that number is in. It seems to be meters, but I can't guarantee that. I've seen between 1000-10000 for that number.

In my gps.conf tweak, I use INTERMEDIATE_POS=1 and ACCURACY_THRESH=3000 - you might try setting ACCURACY_THRESH higher to be in a "lock" state with lower accuracy, but if that number is too high your accuracy will not be good enough to use GPS, even if it's locked.

Feel free to mess around, let me know of your results.
[Vibrant Android Development] agosine:
Thank you for the information. I will play with the numbers and see what effect that has.
[Vibrant Android Development] tsnow247:
I'm still having trouble with the daemon starting.

After a reboot it's fine, but a few hours later it won't start.

Sent from cm7
[Vibrant Android Development] avengethis1:
i think my phone hates gps. this method has still not worked for me. was working with just moving gpsd and angry gps now no luck there.
[Vibrant Android Development] }{Alienz}{:
Can't get the flashable clockwork to work in several different nightlies. On #70, after flashing the daemon would activate it maps but after 30 minutes outside, would STILL not lock anywhere. On GPS Status, no GPS icon would appear (as if its not using it at all) and no locks would ever happen.

On Nightly #80, I can no longer get the GPS icon to start flashing. I'm not sure how to make it work, any assistance is appreciated.
[Vibrant Android Development] strictlyrude27:
I think most people have just been reflashing the fix if it starts to falter.

I'm currently testing the current gpsd (Nightly #84) and so far I'm having good results, although that's not definitive. Will update to 1.5 if this works for me, but I'll leave 1.4 up.
[Vibrant Android Development] Joy2DaWurld:
Any chance this can work for the JVR/JVQ roms? Personally I'm not a fan of CM7 anymore but great job regardless! :)
[Vibrant Android Development] strictlyrude27:
Nope, that's a whole different thing.. In TouchWiz-based ROMs, the GPS is heavily hooked into the TW framework. CM7 doesn't do that.
[Vibrant Android Development] }{Alienz}{:
Finally got it working and it locked with 18 ft in 20 seconds after a reboot but now I can never ever get a lock if the phone isn't freshly rebooted. Oh sigh.
[Vibrant Android Development] strictlyrude27:
Which ROM? I'm having the same issues right now with Trigger 0816, but there could be an issue with that build (Roman implemented external GPS, but it looks like there was a bug in it). Maybe try a nightly?
[Vibrant Android Development] bosox86:
just installed nightly 95 and this gps fix works perfectly. Maps and Navi are accurate to about 70 feet. GPStest locks onto 9 of 11 birds in about 15 seconds sitting on the window sill.
[Vibrant Android Development] strictlyrude27:
Please let me know if you can replicate these results after your phone's been on for at least 24 hours. Some can, some can't. I'm trying to narrow down why this is happening, but it's so sporadic for me.
[Vibrant Android Development] }{Alienz}{:
That was with CM7 Nightly 84 and the 1.4 GPS fix applied on top of it. Are you saying I should just install a nightly and not install the GPS fix and test?

As far as I know CM7 doesn't have the GPS working out of the box...am I wrong?
[Vibrant Android Development] macgar32:
70 feet?

That is not accurate enough to do navigation or any tracking of running or exercise...

I am having around the same accuracy with drift and it is not accurate enough for daily use...

I guess I will continue to use my work BB for GPS tracking.
[Vibrant Android Development] bosox86:
Gps stopped working completely, GPStest sees nothing. Phone will not sleep after charging unless I reboot it off the charger.
[Vibrant Android Development] p()()pypants:
Well this worked yesterday right after I flashed it, down to 6 feet.

Half hour later it would search and search with the flashing icon and never lock. Now today after a reboot even it won't lock even outside in open air where it locked the first time.

Running biffmod 131. Glitch kernel. V6 super charger memory script. no clocking or volting done.

Can anyone link me to the hardware gps fix? Tag lines of the same topic don't pull up jack in these forums.
[Vibrant Android Development] strictlyrude27:
I wonder if the name of the file matters. I rename lto2.dat to lto.dat, but maybe having it as lto2.dat works best..?

Please download http://gllto.glpals.com/7day/v2/latest/lto2.dat, place it in /data/gps, give it 0755 permissions, then reboot. See if you get better results..

I'm really sick of this GPS issue :(

Also, someone please try the no-gpsd flash? I'm currently running Trigger and its default gpsd is the same as the fix.

EDIT: I'm trying out having both lto.dat and lto2.dat. Who knows if this is going to work, but I'm running out of ideas. Could someone please pull me a gpsd from the latest CM7 nightly so I can try with that?
[Vibrant Android Development] p()()pypants:
0755 is rwx rw rw right? Got it placed and permissions set just waiting to make sure

thats correct
[Vibrant Android Development] p()()pypants:
Rwx, rx,rx rebooting
[Vibrant Android Development] p()()pypants:
Ha, nope...

Now it doesn't even show the icon for searching at all.

I just added the file you placed there... Ill try deleting the other. If it doesn't work ill just reflash your zip.
[Vibrant Android Development] p()()pypants:
K. Deleted other file left the "2" file. Locked in 5 second at 30 feet.... Will continue to test see if it locks again and see if it locks a couple hours from now.
[Vibrant Android Development] p()()pypants:
K it locked a second time after closing and re opening maps. 9 secons 30 meters. 2 more second 6 meters all in open air.

Will report back later today to see if it sticks.
[Vibrant Android Development] strictlyrude27:
Excellent news! I'm really interested in if GPS can still lock after, say, 12 hours, as well as if the results may be replicated after a reboot. If that's true, I'll PM you to test out v1.5 for me before it goes live. I am downloading lto.dat upon boot, but I'm not sure if a reboot is required to use that - this depends on if that data is injected into the GPS when it's first used or on boot. We'll have to experiment a bit, but I don't have time to do it myself really.

I also found a typo in my init script to download the latest lto.dat - seems it was actually forcing a download upon boot all the time rather than after 3 days of downloading an old one. I might have it refresh data on boot permanently though.
[Vibrant Android Development] p()()pypants:
Alright. In the mountains right now on edge network, took 25 second to lock but shot from 30 meters to 9 right after initial lock. Also rebooted locked again in a similar fashion... I think this is gtg now.

want a copy of my data/gps folder?
[Vibrant Android Development] strictlyrude27:
I don't need a copy of the folder per se, but certainly list the contents of /data/gps . I think you downloaded lto2.dat and kept it named that way, right? Also, did you modify /etc/gps.conf at all? Let me know of anything you changed from the original 1.4 fix.
[Vibrant Android Development] p()()pypants:
Sorry, just posted but this is great.... Rebooted, opened maps as soon as sd scanning completed. In just 32 seconds, before i could even load the full resolution of the map on edge network after startup, I had a 50 meter lock. Tap map, tap arrow, tap map, tap arrow, tap map, tap arrow ect. Resulted in immediate display of closer lock... 50m, 30m, 20m, 9m, 8m, 7m, 6m.....

I think I have a working gps again.

Thanks are due!
[Vibrant Android Development] p()()pypants:
I downloaded lto2.dat, deleted lto.dat, no other changes...
[Vibrant Android Development] strictlyrude27:
I'll package up 1.5 and test it tomorrow, then release the next day if all goes well. From what it sounds like, it'll go well hopefully :)

Could you test this for me? Delete lto2.dat, reboot, then redownload it and give it 0755 permissions. Do NOT reboot, then test GPS. I've been injecting lto.dat like this from the init script, but I want to see if it requires a reboot before it takes effect.
[Vibrant Android Development] ronin4740:
I'm also running Trigger (8/22) and not having any luck with the GPS. The LTO2.dat trick doesn't seem to have fixed my issue... I get a list of GPS satellites in the GPSTest app but they don't show any signal... On the rare occasion that they do and I do get a lock it doesn't last more than a few minutes.

Not sure what Roman has done with GPS since earlier versions of Trigger (where it worked pretty well and a reboot would almost always get it to work for an hour or so)... It's driving me nuts as I'd like to be able to use Mapmyride to track my cycling workouts...
[Vibrant Android Development] iwapu:
A noobie question:

Does GPS in Vibrant has to have network (WIFI, 3G or EDGE) to work?
[Vibrant Android Development] ronin4740:
I retract my previous post. GPS fits work on, trigger 8/22 after inserting lto2.dat, deleting lto.dat and installing the 1.4 hours fix script. Just took a while to get the first lock. Can provide more info if needed
[Vibrant Android Development] smali26:
will this work on any other ROM or only CM7?

Kindly let me know.

Cheers!!
[Vibrant Android Development] strictlyrude27:
CM7-based ROMs such as MIUI should also work.

Good stuff. I'll try to release 1.5 today, but I'm really pressed for time lately. More likely it'll be released by the weekend.

Technically no, but it's helpful to triangulate the position to a smaller area. You'll need data on boot, however, as that's when I download the latest long term orbit data. I have to think about how to deal with someone not having data for up to 5 days.
[Vibrant Android Development] p()()pypants:
Ok so heres what happened so far.

I deleted ito2.dat. Rebooted, decided to test gps first without any ito.dat at all (or so I thought ) and got a lock in 30 seconds to 7 meters right away....

Wth? So I checked data/gps and ito.day was already there, it had automatically replaced ito2.day once I deleted it.

So whatever you have the boot doing is making it replace ito.dat when there is no file present but if ito2.dat is there it places no new ito.dat file in data/gps.

Is there any difference in file content from the ito.dat file automatically loaded in the folder and the ito2.dat you had me dl?

Like I wonder I'd this ito.dat file is going to lock a second time and hours later again like ito2.dat was doing for me....

I'm going to delete ito.dat, reboot, delete ito.dat, dl ito2.dat and run immediate gps test to still get what you wanted to test done but just thought you should know about this development.
[Vibrant Android Development] p()()pypants:
K. I deleted ito.dat after reboot. DL'd the file again from the forum (its no different from yesterday right?) Placed in data/gps, opened maps and locked in 12 seconds.

So findings... reboot isn't necessary after dling ito2.dat. But reboot without any ito.dat or ito2.dat does automatically place a new ito.dat file into data/gps but doesn't seem to lock as fast as the ito2.dat file and in not sure it will be as reliable over time...

Just so you know the only other file in my data/gps folder besides ito2.dat is svstatus.txt.

Hope this all has helped with your testing lmk if its not explained clearly enough.
[Vibrant Android Development] strictlyrude27:
Thanks for the help!

Last test: delete the file /etc/init.d/90getgps_lto, delete everything /data/gps, reboot; then download lto2.dat again and put it in /data/gps, then try GPS again. You'll need to do an adb remount at a shell before you can delete the init script.

/etc/init.d/90getgps_lto tries to download the latest lto2.dat if you don't have one or if yours is old. Originally I renamed it from lto2.dat to lto.dat, which is why it's appearing over and over for you. There should be no difference between lto2.dat and lto.dat (that you see on your phone, anyway) but the difference in name may change how the that GPS data is injected. Without having GPS driver source I can't really explain how or why this works.

svstatus.txt is also expected to be in there. It likely doesn't hurt, but it might help. It gives the status of current satellites. Again, without the GPS driver I can't really tell if this helps or not.

I'll upload a script version of 1.5 shortly.
[Vibrant Android Development] }{Alienz}{:
So does it look like 1.5 will resolve the GPS not locking after some time of the phone being idle without using GPS?

That was my only gripe with it, GPS Fix 1.4 would lock but ONLY after a fresh reboot and never afterwards.
[Vibrant Android Development] strictlyrude27:
Hopefully. Based on p()()pypants' testing anyhow. Again, without GPS code to look at I'm kind of in the dark as to what works and what doesn't. It's quite empirical.
[Vibrant Android Development] jad3675:
Excellent, glad this is getting worked out. I thought I had mentioned to use lto2.dat, though.

John
[Vibrant Android Development] strictlyrude27:
Dear all -

V1.5 SCRIPT version is available for download in the OP. I'll try to get a CWM flashable up today but I have other things going on.

Please delete /sdcard/GPSFix if you've previously used the script version of the fix; then unzip the GPSFix folder to /sdcard. Open a terminal and run:

su # if you're not already a superuser
cd /sdcard/GPSFix
bash GPSFix.sh

Note that I haven't personally tested this fix yet, but based on user testing this should be better at getting locks long after boot (i.e., reboot should not be required). I'm keeping v1.4 up as well because others had very good luck with it. But give 1.5 a try if 1.4 didn't work out.

Finally, note that you MAY need a second reboot before the LTO data kicks in after it's initially downloaded. I might just set it in the init script to automatically reboot an extra time if this turns out to be an issue. Personally I needed a second reboot, but YMMV. Please report your results so I can send out V1.5.1 if needed.
[Vibrant Android Development] strictlyrude27:
You did, but I thought you renamed it to lto.dat.. my mistake, I must have misundestood :o
[Vibrant Android Development] jad3675:
No worries, thought maybe I was wrong.

Glad you're running with this.

John
[Vibrant Android Development] p()()pypants:
Ok... This is awesome.

Deleted initd file. Deleted all of data/gps (including svstatus, but saved a copy just in case) and rebooted. Replaced ito2.dat in data/gps again opened maps...

Locked in 7 seconds! Closed. Task killed. Reopened, locked in 3 seconds (all in unobstructed open air).

Saweet. Will reboot. And report. Well report again later today to make sure it sticks.... But I think this is it!
[Vibrant Android Development] p()()pypants:
Reboot and relock went fine of course. No files changed automatically with initd gps file gone, of course.

Will leave phone on now and report later but I suspect it will go the same as last night and work fine.

Again I'm on biff 1.3 with glitch hl, v6 super charger memory script, originally 1.4 gps fix with the mentioned alterations to this point of clearing initd file, data/gps folder reboot and manually placing Ito2.dat back into data/gps. just in case others want to recreate the exact situation that's got me here. I'm sure strictlyrude will have it all packaged neatly though soon n hopefully it will work on cm7 builds across the board.

Thanks for the hard work to this point n to others this idea came from, glad I could help a lil as I of course get to benefit from the results!
[Vibrant Android Development] strictlyrude27:
p()()pypants, after your test you will want to run the 1.5 shell script; that lto2.dat is good for no more than 7 days, and I delete it and get a new one every 3 days with the init script. FYI.
[Vibrant Android Development] p()()pypants:
K, thanks for the heads up.
[Vibrant Android Development] p()()pypants:
Mine also took the double reboot as well after running the script to get a lock. Thanks again!
[Vibrant Android Development] strictlyrude27:
V1.5 CWM now available for download (both with and without gpsd). Enjoy.

Please let us know of your results. In particular, if you flash and it doesn't work initially, try rebooting. I am wondering if I need to add an automatic reboot after downloading the latest LTO data before the data is injected to the GPS. If enough people see that behavior, I'll update all variants to 1.5.1 with the extra reboot.
[Vibrant Android Development] creeve4:
What gpsd is included with this newest update?
[Vibrant Android Development] strictlyrude27:
Still from Nightly#54. That's given the best performance so far, I think; I've tried gpsd from #78 and #84 and neither would lock. if you're feeling adventurous and willing to run some tests for science, maybe flash the no-gpsd and try out the gpsd from your current nightly..
[Vibrant Android Development] Toddw:
GPS Fascinate

Will this work for the Fascinate? If not is there a method that will?
[Vibrant Android Development] strictlyrude27:
It might. But flash at your own risk. Report back if it works out and I'll post a link in the Fascinate forum.
[Vibrant Android Development] d_phekt:
Didn't seem to work for me on MIUI Revamped + Bali 2.0. Any suggestions on how to get it to work?
[Vibrant Android Development] cashyftw:
Wow this is the first time my GPS has ever worked on my vibrant!! I'm running miui newest version, thank you so much.

Sent from my GT-I9000
[Vibrant Android Development] reocej:
It works, first lock may take a while. If you have the angry gps app, try deleting gps data. Also, d/l gps status and clear/redownload agps data. Also, do a couple of reboots after installing. Cheers.
[Vibrant Android Development] d_phekt:
YES!! Got it working, and locked 6/12 birds within seconds indoors. Great work to all involved.
[Vibrant Android Development] iwapu:
Flashed 1.5 over 1.4 and confirmed working great on the latest MIUI ROM.

With data + wifi, I got the best results - locked in seconds and got 26 feets accuracy near window.

It also works without data or wifi even though it takes a couple of minutes to lock and the accuracy is above 120 feets.
[Vibrant Android Development] }{Alienz}{:
This actually works! FINALLY! 1.5 works for me now! And I think it works even after the phone has been idle! Yay. Achieved 15 feet accuracy.
[Vibrant Android Development] MadJoe:
Awesome! First GPS lock I've gotten in weeks! 1.5 did the trick. Running latest Trigger, stock kernel.

Sent from my rough sketch of a Vibrant on a brick.
[Vibrant Android Development] p()()pypants:
So last night and this morning I'm still getting locks, I think the longevity of the fix is proven now. Hopefully it passes the one week mark with the auto update of the ito2.dat file!
[Vibrant Android Development] strictlyrude27:
Thanks for your testing :) If it does fail, a reflash will wipe lto2.dat and force a re-download anyhow.. but at least, flashing once a week is way better than flashing daily..
[Vibrant Android Development] MadJoe:
I love that tapatalk finally got the thanks working in the mobile app, but the sexuality-questionable flowers that it choose to represent said thanks...well, they question every single thing manly about me, really. So I hope that helps you to grasp just how appreciative I am that you fixed my GPS for me.

Sent from my rough sketch of a Vibrant on a brick.
[Vibrant Android Development] ew:
Thanks for the fix. GPS is finally workable for me - even though I am not experiencing the same success that others have reported.

With 1.4, after about an hour or so of not using the gps, I had to reflash and battery pull to get the gps working agail. With 1.5 a reboot seems to do it, and the locks seem to be much quicker. However, I do not have the longevity that others have reported (after about 1 hour of idle time I don't see any birds without rebooting).

However, this is soooo much better than before.
[Vibrant Android Development] Djapatos:
nope still nothing

idk why but my GPS just won't work. I flashed the 1.5 which works for everybody but not for me. and yea I flashed the right way... I even tried rebooting
[Vibrant Android Development] iwapu:
At the first time you need data connection. Did you try testing it with data and wifi?
[Vibrant Android Development] sada23:
You dont have to have data connection for GPS to work. You can try deleting the existing GPS data. Use AngryGPS is necessary to delete the GPS data. Then Flash Fix GPS from OP using CWM. Reboot. It takes clear sky and a while to get the Satellites locked. After that you are good to go.
[Vibrant Android Development] coasterman927:
anyone know if this mod is relevant to MIUI.us 1.8.26?
[Vibrant Android Development] asatnik11:
Gpsd still sucks on nightly 102 with v1.5 nogpsd. It works about the same with the gpsd v1.5 comes with as it did with v1.4. It seems that when GPS is running and the screen turns off or rotates then gpsd flakes out until reboot. Has anyone else noticed this behavior? I've seen the same on every cm7 nightly and no matter what GPS fix I use. If I don't turn off or rotate the screen it works great!
[Vibrant Android Development] ronin4740:
http://xdaforums.com/showthread.php?t=1239058 any chance of the OP using these files for a CWM flashable v1.6 alpha test? :)
[Vibrant Android Development] strictlyrude27:
Feel free to flash 1.5 nogpsd and rip out that gpsd.. I'm not convinced that this recent spate of GPS drivers from other phones will work, and even if they do they'll likely require hooking into the Samsung framework, meaning they won't work for CM7-based ROMs. I think the only way we'll get a perfect GPS is if drivers actually drop, which is pretty doubtful.
[Vibrant Android Development] ronin4740:
I'll try. I've already flashed the 1.5 with gpsd and it's working fairly well... Where I currently have issues is if an app lets the phone sleep the GPS gets turned off even if the app is running and using it. This makes the iMapmyride app not usable for me.

Could you confirm that to get back to the original gpsd I'll need to wipe data/factory reset, clear cache, wipe davlik then reflash my current ROM? Wished I'd backed up the files as it would probably be simpler...

...Once I have time to revert I'll flash the 1.5 nogpsd and see if I can figure out which files go where from the Vibrant4G GPS leak...
[Vibrant Android Development] strictlyrude27:
You don't need to wipe or reflash anything if you want to change gpsd or remove the fix. If you're running vanilla CM7, just open up the flashable and pull the gpsd file from /system/vendor/bin to restore the "original" gpsd.

I'm not entirely sure I completely understand what you plan to do. Do you just plan on trying this gpsd with the fix, or the gpsd by itself?
[Vibrant Android Development] iwapu:
It seemed that GPS stopped working from time to time. Had to reflash 1.5 to get it working again. Anyone gets sort of stable GPS with this fix?