Database Info

Nameless Headunit Reviews / Experiences

I'm looking for an Android headunit and was wondering what everyone's opinion was on the various no name manufacturers? So far I've tested a few Cusptech units, but noticed several flaws. I'm sure if I had access to the MCU source code or schematics, I could fix the issues myself. Ultimately it'd be nice to be able to use a custom ROM on it.
In any case, here's my take on the CP-F011 from Cusptech. Please add to this thread with your experience for other units. Hopefully this can provide some guidance for anyone looking to purchase an Android headunit.
OS / General
The units I purchased all came with Android 4.4.2 installed. After a few days of use, I haven't noticed any serious issues with the user interface aside from it being seemingly cluttered. One nice feature it has is integrated WiFi. The antenna is internal, so the range is pretty limited though.
Power On / Off - One frustrating thing for me is that the unit always has to boot up when the accessory line is turned on, despite the constant hot line always having power. It'd be much nicer if the unit would go into lower power mode rather than completely shutting down. Interestingly, the tuner and sound come on almost immediately while the OS is booting.
AM/FM Radio - With a plain old AM/FM antenna, this tuner is essentially worthless. On my stock Ford nav unit, I get excellent reception across the FM band. The Cusptech unit however picks up nothing but static with maybe a slight hint of a radio station here and there. I'll try again with an amplified antenna to see if it makes a difference.
Bluetooth - In the Android settings menu, there's an option to turn on Bluetooth. When selected, it tries to turn something on, then shows an error message indicating failure, and shuts off again. Despite the UI showing Bluetooth off, the unit broadcasts as "Apple" and allows a phone connection with my HTC One.
GPS Receiver / Navigation Apps - I hope to test this in the coming days. By default the unit is configured for Waze, which I've never used. After playing around with a bit, I'll see about using Google Maps.
Rear-view Camera - No complaints here. When voltage is applied to the reverse line, the display flips to the rear camera instantly. No picture-in-picture functionality, but that also means the rear-view camera works while it's booting.
Sound Quality - I haven't had a chance to connect this unit with the appropriate speakers, so I can't comment on this yet. Will update when normal speakers arrive.
On a side note, if anyone knows of a unit that someone has been able to write custom MCU code for, please let me know. I'd be more than happy to contribute my software/hardware development expertise in making it better. At this point, if the enclosures weren't such a PIA to build, I'd design my own.

MTCD SoFia "LM" Head Unit Pre-Amp Output Levels?

New to these Android units.
Does anybody here know of a way to increase the output levels from the RCA Pre-Amp Outs?
I am wondering if settings for this are in the MCU software, or in the Android side of the software. My Radio sounds great with this unit, but the Music Player app seems to have around 30, or so percent less audio volume. I have searched, but so far found very little about this issue. Any help will be much appreciated.

I ran into the same problem, so I've used a NVX LOC with independent gain controls for all 4 channels.

Thanks for your reply
Thanks, but I want to keep the factory Bose amp, because I have read in several places that the speakers in the car have a non-standard impedance that the amp is matched to. Besides that I want to keep all the wiring in the car stock so I can put everything back to stock later if wanted. There must be some way to increase the output in the units software somewhere, so I am hoping that a software guru will chime in here at some point and tell me something like: "oh, yeah, just change the values in the such and such file located in the sub folder of the System folder. I'm patient, so time will tell.

Doesn't these factory sound systems use proprietary connectors with high level inputs? I've never seen a factory amp with RCA inputs.

Proprietary Factory Audio Systems
Yes, in my case with the Infiniti Q45 it is is a proprietary system, but I used a Metra aftermarket connection adapter (Metra 70-7551) to tap the original wiring plugs that normally go into the back of the factory Bose head unit. The Metra adapter allowed me to make the connections without having to cut up the factory plugs. It included the 4 RCA plugs to tie into the original feed wiring going back to the amp in the trunk. Helped me keep everything nice and neat, and eliminated the need to run speaker wires, or make splices into the amp inputs. I also used a Metra 40-NI11 antenna adapter to convert the Nissan proprietary antenna lead to a standard antenna fitting to go into the new Android radio. I don't sell Metra stuff, but only mention it here because it helped me do a nice clean install of the new radio, and it gives me the option of going back to stock very easily.

TECHADDICT5610 said:
New to these Android units.
Does anybody here know of a way to increase the output levels from the RCA Pre-Amp Outs?
I am wondering if settings for this are in the MCU software, or in the Android side of the software. My Radio sounds great with this unit, but the Music Player app seems to have around 30, or so percent less audio volume. I have searched, but so far found very little about this issue. Any help will be much appreciated.
Click to expand...
Click to collapse
isn't that the "input gain" settings, usually reachable via factory settings?

No external canbus decoder box on newer PX5 HUs?

Hi MTCD community.
Thanks to the time between the years (that's how we call December 27th to 31st in Germany), I had time to upgrade my HU. Up to now I had a RK3188 quad-A9 one (Erisin ES2508B, KGL) that had a proprietary power connector and a external canbus decoder box. (more information here: http://vi.vipr.ebaydesc.com/ws/eBay...descgauge=1&cspheader=1&oneClk=1&secureDesc=0 )
That external canbus decoder of the unit has a few dedicated output pins for illumination, reverse gear and a UART (?) style digital RX/TX connection to send wheel-button key commands. It's a perfect example for a Chinese product. This solution it easy and works - almost:
On Mercedes cars the wheel-buttons are used to steer the so called Kombi (KI). KI and HU are connected via canbus. Key commands are send in one specific can-message. The canbus decoder box is said being made specifically for Mercedes cars. While it correctly decodes button presses it fails to decode the current KI menu. As a result the HU will always interpret the "prev./next" buttons, even when you're not in the KI's Audio menu. As a result you either stop using your KI (bad option) or you disable some keys in the HU (that's what I did). The decoder box is also only reading the canbus and thus not able to send audio titles or the current radio frequency/station name to the KI.
Because of the decoder box sitting between HU and KI I never tried to enhance functionality because that would have ment either connecting another R/W canbus dongle to the HU or replacing the chinese decoder box and reverse engineering the RX/TX communication between decoder box and HU.
---
The newer PX5 unit that I now own (Erisin ES7689C, KGL?/LM?, http://www.ebay.co.uk/itm/Android-8...s-W203-W209-/123151147422?hash=item1cac61619e ) has a Quadlock connector (that's the correct name for the multi pin connector that became popular on HUs beginning in the early 2000th) and no external canbus decoder box (it is indeed perfectly plug'n'play). It is also able to identify itself to the KI as Radio which means it is also writing to the canbus. Compared to an original OEM HU, information is still extremely limited and it again fails to interpret only wheel-button commands send from the KI's Audio menu. - But, it is able to write to the canbus, so potentially this is a much better starting point for enhancements.
Now the key question: Does anyone know how the HU is communicating with the canbus? Is the decoder box just inside the HU's housing (and again being an extra translation module) or is it a proper canbus device controlled by an app or service from inside the HUs android?

Good piece of info mate. Thanks a lot
Unfortunately i am not able to answer the question due to limited knowledge.
I own a Mercedes w164 and have the same issues and i am keen to find a solution. Open a thread for that too here > https://forum.xda-developers.com/an...t/adapter-help-mercedes-t3903165#post79005544
My MTCD idetails are :
Unit: MTCD PX5
MCU: MTCE_GS_V3.00_3
ROM: Halk9 Mod 3.1 (Android 8)
Can Adapter : GS 10280514 / HW:V2 SW:V3
Can adapter Setting: 23 Benz_B200(simple)
On another thread more HW related you can find pleanty of info >
https://forum.xda-developers.com/an...elopment/mercedes-benz-class-comfort-t3680320
Also this guy did some work on canbus : http://honeysw.com/canproject.php
and here another piece of info : https://forum.xda-developers.com/an...-units-qa/how-bus-messages-make-unit-t3352343

Hi I also have a MB lol, a w203.
I have been through several head units of types makes etc, so know exactly what you mean. Although I never heard of 'ki' before.
My latest unit I have is def very good (best was a pioneer with separate car-pi can decoder) and that is also an erisin.
Great minds an all that eh!
The unit I have is a 4/32gb android 8. MTCE. It was working very well until I developed a problem with my reverse camera signal not getting picked up. Was switching OK but no image??
Anyway I bit the bullet and installed the custom rom by Malaysk which helps the camera but no steering control (for me) on 3rd party apps.
There is some talk about mtce files etc but I couldnt get anything to work until I installed a brilliant prog called mtcdtools (free from github).
Very techy to understand / use but with the info and help from others managed to replicate enough to get the two up/down left buttons working perfectly on all apps. It starts up by itself and stays in background. I'm very pleased with result and sure it could do much more if i only knew how. Def give it a go.
Also the up/downs only while in the audio sub menu and they operate whichever music app is running even while in the background if that makes sense. The right volume buttons always worked anyway, and with the phone.
I think the real challenge now will be getting info in the dash display to correspond with what ever app is on top. Currently mine just says audio off when using dab, but displays station number in radio and time elapsed from music player., but nothing from nav.

For W211/203 owners with Headunits - I've ported MBUX with full CAN data to android!

This has been a little lockdown project for myself.
DISCLAIMER: I am not responsible for ANY distractions caused by the shiny new interface, or any bricking of peoples tablets caused by flashing a custom ROM!
For those who don't know, MBUX is the new UI design language that Mercedes uses in the W205 models and up.
I decided to have a go at porting the interface to my MTCE tablet, using assets pulled from reverse engineered cluster firmware for the W213 E class.
Currently, this application works as a new home launcher, being the exclusive application running on the device. There is no way to browse other applications currently (I need to integrate that into the interface), however, it decodes data from CANBUS, and displays a TON of information!
Limitations currently (Early developement)
1. Volume controls and brightness doesn't work. We are bypassing the stock headunit canbus decoder box! (Reasons below)
2. The app will crash on first launch due to USB permissions
Current data shown on interface
1. Fuel data (Consumption per second, Average + Current MPG)
2. Transmission status for 722.x transmissions - Gears, oil temp, Torque converter status and more
3. Climatronics data (Get to see interior and exterior temps, as well as current fan speed, AC work load, Refrigerant pressure, flap statuses)
Future additions
1. Sending track data to Instrument cluster display - full name supported, as well as play duration
2. Phone support on IC display (Show current caller name, as well as call duration)
3. LOADS more sensor data - I have full access to every module on the cars as well as all the messages on canbus and their containing data!
4. Possible 0-60 lap timer?
5.
Why bypass the stock canbus box?
1. The stock decoder box with headunits spam data to the instrument cluster. I've reverse engineered the cluster protocol in these cars, so i can display a lot more text on the display!
2. The stock decoder box triggers the headunit to force show the reverse screen when the car is in reverse. I want the app to be in control of what happens, not the headunit.
3. The arduino required for this project talks to BOTH Canbus C and B, so no need for the headunits own box (Which i found out was filtering data)
What you'll need to try it
1. Malysk ROM installed (Root is required to run it, and Malysk has WIFI ADB debugging enabled for ease of development!)
2. Arduino Uno with 2x CANBUS shields (We will bypass the Headunits own canbus box for our own!
3. Suitable wires for running the Arduino to the 2 CAN systems on the car (see below)
Installation
1. Connect your Arduino to CANBUS C. I have 2 wires running to behind the instrument cluster. These plug into the 2 green wires on the cluster harness (Green is CAN L, Green+White is CAN H):
2. Connect your Arduino to CANBUS B. I have 2 wires running to the hub connector, accessible by removing the panel on top of the driver's pedals. (Brown is CAN L, Brown+Red is CAN H)
3. Connect your Arduino to a laptop, and upload the code found in UNO_CODE in the code repository
4. Connect the Arduino to the headunit with a USB cable.
5. Compile and upload the APK to the headunit, and choose "MERCEDES UI" as your new home screen.
6. Enjoy!
Code repository: https://github.com/rnd-ash/MBUX-Port

Ha - you the man.
First project Ive come across for my car.
However couple of Qs.
1, what is this project for, just to display car info with MB launcher?
I know this is good but without normal control of headunit apps there's not much point.
Could you not easily achieve the same with torque and a similar launcher thats similar
.
2nd. My px5 has a built in canbus, no way to bypass or disable it. Could it still work with the limitations / further research?
Does this have to be run on malaysk rom. Can it not be run as an app or on Hal9ks?
Anyway fantastic news and well done for having a go. Let me know if I can test anything for you.

203 or 211?
Currently, it's still in early stages! But I've been documenting it all on twitter: https://twitter.com/rndashm/status/1286652539337940992?s=19
You can disable canbus. If your using the factory harness (big black thing with loads of wires going out of it), what I did was to simply tape up the male canbus pins on the headunit, so they don't make contact
And as for using existing canbus. No you have to use a dedicated shield. The MTC headunits seem to filter a ton down by the time the Android OS connects to the MCU controller, so there is hardly anything useful there to see. Not to mention that same onboard MCU controller spams canbus with messages for the instrument cluster display from power on, and can't be turned off. Hence I had to bypass that as well in order to render text on the instrument cluster display (I plan to show track names playing on the AUDIO page and, if you have the telephone page, allow you to dial a contact from there! (Ive done this with a prototype project on my GitHub account called W203-Canbus).
For now, I don't think you can test anything as such but I suggest you get some wires ready for both can B and can C, and buy an Arduino Uno and 2x canbus shields

Great Job !!!
I was desperately looking for CANBUS related info for my use case on a mercedes car (2009 W164) where i receive very limited CANBUS info and found this thread.
Comparing folks with Audi/VW/SKODA where they are able to see pleanty of info (AC, Parking Sensors, door open etc) with my situation on a mercedes vehicle made me mad for not able to have those info available.
Keep up
Thx, Alexis

Thanks!
I'm making a series showing how I'm building the whole interface FYI - you can see all the interface progress as I'm designing the system:

@UKSFM99 how's it going, it's been a while since you posted these... ?

Question NaviFly 7862 steering wheel controls not working

Hi
I have purchased an Android HeadUnit for my Renault Megane 2 (2007) from AliExpress. Every function works except the steering wheel controls. The unit has the UIS7862 CPU @1.8Ghz, 6gb Ram and 128gb storage. I have installed the CanBox correctly and tried many CanBox settings in factory menu, but I cannot get the control app to enter learning mode. Does anyone have any idea? Maybe the built in key map application is at fault (com.syu.steer).

Did you find a solution to your problem yet?
I'm stuck at the exact same scenario, same unit. The support over at AliExpress mention to me to select "XP" for canbox settings. However, my canbus module is by Raise, hence I should be using the "RZC"
Also, my reverse cam doesnt work too.
Pls share your findings. Thank you!

I got the steering wheel keys to work with a custom controller made by an engineer in my country specifically for my car and my HeadUnit. The controller is connected directly to the wheel controls and the "key" wire on my HeadUnit. I had to disassembly the steering wheel base and route the cable around the original one. Now I can map every key to an action in the Key Learning app. For the backup camera, because I used a wireless kit, I couldn't use the "back" camera wire to trigger the HeadUnit to switch to it. The kit came with a receiver which only had power wires and a yellow RCA cable. I wired the receiver's power cables to the ACC power so that the receiver only powers on when the engine is running and I managed to map a button on the steering wheel to switch to the RCA input. Now when I want to use back up camera, I just need to press a button to see the image. The camera's transmitter is wired to the license plate bulb and I managed to fit it in the rear bumper.
This wasn't a "plug and play" experience that the Chinese seller promised, but overall I can say I am pretty happy with the end result. The audio quality is wayyy better than the stock HeadUnit. I didn't know that my stock speakers could get that loud and have so much bass. The DSP chip does it's job wonderfully. Also the radio reception is better than with the stock unit. The Android HeadUnit is fast and snappy. Apps open almost instantly and those 6gb of ram really help. I could compare the overall user experience with my OnePlus 7 phone. The unit also cold boots very quickly. The wifi reception is pretty poor. The unit shows 75% signal when my phone is in the car. It doesn't bother me because I put a Sim card in the unit and the mobile reception is as good as on my phone.

andrei-2200 said:
I got the steering wheel keys to work with a custom controller made by an engineer in my country specifically for my car and my HeadUnit. The controller is connected directly to the wheel controls and the "key" wire on my HeadUnit. I had to disassembly the steering wheel base and route the cable around the original one. Now I can map every key to an action in the Key Learning app. For the backup camera, because I used a wireless kit, I couldn't use the "back" camera wire to trigger the HeadUnit to switch to it. The kit came with a receiver which only had power wires and a yellow RCA cable. I wired the receiver's power cables to the ACC power so that the receiver only powers on when the engine is running and I managed to map a button on the steering wheel to switch to the RCA input. Now when I want to use back up camera, I just need to press a button to see the image. The camera's transmitter is wired to the license plate bulb and I managed to fit it in the rear bumper.
This wasn't a "plug and play" experience that the Chinese seller promised, but overall I can say I am pretty happy with the end result. The audio quality is wayyy better than the stock HeadUnit. I didn't know that my stock speakers could get that loud and have so much bass. The DSP chip does it's job wonderfully. Also the radio reception is better than with the stock unit. The Android HeadUnit is fast and snappy. Apps open almost instantly and those 6gb of ram really help. I could compare the overall user experience with my OnePlus 7 phone. The unit also cold boots very quickly. The wifi reception is pretty poor. The unit shows 75% signal when my phone is in the car. It doesn't bother me because I put a Sim card in the unit and the mobile reception is as good as on my phone.
Click to expand...
Click to collapse
Thank you for explaining your solution. Seems like quite a bit of work.
I managed to get my steering controls working finally. Got the correct canbus setting and corrected a connection.
Now, I'm stull stuck with the reverse cam issue. The +12V does energize when I am in reverse gear - I tested this when I connected my cam to DV-in and cam turns on only when in reverse.
But I just don't understand why the Android won't switch to Cam in during reverse gear.
Will continue to seek help from the manufacturer. Otherwise, it's a great HU as you said. Awesome speed!

MasK said:
Thank you for explaining your solution. Seems like quite a bit of work.
I managed to get my steering controls working finally. Got the correct canbus setting and corrected a connection.
Now, I'm stull stuck with the reverse cam issue. The +12V does energize when I am in reverse gear - I tested this when I connected my cam to DV-in and cam turns on only when in reverse.
But I just don't understand why the Android won't switch to Cam in during reverse gear.
Will continue to seek help from the manufacturer. Otherwise, it's a great HU as you said. Awesome speed!
Click to expand...
Click to collapse
You connected the reverse wire?
Maybe this triggers the camera view of it doesn't work via the canbus.

Well, it does work via canbus, just doesnt switch to cam input automatically. Perhaps its some software settings.

MasK said:
Well, it does work via canbus, just doesnt switch to cam input automatically. Perhaps its some software settings.
Click to expand...
Click to collapse
Not all canbus provide the reverse signal. So maybe you have to provide the reverse signal on the separate input.

TorstenH said:
Not all canbus provide the reverse signal. So maybe you have to provide the reverse signal on the separate input.
Click to expand...
Click to collapse
I feel that the HU knows when I am referring (CANBUS might be working here), because the 12V turns on when Im in reverse. The only issue is the HU doesnt switch to the cam automatically. Looks to me like a SW issue. Still awaiting reply from manufacturer.
Also, I realised my backward/forward buttons are swapped. Why is it I can't re-learn them?

It may not be the same for the Navifly, but on my unit, G5 must get the proper voltage to "detect" the car has been put in reverse. I'm re-using my factory rear view camera and it's a 6.5V camera. However, I had to up the voltage to 8.6V so that G5 go that voltage...then the rear image showed up. I reused the car wiring and that's why I had to do this.
Check the voltage that G5 is getting. With a canbus module, I believe there is a wire from the canbus going to G5. If no voltage, make sure the pins are in properly.
FYI, if you are using a canbus and the steering wheel controls go through the canbus, then I believe that you cannot remap the keys.

The 12 V from the reverse wire are coming from your car (or in some cases from the canbox if the information gets transmitted from car to the box via canbus).
My suggestion is:
There is a separate reverse connection (usually a brown wire) on the head unit which triggers the radio to open the app which shows the image of the reverse cam.
You could even connect ACC or B+ to the reverse connection for testing purposes.

mastrv said:
It may not be the same for the Navifly, but on my unit, G5 must get the proper voltage to "detect" the car has been put in reverse. I'm re-using my factory rear view camera and it's a 6.5V camera. However, I had to up the voltage to 8.6V so that G5 go that voltage...then the rear image showed up. I reused the car wiring and that's why I had to do this.
Check the voltage that G5 is getting. With a canbus module, I believe there is a wire from the canbus going to G5. If no voltage, make sure the pins are in properly.
FYI, if you are using a canbus and the steering wheel controls go through the canbus, then I believe that you cannot remap the keys.
Click to expand...
Click to collapse
Absolutely correct.

Thanks guys, but there is no other brown wire for this.
I have a discussion abt this on this thread too:
Medeke/Navifly 7862
Hi, Recently received above unit for my 2006 RS4. everything is great (much better then the M400 I had before) apart from the radio. It seemed to work for the first 2 days, then worked intermittently and now not at all. I have tried...
forum.xda-developers.com
My "cam12V" wire is from the HU and it turns on when I am in reverse. Does this mean that this signal might be coming from my canbus? If so, is there another input back to the HU to trigger the screen to display the video feed? Only other wires I see are AMP related

Give 12V to pin 2 and check if the app to display the image of the cam will start:

TorstenH said:
Give 12V to pin 2 and check if the app to display the image of the cam will start:
View attachment 5374441
Click to expand...
Click to collapse
Yes! It took me a while to figure this out.. mainly because I'll have to cut the wire (wasn't very confident in that)
and also.. the wires at Pin2 didn't make sense! They were more like Battery12V. I did cut and tested that.
So.. it turns out its a pink wire at pin3!
I realized this as I looked at my old Dasaita wires from the canbus connector. Since canbus is a standard, they should be comparable. That reverse wire went into Pin3.
I'm really surprised that Mekede and Navifly has this pin layout printed in all their listings.. but it's just wrong.
Thanks alot for the help!

That means it works now? I think you had to cut the ACC wire according to the manual because the "ignition on" information is provided by the can box.

TorstenH said:
That means it works now? I think you had to cut the ACC wire according to the manual because the "ignition on" information is provided by the can box.
Click to expand...
Click to collapse
Yes it works now. Check out the images. The Pin2 (red) is probably ACC or batt 12V as there was no power when cut. I then cut the wire opposite it (pin10) in case I was looking at the connector wrongly. That turned out to be the headlight sensor.
After tracing the wire and comparing to my old Daisata, it turns out Pin3 (pink) is the reverse IN.

Excellent. Thanks for the clarification.
That means it makes sense to get the wiring diagram from the old radio of the car and compare it with the description of the new head unit.
In my case I had to completely rewire the harness (just if someone is interested):
Junsun V1 MTK8259 - the adapter battle (Kia Ceed Jd) / OEM camera usage / reference thread
I bought the Junsun V1 head unit but my Kia Ceed JD had a OEM nav unit which isn't directly compatible to Junsun V1. So I re-wired the wiring harness based on the pins description of my original OEM navigation unit. I'm only modifying the wiring...
forum.xda-developers.com

The only thing that I could compare to (between old and new HUs) is the canbus connectors. Rest cannot be compared as they're all different.
Oh well..
Anyways, the current Mekede I have has Radio chip NX6686. My old Dasaita PX5 also has a NX6686. However, the radio reception is absolutely trash in the new one. I dont listen to radio that often (I can resort to streaming radio) but my dad takes the car occasionally and he's already complained about it
Your experience on the harness rewiring is pretty intense!
Update: Turns out my Antenna connector was a tad loose and I had to do a re-connect. The radio reception is all good now

MasK said:
Thank you for explaining your solution. Seems like quite a bit of work.
I managed to get my steering controls working finally. Got the correct canbus setting and corrected a connection.
Now, I'm stull stuck with the reverse cam issue. The +12V does energize when I am in reverse gear - I tested this when I connected my cam to DV-in and cam turns on only when in reverse.
But I just don't understand why the Android won't switch to Cam in during reverse gear.
Will continue to seek help from the manufacturer. Otherwise, it's a great HU as you said. Awesome speed!
Click to expand...
Click to collapse
So you found correct canbus settings and connections .. i cant find anything about you sharing them