yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Case_:
I'm almost certain the problem is in software. I was testing the GPS today with MyTracks and comparing it with another quite accurate GPS as well. While MyTracks was reporting my current position at least 20 meters off, when I switched into the internal GPS diagnostic application, it was reporting lock to 7 satelittes out of 11 available and accuracy 5 meters without a single hitch. Obviously there must be something wrong "in between".

Edit: Sorry, I wasn't paying attention and obviously skipped some of the posts when replying. Still, some of the info is valid, I think.
[Galaxy S I9000 Android Development] chluk2425:
those found out the lock is meters off try GPS Informaion, it's in the Market.... I got the exact location when testing it yesterday, can even tell you are on the left or right lane when driving....
[Galaxy S I9000 Android Development] milsjg:
I have to agree it is down to meter accuracy with the GPS information but you have to understand Lat and Long and how to recalculate it. I think that the problem is due to software, how different programs handle the information. Maps seems to do there own calculation and smoothing witch tends to get the path going smooth but may have an error of 20 meters and above when turning. It also lose all information if the screen goes dark. My tracks seems also to have some strange calculations although much better however if the signal is lost it tend to start all over again without taken the previous location into consideration. Mycardio seems to get it more or less right and the tracks will be correct all the time.

People has complained about the time to lock. Normally it is a fairly long time before an accurate fix for all GPS. They all implement different techniques to shorten the time, but I really do not think that you can get a position from coldstart in less than 5-10 sec with a fix within 100 feet. I have seen some movies here showing instant fix within 10 feet for a HTC brand. That is not possible, may be with the military signal, but definitely not with our GPS. What you see is just some nice programming and guesswork.

So to conclude I think the GPS issue is a software problem and that different software handles it different. Thats why Samsung have to take their time to fix it.

By the way the chip I am told is bcm4751, I do not think so. I belive it is BCM20751 as I wrote a few weeks ago. This chip is a combo with GPS + Bluetooth 3.0 and FM radio. The GPS is sharing it's calculations with the phone processor and that may explain the strange behaviour and problems to get it working flawless for Samsung programmers.
[Galaxy S I9000 Android Development] pepitodequetequejas:
sjdean two questions .

have you ever seen more than 8 fix in NMEA sentences (in GPS debug mode )?.

(and more difficult) is debug mode NMEA output written directly for the driver?.
[Galaxy S I9000 Android Development] sjdean:
I'll be honest, both of those questions kind of go over my head. Im not sure what exactly produces the debug logs. It's something definitely activated within jupiter.xml - question is, what that is passed to is another question.

One may however suspect the Broadcom GLL interface.

I have seen a 9 satellite fixes a few times:

$928439I <SKFNAV> m_stSKF.rt [52.427664, -1.856145, 156],[0.0m/s, 0deg] dts:8ms 8.487334
%928441E GL_NMEA[$GPGGA,101512.00,5225.660399,N,00151.368988,W,1,09,1.0,97.7,M,49.1,M,,*47
%928457I GL_NMEA[$PGLOR,STA,101512.00,0.008,0.000,419,1,10,0,PWR,D*0D
%928458I GL_NMEA[$PGLOR,SAT,15,030,1F,27,022,1F,09,020,15,26,034,1F,18,023,11,28,025,1F,17,028,1F,22,019,11,12,017,11*4D
%928464I GL_NMEA[$PGLOR,SIO,TxERR,0,RxERR,0,TxCNT,308,RxCNT,1920,DTMS,992,DTIN,1,DTOUT,278*77
%928465E GL_NMEA[$GPGSV,3,1,12,15,73,167,31,27,70,276,23,09,53,268,20,26,47,133,34*7A
%928469E GL_NMEA[$GPGSV,3,2,12,18,37,283,23,28,30,050,27,17,24,096,29,22,19,317,19*76
%928473E GL_NMEA[$GPGSV,3,3,12,12,10,207,17,39,25,147,16,33,28,197,,24,05,323,*77
%928477E GL_NMEA[$GPGSA,A,3,09,12,15,17,18,22,26,27,28,,,,2.1,1.6,1.4*39
%928481E GL_NMEA[$PGLOR,FIX,1.0*3E
%928484E GL_NMEA[$GPRMC,101512.00,A,5225.660399,N,00151.368988,W,000.0,,310710,,,A*62
LBS_I: API: gllbs_gps_notify_position(52.427673, -1.856150)
LBS_I: CB: RIL request 3

This is interesting.

15 SnR 31	18 SnR 23	12 SnR 17

27 SnR 23	28 SnR 27	39 SnR 16

09 SnR 20	17 SnR 29	33 SnR ??

26 SnR 34	22 SnR 19	24 SnR ??

Automatic, 3D fix, using 09, 12, 15, 17, 18, 22, 26, 27, 28

GPS Test won't show us satellites < 20 SnR, but here, the GGA line show 09 satellites being tracked, and GSA shows 9 satellite fixes, including 22 with an SnR of 19 and 12 with an SnR of 17. And look at the Horizontal dilution of Precision - 1.0!

Oooh.
[Galaxy S I9000 Android Development] pepitodequetequejas:
Thanks sjdean

:D , good news (i suppose).

GPS seems work well.

GPS test (android apps , kernel) dont use NMEA , android uses an interface

implemented by the driver.

http://pdk.android.com/online-pdk/guide/gps.html

may be part of this implementation is wrong.
[Galaxy S I9000 Android Development] sjdean:
Tell me more about GPS in Debug - ie, what it is, where it is, how you activate it etc.

Thanks

Simon
[Galaxy S I9000 Android Development] pepitodequetequejas:
Sorry, sjdean.

i wanted to say that "GPS seems works well" ,i said debug mode because i am developer and

when i saw low level logs (NMEA sentences) i think is "debug mode" (in this case i think

debug mode only enables driver writes all or low level logs (but really dont know how works) )

Excuse my English
[Galaxy S I9000 Android Development] boomerbubba:
I just discovered a relatively new Market app called GPS NMEA Monitor, which is supposed to capture and display NMEA data in real time without rooting the phone. It is from Chartcross Ltd., the folks who produce GPS Test, and has only had a few downloads as of today.

It would seem to be useful to see the NMEA data at the same time that the driver-derived data is displayed in GPS Test or GPS Status.

I just installed GPS NMEA Monitor on my Samsung Vibrant, but was unable to get the utility to display any data. Has anyone else tried this app?
[Galaxy S I9000 Android Development] sjdean:
Im a developer too, not in Android or anything, so some of the phrases go over my head. Im very user orientated myself.

But I understand what you mean, thanks, and don't apologise for your English.

Some interesting lines in the GPS initialisation:

$180442D GlEngineImplStd::Finished loading components
#180442D ->GlPePwrStateMgr::SteadyNormalMode(PE2PE_LP_ENABLE_LOW_PWR,0)
#180442D ->GlPePwrStateMgr::NormalMode(PE2PE_LP_ENABLE_LOW_PWR,0)
$180442I StartRequest GL_REQ_PERIODIC(0016BC1C) cb=(SNRCTP ydlT) acc=50 per=1 timeout=-1
$180442I
$180452I GlReqSm: add pend req GL_REQ_PERIODIC ok
#180452D ->smRqRtr::idle(US2PE_START_REQUEST,234)

Most interested in the lines that reports "LP_ENABLE_LOW_PWR".

I can confirm that the Broadcom GLL Driver has a different date and version to the XXJF3. So something is happening, but it's not there yet IMHO.

Cya

Simon
[Galaxy S I9000 Android Development] chluk2425:
I have seen lots of threads saying it's due to software problem, I've no comment on it since i know nth about it :p

what I did is try to get a program that will give you (whatever it's doing calculation or guessing or what) a constant accurate lock, so far, using GPS Information as a starter works for me (in Hong Kong). it might not work when i get back to UK, but for now, that's the temporary solution, isn't it? :)

I can't try using cold start since i can't get access to the GPS setting using the secret code (possibly due to i haven't rooted it yet), so i can't tell whether you will get a spot on if you use cold start, but i can imagine how long will it take to lock if it has to find the satellites from stretch every time it starts.
[Galaxy S I9000 Android Development] hmose:
I'm interested in GPS NMEA Monitor as well. Hope someone has installed it and gotten it running on Captivate (which I am holding off purchasing 'cause of GPS problem). I can watch NMEA sentences on my Tilt thanks to Fugawi software and it is a great tool especially to troubleshoot the chip vs firmware question.
[Galaxy S I9000 Android Development] sjdean:
On the inspiration of elsewhere, I've taken the NMEA logs and converted them to a Google Maps file and compared to a MyTracks map.

Not good.

Looks like the NMEA information is wrong too:

http://maps.google.com/maps/ms?ie=U...77579,-1.794891&spn=0.005594,0.01929&t=h&z=16

(Blue Squares indicate NMEA positioning, Blue Track is MyTrack)
[Galaxy S I9000 Android Development] milsjg:
Well, this is an enigma. I just drove from my home to the basketball hall using My tracks as the logger.

This is the results:

http://maps.google.se/maps/ms?hl=sv...3.790978,20.470276&spn=0.206214,0.558929&z=10

As you can see it is almost perfect I got a phone call during the drive and picked it up to my ear (illegally?) the result was a break in the track. It also tracked som new round abouts that has been built this year and are not on the map. The maximum error anywhere seems to be maximum 5-10 meters.

So why do some of you have this spurious errors and bad tracking? The phone is same I suppose (I9000) and the software is more or less the same so what is happening? The operator (Orange, Telia, Verizon etc), how many programs you try to run simultaneous with the GPS or maybe some faulty phones in a batch going to some people? One should know that even if 100 persons has complained the phone has sold in millions.

I hope Samsung with the effort of people in this forum can come to some solution so that everybody gets a great phone.

Firmware JM2 with Samset 1.7
[Galaxy S I9000 Android Development] Case_:
Well, I wouldn't call this "almost perfect", it's quite off in lots of places. Not after the GPS precision I was used to with my Magic and that can be achieved on even the cheapest of the cheap Android phone, Vodafone 845...it's actually really sad putting the Galaxy S and VF845 side by side and watch the 100€ phone get pinpoint precission tracking while 500€ Galaxy insists on my position being 5-10 meters off most of the time (and quite often A LOT more) and drifting drunkenly all over the place with no relation to my actual movement...:(
[Galaxy S I9000 Android Development] sjdean:
In case I failed to mention it previously, one thing I noted was that the accuracy seems to be determined based on signal strength of the satellites, not on how many satellites you see where only 4 should be required for a precision fix IIUC.

Additionally, Im noticing people running various speed fixes. I note that there is a path called /data/gps with stores I think the almanac and ephemeris data, not to mention the control pipe etc:

acNmeaOutName="/data/gpspipe"

gpioNStdbyPath="/sys/class/sec/gps/GPS_PWR_EN/value"

gpioNResetPath="/sys/class/sec/gps/GPS_nRST/value"

ctrlPipe="/data/gps/glgpsctrl"

lcsApiSockName="/data/gps/lcs.socket"

acNvStoDir="/data/gps/"
[Galaxy S I9000 Android Development] hmose:
I emailed Chartcross and asked them about NMEA Monitor on the Galaxy but no word back yet. Meanwhile found app called ASPARA which supposed to put out nmea sentences but have not been able to try it yet either.
[Galaxy S I9000 Android Development] milsjg:
Well as I stated the GPS is more accurate than Google maps. It has been several new roads since the Google updated their maps. In Sdjean's case with errors that jump back and forth is of course not acceptable but to have tracks with less than a few meters errors is not possible due to certain restrictions in the system, clock precision, space weather, correction etc. You can of course use EGNOS or WAAS and compensate and get it down to under 2 meters but with a raw handheld GPS the normal accuracy is between 5 to 15 meters (15 -45 feet). If you want precision you should invest in a DGPS witch take you down even further. However the point is that the forum is giving people the wrong idea what GPS precision can be. The maps that shows the jumping fixes is not not acceptable but if you have a track and the error is 5 - 10 meters in a fairly straight line you have a normal handheld GPS (if you dont have some error correction).

Read for example http://www.gpsaccuracy.com/handheld-gps-devices-how-accurate-are-they.
[Galaxy S I9000 Android Development] milsjg:
I tried to explain that the road on the satellite map where it deviates from the GPS positons is rebuilt so actually my GPS is better than the map. I had the GPS on a shelf on the console in the car with no direct view of the sky above (but to the side through the side windows). The jump you see after the break one third on the track is caused by me answering the phone and putting it to my ear which is 20 cm from the roof blocking the GPS signal effectively. The start of the track after the call has a small deviation due to it trying to find the satellites after the break (5 sec or so).

The normal fix for a handheld is 5 to 15 meters if you not use error corrections (DGPS WAAS ERGNOS etc) so do not sell your Vodafone.
[Galaxy S I9000 Android Development] Tinyboss:
I tried the suggestion from sjdean in #33 of this thread, and I can (cautiously) say that it seems to have made a positive difference. Here are my observations:

Before, my GPS would often fail to get a lock, even with 6 or more satellites in view for several minutes (as reported by GPS Status).

Rebooting would always fix it, but in a day or less it would revert.

After sjdean's fix, it works significantly better than it used to, even immediately after a reboot.

In particular, before the change and with a freshly rebooted (and btw rooted) Captivate, GPS Status could not see any satellites from my recliner inside my home, and could see 6 or 7 in my backyard, locking up to 4. After the change, it sees 9 in my backyard, locks up to 7, and can even lock 3/7 or so from my recliner inside, which was never possible before.

I will keep an eye on it to see if it degrades from here.
[Galaxy S I9000 Android Development] boomerbubba:
FWIW, another I9000 user reported in a different thread that GPS NMEA Monitor works for him. So you might just try the app.

(My own phone, a carrier-specific variant here in the U.S., is a Samsung Vibrant. No doubt the Chartcross developer in the U.K. lacks such a platform to test with.)
[Galaxy S I9000 Android Development] sjdean:
Ooh, I made a fix.

I hope it works. I sincerely hope it does. Unfortunately mine comes and goes as it wants to. I really haven't a clue what's going on. Maybe mine has just given up the ghost.

Keep us informed though.

Cheers

Simon
[Galaxy S I9000 Android Development] Tyxerakias:
Just saw this post. Do you think it would make any difference if you added the enable_low_power to all the jobs and not just the normal?
[Galaxy S I9000 Android Development] sjdean:
If we can figure out what job its running, then maybe. It appears to maybe being a periodic job, but after adding that job in, it still didn't have an effect.
[Galaxy S I9000 Android Development] Tinyboss:
I'm sad to report that although the suggested change did seem to produce an improvement significantly better than I've seen from just rebooting, performance still seems to degrade in less than a day. Maybe if I have the patience to leave it alone for another day or so, then I'll see it come back to decent performance? We'll see...
[Galaxy S I9000 Android Development] miker71:
No. (JP3)

See http://www.everytrail.com/view_trip.php?trip_id=740519

Also I noticed at the end of the trip that Everytrail had been backgrounded (not by me) and the GPS icon from the status bar was not there (seems to me maybe there was a FC - so maybe it's just a bug and nothing to do with the GPS - but thought I would share the result)

The Froyo builds are buggy, reserve final judgement for the final golden release ...
[Galaxy S I9000 Android Development] sjdean:
Not for me either. XWJM5 though looks the best yet. Still errors, but it's not as crazy and is much more reliable for much longer.

How much of that is purely because I probably have a good view of satellites at the moment directly over head. I seem to get better results then.
[HD2 Android Q&A, Help & Troubleshooting and Genera] ebeltran1234:
ok. I've spent over 5 hours now looking over all the tuts and faqs and everything i can find, but i havent found an answer...

I'm trying to get android running on my hd2, but cant get rid of the robot voice. i was going to update my rom, but in the rom updating tut it said i needed to instal hard spl, but in the hard spl install tut it said "*You can only select between SPL2.08.0000 or 2.08.HSPL. This is to avoid people with 1024LEO's installing an incompatable version and bricking their device*" at which point i got really confused.

ive got android with htc sense running, i just cant get rid of the robot voice. the first time i tried, when i ran clrad it did something, the voice worked for one call, then turned into the robot voice. now when i run it, it doesnt do anything, like literally nothing at all. it gets highlighted, but thats it. then i ren haret, android boots, and robot voice ensues.

any help at all would be GREATLY appreciated, links, directions, anything at all.

my specs:

htc hd2 tmobile usa

1024 mb flash

radio 2.10.50.26

spl 2.10.0000

os version 5.2.21892

manilla version 2.5.20121412.2
[HD2 Android Q&A, Help & Troubleshooting and Genera] alex1261:
Install 2.08.hspl and install chuckyrom or another custom rom and redo android and the robot voice should be gone
[HD2 Android Q&A, Help & Troubleshooting and Genera] tuppaacc:
haha funny I was thinking the exact same thing.

First make sure you get HSPL3, then get chucky's rom here: http://www.xdaforums.com/showthread.php?t=734238 AND MAKE SURE TO GET THE T-MOBILE VERSION, then run android, if you still have the robot voice try to find a good combination between you're rom and the radio you are going to be using
[HD2 Windows Mobile 6.5 ROM Development] Stephen:
Hi,

Can somebody provide a mirror link, or an UK Serial number for a UK HD2 TMobile. I have tried using the US version for my ROM so I can enable the 576mb of ram but I then have problems with different dialing rules.

Looking for standard latest stock rom so I can build my own kitchen.
[HD2 Windows Mobile 6.5 ROM Development] samsamuel:
leo official ROMs thread, first post first link.

as dialing rules its because the tmous rom only has the connection setup for tmous settings. find the regular "connectionsetup.cab" and sorted.
[HD2 Windows Mobile 6.5 ROM Development] Stephen:
Cheers Man I will try that now.
[HD2 Windows Mobile 6.5 ROM Development] Stephen:
Man thank you very much for you help. I now have a 576mb rom that I can work with and easily splice sense 2016.
[HD2 Windows Mobile 6.5 ROM Development] samsamuel:
no worries. welcome.
[HD2 Windows Mobile 6.5 ROM Development] FrpStar:
SAMSUNG A022F FLASH FILE

Hey bro I kindly ask to be informed with a veried link to download A022F firmware that I can use to flash kg/mdm file without complications....kindly assist Big Bro🙏🙏🙏
[G1 General] pablo34:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
[G1 General] ilostchild:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
[G1 General] r3s-rt:
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.

Either way, nicely written guide. Someone will probably find this useful.
[G1 General] mblaster:
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...

* note: I don't have a desire (yet) so this is speculation *

Best is probably something similar to this http://xdaforums.com/showthread.php?t=750852

I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.

After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.

As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.

Enough OT... @ANtiHazarD: Very useful overview. Thanks.
[G1 General] lbcoder:
WAY WAY WAY more complicated than it should be...

It is a simple matter of:

fastboot flash recovery recovery.img

Done.
[G1 General] ezterry:
Its not quite that simple,

1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)

2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is
[G1 General] ANtiHazarD:
:) maybe so

but i want to post here ALL known methods :-) thats why so much text is here

why? coz it was a trouble and the method with

fastboot flash recovery recovery.img

not working! thats why - all ways is here.

(all pre-info into 1st post in the top)
[G1 General] ANtiHazarD:
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.

so... thats why only - sorry :(

maybe there is some guide in the same way in desire section?

p.s. and thanks one more time to ezterry for old support :-)
[G1 General] betizad:
Can you please help me,

I have stuck here with the G1 phone,

it starts up and stucks on the G! logo.

I can get into fastboot bet have the same problem :

writing 'recovery'... INFOsignature checking...

FAILED <remote: signature verigy fail>

I get into fastboot with thre android logos on skates,

even tried to restore nandroid using fastboot but I get the same error? could you help me out?

I have HTC DREAM with 1.33.0013d and radio 2.22.27.08

I am really frustrated,

I tried all you gave up here but none worked for me.
[G1 General] betizad:
Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.
[G1 General] AndDiSa:
Did you read everything before you flashed the 1.33.0013d SPL?

If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...

Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App
[G1 General] ANtiHazarD:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh

after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope :-)

ezterry can give for your advanced advice, may be
[G1 General] ezterry:
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.

If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here

basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post

You can do this without a goldcard because I bypass various checks in 1.33.0013d

(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)
[G1 General] ANtiHazarD:
try to 'fastboot wipe system -w'

after

wipe all (data/cache, cache, dalvik, ext, stats)

and move log to sd
[G1 General] breezy169:
ive never really done fastboot tho . is there any other way ?
[G1 General] AndDiSa:
It's worth learning to use it ... ;)

Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.