I'm in the same boat, seems all good so far, managed to get my speedcams working by changing to skin 35 I believe it was... have the 3 box status bar which I like on my TomTom One V3, I also have the height11 plugin working well on it which is cool around here as we drive a lot of mountain passes and vocalizer tts. I have about 6.9mb free ram but that changes often but its never gone below 6mb with this navicore. The framerate seems Ok, not as good as the proper navicore but still ok, better than with the 8.xxx navicores. I've never had a weird reboot happen but I did only have 10mb free space on my device when I started it so I have no idea how making the swapfile went with such a small amount of free space. I could delete some stuff but there isn't much on there to delete that I don't need? where is the swap file so I can see how big it is?

If i free some space, delete the swap file and restart the tomtom will it recreate it bigger?

What's the best bootloader to use on a Tomtom One V3, I still have its original one which was 5.5128. It seems to be ok but sometimes when I boot right since it was brand new and unmodified it sits there trying to pickup satellites forever until I hard reset it then it works within a few seconds, It's not the fault of the navicore as its done it with every one I've used over the years so I assume its the bootloader causing that?

IQ Routes and ALG appear to be working fine. Menu movement is quick.

Thanks

phrunt wrote:I also have the height11 plugin working well on it which is cool around here as we drive a lot of mountain passes

Height 17 is the current version.

Thanks, updated mine to 17

Downunder35m wrote:@defibf : same for you if the skin changer is not visible edit the reskin file, otherwise selevet XL Live for the emu (36)

NT

Thanks I will give it a try

This navcore runs fine on my TT ONE V1 (2005) in X50 emulation

At least in this way:
- Put navcore on an empty 4GB SDcard
- Added Europe_890_4222
- Added "voices" folder, with 1, non-computervoice
- Removed ASR and Loquendo folder
- 1st boot until "you cannot use this map, etc"
- Ran fastactivate
- Choose X50 "skin"

Planned a 200 KM trip and drove it, all fine.

What do I like about this navcore:
- the fact that its even (made) possible to run it on a 7 year old device.
- the skins + chooser
- the ability to use a map early, because the metacode always first for NC9 maps.

What I don't like:
- I miss the ideal combination of the efficient "old" status bar, with the GPS-status in the right corner and the modern X50 menu, like in the 8.412 SE navcore.

Regards.

on my TomTom one v3 the speed thing down the bottom left corner is absolutely tiny, especially when it changes to 100km/h or higher, is there anyway to make this bigger? I assume its because of my smaller screen its doing it. It used to be rather big on older navicores, its in the 3 segment status bar on the far left corner, oddly there is room in the box for it to be much bigger but it just goes tiny. Is there a way to change it to a larger font size?

Not that I know of, it is either 2pane or 3pane with the small font.
I guess it is a limitation in regards to the screen resolution.

well x50 emulation is perfect except i cant get safety cameras to work under it, the menu option just isnt there but the current speed/speed limit thing is the correct size with the 3 box status bar

Set the cams correctly in a different emu, than change to x50 and do a route simulation for a stretch of road you know it has a cam (and the TT shows it).
If I'm not mistaken and TT kept this loophole the cams will work as setup even if you don't have the menu option for them.

phrunt wrote:well x50 emulation is perfect except i cant get safety cameras to work under it, the menu option just isnt there

With SE 9.450 X50, the speed cam option is in Main Menu, TomTom Services.

it doesn't show up there on my tomtom one v3 with x50 emulation, maybe it needs that bton setting like in older versions? I will try what you said downunder thanks

ok your trick worked fine downunder, but i have a new problem... on the new zealand map the tom computer voice works well and speaks as expected, when i switch to the australia map before saying any street name it goes something like this ... turn right language en street name... for some reason its putting in a language en in there... i think it says language en anyway, it says language and i think the next part is "En" its the australia 8.90.4278 map.

tried reverting to the 885 australia map, same problem... doesnt happen on the nz maps though... strange and so frustrating! its something to do with this navicore and vocalizer voices

any ideas?

-- update : i put on the kate voice off your full backup downunder and removed vocalizer completely and kate seems to read the street names properly on au and nz maps... although i didnt think i was able to use these voices on a tomtom one v3, they have probably slowed it down a little but not enough to notice a major performance problem... i still have 9mb free with a drive demo from sydney to brisbane too... more than i had with a vocalizer voice... should i leave it like this or will stuff go wrong?

Well, using TTS voice and support for the latest full featured maps were the main reasons why I uploaded this release ;)
Since it seems all is working fine you can discard the old vocalizer voices and stick to the TTS voices.
If you notice that some freeways/highways are prounounced weird check if reading street numbers is enabled in the voice settings - if so untick it ;)

The NC is optimised for 32mb devices and will free additional Ram as soon as it drops below about 5.4mb, so you will always have enough Ram for full "service".
Only downside is the delay until the swap is created and the slow start/response after a cold start, but once running it should work just fine.

Brilliant, Thanks so much downunder... I'm very happy with it, it's been flawless so far using the loquendo voice and oddly the voice uses less space on my tomtom than the vocalizer voice did and I have more memory using it than vocalizer... and sounds better. I will untick that option. I live in New Zealand but Im from Brisbane and am back there regularly, I'm going in 2 weeks so I was hoping to get that Australian speech problem solved by then but looks like its solved now. The one way I've been able to solve the tiny little speed thing is by using the TomTom Start emulation, it's the only one with it big but I can deal with that, it doesn't seem I lose many features except the compass. The menu's are just more limited but most the features are still there. I had it good with the TomTom One emulation and it had all the menu options and big speed segment but it doesn't seem to support IQ Routes. I can't win :)

Thanks again though, at least its all working now and I have a funky better sounding voice.

You can use the "template" in my thread to create your own custom menu with the things you need ;)