nivanov

My reception bars don't move past half the strength of the reception with nothing obstructing the sky - I even took it outside of the car to see the best case scenario. To compare, my bluetooth gps i-Blue 737 had much better reception from my glove box. It also held a reception to about 8 satellites on average, whereas F90BT holds 5-6. I just also want to say that in no way am I bashing the F-series. I think the overall unit quality is GREAT and features are amazing for the price. But if i wasn't looking to improve it, I wouldn't be on this forum, now, would I?

I'm not sure what you mean by hardwire? If you mean using the stock receiver, all i was saying is that it's not that great and there could be alternatives. I'll give it a shot over the weekend to see if i can get it working with the bluetooth gps.

That much trouble? That's very little trouble if it actually ends up working. I was set on buying a carputer but I could not find a double din screen/AM/FM/AMP combo with AM/FM and buttons being accessible from the OS. DL650 is the screen that came the closest to that, but the radio is independent, and so are the buttons. Also, carputer would run up well over a grand, whereas f90bt cost me around 600 with all necessary installation parts.

Hey everyone. I have a F90BT and my install looks pretty stock except for the GPS receiver. I couldn't route it well, since I did not want to remove the bigger dashboard panel (the one that has passenger-side airbag under it). So I have a wire going from the panel above my radio to the gps receiver near the windshield. I tried hiding the receiver in the glove compartment and right above the radio under the dash, but I noticed the gps signal losing strength - I had the unit running and i saw the reception strength lines going from green to yellow/red. I realized that i might actually be abl

Hey leet, no problem man, I understand. I've been trying to reverse-engineer the ipod library too, since I figured it would be a good start to get the Ipod player to work. As I mentioned before, I don't have that much experience with WinCE. I'm using PE Explorer, same tool I used for windows. It seems that the ipod.dll does have a bunch of useful functions, but PE Explorer does not read parameters that well: // ActiveiPodVR; Index 1; Information not available // AlphabetSearch; Index 2; Information not available // AttachToDebugManager; Index 3; Information not available // BrowseInd

Our options are IGO, IGuidance, Tomtom. There's also Destinator but I think it went out of business. These are the major players and I think these are the ones we should try to support.

Hopefully we can abstract the navigation part of the program, so, given a proper plugin, we can use any 3rd party application, including the ones you listed

I switched to VS 2008 and checked in all the file changes.

I structured the resource code so it would be easy to skin the application by providing different files for button images and stuff like that, so we'll definitely need someone to design the "default" skin. It would be nice to get the basic functionality going first though, but you can definitely contribute to GUI components. Thanks!

Yeah it should... Maybe I should upgrade? For now, please don't commit any non-text files to SVN, like sln or resx.

I created an SVN tree and uploaded some files to a repository on Assembla: http://www.assembla.com/spaces/OpenNav To contribute to the project you'll need Visual Studio 2005 with AnkhSVN installed (you can use other SVN clients too, but that one integrates well with VS). I also uploaded an emulator image we can use for debugging - you can find it in the Files section. I'll write a short guide to setting up the environment soon.

I confirmed today that if you are only using software bypass for the brake, you need to use USE_SEPARATED_SAFETY_MODE=0 attribute for both Button tags in order for the mute button to work while you are driving without parking brake engaged.

The more I think about this front-end, the more it looks like a more powerful Launcher, kind of like what LeetCoder. I'll PM him and see if he'd like to join us on this project.

Yeah boris is right. You can't run XP Embedded on a non-x86 platform. You need to write the application directly for WinCE running an ARM processor for it to be compatible with AVIC units. One can attempt to port one of the pieces of software from x86 to ARM but I imagine it's a huge pain.

We'll probably end up using .NET CF 2.0, which is, by default, not installed on WinCE 5. It is pretty simple to deploy it though.

Thanks! Gonna give it a try tonight!

Hey everyone, I recently posted this idea under the topic about AVIC running Linux. Although, Linux is definitely an option for this system, I think it's a bit of an overkill. I was thinking of rewriting the front-end in managed .NET code for .NET CF platform, and I'm trying to see how many people would be willing to contribute. I'd want to keep it open-source and free, so by contributing, I mostly mean "code". Please reply if you have programming experience in .NET or Java. Here are a few advantages as well as potential hurdles: Pros: -.NET is easier so the programming community i

Most car-pc projects are x86-compatible, which means they are able to run regular Windows, like WinXP. Centrafuse is a decent front-end, but unfortunately, it doesn't run under WinCE.

I was thinking more of .NET CF replacement shell with some heavy interop. I'm a .NET programmer, and though it is definitely slower than straight c++, it is MUCH easier to use in WinCE. I don't think I can tackle the whole thing myself though, so I'd be curious to see if there are enough people that are willing to contribute on a replacement shell initiative. Clearly, it would be better since any customization in that case is possible. Additionally, Pioneer contains all the necessary libraries to talk to Ipod, play mp3/mp4/aac audio/video files, and maybe even interactions with IGO. ...Ma

Hey everyone. I recently got F90BT and so far it's been great apart from some small inconveniences. One of those is the lack of a headphone jack (or minijack as I think they are called) input so you can connect an mp3 player (other than the ipod, which has its own dedicated connection). The front panel minijack is supposed to be used with a Minijack-to-composite cable CD-RM10 ONLY. I looked in the manual and it shows the pin-out of the input. I was wondering if that pin-out happens to match the standard headphone jack pin-out (except for the lack of video of course). I'm pretty handy with a so

It looks like this hack only works when the unit is bypassed. I did the software bypass but did not ground the parking break wire and I could only press it when i pulled my handbrake up a little bit. I wonder if adding the USE_SEPARATED_SAFETY_MODE attribute and setting it to 0 to either of the buttons would allow me to press those buttons regardless of the parking brake state.

Thanks guys. Ironic - I'll try what you suggested tonight, thanks! Terrons - I'm a software engineer and know quite a bit about programming, but if I understand the pioneer software correctly, the sound coming from IGO is handled separately by another application. That application is a compiled .exe file, and those are an absolute bitch to change. I don't know assembly language well enough, especially ARM assembly, which is the type of processor the avic f-series has. I think our best guess is to hope the pioneer people will actually implement this feature in the future. I'll shoot them an

Hey everyone, I just recentlly installed my new F90BT into Toyota Yaris 2007 and it's working great. One complaint I have, though, is that the Ipod keeps playing when a unit mutes the AV1 input. Is there a way to make the Ipod pause playback when directions are read? I decided to settle for quieter music when directions are read but then I stumbled on another problem. When I go to AV settings, I used to be able to choose between Mute, ATT (quieter music), and Normal. Now that option is grayed out and is stuck on Mute. The manual said something about that option only being available when

Thanks! I found some diagrams online about the speed sense (tachometer) wire being right under the little box compartment on the left side of the steering column - hopefully i'll have no problem hooking it in there. I had no idea about the antenna - I haven't taken my dashboard apart yet, so I'm not sure what to expect so I'm trying to collect as much data as possible before opening it up - my dash bezel should be arriving today, so I don't have much time left to wait. I also have a Yaris 2007. It's not the "S" model, but it has a power package, which includes 3" screen integrated radio so I

Hey, I got the wiring harness from Crutchfield and what do you know - all wires match up. However, I still have to hook up the parking break wire as well as the speed pulse wire. I'm not going to hook up the reverse wire, since I'm not using a reverse camera. Devenlf, do you remember exactly where you hooked up the speed pulse cable and parking break cable? I'm not worried as much about the parking break cable, since it probably goes from the parking break itself which is pretty close to the center console. However, I have no idea where to look for the speed pulse cable. Any ideas? EDI