Joying MTCB HU, USB connections. - MTCB Android Head Units Q&A

Just installed a Joying:
. SKU: JY-UL124 . Quad Core Android 5.1.1 Lollipop OS Capacitive 7" High Definition for Universal Double Din . CPU: RK3188 1.6GHz Cortex A9 Quad Core, Resolution 1024*600. RAM:DDR3 1G, 16 GB memory
To my 2014 Australian Hyundai Elantra.
I waited to get the latest HU from Joying that has an unrated mother board and USB/ Comms board. With Lollipop 5.1.1. the unit performs very well with none of the problem previously mentioned on these pages. The internal and external mics are clear and the Bluetooth systems are perfect. Unit has been rooted and I don't seem to need for apps so I won't changed the software.
The dimming for the button and the screen to follow the vehicles rheostat was fixed by making a circuit to invert and amplify the rheostat output to the HU ill line. Work's well, Kudos to the guys at the Subaru forums.
I had one bug fixed by Joying when the GPS nav was muted whenever I plugged in the DVR front camera. Joying quickly sent me a link to re flash my firmware and the problem was fixed. I have them currently looking into a bug when I view the DVR input shown on the HU I get lots of flashing to the screen in all pixel settings. I have been told this will be fixed in the next firmware update soon.
One problem that I can't solve is when I try to use my vehicles Multimedia Jack located in my center console. There is a Aux and USB jack there. All wiring from console to HU is complete. If I connect a USB stick to the Jack in the console then then HU struggles to connect and gives up. If I interrupt the USB plug and socket behind the HU then I am able to use the USB correctly. Looking at the car wiring diagrams there is a amplifier cct behind the Multimedia Jack supposedly to amp up the USB to HU. Doesn't seem to work?
Any ideas appreciated.
Duke
If anyone has any ideas on

i have nothing to add, other than interested to see what the result is. Are you saying that your car comes with a built in hub in the console, and you are trying to make that USB port in the console work to the Joying head unit? my vehicle is similar, and I would like that to work as well

Update
Yes I have a console hub I guess.
The book calls it a multimedia center. Just an Aux port and a USB port or Jack in the tidy bin in the center console. If I by pass the Jacks and directly put the USB stick into the USB tail from the radio then it works fine. When I plug into the console port it tries to read it and fails. The HU then reports a read fail, have tried other known working USB sticks.
I have inspected behind the console jacks and found a cct board attached to the Jacks and then to the car wiring. From looking at the diagrams of the car previous to mine I see a cct board containing what looks like an amplifier. Tracing the car wiring to the radio input connectors seems to be OK and the wiring correct. Voltages at the radio connector are right in that there is 5v +ve, negative - earth and the center pins are data as they should be.
The console Jacks
w.hemanual.org/multimedia_jack_description_and_operation-2037.html
The wiring for same (mine is same but more complex)
w.hemanual.org/multimedia_jack_schematic_diagrams-2036.html
Really bugs me not to be able to access that USB input Jack esp as the radio is a great unit.

You need to post this question in the MTCD (Lollipop) hardware thread. This thread is for MTCB (KitKat) units. The hardware in the MTCD headunits are very different than the MTCB headunits.

bsavoir22 said:
You need to post this question in the MTCD (Lollipop) hardware thread. This thread is for MTCB (KitKat) units. The hardware in the MTCD headunits are very different than the MTCB headunits.
Click to expand...
Click to collapse
When I tried to repost this in MTCD I get this.
vBulletin Message
To prevent spam, you must have a higher post count in order to make a new thread in this development section. But feel free to make new thread in the non-development sections like General, Q&A, etc. Thanks for your understanding!
Am I still in the wrong section?

Yes, the MTCD thread is for the headunits with 5.1.1. The hardware changes and software are different. Send one of the admin a message and tell the why you need to get the permissions to post. I had to do that some time ago. Just make sure you follow the rules when post or you can have you account suspended or whatever the moderators deem necessary.
Sent from my SM-N910T3 using Tapatalk

Posting
Ok thanks for that. I don't seem to be able to find how to "Send one of the admin a message" Can you help?

Just for info, there are both MTCB/C and MTCD/E Lollipop units.

Related

MTCD schematic

Found - MTCD Schematic. A most valuable find on russian android car audio forum and attached here.
[Android Car Audio]
The schematic corresponds to a GS Mainboard I have as a spare part. It varies to my JY board in terms of USB operation, with this board OTG is provided for.
This is ridiculously helpful, regardless of what MTCD manufacturer you have. I've had to replace MOSFET's and internally shorted caps in my KGL before, and having a general reference like this would have made the process so much quicker. Cheers!
MbTaNk16 said:
This is ridiculously helpful, regardless of what MTCD manufacturer you have. I've had to replace MOSFET's and internally shorted caps in my KGL before, and having a general reference like this would have made the process so much quicker. Cheers!
Click to expand...
Click to collapse
Indeed! I was astounded to find this. Unfortunately I still wasnt able to get my PX5 board to go into maskrom for OTG flashing, but is probably something I am not doing right. Schematic is absolutely valid and is spot on for MTCD GS.
18/07 - Was able to put PX5 into OTG [LOADER] mode after modifying board.
Thanks @cupi1234
marchnz said:
Anyone with a 4pda account - can you please try and download and attach here - http://4pda.ru/forum/dl/post/9567228/MTCD++Witson-A510-2016-04-28+V01.pdf
[MTCD Witson-A510-2016-04-28+V01.pdf - 4PDA]
Click to expand...
Click to collapse
witson
Hi, does somebody knows the wiring of the PB76FSAP-S, an MTCD from Ownice (C500). I am trying to connect a OTS020 tpms to port F. The OTS020 has 4 wires, +, gnd, data and something else. I want to know how the unit supplies power and wich pins are used for data.
Thanks.
747 Driver said:
Hi, does somebody knows the wiring of the PB76FSAP-S, an MTCD from Ownice (C500). I am trying to connect a OTS020 tpms to port F. The OTS020 has 4 wires, +, gnd, data and something else. I want to know how the unit supplies power and wich pins are used for data.
Thanks.
Click to expand...
Click to collapse
The Ownice C500 is not an MTCD unit. Ownice dont make MTCD units, their units are of an entirely different design with totally incompatible software.
Source for Raw Audio Output?
Looking at this schematic on page 10, it appears that the section labeled 'ARM' would be the interface connector from the Android board to the MCU Board.
Following @dazza007 's and @7floor 's posts below, it looks like the raw audio output from the Android Board is available at pins 12 and 13. Without a schematic of the Android Board I can't be sure, but I assume that these should trace back to pins 12 and 13 from the WM8731 Audio Codec chip.
If I'm correct and we could harness these raw line level audio outputs it could give the people that were looking for a clean feed for DSP's and the like.
Full disclosure, I do not have one of these units yet but am looking at a GCS Apex branded unit that appears to be a MTCD KLD model per the merchant website pictures. http://www.subispeed.com/2013-crosstrek/interior/audio-stereo-upgrades/gcs-apex-android-v2-head-unit-w-gps-2013-2016-forester-crosstrek#.WgRiFFuPLIU
dazz007
https://forum.xda-developers.com/android-auto/mtcb-hardware-development/mtc-sound-controlling-bd37xxx-sound-t3234660
7floor
https://forum.xda-developers.com/showpost.php?p=63520630
typos1 said:
The Ownice C500 is not an MTCD unit. Ownice dont make MTCD units, their units are of an entirely different design with totally incompatible software.
Click to expand...
Click to collapse
Please enlighten me. It says MTCD in the settings, I have a GS v 2.56 running.
What type of unit is it? According Xtrons it is a PB-76FSFAP-S. What type is it (MCT/B/C/D/E?)
Thanks
747 Driver said:
Please enlighten me. It says MTCD in the settings, I have a GS v 2.56 running.
What type of unit is it? According Xtrons it is a PB-76FSFAP-S. What type is it (MCT/B/C/D/E?)
Thanks
Click to expand...
Click to collapse
If it says "MTCD GS" in the MCU field then you have a GS MCD unit.
Xtrons are simply resellers - they buy units from various manufacturers and then give them made up model numbers.
Ownice are an entirely different company that make entirley different units.
i have a GS PX5 Android 6.0 ( now migrated to Oreo) unit, i'd like to know if this board have USB OTG port.
I need to connect a USB/SPDIF Converter , the Matrix X-SPDIF2, and it is Android 8 certified for USB OTG port.
PX5 MX2 Unit No RESET
Hey guys,
I'm half offtopic here, but my thing has to do with the schematics / HW mod (can't open topics due to low post count..)
Just recently bought a replacement for my Opel Astra J '12 and ..
It's a MX PX5 4GB Oreo sold by Witson.
This HU is very specific, because it comes in two parts.
1. Silverbox with the MCU and sockets + 2. Display board with SD slot
My point writing here is, that it doesn't have a reset hole - Oh well yea it has, but behind it there's nothing to push
Desperate as I am, I wanna have a reset button to enter recovery and .. well - if it gets stuck, to recover.
As the silverbox will be behind the dash, my only option would be the display board, where I found two connectors having a PIN def for RST_KEY and now I need instructions how to do the cabling, as I'm not sure how to achieve the reset function.
RST_KEY + GND ?
OTG? Found a little connecter not having a corresponding plug (white 8PIN in IMG_2613)
-> Pictures
abload.de/gallery.php?key=sNOKaV7R
Would be cool if you guys help me out
BR X
Hey Xorit,
I guess you've got the v5754 unit.
The reset line won't help you for recovery, I tried the same and reset is only a hard reset.
I've soldered a cable to key1, gnd and led8v on the display part (under the back cover), put a plug on the end and placed it in the glove department.
I then made a small pcb with a tactile switch connecting key1 - gnd and a 12v led on led8v and gnd, with this you'll be able to enter recovery by holding the button until the led flashes 3 times and then stays on,
Releasing it for a second and the keep on pressing, releasing, pressing for a couple of times.
I'm not sure if you're able to flash any custom rom because the sd slot on these units is a USB converted and not a gps slot.
Btw. I flashed mine with a custom rom by extracting the board, placing it in a xtrons model and then puting it back.
Thanks for that super helpful post!
Just ordered the needed components
Yep, indeed the V5754.
Dunno why they didnt wire any of those support keys.
Thanks mate!
bunnymc said:
Hey Xorit,
I guess you've got the v5754 unit.
The reset line won't help you for recovery, I tried the same and reset is only a hard reset.
I've soldered a cable to key1, gnd and led8v on the display part (under the back cover), put a plug on the end and placed it in the glove department.
I then made a small pcb with a tactile switch connecting key1 - gnd and a 12v led on led8v and gnd, with this you'll be able to enter recovery by holding the button until the led flashes 3 times and then stays on,
Releasing it for a second and the keep on pressing, releasing, pressing for a couple of times.
I'm not sure if you're able to flash any custom rom because the sd slot on these units is a USB converted and not a gps slot.
Btw. I flashed mine with a custom rom by extracting the board, placing it in a xtrons model and then puting it back.
Click to expand...
Click to collapse
got it working with ur directions!
the button mutes on single press, so it might be possible that the mute button on the steering wheel will do the same..would be weird tho.
might be helpfull for those who have no reset button either!
that new button selects options on single press in recovery and activates on long press, just like the normal reset hole.
->
on the display board you have two flat flexi cable connectors (not in use), where there are pin outs for usb + led + 2 keys.
thanks again!
Hey i have one Question. It says u can Solder it directly to the SOM or with a Flexible flat Cable. I have on my Unit the SOM and this is connectet to the Bigger Board. On this Bigger board i have 2 Flat Flex Connectors. Can i use them for this method?! And if yes wich one is the Right flat connector and where to get a flexible Band cable!? Would help me much if someone helps me because i have done the USB OTG Cable mod and now i have no Recovery and no USB anymore so i can not flash anything. I tried flashing in Android an MCU update but it does not do. Downloaded all to the units internal storage.
Greetz Tom
Nice I'm glad that it did the trick for you
The mute button from your steering wheel won't work because it's connected via canbus (same as cd3/4/600 button panel).
The mute from the soldered button is just a setting in the firmware (you could change it with the steering wheel button assignment settings to whatever you want.
I also added 2 more tactile switches to the key1 line with different resistors (resistor ladder) to be able to use them as hardware buttons (e.g. Vol up/down and power) but haven't had the chance to test it yet.
Xorit said:
got it working with ur directions!
the button mutes on single press, so it might be possible that the mute button on the steering wheel will do the same..would be weird tho.
might be helpfull for those who have no reset button either!
that new button selects options on single press in recovery and activates on long press, just like the normal reset hole.
->
on the display board you have two flat flexi cable connectors (not in use), where there are pin outs for usb + led + 2 keys.
thanks again!
Click to expand...
Click to collapse
Still in the wrong forum !!
typos1 said:
Still in the wrong forum !!
Click to expand...
Click to collapse
I reported - post gone.

Anyone with a dead px3 who can locate the SPDIF pin? (Expose the Balls)

Hi, I recently installed an MTCD px3 unit in my car but the audio quality is not that great. I'm looking at the option of a USB DAC but that appears to have its own set of issues and complexity.
I do note though that the RK3188 chip includes an SPDIF function and this does appear as an audio device in /proc/asound/cards so if the pins (balls) are exposed somewhere on the px3 module board then it should be just a matter of soldering to the right points to create an SPDIF interface.
If someone has a totally bricked unit would you consider doing some research? I.e. using some heat to the remove the RK3188 BGA chip and locating the ball that relates to SPDIF and seeing if it can be traced to a track?
The SPDIF transmitter is located at ball N20. You can find the datasheet by googling "RK3188 Datasheet" (sorry I can't post links yet). So who can "expose the balls"?
Alternatively if someone has a dead board/unit they would give away, I'd be happy to pay shipping for you to send it to me (in New Zealand) and I'll do the research and share my findings with the community.
Also looking for someone who understands what would be required on the software side of things to actually use the interface. Some kind of ALSA magic I guess?
Note - I do understand the limitation. I.e. this only applies to audio within Android, not the radio or bluetooth etc. My approach would be to install a physical switch so I could switch my car amp between the analog and digital outputs.
mcraenz said:
Hi, I recently installed an MTCD px3 unit in my car but the audio quality is not that great. I'm looking at the option of a USB DAC but that appears to have its own set of issues and complexity.
I do note though that the RK3188 chip includes an SPDIF function and this does appear as an audio device in /proc/asound/cards so if the pins (balls) are exposed somewhere on the px3 module board then it should be just a matter of soldering to the right points to create an SPDIF interface.
If someone has a totally bricked unit would you consider doing some research? I.e. using some heat to the remove the RK3188 BGA chip and locating the ball that relates to SPDIF and seeing if it can be traced to a track?
The SPDIF transmitter is located at ball N20. You can find the datasheet by googling "RK3188 Datasheet" (sorry I can't post links yet). So who can "expose the balls"?
Alternatively if someone has a dead board/unit they would give away, I'd be happy to pay shipping for you to send it to me (in New Zealand) and I'll do the research and share my findings with the community.
Also looking for someone who understands what would be required on the software side of things to actually use the interface. Some kind of ALSA magic I guess?
Note - I do understand the limitation. I.e. this only applies to audio within Android, not the radio or bluetooth etc. My approach would be to install a physical switch so I could switch my car amp between the analog and digital outputs.
Click to expand...
Click to collapse
Hi.. my Android Radio just recently crashed. If you like.. i can give it to you.
Its a Hot Audio Android Radio PX3 RK3188.
Thanks very much. I've sent a PM.
Cheers,
Rhys
do you located SPDIF transmitter? Is possibile to connect directly an external DSP such Audison P8.9?
Bump

Help Please - AV Output Question

Hi all, hope someone can help me,
I have an X-Trons branded unit MTCE_GS PX5 unit running Android Oreo (8.0) and all seems to be working well except for the AV-Out.
I was assuming I could use one of the two AV Out connections to connect to the TV in my Campervan to mirror the screen. I have tried to connect to them both but getting no output to the TV.
Is there a setting I need to change or is it not possible and these connections are for something else?
Thanks
KevCorks
Some of these Android head-units only send output to the video out connections when the unit is in Aux or DVD mode.
I ordered two units - one Hizpo-branded unit (MTCE-XRC), which I believe is that same as the Xtrons - and an Eonon-branded unit (MTCE-WWW) - both octa-core, 4GB of RAM and running Android 8.0.
The Eonon-branded MTCE-WWW unit sends the video out signal at ALL times regardless of the input selected - it simply mirrors what is on the head-unit screen regardless of what it is.
The Hizpo-branded MTCE-XRC unit would only send the video out signal if you were playing a DVD or used the Aux input.
Both units, however, did let you view the navigation app on the head-unit screen while also sending the video out signal (so you could still see navigation without interfering with the video output sent to other screens).
I suspect that your video out will only work if viewing a DVD or when using the aux-in input.
Thanks
Thats a bugger!
My intention was to use the head unit when camping to feed to the TV for Iplayer, Netflix etc.
I Don't use a DVD player anymore and don't want to feed a signal into the stereo just to feed it out to the TV, kind of defeats the object really.
Thanks for the quick reply
KevCorks
Yeah, I was kind of disappointed with the way the Hizpo-branded unit worked in that respect as well. I have headrest monitors in my car and really don't use physical DVD's anymore either - so it basically rendered my headrest monitors useless. I ended up returning the Hizpo and kept the Eonon. Although, neither unit has real "dual zone" capabilities like my older WinCE-baded head-units, which allowed me to send both audio and video to the headrest monitors while using the head-unit for something completely different (so I could listen to music while the kids in the back watched movies with headphones). Can't do that with these Android units, which is a shame. Fortunately, my kid is older now so I rarely use the headrest monitors any more (especially since kids have tablets nowdays anyway)...
kevcorks said:
Thanks
Thats a bugger!
My intention was to use the head unit when camping to feed to the TV for Iplayer, Netflix etc.
I Don't use a DVD player anymore and don't want to feed a signal into the stereo just to feed it out to the TV, kind of defeats the object really.
Thanks for the quick reply
KevCorks
Click to expand...
Click to collapse
The solution for me to use video out was to buy an displaylink usb card with hdmi output , to plug it on USB/OTG and install DisplayLink Presenter.
I try a lot of usb otg to hdmi adapter, and compatible "displaylink" driver because it is very simple without any start program each time.
The problem is to buy the right card: small, compatible OTG, without dc 5v... : for me it was: "Delock Adapter USB 3.0 > HDMI (4K)" / Item No. 62617.
myspac said:
The solution for me to use video out was to buy an displaylink usb card with hdmi output , to plug it on USB/OTG and install DisplayLink Presenter.
I try a lot of usb otg to hdmi adapter, and compatible "displaylink" driver because it is very simple without any start program each time.
The problem is to buy the right card: small, compatible OTG, without dc 5v... : for me it was: "Delock Adapter USB 3.0 > HDMI (4K)" / Item No. 62617.
Click to expand...
Click to collapse
Thanks @myspac !!
I'd like to copy your idea Quick 3 questions:
1) While the adapter is USB 3.0 I assume your unit was USB 2.0 right? No problem for the adapter to work on USB 2 mode, right?
2) How is the delay? noticeable? My idea is to have a 2nd screen closer to the line of sight of the driver, mainly to see the navigation, so delay any will be a problem.
3) Any additional advice?
Kr
Max
Video out Android 8.0 PX5 MTCE XRC upgraded to Hal9k
I have same problem no video outs on mtce xrc i was thinking maybe need to replace mcu software for other one it will work if i put mtce hu ore some other? i dont know if i can put mcu from another manufacture ! so please if someone knows replay to me.thanks!!!
maxiauer said:
Thanks @myspac !!
I'd like to copy your idea Quick 3 questions:
1) While the adapter is USB 3.0 I assume your unit was USB 2.0 right? No problem for the adapter to work on USB 2 mode, right?
2) How is the delay? noticeable? My idea is to have a 2nd screen closer to the line of sight of the driver, mainly to see the navigation, so delay any will be a problem.
3) Any additional advice?
Kr
Max
Click to expand...
Click to collapse
did you manage to make the connection afterwards, if yes what did you buy?
thanks
dodis827 said:
did you manage to make the connection afterwards, if yes what did you buy?
thanks
Click to expand...
Click to collapse
Yeap, and it mostly worked.
So, I acquired "PPA USB 3.0 to HDMI External Display Adapter 5460", but only because it was available at Frys on my neighborhood and I could return it in case the idea did not work. I guess any DisplayLink compliant adapter would work the same.
Some caveats:
- I never perceived any delay
- Works on Android 8 and 9
- In android 9, sometimes the video is not mirrored. I haven't had time to debug it, it might be the fact that I am using a custom ROM. Plug and Unplug the USB solves it, but as my cabling is not accessible, I usually reset the unit.
- I use the DisplayLink Desktop (Demo) (Early Access) app and NOT the DisplayLink Presenter App (so, you will be using a beta app). Not sure if the Presenter App works.
- The Desktop SW will try to send audio through the HDMI. I solved that with "Lesser AudioSwitch" app to have control of audio routing (maybe the DisplayLink Presenter app does not have this problem?)
All in all, I am happy with the outcome. While not perfect (due to the random black displays now and then), it is not expensive and easy to install.
Hope this helps
maxiauer said:
Yeap, and it mostly worked.
So, I acquired "PPA USB 3.0 to HDMI External Display Adapter 5460", but only because it was available at Frys on my neighborhood and I could return it in case the idea did not work. I guess any DisplayLink compliant adapter would work the same.
Some caveats:
- I never perceived any delay
- Works on Android 8 and 9
- In android 9, sometimes the video is not mirrored. I haven't had time to debug it, it might be the fact that I am using a custom ROM. Plug and Unplug the USB solves it, but as my cabling is not accessible, I usually reset the unit.
- I use the DisplayLink Desktop (Demo) (Early Access) app and NOT the DisplayLink Presenter App (so, you will be using a beta app). Not sure if the Presenter App works.
- The Desktop SW will try to send audio through the HDMI. I solved that with "Lesser AudioSwitch" app to have control of audio routing (maybe the DisplayLink Presenter app does not have this problem?)
All in all, I am happy with the outcome. While not perfect (due to the random black displays now and then), it is not expensive and easy to install.
Hope this helps
Click to expand...
Click to collapse
Thanks, I have a dasaita px5 with 4 GB of ram with Android 6.1, do you think there is hope that it will work? But every time you turn on the radio does it connect automatically?
dodis827 said:
Thanks, I have a dasaita px5 with 4 GB of ram with Android 6.1, do you think there is hope that it will work? But every time you turn on the radio does it connect automatically?
Click to expand...
Click to collapse
I also have the Dasaita PX5 that (originally) came with Android 6.1 (MTC-D version, not E). I don't know if this would work on Android 6.1. DisplayLink claims the app requires "Any Android device running Lollipop 5.0 or later..." and the device is plain USB 2.0... but you never know with old Android releases. Worst case you will have to upgrade to Andoid 8 or 9
The DisplayLink App is able to auto-start every time that the USB port is started and the DisplayLink device is detected (meaning, every time you start the car). In my case, this usually works w/o issues...but once a week it fails to detect the DisplayLink device. This problem could be the device I am using (DisplayLink sells the patent to chinese companies to manufacture their own device), the fact that I am using a custom ROM, or the fact that the DisplayLink app is still beta...
In short: I can not promise it will always work. And I can not promise that any chinese HW will work as well as the one I have.
Also, you might want to route the USB cable using an USB extension cord, in a way that you can plug and unplug the extension without dismounting the whole unit...just in case.
WARNING: my DSP antenna was almost NEXT to the external display, and I originally used cheap HDMI cables to go from the adapter to the display. That messed my GPS in a terrible way (no Satellite found). Problem was solved when I acquired a better (not necessarily top expensive) HDMI cable.
Hope this helps
Max
maxiauer said:
I also have the Dasaita PX5 that (originally) came with Android 6.1 (MTC-D version, not E). I don't know if this would work on Android 6.1. DisplayLink claims the app requires "Any Android device running Lollipop 5.0 or later..." and the device is plain USB 2.0... but you never know with old Android releases. Worst case you will have to upgrade to Andoid 8 or 9
The DisplayLink App is able to auto-start every time that the USB port is started and the DisplayLink device is detected (meaning, every time you start the car). In my case, this usually works w/o issues...but once a week it fails to detect the DisplayLink device. This problem could be the device I am using (DisplayLink sells the patent to chinese companies to manufacture their own device), the fact that I am using a custom ROM, or the fact that the DisplayLink app is still beta...
In short: I can not promise it will always work. And I can not promise that any chinese HW will work as well as the one I have.
Also, you might want to route the USB cable using an USB extension cord, in a way that you can plug and unplug the extension without dismounting the whole unit...just in case.
WARNING: my DSP antenna was almost NEXT to the external display, and I originally used cheap HDMI cables to go from the adapter to the display. That messed my GPS in a terrible way (no Satellite found). Problem was solved when I acquired a better (not necessarily top expensive) HDMI cable.
Hope this helps
Max
Click to expand...
Click to collapse
Ok Thank you, I want to buy this StarTech-com-Adattatore-Convertitore-Esterna-Displaylinkd, The manufacturer says it's not compatible with Android, now I don't know what to buy is try, If it doesn't work I throw away 70€
dodis827 said:
Ok Thank you, I want to buy this StarTech-com-Adattatore-Convertitore-Esterna-Displaylinkd, The manufacturer says it's not compatible with Android, now I don't know what to buy is try, If it doesn't work I throw away 70€
Click to expand...
Click to collapse
So, what won't work for sure is the feature of "...installazione e aggiornamenti automatici dei driver..." because Win drivers are different than Android. Actually, that looks to me like "tricky advertising", my understanding is that DisplayLink drivers come by default with Windows, so all DisplayLink are plug&play on windows.
Will the device work once you installed DisplayLink app on Android?... it should, but...
Anyway the device looks expensive (although Star-Tech is a good brand) Why not trying with some Chinese HW? Also, is Amazon available on your area? Usually you can return things to Amazon without any issue.
Max
maxiauer said:
So, what won't work for sure is the feature of "...installazione e aggiornamenti automatici dei driver..." because Win drivers are different than Android. Actually, that looks to me like "tricky advertising", my understanding is that DisplayLink drivers come by default with Windows, so all DisplayLink are plug&play on windows.
Will the device work once you installed DisplayLink app on Android?... it should, but...
Anyway the device looks expensive (although Star-Tech is a good brand) Why not trying with some Chinese HW? Also, is Amazon available on your area? Usually you can return things to Amazon without any issue.
Max
Click to expand...
Click to collapse
Yes I have Amazon in my area cost so much..... How much did you pay him?
I know it's an old thread, but only one I could find about getting video out to work on these units. Joying now sells a USB to rca video adapter and I wanted to ask if anyone has tried it on different brand units? They say it only works on joying and even messaged me after I ordered one to confirm I had joying unit (I do not in fact but told them to please send it anyway). I have an Xtrons px5 unit with Android 10. The dongle says for joying Android 10 unit so I'm hoping that since most of these units are similar it will still work.
Here is link to that dongle:
Joying RCA Video Out Adapter for Headrest
SKU: V-RCAShip From: China Note: This RCA video out adapter only compatible with Joying Android 10.0 car radio, if you own other system JOYING head unit, please don't buy this. It will ship by China post, 12-28 days to arrive, if you want fast shipping methond, pls pay extra 15USD at this link.
www.joyingauto.com
jmckeejr said:
I know it's an old thread, but only one I could find about getting video out to work on these units. Joying now sells a USB to rca video adapter and I wanted to ask if anyone has tried it on different brand units? They say it only works on joying and even messaged me after I ordered one to confirm I had joying unit (I do not in fact but told them to please send it anyway). I have an Xtrons px5 unit with Android 10. The dongle says for joying Android 10 unit so I'm hoping that since most of these units are similar it will still work.
Here is link to that dongle:
Joying RCA Video Out Adapter for Headrest
SKU: V-RCAShip From: China Note: This RCA video out adapter only compatible with Joying Android 10.0 car radio, if you own other system JOYING head unit, please don't buy this. It will ship by China post, 12-28 days to arrive, if you want fast shipping methond, pls pay extra 15USD at this link.
www.joyingauto.com
Click to expand...
Click to collapse
Did it work the joying adapter?
Eddie31386 said:
Did it work the joying adapter?
Click to expand...
Click to collapse
It did not unfortunately.
jmckeejr said:
It did not unfortunately.
Click to expand...
Click to collapse
Is it an MTCD
marchnz said:
Is it an MTCD
Click to expand...
Click to collapse
It's MTCD/MTCE. Exact model is PBX80JCCL.
jmckeejr said:
It's MTCD/MTCE. Exact model is PBX80JCCL.
Click to expand...
Click to collapse
Yes but is it an MTCD type.
You would have noted the posts listing how to ID your unit, based on MCU version.

Seicane CANBUS assistance

Hi everyone,
I haven't been on in a while and my username is new, but been using the site for years in the early root days.
I just purchased and installed a Seicane head unit in my Volvo XC60. Things are working great, but I had to bypass the amp to get sound which I thought was weird. Once installed, I noticed none of my buttons would work. Doing some research, I see that this could be due to the CANBUS not being set up correctly. The unit is a P series with a Octa-Core Cortex-A53. I went into the the factory settings where you can pick your CANBUS but I cannot find one that specifically states Volvo. The harness that was provided by Seicane bridges between the stereo and the main unit and information screen. The main until connector provides power and ground. The information system provides some CANBUS lines to the unit. I would think that since these CANBUS lines feed into the unit I would not need a separate box to decode them, but I could be wrong.
1. Is anyone familiar with CANBUS that might give me some insight into which CANBUS manufacture option I should pick.
Is it an MTCB unit or something else. Details are everything.
MTCE_hf_v3.30_1.
Edit: I just realized that I posted in the wrong area. Apologies. Deleting.

Would like to better understand canbus integration, please help educate me

I've searched and searched but only find bits and pieces of information. So far, I haven't been able to connect enough dots to understand how this works.
Back in 2016 I purchased an Android head unit from Auto Pumpkin. I stumbled upon it by pure accident, thought it looked slick, and decided give it a shot. The radio body was Chevrolet specific so it popped right into my Express van. It also came with a canbus decoder box which I didn't know anything about but hooked up anyway and was impressed by the integration. Door status, reverse overlays, brightness control, and some other cool stuff.
Fast forward to last year, I bought another head unit for a new Chevy van but I couldn't find one that came with the canbus integration so it's installed as a standalone radio. The unit has the canbus pins on the back, but the corresponding wire harness didn't have any conductors to match up with them. It also didn't come with any type of canbus decoder. The config area in Factory Settings is still there, though.
That brings me to my first question: Are the pins on units like these still ready/capable to be connected to *something* even though the wire harnesses that come with them don't have the specific wires for it? What I'm asking is, if I purchase a Chevrolet canbus decoder separately, can I hook it up (adding the required wires) and expect it to work?
Lastly, I recently purchased yet another head unit, this time from Dasita, for my RV. It's built on a Ford chassis. Same as before, the radio has the pins (and they're labeled as canbus!), but the wire harness doesn't have wires connected to those pins.
Is there a Ford canbus decoder available somewhere, and, with some tinkering, is it possible to get the vehicle to talk to the head unit?
nomaxtech said:
Is there a Ford canbus decoder available somewhere, and, with some tinkering, is it possible to get the vehicle to talk to the head unit?
Click to expand...
Click to collapse
Yup, just make sure you order the right one for your head unit.
https://www.aliexpress.com/item/4000875414226.html?spm=a2g0o.productlist.0.0.2d785d7aDFgDYy&algo_pvid=8d9f7a38-3a25-48c1-8c5b-a0f1372ec0d7&algo_expid=8d9f7a38-3a25-48c1-8c5b-a0f1372ec0d7-3&btsid=0b0a556e16134130756217144e212d&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_

Categories

Resources