Garmin Firmware 3.7 - Another Lemon

[BikinOn]

Just a heads up for those who haven't been following this in other forums, it looks like Firmware v3.7 could be another lemon. I think I'll stick with v3.6 for now especially since 3.7 seems to be mainly aimed at reducing copyright infringement with maps. I'm beginning to suspect that Garmin do very little real world testing before releasing these updates.

http://forums.groundspeak.com/GC/index.php?s=e91ed6cf37d4176435c54059b1d1bc22&showtopic=319395&st=0&p=5347670&#entry5347670
http://garminoregon6xx.wikispaces.com/share/view/65927778

[Oscar's dad]

Just a heads up for those who haven't been following this in other forums, it looks like Firmware v3.7 could be another lemon. I think I'll stick with v3.6 for now especially since 3.7 seems to be mainly aimed at reducing copyright infringement with maps. I'm beginning to suspect that Garmin do very little real world testing before releasing these updates.

http://forums.groundspeak.com/GC/index.php?s=e91ed6cf37d4176435c54059b1d1bc22&showtopic=319395&st=0&p=5347670&#entry5347670
http://garminoregon6xx.wikispaces.com/share/view/65927778

This point needs emphasizing.  Reading the forum you link to it appears that users of unofficially sourced "unlocked" maps will have a big problem if they upgrade to v3.7.

[BikinOn]

Latest forum posts indicate that firmware 3.7 has been removed from Garmin's website, but it looks like Garmin are coming after people who have unofficial unlocked maps!

[Feanor]

It really depends on how the maps were unlocked.

Long ago, there was a keygen called Jetmouse that could generate a valid unlock file for your map / handset combo.
The map image remained encrypted on the device, but the keygenned key would unlock it for that device, as a genuine Garmin key would.
And so the world was for many years.

Then Garmin added GMA.
GMA was an additional layer of protection, added to later firmwares.
It would require a Garmin-signed file too, as well as the unlock file, in order to disrupt keygenned keys.

However, the current method of unlocking involves totally removing the encryption on the tiles inside mapsource itself, or inside the img file.   No keygen required, and GMA by-passed because the maps are Not Lockable.

Allegedly.

[BikinOn]

We'll I must admit I've always preferred OSM sourced maps for the bike, so I've no experience with unlocking Garmin maps, other than the one time I did it the "official" way, which was a royal pain in the bum!

The guys on the other forums seem to think Garmin are targeting unofficial unlockers, so I'd have to guess there's a way of doing that, perhaps it just the older methodology they are attacking. OTOH, Garmin have trouble producing a firmware update that fixes more problems than it creates, so people shouldn't be that concerned for now 

[fhills]

My Etrex 20 is still on version 3.0.
I can't see any great reason to upgrade it.
Just been onto the Garmin website to look for a list of updates but can't find any - am sure I have in the past - I find the Garmin web page a bit of a pig.
It keeps trying to encourage me to connect the unit to the PC with Garmin Communicator but I am wary of doing that in case it starts to force an update.
If someone can point me at a simple list of firmware updates and their alleged "improvements" please feel free.
My Etrex 20 freezes now and again but the solution is pretty easy - switch on and off or in worst cases remove and reinsert the batteries.
A bit of a fag but I have the idea that any update will be more of a fag.
And fair to assume that it will maybe soak up more of the unit's processing power?

[BikinOn]

It doesn't look like there's been a lot going on since v3.0, but the wiki says there have been two updates. Take a look and see if they are worth it, the last one has been out some months so it is presumably stable. I know I'm not going to touch any updates until others have tested them for at least a month, after the last couple of debacles!

http://garmin-etrex.wikispaces.com/firmware

[fhills]

Many thanks for that Bikinon - interesting - I can see myself sticking with current firmware until it dies.

I never even bothered to figure out what Garmin Adventures was all about - some sort of social networking trash? - I'd rather ride my bike.

[BikinOn]

Well firmware 3.8 has been released...
http://forums.groundspeak.com/GC/index.php?s=1777ca67bfd4ab0d454628f944742eec&showtopic=319730

Be afraid, be very afraid 

[Ningishzidda]

“Shuda bort a TomTom, ner ne ner ne ner ner.”

   

[BikinOn]

Well it's a point of view 

Just as a matter of interest, how fast does the Tom Tom go through batteries in your battery extender, on rides over 200K?

[Ningishzidda]

Well it's a point of view 

Just as a matter of interest, how fast does the Tom Tom go through batteries in your battery extender, on rides over 200K?

When the TT low batt level notice appears, I plug in the USB batt box. The TT internals recharge in about 4 hours while the TT is still running. The internals are 2200 mAHr.
The TT icon will be a 'lightning flash' while charging, and then change to a green battery when charging is complete.
I ride a 200 on the internals and the ride is finished with the 'lighning flash' showing.
One run of the internals and a set of 2700 mAHr rechargables will get me through a 300.

When running on internals, TT shuts the screen if there is more than two miles to the next instruction. When charging, it doesn't.
If I approach a junction and am curious, I tap the screen and the map appears, to shut down again after 10 seconds.

After using Garmin for ten years ( Legend and Edge 605 ) this is a VERY LOW price to pay for some intelligent autorouting and absence of firmware update jokes,,,,,

 

[BikinOn]

I've got to admit you're right about Garmin's Firmware updates, sadly I've seen this so many times working on programming projects, QA and general real world testing are often almost non-existent 

Interesting that the Tom Tom isn't that hungry for batteries, my Edge 705 managed a 600K, starting with a full charge and then plugging in an extender pack with 4 AA batteries. I'd guess the Oregon 600 would go through 6 batteries on a 600K and require a 2nd set to be used on anything but a really flat 300K.

I really haven't used the routing functions much, which I know you regard as one of the Tom Tom's big pluses. Last week, when my car's GPSr went on the fritz the Oregon got me through London OK, but on a small test "in country" it was keen to put me on rutted single tracks. To be fair I haven't really investigated the avoidance options too much.

[BikinOn]

Just a thought that came to me afterward on the subject of copy protection in maps. To be honest I'm not sure Feanor is correct when he says the new methodology removes all copy protection from the Garmin maps, I can think of at least two methods of copy protection that would remain.

The most obvious one is that used in OS paper maps, the copying of paper OS maps has been caught a number of times via their copy protection method, they deliberately put a number of small inaccuracies in their maps; if the inaccuracies are repeated in the other guy's map - it's a copy 

The other one, which is what I'd use if I were Garmin, is to bury another much smaller image, in pieces, within the map image (stochastic encryption? - can't remember the terms now, it's not really my field)

[Feanor]

Just a thought that came to me afterward on the subject of copy protection in maps. To be honest I'm not sure Feanor is correct when he says the new methodology removes all copy protection from the Garmin maps, I can think of at least two methods of copy protection that would remain.

The most obvious one is that used in OS paper maps, the copying of paper OS maps has been caught a number of times via their copy protection method, they deliberately put a number of small inaccuracies in their maps; if the inaccuracies are repeated in the other guy's map - it's a copy 

The other one, which is what I'd use if I were Garmin, is to bury another much smaller image, in pieces, within the map image (stochastic encryption? - can't remember the terms now, it's not really my field)

Is 'steganography' the word you're looking for?
Both of those things you mention will identify the copy as being from a Garmin original, but we're not trying to conceal that!

The workflow I alluded to allows you to use a copy of an original Garmin map on any GPS handset, exactly if it were an original Garmin map.   It's removing the encryption that 'locks' it to a particular handset.   If it's successfully unlocked, then it will be exactly like the Garmin original ( including any errors or steganography ), and that's exactly the desired outcome.

Anyways, I don't want to turn this into a warez forum, so I'm going to say no more on the issue.

[Ningishzidda]

IIRC, I used the unlock code to install Topo GB onto Mapsource.

After registering a particular handset Serial No. with Garmin, Mapsource allowed the map tiles to be loaded onto the handset.