Tue Mar 12, 2013 11:21 pm
Wed Mar 13, 2013 8:34 am
Wed Mar 13, 2013 10:30 am
Wed Mar 13, 2013 8:06 pm
filesupload100 wrote:I didn't have any experience with what you describe, but I came across 2 settings that will be worth to check.
I'm using iGO 8.3.5.183522 so I hope this settings are in your version as well.
Settings-> Route Planning-> Options -> (next screen) -> Offroad mode (check-box)
Settings-> Navigation-> Off-route sensitivity (play with the scroll-bar)
Wed Mar 13, 2013 8:08 pm
bazzle wrote:Try agin with no speedcams in folder, then with no Dem etc to eliminate memory issues.
Bazzle
Thu Mar 14, 2013 2:20 am
Thu Mar 14, 2013 2:55 am
Thu Mar 14, 2013 1:16 pm
bazzle wrote:what are specs of your unit?
On SD card.
igo8
content\dem
content\speedcam
content\voice (tts files
content\building
all the above use up memory and can cause crashes when allocating resources.
If removing (renameing) any(all) of the above helps you may be able to reallocate memory in sys.txt
Bazzle
Thu Mar 14, 2013 1:21 pm
kamoteka wrote:I think this is a problem on older igo 8 versions, some dating back to 2009 and I experienced this myself. This was never a problem on later releases of igo8 and certainly unheard of on all versions Primo. The workaround I remember is to uncheck [Keep Position on Road] under Navigation settings.
There is actually an old thread/discussion about this here:
removed....
EDIT: the forum name is being changed to "disney", so just do a google search on "igo parking Lot Freeze".
Thu Mar 14, 2013 2:59 pm
EDIT - I wonder if I bought my own version of IGO and got something newer if it would work in my head unit?
Thu Mar 14, 2013 9:30 pm
nabi wrote:When your device really is 256 MB RAM, than you should not have any memory problem at all.
The parking lot freeze is solved in iGO8 a very long time ago. It was an issue in 2008-2009 and solved by a (at the time) new release. Anyway, if I remember correctly, it was the early 8.3.2.7**** and 8.3.2.8**** series that suffered that problem.
I can's say what date your build really is, because it is unknown to me. You say it is 8.3.5.151770.
Here is my problem with that. 8.3.5 is AFAIK introduced in march 2011. However the first known (by me) 8.3.5 build is 8.3.5.183522.(16 March 2011)
The last 6 numbers are always sequentially used by NavnGO. An example: early Primo 8.5.11.176142 is dated Jan 24 2011. Primo is an evolution of iGO8.3, but was released before 8.3.5.183522. This way of numbering builds chronological is valid for all iGO builds, including Android (iGO 9.6.7) and iPhone builds.
Well, in my list of programs (which is not THE final iGO list, but is considered all around reasonably up to date and correct - http://www.navitotal.com/showthread.php?913-List-of-iGO-8-Amigo-and-Primo-(Windows-CE-Based)-releases), 151770 should be placed (chronological) early July 2010.
Edit: Found some info : 8.3.5.151770, 14 July 2010, probably released on Airis t950, Argentina - added to my list.
When it is 8.3.5, it's long before the previously first known 8.3.5, while the error points to even more early 8.3.2 and with it, a release period long before July 2010 (= april 2009). Remarkable. I wonder why a "new" release reintroduced old program faults?
FYI
8.3.2 introduced 3D views and turn around 360° views of the map
8.3.4 added driver alerts
8.3.5 added truck/bus/mobilhome routing
A certainty is that this build is not wide spread. All I can find around the net about it are some posts on different forums. Mostly in Spanish, about the introduction? And then some problems post in different forums. All by you.
I won't stop you buying a new release, I just wonder why you ask here (and on "fellow" grey sites) such question?
Maybe it would be the easiest when you look around here and find you a working, "cured" and recent release for free? They all seem to work fine.
Like this one : http://www.navitotal.com/showthread.php?11942-iGO-8.3.5.231128-NavOn
Or a Primo? http://www.navitotal.com/forumdisplay.php?83-Program-(-data.zip-branding.zip-license)
In fact, I think you should upgrade to at least a stable build. A new world of GPS will open.
Thu Mar 14, 2013 10:06 pm
gsthunder wrote:
All I can do is post the version info that it tells me it is? Maybe this was something special for Astrium I don't know? All I know is it is the version number I provided and Astrium states they use IGO nav software with NAVTEQ maps. The Nav software version is 8.3.5.151770 and all the maps are 2012.Q3.
I have posted around the internet trying to find an answer is all. 4 Forums in total counting this one trying to get an answer.
gsthunder wrote:I believe this is the only site I have asked about buying a new version on. I didn't know it was wrong of me to want to buy the product? I am confused. I didn't come here initially looking for free stuff. I came here because there seems to be a lot of knowledgeable folks and I was not getting any answers from the head unit mfg or on IGO's site. I thought I might find the solution to the problems with the version I have, which other than this parking lot freeze up issue, works great.
Thanks for the help.
Fri Mar 15, 2013 4:04 pm
You want help/advise? Why bother to solve a issue that is solved in later builds, that are newer and better? Isn't it better then to upgrade to a newer build?
Again, I won't stop you when you want to buy it. Good for NavNGo. They can't blame us for giving the help they don't give. You are not the first experiencing this.
But you can get free builds as well. Just download one and place it on an SD (a new blank one !! never ever use the original SD !!! ), keep the same file structure and the same name for the .exe file, add the content (maps etc) and you are up and running.
Fri Mar 15, 2013 4:46 pm
Fri Mar 15, 2013 5:52 pm
gsthunder wrote:Why not fix the version I have if it is something simple? It came with the head unit and works great other than that 1 issue. Certainly that is easier than me having to "borrow" :D anything or mess with programming in the sys.txt and such wouldn't you agree?
gsthunder wrote:I don't understand your confusion. I simply was asking if there was a solution to this problem with my version. I prefer to use a legal version as well. I am not judging anyone or anything by that either.
I like this version and it works good other than the PLF so I see no reason to replace it if it is something that I can fix on this version.
Again, thanks for trying to help.