sofakng Posted April 24, 2015 Report Share Posted April 24, 2015 I've read through most of this topic, but can anybody give any reports about flashing the 8100 firmware to the 8000? How well is it working? Is there anything new in the 8100 firmware besides Android Auto? Quote Link to post Share on other sites
EditorDZ Posted April 24, 2015 Report Share Posted April 24, 2015 It's all working except for blank map screens and no BT audio (which includes all Android Auto audio). Lack of BT audio makes it pretty much a non-starter unfortunately. Quote Link to post Share on other sites
bass_rock Posted May 8, 2015 Report Share Posted May 8, 2015 Hi, I can't get the links on the front page to work. Anyone else having issues with that? Quote Link to post Share on other sites
soosb21 Posted May 8, 2015 Report Share Posted May 8, 2015 yeah I'm having trouble with the links also Quote Link to post Share on other sites
jdoutine Posted May 8, 2015 Report Share Posted May 8, 2015 Also having trouble with the links. just get redirected to filedropper.com If anyone is able to put the files for download again, that would be awesome. Just went through all the posts here and looking to try this out. I have the 4000nex but all file links appear to be broken Quote Link to post Share on other sites
bass_rock Posted May 9, 2015 Report Share Posted May 9, 2015 Ok gonna give this post a shot its an example how to recompile the .prg files! #24 Quote Link to post Share on other sites
bass_rock Posted May 9, 2015 Report Share Posted May 9, 2015 It works I can now browse the platform directory and make changes. Now the question is, am I crazy enough to try it on my deck. I am starting to do each prg file. You can see the progress here: https://www.dropbox.com/sh/hwswi29kyo7nq6o/AAB2Emua4zzeis-cpr-v8twOa?dl=0 Note that this is for the 8100NEX even though it says 5100 Quote Link to post Share on other sites
bass_rock Posted May 9, 2015 Report Share Posted May 9, 2015 Looks like only the Platform folder has a mountable filesystem Quote Link to post Share on other sites
DP3343 Posted May 10, 2015 Report Share Posted May 10, 2015 It works I can now browse the platform directory and make changes. Now the question is, am I crazy enough to try it on my deck. I am starting to do each prg file. You can see the progress here: https://www.dropbox.com/sh/hwswi29kyo7nq6o/AAB2Emua4zzeis-cpr-v8twOa?dl=0 Note that this is for the 8100NEX even though it says 5100 If you could figure out what in the firmware controls what version of the carplay interface is displayed, I'd care about that more than anything else. There is something that changes the interface for the 4000 to be the same as that of the appradio 4 and the 8000 Quote Link to post Share on other sites
bass_rock Posted May 11, 2015 Report Share Posted May 11, 2015 If you could figure out what in the firmware controls what version of the carplay interface is displayed, I'd care about that more than anything else. There is something that changes the interface for the 4000 to be the same as that of the appradio 4 and the 8000 I believe it is the airplay.conf file as it houses the Icon files. If you decompress the 4000 firmware I would bet that it houses some config. Quote Link to post Share on other sites
newtonfb Posted May 11, 2015 Report Share Posted May 11, 2015 I believe it is the airplay.conf file as it houses the Icon files. If you decompress the 4000 firmware I would bet that it houses some config. if you could figure out how to get bluetooth working i'd care more about that than anything else lol Quote Link to post Share on other sites
bass_rock Posted May 11, 2015 Report Share Posted May 11, 2015 if you could figure out how to get bluetooth working i'd care more about that than anything else lol Yea same. The first step is figuring out why the bluetooth behaves the way it does. Do we have confirmation it is the exact same bluetooth chip? Quote Link to post Share on other sites
EditorDZ Posted May 11, 2015 Report Share Posted May 11, 2015 Yea same. The first step is figuring out why the bluetooth behaves the way it does. Do we have confirmation it is the exact same bluetooth chip? I upgraded the bluetooth software with the file from the 8100's firmware, and it works fine. Empirical, but seems to be the same chip. Quote Link to post Share on other sites
newtonfb Posted May 12, 2015 Report Share Posted May 12, 2015 I would think its the same chip. What about if you move the android auto apk over to the old file and install on unit? Quote Link to post Share on other sites
bass_rock Posted May 13, 2015 Report Share Posted May 13, 2015 I would think its the same chip. What about if you move the android auto apk over to the old file and install on unit? 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. 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.