[Archive] TomTom v9 Firmware and Maps - Page 249 - GSM-Forum

Zebra92 · 07-05-2012, 18:15

Quote:

Originally Posted by dsa8310

I had recently reset to factory settings my go910 and mysteriously the RDS/TMC side bar has appeared. Then, after browsing through a few NCs, it has disappeared again ( I don't have an actual RDS receiver).
I am using currently the 25 (aka x30) mode, NC v9.450 with K50, but a different/default kernel could maybe change the RDS status.
Anyway, before resetting, save your favorite destinations (file mapsettings.cfg), and check the RDS out both before and after restoring them.

I try resetting to default and I try different Nc the first one supporting RDS/TMC in X40 emulation is 9.205 in descending order for sure in my GO 910.
RDS/TMC receiver is small, expensive but very usefull.

So, I will try new map in 9.205 to see if it's ok for MAPSHARE with the new TTHOME.

I will give the result after testing.

Thank for your help.

Zebra92 · 07-06-2012, 10:50

I tried with the new map but infortunatly it goes into a loop of reboot.
I reinstalled the old map and it works again.
So, for the moment I have no other choice, I can't use the new map for an unknown reason and mapshare for an unknown reason....
Perhaps a trick will be find to solve the RDS/TMC support with X40 emulation but today I am obliged toi stick with the old stuff.

omolino · 07-07-2012, 21:51

i was testing new swap yesterday driving some km long...

My One is V6 then i did a NC with MB

my first impresion was bad, it was slow moving betwen screens and it was realy freezing, i supouse that it is the time when the swap was writting.

Then it pass and starts to work well the position was realy exact and in other NC loquendo freeze the screen when he is spoken but not in this the navigation is realy flow and realy perfect
Then i return to the menus and it was movig perfect betwen screens...

I thik all is ok but i maybe 24Mb is to much for a 32RAM engine, and when it was writting the swap the time is slow
I thin that 12-16 is enought

but why not a button to select this ? because not all the Ones using the same SD or the internal memori has the same velocity.

------------------------------------------------------------------

in other hand....
i realy need help with IDA, because when i see the origina PDNavigator i see one kind of code !!!

But when i see the same PDNavigator but with ONE BIT changing then i sow a diferent code !!!

How i going to find a pattern ????

Thanks.

dsa8310 · 07-08-2012, 13:08

The swap size no longer matters, it's another parameter that determines the duration of initial aggressive swapping.

Change in file skins/skins.sh (on device) the line reading:

if [ $rss -lt 23 ]; then break; fi

Instead of 23 try bigger values, e.g. 27 ; don't go beyond 37, or initial swapping will be canceled.
But even with no initial swapping, memory boost will happen, but at a very slow rate - you may try it out too.

omolino · 07-08-2012, 14:01

This is exactly, were i was asking for...

The MB works PERFECT, but only have delays in the begining

big delays the first start
and small delays in others starts
AFTER starts it works PERFECT !!!

i going to try with 27
tomorrow i have to travel with this device and i will say the results.

There are a lot of devices, and diferent ONEs devices. I think that not all works at the same way, because the old Ones like V1, have a quick processador and better hardware but slow memories, the news ones like START have cheaper processor but memoirs more fast.

Thanks again.

Eramaavaris · 07-09-2012, 19:33

Quote:

Originally Posted by Zebra92

I tried with the new map but infortunatly it goes into a loop of reboot.
I reinstalled the old map and it works again.
So, for the moment I have no other choice, I can't use the new map for an unknown reason and mapshare for an unknown reason....

I'm not sure will this help you, but in every mapfolder you have file called mapsettings.cfg. If you have important favourites, places etc. write them down and after that delete all mapsettings.cfg -files. Now try to install new map/maps and try again.

Zebra92 · 07-09-2012, 21:24

@Eramaavaris,
I already have tried to delete mapsettings.cfg but with no success for the infinit loop of reboot.
That the reason I return back to the old goodies and now my GO 910 works perfectly but I don't use mapshare to update the map anymore...
Thank you for your help.

ahkp3 · 07-11-2012, 12:56

@DSA: I assume this will probably be in vain, but TomTom has just released the GPL-parts of the source code for the MyTomTom application here:
TomTom, portable GPS car navigation systems

Can you draw any useful information on how TT accesses the new devices via MyTomTom other than their filesystem is most likely ext2?

Sorry, for my previous behaviour. I was just a little fed up, but as soon as TT releases version 9.x GPL sourcecode I will certainly be back.

Regards,
ahkp3

ahkp3 · 07-12-2012, 11:33

Dear DSA again,

looks like TomTom did just release the GPL source code for all their version 9.x navcores. Please check it out here:

TomTom, portable GPS car navigation systems

Is that all what we wanted for a long time or do you need more?

Kind regards,
ahkp3

dsa8310 · 07-14-2012, 00:41

The highest kernel version I could find is apparently from NC v9.026:

zImage.473972

Please give it a try, just overwrite file dsa.app/Contents/Resources/Java/tomtom/zImage.mbs.v9 with the above file; keep name zImage.mbs.v9!

You may want to reinstall dsa first, from a modified dsa.app directory.
Then, you should reinstall your preferred v9 NC to device, with dsa & MB.

...
I cannot be sure it's the real v9.026 kernel, it's a mismatch between the file name on TT's GPL page and the actual downloaded file name.
But, a real x50 device owner could check it out (previously the fake zImage.mbs.v9 kernel did not work - now it would work?).
If it's an old kernel, then even non x50 devices would not work with any v9 NC (&MB).
Anyway, we are still away from a desirable v9.205 kernel, which is of version 547200. So TT was rather parsimonious with its release...

If it's OK, please let me know it, I would have to release a new dsa version too.

dsa8310 · 07-14-2012, 00:45

Quote:

Originally Posted by ahkp3

Dear DSA again,

looks like TomTom did just release the GPL source code for all their version 9.x navcores. Please check it out here:

TomTom, portable GPS car navigation systems

Is that all what we wanted for a long time or do you need more?

Kind regards,
ahkp3

Nothing happens by chance

Thanks!

ahkp3 · 07-14-2012, 09:44

Quote:

Originally Posted by dsa8310

The highest kernel version I could find is apparently from NC v9.026: build 473972
....
Anyway, we are still away from a desirable v9.205 kernel, which is of version 547200. So TT was rather parsimonious with its release...

Build 473972 is near the beginning of the new V9.xxx GPL release list. What about the rest of the builds, like 567329, 734578, 797162 and 842337?

TT switched over to linux base version 2.6.23.17 instead of 2.6.13 for those.

I don't seem to get it, what am I missing? Did TomTom hide [again] linux versions, that should be published?

dsa8310 · 07-14-2012, 10:30

I don't think the kernel for any v9 NC is of version 2.6.23 but of version 2.6.13 .
I cannot double check things out right now, but a simple BT Console or even TT Tool run of command "uname" would tell the real version for a recent v9 NC like v9.205, v9.160, v9.450, etc.

ahkp3 · 07-14-2012, 10:47

Quote:

Originally Posted by dsa8310

I don't think the kernel for any v9 NC is of version 2.6.23 but of version 2.6.13 .
I cannot double check things out right now, but a simple BT Console or even TT Tool run of command "uname" would tell the real version for a recent v9 NC like v9.205, v9.160, v9.450, etc.

I just checked the build numbers of some of my favourite Navcores:
8.550 runs build 342869 -> NOT published
8.562 runs build 331278 -> NOT published
9.205 runs build 547200 -> NOT published
9.430 and 9.450 run build 842337 -> IS published

Well, compliance with GPL is something totally different than what TomTom just delivered. That was just a nice teaser. I am really fed up with TomTom by now.

We need to check whether 9.430 or 9.450 runs really kernel version 2.6.23.17? Can someone with access to the console or TT Tool run the uname command on his device, please? That would be great and thanks in advance.

dsa8310 · 07-14-2012, 13:05

I was right, v8, v9 they use kernel 2.6.13.
2.6.23 is actually a v10 kernel (with SWAP enabled by default!).

I wouldn't really need ALL kernels, just a few good ones.
v9.205 would be ideal.
But this v9.026 kernel (zImage.473972) seems OK on my go910 & MB.

I will have to release a new dsa then... in August?!

07-12-2012, 11:33	#3729 (permalink)
ahkp3 Major Poster Join Date: Jun 2011 Posts: 45 Member: 1594667 Status: Offline Thanks: 20 Thanked 8 Times in 8 Posts	GPL source codes for Navcore version 9.x released Dear DSA again, looks like TomTom did just release the GPL source code for all their version 9.x navcores. Please check it out here: TomTom, portable GPS car navigation systems Is that all what we wanted for a long time or do you need more? Kind regards, ahkp3

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
thread	Thread Starter	Forum	Replies	Last Post
TomTom v8 Firmware and Maps	BuMobiles	GPS devices , Navigators & Maps	5948	03-31-2013 10:47
TomTom v7 Firmware and Maps	BuMobiles	GPS devices , Navigators & Maps	3479	03-05-2013 21:55
how to install tomtom V6 software and maps on NAVMAN F20	sniper007	GPS devices , Navigators & Maps	4	11-06-2012 17:58
TomTom v6-7 and Route 66 v6 Firmware and Maps	BuMobiles	GPS devices , Navigators & Maps	4687	05-25-2012 15:52

07-06-2012, 10:50	#3722 (permalink)
Zebra92 Crazy Poster Join Date: Oct 2009 Posts: 58 Member: 1145396 Status: Offline Thanks: 1 Thanked 3 Times in 3 Posts	I tried with the new map but infortunatly it goes into a loop of reboot. I reinstalled the old map and it works again. So, for the moment I have no other choice, I can't use the new map for an unknown reason and mapshare for an unknown reason.... Perhaps a trick will be find to solve the RDS/TMC support with X40 emulation but today I am obliged toi stick with the old stuff.

07-07-2012, 21:51	#3723 (permalink)
omolino Freak Poster Join Date: Dec 2009 Posts: 172 Member: 1177877 Status: Online Thanks: 59 Thanked 18 Times in 16 Posts	i was testing new swap yesterday driving some km long... My One is V6 then i did a NC with MB my first impresion was bad, it was slow moving betwen screens and it was realy freezing, i supouse that it is the time when the swap was writting. Then it pass and starts to work well the position was realy exact and in other NC loquendo freeze the screen when he is spoken but not in this the navigation is realy flow and realy perfect Then i return to the menus and it was movig perfect betwen screens... I thik all is ok but i maybe 24Mb is to much for a 32RAM engine, and when it was writting the swap the time is slow I thin that 12-16 is enought but why not a button to select this ? because not all the Ones using the same SD or the internal memori has the same velocity. ------------------------------------------------------------------ in other hand.... i realy need help with IDA, because when i see the origina PDNavigator i see one kind of code !!! But when i see the same PDNavigator but with ONE BIT changing then i sow a diferent code !!! How i going to find a pattern ???? Thanks.

07-08-2012, 13:08	#3724 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,565 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	The swap size no longer matters, it's another parameter that determines the duration of initial aggressive swapping. Change in file skins/skins.sh (on device) the line reading: if [ $rss -lt 23 ]; then break; fi Instead of 23 try bigger values, e.g. 27 ; don't go beyond 37, or initial swapping will be canceled. But even with no initial swapping, memory boost will happen, but at a very slow rate - you may try it out too.

07-08-2012, 14:01	#3725 (permalink)
omolino Freak Poster Join Date: Dec 2009 Posts: 172 Member: 1177877 Status: Online Thanks: 59 Thanked 18 Times in 16 Posts	This is exactly, were i was asking for... The MB works PERFECT, but only have delays in the begining big delays the first start and small delays in others starts AFTER starts it works PERFECT !!! i going to try with 27 tomorrow i have to travel with this device and i will say the results. There are a lot of devices, and diferent ONEs devices. I think that not all works at the same way, because the old Ones like V1, have a quick processador and better hardware but slow memories, the news ones like START have cheaper processor but memoirs more fast. Thanks again.

07-09-2012, 21:24	#3727 (permalink)
Zebra92 Crazy Poster Join Date: Oct 2009 Posts: 58 Member: 1145396 Status: Offline Thanks: 1 Thanked 3 Times in 3 Posts	@Eramaavaris, I already have tried to delete mapsettings.cfg but with no success for the infinit loop of reboot. That the reason I return back to the old goodies and now my GO 910 works perfectly but I don't use mapshare to update the map anymore... Thank you for your help.

07-11-2012, 12:56	#3728 (permalink)
ahkp3 Major Poster Join Date: Jun 2011 Posts: 45 Member: 1594667 Status: Offline Thanks: 20 Thanked 8 Times in 8 Posts	@DSA: I assume this will probably be in vain, but TomTom has just released the GPL-parts of the source code for the MyTomTom application here: TomTom, portable GPS car navigation systems Can you draw any useful information on how TT accesses the new devices via MyTomTom other than their filesystem is most likely ext2? Sorry, for my previous behaviour. I was just a little fed up, but as soon as TT releases version 9.x GPL sourcecode I will certainly be back. Regards, ahkp3

07-14-2012, 00:41	#3730 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,565 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	The highest kernel version I could find is apparently from NC v9.026: zImage.473972 Please give it a try, just overwrite file dsa.app/Contents/Resources/Java/tomtom/zImage.mbs.v9 with the above file; keep name zImage.mbs.v9! You may want to reinstall dsa first, from a modified dsa.app directory. Then, you should reinstall your preferred v9 NC to device, with dsa & MB. ... I cannot be sure it's the real v9.026 kernel, it's a mismatch between the file name on TT's GPL page and the actual downloaded file name. But, a real x50 device owner could check it out (previously the fake zImage.mbs.v9 kernel did not work - now it would work?). If it's an old kernel, then even non x50 devices would not work with any v9 NC (&MB). Anyway, we are still away from a desirable v9.205 kernel, which is of version 547200. So TT was rather parsimonious with its release... If it's OK, please let me know it, I would have to release a new dsa version too.

07-14-2012, 10:30	#3733 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,565 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	I don't think the kernel for any v9 NC is of version 2.6.23 but of version 2.6.13 . I cannot double check things out right now, but a simple BT Console or even TT Tool run of command "uname" would tell the real version for a recent v9 NC like v9.205, v9.160, v9.450, etc.

07-14-2012, 13:05	#3735 (permalink)
dsa8310 No Life Poster Join Date: Feb 2009 Posts: 2,565 Member: 973199 Status: Offline Thanks: 204 Thanked 1,591 Times in 775 Posts	I was right, v8, v9 they use kernel 2.6.13. 2.6.23 is actually a v10 kernel (with SWAP enabled by default!). I wouldn't really need ALL kernels, just a few good ones. v9.205 would be ideal. But this v9.026 kernel (zImage.473972) seems OK on my go910 & MB. I will have to release a new dsa then... in August?!