yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] sewe:
Are you serious,isn´t the other way around?

Anyway, I can´t change the jupiter.xml because I can only write "fals" and I can´t get write permission in root exlorer nor terminal, probably something I´m not doing right but what?
[Galaxy S I9000 General] sjdean:
Sorry, you are of course right. I read it as, how do I enable logging. My bad. :(

You do know for write access to this file, you need to "root" your phone?
[Galaxy S I9000 General] sjdean:
Aww sweet. Thank you. Im noting lack of smilie so you're not even being sarcastic? Irregardless of what I've said to you, I have not insulted you the way you've done to me.

Thanks

Simon
[Galaxy S I9000 General] sewe:
I have "root" my phone so that´s not the problem
[Galaxy S I9000 General] sjdean:
Why certainly. I can't remember if it was the Captivate or Vibrant, but I was comparing some of the screen shots from one of those in GPS Test showing locks onto Satellites <20 SnR.

That was a big clue right there that US phones were doing something different compared to UK phones.

Im not saying that the driver isn't interchangeable - as has been proven. But it wouldn't surprise me if there were two different sets of drivers - at least between the Galaxy S and the Vibrant/Captivate.

That's why I think there's such a big mixed bag of reports.
[Galaxy S I9000 General] appelflap:
(last one before I leave this crazy thread)

easiest way is to copy the jup. file to your computer, and edit it there and then copy it back.
[Galaxy S I9000 General] Bajo76:
Thats exactly my problem too. Mounted as read/write also doesnt work.
[Galaxy S I9000 General] sjdean:
And you've given permission to the root program through the Superuser program?

Hrm. OK.

Well I guess you then have two choices. Using "adb" from the android development kit and doing something like:

adb pull /system/etc/jupiter.xml jupiter.xml

edit the file, then move it back with:

adb push jupiter.xml /sdcard/jupiter.xml

log onto the device:

adb shell

at the prompt, type:

su

then

cd /system/etc

cat /sdcard/jupiter.xml > jupiter.xml

Now, if that fails to work, you could take one of the root update.zip packages, edit it, adding your new jupiter.xml into the path under system\etc then follow the guide here to download the testsign.jar package and resign the package.

http://www.robmcghee.com/android/creating-an-android-update-zip-package/
[Galaxy S I9000 General] Bajo76:
Ok, already tried this before. It does not work.
[Galaxy S I9000 General] sjdean:
Ok, if you can get me your jupiter.xml I'll try and create an update.zip for you both....
[Galaxy S I9000 General] sewe:
Already tried that and it complains over the discspace,I have 4mb left on /system but it should´t matter when I copy it over or?
[Galaxy S I9000 General] appelflap:
I did answer you that thread: I ran it on the full Captivate fw. But I also ran it on the JM fw with the drivers installed.

The last screenshots were from a test with the SonyEricsson XPeria 10. There I saw ehp and alm data, never saw it on the Galaxy. Not with the new and not with the old drivers.
[Galaxy S I9000 General] sjdean:
You cannot adb push directly to the system folder as far as Im aware.

You have to push to /sdcard then go into adb shell then:

$ su

# cd /system/etc

# cat /sdcard/jupiter.xml > jupiter.xml
[Galaxy S I9000 General] appelflap:
No, not that i'm aware of. You can also try to rename it and copy a fresh one to that dir.
[Galaxy S I9000 General] sewe:
"cannot create jupiter.xml: read only file system"
[Galaxy S I9000 General] sjdean:
Is that when you're trying to adb push to /sdcard or when you're trying to cat /sdcard/jupiter.xml ?

Let me just check as well, which firmware are you running?

Also, is it a Galaxy S?
[Galaxy S I9000 General] Case_:
Ah, didn't see your reply, then, sorry.

And thanks for clarification regarding the ephemeris and almanach data. No reason to waste my time on this, then.
[Galaxy S I9000 General] sewe:
When I´m trying cat /sdcard/jupiter.xml and I´m on JF3 and yes it´s a Galaxy S
[Galaxy S I9000 General] sewe:
So annoying, I can rename it and when I go back to system and back again to etc it has change the name by itself to jupiter.xml
[Galaxy S I9000 General] sjdean:
If you can get me your existing jupiter.xml, I can try and create you an update.zip file.
[Galaxy S I9000 General] sewe:
Here you go
[Galaxy S I9000 General] sjdean:
Quick question, have you already edited the jupiter.xml, just that it already says

cLogEnabled="false"
[Galaxy S I9000 General] sewe:
yes I have
[Galaxy S I9000 General] boomerbubba:
Mine is not a technical question but a business and legal question. Are the consumer-protection terms in European markets really this strong?

I am in the U.S., where the business model is different. Here, the distribution channel for such "phone" devices is dominated by the four major telecom carriers, who generally want to tie the purchase of a phone to a two-year contract for network service -- perhaps a $2K commitment. Here there are basically two tiers of consumer rights:

1) A very short "buyer's remorse" period -- typically 14 or 30 days -- during which the customer can return the purchase and roll back the service contract.

2) A one-year manufacturer's warranty, which provides not for refunds but replacement devices (often refurbished) in the case of defects in materials or workmanship.

These terms are much less protective than those that the comments above decribe in the I9000 users' environment. There is an assumption that everyone can just return their phones for a refund if the September update doesn't work. Is this really correct?

That is not the case in the States. Only the brief buyer's remorse period has any real protective strength. And it is that ticking clock -- while there is zero assurance from either Samsung or the carrier/vendors that the GPS problem will actually get fixed -- that causes great anxiety among Galaxy S customers here. Once that period has passed, the buyer is stuck, and has no real recourse except to ask Samsung for a replacement device on the theory that there is a provable defect in materials or workmanship. Obviously, if the root cause (hardware or software) is not corrected upstream, no such replacement makes the buyer whole. One lemon just gets replaced by another.

Further, the public statements by Samsung have been carefully worded to avoid any admission that there is any defect at all. (That's obviously one reason this is called "optimizing" GPS, not "fixing" a problem. There is no admission that anything is broken; Samsung has conceded only that the performance does not meet some users' expectations.) The manufacturer seems to be positioning itself to deny any liability because those annoying customers just have quality expectations that are too high! Similar memes are being floated in online venues by apologists for the vendors.

So on my side of the pond, I doubt that the Samsung warranty is worth a bucket of warm spit. I have never heard of anyone submitting a warranty claim to Samsung over the GPS issue yet, let alone having that claim honored.

If the situation is different in your markets, I envy you.
[Galaxy S I9000 General] Beowulf_pt:
Here in Portugal we get days at best in some stores.. others 15. I will return mine Monday after around 10 days with it but in many cases stores won't even accept returns unless it is considered a defect, in this case this would be hard to prove as it isn't a clear malfunction like a defective LCD or speaker. Plus many customers don't complain or say their GPS work very well (most can't even know how to test them properly).

I doubt many users here can afford to wait long before returning the units. Some will be stuck with their phones and lose money later by selling.

I don't trust Samsung to fix this anymore so I will not risk my 599€ in this case. It is a lot of money so I'll just get it back for now. If their get it working well in the future (doubt it) I'll just buy the SGS again cheaper. If not, well, I'll keep my Symbian Nokia E72 or perhaps try an HTC Desire.

I would not advise anyone now to trust the GPS issue will be fixed and lose their chance to return the SGS. Do it while you can.

If you can't anymore... well, there is nothing to do but wait and keep spending (wasting) time in foruns and debugging/testing tasks that should have been performed by Samsungs QA teams before release.
[Galaxy S I9000 General] larryccf:
Beowulf - did the external GPS antenna ever arrive? and if so, did you get a chance to try it??

curious what effect it had

tks in advance
[Galaxy S I9000 General] Beowulf_pt:
It has not arrived yet. Perhaps I'll have a chance to test it before I return the phone if it arrives Monday.

I have the impression I read some user (not sure if it was on XDA tho) comment that an external antenna did indeed improve SNRs as expected but that even with it the Galaxy S kept losing locks and sat-hopping a lot. It probably won't solve the problem.

I did some more GPS usage today, this time trying Copilot for a change and with a car dock having the phone very close to the "clear" area of the athermic windshield.

Results were the same as usual... it seemed to work fine sometimes (no doubt when copilot was snapping) but it often lost locks and snapped to the wrong roads and so on. Navigation remains a total mess. Even when it appears to be working ok it is just an illusion.. changing to MyTracks and GPSTest will reveal the chaos that is going on.

Had a friend laugh at it in the car. I really wanted to like this phone but have no patience to spend more time messing around with the GPS issues. Even the lag (which is quite annoying) I'd tolerate and would try to work around it even knowing it is not satisfactory out of the box.. at such price.

Yeah. I'd deal with the lag and the other details. But not with the GPS. It will feel good to return it. Only question now is if I'll bring a Desire on the same day... got more interested in Android and apps like Tasker.
[Galaxy S I9000 General] andrewluecke:
Not sure, but here in Australia, yes (but very few people are aware of it). In most markets:

You have your 14day period to return it and get money back if you are getting issues (generally referred to as a DOA). Then you also have manufacturers warranty. In our case this is 1 year.

BUT in many countries, there is also a 3rd type of warranty, which is an implied warranty. If you buy a Rolex watch for $2000, how long would you expect it to last even if it only has a 1year warranty? It would be fair to assume that the watch should last at LEAST 5 years at that price (after all, it cost a significant amount because of its "awesome workmanship". Despite now dropping in price, the SGS was certainly NOT a cheap phone, certainly not cheap enough to believe that there is a possibility that it will be faulty within the first year. There is probably a reasonable expectation that the phone should last at least 2 years. It is also certainly reasonable to believe that the GPS signal remains strong, and doesn't drift for miles when sitting down.

At the very least, the accuracy should remain somewhat correct when there are no misfunctioning satelites (and it doesn't), so we would probably be able to get a refund, especially as the phone ships with Layar, Google maps and are releasing accessories for "car mode" (which uses GPS). GPS isn't advertised as a "bonus feature", but rather as a core feature, and if they can't get it working, receiving our money back isn't unreasonable (because we wouldn't have to compromise with other popular phones). Keep in mind though, that there are no set guidelines to implied warranty laws, so some officials may judge it to 1.5years, whilst some 2years, or some 1..

That being said, since Samsung have committed to September as the timeframe for the GPS to be fixed, you'd be best off waiting until the official "fix" is released before trying to claim implied warranty. But if you are concerned that the software might not fix the problem, returning during the return period would be MUCH less effort!
[Galaxy S I9000 General] sanktnelson:
Not really, since it's different everywhere in Europe. In Germany you have a 14-day "buyer's remorse period" as you call it. You can return everything bought online within 14 days, no questions asked, no cost. Amazon even extends that to 30.

The merchant has to give you 2 years warranty, and if they are unable to resolve your warranty claim, they have to give you a refund. Usually this is considered the case after ~5 exchanges have not fixed the problem.

So returning stuff in the first 2 weeks is much simpler, which is why I did that.
[Galaxy S I9000 General] BronzedDroid:
The "buyer's remorse"-period is pretty much the same in Norway, but we have a five year warranty for electronic equipment stated in the law.
[Galaxy S I9000 General] milsjg:
Track with GPS-Fix from Captivate

Hi, some of you complains that they havent seen a good track, so here you have one. I drove from the airport earlier this morning and this is the track in My Track. If you not satisfied with this type of tracks you should buy a dedicated GPS with WAAS or EGNOS. I am using the GPS-FIX from captivate so clearly it is a good GPS and the fix is on the way.

The track: http://maps.google.com/maps/ms?ie=U...89699,20.29707&spn=0.004625,0.013797&t=h&z=16

By the way, I have had a fairly good GPS all the time. It has worked according to NORMAL specifications. Only a few times I have seen the famous jump error. I would suggest that the GPS error is connected to software and the specific chipset which I still believe is Broadcoms 20751 specification but maybe made by Samsung (GPS,Bluetooth and FM radio). The drivers could be the same as other chipsets but the processing is distributed.

It makes much more sense to the GPS enigma, because of the shared processing with the CPU. Android is trying to conserve battery and it seems very reasonable that the GPS will suffer if it shuts down key systems in sleep or prioritize "wrong" when overloaded. This is far more consistent with the errors I encountered (error when receiving phone calls, starting new programs etc) than any mystical hardware problems.

I think that this thread has started to be a bit of a complaining thread, where some "experts" seems to have all the answers even if they evidently doesn't know very much about tracking or GPS. Just making complains, discarding GPSs that works or just get emotional are not going to solve the problem that SGS have.
[Galaxy S I9000 General] sjdean:
I've seen good tracks too. I've seen average tracks. I've also seen really poor tracks. The GPS has a schizophrenic personality.

I think we'd be over the moon if we could produce the types of tracks you run...

How so? What reason have you for that assertion?

Sorry, you think Samsung make Broadcom chips? Additionally, it's not a 20751. Internal logging and even jupiter.xml shows it is a 4751.

What makes you so sure that it isn't hardware problem exacberated by heat or interference? What makes you so sure that for example, those with problems just have a bad batch of GPS chips or anything else?

Hrm. And you've just given your answer now. It's also inaccurate in that it is clearly not a 20751 chip. Pot meet kettle.

So what's the solution to my map (also with the Captivate fix)

http://maps.google.com/maps/ms?ie=U...59344,-1.813173&spn=0.006864,0.02238&t=h&z=16

(note this is much better than normal, but still off and appearing somewhat delayed in updates - the next track I did was even worse)

I've tried every fix out there and the Captivate one still doesn't cut the mustard for me at the moment as it only locks onto a very select few satellites - ie, they have to be overhead not on the perimeter - even if they're stronger.

I'm still waiting on Samsung to release the real fix in September..
[Galaxy S I9000 General] milsjg:
So why do I and many others get good tracks, if everything is wrong?
[Galaxy S I9000 General] boomerbubba:
Actually, it is not true that "Samsung have committed to September as the timeframe for the GPS to be fixed." Samsung has commited to no such thing. It has merely announced that it will "optimize" the GPS -- without conceding that anything is broken. Those weasel words were obviously chosen to avoid warranty liability.
[Galaxy S I9000 General] andrewluecke:
As far as I'm concerned, they are committing to a fix. As I mentioned, software companies generally call them patches, not bug-fixes, but it doesn't mean they don't fix bugs. Similarly, having dealt with many companies previously, it is rare for any companies to even provide set dates for fixing problems.

Furthermore, the GPS does work, but is flawed. I agree the wording is beaurocratic BS, but calling it optimisation isn't an impossible link. Most importantly, it's confirmation that if the GPS WILL get fixed by software, it will be next month.

By law in most countries, they don't need to officially call it a bug for us to be able to return the device for a refund if the fix is a lie. Don't read too much into it's wording. All that is important is that if it isn't fixed in September, it isn't a software fix and we are being deceived.
[Galaxy S I9000 General] Bajo76:
Here is the captivate gps fix where logging is disabled.
[Galaxy S I9000 General] wascaa:
I have now much better results using the official JM1 update from Kies with captivate fix applied.

I recorded a 45 minutes run this afternoon, and for the first time I got a usable track.

With previous versions the recorded tracks were terrible, most of the time Mytracks would just give up recording the track.

Here is a link to the recorded track (red is recorded, green is actual) :

http://maps.google.fr/maps/ms?ie=UT...60196,1.449659&spn=0.010511,0.018003&t=h&z=16

Most of the time the cross-track error is below 10m, exept when going through small woods, nothing abnormal here.

I have no idea if this is the best the SGS can achieve, but it is in anycase a huge improvement over the previous versions.
[Galaxy S I9000 General] PsiIion:
Based on my experience I don't think any of those would be true. I have tried it in my car and when walking around. I have tried it in different weather, and been driving and walking in dense forest where you hardly can see the sky. I have been driving on roads with 90 degree turns.

And luck would not be that much of a factor, because I used the GPS many hours in total and always have pretty decent tracks, while others almost never seem to get a decent track. And it's not only me, there are many with consistently really bad performance as well as many with consistently good performance as well, which seems to exclude luck as a factor.

Here are the latest tracks I recorded, all using JP3 without any fixes applied:

http://maps.google.com/maps/ms?hl=e...d=114564631644081718252.00048de1fcf19a2e09464

http://maps.google.com/maps/ms?hl=e...d=114564631644081718252.00048de2081fbf61ea632

http://maps.google.com/maps/ms?hl=e...d=114564631644081718252.00048de20fe1bf2f59306

I have now done the new captivate fix, but not had a chance to test it out properly. What I have noticed is that it's quite hard for me to test if it locks to satellites with a SNR < 20, because if I have enough satellites for a lock it's rare that they have a weak signal. I never seen anything like the screen Case_ showed, regardless of how many locks. If I'm outdoors most satellites will have an SNR around 40.

Considering the great variations in how well the GPS works for different users I would guess that not all phones are equally sensitive. Maybe that is normal, but it's also obvious that the software is not good at handling weak signals which means any issues with sensitivity becomes very severe. So for lucky users like me who got a phone who happens to be a bit better at receiving signals it will work fine, but for some users the combination of less sensitive hardware and the issues with the software means the GPS is almost useless.

I think if it was only software we would have found a common denominator by now.
[Galaxy S I9000 General] PsiIion:
I just went out and turned on the GPS and took a snap of GPS Test to demonstrate the typical reception I get:

For those of you with GPS problems, would you normally see the kind of signal strength Case_ had in the image he posted, or is the image above more typical?

I doubt the signal strength would be affected by the software, and if people do experience different sensitivity in their phones it seems to me like at least part of the problem is that the hardware on some phones is not optimal.
[Galaxy S I9000 General] foxbat121:
My signal strength varies from 20 to 40 typical. Sometimes in low teens. Sometimes in 40s.

As shown in your screen cap above, even though you have strong signal with 8 satellites locked, your accuracy is still 10 meters. That's the core of the problem with SGS-- lack of accuracy. You should get 2.5 meter accuracy or better with that kind of signal strength.
[Galaxy S I9000 General] sjdean:
I actually get great signal strength most of the time, but there's something that's affecting the reported location.

I think worryingly in the screen shot, the overhead shot bottom left of the screen, doesn't show where the satellites are. That's another curious one. I find my GPS won't come alive until its at least found where all the satellites are.

Again another difference.

Im not entirely sure accuracy is the biggest problem. The problem I think is it determining the location. It can still give an accurate location, but say that the reading is only accurate to within 100 metres.

I think even if we had 2.5m accuracy in the current system, the location reporting is way off.

I've seen mine report 5m, 10m accuracy, but show me walking effectively sideways down the road despite turning left, or 200m elsewhere. The location reporting is very odd.
[Galaxy S I9000 General] foxbat121:
I agree with you on that. The mediocre accuracy might just be the sympton of something bigger in Samsung's the faulty implementation of the GPS stack.

BTW, stationary accuracy on SGS is typically better than moving accuracy. That's why a lot ppl reported their GPS just fine because they just stand out side their house and get a quick lock and call it a day :) And I also suspect Samsung implemented two algorithms for caculating GPS position, one for driving and one for stationary or slow moving. I found a lot of the times, Google Nav can be pretty good traveling at a constant speed. But when I slow down to an intersection, the blue circle grows larger quickly, inidcating the accuracy getting worse. But that's not to say the highway accuracy is better. The GPS software smoothes it out using some predictions so that it don't have to work harder. That's also the reason why whenever you make a turn, the GPS can't follow you closely because the prediction algorithm predicts you should continue go straight :)
[Galaxy S I9000 General] larryccf:
tks

i'm starting to develop similiar feelings - questioning whether the screen and the phone's specs are worth the effort i've given studying this issue
[Galaxy S I9000 General] sjdean:
I have my car kit on order, as well as an mmcx gps aerial. I'll feed back with updates when I get that.

Cheers

Simon