Jump to content

andregixxer

Members
  • Posts

    41
  • Joined

  • Last visited

Posts posted by andregixxer

  1. All Garmin updates with decimals are Beta's and agree with you, there should be no new bugs in new software, BUT they include new options, making the gps even more complete.

    But still, I'm happy with the beta's. :rolleyes:

     

    sure ? i've an Oregon 400T with 4.20 FW version, Edge 800 with 2.20 FW version

     

    for oregon 400T there was a Beta page with "beta software".. then the official page with the final release ( every 5-6 beta releases ) ..

     

    beta page : https://buy.garmin.com/shop/store/downloadsUpdates.jsp?product=010-00697-02&cID=145&pID=14904

    official page : http://www8.garmin.com/support/download_details.jsp?id=4051

     

    they should made a 100% stable bug-free version first ...

    develop a lot of beta versions with new features ecc....

    then release another 100% stable version...

     

    (xcuse my bad english :) )

  2. These "toys" as you call it, are used by millions of people, everybody handles it it's own way with thousands of different maps, many in different profiles and/or shortcuts, used by hikers, kayak, car and airplanes, or whatever, in extreme heat or cold, so we really stretch it to the limit.

    In 8 weeks we had about 1 update every few days, by now most of the issues are solved.

    If your Montana problem is not fixed with the new update it seems to take ages until your problem is solved, but after 2 month I think they did a quite decent job this time.

    Not all Montana's crashes are because of the software, users can be very tricky too and even high-tech professional stuff crashes sometimes.

     

    i undestand this...

    but ( i'm a developer ) .. when i fix a bug i can't create a new bug in different places..brand new problems in working existing procedures.

    when i compile my source code i must complete a full beta testing cycle before publish my program...

     

    montana's developer must flag FW as "BETA FW" ;)

  3. It's incredibile..every time i use my montana after a new FW release..i found new orrible bugs.

    NOW route/trip planner ( "Pianifica Percorso" in Italian ) stop working..every time i select an existing trip when i select "Map"..montana shutdown; if i create a new trip...same thing.

    I've created a new shortcut for map change...but again..it don't work, same active maps....no changes

    after 4-5 minutes of playing inside shortcuts menu...montana lock for 2 seconds then CRASH..

     

    it's incredibile i'm an developer too...and i can't understand why every time they release a new FW there must be new problems.

  4. ZAGGs must be used on gass-type screens with "capacitor touch" ( like Iphone etc. ) NOT "resistive touch"

     

    Zagg markets a screen protector for the Oregon series and Dakota series, both of these units have resistive touch. Perhaps Zagg doesn't know these units have resistive touch?

     

    With standard screens protector it's impossible to break the unit

     

    1. wrong product

    Or

    2. uman error..

     

    .i don't believe in a Montana's defect

  5. i'm not find this on Zagg webpage, but the adesive-solution result in strong stress for non-gass surfaces..glue (et similia) based solution are usually used with glass surfaces only like IPad, Iphone ecc (capacitive touch)

     

    For my montana i've used standard cellular screen protector and installed it underwater for a "bubbleless" installation ^^

  6. i've placed and removed my screen protector 5-6 times ( on Montana ) until I put it correctly; no problems here, screen is perfect

     

    I don't believe you did this with a ZAGG brand screen protector. The adhesive on the ZAGGs is many times stronger than on most protectors, so much so that the act of removing a fully cured ZAGG will so stretch the ZAGG that you can't put it back on.

     

    ZAGGs must be used on gass-type screens with "capacitor touch" ( like Iphone etc. ) NOT "resistive touch"

  7. they answer me today..developers write me they are following forums ( and yes, this thread .. ) for a complete users error log

     

    original :

     

    We do read several of our user forums including this one and are working with several of their forum members on some of these issues.

     

    Thanks

    Garmin Montana Software Team

  8. Here is the photo issue I was referring to in an earlier post. Standard mode in less then ideal light. Low light mode does NOT show this artifact. The issue is the shaded line that runs horizontally through the picture. It's more of a brightness boundary then a line. The top half of the photograph is darker (less exposed) then the bottom half.

     

    1310659452.jpg

     

    stupid question...the lens is clear ?

  9. "3) The 3D view position indicator arrow is often in the wrong place. Test: toggle between the main map screen and the 3D view screen. For some reason this prompts the error more often . I'd say about 1 out of 10 times that I open the 3D view my position indicator is a city block or two off of my actual position. When I toggle between the main map screen and the 3D view screen the ocurrence jumps to about 7 out of 10."

     

    2.50 and 2.60..same problem in both FW

  10. Anyone else notice a shade line that shows up near the center of any photo taken in lower light conditions? Take one in a room or inside your house and look for the line. I hope I don't have a bad sensor.

     

    I don't have any line on my pictures taken in low light mode.

     

    Well it does show up in "Standard Mode" in less than ideal lighting conditions. How would a user know when the cutoff is to switch to low light mode and when to keep it in Standard? I wouldn't want to get back from a hiking trip only to realize I should have switched to low light mode because some of my photos have lines through them. Hopefully the good folks at Garmin can get this resolved in a future update. Maybe greasing the skids with a few emails from other folks wouldn't hurt either.

     

    LowLight mode is an ISO amplification, a voltage amplification for the sensor...this could create a vertical line in high-constrast situation ( light spot for examples ) .. can you send me a photo with this problem ? i'm a naturalistic photographer ( as you've seen in my mail )and sometimes this happen in hight ISO photos ( vertical stripes ).. i think could be normal

×
×
  • Create New...