leetcoder

Im actually disassembling and modifying some functionality in the unit. Still trying to get acquaintance with the libraries that is used in the making of this unit. Im looking forward to code a fully working kiosk equivalent to pioneer working one that will boot up faster and more features. Mostly I will try to keep the original factory AVIC intact and running a modified one through SD Card. So far from testing the SDCard, it ran as fast as the internal memory or not noticeably different. After looking through the libraries, this unit seems to be fully modifiable. From this workaround b

UPDATES: 04/05/2009 LeetLauncher v3.0 - LeetCoder DISCLAIMER::: PROCEED AT YOUR OWN RISK! I WILL NOT TAKE ANY RESPONSIBILITY IF YOU BREAK YOUR PIONEER DECK. READ ALL THE DOCUMENTATION CAREFULLY BEFORE TRYING TO ATTEMPT ANY MODIFICATION. I DO NOT condone any illegal activity, nor am I responsible for your actions. I will NOT be providing any support on downloading maps or cracking any software. --------------------------------------------------------------------------- ////////////////////////////////////////////////////////////////////////////// [04/05/2009] Whats new

I just figured out how to launch my own kiosk without going through the AVIC one working on some stuff right now.

Just found out something. I take it back that the AVIC IGO can't run on Device Emulator. It does run however exit right away. But I can be certain that some of the Kiosk exe file can not be run with the Device Emulator, whereas it can be run on my PDA.

Here is a screenshot of Device Emulator running IGO8 (not the AVIC IGO). This tells you that IGO8 runs on most hardware architecture. However, Device emulator can not run AVIC IGO. Borris if you are right about IGO software running on your ARMv4 processor, it might not be that the software was compile with ARMv6 instructions. However it is definitely compiled differently than of IGO8.

Check the processor on the pda and get back with me. I know so far the pda that i have are all ARMv6 instruction set compatible. Most PDA nowadays are. If you talking about IGO Software alone (the one that is design for pda), it can be compile for any platform. The AVIC software itself is compile/uses the ARMv6 instructions. Remember software is backward compatible. ARMv6 and ARMv5 below all can run within our AVIC. IGO sottware can run on pda because it is compiled for compatibility with vast number of devices. If you are a cs major you would know. If the AVIC software is coded to utili

Guys I've already gone down this road. As of right now you can't run any of the AVIC software on windows device emulator. The reason is that Microsoft have not release a compiler (platform builder) that supports ARMv6 instruction set. Also the latest Microsoft Device Emulator does not support ARMv6 Instruction sets as well.. Thus you can not run the avic software on the emulator so dont waste your time trying. The processor for the AVIC F-series is ARM1136JF (ARMv6 instructions set supported). Im awaiting their SDK, once it is release I can create software for this unit, maybe even a

Does anyone have problem with the screen blanking out sometime while in the ipod mode? I keep getting gray blank screen sometimes, usually happens alot while in the Ipod screen. It would blank out to the grey screen for a second and then come back to normal.

Yeah this is very annoying it happens randomly, alot of time while I am driving. Make it seems rather hard for me to pull out the usb and plug it back in. So I have no music until there is a long redlight . The ipod connection failure message keeps staying on the screen as well.

If only Microsoft release a compiler that supports ARMv6 instructions set and a device emulator that support the CE on ARMv6. We can produce 3rd party software for the unit. Right now, its too painful to be developing anything for this unit. The reason is that i have to run up and down to my car to test. I also tested the avic softwares on HTC Tilt phone that support ARMv6 it seems to run fine.

It would be much faster if it doesn't even have to load the silence .wav. It takes some processing when loading a .wav file, even if a silence wav. If only pioneer allow us to disable the sound. It might even be possible for us ot hack this to not even load the .wav.

I notice it big time. The reason why is that I integrated the deck with my steering wheel control. Everytime I control the steering wheel with the sound there is a huge lag and delay. After I silence out the tone, it seems to run much quicker.

No our pioneer unit doesn't have the audio alert features for poi. Yes it have cams icon, just make sure you change the view options in Manage POI. If im correct, I believe its Settings-> Navi Settings->Visual->Manage POI

Extract it into your storage card root folder which means /Storage Card/ after extract your SD card should contain the folder "POI" and "usericon". Put your SD card into the Pioneer Unit .... go to manage poi you can change settings in there so that those poi can appear on map.

There http://www.avic411.com/forum/viewtopic.php?t=17592

Here we go USA/Canada RedLight and Speedcam POI. Just download the zip extract it to the root of the SD Card and you should be able to feed it into your AVIC. Enjoy. This is based on POI-Factory POI. Thanks to VBLUE42 for the attachment. USACANADA_CamerasPOI.zip

The phantomalert poi seems to be very repetitive, I see speed trap poi all over the freeway. It isn't very useful at all. You are better off getting a radar detector. I found some incorrect redlight camera poi in my town as well. VBLUE42 attachment POI is much more cleaner. I split mine for California only. If anyone want the California redlight and speedcamera klm, i'll attach it here.

I notice there is another limitation for POI. Inside the "Storage Card/POI" folder, it can not exceed 1.4 MB?

I havn't hook my vss wire up yet, for those of you guys that did hook up the VSS will the bypass still works? Such as changing stuff in the navi while driving.

Same here, im having the same problem. Its very annoying that I have to unplug the usb and then replug it back in.