Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Posts posted by binzi

  1. I think it's even worse. It's not just a problem with live maps but also with PQs downloaded to my Garmin device.


    I solved a fair deal of mysteries around my home coordinates and used the corrected coordinates feature on gc.com. What happens is that when putting a PQ on my Garmin device there is simply no way for me to determine which mysteries I've solved and which I haven't yet solved. That is, I simply don't know which mysteries are still on fake coordinates and which point to GZ.


    The only solution I found is to exclude mysteries from all my PQs and manually create a gpx-waypoint for each mystery I solve. This really sucks big time but unfortunately is the only solution I found so far...

  2. I know it has already been said a couple of times but I think it doesn't hurt to repeat it once more: Please bring back the found caches count on the friends list.


    Removing this was obviously a very bad idea. Instead of being able to view the number of all found caches by all my friends at one glance I now do have to do a couple of clicks for each and every friend. So I lose time while you lose resources. Kind of a lose-lose-situation here...

  3. The problem happened to me today using an Oregon 300 with firmware 3.2:


    - connected the Oregon to the PC

    - deleted 4 gpx files each containing 500 caches (internal memory)

    - copied a new gpx file containing 500 caches to the Oregons internal memory

    - disconnected the Oregon from the PC

    - booted the Oregon and it would not finish its booting process

    - only thing that helped was to pull the batteries

    - booted the Oregon again without any problems, however, no caches were displayed

    - connected the Oregon to the PC, opened the gpx file using a text editor, inserted and deleted a space, saved the gpx file

    - disconnected the Oregon from the PC

    - booted the Oregon

    - finally all caches were displayed again


    Is there any way to make the caches reappear in such a situation without having to connect the Oregon to a PC? Otherwise it would really suck if this happens somewhere outdoors where there is no PC available...


    P.S.: In my opinion this again shows how inefficient the way the Oregon handles caches and waypoints is. Why can't it just always display all caches and waypoints that are stored in gpx files on the Oregon. If one deletes a cache/waypoint on the Oregon it is also deleted from the gpx file. Simple as that....

  4. I'm also very satisfied with this release. Accuracy is great and the compass updates way more frequently than before.


    Only issue I noticed so far is that when changing profiles sometimes some of the settings are not changed correctly. This is especially true for the Lock on road yes/no setting, which often stays on "no" when changing to a profile where it was supposed to be on "yes"

  5. While playing around and trying to recreate your problem I noticed something interesting today:


    - I had a couple of custom maps on my Oregon such that it would not allow me to search for countries but only for states and provinces.

    - I then renamed all foobar.img files (including the basemap) to foobar.old and restarted the device

    - for each map I would then reconnect the Oregon to the PC rename one single map file back to .img, unplug and restart the Oregon to see which map did cause the problem


    Surprisingly I was able to rename all maps to .img without causing the state/province problem. So now I do have all my maps on the unit and I am able to search for countries etc...


    Seems like it might also depend on the order in which you install your maps.

  6. As stated above, this might be caused by one of the maps installed on your device. In my case it was a self-compiled OpenStreetMap.


    Disabling the maps using the menu of the Oregon does not fix this problem. You actually do have to temporarily remove the map that is causing this from the Oregon. It should be enough to rename it from say test.img to test.tmp.


    I would recommend to re-install/re-copy/re-name the maps one by one to figure out which one is causing this problem.


    This should help you to go back from "Type State/Province" to asking for the country again.

  7. Thx g-o-cashers! My gmaptz.img was actually missing...


    Probably my fault since after the crash caused by adding new maps I deleted all maps on the Oregon and added them one-by-one to see which one caused the crash. Luckily I had an initial backup and was now able to restore the original gmaptz.img. Phew.


    At least I do now know what gmaptz.img is good for (tz = time zone :D ).


    I'm still a bit curious why the time was running two hours late instead of just one hour (which would be my difference to GMT+0


    Thx again. One issue down. At least two to go :P

  8. The time issue started to appear today. Yesterday everything was still fine. Today it just won't go back to the right time...


    Update: Just met a friend who also owns an Oregon running on 3.10. We were standing right next to each other receiving the exact same satellites. Both Oregons were set to time zone automatic. His does show the correct time. Mine however does still run 2 hours late.... Restarting the unit or changing the time zone to some value and then back to automatic does not solve this issue...

  9. Running firmware 3.10 I do experience the following problems:


    - the "time of day" field runs two hours late. It e.g. shows 6:30 p.m. when it actually is 8:30 p.m. This didn't happen with any previous release


    - after installing a new additional map on the SD card the Oregon will sometimes start to crash during bootup. If so, the problem remains until I connect the Oregon to the PC, boot it up, and rename or delete the map file


    - once all of a sudden it would stop showing the caches of one of my gpx files which was on the SD card for like two days and working fine. Problem was resolved by opening the gpx file, adding and deleting a space and then saving the file


    - I too do experience the problem where the compass will jump all over the place


    Unfortunately 3.12 seems to have some major bugs and some other problems that already had been solved in previous releases.


    Bottom line: Since I really do enjoy some new features of 3.10 and at least for me this version suffices for geocaching, I'll probably stick to it for now...

  10. Seems like 2.99 is the first beta that I won't put on my Oregon. From what you guys are writing one must get the impression that it has a lot more bugs than it actually gets rid of. In addition those bugs do sound really serious to me.


    To those of you who "bricked" their Unit using Firmware 2.99 beta: Did you get your unit working again and if so how? If not, did you send it to Garmin and how did they respond?

  11. Personally I thought that 2.97b gave me the best accuracy. However, this version does have a bug where it might not be able to get a signal at all even though there might be plenty of satellites available.


    2.98b fixes that bug, however there are some discussions about its accuracy. It seems like Garmin changed the EPE algorithm. That is, Garmin uses another algorithm to calculate the accuracy displayed by the unit. In how far they also did change the way the actual position is calculated is less clear though. My experience is that 2.98b shows a much worse accuracy than 2.97b while the actual accuracy is not that much worse. Yet sometimes it feels like 2.97b did not just display a better accuracy but actually was more accurate.


    Bottom line: In terms of accuracy I would prefer 2.97b. However, since it has a bug that might render your GPSr useless in the field, I would not recommend it for a longer trip.


    What do others think?

  12. Went out doing some caching with 2.98b under heavy tree cover today. I too can confirm that the algorithm to estimate the accuracy seems to have been changed. While the displayed accuracy was somewhere between 4 and 22 meters the Oregon would actually end up pretty close to ground zero.


    Personally I only care about how accurate my Oregon actually is and not that much about how it calculates its accuracy estimate. However, I think it would help a great deal to know how the accuracy is estimated as this would give me a much better idea about how to interpret that accuracy.


    One more thing I noticed with 2.98b today. While walking towards a cache the compass as well as that blue arrow on the map page would sometimes point into a totally different direction even so the map page tracked my movements just fine. If I was e.g. walking north the map would actually show me walking north on the map, while the pointer was pointing west. Just as if I was walking sideways (which I was not).

  13. As g-o-casher already mentioned I tried to write a Wherigo-Cartridge that uses os.rename(oldFileName, newFileName) to rename files like .gpx files on the Oregon. When played in the Wherigo-Emulator on a PC it is actually possibly to rename files. However, if played on the Oregon calling the os.rename function will make the unit crash. I was playing around again with this lately but still didn't get it to work.


    As to the 2000 geocaches limit I totally agree: It feels kind of strange to me to carry a unit with more than 4GB storage, yet I'm not able to use more than 2000 geocaches or more than some hundred waypoints. Basically you should be able to have unlimited geocaches, waypoints, tracks and so on. I just don't get why Garmin differs between information stored on the internal "harddrives" and information stored on the internal memory.


    In addition to this limit this also causes another problem which I mentioned in several other posts: You always have to manage two geocache databases as well as two waypoint databases. That is if, e.g., I delete some waypoints on my unit, they will still remain in the file on the SD card but will be ignored on the until I change the corresponding gpx file. If I then add a new waypoint to the gpx file all deleted waypoints are also back again on the unit. In my opinion, this really unecessarily complicates waypoint management.


    Why can't the waypoints on the SD card just be the same as those displayed by the unit. If I delete/create/change a waypoint either using the unit or directly in the gpx file the changes should affect both the gpx file and the waypoint displayed by the unit....

  14. Now here is another odd thing. I didn't have the time to downgrade and upgrade but still wanted to go out caching today. So I ended up using the unit without changing anything from yesterdays configuration and guess what: It was more or less back to normal! It took some time till it had a good lock but then it kept that lock and had an accuracy of 2 to 6 meters...


    Maybe waiting for the satellites to change their state or constellation is just as good as down- and upgrading :unsure:

  15. So today it happened to me...


    I'm on 2.97 since the day it was released and didn't have any problems so far. In fact my unit was very reliable and spot on all the time.


    Today all of a sudden my unit would lose all satellites and never really recovered from it. Now, it only looks on to 1 to 4 satellites even though it shows way more grayed out satellites on the satellite page. If I get lucky enough to get a fix it comes with an accuracy of about 30 meters!


    What is the best practice to get the satellite reception back to normal? What helped all you guys who had the same problem? Any other idea than down- and upgrading again?


    Any reply appreciated.

  16. I went out for a run yesterday going at a speed of around 8 to 9 km/h. I put the track record to one second. Here's a look at what I got:




    The upper line was recorded on a bicycle track that pretty much has an open view to the sky. The Oregon showed an accuracy of 5 meters most of the time.


    The lower line was recored on a regular street having some houses on one side and some trees on the other side. The Oregon showed an accuracy of 2 meters most of the time.

  17. Thanks for your hint. As far as I understand your solution basically is the same as mine.


    - You first have to copy current.gpx to your PC in order to save those waypoints that you created on your unit.

    - Then you may delete all waypoints on your unit by using the unit's software.

    - Then you have to edit and rename all gpx files whose waypoints should reappear on the unit

    - To keep some of the waypoints created on the unit you have to copy them from the former current.gpx file to one of your gpx files


    I usually do have something like 10 gpx files on my unit... If I just want to delete some of the waypoints of one of the gpx files as well as some of the waypoints created on the unit I have to do what I described in my last post which I think is more or less what you would also be doing.

  18. Hi I'm having the exact same annoying problem with waypoint handling. It does get even worse once you start creating waypoints on the unit. Then everything does get mixed up and really complicated.


    Does anyone have a best practice solution for the following problem:

    - I uploaded a gpx file containing 100 waypoints to the unit

    - out in the field I created another 50 waypoints on the unit

    - back home I want to delete 40 waypoints from the unit, 20 of which are in the original gpx file and the other 20 are among those created on the unit

    - on top of that I also want to transfer 20 new waypoints created on my PC to the unit


    Here's what I usually do (and I do think it is unnecessarily complicated):

    - create a new gpx file on my computer containing the 20 new waypoints

    - download my "old" gpx file from the unit and copy those waypoints I want to keep to the new gpx file

    - download garmins gpx file from the unit and copy those waypoints I want to keep from that file to the new gpx file

    - delete my "old" gpx file on the unit

    - disconnect and start the unit to delete all waypoints using the units own software

    - reconnect the unit to the PC and copy the new gpx file to it


    Maybe there is a better way to do this?

    In addition it does even get more complicated if you also have other gpx files on the unit. Here's why: As soon as I delete all waypoints using the unit's software it won't recognize/read all those waypoints from the other gpx files as it somehow remembers that I deleted them. So when I do the above I additionally have to rename/resave (=change timestamp) all other gpx files as well...


    Personally I think it would be much better if the Oregon wouldn't make any difference between gpx files and "internal memory". Wouldn't it be better if it just read and deleted waypoints from gpx files. So if you delete a waypoint it also deletes it from the gpx file and if you delete the waypoint from the gpx file it wouldn't read it anymore... Waypoints created on the unit could be stored in a seperate gpx file maybe called oregonwpts.gpx or whatever.

  • Create New...