yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Q&A, Help & Troubleshooting] beaver6d9:
Hopefully I'm not too late to the party on this thread... First things first... I am running CM7 Ba2TF and am having a similar issue. Thanks for mentioning the various options you've tried, will save me from messing with it in my car.

There may be hope, though. When I mount the drive, I actually do get access to mp3s, yet they are on the ones on my internal memory card and not my external card like I am used to. I didn't see this particular quirk mentioned in your post so if you haven't tried that, it's certainly better than nothing.

If it's super duper important, I haven't had any issues with external SD card mounting in my car whenever I had a stock based rom, namely darkside and alien.

I have been googling around a bit on this and it looks like it might just be a rom issue. They can't all be perfect, I suppose, but try putting them on your internal card and see how that mounts.
[HTC Flyer, EVO View 4G] robroy90:
For those of you who have rooted a Sprint Evo View, is there any ROM (stock or otherwise at any version 2.x or 3.2) that allows the WiFi tether app (any version) to work reliably?

After much frustration with a rooted Evo and a rooted Thunderbolt, the only tethering which was stable and reliable for me was the official (and for an additional monthly fee) carrier-installed hotspot app.

Not the route I want to take for multiple reasons. If anyone has any experience with this and can detail a configuration that I can reproduce it would be much appreciated.

Thanks in advance!

-R
[Captivate Android Development] Rrryan2:
Note: This project has been abandoned. Use at own risk.

See http://xdaforums.com/showthread.php?p=18699097#post18699097

pb3 Captivate Gingerbread GPS Tweaks

This is a package of tweaks and modifications to GPS configuration on Samsung Captivate under Gingerbread. Tested so far under KH3 (Pinnacle, Captivate I897 2.3.4) but is derived from XXJVS 2.3.5 GRK39C 2.3.6 Nexus S i9020A and should work on any deodexed, I-897/I-9000 Gingerbread ROM/modem.

Users of Odexed ROMs should delete /system/app/AngryGPS.apk from the .zip before flashing, and if desired substitute an odexed XXJVS AngryGPS.apk.

WILL NOT WORK WITH FROYO ROMs.

WILL (Probably) NOT WORK WITH CM7 OR MIUI

Localizing for your Country/Region

This BETA version is localized only for North America. As the North American pool is about 90% US-based servers anyway, this setting is likely adequate for most users throughout North America. If desired, NTP server localization (i.e. us.pool.ntp.org, ca.pool.ntp.org, europe.pool.ntp.org etc.) can be changed by editing line 1 of /etc/gps.conf to the desired NTP server. See http://www.pool.ntp.org/zone/@ for server details for your region.

Installation Instructions:

IMPORTANT: In order for this to work properly you must adjust your SUPL settings after flashing!

Download the file and flash in CWM3 recovery.

Apply the SUPL configuration settings in AngryGPS as described below.

Make sure GPS is turned on.

Open dialer and dial *#3214789650# or *#*#3214789650#*#* to start AngryGPS

Settings -> General Settings:

Test Mode: S/W Test

Operation Mode = MSBASED

Start Mode: Hot start

Settings -> SUPL Settings

Server FQDN Type: Custom Config

Server: supl.google.com

Server Port: 7276

Server Type: UMTS SLP

SUPL Secure Socket: ON

AGPS Mode: SUPL

SSL Type: Google Server

Download: https://code.google.com/p/captivate-gb-gps-tweaks/downloads/list

Problems/Issues should be reported at https://code.google.com/p/captivate-gb-gps-tweaks/

Changelog:

Beta 2: (Initial Public Beta Release)

gpsd daemon from GRK39C 2.3.6 Nexus S i9020A

gps driver from GRK39C

minor changes and additions to gps.xml from GRK39C

Beta 1:

Latest GPS-related binaries from XXJVS (I9000 Gingerbread 2.3.5)

Tweaked configuration files gps.xml and gpsExtLNA.xml

SSL Secure SUPL enabled for privacy/security - no more broadcasting your location in the clear over the Internet every time you use your GPS

Local LBS enabled - keeps a local registry of wireless networks of known location to speed re-acquiring initial fix in those areas

Tweaks to gps.xml and gps_ExtLNA.xml:

extraneous debugging code removed

position smoothing re-enabled

local LBS re-ennabled

LBS sync days set to 1

Dynamic mode set to pedestrian for most frequent position updates

SUPL re-aiding time reduced to 5 min.

Files Included:

gps daemon and script from XXJVS Samsung I9000 Gingerbread 2.3.4

AT&T SSL certificate from KB1

Uuencoded SSL certificates from KB1

AngryGPS.apk from JVS

GPS driver from JVS
[Captivate Android Development] syanz87:
Great work bro... keep it up
[Captivate Android Development] DAGr8:
good to have you back .. how about them NexusS files ?

fyi JVS = GB 2.3.5 :eek:
[Captivate Android Development] Rrryan2:
Beta

2

is derived from GRK39C 2.3.6 Nexus S i9020A

:p
[Captivate Android Development] Peaster111:
@Rrryan2

Heck of a great start. I'm only seeing two satellites though now.

... But hey one is always showing a signal strength of over 230 using the gps test app! I posted the issue on your link.

I'm on Pinnacle 1.2

As always, thanks for the efforts.
[Captivate Android Development] iXNyNe:
Beta 2 on apex 10 makes gps actually work. :)
[Captivate Android Development] Rrryan2:
Pinnacle problem - if you upgraded from Pinnacle 1.1x using the 1.2 no-wipe upgrade, the GPS issues that were in 1.1 are still present. Upgrade using the 1.2 full wipe and that issue goes away.
[Captivate Android Development] Peaster111:
Okay will do... Thanks
[Captivate Android Development] shadvich:
Good results on Pinnacle 1.2 with KF1. Getting a little better results than with h3llstorm's fix, I'd usually get 7/7 sat lock with 30m accuracy in 15 seconds cold, but now I get 8/8 with 10m accuracy. Good stuff, thanks. And this is coming from a captivate which had terrible gps on froyo except for JVO modem, and practically non-working gingerbread gps without any fixes.
[Captivate Android Development] poolemit:
would love to try this. is it possible to install on non-cwm, stock kh3? tried with the update via zip in recovery but it complained about invalid signature...
[Captivate Android Development] shadvich:
Why can't you just flash boog's kernel?
[Captivate Android Development] soblecram:
*#3214789650# for me...
[Captivate Android Development] xhozt:
Fails here
[Captivate Android Development] goodolsen:
Same for me.
[Captivate Android Development] nyydynasty:
+1

+10char
[Captivate Android Development] soblecram:
Does the *#3214789650* work for you? or does the # bring you location and security menu (means you need to enable GPS first before dialing code)
[Captivate Android Development] Rrryan2:
Whoops. Typo.

Edited op.
[Captivate Android Development] laihafloyd:
Try *#*#3214789650#*#*
[Captivate Android Development] iXNyNe:
This is what I've always used.
[Captivate Android Development] poolemit:
only this worked for me. however, now i'm getting a force close for angrygps.apk. does this work for stock, non-deodexed roms? perhaps i need a different angrygps.apk for the stock KH3.
[Captivate Android Development] AnarchoXen:
same here, other way doesn't work.
[Captivate Android Development] ThisWasATriumph:
So I'm guessing this doesn't work on CM7 because it hasn't so far for me.
[Captivate Android Development] Rrryan2:
*#*#3214789650#*#* was the only one that worked for me on stock KH3 deodexed AngryGPS.apk, but *#3214789650# seems to work again after flashing the updated JVS AngryGPS.apk.

If one doesn't work, try the other I guess.

The AngryGPS.apk included in the package is JVS, deodexed. You probably need the odexed version, which unfortunately I don't have handy.

Sorry, I hadn't anticipated anyone wanting to run it on an odexed ROM.

Have no idea. Wasn't designed or tested with CM7 in mind. CM7 uses a different GPS driver, so I'm guessing it won't.

Thanks for pointing it out though, I'll append it to OP.
[Captivate Android Development] 41LY45:
Just flashed it on mine running Pinnacle 1.3.

Locks in less that 20 secs. 9-10 birds.

Awesome work dude.
[Captivate Android Development] DKirk:
Check to make sure that the GPS is enabled. I had the same problem before realizing that the GPS was off. Once turning it one it still Fc'd but a reboot cured that.
[Captivate Android Development] adelecho:
hi, i want to try this. But if it does not work, how can I revert to Pinnacle 1.2 settings?
[Captivate Android Development] shadvich:
It's been working well for me on pinnacle 1.2, but I suppose you could see which files this fix replaces and pull them from the pinnacle 1.2 zip and copy over with root explorer
[Captivate Android Development] Rrryan2:
I've been testing on Pinnacle 1.2 as well and would like to encourage Pinnacle users to try it out, so here's a revert package just in case.
[Captivate Android Development] Fate-Silver:
Pinnacle have bad GPS?

I tried stock Pinnacle. My GPS is working great with it.

Lock damn fast without this trick. Like 10 seconds as I recall.

With this trick... LOL. I think it'll be solid rock and super fast.

I think it's depending on area and it's depending on your phone hardware sometime(lucky users might have better GPS hardware).
[Captivate Android Development] poolemit:
my problem was that i was running stock odexed KH3. since i want to keep it as close to stock as possible, i flashed this (http://xdaforums.com/showthread.php?t=1245698) and then installed the zip. works great.

thanks for making it!
[Captivate Android Development] Rrryan2:
Pinnacle GPS is fine. But there's always room for tweaking. :)

I'll consider adding an Odexed Version as an option after the Beta phase, and since I think I've even uncovered a couple minor bugs in AngryGPS, I might even just drop it altogether.
[Captivate Android Development] Rrryan2:
Whoops. Duplicate post.
[Captivate Android Development] iXNyNe:
is there even a suitable alternative to angrygps?

and im assuming at least one of the bugs you are talking about is that the secure server switched back to verisign with every reboot?
[Captivate Android Development] Rrryan2:
Not really. I guess if you really wanted you could manually edit settings.db using SQLite Editor or something, but it's kind of a pain in the neck and won't necessarily provide any advantage over using AngryGPS.

Yeah, the "stickiness" failure of the SSL server is the only real bug that I remember off the top of my head, and I'm still not sure what if any impact it actually has since AGPS data still downloads just fine.
[Captivate Android Development] tamanaco:
Just flashed this GPS tweak on my Captivate running Pinnacle 1.3. It "appears" to be working fine, but for some reason I can not get the SSL Type: Google Server to stick. It keeps reverting back to VerSign. Anyone else experiencing this?... Does this setting make a big difference?
[Captivate Android Development] iXNyNe:
Known bug, so far its not affecting performance to my knowledge.

P.s. literally one post above yours Ryan was talking about this issue. Please read before posting to eliminate cluttered posts.
[Captivate Android Development] Rrryan2:
Known issue, already documented at the Google Code page and even here in the thread. Seems to be an issue with the JVS version of AngryGPS.apk. Does not seem to impact performance

as best as I can tell. GPS still works fine, and since you can get an approximate lock in Google Maps even with GPS disabled it would seem that SUPL (wireless network based) is working fine too even in secure mode. This version is the first time I can recall seeing google server even presented as an option, which might have something to do with it.

As even "VerSign" is a typo (should be VeriSign") I'm guessing there's just an oversight or two by Samsung that will hopefully be corrected soon.

Once again, please report (and check) issues at the Google Code page. It does a much more efficient job of reporting and tracking issues then having to sort thru emails and forum threads if/when the thread starts getting long.
[Captivate Android Development] ryboto:
I just want to say, this is an awesome fix. I was using Pinnacle 1.3 with a modified gps.conf file, and I'd still lose the GPS lock, and it'd take forever to re-lock, or it simply wouldn't. Applied this tweak, and the GPS only lost it's lock twice, and both times it re-locked within 15 seconds. Thanks!
[Captivate Android Development] ScottyNuttz:
This appears to work well... it does not magically fix the hardware issue that afflict many Captivates, but it appears to lock quickly outdoors. I can't get a lock from my desk at work (on the top floor of an office building) but I never have before either.
[Captivate Android Development] Nick0703:
AngryGPS

Hey guys I can't open angrygps, when I type *#*#3214789650#*#*, I get a popup that says Service Mode has stop unexpectedly please try again??:confused:
[Captivate Android Development] Rrryan2:
The "fixes" that add bunches of stuff to gps.conf will not work on these devices. Most of the gps config is done in gps.xml instead, and gps.conf only seems to get looked at byt the Samsunf daemon for NTP configuration. In fact, you can delete everything but the NTP server settings from gps.conf and gps will still work fine. And if your system clock is already synced to UTC, you can even delete the NTP settings and GPS will still work fine.

You didn't say, but your sig implies you're running Firefly. As stated in the OP, this will not work with Froyo ROMs.

Try plumbBob 1 instead.
[Captivate Android Development] mastergrillo:
I tried. Beta1 & beta2 on apex 10 and did not have any luck but then I used the pinacle revert .zip and my gps lock way faster but haven't tried tracking yet will try on my eay home and update

Sent from my apex infused captivate
[Captivate Android Development] Rrryan2:
Well that's... weird.

Either Beta1 (I900 JVS 2.3.5 based) or Beta 2 (Nexus S 2.3.6 based) should probably better matches for Apex 10 (JVS). I can't think of any good reason why the Pinnacle revert file (Samsung AT&T KH3 Captivate 2.3.4 "leak" based) would produce better results on Apex *unless* there's something in them that's a better match for Captivate hardware. However, I would expect most of the relevant hardware control differences would actually be accomplished at the kernel level which Apex 10 wouldn't take advantage of so even that hypothesis doesn't seem to hold much water. What kernel are you running?

I'm going to treat this report as anecdotal for the time being but I'll keep it in mind. And there's even a little bit of precedent -- when I was doing the testing that led up to plumbBob1.0 I couldn't find gps binaries that worked reliably better on Captivate than the KB1 files. Even GPS binaries from later I9000 Froyo builds like JS8 couldn't seem to give consistently better results on Captivate under Froyo.

Hmm....
[Captivate Android Development] mastergrillo:
Well I just got home and the tracking was spot on, I'm using dc4 with kc1 modem but what I did was I tried just apex stock and it sucked then I.went to beta1 worked ok then I went to beta and it didn't work at then flashed the revert.zip and.it worked perfect going.to.leave as is. But I'm guessing every phone is different

sent from my apex infused captivate
[Captivate Android Development] ctrclckws:
Every Phone is Different, when it comes to Captivate and GPS.

Phone 1, 1007 Build, horrid, no matter what.

Phone 2, 1010 Build, Refurb, Very Good, no matter what.

Rcvd with Froyo Kb1

Changed to Cog 4.5.3

Changed to Cog 5v2

Currently Pinnacle 1.3

Phone 2 is about 95% as good as a dedicated GPS.
[Captivate Android Development] geokilla:
Hmm this is weird. I couldn't get a GPS signal today and I was out in the open. Prior to flashing, I had very good signal that would connect almost instantly.
[Captivate Android Development] Shoey Peachew:
I tried beta 2 with apex and I never got a lock and it could only see 2 sats.
[Captivate Android Development] ryboto:
Mine's a 1007, and with these tweaks it's working pretty great.
[Captivate Android Development] Frontier3:
I am using Apex 10, with a fresh install GPS did not work at all. I installed pb3 beta2 and it still does not work at all. Will try flashing the pinnacle revert and try it out

---------- Post added at 02:33 PM ---------- Previous post was at 02:17 PM ----------

Just flashed the pinnacle revert and immediately got 7/7 - 8/8 locks with 10m error
[Captivate Android Development] Nick0703:
Yeah, that's my old ROM!!! I'm running Gingerbread 2.3.3 OFFICIAL UPDATE from Rogers!
[Captivate Android Development] Frontier3:
OK, using a Captivate with Apex 10 and the pinnacle 1.2 modem appears to make the phone incredibly unstable. So while the GPS did work nothing else really did.

Reverting it back to whatever modem the pb3b2 file has appears to make it stable again... although i haven't done much playing around with this phone since i installed apex10 this morning

*EDIT* it appears the biggest instability issue was with with home program and apex10... so while the pinnacle modem is the only one that's worked so far my comments on stability can be taken with a grain of salt.
[Captivate Android Development] Madtowndave:
You're mixing an i897 modem with i9000 kernel...that's your problem; kernel and modern got to match
[Captivate Android Development] Rrryan2:
KI2 Update

So I spent some time tonight playing with GPS files from the new UCKI2 "leak" for Captivate. The GPS handling in KI2 has been reworked quite a bit. The /system/vendor/ directory where most of the gps files and configuration were before has been removed, with the GPS files relocated elsewhere. The configurations are now consolidated in a single gps_ExtLNA.xml, with no separate gps.xml for some indiscernible (especially since there's no OEM

Ext

ernal

L

ow

N

oise

A

ntenna available for these devices) reason. This does seem to be the trend with other Samsung Android devices like Nexus S etc. though.

After some tinkering and trial and error I managed to get the GPS files from KI2 running on Pinnacle 1.3 (KH3 based). Unfortunately though, in initial testing results are... mixed, maybe even a little disappointing. TTFF is almost comparable to what I've seen lately (10-12 sec static indoor), and DOP is still nice and low, but SNRs seem pretty poor and usually fewer visible birds are in use.

There is an updated version of AngryGPS, but the bug about the stickiness failure for SUPL server type settings persists. Still doesn't seem to make much of any difference though.

Since the changes under KI2 GPS are moderately substantial, this file is provided here as an experimental version only. You probably shouldn't flash this if you're not 100% sure you know what you're doing and have a reliable method of rollback/recovery. And again, you'll still need to modify SUPL settings as described in the OP if you haven't already.

Changelog:

- updated AngryGPS from KI2 (thanks to emunee for deodexing!)

- updated gps driver from KI2

- updated AT&T secure SUPL certificate from KI2

- reorganized gps file structure for compatibility with new daemon

md5: c6db8950fbc7fdfca48047b83dfbcce5

EDIT: Actually, this was sourced from KI2. Was getting late...
[Captivate Android Development] iXNyNe:
Astounding results here. 6 second ttff cold start after deleting gps data. Held lock perfectly, navigation test was disgustingly accurate.
[Captivate Android Development] Rrryan2:
That's... great, I guess. :confused:
[Captivate Android Development] iXNyNe:
Is there a specific statistic like signal strength of each sat or number of sats you'd like me to report? Or would you know how to read the angrygps output logs?
[Captivate Android Development] mrsubway:
Nice!
[Captivate Android Development] eliminat:
After a few days of testing, Beta 2 works well, but keeps hopping (I'm on the road, I'm a few feet off the road, I'm back on the road).

Beta 3 has been completely useless for me. It says it locks, but puts me a quarter of a mile away from where I really am.
[Captivate Android Development] jswclw:
It has gotten quiet around here! Just wanted to give some of my feedback after trying beta 2 and 3 on stock KJ3. I really would love to get my GPS working as well as it was working with the I9000 based ROMs I had been running. So far, no luck.

For me, beta 2 was a non started. Beta 3 works much better.

In short, I can get a reasonably accurate and quick lock while stationary. But on the move using Google Nav, no luck. It just loses the lock over and over. What I stumbles upon was that if I let it run, but lock the phone so the screen is off, it is flawless. Since it still talks to me when locked, it is very usable. All the instructions are right on time.

So this begs the question, why? Some things come to mind.

CPU is not scaling up enough to run both the display and location services

Power to GPS is reduced when screen on

Data required to update display is interferring with GPS

Display is generating interference

Any thoughts? I would be interested to know if others have the same improvement by turning off the screen.
[Captivate Android Development] Nuskul:
My GPS didn't work well with kj3 either, i flashed ki2 modem and it works much better. Not as good jv6 on i9000, but best captivate modem i found and battery is still exceptional.
[Captivate Android Development] jswclw:
Giving KI2 modem a try now. Had to switch from ms based to standalone. That said, it definitely looks better. I hope the improvement holds through on navigation too.
[Captivate Android Development] jswclw:
Update: Gave the KI2 modem a try for navigation. Still, while the screen is on, it cannot keep up. It keeps getting lost. If i turn the screen off, it works like a charm. I get all the voice prompts right on time.
[Captivate Android Development] Elad92:
Can't open the AngryGPS app, something is wrong there.

What's the file that I can edit instead? (not all the fields appear in gps.conf file)

Thanks!
[Captivate Android Development] goodolsen:
AngryGPS isn't an app you can open. Use the key sequence in the first post to get into it.

Sent from Mister Red
[Captivate Android Development] Rrryan2:
Update: I've decided to abandon this project for several reasons:

Limited feedback::leech ratio. After something like 1000 downloads there were only about a dozen feedback reports. Not easy trying to develop in a vacuum when working with something closed source.

As detailed previously in the thread, Samsung has been changing the way GPS is implemented in recent GB builds. Files are moved out of the /system/vendor/ folder for instance. This essentially would mean that multiple versions would be needed at least until official GB source drops, and I just don't have the patience for it.

I finally found the 100%, guaranteed utterly effective way to fix the GPS on the Captivate: replace it with SGS II. The SiRFstarIV gps chip in it actually works, and it works great. :)
[Captivate Android Development] DAGr8:
Lol

Thx for all your hardwork
[Captivate Android Development] F1reEng1neRed:
Lol, that's a sure fix. Thanks for your efforts.
[Captivate Android Development] amtrakcn:
beta2 actually worked fine with my JVR ROM, so far no issue to report.

Glad you found the ultimate solution, considering upgrage too.:p
[Captivate Android Development] Elad92:
I know I need to open it with the key sequence, but it didn't work out, so I went to the app folder in the system folder, try to launch from there, didn't work out.

Anyway, can someone help me to configure the fields from the AngryGps in other way? (Maybe a file I can edit)
[Captivate Android Development] 4-2ndtwin:
Did u turn on GPS then dial *#*#3214789650#*#* ?

Sent from i897uckj3
[Captivate Android Development] macropp:
It really helped my captivate a lot. I think it's kind of "virtual satelite" thing. Because I also get 255 coverage of one satelite that is always present if even 1 other satelite is in view. But what do I care it works! Thanks a lot!!!

EDIT: I forgot... I used BETA2 running I897UCKJ3 Android 2.3.5 Gingerbread, Boog's Kernel.