Jump to content
AVIC411.com

e0x70i

Members
  • Content Count

    25
  • Joined

  • Last visited

Everything posted by e0x70i

  1. 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
  2. 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
  3. 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.
  4. 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.
  5. 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
  6. Have you found which apk or jar the jp.pioneer.ceam.widget.DebugModeServiceProxy.* package is in?
  7. 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
  8. 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
  9. 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?
  10. 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?
  11. Oh nice! Ok I'll take a look at those scripts
  12. 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.
  13. 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
  14. e0x70i

    dio

  15. e0x70i

    Dio Nex demo image

    From the album: dio

    DIO is carplay
  16. 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
  17. kpartx -l AVIC.img gives me no output. fdisk -l AVIC.img gives me Device Boot Start End Blocks Id System /wordlists/AVIC.img1 1050624 1071103 10240 83 Linux /wordlists/AVIC.img2 1071104 1091583 10240 83 Linux /wordlists/AVIC.img3 1091584 3573759 1241088 5 Extended /wordlists/AVIC.img4 3573760 30197759 13312000 83 Linux /wordlists/AVIC.img5 1091585 1153023 30719+ 83 Linux /wordlists/AVIC.img6 1153025 1214463 30719+ 83 Linux /wordlists
  18. Thanks, I completed the NOR and SD card backups and posted details in the backup thread. Won't be able to flash the BSP and put in the new sd card until this weekend. In the meantime, I'll start looking at the image itself, play around with the PRG conversion script you guys wrote, and explore interesting APKs.
  19. NOR Backup and SD Card backup worked. NOR backup completed instantly to USB1. Backing up to /sdcard/ for the SDcard backup took about 30 minutes. Pressed the volume minus button a handful of times. After putting the SD Card back into my computer, however, windows gave the error "found errors on this drive. to prevent data loss, repair this drive now." After scanning the drive, it said no errors were found. Maybe I ejected it wrong from my machine initially, or the linux NTFS drivers on the next are causing weirdness. I copied the avic.img over . Despite the windows error message
  20. I hope I will But for real, give whatis a break. He did some great work and probably has valid reasons for removing his posts. Besides his posts aren't part of an open source project or under any license so he can do what he wants with them.
  21. Give it some time. There's going to be more lead time on testing out something that requires ripping a radio out of a car vs. just plugging in a phone. I am going to be testing this out this weekend. Also, anyone daily driving with warp disabled? Is it still fast enough to not be terribly annoying? EDIT: Is everyone doing this from firmware 1.10? I am on an older version currently.
  22. Amazing work guys. wow very hide, much scare
  23. Nice detective work! 12 Khz is pretty low, I'll try to remember to do the measurement tonight on mine and see if it is the same.
  24. Oh interesting, that one sounds a bit harder to fix than gluing a capacitor Yeah its very high pitched, you would have to be sensitive to the noise and relatively young. I am 24 and really have to listen closely and have my head in the right position to hear it. Would be interesting to see what the results are of that test! I have an iphone app that measures frequency, I'll try that too, but im doubting the iPhone mic can pick something up that high in the frequency range
  25. I had the exact same issue you are describing. Display whine, high pitched, and only when some sort of dimming is enabled. I went to the shop I got the unit from and checked out some of their other 8000nexs, they all had the exact same issue. I think every 8000 has this issue, just most people aren't sensitive enough to the noise to notice it. I don't notice it when the engine is on so I have just accepted it. Opening a support ticket with pioneer may get you a new one but it is probably going to have the same issue. This is a common issue on crappy screens with cheap components, it is p
×
×
  • Create New...