[Captivate Android Development] Rrryan2:
Yes, it has issues, sorry. Not sure what happened as I flashed a version that was basically identical without issue. After if I remember right I just signed and zipaligned it before uploading. Maybe something got corrupted in one of those operations or I made some other dumb mistake. I'll look into and try to get a revised version out in a day or two.

Was trying to finish that off and take a day or two off from GPS, maybe I got in too much of a rush. :o

Didn't think I made any changes that would have caused any cahnge in LTO refresh rate in 1.1b1. Is it possible it was happening for you on 1.0 too and just never got noticed as the issue was never really in focus before?

In general that behavior matches my experience on 2.0. 1.0 is faster TTFF but less stable tracking, lower SNR and higher DOP. I've not been able to replicate your intermittent start failure issues.

Yeah. Sorry 'bout that. :o

Odd. Haven't seen that, and none of the changes in 1.1b1 should really have affected anything like that.

I did change the permissions to secgps.conf to allow changes to the settings in LbsTestMode to update secgps.conf. Maybe verify your settings against the instructions in the OP? If that doesn't help I may need to rollback to locking secgps.conf like I had in 1.0...?

I like Root Explorer (paid - well worth it IMHO) but ADB trumps all of them if you really want to know for certain.

gldata.sto = general GPS data written by the daemon. Includes last known fix etc., updates each time you use GPS

lbsdata.sto = locally stored networks/towers with known locations. Helps provide approximate location for first fix based on what towers/networks it sees.

lcs.socket = 'pipe' that AGPS data goes through. Timestamp changes each time it's used.

Default Android timestamp for some files if they haven't been updated directly by the OS recently. No biggie.

Damn, you have a lot of question. :)

This means you got a good LTO refresh on 1st boot after install, which is good news. It should update after 24 hours. 2.0 seems to do it at boot most to all of the time for some reason, but 1.0 is mostly better about doing it once a day. It's really only an issue if it gets more than a few days old.

The permissions of them turned out to not be much of an issue, and modifying them (under 2.0 at least) was less than helpful and not necessary.

I really need testers and quality feedback in IRC, esp. for 1.1. One of the bigger annoyances I've had lately is that I'll post up a beta which will get 200+ downloads but only a handful of feedback reports, which makes it difficult as hell to figure out if it's really working.

Addressed previously; dropping it to 40 was an attempt to get better mobile tracking by discarding reported locations outside that range. It turned out to help little if any and I reverted back to 50 in versions after 1.0. I haven't even dwelt on making everybody change it in LBSTM because it doesn't seem to really do anything to help or hurt performance.

Depending on who you ask, you should wipe Dalvik (and/or /cache/) when flashing *anything*. Since it adds such a delay I'm trying to get it working without doing so and since it works most of the time without I haven't added it into the instructions. It does seem to help sometimes when things don't start working automagically.