EditorDZ Posted May 13, 2015 Report Share Posted May 13, 2015 We would need the settings api as well. However I haven't figured out which one is the Android Auto APK. I'm actually starting to look into it more and more. If we can start and get the bluetooth working, then we could create an Open Source alternative based on the original system and start adding more features. It looks like the base system is based on Android 4.4 and the Pioneer OSS says how to get a base system running. If you succeed, you'll instantly go from bass_rock to INFINITY_MEGA_ROCKS Good luck, I'm glued to your progress! Quote Link to post Share on other sites
bass_rock Posted May 13, 2015 Report Share Posted May 13, 2015 If you succeed, you'll instantly go from bass_rock to INFINITY_MEGA_ROCKS Good luck, I'm glued to your progress! I'm working on it. As of right now I need to figure out how to turn the system img back into a .prg. My plan is to do that without modifications, verify it flashes then start with small string changes to the apks. But I'm planning on this being my next hobby project. So we shall see if I progress. Quote Link to post Share on other sites
bass_rock Posted May 13, 2015 Report Share Posted May 13, 2015 So I updated my 8000NEX to the 81000 NEX software just to verify what does and does not work. Some notes for this as well: Did the map update for the 8000NEX that is available beforehand with navitoolbox Did the 81000 bluetooth update beforehand The navigation does work after an initial long load time (5-10min), so not sure why some are seeing a white screen. I can confirm that the bluetooth audio, carplay audio and phone audio; do not play, while the controls and song title do show up. An interesting note, if you turn carplay off and plug the phone in, the regular Pioneer usb/ipod interface works and does play music through the car. Quote Link to post Share on other sites
newtonfb Posted May 13, 2015 Report Share Posted May 13, 2015 So I updated my 8000NEX to the 81000 NEX software just to verify what does and does not work. Some notes for this as well: Did the map update for the 8000NEX that is available beforehand with navitoolbox Did the 81000 bluetooth update beforehand The navigation does work after an initial long load time (5-10min), so not sure why some are seeing a white screen. I can confirm that the bluetooth audio, carplay audio and phone audio; do not play, while the controls and song title do show up. An interesting note, if you turn carplay off and plug the phone in, the regular Pioneer usb/ipod interface works and does play music through the car. I believe someone said carplay played music of the cable, but not sure. I don't use anything Apple. Yes you are correct, the bluetooth infomation still goes through but the audio doesnt. If you need someone to test anything or help in anyways let me know I got a 4000nex. Quote Link to post Share on other sites
bass_rock Posted May 14, 2015 Report Share Posted May 14, 2015 Also for those of you that were curious about the bluetooth setting, like I was to understand here is an image of the Bluetooth Audio Setting. Quote Link to post Share on other sites
bass_rock Posted May 14, 2015 Report Share Posted May 14, 2015 Hmm. Well I tried a variety of things in this order: Updating to 8100 by just renaming files (but first updated bluetooth firmware)All but bluetooth audio and carplay audio worked. Updated to 8100 straight upgrade (no modified files) after updating to the 8100 by aboveAll but bluetooth audio and carplay audio worked. Updated to 8100 with the old 8000 Bluetooth filesAll but bluetooth audio and carplay audio worked. Click the bluetooth firmware update (which had the 8000 bluetooth files)bluetooth firmware downgraded Carplay and usb iPod stopped working with a 02-60 error. Downgraded back to 1.08 (8000NEX)All working again. So I wonder if it really has to do with some type of security feature in the audio subsystem for bluetooth and carplay that causes it to behave this way. Quote Link to post Share on other sites
bass_rock Posted May 14, 2015 Report Share Posted May 14, 2015 In order to continue it looks like the 8100 update is delta and may not contain the need pieces. Is there anyone here that can image their sd card from their 4100,5100,6100,7100,8100? Quote Link to post Share on other sites
goke Posted May 14, 2015 Report Share Posted May 14, 2015 Great work guys Quote Link to post Share on other sites
therooster Posted May 14, 2015 Report Share Posted May 14, 2015 I reached the same conclusion that one would need the whole SD card dumped to continue testing. A simple card swap would confirm if this would work. A dump of the contents would be a bit harder because of the CMD 42 password lock. Quote Link to post Share on other sites
bass_rock Posted May 14, 2015 Report Share Posted May 14, 2015 Well looking at testmode and dumping the logs you can see the following: 1-02 00:00:11.010 2724 2876 E BinaryDictionaryGetter: Could not find a dictionary pack 01-02 00:00:11.700 2581 2626 E BluetoothManagerService: fail to bind to: android.bluetooth.IBluetooth 01-02 00:00:11.720 2581 2594 E BluetoothHeadset: Could not bind to Bluetooth Headset Service 01-02 00:00:11.720 2581 2594 E BluetoothA2dp: Could not bind to Bluetooth A2DP Service 01-02 00:02:28.177 2501 2501 E datalink: [frameworks/extend/Sources/iDataLinkServer/src/DataLinkManager.cpp:201][0x20b00006][read error for mUserSelectedSource from data manager (0). force to use default source : JAVA_MEDIA_SOURCE] 01-02 00:02:28.217 2462 2462 E blueforce: [frameworks/extend/bluetooth/src/forcesrv/interact/CSourceBTAudio.cpp:61][0x22400068][error] 01-02 00:02:28.287 2457 2457 E DataManager: [frameworks/extend/DataManager/sqlite/SqliteDataBaseManager.cpp:544][0x21a00109][1##2#1#B#FAL#MSCSDFILEPATH, data size is wrong:0.] 01-02 00:02:28.287 2457 3180 E DataManager: [frameworks/extend/DataManager/sqlite/SqliteDataBaseManager.cpp:544][0x21a00109][1##2#1#B#FAL#MSCSDREARFILEPATH, data size is wrong:0.] 01-02 00:02:28.287 2457 2457 E DataManager: [frameworks/extend/DataManager/sqlite/SqliteDataBaseManager.cpp:544][0x21a00109][1##2#1#B#FAL#MSCUSB1FILEPATH, data size is wrong:0.] 01-02 00:02:28.287 2457 3177 E DataManager: [frameworks/extend/DataManager/sqlite/SqliteDataBaseManager.cpp:544][0x21a00109][1##2#1#B#FAL#MSCUSB1REARFILEPATH, data size is wrong:0.] 01-02 00:02:28.287 2457 3177 E DataManager: [frameworks/extend/DataManager/sqlite/SqliteDataBaseManager.cpp:544][0x21a00109][1##2#1#B#FAL#MSCUSB2FILEPATH, data size is wrong:0.] 01-02 00:02:28.297 2494 2521 E AUXPlayer: [frameworks/extend/Sources/AUXServer/src/../jni/AUXPlayer.cpp:292][0x20400003][AUXPlayer::getDisplayFormat fail!] 01-02 00:02:28.317 2496 2547 E dio-service: [frameworks/extend/Sources/DIOServer/src/AirPlayAVClient.cpp:497][0x22500005][AirPlayAVClient::setSubVolume() the MIX DAC have not started] 01-02 00:02:28.777 2493 3292 E SMP : setting getVideoOutputFormat error occurs. 01-02 00:02:28.827 2461 2509 E mediamanager-exe: SwitchManager::onSourceStatusChanged, getSourceID fail! name=extnavi 01-02 00:02:28.867 2462 2462 E blueforce: [frameworks/extend/bluetooth/src/forcesrv/interface/CBlueforceService.cpp:3017][0x22400069][error] 01-02 00:02:28.867 2493 2561 E blueforce: [frameworks/extend/bluetooth/src/forcelib/BpBlueforce.cpp:1757][0x22400069][error] 01-02 00:02:28.867 2493 2561 E blueforce: [frameworks/extend/bluetooth/src/forcelib/CBlueforceManage.cpp:2121][0x22400069][error] 01-02 00:02:28.867 2493 2561 E IOSMgr : call IAP Error = -105 01-02 00:02:28.877 2462 2513 E blueforce: [frameworks/extend/bluetooth/src/forcesrv/interface/CBlueforceService.cpp:3017][0x22400069][error] 01-02 00:02:28.877 2493 2561 E blueforce: [frameworks/extend/bluetooth/src/forcelib/BpBlueforce.cpp:1757][0x22400069][error] 01-02 00:02:28.877 2493 2561 E blueforce: [frameworks/extend/bluetooth/src/forcelib/CBlueforceManage.cpp:2121][0x22400069][error] I'm not an android rom expert but it looks like there is an issue with the Bluetooth A2DP Service. If any android experts know any ideas for how to debug that without adb and just the firmware update files, that would be a big help. Quote Link to post Share on other sites
goke Posted May 15, 2015 Report Share Posted May 15, 2015 Will make a donation.....not sure if he's still taking donation 1)I am currently on 1.06/NEX4000 will I need to be on 1.08/NEX4000 to install 1.03/NEX4001? 2)If I install 1.03/NEX4001....are you saying bluetooth audio from my phone would not work? Is there anything else that would not work? 3)would there be a method to violate the album art pixel size limit from 600 pixels? Quote Link to post Share on other sites
ThaBlackMamba Posted May 23, 2015 Report Share Posted May 23, 2015 Just donated, this is REALLY exiting news. Thought I was going to have to get a whole new headunit to be able to take advantage of Android Auto. Keep up the good work Quote Link to post Share on other sites
newtonfb Posted May 23, 2015 Report Share Posted May 23, 2015 Pretty sure the project is dead... Quote Link to post Share on other sites
bass_rock Posted May 24, 2015 Report Share Posted May 24, 2015 Its not dead necessarily. We are just in need of a full sd dump Quote Link to post Share on other sites
bass_rock Posted May 24, 2015 Report Share Posted May 24, 2015 Ok update time. So I just gathered the logs from the 8000 vs 8100 when playing bluetooth and then using CarPlay. They both have the bluetooth errors as seen above. The main difference I can see is that the 8100 has long lists of this error: 01-02 00:02:13.400 2459 2459 E SettingServer: BnSettingServer::onTransact failed when settingserver is resume. cmd 468 Looking into what this really is but hoping this one is the issue. Also tried reinitializing the bluetooth and user cache after the upgrade to the 8100, but after I got the logs. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.