Awesome work. I wish i knew how to develop a ROM. Until then my 4000nex awaits bluetooth working android auto or another custom rom!

lol a douchebag with 5 posts trolls me with a 2 year old meme.  Nice.

 

Welcome to AVIC411. You will fit in just fine

 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. 

 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. 

Almost all of what was contained is in the FAQ or development notes. It was better to compile them all here.

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. 

Having WARP disabled makes the unit boot about 30 seconds before you can listen to music. It is even worse startup times with the Original SD Card Pioneer ships with. If you are going to disable WARP and are opening your unit, you should replace the SD Card with the fastest SD Card you can find to help speed it up.

Quick question, I've got an AVH-P5200BT. Is there going to be a list of units susceptible to this? I'd love to see if I can flash my unit.

All NEX Units that run the Android firmware are compatible. So that means NEX 4000, 5000, 6000, 7000, 8000, 4100, 5100, 6100, 7100, and 8100. As well as their European counterparts.

Is it possible to re-create a "warp" compatible image once any firmware changes are made?  This would give people the best of both worlds (customizable and quicker boot times.)

Also, what version of android are the NEX units running?  I'm wondering if xposed framework could be made to work with it...  That should allow some quick changes (like bypassing the boot up "warning" screen) fairly easily.  

Some ideas of what to do...

* (As mentioned,) bypass the bootup warning screen

* some digging into whatever launcher code they are using -- or just replacing the launcher (else adding anything would be pointless)

* If the device/kernel can handle multiple BT connections at once, perhaps OBDII software (such as torque) on the HU would be nice.

* getting some form of adb working would be extremely helpful.  Otherwise, testing stuff will be a PITA.  (However, I doubt the USB ports on the HU will work in that mode.)

* if getting adb working isn't an option, perhaps a version of the firmware could be put together that would work on a tablet (nexus 7?) to use for testing/debugging.  

...  just some random thoughts.

Take care

Gary

Is it possible to re-create a "warp" compatible image once any firmware changes are made? This would give people the best of both worlds (customizable and quicker boot times.)

 

Also, what version of android are the NEX units running? I'm wondering if xposed framework could be made to work with it... That should allow some quick changes (like bypassing the boot up "warning" screen) fairly easily.

 

Some ideas of what to do...

 

* (As mentioned,) bypass the bootup warning screen

 

* some digging into whatever launcher code they are using -- or just replacing the launcher (else adding anything would be pointless)

 

* If the device/kernel can handle multiple BT connections at once, perhaps OBDII software (such as torque) on the HU would be nice.

 

* getting some form of adb working would be extremely helpful. Otherwise, testing stuff will be a PITA. (However, I doubt the USB ports on the HU will work in that mode.)

 

* if getting adb working isn't an option, perhaps a version of the firmware could be put together that would work on a tablet (nexus 7?) to use for testing/debugging.

 

... just some random thoughts.

 

Take care

Gary

The units use android 4.2.2, the units should be able to create a new snapshot, as it is a mode that exists in UBoot but is untested at the moment.

The devices have a USB OTG mode that we have looked into but we have not got it to function properly yet.

Having WARP disabled makes the unit boot about 30 seconds before you can listen to music. It is even worse startup times with the Original SD Card Pioneer ships with. If you are going to disable WARP and are opening your unit, you should replace the SD Card with the fastest SD Card you can find to help speed it up.

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. 

Course friend,even modded AVIC-F77DAB...

 

2015-08-11_8.jpg 2015-08-11_2.jpg

 

I think they use the same firmware? Would be nice to have no warning at the beginning and maybe mirrorlink for the Galaxy S5 if possible

I think they use the same firmware? Would be nice to have no warning at the beginning and maybe mirrorlink for the Galaxy S5 if possible

The  EU firmware is practically the same,with some minor differencies from the US/CA/ME/...

I don't use and like Android based smartphones (exept of some for test purposes only)..,but,can confirm,that Pioneer AppRadio & Pioneer NavGate HUD works perfect with my unite and my iPhone 6

Quite amazine works guys !!!!!

All NEX Units that run the Android firmware are compatible. So that means NEX 4000, 5000, 6000, 7000, 8000, 4100, 5100, 6100, 7100, and 8100. As well as their European counterparts.

SPH-DA120 is quite similar to 4000 so i guess it should applies to this list (difference is about GPS module http://avic411.com/index.php?/topic/38859-nex-runs-android-and-other-useless-info/?p=332325 )

The  EU firmware is practically the same,with some minor differencies from the US/CA/ME/...

I don't use and like Android based smartphones (exept of some for test purposes only)..,but,can confirm,that Pioneer AppRadio & Pioneer NaveGate HUD works perfect with my unite and my iPhone 6

Have you some more details... As US models do have 1.10 firmware but EU ones still rely on 1.07 .... Maybe a cross flash can be done

Have you some more details... As US models do have 1.10 firmware but EU ones still rely on 1.07 .... Maybe a cross flash can be done

Cross flash isn't possible yet between EU/US  x000/x100 to avoid a damage of the units,

only between  x000/x100 US/ or! F7x,96,97 BT etc. EU ..,

Cross flash isn't possible yet between EU/US  x000/x100 to avoid a damage of the units,

only between  x000/x100 US/ or! F7x,96,97 BT etc. EU ..,but the navigation can be ported even to the android based smartphone from 2.3.x 

My sph-da120 does not have navigation  ...

My sph-da120 does not have navigation  ...

Install ®Market Helper & enjoy any navigation program..

My sph-da120 does not have navigation  ...

Lucca says that he have working navigation from 2.3.x in every forum thread, even if this isn't thread or post subject as in your case. But he only says, no one seen this working navi with world licenses as he says.

No offense here, I mean SPH-DA120 is a bit different case, as it's basically a mirror touchscreen display/ + GPS antenna. So you only need to have your prefered nav program running on phone. I'm not sure, it's revelant to add another apk in such device. But removing warning screen, changing boot/splashcreen, create colored skin or even correct Pioneer typo would be really nice. And changing the base image (US->EU) with the newest one could help if specific US elements can be replaced...  

Lucca

 

So give it all, what the fuck are you waiting for?

Due to yours boorish behavior - no releases!

@Lucca

wenn you have it ,then give it to us , wenn not , don't waist our time

@Lucca

 

wenn you have it ,then give it to us , wenn not , don't waist our time

You'll have a lot of time together with vke/whatis..for hard work and longtime awaiting...

You'll have a lot of time together with vke/whatis..for hard work and longtime awaiting...

So you are single handily deciding to slow progress for the development community, when you may know something that can greatly speed up our progress. That is not what this post and topic is about. It is about cooperation and working together to create software for our radios, that the manufacturer has decided to neglect. 

So either help us and be constructive, or don't waste everyone's time.

So you are single handily deciding to slow progress for the development community, when you may know something that can greatly speed up our progress. That is not what this post and topic is about. It is about cooperation and working together to create software for our radios, that the manufacturer has decided to neglect. 

 

So either help us and be constructive, or don't waste everyone's time.

.

You'll have a lot of time together with vke/whatis..for hard work and longtime awaiting...

Тhese people take a time and make a lot of progress for us , you make nothing , only promises , and now you say to us,  that we became nothing , it's realy good turn ) it seems ,that you have nothing to give to us , only a game that you play hере ,  Ðндрей....

I've just brought 2 SD Cards to do some tests. Will give feedback soon.

This is great news.. So happy to see this is happening

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