Found some interesting stuff digging through the 1.10 backup image from my 8000nex.

 

Looks like carplay is called "DIO" internally. Smoking gun are dio_demo.jpg files that are screenshots or ads for carplay. Additionally the functionality of the classes referencing DIO look like they are working with carplay.

 

 There are a handful of classes so far relating to DIO. The jp.pioneer.ceam.mode.modescreen.DIO.SCR_DIO_Base class, which is found in the mode.apk,  has most of the basic functionality in it. This includes the display of the caution screen. First thing I am going to try is disabling the caution screen by editing the smali for this class. 

There are more references to DIO in other classes, mostly classes that manage the state of the UI/audio services. 

 

There are also many references to AAM. The base class for AAM in mode.apk looks MUCH more complicated than the carplay classes. I think this is appradio, but am not sure. I will take a look at the 8100nex image and compare to see if AAM is possibly android auto.

 

Attached the carplay DIO image file below. 

 

AV.apk -> /res/drawable-mdpi/dio_nex_demo_image.jpg

 

Agreed that DIO = Carplay. 

There are Services in the bin folder that get started by the init scripts on system property changes.

If you are familiar with mkboot, you can dd the 1st partition on the big image to a smaller image, then run mkboot to open it up and change it.  The init scripts are there on the system property changes.

The apks then seem to change system properties when you change modes.  Some start a DIOService others do Xm and etc.

Oh nice! Ok I'll take a look at those scripts

All, new developer menu that was discovered: http://avic411.com/index.php?/topic/81482-avic-development-mod-developer-debug-menu/

Nice!!

also, noticed adb daemon in the sbin folder on the /boot partition.

Has anyone tried having this run in rc.local or something? Maybe combo of enabling USB OTG and running the daemon? 

/wordlists/nex/boot/ramdisk/sbin# ls
adbd  andsnap  snapshot  ueventd  watchdogd

Actually, what about changing the sys.usb.config to adb?

# adb only USB configuration
# This should only be used during device bringup
# and as a fallback if the USB manager fails to set a standard configuration
on property:sys.usb.config=adb
    write /sys/class/android_usb/android0/enable 0
    write /sys/class/android_usb/android0/idVendor 18d1
    write /sys/class/android_usb/android0/idProduct D002
    write /sys/class/android_usb/android0/functions ${sys.usb.config}
    write /sys/class/android_usb/android0/enable 1
    start adbd
    setprop sys.usb.state ${sys.usb.config}

Can we change this in default.prop?

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp

 

Actually, what about changing the sys.usb.config to adb?

 

init.usb.rc

# adb only USB configuration
# This should only be used during device bringup
# and as a fallback if the USB manager fails to set a standard configuration
on property:sys.usb.config=adb
    write /sys/class/android_usb/android0/enable 0
    write /sys/class/android_usb/android0/idVendor 18d1
    write /sys/class/android_usb/android0/idProduct D002
    write /sys/class/android_usb/android0/functions ${sys.usb.config}
    write /sys/class/android_usb/android0/enable 1
    start adbd
    setprop sys.usb.state ${sys.usb.config}

Can we change this in default.prop?

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp

I have not tried that method yet as I thought it just gets overwritten. 

Have you found which apk or jar the  jp.pioneer.ceam.widget.DebugModeServiceProxy.* package is in? 

I have not tried that method yet as I thought it just gets overwritten. 

Sorry, im a noob at this, not sure what the best way to change these android system properties are. I'll do some more research on this and how the init scripts work. 

I want to take a closer look at the debug proxy class as that may have some hints on how to enable adb just through the av debug menu, which is much more ideal

Hmmm this looks promising: http://android.stackexchange.com/questions/55674/how-can-i-enable-adbd-during-boot-on-cyanogenmod

We can disable adb auth requirements and make it so when mtp is enabled, adb also gets enabled. 

I don't have access to my internal sd card till this weekend when I can pull the thing out of my car so just throwing suggestions in the air for now. 

Found the DebugModeServiceProxy class . It is in framework/framwork2.jar, along with a lot of interesting pioneer classes.

The setting the usb device mode change method calls a native JNI function though, so have to do some more digging to find out exactly what that JNI is doing when setting usb to device mode

    private native int SetUsbPortMode(final int p0);

Also have been exploring the 8100 /system partition extracted from the PRG using the methods in AVIC.sh. 

It looks like the av.apk debug mode  indeed has a ton more stuff than that of the x000 series av.apk. Unfortunately, we can't just drop the x100 series av.apk in since it at the very least relies on new functionality in framework/framework2.jar. We will have to transplant both the app and framework folders into the x000 series. 

Has anyone already tried  replacing the x000 app and framwork folders with the x100 app and framework folders? 

Update 8/16/2015: Added how to unlock an SD Card to the FAQs.

Course friend,even modded AVIC-F77DAB...

 

 

 

Hi Lucca,

please can you reup the spoiler? What changes you've made?

Will it be possible to use the modded AVIC-F77DAB firmware also on a AVIC-F70DAB? On my oppinion there is only the HDMI-input the difference betwenn both models

Hi Lucca,

 

please can you reup the spoiler? What changes you've made?

 

Will it be possible to use the modded AVIC-F77DAB firmware also on a AVIC-F70DAB? On my oppinion there is only the HDMI-input the difference betwenn both models

Hi!,

Ye,you're right - only the HDMI-input is the difference between both models. I only replaced the stock iGO with the custom one.

Hi Lucca!,

please can you give a small howto how you have IGO modified / replaced? Unfortunately I can not get access to my F70DAB.

thanks in advance for your help

Have solved the problem with my F70DAB for booting in the technical testmode.

The problem with the European version of F70DAB seems to be the following:

- The device will boot only from SD card with FAT32 in the technical test mode.

- It is only storing the image files to USB1 possible.

Thus, you need an SD card in FAT32 with the script files and a USB stick in FAT32 or NTFS for data backup, all other ways were not successful.

I hope people can still find this now that it's pinned... it seems to have gotten quiet. Thank you all again for the hard work, I'm excited to see what's coming!

I hope people can still find this now that it's pinned... it seems to have gotten quiet. Thank you all again for the hard work, I'm excited to see what's coming!

Definitely still working on it. Just not enough progress to post anything substantial yet. 

Definitely still working on it. Just not enough progress to post anything substantial yet. 

Thank you for the update!

Also Excited For this. Wish I was able to help but do not have the know how. Thanks for the hard work Keep it up!

Hi guys, 

I am happy to see you have made progress on this. I have been keeping my eye on this since seeing the Failoverflow blog posts a year ago. I was going to purchase a unit and get this working, but I have been busy and couldn't justify the cost. Since you guys basically figured it out, I think I can help.

I was the first to root the Kenwood DNN990 Excelon unit and learned a lot of "tricks" about getting ADB going and the like. 

Sounds like the next step is just to get a WiFi dongle with drivers working and then enable ADB over TCP? 

Last time I looked at a Pioneer update file with a mate of mine it seemed to have a dual core CPU and I can't remember the RAM. Can anyone confirm? I remember it being a lot better than the Kenwood crap. 

If you guys still need help, I can get help you get:
-root

-Play Store

-Wifi ADB working

Some questions:
Has anyone figured out if the lower end non GPS advertised units do have GPS built in? 

Has anyone figured out if there are CPU/RAM differences across various NEX units?

Have we gotten custom recovery working?

I will spend some more time catching up and look into buying a unit.

Great work guys!  This is some awesome stuff.  I'm working on some things in my spare time to contribute. 

Hopefully theres still progress being made. I check this thread everyday wanting atleast Android Auto working on my 4000nex. Heres to keeping my fingers crossed

carplay new logo

Hopefully theres still progress being made. I check this thread everyday wanting atleast Android Auto working on my 4000nex. Heres to keeping my fingers crossed

You and me Both! 

This thread looks like it hasn't seen any action lately but if you scroll up a bit ASD255 has been making some progress and has even changed the carplay logo but my questions on his youtube page go unanswered. 

This thread looks like it hasn't seen any action lately but if you scroll up a bit ASD255 has been making some progress and has even changed the carplay logo but my questions on his youtube page go unanswered. 

Ya im thinking this project is dead unfortunately. I was really hoping too. I dont even care about a custom rom, I just wanted BT to work when I installed 4100 firmware on my 4000.