Jump to content
AVIC411.com

Stephanie

Members
  • Content Count

    220
  • Joined

  • Last visited

About Stephanie

  • Rank
    Member

Profile Information

  • Location
    http://www.felesmagus.com/stuff/steph_data.zip for my current files
  • Interests
    Almost everything, one thing at a time.
  1. If the wiring kit didn't come with a diagram or anything, then have a close look at the wires themselves. The Rav4 harness kit I bought didn't come with any information, but there was very small, light (silver coloured) writing on each wire that described what it was for. Cheers!
  2. I'd double check that the parking brake wire is properly grounded. If the software bypass works if you engage the parking brake slightly, then it should work when the parking brake wire is grounded. Having the parking brake engaged slightly just grounds the line. When you ground the parking brake wire, tie it to the negative / black wire that grounds the nav unit. Use a continuity tester or DMM to verify that it is truly grounded.
  3. I was going to add this to another thread, but after thinking it over, I figured that this deserves it's own spot, so hopefully more people will see it. I'm sure that experienced programmers/hackers will already be familiar with these, but for those who are just getting started, these are good rules to live/code/hack by. The following are a list of tips and cautions, that can save a lot of grief and stress when it comes to modifying your navi. #1 - Make A Backup! Most of the hacks/mods revolve around the data.zip file. Make a backup to leave on your head unit (rename it data.bak or
  4. I haven't tried movies at all so can't help there, sorry. Re the NSEW thing, I can get it to display a 'linear compass' which basically is like one of those old floating compasses, it floats the letters along on the screen. The code is already in place in the files, just not displayed, so it's just a matter of enabling it. Oh and the compass.bmp they had was backwards (E and W were backwards) so I had to make my own graphic for that. Sadly there is no way I can find to display the heading in degrees.
  5. If you have the three bars of info displayed on the lower left corner, speed limit is one of the functions you can opt to have put in there. It's under settings, navi settings, visual, displayed info. Otherwise if you want to add a custom bit of text for it, just use search. The speed limit code has already been posted in this forum, I believe.
  6. A note in the manual (page 179) made me try moving my music up a directory level when I first tried it out. It's a small little thing, but it solved the problem for me at least. I took that to mean, if a folder contains no music at all (even if it has subdirectories which themselves have music), the folder's contents will not be displayed. They have an illustration on that page that shows music in various subdirectory levels, but every level does contain some music.
  7. I'm going to give up on this one.. I've tried every variable I can think of, every combination of textmodel I can think of, and nothing comes up at all. At this stage, I don't think there is a way to access the data. I know the data is in there, of course, but there doesn't seem to be a way to display it other than the zoombar. Of all the variables I tried, I thought these had the most potential: map.zoom_level_in_map map.zoom_level_in_navigate map.zoomlevel Unfortunately none of the textmodels revealed any data for me, nor any of the text methods. I have a feeling that the
  8. I noticed one quirk that might affect how it looks at the SD cards. Mind you this was a 2GB card, but it might affect the larger ones as well. I found that it would only search one level of directories for music. If it found no music in the first level of subdirectories, it gave up. So this works: SD Card -->Album1 (folder) ---->Song1.mp3 ---->Song2.mp3 ---->Song3.mp3 -->Album2 (folder) ---->Song1.mp3 ---->Song2.mp3 ---->Song3.mp3 But this does not work: SD Card -->Music (folder) ---->Album1 (folder) ------>Song1.mp3 ------>Song2.mp3 ----
  9. It seems to me that there's an awful lot of button-pressing just to get anything done. It is possible to make a shortcut button to get from the map screen to virtually any other navigation / iGo screen, if you know the trick. Personally, I use the Favorites a lot, and it was annoying to have to push Menu, then Destination, then Favorites. (No wonder they want you to be in Park to do anything - you have to press so many buttons and read so many screens!) In the example below, I'm going to make a display function (specifically, the Clock) become a clickable button by adding a bit of code
  10. x=### is the value in pixels from the left side of the screen to the left edge of the text. y=### is the value in pixels from the top of the screen to the top edge of the text. w=### is the width of the text in pixels (handy for centring or right-justifying) z=### is the 'layer' to get stuff above other stuff. Higher z = more visible. Useful for putting text ontop of background graphics. h=### is the height of the text in pixels (handy for vertical alignment) Cheers! edited to add: All of which means, to move the text up, make the Y number smaller.
  11. The dot is your true GPS position. The arrow is the snapped-to-road position. If the snap-to-road is turned off, it would show you as being offroad somewhere. I get that going into parking lots etc, the dot would show me actually in the parking lot while the arrow would bounce around from road to road trying to lock me to something. That's why I wanted to disable the snap-to-road thing.
  12. Sorry - I forgot there were 3 more lines to comment out: ;runif nVehicle 5 'rdkeepposon.enable, rdkeepposoff.enable' ;else_runif nVehicle 6 'rdkeepposon.enable, rdkeepposoff.enable' ;else_run 'rdkeepposon.disable, rdkeepposoff.disable' When those lines are not commented, they disable the keep gps on road unless your vehicle is a bike or pedestrian. Comment them out to enable the buttons for all vehicles.
  13. The images are in the Images.Res file in My Flash Drive\APL The program that displays the information is not part of the iGo software. I believe this is the command that launches it: EXEC "other.pioneer.postmessage" "AV" "WM_APP_AV_IGOMAP" 1 That line is in data.zip\ui_pioneer\common\ui\navigatemap.ui As far as I have seen, there's no way to move it around, you can just suppress it by commenting out that line.
  14. Well I tried those variables this morning, and it didn't pitch any errors, but it didn't display anything either. This means that either the variables I guessed at don't actually exist, or that the textmodel I used is incorrect for the type of data in the variables. I'll test again with different textmodels and see if anything turns up. I'm sure there must be a way to display something, it's just a matter of finding the right variable and matching textmodel. Cheers!
×
×
  • Create New...