Related
Googling and searching these forums doesn't bring up anything obvious. So does anyone know what chipset it uses? Looking at logged data it is operating at 1Hz.
It's built-in the Qualcomm Snapdragon chipset, see here
Thanks. I'm just trying to work out if it will do as good a job as my external bluetooth sirf III one I used for racetrack lap timing with my previous phone.
For normal navigation the inbuilt GPS gets fast lock and seems to work okay but the more accuracy the better for the track.
Guess I can just run it and compare times to the electronic timing (which take 1-2 hours to be printed out and released hence the need for an instant solution).
it's the best inbuilt gps ive used gets a lock in under 10 sec my xperia used to take 30s to 1 min.
michaeljf said:
Thanks. I'm just trying to work out if it will do as good a job as my external bluetooth sirf III one I used for racetrack lap timing with my previous phone.
For normal navigation the inbuilt GPS gets fast lock and seems to work okay but the more accuracy the better for the track.
Guess I can just run it and compare times to the electronic timing (which take 1-2 hours to be printed out and released hence the need for an instant solution).
Click to expand...
Click to collapse
The SiRF chip is better than the GpsOne on Qualcomm SOCs.
And to above post, this might be because AGPS is actually working on this phone rather than the antenna being better.
dont think i have agps enabled if im correct it uses data, when i start igo 8 no connection is made, im just using antena.
my device recives signals even if iam in home and recives at least 3 satellites
michaeljf said:
Thanks. I'm just trying to work out if it will do as good a job as my external bluetooth sirf III one I used for racetrack lap timing with my previous phone.
For normal navigation the inbuilt GPS gets fast lock and seems to work okay but the more accuracy the better for the track.
Guess I can just run it and compare times to the electronic timing (which take 1-2 hours to be printed out and released hence the need for an instant solution).
Click to expand...
Click to collapse
it will be down to how fast/often the app polls the gps surely?
I've been playing with it a fair bit (for the same purpose) and it certainly better than one or two stand alone gps
Getting satellites indoors or getting a fast satallite fix does NOT automatically indicate that the GPS chip is good.
Actually GPS on the HD2 is pretty poor compared to the SIRF III chip, or even compared to other HTC devices, I am talking about accuracy and stuff. This is a fact, so i don't want to hear any more about "how good it is because it gets a fast fix" or other crap
For more info:
GPS going crazy (proven with plot screenshots)
Weird GPS problem. Moving even while my car is motionless.
Recent ROM/Radio for the HD2 upgrades do seem to improve this bad GPS functionality though.
barty22 said:
Actually GPS on the HD2 is pretty poor compared to the SIRF III chip, or even compared to other HTC devices, I am talking about accuracy and stuff
Click to expand...
Click to collapse
Accurate, scientific data to prove that assumption, please?
kilrah said:
Accurate, scientific data to prove that assumption, please?
Click to expand...
Click to collapse
I understand your viewpoint, actually I had such information (plots of the HD2 and of other devices), but I really can't be bothered to make them again and spend all the effort on it... just believe me when i say it (or don't believe it, i'm just sharing what i know)... or have a read through the topics i linked to (should be enough proof in there)
Well if I have time I'll try both at the same time this weekend at the track (still have my old phone and external GPS).
With the high speeds involved and a racing line that varies no more than 1-2m it becomes pretty easy to tell if the GPS is out when plotted on a track overlay.
Plus values for lat/long g forces and speed are all extrapolated so if these are out it becomes pretty obvious.
Why has this been brushed over? Is GPS ironed out here? From what I can tell, Samsung has a horrible front end for their GPS with the Galaxy S line and a weak/insensitive GPS antenna to boot
I don't have a Galaxy S to compare, but on my Tab it seems to be working just fine. Better than on my G1 even. I just got six satellites and a very quick lock, and I'm currently indoors, just sitting next to the window(yes, writing this on the Tab).
Yep mine is just fine. I keep agps off in Google maps and its very accurate - more so than my moto milestone.
EDIT typos.
No GPS issue. This have been noted in preliminery reviews all over the web.
Size matters
Wonder if it has a different chip inside than the galaxy phones. If not then we can probably port the tab OS to the galaxy phones.
Rapax said:
I don't have a Galaxy S to compare, but on my Tab it seems to be working just fine. Better than on my G1 even. I just got six satellites and a very quick lock, and I'm currently indoors, just sitting next to the window(yes, writing this on the Tab).
Click to expand...
Click to collapse
Yes, the Tab does appear to have a good GPS function. I've got the Tab sitting next to my Galaxy S near the window at the moment. The Tab can see 7, with a lock on 6; the Galaxy S can also see 7 with a solid lock on 4.
Coincidentally, I did a 'wardrive' test on the tram ride to work this morning. The Tab was tucked comfortably into the inside pocket of my heavy winter coat, producing good results.
Mind you, I've also had pretty good results under identical conditions from my Galaxy S.
I don't quite understand the recent fuss that seems to have been made concerning the strengths and weaknesses of the Galaxy S; after all, it's simply a GPS-enabled consumer grade handset.
ftgg99 said:
Yep mine is just fine. I keep agps off in Google maps and its very accurate - more so than my moto milestone.
EDIT typos.
Click to expand...
Click to collapse
Hello...One question if I may:
Since Android (eclair and froyo) doesn't have proper or at least clear connectivity control, how do you make sure agps is off and why do you keep it off?
Just curious......
« »
betoNL said:
Hello...One question if I may:
Since Android (eclair and froyo) doesn't have proper or at least clear connectivity control, how do you make sure agps is off and why do you keep it off?
Just curious......
« »
Click to expand...
Click to collapse
By clicking on the big gps icon in the notification bar
Sent from my Galaxy Tab
Azhad said:
By clicking on the big gps icon in the notification bar
Sent from my Galaxy Tab
Click to expand...
Click to collapse
Please! Let him answer.... it's about A-gps (full assisted gps -SUPL) and nothing to do with the internal gps receiver.....
.
I'm pleasantly surprised by how good the internal dedicated GPS receiver is. I have an external bluetooth GPS unit (Sirf III) but I will probably not need it with the Galaxy Tab.
As for the A-GPS feature, it can easily be switched-off completely via the system settings panel.
daniel.weck said:
As for the A-GPS feature, it can easily be switched-off completely in the system settings panel.
Click to expand...
Click to collapse
Where exactly in settings?
Location and security ( wireless networks) ?
In the froyo I have (JPA firmware of the sgs) there isnt a clear a-gps settting/key to disable like in the Symbian Os for instance....
« »
Believe it says check here if you want to use wireless networks for location.
I was amazed at how fast mine got a lock in downtown Vancouver, my Galaxy S (and my Milestone and my Blackberry and my...) all too quite awhile to get a good fix when surrounded by office towers, the Tab is much faster.
konawayne said:
Believe it says check here if you want to use wireless networks for location.
Click to expand...
Click to collapse
That's not aGPS.
I'm happy to hear this anyway. The GPS on my current Vibrant is OK, the ones I had before we're pathetic though.
I have a Captivate and just picked up the Tab for Verizon. I have to say that the Captivate's GPS is fickle at best, but it is a completely opposite with the Tab. It locks on immediately when I am outside and at most 15 seconds indoors. I really hope it is a software problem, but I also wonder if they both have the same GPS antenna. It scares me that it might actually be the Captivate's hardware if they aren't the same.
I'm pretty sure the Captivate uses the metal back for it's GPS antenna. The Captivate's I tried at the AT&T store locked on pretty quickly, no test of tracking accuracy of course. I have my old Vibrant next to my New (but obviously previously owned) Vibrant and the GPS is obviously much better on this new one I have now.. SNR's are much higher, it's picking up more birds and when navigating my old one gets big circles around my location and often blips up on accuracy.
The CDMA/GSM-WCDMA versions have different GPS receivers. I know for a fact that the GSM-WCDMA Galaxy S and Galaxy Tab share GPS receiver chips so it should be the same for the CDMA versions.
heygrl said:
I know for a fact that the GSM-WCDMA Galaxy S and Galaxy Tab share GPS receiver chips so it should be the same for the CDMA versions.
Click to expand...
Click to collapse
Would share this fact with us? Wich gps chipsets those devices got? And where the info comes from?
Thanks
mr. haison said:
I have a Captivate and just picked up the Tab for Verizon. I have to say that the Captivate's GPS is fickle at best, but it is a completely opposite with the Tab. It locks on immediately when I am outside and at most 15 seconds indoors. I really hope it is a software problem, but I also wonder if they both have the same GPS antenna. It scares me that it might actually be the Captivate's hardware if they aren't the same.
Click to expand...
Click to collapse
If you are getting a lock indoors, it have nothing to do with antenna, etc. but with full a-gps (supl) wich I don't use.
Btw I use only onboard/offline gps navigation programs.
And I go online only via wifi...
« »
betoNL said:
Would share this fact with us? Wich gps chipsets those devices got? And where the info comes from?
Thanks
Click to expand...
Click to collapse
They both have the Broadcom BCM4751 GPS Receiver. All GSM-WCDMA Galaxy S variants have this receiver
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/2
Same for the Galaxy Tab.
heygrl said:
They both have the Broadcom BCM4751 GPS Receiver. All GSM-WCDMA Galaxy S variants have this receiver
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/2
Same for the Galaxy Tab.
Click to expand...
Click to collapse
Neat!! Thanks!
Based on my gps experience with the sgs international, I can say that eventhough the Broadcom chipset is not that dependable on full agps (supl)support, it's still much less capable than sirfstar chipsets....
« »
Edit 30 dec 2010:
see my last post in page 4
GPS suc*s when tested in high roads density urban areas
Hi,
I see many debate here about Galaxy S issues, mainly lag and GPS.
I was scared when got one, but finally, becoming a fan boy too:
In answer to this topic:
DSF said:
1) Test Google search (press and hold option button in home). Press a leter, for eg N. Now you have to wait seconds. Just web, apps are in searchable items. Without web suggestions
2) Swype
3) Manage apps
4) List processes
5) Apps shortcut
6) TouchWiz app drawer
7) Browser (still on JP6 ATM)
And so many issues.
Click to expand...
Click to collapse
So I tested in my SGS, recently bought (3 weeks):
GPS driving on road behaves like my Sirf III module (but under Navigon, google maps not tested)
Google search is fine (lag less than 1sec)
Swype: really smooth
Manage apps: small lag, max 1 sec or less
Apps shortcut: first time just 1-2 sec, than instant
App drawer is fine, lag is really minimal to abscent, far less than 1 sec when it is there
Browser: no issues
It came with JM7 bundled, never updated firmware as I don't see the need. Bought it in october, just after an out of stock long period
I'm really thinking there are some hardware issues solved recently. My SGS seems to behave like the one from "fanboy"
I'm not going to become a fanboy, just maybe helping with my case. If it is really hardware dependent issues, a mass RMA would help samsung to admit the problems (that they look like have solved in newer devices?). After all, Apple, with their small antenna bug was finally more fair than Samsung.
I really open this topic to give a positive feedback. I also wonder why I have a "perfect" SGS, while many have a bad one? If it is not hardware, what can it be?
Maybe people that get new units, bundled stock with a new firmware (mine was JM7), should give a feedback here.
If it is hardware, why not RMA and put pressure on Samsung
jonny_ftm said:
Hi,
I see many debate here about Galaxy S issues, mainly lag and GPS.
I was scared when got one, but finally, becoming a fan boy too:
In answer to this topic:
So I tested in my SGS, recently bought (3 weeks):
GPS driving on road behaves like my Sirf III module (but under Navigon, google maps not tested)
Google search is fine (lag less than 1sec)
Swype: really smooth
Manage apps: small lag, max 1 sec or less
Apps shortcut: first time just 1-2 sec, than instant
App drawer is fine, lag is really minimal to abscent, far less than 1 sec when it is there
Browser: no issues
It came with JM7 bundled, never updated firmware as I don't see the need. Bought it in october, just after an out of stock long period
I'm really thinking there are some hardware issues solved recently. My SGS seems to behave like the one from "fanboy"
I'm not going to become a fanboy, just maybe helping with my case. If it is really hardware dependent issues, a mass RMA would help samsung to admit the problems (that they look like have solved in newer devices?). After all, Apple, with their small antenna bug was finally more fair than Samsung.
I really open this topic to give a positive feedback. I also wonder why I have a "perfect" SGS, while many have a bad one? If it is not hardware, what can it be?
Maybe people that get new units, bundled stock with a new firmware (mine was JM7), should give a feedback here.
If it is hardware, why not RMA and put pressure on Samsung
Click to expand...
Click to collapse
Many people still have release-day SGS's and they work just as good as yours; some people have the problem and some just do not. Was there a hardware update? We don't know and if there was, why would Samsung not announce something and try to put themselves in a terrible position?
We just don't know. I have a release-day SGS myself and the only problem I've had was the button's delaying (which is quite annoying) and "the Black Screen of Death" a few times (which was fixed by not putting on a hard-case from Bell).
hol17 said:
Many people still have release-day SGS's and they work just as good as yours; some people have the problem and some just do not. Was there a hardware update? We don't know and if there was, why would Samsung not announce something and try to put themselves in a terrible position?
We just don't know. I have a release-day SGS myself and the only problem I've had was the button's delaying (which is quite annoying) and "the Black Screen of Death" a few times (which was fixed by not putting on a hard-case from Bell).
Click to expand...
Click to collapse
Hi. Just a couple of questions for you if you dont mind.
1.) When you say "Black Screen of Death, do you mean the weird Coma/Crash syndrome? Mine from Bell as well just started doing this about 60 days into owning it and it has happened a total of 3 times in the last 5 days or so.
2.) What do you mean it was SOLVED by not putting on a Hard Case from Bell? I have one from Bell (looks like leather on the back) and you now have me wondering. I have had the case almost since day one though and my phone just started the Coma/Crash as mentioned above about 60 days after owning it. Please advise...
3.) A bit off topic but I see you are rooted on JH2. Can you please tell me how you rooted the device? I have tried the update.zip files I have found before but none of them ever work for me. Do you need to be sim unlocked for the root to work? Please advise...
Thank You...
@yiannisthegreek
1.) When you say "Black Screen of Death, do you mean the weird Coma/Crash syndrome? Mine from Bell as well just started doing this about 60 days into owning it and it has happened a total of 3 times in the last 5 days or so.
Click to expand...
Click to collapse
Yes; try to wake the phone and I just can not, no matter what I do and thats when...
SEGWAY
2.) What do you mean it was SOLVED by not putting on a Hard Case from Bell? I have one from Bell (looks like leather on the back) and you now have me wondering. I have had the case almost since day one though and my phone just started the Coma/Crash as mentioned above about 60 days after owning it. Please advise...
Click to expand...
Click to collapse
I'll break it down for you; my problem with the BSOD started to happen after I attached my cases I bought from Bell (the semi-clear hard grey case and the fake crocodile skin case). The cases felt VERY snug to my phone, almost 'death-gripped' (which meant the cases were difficult to take off, almost 'ripping-the-backplate-off' difficult) and I could feel heat through the case. After taking them off, I have never had the BSOD since, although my phone feels a bit naked. I had also UNROOTED my phone but the BSOD happened a few days later (with the case on).
3.) A bit off topic but I see you are rooted on JH2. Can you please tell me how you rooted the device? I have tried the update.zip files I have found before but none of them ever work for me. Do you need to be sim unlocked for the root to work? Please advise...
Click to expand...
Click to collapse
This is the post where I got my update.zip:
Code:
http://forum.xda-developers.com/showpost.php?p=7536130&postcount=11
The steps were guide-lined here:
Originally Posted by AllGamer
Step 1. root your phone
Bell's I9000M is slightly different than the regular I9000
most of the root methods mentioned on other topics will not work.
Even the 3 button recovery mode has been disabled
After some experimentation this is the working method
download the update.zip from this topic (Thanks to jentech)
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=7536130&postcount=11
then you need to run adb devices to make sure your phone is listed
(ADB is part of Android SDK, download it from the source http://developer.android.com/sdk/index.html )
if you get something like
Code:
adb.exe devices
List of devices attached
900098c722a9 device
(if you run adb.exe devices and comes back with an empty list, then make sure you have set the phone into debugging mode Application > Settings > Development > USB Debugging)
then you are can execute
adb.exe reboot recovery
this will take you to the recovery screen
now if your device works with the Power + Volume Up + Home button, then you can skip that, however in my case the 3 button mode didn't work
select the update.zip with the volumen up down button, then hit home screen, it should say installing in yellow, then you are done, it reboots back to normal, and now you can install Busy Box
Click to expand...
Click to collapse
Hope that helps
I got mine also after the "outstock" period.
Got 2, first one had weird issue, rebooted for no reason and, in the end, USb would work and, everytime I pluged it in (PC or recharge) it would reboot in a loop :S
All of this in the first week
Got it exchange and since then, no reboot, no connection issue, no "lag" and GPS is more than decent (I use it to track jogging and it's right on the spot)
Manif. date of this one is 10.09.21 (specific date on the battery, on the device itself it's 10.09, no day)
I do wonder the same thing as you do, might be a good idea to note the manif. date and if user has issue or not...It might give help to some of us with unreliable SGS get it exchanged!
If the manufacturing date gives different hardware, I would definitely send it back again to get a latest one. My replacement didn't solve the GPS issue...will talk to orange uk again tomorrow...
I agree with thread creator. My SGS works fine right at the beginning (except the lag). I see a date on the battery which is 2010.08.03.
I also think it may be hardware-related issues.
Car navigation software such as Navigon accepts an enormous range of errors though. But the errors are exposed when using GPS for fitness purposes (because if the tracks swing wildly side to side then you do the 10km jog in 7km).
I think it might be hardware these days, but waiting for froyo official to see. After that I'll return my phone as many times as necessary
apart from the gps inaccuracy, there's nothing to complain about! the sgs is simply brilliant however, i'd be happy if they put in more ram on the device :|
the gps update frequency is bad, and sometimes is terribly inaccurate
Has anyone tested, one of these phones, with a bluetooth sirf 3 gps?
I would assume, to a certain extent, that it would help prove, if it is a hardware fault or not.
Are there other factors involved, however?
@jonny_ftm just try a Froyo build. I was pretty happy with Eclair in terms of performance (of course some issues where there too, but not that many).. but froyo has some nice additions (eg: input cursor, copy text from browser, flash support, etc) but it sucks in terms of performance. Even the latest builds (JPO, JPA) seems to suck as some realistic people report.
I have ~ 150 apps in app drawer
I will check the date of manufacture of my phone later and report back.
It could be a good idea to start with this to see if there's really a trend to better hardware with later manufacturing dates.
Sadely, it is not that simple. If in mobile phone industry it works just like in PC electronics, even manufacture date of phone won't help. I explain: intel chipsets on motherboards were often "buggy" in some extent on first production. Later, they enhance the product and produce new build versions of chipset correcting hardware issues. Now, it's upon to motherboard manufacture to use the last chipset build or not. Most time, motherboard manufacture will use old chipset stocks before moving to new one.
So, if we want to know this for sure, only SN and build dates on chipsets inside the phone will be the ultimate proof. Sadely, unlike in PC world, less people open their phones to check components unless they break the screen...
Anyhow, phone manufacturing date can help as early dates would have necessarly early components. Later built phones could or not have the last chipset though.
DSF said:
@jonny_ftm just try a Froyo build. I was pretty happy with Eclair in terms of performance (of course some issues where there too, but not that many).. but froyo has some nice additions (eg: input cursor, copy text from browser, flash support, etc) but it sucks in terms of performance. Even the latest builds (JPO, JPA) seems to suck as some realistic people report.
I have ~ 150 apps in app drawer
Click to expand...
Click to collapse
- I won't try Froyo. Until it is final, we can't say Samsung s**ks, it is just beta testing. My phone works great with original JM7 it came with, I don't need Beta Froyo features if they make the phone unusable. Now, I understand people that need these features getting frustrated. Hopefully, it is not my case, so can't help here
- I only have around 30 applications, I think I won't have more than 50-60 include stock apps. Even a PC with quadcore CPU, 16 Gigs of extreme fast RAM, RAID setup and tons of applications/processes installed will slow down. I don't expect a tiny smartphone to do a better job there. The only OS that was rock stable despite tons of applications is Palm OS, now dead :-(
Mine had 16 6 10 on the battery and I experience the gps issue.
Sent from my GT-I9000 using XDA App
Latest phone aren't struggling with lag out of the box anymore.
householddog said:
Has anyone tested, one of these phones, with a bluetooth sirf 3 gps?
I would assume, to a certain extent, that it would help prove, if it is a hardware fault or not.
Are there other factors involved, however?
Click to expand...
Click to collapse
I tried using my external holux bt gps (which really kicks ass)....but to my surprise i figured android doesn't support external bt gps devices natively! so, google maps or navigation does not bother picking up gps info from the external device. android still has no support....bottom line so we're pretty much stuck with what our sgs can do! sucks i know!
Actually, from what I was led to beleive from the test in the accesories, BT GPS seems to work with everything:
http://forum.xda-developers.com/showthread.php?t=818688&highlight=GPS
See post #10
nope....even in post#10 he mentions that "in theory"! it just wouldnt work and i did a serious amount of research only to realize android doesnt support external bt based gps devices. however, i havent tried in froyo....will do it tomorrow and post if i have any luck!
All working fine here - manufacturing date 25/08/2010
Very interesting, the date manufacture theory I stated seems not that wrong from the few feedback in this thread. If we have more feedback, it will become evident, for those doubting it, that Samsung is just making fun of his customers. They don't intend to admit any defect and won't recall phones unless forced by a massive customers action.
I'm happy I got mine only in October. When I receive my microSD card, I'll open it and add my contribution with manufacturing date for my working out of the box phone.
All this means it is very bad news for people with very laggy, battery consuming and bad GPS phones
dreamtheater39 said:
nope....even in post#10 he mentions that "in theory"! it just wouldnt work and i did a serious amount of research only to realize android doesnt support external bt based gps devices. however, i havent tried in froyo....will do it tomorrow and post if i have any luck!
Click to expand...
Click to collapse
Just install Bluetooth GPS Provider. It's simple.
Please let this thread be only for posting Mytracks results for the Galaxy S II and another phone so we can compare. The setup on each android phone must be the same.
The settings used for my tracks were use wireless networks OFF, use GPS satellites ON and use sensor aiding OFF.
The other phone I used was a samsung galaxy spica I5700. Both phones were on the dash board with a small 20cm gap between them.
http://maps.google.co.uk/maps/ms?hl...55.107542,-6.687498&spn=0.066185,0.10849&z=14
I must say I am disappointed by the Galaxy S II performance, it even went totally off the road at the start compared to the I5700.
I will be keeping a running total of the scores, so on this test the I5700 won, so its
1 Galaxy s II, 2 Other Phones.
I will be keeping the scores updated.
I'd post mine against the HTC magic and Orange San Fran but I can't load tracks from the S2 to google maps, it hangs on the authentication screen.
Frostfree said:
I'd post mine against the HTC magic and Orange San Fran but I can't load tracks from the S2 to google maps, it hangs on the authentication screen.
Click to expand...
Click to collapse
You have to export them as as either KML, or KMZ files. Then you must upload them manually to google maps on your computer.
I only have an SGSI to test against, so obviously the SGSII is going to be better than that. I have many KML tracks for the SGSII, they all look fine to me - more info at http://blog.clove.co.uk
NZtechfreak said:
I only have an SGSI to test against, so obviously the SGSII is going to be better than that. I have many KML tracks for the SGSII, they all look fine to me - more info at http://blog.clove.co.uk
Click to expand...
Click to collapse
Did you do an walking tracks? If not, would that be feasible?
I walk 3 mi per day and often log tracks. My SGS is very inconsistent, some days off by as much as 1 mi. Interested in how the S2 performs on slow tracking. Thanks.
See if this helps you.
http://forum.xda-developers.com/showthread.php?t=1083773
Posted it already in one of the threads, but here goes...
Well, here is a comparison of my morning route to work today, my Galaxy S and Galaxy S 2 were registering route details at the same time, using my tracks.
- Galaxy S: http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=211531279532048944891.0004a3227ff46bf619c86&z=12
- Galaxy S 2: http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=211531279532048944891.0004a32301b1a7f63a9cd&z=12
I tested two tracks last week well pleased near enough bang on target all the way . Seen a few posted elsewhere that where also good .
But as My Tracks are not uploading its difficult at present .
jje
Ok so here is my comparison between HTC Desire and Galaxy S2
Sorry I use different software but you can still track this pretty well.
Please pay attention that I did walk different road in the beginning. So you should pay attention to the final part of my walk, because that shows some difference.
HTC Desire:
http://runkeeper.com/user/AndyE82/activity/31501743
Samsung Galaxy S 2. I didn't walk in the driveway..
http://runkeeper.com/user/AndyE82/activity/35947145
So yes, it doesn't work well. It does get the lock extremely quickly. I think even quicker than Desire. But the accuracy is not good.
Ok guys juding from the maps so far, im scoring the Galaxy S II 1, Other phones 2.
I couldnt see yours CandyAndy, but ill take your word for it that the Desire is more accurate.
JJEgan said:
I tested two tracks last week well pleased near enough bang on target all the way . Seen a few posted elsewhere that where also good .
But as My Tracks are not uploading its difficult at present .
jje
Click to expand...
Click to collapse
What I did was export the tracks as KML files and upload to dropbox public folder, then copy the URL and paste it into Google Maps search and hit enter. It'll show the track in Google Maps.
NZtechfreak said:
What I did was export the tracks as KML files and upload to dropbox public folder, then copy the URL and paste it into Google Maps search and hit enter. It'll show the track in Google Maps.
Click to expand...
Click to collapse
I know did that tested them and deleted them .
Forgot to switch My Tracks on today so missed 2 x 50 mile trips .
But i know it works anyway even if some do not .
jje
Dannyboyni said:
Please let this thread be only for posting Mytracks results for the Galaxy S II and another phone so we can compare. The setup on each android phone must be the same.
The settings used for my tracks were use wireless networks OFF, use GPS satellites ON and use sensor aiding OFF.
The other phone I used was a samsung galaxy spica I5700. Both phones were on the dash board with a small 20cm gap between them.
http://maps.google.co.uk/maps/ms?hl...55.107542,-6.687498&spn=0.066185,0.10849&z=14
I must say I am disappointed by the Galaxy S II performance, it even went totally off the road at the start compared to the I5700.
I will be keeping a running total of the scores, so on this test the I5700 won, so its
1 Galaxy s II, 2 Other Phones.
I will be keeping the scores updated.
Click to expand...
Click to collapse
disappointed?
As i sees it.
The "good" lock on sgs2 came some seconds later.
Possible reasons. You start the sgs2 later? Or did the spica got better cached info? Or maybe sgs2 are some second slower then spica to get a good lock?
After both have a good lock it was close between them but if i should choose a winner i should say sgs2.
hermaniii said:
disappointed?
As i sees it.
The "good" lock on sgs2 came some seconds later.
Possible reasons. You start the sgs2 later? Or did the spica got better cached info? Or maybe sgs2 are some second slower then spica to get a good lock?
After both have a good lock it was close between them but if i should choose a winner i should say sgs2.
Click to expand...
Click to collapse
I am going to run the test again for the sgs2. I will leave the phone to get good lock for 3 minutes in the car then I will set off on the same route the problem happened.
If that doesnt improve things what else do you suggest I do?
Video demo of the GPS, couple of picture-in-picture screencasts to show GPSinfo and the Navigation screen on the same route too (different trips, immediately following each other):
Detailed blog post to accompany all this @ AndroidNZ.net including lots of raw MyTracks KML files for people to pore over should they feel the need - up now.
Thanks.
Great technical information.
It backs up my feeling from using the note for GPS.
Xaddict said:
Thanks.
Great technical information.
It backs up my feeling from using the note for GPS.
Click to expand...
Click to collapse
Thanks man, I'm just putting the finishing touches on the blog piece that goes with this now for anyone who feels like reading more about it (unadulterated MyTracks tracks available there too).
Thanks for the video. How long does it take to get a lock from a cold start?
Sent from my Nexus S using xda premium
My first ever lock with each of the Note's I had (A-GPS enabled) was like 6-8 seconds or something, I was beyond surprised. Virtually all locks since then 2-4s range.
gps on note is amazing
right on target. 16 feet accurracy. didn't lose track even going to the worse curse ever. i am so happy the gps works good on this phone. My captivate worked only on certain mod with several tweeks. The note works out of the box with very good lock and accuracy.
The accompanying review part is up now.