Hello,
i have a major (hopefully minor) Problem:
My Unit MTCD or E probably GS from KANOR, like this one with other backside
https://de.aliexpress.com/item/32842109142.html?spm=a2g0o.productlist.0.0.11677d2dA88rUK&algo_pvid=edfcdfee-6506-42f2-a19d-be2ab538f188&algo_expid=edfcdfee-6506-42f2-a19d-be2ab538f188-0&btsid=e523b817-3495-4acd-960d-716f43a94e62&ws_ab_test=searchweb0_0,searchweb201602_8,searchweb201603_52
Model Name:
KN-U702C
Bought it in 2019, it was working flawlessly....
I now want to sell my car with the hu, and went into the factory settings with the pw: "126" and resetted the hu ("Tablet is restarting" was shown on the display)
After that, no reboot from the hu.
Screen remained black.
I pushed the Reset button in the lower left corner, nothing.
I held down the Power (volume knob) Button for more than 10 seconds.... Buttons are flashing 3 times....nothing. Screen remains black.
I disconnected the hu fron the car, waited overnight, connected it again, but nothing, no boot sequence is shown, screen remains black.
Can somebody tell me what to do to get this unit working again?
Best regards from always rainy, gool old germany
I can not remember exactly but this happened to me. I followed the information in his signature from this post somehow.
Blank screen and confused
I have a px5 radio packed as kanor. It is a px5(1024x600) running 8.0 with mtce_kld_v3.01_1 and has physical buttons. It was running ok. I went into factory settings and changed the led color and changed the mapping on one button. It said it...
forum.xda-developers.com
Related
All the buttons, including the volume knob stop working.
It has happened several times on my android 5.1.1/mtcd/joying unit.
When it happens the boot process is strange. It spends a while displaying the car logo, then it displays the desktop for a second or so and then it displays the car logo again. It sort of looks like it boots twice.
Wiping the dalvik cache does not fix the problem. I have to factory reset or wipe everything from recovery to get the buttons working again.
I am currently using malaysk rom for MTCD units but I had exactly the same issue on the stock rom.
I think the problem is related to autostarting apps on reboot.
Today it happened after I installed the Sygic speed camera/traffic alert app. Everything worked fine for a while, until I chose to auto start it (from the settings menu inside the Sygic app), rebooted, and the buttons no longer worked.
To check if the autostart option really caused the problem I installed the app again, chose to auto start from the settings inside the app, and the same thing happened. Buttons no longer worked.
The issue is not specific to Sygic, as I have had the same issue with other apps.
Now I use tasker to autostart the app. It has survived a few reboots. I hope it lasts.
Does anyone understand the boot process on these units well enough to help debug it further?
It would be nice if I could fix it the next time it happens, instead of having to wipe/reinstall everything.
It seemed to be completely random for me... and it stopped happening as randomly as it started.
I posted the process I went through to get them back (reboot, reboot to recovery, reboot again, etc) but very intermittent.
I experience this whenever I reboot from the power icon in the taskbar. It seems to have started after upgrading to Malaysk's version 4. I have verified this on two Joying units. My workaround is to reboot with the reset button when I have to.
I have not had any apps autostart since the last time it happened, but the buttons stopped working again a few days later, and the "double boot" came back also. The reset button did not help.
A factory reset from the settings menu made the buttons work again.
I was using the latest joying rom and MCU. Spotify, iGo navigation (from joying) and the TomTom speed camera app were the only "extras" installed if I remember correctly.
I am about to give up on the (JY-UL135) head unit now. Unless someone has suggestions on what to do.
xdamember2 said:
I experience this whenever I reboot from the power icon in the taskbar. It seems to have started after upgrading to Malaysk's version 4. I have verified this on two Joying units. My workaround is to reboot with the reset button when I have to.
Click to expand...
Click to collapse
xdamember2, i think you are right. Power icon in the task bar is the root of evil.
Today i've had the same experience. But with the buttons, the sound had also disappeared. Pushing hardware reset button had fixed the problem.
So I suggest to remove power icon from the task bar.
This happened to me yesterday, but as well as buttons/steering wheel control, all sound output stopped working! No radio, music or navigation sounds. Tried a reboot, but in the end only a factory reset did the trick as specified previously.
Very frustrating!
This happened to me again today for the second time. While driving the screen turned to white/black static like moving artifacts and the sound cut off. After holding the power button to reset the buttons are not working. I'll update to Malaysk's Rom v5 now but looks like my apps are wiped again...
i've been on v5 for the past few days and i haven't witnessed this behavior.
Any luck with the buttons and sound stop working? It`s the same with version 6 of this ROM which i like way better then the stock ROM. I`v noticed that any other reboot except the standard one, when the HU shuts off by it self, will make buttons unusable and no sound. The first time it happen to me was when i did some changes in the "factory settings" menu that needed to reboot the device. The only way i managed to fix it was to do a factory reset. Tomorrow will try to flash the same ROM (V6) without wiping to see if this will fix it,because they don`t work again now after rebooting from the power icon . Lets hope someone finds solution for this annoying issue.
MY FIX for Volume knob not working on Android Head Unit
Hi All
I updated my generic Ford Focus PX5 android head unit, and after much swearing and reading on here, I still was unable to fix the top left volume and top right tuning rotary knobs as they had stopped responding.
Eventually i started mucking about with Factory Settings and in the "OTHER" section I looked at "Knob Mode"
Experimenting with the various settings I eventually determined that for me, "2 10K/20K ADC Ports" works. I now have fully functioning controls.
I hope this is of some help to you guys!
I had been fooling with the settings of my Android head unit and some days later realized my volume knob wasn't working. That knob was a big factor in my purchase of this unit. After fooling with a dozen or more logical sounding settings, I happened upon the setting which had to do with 'Key lights'. Here's the fix:
From 'Settings' go to 'Factory Settings' and enter code 8888. Go to 'Key Light Settings'. On 'please open the debug button lamps' press 'OK", slide the screen up and turn off 'whether to turn on the colorful lights'. Back on out and the volume should now be working. Hope this helps
Sdgz said:
I had been fooling with the settings of my Android head unit and some days later realized my volume knob wasn't working. That knob was a big factor in my purchase of this unit. After fooling with a dozen or more logical sounding settings, I happened upon the setting which had to do with 'Key lights'. Here's the fix:
From 'Settings' go to 'Factory Settings' and enter code 8888. Go to 'Key Light Settings'. On 'please open the debug button lamps' press 'OK", slide the screen up and turn off 'whether to turn on the colorful lights'. Back on out and the volume should now be working. Hope this helps
Click to expand...
Click to collapse
I recently bought a new android head unit. All are working well except the original volume knob of the car. Sometimes i must turn it 4-5 clicks for the volume to move 1 click, and other times i may turn it 10-15 clicks and the volume does not respond at all. This is very frustrating! I found a solution on youtube which says factory settings-other- and uncheck the wheel3 option, but my head unit doesn't have this option at all. I hope your solution will help me!
Update : I searched for this solution you mentioned but this option does not exist in my factory settings with 8888 code. Only car logo. I dont know what to do....
Do you know how can I enter recovery / reinstall firmware on a Winston PX3 without any buttons? just reset.
The unit is made of Opel Insignia and uses the car button. The power power button only switches the screen on / off and nothing more.
Is stuck at the lollipop logo without anything else.
I tried all the method here... reset, keyboard without any luck
RK tools not working since is not seen by the laptop
Bootable SD, same... no luck.
Thanks in advance
I also want to know that, never find solutions at this time.
I have same car with same head unit, do you have a good radio reception?
Read here and tell us if it works ... on my witson px3 android 5.1.1 works this procedure to enter in recovery... good lock
bcostea said:
Do you know how can I enter recovery / reinstall firmware on a Winston PX3 without any buttons? just reset.
The unit is made of Opel Insignia and uses the car button. The power power button only switches the screen on / off and nothing more.
Is stuck at the lollipop logo without anything else.
I tried all the method here... reset, keyboard without any luck
RK tools not working since is not seen by the laptop
Bootable SD, same... no luck.
Thanks in advance
Click to expand...
Click to collapse
Solved after taking out the unit.
The trick with power button does not work since on Insignia access to the power radio buttons is via canbus interface. Power button only switches screen on and off when not in Android... nothing more.
So solution:
Is easier if the unit is not mounted in the car, I have not tried to enter recovery after a reset, but maybe I will try sometime.
1. Disconnected all power from the unit... ACC & BAT disconnected
2. Prepared 12V power supply with on negative and two positive connectors
3. Connected negative to GND & one positive to BAT
4. Connected USB keyboard
5. Press right ALT (ALT GR on some keyboards) and PrintScreen
6. Connected the other positive lead to ACC (unit does not work if both BAT and ACC are not connected)
6a. Start pressing repeatedly on E (not holding E pressed, but press...release... press... release..... rapidly)
7. The boot logo shows (Lollipop...etc) and after a few seconds the unit reboots itself
8. Release right CTRL & PrintScreen and continue to repeatedly press on E.
9. The Recovery shows on screen.
Sweet success at last.
I put a USB stick with Hal9k room and selected install from USB and clean... waited for 15-20 minutes and everything fine.
Mounted the unit in the car after switching to MicroG and configuring apps.
Hope this helps others who have problems getting into recovery.
fabro91 said:
I also want to know that, never find solutions at this time.
I have same car with same head unit, do you have a good radio reception?
Click to expand...
Click to collapse
Hi,
Found solution, described in the previous post.
Reception is good. I had also a power amplifier mounted but did not improve reception futher so got rid of it.
Hal9k ROM with MicroG is much faster than stock one.
My MTCD unit touchscreen or soft buttons don't work after wake up after key off.
I have to key on - key off 3-5 times before they work. Once they are working unit performs perfectly until the next key cycle.
I think it's a software issue but is it Firmware or MCU
I am seeing the same intermittent problem with my PX5 unit, screen is black and push buttons do not work, cannot enter recovery mode either, then for no apparent reason it will work normally for a while.
I suspect there is a hardware fault with mcu or maybe even some other failing component or poor soldering. I have raised the issue with the seller but would be interested to hear from others as to what they think the likely cause may be or what can be checked to narrow down the problem.
As far as I can tell the battery and acc voltages are good but 7805 and 7809 regulators do not appear to be powering up in my case?
Mine isn't as bad as the unit will continue to play music from the point key is off and steering wheel controls still function.
Hello, did you manage to solve the problem? I have the same issue after upgrading from PX3 to PX5. The unit works fine after booting (if the power is disconnected). The problem is after wake up, since it does not support to turn it completely off any more.
Did you do something before it happening (e.g. a firmware update, mcu, or?).
Thank you.
I have the same issue with my new GS PX5. Before I had another one which hadn't this problem.
My problem seems to have been solved by updating the MCU to HA 2.61. Now the menu to control shutdown behavior shows up in the Extra settings and I chose the 30 sec delay.
Not sure if auto sleep works too, need to try.
Alex.
My top soft buttons stopped working.Everything else work ok but all the top softbuttons doped working. What can I do?
So, have a bit of a situation and not sure what to do.
My touch screen is working, but only to a point. Only the top status bar and bottom about the same size does not respond at all across.
I've attached a picture as an example of which part of the screen highlighted in red does not respond at all to touch. Everything else not highlighted in red works fine.
Have used my mouse to access boot recovery mode, reinstalled hal 9k mod rom, wiped cache / data and it made no difference.
Even updated my MCU to the latest version available for HA unit, and attempted to re-calibrate the screen via extra settings.
Not sure if original factory rom will fix this, but would like some opinions.
maybe take it apart and check the screen connector is in correctly, sounds like a hardware not software problem.
darkphat said:
So, have a bit of a situation and not sure what to do.
My touch screen is working, but only to a point. Only the top status bar and bottom about the same size does not respond at all across.
I've attached a picture as an example of which part of the screen highlighted in red does not respond at all to touch. Everything else not highlighted in red works fine.
Have used my mouse to access boot recovery mode, reinstalled hal 9k mod rom, wiped cache / data and it made no difference.
Even updated my MCU to the latest version available for HA unit, and attempted to re-calibrate the screen via extra settings.
Not sure if original factory rom will fix this, but would like some opinions.
Click to expand...
Click to collapse
Hi,
I have similar problem on my px5 seicane unit. the bottom part touch screen won't response or acting without touch after wake up from sleep. restart the unit would result the issue.
wondering if you have resolved the problem? If so is that hardware issue?
just realized the touch screen issue I have on my headunit is probably hardware issue.
in the past I have to re-start the unit, that actually fixed the problem, don't know why. but now I just push the touch screen with my palm firmly. that would fix the problem as well, and last much longer (3-5 days). haven't get chance during the weekday to open up the unit. but at least it worked. and probably proofed this is hardware issue.
I have a Joying unit with a PX5 board. I also have the same issue as the original poster.
I would also say this is a hardware issue. Mine was fine with both the original PX3 and PX5 for a while. Now it is increasingly getting worse. Resets do nothing to solve the problem.
I live in a hot environment. Maybe that is a contributing factor?
Hi,
This is my first post on this forum and i am hoping members here will help me solve my issue. I have a Honda HR-V 2016 LX that came with a non android unit. I later purchased a Honda Navi unit from ebay UK that was pulled from a Honda HR-V 2017. The unit worked fine and later I downgraded to RC6 firmware so that I could install additional software from CMdroid. The problem started when i tried to change the skin through system settings, the unit gave a notification that system will restart and since then it is in continuous boot loop. Now this is what i have done till now :
a. disconnected battery for over 15 minutes. No change
b. tried to boot the system through USB with firmware RC6, It updated fine with progress bar and at the end got the message update successful and USB can be disconnected but at restart it still remained in that loop.
c. Again booted with USB having RC8 successfully but no luck
I feel that I need to do a factory reset to get my audio working again but unfortunately it is not booting up to the point that soft keys get illuminated. The reverse screens powers up but without guidelines. I don't want to lose my unit. Please help me recover it.
Regards
Members I need help here. Please some one suggest me a solution to get my audio unit working again. Today I reinstalled the firmware and it went smooth but on restart the system continues to reboot.
Hi Panther3, did you ever get to the bottom of this, the same thing has just happened to mine?
Scooterpop said:
Hi Panther3, did you ever get to the bottom of this, the same thing has just happened to mine?
Click to expand...
Click to collapse
I actually have a 2nd honda navigation unit that has this issue... Been trying to work on it but no luck till now...
So I am curious if someone manages to make it work ^^
here is the official solution from the manual... :
Some units might experience "H screen stuck on"
symptom. Initially the software update will not be
possible when the unit is "H screen stuck on". You will
need to follow these steps before attempting the
update:
• When unit is in fail mode "H screen stuck on",
Press and hold the Power and Day Night button at
the same time for five seconds.
Note: Wait until the loading circle appears on the
screen and then press the Power & Day Night
button.
After five seconds the unit will switch into the
reboot mode, then the unit will do a file check
during rebooting. Rebooting will take
approximately two and a half minutes.
• Now continue with software update procedure.
Note: The "H screen stuck on" symptom can be
caused by software or a hardware failure. In case of
a hardware failure, recovering is not possible and a
new RM unit is necessary.
Click to expand...
Click to collapse