My MTCD Xtrons runnig stock firmware (android 9) randomly siwtches off (clean shut down of the Android system - it closes all the apps before it goes to sleep, etc.) and stays switched off for anything between 5 seconds and few hours and then powers on again on its own. It does it around once per week. When it's off it does not react to any buttons including the reset button. I've tried installing Hal9k firmware but the unit behaved in the same way, so i went back to stock. I have MCU v3.44.
Any ideas what might be causing it?
Much appreciated.
cascader said:
My MTCD Xtrons runnig stock firmware (android 9) randomly siwtches off (clean shut down of the Android system - it closes all the apps before it goes to sleep, etc.) and stays switched off for anything between 5 seconds and few hours and then powers on again on its own. It does it around once per week. When it's off it does not react to any buttons including the reset button. I've tried installing Hal9k firmware but the unit behaved in the same way, so i went back to stock. I have MCU v3.44.
Any ideas what might be causing it?
Much appreciated.
Click to expand...
Click to collapse
Some things needed for context;
- Is it canbus connected
- Post MCU version
- Steps taken to investigate / resolve
- What reseller suggests when contacted for support.
Related
Hello Guys,
I really need some insight on this problem:
I have a KLD (http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151.html) unit for some time now, but since September it wasn't in my car because I was preparing an audio upgrade. As one of the last steps I've checked out the HU and I wanted to upgrade to the latest MCU&FW, but the unit wouldn't turn on. Since it's on my "workbench" I've checked the cables, fuse, the external PSU, everything i could, but it did not help. The unit worked flawlessly in the car and on the workbench 2 months ago. Nothing changed. Now it won't turn on, not even the fan at the back of the unit. The screen and the button backlights are also off.
The one confusing part is, when I push the power button with reset for a few seconds, the unit comes to life, and goes into recovery! I can flash a ROM, clear the cache, etc., but when I reboot the unit from the menu, it turns off, then the button backlights flash once, but nothing else happens. The unit stays turned off.
So far I've checked:
- Fuse
- External PSU
- Power button
- Replaced the SOM (The unit is RK3066 originally, I'm using it with RK3188)
- Tried different ROMs
- Disconnected the DVD drive
Nothing helped. I can get into recovery, but I can't boot the unit, no matter what SOM (or what ROM) I use. I would really appreciate some help, because I ran out of ideas.
Thanks in advence!
LFMF
Ok, the big conclusion is to use the multimeter first. Magically, ACC was not even close to 12v. Switched to another PSU, everything works.
HeuFei based Headunit, no touch, no buttons.
Everything has been fine, no updates, no changes.
Unit was from Pumpkin, it's a RK3066 based unit with KDL
I get in tonight to drive home form work, and after bootup I noticed none of my SWC worked, buttons on the unit itself don't seem to work, and the touch screen is unresponsive.
The unit boots, I see things happening - just no controls.
Reset button works, Power button works - I can get into recovery mode, but cannot navigate with volume have to use power, tried doing a restore, same thing.
any ideas?
Have you tried disconnecting the battery to remove it from a power source?
grinthock said:
Everything has been fine, no updates, no changes.
Unit was from Pumpkin, it's a RK3066 based unit with KDL
I get in tonight to drive home form work, and after bootup I noticed none of my SWC worked, buttons on the unit itself don't seem to work, and the touch screen is unresponsive.
The unit boots, I see things happening - just no controls.
Reset button works, Power button works - I can get into recovery mode, but cannot navigate with volume have to use power, tried doing a restore, same thing.
any ideas?
Click to expand...
Click to collapse
Hi, i'm experiencing the same problem. I updated my HuiFei unit yesterday to MCU: MCU_KGL_2.78 and ROM: update_4_4_4_800X480_RK3066_29_MAL_27_10_2015. Everything was working fine and did all my personalization. I was able to turn the unit on and off and use all the buttons. Later the day when i used it again all the buttons as well as the screen was unresponsive. The only the power button can turn the screen on and off. I also tried to boot into recovery, but no luck...
I'll try disconnecting the battery and see if it works.
---------- Post added at 12:23 PM ---------- Previous post was at 12:01 PM ----------
BiliTheAxe said:
Have you tried disconnecting the battery to remove it from a power source?
Click to expand...
Click to collapse
I just tried disconnecting the battery, left it for a minute or so and connected it again then turned on the unit. No luck, the screen and buttons are still not responsive...
Hein3G said:
Hi, i'm experiencing the same problem. I updated my HuiFei unit yesterday to MCU: MCU_KGL_2.78 and ROM: update_4_4_4_800X480_RK3066_29_MAL_27_10_2015. Everything was working fine and did all my personalization. I was able to turn the unit on and off and use all the buttons. Later the day when i used it again all the buttons as well as the screen was unresponsive. The only the power button can turn the screen on and off. I also tried to boot into recovery, but no luck...
I'll try disconnecting the battery and see if it works.
---------- Post added at 12:23 PM ---------- Previous post was at 12:01 PM ----------
I just tried disconnecting the battery, left it for a minute or so and connected it again then turned on the unit. No luck, the screen and buttons are still not responsive...
Click to expand...
Click to collapse
You may have updated to the wrong MCU file. They are not interchangeable between manufacturers.
BiliTheAxe said:
You may have updated to the wrong MCU file. They are not interchangeable between manufacturers.
Click to expand...
Click to collapse
Hi have a KGL HU and after the update everything worked fine even restarted the HU a few times without any issues... When i started the unit up again after a few hours, that's when i experienced the no response issue.
I have tried the steps to get into recovery -> Press reset + Power for a few seconds and then release reset... but it just starts up normally
Hein3G said:
Hi have a KGL HU and after the update everything worked fine even restarted the HU a few times without any issues... When i started the unit up again after a few hours, that's when i experienced the no response issue.
I have tried the steps to get into recovery -> Press reset + Power for a few seconds and then release reset... but it just starts up normally
Click to expand...
Click to collapse
I managed to boot into recovery after a few tries and reinstalled the MCU and ROM and the screen and buttons work again. The GPS button is mapped for the "back" function for some reason, but that might be some app changing the assigned function.
So I pulled the power on mine -- no dice.
I want to reflash the MCU, but I can't get into the unit to find out which MCU I have -- catch 22!
ok well, a little progress. I remembered reading elsewhere that someone plugged in a keyboard, so I plugged in a MPC keyboard/trackball combo into the unit -- and now i have a mouse, that's useful.. So I was able to check, it says I have KLD -- but is that what's flashed, or is that what I have....
I tried to assign SWC keys, just to see if it was recognizing them - no dice....
I am also installing fresh firmware and fresh MCU, see what happens.
Well, success.... reloaded KLD mcu.img with latest, and latest firmware... All working..
Keep things simple with your software.. Keep it classy.
Ok, I installed the new Joying 10.1" VW head unit in my car the other day, and it's working pretty good, however I'm having a couple of issues. I installed Malaysk's ROM onto it and still working through setting everything up the way I want it, but I'm having 2 issues I can't figure out, and they are driving me nuts.
Wifi: Whenever the unit reboots, the WiFi is disabled. I have to manually re-enable it every time.
12-Hour Time: Every time the unit reboots, the time reverts back to 24-hour time.
Anyone know what I can do to fix these issues? Getting rather annoying having to switch them every time the unit boots up.
Thanks
bwhite757 said:
Anyone know what I can do to fix these issues? Getting rather annoying having to switch them every time the unit boots up.
Thanks
Click to expand...
Click to collapse
Sounds like the 12+ and ACC connections are swapped.
Thanks for the reply, but the unit is switched on Via Can-Bus. There is no ACC wire. It powers on and off just fine when I start and shut off the car.
bwhite757 said:
Thanks for the reply, but the unit is switched on Via Can-Bus. There is no ACC wire. It powers on and off just fine when I start and shut off the car.
Click to expand...
Click to collapse
Then your 12+ is not constant.
Yep it is, verified with a volt meter, 12volt constant stays hot, even went out and checked after my car had been off for over an hour just to make sure... I shouldn't have said there is no ACC wire, ACC is supplied by the Can-Bus adapter.
As far as the wiring goes, I'm confident all of that is wired correctly. I used to install car stereos as a job for 5 years, and this is the 3rd head unit in this vehicle. I'm an Android enthusiast, and definitely know my way around the system, even though this is my 1st Android head unit I've dealt with.
The 12-Hour time issue was happening before I installed the ROM on it, but the WiFi issue didn't start until after I installed the ROM.
Ok, thats a puzzler then. My observations have been that wi-fi will turn off and 24 hour set every time power is lost on the 12+ line. It seems independent of rom used, would happen on the stock rom and on a older version of Malaysk's I'm currently using.
Well, for whatever reason today the settings never reverted back. I don't remember changing anything, but I did go through every single menu and sub menu in the settings section. Oh well, fingers crossed everything stays set, because this head unit is perfect for me now!
I have the same issue + no bluetooth. I have a YINUO 1024x600 Quad-Core RK3188 and it's doing the WIFI OFF, 24 HR, NO BT.
Hi,
I recently updated my rk3188 MTCB-YM from 4.4.4 to dsa’s 5.1.1 ROM. All went well with the update. After a couple of weeks, I found the ROM was starting to run quite slow and was almost unusable - except if you kept the unit on for a long time. It was like it was loading a lot of things for a long time and once that was done, it became responsive immediately instead of being delayed to button presses etc.
So I decided to boot into recovery and do a wipe all/factory reset. My unit does not have physical buttons or a gps sd card slot. None of the usual boot into recovery options work so I use an app to reboot into recovery. I started this app and chose the correct option. At the time I did this, the radio was playing. The screen went black and the stayed like that with the radio still playing. The lights on the unit are still on but nothing works - no response at all. I have turned the car off and left it off overnight. When I turn the car back on, the radio starts playing again immediately. (This would normally take a little time while it boots up, so the unit is obviously stuck). As I cannot do any of the reset/recovery options - is there anything I can do? I haven’t removed the unit to see if it is possible to short the pins as I don’t have access to a bench power supply and have limited skills. But I will try this if there are no other options. I also haven’t removed the battery terminal to cut power yet. That was going to be my next test. But wanted to see if there was any advice before I do this.
EDIT: I took the plunge and disconnected the battery, and the unit started back up again.
Hi All,
I recently updated MCU and firmware to latest firmware on Dasaita's site:
MCU V3.69c：https://www.sendspace.com/pro/dl/pf1zz4
Android 10 Update PX6 HA3_rk3399_10.0_ota(20201217) https://www.sendspace.com/pro/dl/rbsz9o
Since update, I have a strange problem. When I turn the accessory to off, the volume bar appears and increases 5 levels.
Example: volume start at 5, turn acc off, volume increases to 10 before power off. Turn acc back on (volume at 10), turn acc off, volume increases to 15 before power off.
My fear is that, should I have music at a high volume when I turn off the vehicle and turn the vehicle back on, I could see voice coils flying past my head.
Since it is an open cockpit (no roof) vehicle, I do tend to have volume very loud.
I have checked factory settings for boot volume - it is turned off.
Thank for any input.
Well, it goes from bad to worse.
I contacted Dasaita and told them I had updated to the MCU and firmware listed in the post above. Both are what is listed as current firmware on Dasaita's website.
They emailed back and said I had incorrect firmware for the Max10. They gave me the following links (direct copy from email):
PX6 10.0 HA3_rk3399_10.0_ota(20201214) https://www.sendspace.com/pro/dl/f3gyol
PX6 android 10 （1113）
https://drive.google.com/file/d/1rO-wBK8rvVZsXT_5IjN3MyuMY00utZZX/view?usp=sharing
So.....
I updated with the first file.
Now the unit has different problems.
Upon removing accessory power, the unit auto launches the default navigation app, and then powers down.
On power up, the default navigation auto launches, followed by an error message that "Zlink has stopped".
This happens EVERY power up.
So, I tried to update with the second file. Update fails claiming that the unit cannot downgrade to this file.
This sucks for me. I told a friend how great my system works and this unit was actually going to be installed in his vehicle tomorrow.
Any ideas?
Try disabling zlink.
I tried everything.
Emailed Dasaita for a bit of help as the problem only happens on the new unit.
I updated both units with the same firmware/mcu. My radio had no problems (been installed for 6 months).
This new radio continues to be a problem.
I re-updated with the same firmware. Several times as each time seamed to give new problems. SDK errors, wouldn't launch play store.
Each time I did select to wipe from the upgrade menu.
Currently, initial power and boot up appears fine.
When I remove accessory, the unit auto-launches the default navigation program prior to going to sleep. If I apply acc power within 30 seconds, the unit powers on and auto-launches Zlink. If I wait more than 30 seconds for full power off, apply acc power, the unit boots and auto launches navigation as that was the last active program.
Is it possible to completely reformat and load the update from scratch?
It just seems odd since I have 2 identical units on the same firmware yet only one is doing this.
mpj220 said:
I tried everything.
Emailed Dasaita for a bit of help as the problem only happens on the new unit.
I updated both units with the same firmware/mcu. My radio had no problems (been installed for 6 months).
This new radio continues to be a problem.
I re-updated with the same firmware. Several times as each time seamed to give new problems. SDK errors, wouldn't launch play store.
Each time I did select to wipe from the upgrade menu.
Currently, initial power and boot up appears fine.
When I remove accessory, the unit auto-launches the default navigation program prior to going to sleep. If I apply acc power within 30 seconds, the unit powers on and auto-launches Zlink. If I wait more than 30 seconds for full power off, apply acc power, the unit boots and auto launches navigation as that was the last active program.
Is it possible to completely reformat and load the update from scratch?
It just seems odd since I have 2 identical units on the same firmware yet only one is doing this.
Click to expand...
Click to collapse
If you update android there is an option „wipe...“ maybe you check this.
Apollon2 said:
If you update android there is an option „wipe...“ maybe you check this.
Click to expand...
Click to collapse
"wipe data" was selected with each update.
I ended up returning the unit for a new one.
No troubles with the new one.