e0x70i
-
Content Count
25 -
Joined
-
Last visited
About e0x70i
-
Rank
Member
-
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. Also in both x000 and x100 series the debug menu makes system changes by calling methods in framework/framework2.jar's DebugModeServiceProxy class. These methods are just wrappers for native JNI functions, however. Unfortunately, we can't just drop the x100 series av.apk in since it at the very least relies on the DebugModeServiceProxy functionality in framework/framework2.jar. We wil
-
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
-
Just checked on my unit, 8000nex 1.10, I don't have the ADB options. Let us know if adb works! Maybe it will be possible to to just swap out the 8000 av.apk with the 8100 av.apk.
-
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.
-
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
-
Have you found which apk or jar the jp.pioneer.ceam.widget.DebugModeServiceProxy.* package is in?
-
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.co
-
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
-
https://github.com/bassrock/AVIC-NEX#update-file-modification Advice is specific to update files so you probably don't need to edit . But if we want to create a custom rom and package it up for people to update, could modifying boot.img still be an issue?
-
I took a look at your script earlier, awesome stuff! Was going to mess with it later tonight to try and pull a 8100 image from the update file. The main question I had was related to this comment Is modifying boot still a hurdle? have you guys modified boot on the sdcard directly without issue?
-
Oh nice! Ok I'll take a look at those scripts
-
Ah, thanks! So it looks just like normal android /boot and /recovery partitions. Any gotchas with checksums on /boot when I modify the partition on the SD card directly? Or is that a problem only when updating from the PRG file? Either way, I'll avoid making changes to boot since it looks like no-one has found out a way to package modifications to boot.img in a PRG update file yet.
-
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 disablin
-
-
-
Thanks, Sorry just made a ton of edits to my first post! Just tried out kpartx with your flags, nifty. It didn't automatically mount the drives it set up for me, but I just had to mount manually and it worked fine: mount /dev/mapper/loop3p7 /mnt/avic7
