tr_s

Absolutely. Quite a few Android logging apps, GPSLogger is one of them, have exactly this setting: wait until accuracy <x before logging. It works just fine even if the logging interval is set so large that the GPS module turns off between log points.

I'd guess it uses magnetic bearings; new iPhones have a magnetic compass. Almost none of the smartphone compasses actually need active calibration these days. They are passively calibrated without you noticing as soon as you use the navigation system in the machine. On older smartphones one would often get the order to move the device in an "8" to calibrate it. Magnetic compass simply refers to that the Earth's magnetic field is used to get a bearing. I.e. same signal source as for traditional compasses. But in contrast to a traditional compass, there is of course no little needle inside a smartphone or GPS which moves. A chip is used to sense the magnetic field instead (which is why it's refered to as digital/electronic compass by some). This is essentially the techology used in electronic devices, but now far shrunk of course: http://en.wikipedia.org/wiki/Fluxgate_compass

Just adding in that the eTrex 30 shows the same track connection bug. I say bug because that's what it is. It's not necessarily a bug to connect track segments between power cycles. However, recording 2000 km/h speed for the straight lines is. The average speed should be recorded correctly as defined by the time and distance delta between power cycles.

Granted the antennas and receivers in phones are generally worse than dedicated GPS machines, but not so much it should really matter for general navigational use especially with newer phones. Most of the oddities you read about cell phone receivers is due to dumb software implementation (such as, the onboard GPS receiver never locked onto satellites at all but just some crude cell phone triangulation was used, a "snap on road" feature was used in the software etc..) Neither of Xperia X10, Samsung G Pocket, and an older Nokia has for me shown more than moderate deviation from an eTrex H when tracking with appropriate software. I have read especially intense vitriol against the receiver in older iPhones (200m+ off?) but have been unable to confirm this, when borrowing one 3GS for a while it seemed accurate.

You can if you want to - read the one and two starers on Amazon. Much what you'll read there however isn't valid anymore as the unit software has been quite a lot improved since.

Decreasing pressure of more than a couple mb/hour while you stay at the same altitude is indicative of worsening weather (clouds are being sucked toward you). Increasing pressure means the inverse, you are likely seeing better weather soon. That's basically it. But pressure alone is a pretty poor forecaster of weather, and what it means on a specific point on earth is variable. A local meteorologist or weather forecaster should know more.

I totally agree. Unfortunately I think the problem isn't isolated to Garmin - the market is shrinking so small for outdoor GPS that it won't see increasing budgets for development any time soon. The functionality is becoming generic and available in so many other devices (inexpensive smartphones).

With the current official software I would probably not have much to put against the 20 other than a little on the slow end for the startup. Don't put the extra money for the 30 unless you really want a barometer; as the compass is still quite wonky. //Etrex 30 owner

GPSLogger for Android can auto-send log files by email. You can also set it to log only every 30 minutes or so, which means it won't suck obtrusive amounts of battery power. (The GPS module in the phone completely turns off between log instants if you set the interval high enough).

Apparently it seems possible to make a self calibrating solution. My androidphone compass will giving the right directions again within a few minutes of walking even if a weak permagnet is suddenly taped to the case. (Note, my finding, I don't recommend you try this, have no idea about how the magnetometer is designed and if it can possibly be damaged by a strong B-field)

true...but I wouldn't get a low-sensitivity receiver these days, a distorted location is generally better than no location, moderate foliage could make the old etrex useless...

Try this one maybe? http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41

I'd say also, bring at least two devices if you think you will have trouble finding your way without them. Few consumer GPS's made in the last years, if any, is what I'd really call "reliable". Moreover even a reliable unit can be smashed into pieces or lost. One GPS with maps, and one basic GPS which is set such that the displayed coordinates conform to the paper map you are strongly recommended to bring, might be a good combo.

1. It's just a lame analogy made by programmers. "Free as in beer" means the software isn't charged for but the source code is closed, when it comes to GNU/open source the source code is available for anyone to edit. Mapsource is the former of them. 2. What I call "legacy devices" would essentially be the pre 2007 stuff or so, which generally have a serial port instead of USB. 3. Unfortunately not all USB->Serial cables work well with newer operating systems. What version of windows are you running? In any case you probably need to load drivers for the cable for it to work. With the cable connected, are you seeing any "unknown devices" in the Windows device manager? If not... under the "Ports (COM&LPT)" section, can you see an "USB Serial Port (Com ...)"? I have an FTDI cable myself and never had problems using it with garmin devices. Nevertheless drivers need to be loaded, no version of windows seems to have them integrated. Tobias

If you with "free software" mean "free as in beer" and not GNU/open source, simply use Garmin's Mapsource ? It works with all the legacy devices...

I wouldn't worry about the batteries. In case the compass works better with good batteries - which I doubt, then that's a misdesign. I was never a fan of electronic compasses, but the compass on my $100 smartphone still works much better than the one in the eTrex 30, and this without any need for active compass calibration. Now, the former in contrast to the latter does not see battery replacements, so perhaps the comparison is unfair, but anyway... Both are however "thrown off" much easier than a real magnetic compass with inertia, at the end of the day a silva works much better.

I unfortunately believe this has been a problem right from the time the device was released. Never used that data so I haven't noticed it myself. Some reviews on Amazon from way back in 2011 already then note this fault.

There is a share of "tough" smartphones with fair reputation for toughness and water resistance. Xperia active is one of them.

That would be the map set's fault rather than the eTrex 20, that it guides you through an army base. I reckon routing it with a Nuvi would give the same results.

Oh yes. You've just discovered one of the reasons for why geocaching can be considered a sport, and why "hints" exist! Of course it helps if both the hider and finder have had good GPS devices though.

Ten yards off is normal in a GPS context. If that's all position difference you saw, you have a good functioning GPS receiver. The GPS will only take you to the general location. Don't expect meter precision. I have the Galaxy pocket 5300. It's slightly worse than the Garmin eTrex 30 especially if the view of the sky is obscured, but not very much so. Have used both to record tracks in paralell, what is very notable on the smartphone is worse elevation precision. XY position trails follow each other by mere meters.

Just a warning. I read here or another GPS forum that if you put international characters in the startup message, like å,ä,ñ, etc, the unit will deadbrick and require service by garmin (joystick up to force USB mass storage and edit back the message won't work). This was a few months ago and the bug might have been fixed, but you might want to avoid taking the risk.

Below 50 feet off = perfectly normal for any consumer grade GPS machine

I'd say the answer to that one is "When it reads significantly different than a known good reference". Never saw an option to calibrate mine though.

The compass has been practically unusable before 2.87 - now it's quite flawless. Actually sticking coordinates/distance I haven't seen at 2.73 and onwards, but I guess mileage can vary depending on different variations and configurations of the devices... (some claim to never have had a Sticky problem, even at the very first firmware revisions)