zzavadil

Yes, I looks like this beta version is the big improvement regarding sticky issue! I was able "to stick" at most 5 meters in the woods today and I was trying really hard. Many thanks to ones that participated in these "sticky" threads and big thanks to Garmin for listening! I hope that other models will get this improvement too and sticky problem will be forgotten soon...

Thanks. Lucky you. I think no, but this is exactly the procedure for demonstrating the sticky problem in any conditions. Otherwise I've observed the problem in almost normal walking speeds, but only once or twice. I guess it might depend on other factors like satellite constellation, surrounding terrain, handling of the GPSr (especially orientation of the antenna) etc.

Rich, I guess exactly like this. I applied almost the same procedure like described above (except for setting waypoint) when making this video. Zdenek

Perfect instructions, I bet applying these steps will expose the stickiness in its ugliness to anyone. ;-) I've met some sceptics on a local GC forum who are strictly dismissing sticky issue as nonsense, telling me they have never met something like this etc. I'll translate this for them. Thanks, Zdenek

Yep, definitely do it, thanks!

Thanks.

Exactly. I like the unit, but this issue and some other minor quirks are really annoying... What e-mail address did you send your report to? Because I used Oregon.Beta@garmin.com about one year ago (I had Oregon 450 - same sticky problem) and now the local Garmin support, but absolutely no response... Thanks, Zdenek

Hi, in order to support this "fight" with Garmin over the sticky problem, I've made a demonstation video with "sticky" eTrex 30 and "non-sticky" GPSmap 60CSx, side by side in the woods: I've also send another (in fact my third) report to Garmin - they should admit the existence of the problem and offer the solid solution. In my opinion this lousy behaviour is unacceptable for hiking or geocaching GPS device. Zdenek

Changes made from version 2.40 to 2.50: Fixed issue where project waypoint feature would only work once per power cycle. No mention of any other issues, so why expect any other problems to have been resolved? I have one year experience with the Oregon 450, in numerous firmware versions they were constantly tweaking many issues, but almost nothing was mentioned in those changelogs, only minor things. They simply don't want to admit that their firmwares are overflown with bugs, sometimes even fixed and later recurring again. I really don't believe that after more than a month they fixed ONE bug. For example I've tested GLONASS today and it seems that now it's not drifting anymore. I would say that now the GLONASS in eTrexes is finally usable, because before 2.50 it wasn't. And no mention in changelog, guess why...

Dilettantes... BTW, when sticking it helps (besides restart) to switch from GPS to GPS+GLONASS and vice versa.

Installed and tested, but I don't see any improvement regarding sticky issue, slow map redrawing, compass quirkiness etc. Well, maybe next time... :/

Well, I won't use the precise quotation. Is this formulation ok?

Great, thanks for the very insightful information! Is he from ST? What should Garmin do is to make the option accessible in settings and let people to set it appropriately for every profile. That would make both groups satisfied. May I use this info on another forums?

My hypothesis regarding the type of batteries is very probably wrong... Today I've done a test which completely eliminated the effect of batteries - I removed them from GPSr and used an USB cable connected to my notebook. Later in the field I was witness of one very evident sticky issue...

Not yet, but I am planning some bigger testing session. Thanks for the methodology, I will inspire with it - several identical devices side by side with different batteries etc. I'm gonna send a notice to a local GC forum, I hope that someone will join me.

Thanks, could you please guess how often you encounter the issue and approx. howmany meters?

Well, it's just a hypothesis, nothing more. To prove it false or true, more tests needs to be done. I can post some images of tracks from last testing. I'm not a microwave expert but if you see inner construction of NiMH AAs and compare them to e.g. alkalines, you will see the substantial difference. If it can somehow interfere with high frequency part of GPSr is the question for some experts... Remember that these new GPS chips are super-sensitive and any little detail can affect them. I'm just trying to find out the sticky problem because it annoys me for more than a year and Garmin didn't reply on any of my reports.

No, it's not the reboot. It's the observation that with one type of batteries (white Eneloops) during the whole trip I didn't notice any sticky issue, while another day with another set of black Eneloops XX, the problem was more than evident.

Hi, after some tests I've found out that this sticky problem seems to be dependent on type of batteries used in GPSr, see the discussion here: http://garmingpsmap.wikispaces.com/message/view/home/43408702 Did anybody noticed something similar or could someone who is annoyed with this sticky issue on his/her GPSr try to test it with different sets of batteries? Thanks, Zdenek

It's unfortunately nothing new - it's the so called "sticky issue" or "sticky position" well known among the Oregon or 62s users. It is discussed on many forums, e.g. garminoregon.wikispaces.com, geoclub.de etc. Last week I got rid of my one year old Oregon 450 because of this really annoying problem, hoping that the new eTrex will be better. Yes, it's better in many ways (definitely more accurate), but the sticky issue is still there... Using the older models like Legend HCX or 60CSX I had never experienced such an odd behavior. Please report this issue to Garmin, the more people will report the more probably they will finally do something about it.