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!
I can`t find a working SDVC app for my PX5 GS unit. It is my second unit because the first has had a fault and was exchanged. On the first unit I used Graser´s Dasaita tool for volume control. On the new unit that isn´t working anymore and also MyMTCService does not recognise the unit as MTCD and so the sound control is not working.
The only thing that is different to the old unit are the connectors. The GPS connector uses now a Fakra plug, but I don´t think that this is a problem since all other GPS apps are working normally.
Neither Malaysk, the original GS ROM nor a HA ROM is working. I've tried also different MCU's.
Here you can see the problem with Grasers Dasaita tool. I am not driving and not changing the volume level: https://youtu.be/aT0asijim5g @Graser maybe you can help me?
Hi All
Thanks for any help you can give with this, i have been unable to find this problem mentioned elsewhere.
I have changed the mcu on my px3 1gb rk3188 head unit as i had been having trouble with the steering wheel controls being intermittent over the canbus.
I am sure my original was a kgl mcu but if i install that one and a few others i get a random beep every few seconds.
I have just tried the newest www and mx mcus and i also get the beep on these
The last mcu i had without the beep i think it was an mx one had no option for disabling the reversing camera
i was hoping to try hals nougat firmware however this requires a newish mcu.
Is there a fairly generic brand mcu which is likely to be a winner for me please or is there anything i can do to stop the random beeping please?
Also is there any way to make my steering wheel controls less intermittent please they will work fine for a while and then stop completely and same in the car diagnostics app so i assume it gets bored listening to the canbus and gives up.
it is a 2011 seat ibiza ecomotive.
Thanks
Kamcel
It could be the spring cable in the steering wheel if I understand correctly. My cable is going/intermittent but reprogrammed the buttons there are 2 sets for each button, I think it's a resistance issue, but it appears to be working for me.
Sent from my Z981 using Tapatalk
Hey, I have an Audi A3 2012, equipped with a Wondefoo PX5 head unit aswell as a canbus decoder.
Before installing a reverse camera, everytime i switched to reverse it automatically went to "Reverse Mode" And AVIN.apk popped out (even though it was just stating "No signal" - because no camera was installed).
I have installed a reverse camera, gave it 12V and connected the RCA cable directly to the "CCD AVIN" input from the HeadUnit - without connecting the red power cable from the RCA cable to anything. (It recognised reverse automatically via the canbus i guess).
Everything worked great for I think 4 months, and this week without any notice, when i switched to reverse simply nothing happaned.
Since then the headunit simply won't automatically go to reverse mode.
Nothing was changed, so I have no clue what to do..
Someone who expirienced something like this? The CanBus decoder still works great except the reverse mode (as if it's unplugged the system won't start on because it doesn't get any signal that the ACC is on without the decoder).
This is the HeadUnit I have, with Android 8.0 4GB of RAM and 32GB internal memory: https://he.aliexpress.com/item/Andr...215.html?spm=a2g0s.9042311.0.0.27424c4dT5D6nS
Anyone?
Hi,
Did you find a solution? I'm having the same problem
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