I have started reverse engineering the HCTCanBus app.
The reason was that I wanted to display the outdoor temperature in my custom launcher.
But one thing in advance that was only possible because I built my own cunBus box. The radio can only process data it receives and the original canbus boxes only have a very limited number of canBus messages integrated.
The data from the box is transferred to the Android system via the serial port "/dev/ttyV0".
What I found out was that the steering wheel buttons are not transmitted to this serial port.
But all other data with the correct format is transferred there and processed by the HCTCanBus app.
So we can use it to implement our own messages.
I also managed to send data back to the box.
The serial port is not used for this...
The original app processes data on the door contacts, air conditioning, parking sensors and TPMS.
These are at least the things I've found out so far.
In the original app is the handling of the data for the different settings in the factory settings for the canBus.
For each manufacturer there is a file that decides what the message means and how it is to be processed.
I own a Chrysler 300C and use the setting "30 CHRYSLER(Bagoo)".
I have only worked on this. Because I have no access to the data of the other manufacturers.
To read this data from the code is almost impossible with decompiled code, at least for me...
So far I only integrated the door contacts as activity.
For the other displays my car simply does not provide any data (air conditioning) or I have not yet been able to identify the correct can messages (TPMS, radar sensors)
What I have integrated, because of which I have built my own box, is a settings window where I can for example set the events when the radio is switched on or off.
I have uploaded the current state of my work to github.
Even if I am still in the middle of my work it might be interesting for some people.
I would be happy if others would join in and we could integrate the canBus message for the other manufacturers.
github.com/zebbel/MTCD-E_CanBus
Sorry but it's annoying to post stuff here when you can't even insert links...
Hey, zebbel.
You're up to a pretty good start, keep up the good work!
I've also started research in that direction, decompiled HCTCanBus.apk with apktools and started looking at smali code.
(It's pretty readable to my surprise)
But soon I came to the conclusion that there is not much we can do from only the android side.
Canbox itself translates commands it gets from UART into CAN messages using custom firmware on the box. And that is the problem - we don't have access to it.
So, to extend the functionality of "HU-CanBox-Car" system we would need to re-engineer not only CanBox hardware (I've seen some reverse-engineered schematics laying around the forum somewhere) but also it's firmware. A hell of a lot of work, if you ask me...
PS: I personally own Citroen DS5 with HU from Peugeot 508, PX6 platform 4G/64G and PA-SS canbox module. The good thing that almost everything working oob. The sad thing is my pretty "analog" dash clock are not working - That's why I start digging into this, just to find that Canbox App ignores the Time changes completely (e/g not sending to CanBox any information on Clock updates)
Hi All,
I have been doing work on this already, see my post's here, we already have the canbus apk sources.
https://forum.xda-developers.com/showpost.php?p=81859661
darkspr1te
Hi, totally new on this just a questions with a new head unit 8227L and steering control. My car is a jeep compass 2008, the android unit os 9.1 XY Auto 3.3 seems to have some factory set options with can bus for many models but not for the jeep compass, I already identify the cables can high and low and imagine they need to be connected to key 1 and key 2 on the head unit but at the moment no luck with the right can bus selection, any ideas?
Hector114 said:
Hi, totally new on this just a questions with a new head unit 8227L and steering control. My car is a jeep compass 2008, the android unit os 9.1 XY Auto 3.3 seems to have some factory set options with can bus for many models but not for the jeep compass, I already identify the cables can high and low and imagine they need to be connected to key 1 and key 2 on the head unit but at the moment no luck with the right can bus selection, any ideas?
Click to expand...
Click to collapse
Is it an MTCD and is the question related to canbus reverse engineering or solving a problem with your headunit.
No, 8227L units are not MTCD/E.
Related
Some of you must own a Chrysler/Dodge/Jeep vehicle with a Uconnect stereo in it, right?
I've been all over the google search, the Dodge Forums, calling Chrysler's Uconnect dept, etc. and no one seems to have any clue what their talking about. I know that XDA is knowledgeable about all things phone. Searching doesn't get my exact questions, here's an unanswered one for the HTC EvoLTE (http://forum.xda-developers.com/showthread.php?t=1667801). The Ford SYNC systems have a similar problem.
I have a 2012 Dodge Durango with a Uconnect 430 RBZ stereo. It announces that my phone (the Sprint SGS3 with 4.1.1 LJ7 stock non-rooted (for now)) is not compatible with the Bluetooth Messaging Access Protocol profile or MAP-profile necessary to announce and control the SMS messages on my phone. There's a service on our phones that runs constantly when the bluetooth is enabled called MAPSamsungService, which after googling/reading/searching, leads me to believe this is the messaging protocol that the Uconnect desires.
My questions are:
1) Why won't this radio identify the MAP process of the SGS3 and connect to it Are there ROMs that do support this? (CM10 reportedly does support this http://forum.xda-developers.com/showthread.php?t=1916902 - but I don't like the CM10 camera....so...yeah)
2) Has anyone had success in getting the SMS messages functionality on their Uconnect
3) Has anyone had luck with getting your contacts to properly sync? All mine are Google Contacts, and it is VERY random which ones show up. (I have just less than 1000 contacts, which is apparently the upper limit for these radios)
[just in case this shows up in google searches, I have learned that USB drives connected to the Uconnect need to be in FAT32 format and you can only move 2048 songs over at a time to the HDD, so load up multiple flash drives for the transfer. must be constant bit rate not VBR, 1000 folders is limit and 20k songs]
as a former u-connect owner and current audi interface owner, let me offer the following:
When sold, the technology in any car is about 2-5 years old. meaning it was designed to interface with phones 2-5 years ago. so if you have an old phone, it will probably work great!!
Chysler never offered a flash or upgrade to the original uconnect system, but that was supposed to change with the RBZ. My brothers at the LX forum have reported that is not really true. There are some systems that allow you to get around this with aftermarket HU but not what you are looking for.
No way to know what ROM's will work or not because of your specific situation. There is a mammoth black hole where all BT protocols go...no one seems interested in making it generic.
We currently own 2 vehicles under the VW/Audi brand and a Ford with a Pioneer HU in it. My EVO LTE phone book will update in the VW, but not the Audi. Same system, right? In the Audi, it will frequently not sync. one vehicle has different software and Audi cannot flash it. no worries on the Pioneer HU though.
TLDR -> Car companies suck, wha, wha, wha
-----
Thanks for the reply and your experiences. Speaking separately for all the tech they put into every aspect of the car...... I would figure that in 2012, these car companies and their stereos would learn their lesson and start to evolve. I guess we need a Uconnect forum on XDA to really get things heated up! If anyone knows of a site for ROMs and such for these systems, please let me know, I'm willing to take the plunge.
I had an aftermarket Kenwood in my 2000 Jeep Grand Cherokee that I traded in. It synced with my phone perfectly, downloaded all my contacts, but didn't have the ability to read SMS messages (it also had a tiny display). Bluetooth worked well, etc. it just became a real piece of **** car that needed to be replaced.
The latest CM10 logs indicate that MAP functionality was fixed on 11/23: http://mobile.cm10log.appspot.com/?device=d2spr
I really wish that the CM10 camera and data connectivity didn't have so many issues, otherwise this would be a non-point and I'd be happy as can be with full functionality. What I find troubling is how many opinions there are about these different car systems and their compatibility. I understand your point about Bluetooth standards being quite a jumble. You should be required to support them all if you are going to use it in your device. I'm going to back to dual booting CM10 to see if I can get the MAP to work with the Uconnect system.
Then there's the confusion of all these systems. I have read links where a Stock Sprint SGS3 running 4.1.1 worked perfectly with MAP in a toyota prius. You ask Samsung and they say that MAP is not supported by the SGS3, their fact sheets would indicate the protocol is missing. But it was supposedly included in Android 4.1.1, but no one can confirm that.
It's just very disappointing when a company touts a technologically advanced car that can do things like read your SMS messages, display album artwork for songs, play songs from USB sticks, has ipod connectivity, etc. Can't seem to A) do any of those things well and B) offer absolutely ZERO tutorials and guidelines for making the above features actually work. You have to sift through forums to find out that a USB drive needs to be FAT32 formatted!
I just added 26.5GB worth of music to my HDD in my Uconnect 430 RBZ. I ensured that the album artwork was correctly linked with the ID3 tags in all of my music, a painstaking venture to say the least that I was meaning to do for a long time, however NO artwork actually shows up. It did finally all sync over and there are some things that it does "well" but far more that just miss the mark for no other reason than laziness and profitability. Just saying you can do these things is more profitable than actually making them work consistently - OR having knowledgeable people that can help you when you call in.
Overall, I guess I should be happy that it does what it does in the least. I understand the product cycles for cars and the tech is most likely 2-5 years old. Like everything else in this world, hopefully they'll improve their cycle time for updates. Then again, out of sight, out of mind. They have your money, who cares if they add any new functionality. Most cars aren't impulse buys like phones tend to be.
You can use any camera it does not have to be the cm camera. You can flash the stock or the 4.2 or even the note2 camera.apk. Also you xan flash your uconnect with a new firmware
Sent from my SGH-T999 using xda premium
Hello,
I've got an Eonon MTCB unit (with Malaysk 4.4.4) on a Opel/Vauxhall Astra H (MK5).
The way the car is designed means that I get to keep my old LCD display in the dash, positioned above the MTCB unit.
The original car music player displayed current song title or radio station name on that display.
The MTCB unit displays much less useful info like "MUSIC MM:SS", "RADIO", "AVIN" or "OTHER", depending on current input source, but never
something specific like song name or radio station name.
I would like to reverse engineer how the unit sends out these messages so that I can send my own, more meaningful ones.
The unit came with a CAN bus decoder, so I bet that's how messages go out. However, regarding the software side I have no clue.
Does anyone have an idea how I can go about this?
Someone tried to change that thing. There other threads to. But no solution at the moment because it takes a very long time (I believe to read that) :/
One of my cars is a 2008 Ford Crown Victoria Police Interceptor. Since it's a retired cop car, it doesn't have any anti-theft system, no chip keys/immobilizer, and there are various keys out there that can easily open/start my car. My friend found a random key in his Crown Vic ex-cop-car from a completely different department and even though the key is cut totally different it still opens and starts my car. I'm sure there are plenty of other keys out there that will work with my car as well, which is why I'm worried about it getting stolen.
I have a spare cheap phone (with like no resale value) on Xfinity Mobile, there are no line fees, so if I can stay under 100MB of data in a month it's free, or it'll cost me $12 for 1GB which is no problem.
Features I'm looking for are:
-Tracking ability
-Text me when the car is started.
-Text me when there is an impact with the car (using the accelerometer in the phone I guess?)
The tracking device is easy... just use Android Device Manager or Lookout or some other remote tracking app. The problem is the other two things... Not sure how I'd accomplish that honestly. I'm a web developer but I have no idea how to even start with Android app development...
Looking for input, hopefully someone on here could point me in the right direction. I've tried Googling/Binging but nothing I've found is even remotely similar to what I'm trying to do. Thanks in advance!
I was looking for the same thing. But all I found was OBD2 devices or some Chinese that used SMS for communication.
But after long time of searching I found ,,carlock,, it is OBD2 but it is using it only for power so you can use only OBD2 dummy for powering it. It has nice APP, using internet and it's not that expensive.
But if you found different solution let me know.
not a dev, but just wanted to comment on what Mato_xXx said about the chinese app that uses SMS.. if someone were to make an app, in some places (not sure if this is the case in China) data is more than SMS and vice versa.. and i know that those chinese made GPS car tracker devices work like this:
-uses GPS to record location
-checks every so often for location changes
-if location changes SMS gets sent to a number you pre-programmed into it every several seconds
these devices come with apps you can download to track the location of vehicle using google maps. Here is an example of said device:
(i am a new user and was unable to post links, but serach for "gps vehicle tracker" in google or serach amazon)
these things meet the criteria of your first requirement without the use of data (it instead uses SMS). If someone were to make a car security app, they should add this as a feature (location via SMS) because depending on what provider you are using you might run out of data or you could go over you data limit and amass a large bill... this would be an issue for people in Canada as we have some of the most expensive cell data in the world
I think what needs to be done is an app that can be installed where you can make it so the car wont start without some kind of authentication entered via your android device + the key..
what I think you were talking about when you said your friend found a key that would start your crown vic is the crown vic fleet key, which will start any crown vic (and usually the glove box and the trunk) ; (again, i am a new user,cannot post links, but serach google for "crown vic fleet key")
and because your vehicle is an old crown vic, its not going to have any wireless daig features so im assuming you'd have to buy some kind of hookup adapter for OBD2 to interface with your car.. but if you make any progress with this project please let us know..
this may be completely useless, but i stumbled upon this while looking for something completely unrelated: (gawd damn new user spam rules again! lol) www[dot]diagram[dot]com[dot]ua/english/articles/security-and-alarm-system-using-mobile-communication[dot]shtml
(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!
There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!
deja100 said:
(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!
Click to expand...
Click to collapse
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.
Bob_Sanders said:
There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!
Click to expand...
Click to collapse
Yeh I found that threat in my searches, but no one in there quite mentioned this specific scenario (Selecting one of the other options in the Bluetooth settings) so I wasn't sure. And I'm definitely not opening up the unit and cutting on the hardware; hacking config files I can do all day long, but I have no skills when it comes to soldering so I'd probably just destroy the radio in the process of trying to cut that module :laugh:
Yeh I've run the OBDLink EX with Torque as well for data logging temps on track and it worked flawlessly for that as well. BT is definitely more convenient, especially since most are running apps from their phones, but if you have a dedicated radio like these then it's a no-brainer to permanently wire up a USB device.
marchnz said:
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.
Click to expand...
Click to collapse
When you say "hacked BT implementation" I'm assuming you mean they don't use the standard Bluetooth stack built into the Android OS? That would make sense, as when I try to do anything with bluetooth from the standard Bluetooth settings menu, it doesn't do anything, doesn't see any devices available for pairing, or anything else. You can only see other devices and pair to them from the PUMPKIN Bluetooth app; the funny thing is it will go through the first steps and show the XGPS160 as being paired, but none of the apps that use the GPS actually see it as a paired device (my OBD dongle shows up, but not the GPS).
I don't understand why they didn't just use standard bluetooth that's already part of the OS, rather than use some hacky custom solution
Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/
deja100 said:
Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/
Click to expand...
Click to collapse
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.
marchnz said:
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.
Click to expand...
Click to collapse
Yeh, that's extremely disappointing Does anyone know of any Android based radio units that have full working bluetooth? I don't mind buying a new unit for the car if I know it will work with everything.
The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk
ikerg said:
The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk
Click to expand...
Click to collapse
Bummer they don't make those units anymore :/ Then again, they may not have been powerful enough to run my track timer apps anyway.
Greetings XDA Forum,
I am writing from Australia. A few days ago, I purchased a 2nd Hand Car.....a VW Multivan. This car has the Hal9K v3.1 Head Unit. (px5 Android Version 8)
The seller showed me some of the features with this Head Unit, when I did the test drive........Before buying the car, the seller said that he will remove his information from the Head Unit.....Upon collecting the car, he informed me that he Reset the Head Unit.....Now all of the wonderful features that he had shown me are gone.....He did not give me a user's manual, (he doesn't have it)......I have been able to discover some videos on Youtube.....but nothing that really shows me how to set up the Head Unit, and customize it to match my car, and my desires.
For example:
In the Head Unit Set-up, will like to Select the VW and Mulitvan setting, so that when I reverse, it displays a Multivan......I can easily locate the VW symbol, but can't find a Multivan/Transporter option, in the selection of cars in the list....at the moment, the visual shows a normal car. On the Test Drive, the reserve image displayed a Multivan, and the seller made a strong "Selling Point" of the positivity and customizing ability of this Head Unit. I will like to Customize the Head Unit to my specifications.
The Audio-input (3mm socket) doesn't respond, and there is no audio-in App, but there is an AVIN app (Audio-Visual-input).....so I cannot use my iPod (yes, an iPod...I am Old School).
I will like to set-up Apple Car Play, so that I can:
use the TomTom navigator app from the iPhone, onto the Head Unit.
make calls from the iphone contact list.
...........but I can't seem to understand how to create the connection between the Android Head Unit, to the iPhone.....Perhaps I need an app that will let the two Operating Systems work together. (iPhone connecting to Android Head Unit)
Prior to discovering this forum, I have been using the head unit. I am connecting the iPhone to the Head Unit, using "Bluetooth" & an internet "Hotspot"...I can receive & make calls, I have my iPhone attached to the windscreen, and I can select a contact from the iPhone, which then appears on the Head Unit as a number, not as the Contact name. I am using my gmail account through the Head Unit for Navigation purposes, which works great......But I wish to Customize it, to operate the TomTom navigator which is already on the iPhone.
I hope that you guys & gals can help.
All advice, suggestions and ideas, are truly appreciated.
Thank you.
Stephen
You need to look at this section of xda. Find your correct model from the "about" section of of settings, find the operating system installed for that model and follow all the guides.
This section will have all the answers you need
Head Units
forum.xda-developers.com
jbgooner said:
You need to look at this section of xda. Find your correct model from the "about" section of of settings, find the operating system installed for that model and follow all the guides.
This section will have all the answers you need
Head Units
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your reply jbgooner......I clicked on the link that you shared, and I couldn't locate the MCU that matches the system in my car. The MCU in my car is: MTCE_HA_V3.30_1
I then completed a search for MTCE_HA_V3.30_1 and received no matches.
I am a complete beginner with these Android Head Units.....it seems that a person does require some computer skills (perhaps in computer programming??) to set up and customise these Head Units for the Make & Model of the Car......I am slowly researching what I can and realise that I have entered an entire new world of technology, that I didn't know existed. It will be pretty cool to understand this technology and use it accordingly.