gjas18 thanks for the clarification re. the map colours. I found those texture.bmp files and saw an explanation on an iGo forum that talked about messing with that stuff. Using rgb hex values makes a lot more sense.

Re. the contacts / phone book, IMHO it's easier (and more reliable!!) hacking the nav unit to manually update the sqlite database, than it is to screw around with the bluetooth contact transfer process.

Re. the startup screen, I thought I'd found an answer on this web site about the Miomap 3.3 which I just tried, but it didn't work. We'll see how that goes... it would have been too easy I guess for it to just be an entry in an ini file!

Aside from adding fonts and changing text colours and stuff, you can move / add / change entire elements. I've removed those three lines of information in the lower left corner, added a speedometer output there instead as standalone text, removed a few buttons on the right hand side, and added some static text in the upper left corner. The biggest stumbling block (aside from the slowness of the process) is that I can't find any documentation, outside of the comments that are scattered in the files. Without any documentation, there's so much trial and error and guesswork.

Anyhow if you google around about skins for the Mio or iGo, you'll see there's an awful lot of potential for customization with these units.

Cheers!

Stephanie (or anyone else)--I'm trying to find the navi "arrow" in the navigate map file and see if I can reduce the size a bit...do you see it anywhere?? I can't track it down.

ps--Love the speedometer and the Star Trek font!

So all I have to do is to edit that database file and addin all the contacts i need and I should be good to go!

 

so then everytime you have to update your phonebook, be it adding or deleting a contact, you have to edit the database again?

Yeah. But with the frequency that I add or delete a number from my cell phone, it doesn't really matter much. Besides, it's only a 5 minute process. Edit the database on my computer, load it onto the radio, and done.

Stephanie (or anyone else)--I'm trying to find the navi "arrow" in the navigate map file and see if I can reduce the size a bit...do you see it anywhere?? I can't track it down.

 

ps--Love the speedometer and the Star Trek font!

If you mean the red arrow they use to depict your posisition, there are a handful of files:

data.zip\ui_pioneer\common\daycar.bmp

data.zip\ui_pioneer\common\daycar.spr

data.zip\ui_pioneer\common\daycarghost.bmp

data.zip\ui_pioneer\common\daycarghost.spr

data.zip\ui_pioneer\common\nightcar.bmp

data.zip\ui_pioneer\common\nightcar.spr

data.zip\ui_pioneer\common\nightcarghost.bmp

data.zip\ui_pioneer\common\nightcarghost.spr

I don't know which one(s) you specifically would need to change.. but those are all related to the red arrow icon thing.

One more thing. Using SQLite to edit the phonebook database works very well. But I can't seem to get it to work with contacts that have more than 1 number. It recognizes the contact and asks which number I want to call, but I don't know how to name the individual contacts. I press the voice command button, and say "call work"... it then says there are more than 1 number for that contact and asks me to either say which i want to call or select it from the list. On the list, the two numbers are shown as "generaL5551234567" and "general5557654321"... basically calling each by the phone number with the word general in front of them. I can't figure out how to make the system call the numbers "office" and "shop" so that I can select them using voice command.

If you look in this picture, you can see I've got both numbers in there for this contact, but I'm not sure how (or where) to designate what the unit refers to each contact as. What is the dwType column for? I entered Shop and Office in the dwType column but that didn't help anything. Do I need to create a new column for the info the unit uses to name each of the contacts? And if so, what does it need to be named?

Another thing I noticed is you can replace all the system beeps wit custom ones just by replacing the original WAV files in the DATA > Sound folder... you could even replace them with something like the sounds that Windows or Mac OS use.

I replaced all my beep waves with silence. It's golden!

Re. the contacts, the four fields per record are:

ID - numerical, determines the order they appear in the contacts menu, and each ID must be unique.

chShowName - this is the text name which is displayed on the contacts screen

chPhoneCode - this is the phone number that will be dialed when you select a contact.

dwType - this is numeric, either a 1 or 2 or 3 and it determines if the number is 'home' or 'work' or something else. I do not know which is which. In my original phone book, everything showed up as 1 so that's how I kept it. I just made separate entries, so I'd do something like this:

1, Work #1, 5551234567, 1

2, Work #2, 5557654321, 1

Cheers!

Cool. I'll put a 1 and 2 in the dwType boxes and see what it displays them as.

I replaced all my beep waves with silence. It's golden!

 

Re. the contacts, the four fields per record are:

ID - numerical, determines the order they appear in the contacts menu, and each ID must be unique.

chShowName - this is the text name which is displayed on the contacts screen

chPhoneCode - this is the phone number that will be dialed when you select a contact.

dwType - this is numeric, either a 1 or 2 or 3 and it determines if the number is 'home' or 'work' or something else. I do not know which is which. In my original phone book, everything showed up as 1 so that's how I kept it. I just made separate entries, so I'd do something like this:

1, Work #1, 5551234567, 1

2, Work #2, 5557654321, 1

 

Cheers!

Type is what you want, but remember that the contact name is what VR is supposed to use (not that I've ever gotten mine to work).

0 - Other (Unknown maybe?)

1 - Home

2 - Work

3 - Mobile

4 - ???

5 - Main

I got it to work.

ID = order in which they are displayed on the contacts list

chShowName = name of contact

chPhoneCode = phone number

dwType = type of contact (1=home, 2=work, 3=mobile)

I'm hoping to find where to change:

1) Font for song title on map screen and possibly color of the background bars

2) Font for source (AV1, iPod, etc) on map screen

3) I am also curious what would happen if I decreased the navi arrow size (as mentioned above) in MS paint...sounds too easy but I'm scared hehe. Any thoughts?

4) Eliminate zoom level bar completely

I'm looking but I'm not that great with coding.

3) I am also curious what what happen if I decreased the navi arrow size (as mentioned above) in MS paint...sounds too easy but I'm scared hehe. Any thoughts?

i dont think paint is such a good idea because MS Paint doesnt have a transparent color. so when you transfer it back over it'll be an arrow inside a white box

Folks dont know if anyone has noticed but if you hold the MAP button down for 2 seconds it brings up the BRIGHTNESS screen. Why the hell they chose this screen to be triggered with the MAP button is beyond me. Anyway, can any of you see if this can be reassigned to the REARVIEW function. I think that should have been the first choice. This feature is on the DNX8120 and it is a nice feature.

i noticed that today. also if you hold the knob up while in map mode it zooms like really close.

when i go home tonight im going to search for the startup text if it even exists, see if it can be changed.

Folks dont know if anyone has noticed but if you hold the MAP button down for 2 seconds it brings up the BRIGHTNESS screen. Why the hell they chose this screen to be triggered with the MAP button is beyond me. Anyway, can any of you see if this can be reassigned to the REARVIEW function. I think that should have been the first choice. This feature is on the DNX8120 and it is a nice feature.

And for those of us without the rearview, either mute or delete route would be sweet.

An easier DELETE ROUTE function would definitely be cool.

Major props to Stephanie and HiFiSi for their contributions to this thread - I downloaded and installed Stephanie's data.zip file, which got rid of the empty green boxes on the map screen; and using HiFiSi's writeup on the phonebook database I was able to correct all the errors in my Contacts on the F90BT! These improvements, plus silencing the key beeps (again thanks to Stephanie) pretty much resolved all my remaining complaints with the F90BT. I guess I can just ignore Pioneer's official update part deux if and when it's released. (Unless it shortens the bootup time by about 85%.)

One remaining question concerning contacts - I'd like to be able to dial my work voicemail and have it take me straight in to my voicemail box, which means I need to insert pauses followed by numbers in the dial string. Any idea how to accomplish this? I tried commas, that didn't work.

**UPDATE** - Got it - inserted a capital "P" in the dial string after the main number; that forces a 2 second pause, then it dials the following string of numbers (in my case, access code for my voicemail box, then another "P", then 4-digit password.) Works great!

Folks dont know if anyone has noticed but if you hold the MAP button down for 2 seconds it brings up the BRIGHTNESS screen. Why the hell they chose this screen to be triggered with the MAP button is beyond me. Anyway, can any of you see if this can be reassigned to the REARVIEW function. I think that should have been the first choice. This feature is on the DNX8120 and it is a nice feature.

 

And for those of us without the rearview, either mute or delete route would be sweet.

if your in the map section you can hold down the main knob (volume and zoom) for 2 seconds it will mute.

Stephanie,

I went through every config file there is, im going to guess that the caution menu is hardcoded into the unit, since it doesnt use any of the outside graphics and it doesnt follow the same guides as the rest of the igo stuff. so maybe we can look into what actual igo users are doing to bypass this.

Stephanie, I'm looking around the Flash disk as I'm typing this, and I found some things...

-In ui_pioneer/800_480 (which I just noticed that 800x480 is the custom splash screen size), there's a bunch of files starting with 746_32K, and they are all the small icons used throughout the unit. The little green note next to the song playing while in map mode, the blue sphere under GPS and Time settings, the status bars to show reception, the little speedometer, etc etc. And they are all .bmp files with black backgrounds, which I think means these various icons can be changed.

-In those files, 746_32K_OM-71_32b is the little red crosshair that pops up everywhere. Will deleting this .bmp file get rid of the crosshair?

-In ui_pioneer_icons_poi, it looks like all the icons for the Points of interest, but I can't open them, since they're an 'ICON' file. Any way of getting around that?

-In ui_pioneer/common, files 746_32K_OM-300_24b and 746_32K_OM-301_24b are the green/white route arrows.

-Also, in ui_pioneer/common, is the car arrow. It's under daycar and nightcar. Lemonhead, I recall you saying you wanted to change them...there they are, bud

Note: All the .bmp files have a black background. My guess is that black is its transparent color, so if you attempt to change the icon, do it with a black background and don't use 100% black for the icon itself, use like 99%. Which would also explain why the night background is not fully black as well.

This is all I found so far that I fell was worth noting, but I'm going to keep searching.

CatchMeIfYouCan631, good observations. If you want to elminate the red crosshairs, I would suggest rather than deleting that bmp, just edit it to be fully 100% black. This way, the system won't throw a file-not-found error, but the 'crosshairs' will be invisible. If that doesn't work (if it just gives you black blobs all over the place) then replace the file with a copy of the blank bmp from earlier in this thread; that should replace the crosshairs with 1 pixel invisible dots.

I noticed the same thing with the bmp icons' black background; some of the bmps do appear to have transparency, but some seem to use black as their alpha colour. This might be defined somewhere in the .ui files, but it looks like the way to go.

Re. the .icon files, you might need to find a graphics program that can view them.

An easier DELETE ROUTE function would definitely be cool.

This sounded like a good idea and was pretty easy to implement. Add this line of code in navigate_800_480.ui just below the line that displays the time (it's in the first area near the top of the file).

You need to make some changes for position and the actual graphic.

The x=720 and y=140 will probably not look good, as there are other things in that area usually. I'd suggest x=720 if you want it in the same vertical column as the 3D/2D and compass but y=280 or so to move it down towards the lower right area of the map. You'll have to experiment as to where you want it, exactly.

I've attached the graphic I used below, it's basicaly just one of the ones already provided, but cropped to size. It goes in data.zip\ui_pioneer\800_480. You can of course use anything you like; if you want it to be the same size as what I've used, the size is 72x55 pixels.

What happens is when there is no route set, the button is invisible. When you have a route set (specifically, when there is a value in the distance-to-next-manoever) the button appears. When you tap it, you go straight to the Delete Route Yes/No confirmation screen.

Cheers!

KillRoute.bmp.zip

You must have already pursued this, but ... can you use that 'visiblemodel="navigation.distance_to_manuver.valid"' business for the blue boxes and the three times/distances on the lower-left? Or does it only work for the buttons on the right?

You must have already pursued this, but ... can you use that 'visiblemodel="navigation.distance_to_manuver.valid"' business for the blue boxes and the three times/distances on the lower-left? Or does it only work for the buttons on the right?

I tried it for the blue boxes and it didn't work. :/ It was one of the first things I tried, and I'mnot sure why it didn't work.

Edited for clarity: Although there are two kinds of file (visual elements, versus scripts) they all have the same file name of .ui which makes it confusing. The stuff that is in the 800_480\ui directory is almost all visual elements; the stuff that is in the common\ui directory is almost all scripts. Visual elements like and so on, can be turned on and off, or have any properties, manipulated by the scripts. So even though a visual element like the boxes or some text gets hidden or turned on and off in the visual file itself, the scripts can override that. So when I first tried to get rid of the blue boxes, I tried using the visiblemode property. However, it did not work because scripts overrode it and displayed them anyways.

As for using visiblemode on the three lines of text... it can't hurt to try. It is in navigate_800_480.ui. You could add the visiblemode stuff to each of the elements in it (there are 9 or 10 elements). However, I think the visibility mode gets overriden by scripting, for at least some of that stuff. So it might not be effective.

I re-read this thread, but I'm still lost - since I used Stephanie's great modded data.zip file to get rid of the boxes, when in a route the upcoming street names (which are in white) in the upper left-hand corner are barely visible. Exactly where do I go to change the color of that text to be more visible?

**UPDATE** - Fixed it - just changed the color code on the line that includes the text "navigation next street".