Related
I have a PX3 from XRC with 7.1.2 which I flashed with Malaysk rom which worked great for about a week, then the radio totally died. No stations are found, auto search does not work and no audio from radio at all (not even static radio noice). I reflashed stock firmware and MCU but radio is still not working..
I have seen some videos stating the MCU config might be the problem in some way (YT video example) where the radio has been selected wrong or defaulted for some reason, the problem is that under "Radio" in "Factory Settings" I can't select any radio chip as in the video but only "YES" or "NO".
1. The "Factory Settings" option in settings, is this an APK or where are the options (not values!) / GUI stored? I tried flashing a old MCU for XRC but the options of only YES and NO persists so my assumption is that the GUI is stored in a read-only part of MCU (or XRC has removed them in all of their MCU updates).
2. Is there any other way of changing the MCU values with custom values? Another tool?
3. Anyone have any other idea what can be wrong and maybe how to fix it? The seller has stopped responding so I am on my own here..
Thanks for the help!
I had the same problem a few weeks ago. I solved it that way. Factory Settings (Code 126) Then to the rider radio, there the frequenz swap. I changed from Germany to China. Since then it is fine again. I hope that help you. Sorry for the bad Englisch . Google translate
volker64 said:
I had the same problem a few weeks ago. I solved it that way. Factory Settings (Code 126) Then to the rider radio, there the frequenz swap. I changed from Germany to China. Since then it is fine again. I hope that help you. Sorry for the bad Englisch . Google translate
Click to expand...
Click to collapse
Yeah I have already tried that, switching radio present country does not help. Changed to China, save, restart, reset, then same thing to EU. No difference..
If anyone has a XRC config file for Android 7.1.2 with working radio I would be really thankful if anyone could send it to me ?
vonbothmer said:
Yeah I have already tried that, switching radio present country does not help. Changed to China, save, restart, reset, then same thing to EU. No difference..
If anyone has a XRC config file for Android 7.1.2 with working radio I would be really thankful if anyone could send it to me ?
Click to expand...
Click to collapse
i will send you pictures from settings
tbmiso said:
i will send you pictures from settings
Click to expand...
Click to collapse
Please do but I can't think of anything that would work.
"Radio = YES"
"Radio region = EU"
=
No radio.
vonbothmer said:
yeah i have already tried that, switching radio present country does not help. Changed to china, save, restart, reset, then same thing to eu. No difference..
If anyone has a xrc config file for android 7.1.2 with working radio i would be really thankful if anyone could send it to me
Click to expand...
Click to collapse
View attachment 4360214
View attachment 4360215
View attachment 4360216
View attachment 4360217
View attachment 4360219
View attachment 4360220
View attachment 4360221
View attachment 4360222
tbmiso said:
View attachment 4360214
View attachment 4360215
View attachment 4360216
View attachment 4360217
Click to expand...
Click to collapse
vonbothmer said:
Please do but I can't think of anything that would work.
"Radio = YES"
"Radio region = EU"
=
No radio.
Click to expand...
Click to collapse
Here is a list of original factory settings for XRC. Now I am on xrc 2.71 (or 2.72...i dont remember) and new4_px3_7.1(20171102) and setting still works. I have never install Malaysk's firmwares - only the originals from the seller. I have only changed the tab 'VOICE' (to increase system sounds to 20)
View attachment XRC_Settings_Opel.rar
tbmiso said:
Here is a list of original factory settings for XRC. Now I am on xrc 2.71 (or 2.72...i dont remember) and new4_px3_7.1(20171102) and setting still works. I have never install Malaysk's firmwares - only the originals from the seller. I have only changed the tab 'VOICE' (to increase system sounds to 20)
View attachment 4360227
Click to expand...
Click to collapse
Thank you for the photos but my settings are almost identical.
I also use 2.71 MCU since yesterday and it still does not work. It won't search for radiostations and I hear no radio noice at all. The only thing I can think of is that it is a hardware failure..
The file "new4_px3_7.1" also works for XRC then?
vonbothmer said:
Thank you for the photos but my settings are almost identical.
I also use 2.71 MCU since yesterday and it still does not work. It won't search for radiostations and I hear no radio noice at all. The only thing I can think of is that it is a hardware failure..
The file "new4_px3_7.1" also works for XRC then?
Click to expand...
Click to collapse
Yes, all updates in past 4 months works ok ( only new4_px3_7.1......, not malaysk's....). I am always updating the mcu and px2 firmware. It looks like hardware error....
i have the exact same problem since my mcu update failure, i am using a special recovery MCU file created with Wadzio´s mtcdmcutool and the radio is not working
Kayhan 17# said:
i have the exact same problem since my mcu update failure, i am using a special recovery MCU file created with Wadzio´s mtcdmcutool and the radio is not working
Click to expand...
Click to collapse
Can you see it being detected in logcat/dmesg?
Hey mate,
i attached the logs, i dont know to look out for what keyword? =)
Kayhan 17# said:
Hey mate,
i attached the logs, i dont know to look out for what keyword? =)
Click to expand...
Click to collapse
Hi,
In DMESG. - [mtc @@@ radio chip not detected]
Wonder if there is a hardware or i2c issue?
Just looking at the schematic, the designers of these units use a novel supply arrangement with two linear voltage regulators - one 7809 9v reg. Feeding a 7805 5v regulator.
These regulators get hot. Suggest testing with a voltmeter to see if the Radio module is receiving +5v.
marchnz said:
Hi,
In DMESG. - [mtc @@@ radio chip not detected]
Wonder if there is a hardware or i2c issue?
Click to expand...
Click to collapse
marchnz said:
Just looking at the schematic, the designers of these units use a novel supply arrangement with two linear voltage regulators - one 7809 9v reg. Feeding a 7805 5v regulator.
These regulators get hot. Suggest testing with a voltmeter to see if the Radio module is receiving +5v.
Click to expand...
Click to collapse
Obvious keyword xD
and i was looking and thinking in a way like "MD725" etc.
However i will take a look at the Radio Module if its the area where the antenna goes in and come back here =)
Kayhan 17# said:
i have the exact same problem since my mcu update failure, i am using a special recovery MCU file created with Wadzio´s mtcdmcutool and the radio is not working
Click to expand...
Click to collapse
It looks like I have the same issue.
I bought a radio on Amazon
Android 7.1.2
Its a PX3 MCU version loaded now is MTCD_XRC_V2.54a_1 Jun 16 2017
I have two issues with the radio and im hoping to get some guidance from an expert.
The voice to text don;t work, I tried everything to get the mic to pickup but it dont. I even got an external mic to no avail.
If I do a bluetooth call people can hear me, I seen some others on this XDA forum but couldnt find a fix for it.
The other issue is the tuner / radio dont work. Just static and picks up nothing.
I contacted Amazon and they pointed me to the Hizpo website but there is no contact info.
I tried a couple of the downloads here to no avail. Any ideas on this issue?
Again, thanks so much for your time and help.
Anyone fixed this annoying radio crash? Same problem, radio dead. Played with different mcu versions, none of them respawned radio again... is there any tool to diagnose the comm to the radio module or manually select it from a list of tda's? Thanks for your input!
Same exact problem
katalinscrob said:
Anyone fixed this annoying radio crash? Same problem, radio dead. Played with different mcu versions, none of them respawned radio again... is there any tool to diagnose the comm to the radio module or manually select it from a list of tda's? Thanks for your input!
Click to expand...
Click to collapse
My radio is completely dead, no sound whatsoever on this px3.
The reason my radio did not work is/was that i had the USBtoUART Adapter plugged in and wired to MCU, and the RX/TX wires are the ones also going to Radio Module.
So when i unplug the USBtoUART Module, my radio works again, you guys may need to trace or possible bridge that 4700ohm resistor coming from MCU to Radio module test wise
EDIT: here i found my old picture and marked in green
Hi, I have an px5 xtrons and a problem with the clock on Android 8 (stock and malaysk rom) When I restart the car the unit have the old time of shutdown. (Unit connected to battery and no problem with android 6) Canbus is set on my model car and I have this problem, but if I set canbus model to none the clock works ok. I try to change canbus box but same issue. Anyone have a solution? Thanks
edit: even with the last malaysk android 6 rom same problem. Is it possible to solve putting downgrade version of clock app?
AlexRuhl said:
Hi, I have an px5 xtrons and a problem with the clock on Android 8 (stock and malaysk rom) When I restart the car the unit have the old time of shutdown. (Unit connected to battery and no problem with android 6) Canbus is set on my model car and I have this problem, but if I set canbus model to none the clock works ok. I try to change canbus box but same issue. Anyone have a solution? Thanks
edit: even with the last malaysk android 6 rom same problem. Is it possible to solve putting downgrade version of clock app?
Click to expand...
Click to collapse
I've had the same issue for probably the past year or so when I first started playing with custom roms. I'm pretty sure it happened after doing an MCU update. I have GS PX3 MTCD running hal9 rom. I've tried disabling network time etc but no difference.
When booting the headunit the time appears to be correct, then it changes to the wrong time, then after a few mins when either GPS or wifi has got a connection it corrects itself. I haven't tried changing the canbus model in factory settings as it's already correct.
I've found that the Clock app from Google works. All other including the stock clock keeps the shutoff time.
same problem here after upgrading Xtrons PX5 unit to Android 8.... it seems that somethings changed in CAN-Bus communication. Where bevore the car could write the correct time into the HU it's not possible anymore and the wrong (stucked) time get written into the Dashboard. The time will not synced when the HU is in standby (fastboot)... but will synced within 1 minute if i make a full boot.
dud89 said:
I've found that the Clock app from Google works. All other including the stock clock keeps the shutoff time.
Click to expand...
Click to collapse
hi, can you explain in more detail haw you managed to make clock work with google clock app?
i have installed it but no changes. the clock still shows old shutdown time
Hi I'm having the same issue with my xtrons head unit. Did anybody figure out a fix for this?
Hello,
I have the same problem. I have tried to add clock app to the whitelist, (mtce-utils) but It doesn't work. The canbuis I don't know is working correctly, Torque applicacion can not detect ODB unit and I can not view any value.
I set the clock to get the time from GPS only and I ve never had a problem.
typos1 said:
I set the clock to get the time from GPS only and I ve never had a problem.
Click to expand...
Click to collapse
Yes, but it only works if you have GPS connection (outdoor). If you are into garage there is no GPS udpate.
I have XTRON PX5 unit with Malaysk 8.0 and I have set the following things on whitelist:
com.android.settings
com.android.providers.settings
com.microtek.hctwidget
com.android.deskclock
com.cyanogenmod.lockclock
I have used mtce-utils ehitelist and Graser Daisata Xposed modules and none of them works.
I have connected the unit to the battery to avoid losing memory.
What can be the problem?
Thanks!
Same problem here :|
Android 6.0 clock also not working
As of 11/30/2018 after doing an MCU update 2.83 for Android 6.0, my clock also stopped syncing with the car's when turning it back on. It also display the last time right before the car was turned off.
Turning on/off GPS update or network update or setting the clock manually makes no difference and does not fix issue. Hope to see a solution to this.
If you revert back to the original MCU version, does the clock start working normally again? I'm assuming it would... I would just revert back to the original MCU version and be done with it. Unless, of course, there is some specific fix in the newer MCU that you needed?
greygoose82 said:
As of 11/30/2018 after doing an MCU update 2.83 for Android 6.0, my clock also stopped syncing with the car's when turning it back on. It also display the last time right before the car was turned off.
Turning on/off GPS update or network update or setting the clock manually makes no difference and does not fix issue. Hope to see a solution to this.
Click to expand...
Click to collapse
Did you export you MCU config before updating the MCU ?
I don't mind reverting back to the original MCU version I had but the problem I had with that one was my audio kept going back to sounding like mono instead of stereo each time I started the car. When I played video or music sound would only come out on my right door speakers. I kept having to do a factory reset each time to get it to come out at both sides.
I haven't browsed through the forum enough to see if anyone else experienced similar issues or if there were fixes for this.
greygoose82 said:
I don't mind reverting back to the original MCU version I had but the problem I had with that one was my audio kept going back to sounding like mono instead of stereo each time I started the car. When I played video or music sound would only come out on my right door speakers. I kept having to do a factory reset each time to get it to come out at both sides.
I haven't browsed through the forum enough to see if anyone else experienced similar issues or if there were fixes for this.
Click to expand...
Click to collapse
You could try the latest MCU, they may have sorted it out, you dont say what unit you have.
You could also try updating to Ore, it may also be fixed in the latest ROM.
Thanks I'll have to give it a try. My unit is the HA 2150 V600 with the px5 chip.
HI did anybody manage to sort the clock issue out on the headunits thanks
I have been having this same issue for a long time and hoping to find a fix for it.
I have tried the Google Clock app, that did not work.
I have updated my MCU from Ver 1.81 to 2.65 to 2.75 and now on 3.0.1. None of these MCU versions fix this issue.
I have also tried the V2.75_sp and no change (Did not think this would help with this issue, but tried it anyways)
On each of the MCU versions above, I have tired multiple roms (Stock, Malyask and Hal9K) and no luck fixing the problem.
The only time I have been able for this to work is if I have wifi enabled and connected to a Hotspot and Network time sync selected in the settings/Date&Time. With this configuration the time sync works everytime.
Now when the time does not Sync and if I open the GPS Plus app, the time displayed in the app is correct. So based on this, the only thing I can think of is that somehow the time from GPS is not being pushed to the clock app.
Guys I think I found the solution, at least it works in my case. What happens actually is that the unit is set to autosleep and not to shut it down. So when the unit goes to sleep, everything freezes including the clock time. When you put back the key contact, the unit goes back to live and all the apps start again from the moment when they went to sleep.
The solution which seems to work in my case, is to set the unit to shut down after I turn off the engine. Of course, it takes around a minute to turn on back when I put the contact key, but because the whole unit has been shut down, when it starts again it checks also the time clock and it syncs with either the GPS time or with the network provider time zone (depends what you have set). In my case I use the GPS time zone and with this workaround everything works well now.
It's not so much the MCU updates but the actual system update. Going backwards to the 20171214 system update will get the clock working fine again and should work with the most recent MCU update (my instance). With this version I didn't have to bother with changing the auto sleep or shutdown settings since it's an inconvenience to wait for a full minute for the unit to boot up. Also did not have to change GPS or network time sync either. I turn the key ON and the clock just works right away.
Ok,
So I got a on some recommendations here.
now what? Are there any custom roms I can use?
I would recommend read trough the forums...
And no, there are no modded Android 9 Roms at the moment.
You have to wait for Hal9k_ and Malaysk to come out with one when they are done.
LinkseD said:
I would recommend read trough the forums...
And no, there are no modded Android 9 Roms at the moment.
You have to wait for Hal9k_ and Malaysk to come out with one when they are done.
Click to expand...
Click to collapse
I've spent hours on the forums but there is so much out there its hard to get a handle on. the last unit I had was a nu3001 and was a bit more straight forward.
I'm not sure I care about android 9 if there is a ROM I can put on mine that is android 8 or whatever I don't care as long as it de-china-fied. I'll continue to look but was hoping for a quicker answer as I'm about to pull the trigger on buttoning up the car with wiring and dash....
Thanks!
Stormbringer! said:
I've spent hours on the forums but there is so much out there its hard to get a handle on. the last unit I had was a nu3001 and was a bit more straight forward.
I'm not sure I care about android 9 if there is a ROM I can put on mine that is android 8 or whatever I don't care as long as it de-china-fied. I'll continue to look but was hoping for a quicker answer as I'm about to pull the trigger on buttoning up the car with wiring and dash....
Thanks!
Click to expand...
Click to collapse
Your px6 came with android 9 anyway. There is no custom roms for px6 at the moment. With that said, android 9 is what I'm running (px5) and has been the most stable out of any modded ROM available from Hal9k or anyone else. You'll need to wait before a modded release is issued . They are being worked on.
For the time being, you could install FCC Launcher for A9. There's a thread in the forums here.
Sent from my SM-N920W8 using Tapatalk
Furthermore you could root your unit aswell. Even it is just possible by using SuperSu at the moment with Android 9.
Youll find the guides in the forums.
i have orderd one to, same as in first post.
can anyone say if tomtom or tomtom nds is working on this unit?
geldorf said:
i have orderd one to, same as in first post.
can anyone say if tomtom or tomtom nds is working on this unit?
Click to expand...
Click to collapse
I have the Dasita max6 as well, and can confirm: TomTom works perfectly.
S1W-brn said:
I have the Dasita max6 as well, and can confirm: TomTom works perfectly.
Click to expand...
Click to collapse
thanks.. yours is also px6 processor?
Yes, latest version px6
My Dasaita Px6 head unit has been working flawlessly for a little bit less than a month aside from a few disconnects with Android Auto.
However, today my head unit crashed 2x. Each time I heard a speaker popping distortion noise for a second and then the head unit restarted.
The only app that was running was Spotify with the unit connected to my phone's hot spot. Weather was about 60F so it wasn't a very hot day.
Has anyone encountered this before and if so, do you know what might be causing it?
rubberchickenmob said:
My Dasaita Px6 head unit has been working flawlessly for a little bit less than a month aside from a few disconnects with Android Auto.
However, today my head unit crashed 2x. Each time I heard a speaker popping distortion noise for a second and then the head unit restarted.
The only app that was running was Spotify with the unit connected to my phone's hot spot. Weather was about 60F so it wasn't a very hot day.
Has anyone encountered this before and if so, do you know what might be causing it?
Click to expand...
Click to collapse
could be a wiring issue or might need to factory reset the unit. I think everyone should factory reset as soon as they get the unit anyway.
lennylen said:
Your px6 came with android 9 anyway. There is no custom roms for px6 at the moment. With that said, android 9 is what I'm running (px5) and has been the most stable out of any modded ROM available from Hal9k or anyone else. You'll need to wait before a modded release is issued . They are being worked on.
For the time being, you could install FCC Launcher for A9. There's a thread in the forums here.
Sent from my SM-N920W8 using Tapatalk
Click to expand...
Click to collapse
I'm having the same issue and was blaming Malaysk mod for this...
Have you solved the issue? I will go back to stock and factory reset everything next week (is there a MCU factory reset option?).
I too have experienced the same exact problem and it happens once or twice a day. The UI freezes for a few seconds then there is a loud crackling sound coming from the speakers for another few seconds followed by a crash and reboot. It appears to happen randomly when I'm interacting with apps and more than likely is not heat related since it's been only a few degrees above freezing here and has happened only a few minutes after turning on my car. I've also had freezes where the UI and all buttons stop working but the radio keeps playing and only a forced reboot fixes it. I'm on Malaysk full mod and plan to go back to stock to do some troubleshooting and see if it's hardware or software-related.
jwallsuva said:
I too have experienced the same exact problem and it happens once or twice a day. The UI freezes for a few seconds then there is a loud crackling sound coming from the speakers for another few seconds followed by a crash and reboot. It appears to happen randomly when I'm interacting with apps and more than likely is not heat related since it's been only a few degrees above freezing here and has happened only a few minutes after turning on my car. I've also had freezes where the UI and all buttons stop working but the radio keeps playing and only a forced reboot fixes it. I'm on Malaysk full mod and plan to go back to stock to do some troubleshooting and see if it's hardware or software-related.
Click to expand...
Click to collapse
I tried going back to stock and changing many different MCU versions with the same exact issues you are describing: freezing or rebooting in the first few minutes after starting the car.
Today I had another new issue: I had one of the described freezes but after shutting down the car the display of Dasaita went black but the touch buttons remained on (LEDs on). I had to disassemble the HU to unplug the power cable... This is not a small bug anymore, this is a huge issue, I am trying to contact support with no answers. Did you find a solution or have any suggestion?
Do you have stock recovery? Do you know how to install stock recovery?
I also would like to factory reset MCU setting but I have no idea how to do it. Did you change any setting in factory settings menu? I'm worried that it could be something there.
The Android Attorney said:
could be a wiring issue or might need to factory reset the unit. I think everyone should factory reset as soon as they get the unit anyway.
Click to expand...
Click to collapse
I have the same issue sometimes my HU crashes with popping sound. I blame MCU 3.37 but i am not sure. Maybe i should re-update it without cfg settings files because i flashed it with exported MCU settings and put the cfg file next to the img file when i flashed the new MCU
matrixx1 said:
I have the same issue sometimes my HU crashes with popping sound. I blame MCU 3.37 but i am not sure. Maybe i should re-update it without cfg settings files because i flashed it with exported MCU settings and put the cfg file next to the img file when i flashed the new MCU
Click to expand...
Click to collapse
Where do you get the cfg file? I always flashed MCU without cfg file but maybe we could get a cfg file from a device with no issues and flash it alongside the MCU.
Frankk said:
Where do you get the cfg file? I always flashed MCU without cfg file but maybe we could get a cfg file from a device with no issues and flash it alongside the MCU.
Click to expand...
Click to collapse
You create it for your unit from factory config menu. Or document factory settings before updating MCU, right. Perhaps search for more info or read wiki.
marchnz said:
You create it for your unit from factory config menu. Or document factory settings before updating MCU, right. Perhaps search for more info or read wiki.
Click to expand...
Click to collapse
Thank you, I'm going to read it, but I assume that the cfg file you create from the factory settings menu is a backup of your current configuration, not a real clean factory configuration, am I right?
Frankk said:
Thank you, I'm going to read it, but I assume that the cfg file you create from the factory settings menu is a backup of your current configuration, not a real clean factory configuration, am I right?
Click to expand...
Click to collapse
Yes but actually the only thing i changed is SWC settings for Canbus so i can configure it manually.
matrixx1 said:
Yes but actually the only thing i changed is SWC settings for Canbus so i can configure it manually.
Click to expand...
Click to collapse
You have a Dasaita MAX6, right?
If yes, can you send me a dmcu.cfg file generated with your device?
If you changed only that setting it is pratically a stock configuration, I think I changed something more...
I'm not sure if it is the normal behaviour but when I update the MCU or if I wipe data from recovery or if I do a factory reset from system settings, the MCU settings are never changed. My custom configuration is never overwritten or deleted.
Thank you,
Francesco Comi
Hi,
i have installed carwebguru on my android car head unit 5 days ago, and today my backup camera stopped working, i have tryed an other android car head unit on my car and the backup camera was working normally, some technician said it could be a virus due to the download of the carwebguru, is there a solution for that ?
osmbhd said:
Hi,
i have installed carwebguru on my android car head unit 5 days ago, and today my backup camera stopped working, i have tryed an other android car head unit on my car and the backup camera was working normally, some technician said it could be a virus due to the download of the carwebguru, is there a solution for that ?
Click to expand...
Click to collapse
I have the same issue .. it worked fine with a specific Theme but when I started playing with themes etc.. it stopped working. I reset the Head unit and it worked agin till i messed with themes .. so I'm thinking that the app is "taking Over" the setting in the head unit that allows it to switch to the Backup Camera.. gonna play with it some more to see if I can n figure out what setting it is..
BTW.. I using a 1.3 Navi 600 Plus in a c300 (when listing a question, good to tell what your unit is and what car.. this can help to see if its specific to a car or head unit .. or the app )
FuzzyBalls30 said:
I have the same issue .. it worked fine with a specific Theme but when I started playing with themes etc.. it stopped working. I reset the Head unit and it worked agin till i messed with themes .. so I'm thinking that the app is "taking Over" the setting in the head unit that allows it to switch to the Backup Camera.. gonna play with it some more to see if I can n figure out what setting it is..
BTW.. I using a 1.3 Navi 600 Plus in a c300 (when listing a question, good to tell what your unit is and what car.. this can help to see if its specific to a car or head unit .. or the app )
Click to expand...
Click to collapse
figured out that it will only work with the "command" system so i created a shortcut to go back to main App which allows me to go to command system and thus see the cam.. but hope they allow it natively in their future updates.
Hi all of you.
I hope you can help me with this problem.
After debrick my unit, a seicane with android 10 - (MTCE_CHS_V3.67.1), Octa-Core Cortex [email protected] ghz, 4Gb Ram, specific for mini countryman R60, the rear view camera stopped working.
When I engage reverse gear, the screen turns black, but nothing is visible. For the rest, gps, bluetooth etc, all ok.
Android 9 is now mounted.
I don't think it's a wiring error because it always worked and the problem occurred after the debrick.
Thank you in advance for your suggestions.
if your screen turn to black it seems that the fuction of the camera is working... the signal you recieve from the its not something special. Just and old type of analog signal.. try to use an app which can open the video manually without the reverse year. Are you sure camera is working?
lagos911 said:
if your screen turn to black it seems that the fuction of the camera is working... the signal you recieve from the its not something special. Just and old type of analog signal.. try to use an app which can open the video manually without the reverse year. Are you sure camera is working?
Click to expand...
Click to collapse
Hi, thanks for your reply.
I agree perfectly with you. It is a hardware function that does not require any particular configuration. Unfortunately my car is a mini countryman. it is particularly long and complicated to disassemble to access the wiring.
I cannot rule out a wired malfunction but it seems very unlikely to me. the malfunction occurred when the radio was reset after the debrick.
IMHO : Check (re-write) your MTCE_CHS_V3.67.1, and, eventually upgrade !
LE : Unfortunately I don't see a higher version... (https://disk.yandex.com/d/umCvHqCDzHccr/MCU for MTCD, MTCE, MTCP, Intel Sofia3g/CHS)
Contact the seller !
fratellos said:
IMHO : Check (re-write) your MTCE_CHS_V3.67.1, and, eventually upgrade !
LE : Unfortunately I don't see a higher version... (https://disk.yandex.com/d/umCvHqCDzHccr/MCU for MTCD, MTCE, MTCP, Intel Sofia3g/CHS)
Contact the seller !
Click to expand...
Click to collapse
Ok. I had already thought about this solution, but I have not found V3.67.1
Can I install 3.57?
Pamigianleo62 said:
Ok. I had already thought about this solution, but I have not found V3.67.1
Can I install 3.57?
Click to expand...
Click to collapse
If the 3.57 is also CHS, you can install.
Ati_gangster said:
If the 3.57 is also CHS, you can install.
Click to expand...
Click to collapse
As I am inexperienced with these car radios and would like to avoid disasters, is the MCU common to many radio platforms?
MCU for MTCD, MTCE, MTCP, Intel Sofia3g
Hello everybody.
always concerning my problem I realized that in the factory settings (those protected by the pin) before the brick appeared a voice of the microphone, now it has disappeared. Is it possible to understand why this difference considering that it is a function of the MCU?
Thanks for your collaboration.
Have you installed the older MCU?
Thanks for the reply. Not yet.
I sent a request for assistance to Seicane, the manufacturer of my radio, asking for the firmware for a total reset.
Still no answer, unfortunately.
He waited a little longer and if they don't respond I will install the version you recommended.
I have teh same problem after debrick. Upgrade to Android 10 solved the problem for me, so it's problem with firmware.
hali8 said:
I have teh same problem after debrick. Upgrade to Android 10 solved the problem for me, so it's problem with firmware.
Click to expand...
Click to collapse
Wow fantastic.
I get active for this and let you know.
Could you please give me the link to proceed with the update?
Unfortunately I am not very experienced with android auto and I am always terrified of causing disasters.
Thanks in advance
hali8 said:
I have teh same problem after debrick. Upgrade to Android 10 solved the problem for me, so it's problem with firmware.
Click to expand...
Click to collapse
I solved.
As you indicated I have updated to android 10 and everything works.
Thanks