Hi there
So i downloaded from here MCU MX v3.71 as i have v3.60_1 at the moment.
Formatted a 4GB USB stick as FAT32, default allocation list and copied dmcu.img on the root of the USB
Then, inserted the stick into HU USB port, clicked on MCU update, it was found, system restarted.
next ? surprise: Android green guy dead, and "no command" on the screen.
I shut down the car for 5 mins to let the unit go to sleep and when i put the ignition on, the unit started fine, but still having old MCU
next, i plugged the USB stick into my computer and surprise: "this disc needs to be formatted".
Somehow, android unit didn't update the MCU but damaged the USB stick filesystem.
Did anyone have the same issue ? I am afraid now to use a different USB and repeat the process because my reset button is inside the screen and i need to dismantle half the dashboard to reach that button.
I have an AOTSR PX6 RK3399 unit with Android 10 and HCT2 kernel (firmware), MCU is MX v3.60
Thanks
tox2k4 said:
Hi there
So i downloaded from here MCU MX v3.71 as i have v3.60_1 at the moment.
Formatted a 4GB USB stick as FAT32, default allocation list and copied dmcu.img on the root of the USB
Then, inserted the stick into HU USB port, clicked on MCU update, it was found, system restarted.
next ? surprise: Android green guy dead, and "no command" on the screen.
I shut down the car for 5 mins to let the unit go to sleep and when i put the ignition on, the unit started fine, but still having old MCU
next, i plugged the USB stick into my computer and surprise: "this disc needs to be formatted".
Somehow, android unit didn't update the MCU but damaged the USB stick filesystem.
Did anyone have the same issue ? I am afraid now to use a different USB and repeat the process because my reset button is inside the screen and i need to dismantle half the dashboard to reach that button.
I have an AOTSR PX6 RK3399 unit with Android 10 and HCT2 kernel (firmware), MCU is MX v3.60
Thanks
Click to expand...
Click to collapse
What issue do you think will be resolved by updating the MCU? The MCU isn't Android.
my Waze app keeps crashing... i know that this issue might be from the firmware but i have a 2 unit pieces for Opel Astra J, it has a original fitting HU with DVD player which connects with 2 lots of pin cables to the display, and no reset button or hole. So is not a 1 unit Android, is 2 pieces. All main cables come from the big HU which sits instead of the original HU
I am really afraid to put another Android 10 firmware as i don't know how to enter recovery if something goes wrong
tox2k4 said:
my Waze app keeps crashing... i know that this issue might be from the firmware but i have a 2 unit pieces for Opel Astra J, it has a original fitting HU with DVD player which connects with 2 lots of pin cables to the display, and no reset button or hole. So is not a 1 unit Android, is 2 pieces. All main cables come from the big HU which sits instead of the original HU
I am really afraid to put another Android 10 firmware as i don't know how to enter recovery if something goes wrong
Click to expand...
Click to collapse
You've confused MCU with Android. At that point, I agree, leave it as is.
tox2k4 said:
Hi there
So i downloaded from here MCU MX v3.71 as i have v3.60_1 at the moment.
Formatted a 4GB USB stick as FAT32, default allocation list and copied dmcu.img on the root of the USB
Then, inserted the stick into HU USB port, clicked on MCU update, it was found, system restarted.
next ? surprise: Android green guy dead, and "no command" on the screen.
I shut down the car for 5 mins to let the unit go to sleep and when i put the ignition on, the unit started fine, but still having old MCU
next, i plugged the USB stick into my computer and surprise: "this disc needs to be formatted".
Somehow, android unit didn't update the MCU but damaged the USB stick filesystem.
Did anyone have the same issue ? I am afraid now to use a different USB and repeat the process because my reset button is inside the screen and i need to dismantle half the dashboard to reach that button.
I have an AOTSR PX6 RK3399 unit with Android 10 and HCT2 kernel (firmware), MCU is MX v3.60
Thanks
Click to expand...
Click to collapse
hi, i have same AOTSR headunit, can you please post the url where you have downloaded MCU MX v3.71, thanks
tox2k4 said:
my Waze app keeps crashing... i know that this issue might be from the firmware but i have a 2 unit pieces for Opel Astra J, it has a original fitting HU with DVD player which connects with 2 lots of pin cables to the display, and no reset button or hole. So is not a 1 unit Android, is 2 pieces. All main cables come from the big HU which sits instead of the original HU
I am really afraid to put another Android 10 firmware as i don't know how to enter recovery if something goes wrong
Click to expand...
Click to collapse
same here, Waze keep crashing randomly
vralvi said:
hi, i have same AOTSR headunit, can you please post the url where you have downloaded MCU MX v3.71, thanks
Click to expand...
Click to collapse
No, search for it.
vralvi said:
same here, Waze keep crashing randomly
Click to expand...
Click to collapse
here is thread: https://forum.xda-developers.com/t/...ith-mx-or-mx2-to-use-it.3913654/post-84413769
I only wanted to update the MCU because it is the last version, but this does not manage applications, it's the ROM that does that, as marchnz said.
You may need to ask from your seller support a newer version of the ROM you are running. I did the same but the language barrier is huge, i did not solve anything OR install a custom rom such as Malaysk ROM. I read somewhere here that Waze app needs to be downloaded from Aptoide and has to be a specific version for it to work but i cannot recall which thread was it.
tox2k4 said:
here is thread: https://forum.xda-developers.com/t/...ith-mx-or-mx2-to-use-it.3913654/post-84413769
I only wanted to update the MCU because it is the last version, but this does not manage applications, it's the ROM that does that, as marchnz said.
You may need to ask from your seller support a newer version of the ROM you are running. I did the same but the language barrier is huge, i did not solve anything OR install a custom rom such as Malaysk ROM. I read somewhere here that Waze app needs to be downloaded from Aptoide and has to be a specific version for it to work but i cannot recall which thread was it.
Click to expand...
Click to collapse
thank you
tox2k4 said:
here is thread: https://forum.xda-developers.com/t/...ith-mx-or-mx2-to-use-it.3913654/post-84413769
I only wanted to update the MCU because it is the last version, but this does not manage applications, it's the ROM that does that, as marchnz said.
You may need to ask from your seller support a newer version of the ROM you are running. I did the same but the language barrier is huge, i did not solve anything OR install a custom rom such as Malaysk ROM. I read somewhere here that Waze app needs to be downloaded from Aptoide and has to be a specific version for it to work but i cannot recall which thread was it.
Click to expand...
Click to collapse
MCU MX v3.71 worked on my unit, i upgraded from 3.60 with no issues
Related
I installed an Xtrons PF75ATTAR a couple of days ago, replacing the factory Audi RNS-E. It worked fine when I installed it. I then upgraded the software and the MCU firmware with the updated files on Xtrons website, it killed off TomTom due to the serial number thing but other than that it worked as before. I upgraded the software to Malaysk's latest v7 and managed to get TomTom working with the Xposed stuff so all good.
Today however I get in the car and there is no sound. If I turn the volume up I can see it showing on the head unit, I have tried the Radio, music etc and no sound is heard I have checked all the connections and everything is fine.
I put the original Audi RNS-E back in and there is sound so its not the car's amplifier (BOSE). I assume its a hardware fault on the unit? Anything else I should check before trying to contact Xtrons?
Andy
Disconnect battery power to unit e.g disconnect harness or remove car battery terminal for 1 minute then retest.
marchnz said:
Disconnect battery power to unit e.g disconnect harness or remove car battery terminal for 1 minute then retest.
Click to expand...
Click to collapse
I pulled all the cables. Left it for a couple of hours and reconnected everything and it was still the same. I then went into the Factory Settings and adjusted the System Volume in 'Voices' from 10 to 12 and after the reboot the sound returned. I then set the System Volume back to 10 and after reboot it continued to work. However got back in the car a few hours later and there is silence again. I tried messing with the System Volume in the Factory settings menu again, but this time there is no change and no sound..
I think I'll install the latest official ROM and MCU and see what happens. I think its a hardware issue, however its a bit tricky to diagnose...
Andy
I had the same problem with Malaysk v6.
I installed another rom an all is ok now, the problem disappeared.
fx200984 said:
I had the same problem with Malaysk v6.
I installed another rom an all is ok now, the problem disappeared.
Click to expand...
Click to collapse
I installed Malaysk's latest 7.3 version this morning - still no sound. Installed the latest factory image and performed a full wipe and still no sound. I guess I have a faulty unit?
There is a circuit board inline in the audio cable where the RCA's connect that I am not sure about?
Andy
I am having the same issue. the sound was working great and then... Poof. it stopped working.
https://www.amazon.com/gp/product/B07CPYGH9G/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1
Link above is the model head unit i bought. is there anyway to get it working again?
I did install an updated MCU per
https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
and it did not seem to change anything.
The screen works, all apps work, volume shows it is turning up and down but nothing out of the speakers. see video link of the issue below.
https://drive.google.com/file/d/1BNBbP6Y8RXq4kuH967RE9jpeUBYE_UdY/view?usp=drivesdk
Also, I do not have a factory amplifier.
Thanks everyone! any help would be Great!
Hi,
I just installed few days ago a PX5 MTCE_MX_V2.92_1 in my Peugeot 508 with JBL Sound system.
It went all almost ok (except the seller didn't understand I had to activate "With Amplifier" in the Factory settings, or I had absolutely no sound).
I have one problem : There is sound when I put radio, Ad2p music, usb stick music, phone call... but absolutely no sound when I try to read a CD or a DVD with the DVD app that came installed on the system.
I tried the MyTunerRadio app, and also no sound.
Do the stock apps (radio, bluetooth, usb stick) have something special to output audio differently, or am I missing something?
Does anyone also know any other app on the play store that can read the CD/DVD from inside the Unit?
Thanks
Hi again,
I received a new Canbus today from the seller, I don't understand why... and since we have trouble communicating, I'm asking you guys.
The one I got with the head unit, with for Peugeot 407 (I have a 508), the Android is starting, and all is working "more or less" ok.
The one I received today has two plugs, on each side of the decoder. And when I plug one side, well, Android is not turning on... which seems logical to me.
Any idea? do I need a new cable to connect the new decoder?
Thanks
Any Idea on this? I got a carplay dongle but also no sound...
do u solve it? i have 508 with JBL also..installed android device..no sound at all
Same here
Hi, same for me on my 508 with JBL amplifier.
Bluetooth Ad2p audio, radio and USB music works nice.
But no audio from CD, DVD, and the worse: from Bluetooth calls.
I am checking with the reseller and if can't help I'll ask for a refund. Or I hope you guys will get luckier and get an answer
Edit: I am under MTCE_MX_V2.91.
A weird thing is that if i want sound from basic apps, I first need to play music from USB, pause it, then I can hear the sound from the other app suddenly (but still not from CD, DVD, YouTube app). As the original poster wrote, there must be something with the way some apps output sound. I really hope it's easy to fix.
Solution
Guys, I have the solution!
Hopefully, this works for you too.
After a week of fighting about that with my seller (Autostereo), he finally provided me with a solution (I had opened dispute with agreed half refund so it motivated him I believe, to help me more...).
So, I updated my PX5 (manufacturer: MX / Witson - octacore, 4gb RAM) to a very last version "mx4_PX5_8.0(20181122)". The seller also sent me an update for the MCU but I didn't deploy it because it was working already with the PX5 upgrade. I give you here both files. Again, it was enough for me to just do the PX5 update; it all started to work suddenly (among other improvements), so I am more than satisfied.
At the time I am writing this post, there are 6 days left for the files: we.tl/t-A8ysf9ggAp EDIT: changed the link on Dec. 27, 2018
If needed, I can later upload them somewhere else (GDrive or something).
Can you send to me. I have the same problem. I would be very gratefull for your help.
@Perle123 check on the link I provided
?.Did you unzip them after download, or put them straight on to usb. How did you install.
Perle123 said:
.Did you unzip them after download, or put them straight on to usb. How did you install.
Click to expand...
Click to collapse
I could answer you "search on the forum" because that's what I had to do the first time, I had no clue how to update But it's easy:
1. Format a USB key to FAT32 file system (quick format is enough).
2. Unpack the mx4_PX5_8.0(20181122).zip
3. From the mx4_PX5_8.0(20181122).zip, copy the file update.zip (do not unpack it!) to the USB key.
4. Plug the USB key into your car unit, Android should recognize it straight and allow you to upgrade.
5. Click OK to upgrade, it will do the job (5 minutes for me), restart with updated PX5 (and sound working in all applications, DVD, CD, YouTube, DI.FM, etc.).
Note 1 : it asked me if I wanted to wipe data or not; I chose no.
Note 2: I recommend you do it with engine running in case the upgrade takes longer, to avoid safe consumption energy cut during the upgrade.
Note 3: I didn't have to reconfigure anything, not even CANBUS. I let it to amplifier mode "with amplifier".
Additional note for @ifoul: I have the same CANBUS as you exactly. I mean the original one, not the one the seller sent you again. And I think you should remain with the original one, it is configured for JBL. It is originally for Peugeot 408 (not 407 as you wrote), a model mostly sold only in China and that has similar commands as the 508; that's why it works with the 508.
Hope this helps!
Hi All,
Sorry for the long delay, turns out I didn't get thread notifications on my email.. so I forgot a bit about this thread.
It's funny because I also received two days ago (after long battling with seller DADAgps ? ) a new DMCU 3.00 MX and firmware from 20181122, and It's working correctly since two days.
I first did the DMCU upgrade, was not working, and then firmware upgrade ,and working.
So I can confirm it's definitely the Firmware.
the CarPlay dongle is finally useful (main reason why I bought the Android Head Unit).
If needed I can host the files online, just ask.
@slovinco, Yes, I stayed with the original Canbus, the other doesn't even start the android.
Also I have another Canbus on the way, they were sending it last week, before knowing about the new firmware.
ifoul said:
Hi All,
Sorry for the long delay, turns out I didn't get thread notifications on my email.. so I forgot a bit about this thread.
It's funny because I also received two days ago (after long battling with seller DADAgps ) a new DMCU 3.00 MX and firmware from 20181122, and It's working correctly since two days.
I first did the DMCU upgrade, was not working, and then firmware upgrade ,and working.
So I can confirm it's definitely the Firmware.
the CarPlay dongle is finally useful (main reason why I bought the Android Head Unit).
If needed I can host the files online, just ask.
@slovinco, Yes, I stayed with the original Canbus, the other doesn't even start the android.
Also I have another Canbus on the way, they were sending it last week, before knowing about the new firmware.
Click to expand...
Click to collapse
Perfect then Probably the manufacturer sent a FW upgrade to all sellers, seeing that a few os us have problems. Still, we must not be a lot with JBL and Android unit
Now finally we can fully enjoy this delicious unit.
Yes, not that many, for sure ?
From which country are you?
Now I need to install the camera that I received... that will be fun to put all the cables from the trunk to the Android!
ifoul said:
Yes, not that many, for sure
From which country are you?
Now I need to install the camera that I received... that will be fun to put all the cables from the trunk to the Android!
Click to expand...
Click to collapse
According to the photo of your radio app and the radio station names, maybe from the same country as you
I also installed rear camera for backup. It was not funny at all, especially taking down the plastic parts and putting them back. My hands still hurt. And also the wireless version is not very stable so I ordered cables to make it better. That means I'll have again to take down the plastic parts.
FYI, I bought this: aliexpress.com/item/For-Peugeot-301-308-408-508-2013-2014-Citroen-C5-C4-Car-CCD-Night-Vision-4LED/32598855986.html
But that's also another topic When I finish all this (I will also install headrest monitors), I will publish some articles on some Peugeot blog, because I quite enjoy doing this all!
Well, let's keep in English, in case it's useful for other people.
I ordered a similar one from amazon : https://www.amazon.fr/gp/product/B079NX178V/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1
because I found that the one I got for free from the aliexpress seller was hanging a bit too low. ( https://www.aliexpress.com/item/Wat...ml?spm=2114.10010108.1000023.9.6681277dXMa7AN )
Before you make your blog posts, do you maybe have some photos you took during install, to see how to remove the parts?
Small question regarding the camera.
Which cables did you take for the alimentation?
That was hard unboxing the trunk, but good thing I found all those PDFs from Peugeot https://www.forum-peugeot.com/Forum/threads/schema-pour-démontage-garniture-hayon-sw.34967/
Will answer you in private message as this is off topic
Thank you for your help. It worked for me too. The only thing that dosnt work is the front parking sensor and not all the steering wheel buttons. Can you assign the buttons in your meny, becourse i can not
sent to me also
Perle123 said:
Thank you for your help. It worked for me too. The only thing that dosnt work is the front parking sensor and not all the steering wheel buttons. Can you assign the buttons in your meny, becourse i can not
Click to expand...
Click to collapse
I don't have those issues, sorry for you. Make sure you have at least the proper canbus set up.
One thing though, the Wheel key study application does not work for me either. So even if all buttons work ok for me, I am not able to change their settings.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
scoponoc said:
sent to me also
Click to expand...
Click to collapse
You mean "send" maybe? In that case, how about a little "please" with that?
Anyway, read again my previous posts...
I have a one year old 7" Dasaita PX5 4GB RAM, Android 8, which performs flawlessly. Even the Blootooth and MIC volume level issue was solved in this unit, it has configured Bluetooth WD-BC6.
I wanted to upgrade to DSP, so instead of removing componentes and soldering wires , I just bought in Ali Express Dasaita Official Store the Dasaita MCU board with DSP:
https://es.aliexpress.com/item/32965198383.html?spm=a2g0s.9042311.0.0.6de363c0vGoD1p
After installation on new MCU board, everything is working fine, except Bluetooth, which is not working, if I go to FACTORY SETTINGS, (Password 126) I can select different Bluetooth Adapters, like: MD725, WQ_BC5, WQ_BC6, WQ_BC8, Parrot_FC6000T, SD-968, SD-BC6, SD-GT936, IVT-i145, SD-8350
But after trying several of them, Bluetooth is still not working. Dues anybody know which one I should select.
etulio said:
I have a one year old 7" Dasaita PX5 4GB RAM, Android 8, which performs flawlessly. Even the Blootooth and MIC volume level issue was solved in this unit, it has configured Bluetooth WD-BC6.
I wanted to upgrade to DSP, so instead of removing componentes and soldering wires , I just bought in Ali Express Dasaita Official Store the Dasaita MCU board with DSP:
https://es.aliexpress.com/item/32965198383.html?spm=a2g0s.9042311.0.0.6de363c0vGoD1p
After installation on new MCU board, everything is working fine, except Bluetooth, which is not working, if I go to FACTORY SETTINGS, (Password 126) I can select different Bluetooth Adapters, like: MD725, WQ_BC5, WQ_BC6, WQ_BC8, Parrot_FC6000T, SD-968, SD-BC6, SD-GT936, IVT-i145, SD-8350
But after trying several of them, Bluetooth is still not working. Dues anybody know which one I should select.
Click to expand...
Click to collapse
what BT module does your new unit have?
I did not check the Bluetooth module and I mounted the unit in the car. I took pictures of the board, but they do not show the BT model. So to check it physically I would have to disassembly again. To save this step, I was asking here just in case somebody has this MCU and knows the anser. But looks like I'll have to dissassembly.
Finally, I removed the new unit to check the BT, and it ios as follows:
The BT card in the "old" (one year old) board is:
Silk Marks in the back of the PCB: GOC-MD-705D
Paper label on top of QFP IC (Probably FW version and date) = A5BC6 1907
To have it working I selected in HU Factory Settings : WQ_BC6
The BT in the new MCU with DSP is smaller (shorter) and marks are:
Silk Marks in the back of the PCB: GOC-RF210 2019.04.27
There are no FW labels in the ICs on Top side of the PCB
What do I have to select to have it working?
In Factory configuration, the available BT optios are:
MD725
WQ_BC5
WQ_BC6
WQ_BC8
Parrot_FC6000T
SD-968
SD-BC6
SD-GT936
IVT-i145
SD-8350
I am attaching pictures of Old and New BT boards.
MCU has the latest FW 3.37, but PX5 has Android 8.0 one year old.
etulio said:
Finally, I removed the new unit to check the BT, and it ios as follows:
The BT card in the "old" (one year old) board is:
Silk Marks in the back of the PCB: GOC-MD-705D
Paper label on top of QFP IC (Probably FW version and date) = A5BC6 1907
To have it working I selected in HU Factory Settings : WQ_BC6
The BT in the new MCU with DSP is smaller (shorter) and marks are:
Silk Marks in the back of the PCB: GOC-RF210 2019.04.27
There are no FW labels in the ICs on Top side of the PCB
What do I have to select to have it working?
In Factory configuration, the available BT optios are:
MD725
WQ_BC5
WQ_BC6
WQ_BC8
Parrot_FC6000T
SD-968
SD-BC6
SD-GT936
IVT-i145
SD-8350
I am attaching pictures of Old and New BT boards.
MCU has the latest FW 3.37, but PX5 has Android 8.0 one year old.
Click to expand...
Click to collapse
Good post, an example of what information to post. Also good /must to know MCU version and that you have upgraded it to the latest available.
Unfortunately I still dont know what BT module you have - it might be a new model or compatible with one of the others lists, or it might require new firmware. Have you tried cycling through all of the MCU BT options, restarting in between? Also try reviewing logcats for BT detected type.
Hi, thank you for your help.
MCU PCB is the latest one: HA-D6100-MAIN VER 0.1 20190701, that integrates a DSP board. MCU FW version is the latest one from Dasaita, MCU 3.37. I tried cycling all MCU BT options with restarting in between, but without success. I do not know how to check Android BT logs.
I purchased this MCU PCB in Aliexpress Dasaita Official Store and I send messages asking for support, but I got no answer. I had to open a dispute to get an answer from Dasaita, now they say that they will send a new BT module, but if the real problem is the lack of support by MCU FW, this new module will not fix the issue.
BT Module and MCU PCB are very new, so probably they will release soon a new MCU FW that will support it, but the Dasaita support
Still not working
etulio said:
Still not working
Click to expand...
Click to collapse
Hello. I had a similar problem. Today I solved it. With the help of seller Dasaita on Aliexpress, I found out that the motherboard has a fresh Bluetooth chip installed. As the seller says installed RF210 Bluetooth 5.0 chip, which is not supported by Android 8. Therefore, all you need to do is install Recovery Android 9, then the firmware with Android 9, and then in the Factory Setting, in the Bluetooth settings on the first tab, select RF210 (it will be added to the list, on Android 8 it simply does not exist). That's all. Everything worked for me. The sound is better than it was on the old Bluetooth chip.
555sssaaa said:
Hello. I had a similar problem. Today I solved it. With the help of seller Dasaita on Aliexpress, I found out that the motherboard has a fresh Bluetooth chip installed. As the seller says installed RF210 Bluetooth 5.0 chip, which is not supported by Android 8. Therefore, all you need to do is install Recovery Android 9, then the firmware with Android 9, and then in the Factory Setting, in the Bluetooth settings on the first tab, select RF210 (it will be added to the list, on Android 8 it simply does not exist). That's all. Everything worked for me. The sound is better than it was on the old Bluetooth chip.
Click to expand...
Click to collapse
Thanks for taking the time, your explanation solves the puzzle. Good to know they finally have an updated BT option, wonder if they improved the code/drivers.
I will add links. I installed Recovery and Android 9 according to the instructions Hal9k. Hal9k, thank you very much!
Link to his Mod - h t t p://4pda.ru/forum/index.php?showtopic=973606&st=0#entry91199154
Link to Recovery for Android 9 - h t t p://4pda.ru/forum/index.php?showtopic=883219&st=24080#entry84508631
The link to the instructions for installing Recovery - h t t p://4pda.ru/forum/index.php?showtopic=891403&st=540#Spoil-77218289-3
Probably on this forum there is a description of the upgrade from Android 8 to Android 9. But I rarely come here. I just saw a problem similar to mine and want to share its solution. I hope this helps someone.
Hello,
I have the PX6 (Adroid 9) with the RF210 BT module, but it doesn't work at all. I've installed the latest MCU and the one before that (MCU 3.45 then MCU 3.53).
I also installed the latest firmware update (20200521). In the end I also installed Hal9k mod, and it still doesn't work.
Does your BT work?
RupOase said:
Hello,
I have the PX6 (Adroid 9) with the RF210 BT module, but it doesn't work at all. I've installed the latest MCU and the one before that (MCU 3.45 then MCU 3.53).
I also installed the latest firmware update (20200521). In the end I also installed Hal9k mod, and it still doesn't work.
Does your BT work?
Click to expand...
Click to collapse
No, it did not work. But I did not try to install Android 9, mine was at Android 8.
SD-BC6
Hi,
I have tried all the BT setting and for me finally working SD-BC6 (PX5 with Android 9 Malaysk mod) . Finally means that my mobile can connect and working and ODB2 module can connect and working. All others setting worked only for mobile or only for ODB2 or not worked at all.
Head unit: PX6 4/64 GB with Hal9k Android 9.
I have no separate connection for TPMS on the back of my unit, so I ordered a USB TPMS-receiver. The included app on a USB-stick is quite new (202002) but I have only problems with it. So I tried StoreBao from Play Store, the connection works better but I can't stop it from autostarting every time the unit wakes from sleep, tried the USB-settings in the Hal9k mod settings, but no difference.
In the factory settings I have six different choices for TPMS, which enables built in TPMS-apps, and they have nice design and are also translated to the language of the head unit. I have tried all six, restarted in between, and while I do not get any error messages, they just don't seem to recognize the USB-receiver. Maybe there is a "fix" for this?
I am very thankful for any help to get it working, or maybe if someone has another solution for his?
Dasaita makes one for their units and it plugs in directly to the back using a special connector and with use the installed TPMS App. So you can't use this, see Pic.
I have a USB app you could try. I got it when I got my first unit and works fine. I have had it on different units as well and no issues. If you still need it send me a PM.
bsavoir22 said:
Dasaita makes one for their units and it plugs in directly to the back using a special connector and with use the installed TPMS App. So you can't use this, see Pic.
I have a USB app you could try. I got it when I got my first unit and works fine. I have had it on different units as well and no issues. If you still need it send me a PM.
Click to expand...
Click to collapse
Thanks, I will send PM.
@bsavoir22 Hi. Do you know if it is possible to use another tpms system that is from another brand, such as this one, in a dasaita unit?
https://a.aliexpress.com/_BPa9Qx
Hi, I have a Chinese android head unit, I've fitted it in my van, all good apart from the one thing I wanted...Android Auto. Allegedly it's come with Android Auto installed. My phone and cable work fine in my car, and Auto connect to Android Auto, but not on this Android head unit I've fitted. I naively thought I could plug my phone in and it automatically start up but nothing happens, everything else on the head unit, I've worked out, and is fine. It's probably a set up problem, I'm wondering about an APL file, but I just don't know what to do and the instructions that came with it are not much help, I would appreciate a point in the right direction pls
Scrapman326 said:
Hi, I have a Chinese android head unit, I've fitted it in my van, all good apart from the one thing I wanted...Android Auto. Allegedly it's come with Android Auto installed. My phone and cable work fine in my car, and Auto connect to Android Auto, but not on this Android head unit I've fitted. I naively thought I could plug my phone in and it automatically start up but nothing happens, everything else on the head unit, I've worked out, and is fine. It's probably a set up problem, I'm wondering about an APL file, but I just don't know what to do and the instructions that came with it are not much help, I would appreciate a point in the right direction pls
Click to expand...
Click to collapse
I meant APK file, I've seen them but don't know what to do (if that is the issue)
Is it an FYT unit. Post Android system information including MCU version
@marchnz is right. Tell us what you have. There are a lot of different units.
Scrapman326 said:
I meant APK file, I've seen them but don't know what to do (if that is the issue)
Click to expand...
Click to collapse
It does not work automatically on these Chinese head utnits.
You first have to pair it to bluetooth.
Then you connect it via USB.
Then you start the z-link or carlink app, whatever it is called on your unit (and that is why we need to know what your unit is).
Then it should work.
surfer63 said:
@marchnz is right. Tell us what you have. There are a lot of different units.
It does not work automatically on these Chinese head utnits.
You first have to pair it to bluetooth.
Then you connect it via USB.
Then you start the z-link or carlink app, whatever it is called on your unit (and that is why we need to know what your unit is).
Then it should work.
Click to expand...
Click to collapse
Thanks, I’ll find the Android version and MCU (whatever that is), bare with me, thanks for the response, Bluetooth is paired, I can make calls via the head unit that way, and I connect via USB just as I do in my car, I haven’t seen a link for zlink or the android auto logo ?, all my phone does when I plug in is charge, there are two usb sockets on the back of the unit, 4 wire and five wire, my DAB aerial is plugged in the 4 wire and is working ok, my phone is in the five wire USB, I did swap them round , it made no difference, I’ll come back with MCU and Android version, thanks again, it’s a Brosmartek XRC-T3 06FuTe (that’s exactly what’s on the box) if that helps. I’ve found previously that purchases such as this come with very, very basic instructions, virtually zero.
If I search on your Brosmartek XRC-T3, the adds say you need to download the EasyConnect.apk. Did you do that?
surfer63 said:
@marchnz is right. Tell us what you have. There are a lot of different units.
It does not work automatically on these Chinese head utnits.
You first have to pair it to bluetooth.
Then you connect it via USB.
Then you start the z-link or carlink app, whatever it is called on your unit (and that is why we need to know what your unit is).
Then it should work.
Click to expand...
Click to collapse
Hi, I got it sorted, I hot spotted the unit off my phone and updated it, then I thought about z-link that you mentioned and recalled seeing Tlink5 ... I went into settings and changed from Google maps to the mysterious Tlink5 and hey presto...Tlink5 is required for Carplay and Android Auto. Everything is good now, such a shame that it's not in the instructions, then again what little instructions there was , was no help. Thanks for all your help, it was the Z-link mention that just got me wondering. "Tlink5"... who would have thought it.