Hi,
i have a KGL-790 Headunit RK3066 were the screen is flashing, it seems to flash every second. I have noticed the flashing doesn't begin right from the beginning when first started up. maybe a couple of seconds later and sometimes seems to get more rapid.
the display itself seems fine resolution , pixels etc almost as if theres another layer on top which flashes.
i have updated the mcu to kgl5 2.55 as the mcu had been updated.
i'm trying to work out if i have a hardware or software issue here.
Related
I flashed latest KGL 2.83 but encountered problem: sometimes on first boot in the morning, touchscreen is not responding. Also, once there was mess with boot logo changed to generic Android and I was not able to enter factory settings as password was not recognised.
These problems occurring occasionally, not on every boot.
On the other side, it looks like radio reception / station finding is improved.
I wonder if anyone else tryed upgrade of KGL to 2.83? Do I have to change something in Factory settings (I don't understand Malaysk post on MCU list page)? Anyone expired similar issues?
Where did you get v2.83 from?
edit; sorry, noticed MTCB unit not MTCD...
Hi there, i am also planing to upgrade from MCU KGL 2.80 to 2.83. Main reason ist a very poor radio signal. So, may i ask how things went on your side?
Greetz Moe
moetheone said:
Hi there, i am also planing to upgrade from MCU KGL 2.80 to 2.83. Main reason ist a very poor radio signal. So, may i ask how things went on your side?
Greetz Moe
Click to expand...
Click to collapse
Well, I stick with 2.83. occasionally it still freezes touch screen on boot. But I discovered that pressing button to turn off and then turn on the screen resolves issue ( I have he button for that)
I think radio reception is bit better with this than 2.80 though.
Hi, I have a Pumpkin, this one specifically:
Pumpkin Quad Core 7 inch 2 DIN Universal Android 4.4 Car Stereo Radio HD 1024*600 Muti-touch Screen GPS Navigation Without DVD Player Support WIFI/3G/Bluetooth/OBD2/DVR/Mirror Link/SWC https://www.amazon.com/dp/B016B4IY60/ref=cm_sw_r_other_awd_BNbkxb27QAKDQ
The only issue I'm having is that the volume knob will stop working after a few minutes of running. This has happened on two separate head units (same model). I've seen a couple posts with the same problem but no one really talks about it.
Disabling Wheel3 won't do anything because the option is already disabled.
Is this a major problem across all these units or did I just get two problematic units? Anyone have a fix better than the statusbar volume control?
This is known bug on XDA, faced by many of us. I have this issue with my RK3188 HU (Joying JY-UQ130, 99% the same HU than yours).
The most frequent issue is due to Waze v4.x. To avoid knob issue, just reinstall older Waze version (3.9 and before).
Actually, no hardware nor software fix. This problem doesn't occur with SWC.
Lwysiwyg said:
This is known bug on XDA, faced by many of us. I have this issue with my RK3188 HU (Joying JY-UQ130, 99% the same HU than yours).
The most frequent issue is due to Waze v4.x. To avoid knob issue, just reinstall older Waze version (3.9 and before).
Actually, no hardware nor software fix. This problem doesn't occur with SWC.
Click to expand...
Click to collapse
Waze is currently not installed.
Damn ! Try to update your ROM and MCU with the latest versions. It solved issue for a few of us.
Next step should be to have stock ROM with no app and test if problem occurs again. Issue is not clearly identified right now
Same issue on my Joying sometimes. It also seems to be caused by particular apps such as Waze as mentioned.
If I don't use those apps, it usually works fine.
BTW, when that happens as an emergency "this has to be turned down/up" solution, you can PULL DOWN the main menu bar and click "volume" on the settings toolbar and you will get the volume on screen display that you can click for a few seconds before it goes away to change the volume.
I have it on my Pumpkin 3188 SD (which is a KLD2 unit) too.
It has nothing to do with Waze 4. Sure, Waze 4 makes it happen more often, but it will happen with older Waze (probably less often but still happens) and all other audio apps.
It happens often when you get a call via blutooth (which interrupts your current audio) and so on.
Seems it is a bug in the firmware in all these units.
No one has found a fix yet so you'll have to learn to live without a volume knob for now.
---------- Post added at 11:30 PM ---------- Previous post was at 11:01 PM ----------
Lwysiwyg said:
Damn ! Try to update your ROM and MCU with the latest versions. It solved issue for a few of us.
Next step should be to have stock ROM with no app and test if problem occurs again. Issue is not clearly identified right now
Click to expand...
Click to collapse
Happens with the stock ROM too. I tried latest firmware (KLD2 2.81) on mine and it still happens.
Some have "solved" it by using a single audio app at a time, not using bluetooth with their phone, etc. but that's just trying to avoid the problem and not fixing it.
Same here with original ROM (I didn't change the ROM at all nor rooted the device actually) and latest waze installed...
Does anyone know if updating to Android 5.1 (e.g. Malays) solves the issue?
Upgrading the MCU software won't help since on my KLD2 I've tried flashing firmware up to KLD6 2.97 (that's what I am running now) and the volume knob issue remains. I suspect the issue is somewhere in the KitKat flash. Wondering if the problem is still there with the Lollipop flashes.
Sorry to resurrect a dead thread, but has there ever been a solution to this? Even a widget that could do volume control on these head units would be fine. All of the available widgets for Android to control volume do not work with this head unit.
Also, is this still a problem with the new Intel units?
I'm still having this problem occasionally too, usually when waze is open.
thintin said:
I'm still having this problem occasionally too, usually when waze is open.
Click to expand...
Click to collapse
Always Waze, no idea why. On a bright note, I switched to Malaysk ROMs Lollipop 5.1.1 yesterday and did not have the issue at all today (although the ROM itself is SLOOOOWWWW). Will continue to run it for a few days and report back.
My headunit (MTCB KLD6 with latest MCU 2.98 ) touchscreen is not more working properly, some upper and bottom part of the screeen is not responding to my finger touch, even tough I have managed to enter the factory settings to reset some setting such as the radio band (because I dont hear enything) it doesnt accept the "enter" comand when I press the OK button.
Also the "space" button and numbers/letter on the left bottom corner is not working when pressing the screen.
Is there anyway to make it work again??
I have also reinstalled another rom, resintalled it twice, maybe I should revert to an older MCU version?Currently I am running an MCC mcu version (kld6 2.98).
Is there any way to re-calibrate the screen??
I am so frustated.
Yes, it's really frustrating. I have the same problem with my Eunavi (MCU MTCD_LM_2.55_1, px5). Bottom of the screen (20%) doesn't respond. I also made factory reset of device, installed another ROM and changed MCU (from 2.55_1 to 2.52_1). All that things doesn't help. Because seller is not interested in helping me, in weekend i'm going to disassembly device and check connections between display and mainboard, eventually try to buy another display (digitizer ?) to replace it.
Has anyone ever suffered this problem?? Is there a way to re-calibrate the Head-Unit??
if I enter the code httouch into factory settings to check the unit resolution it says "1024*768" but my unit is a 800x480 native resolution.
I've never installed a wrong rom with incorrect resolution, I've changed serveral roms, reinstalled original MCU, but some part of the screen does not respond to finger touch...
Goaz said:
if I enter the code httouch into factory settings to check the unit resolution it says "1024*768" but my unit is a 800x480 native resolution.
I've never installed a wrong rom with incorrect resolution, I've changed serveral roms, reinstalled original MCU, but some part of the screen does not respond to finger touch...
Click to expand...
Click to collapse
If you want I have a MTCB 1024*600 touchscreen left. BTW I am from Italy too
Touchscreen change is great idea. I changed my digitizer after one month (1,5 week conversation witch seller and 2,5 week waiting on package). Now device working like new - I'm absolutely sure that was hardware failure. Changing is simple in my issue - 18 screws and 7 wiring tapes.
How did you know which to buy ?
Sent from my SM-N975F using Tapatalk
I just got mine installed and the top band of my screen is unresponsive as well.
I cannot touch My Apps in the play store or search in the play store due to the dead area being on that top portion.
I cannot even search in maps as that search bubble is at the top where the screen seems to be dead.
Time to contact Aliexpress.
Hi guys,
I flashed MCU 3.06 (Version HA) on my WITSON unit yesterday and realised that my radio even boots up immediately after more than 10 hours.
Altough I have set AC auto sleep option to "automatic" with older MCUs, usually that was working only for one, maybe two hours.
I am kind of impressed, but I do not know whether this really is caused by this new MCU.
Still I thought share my impression and adding a poll to get your feedback on this.
MCU version is attached. I can confirm it works on Witson (MX) unit after unlocking.
BR!
Christian
Yes, upgrading MCU to get Sleep is what inspired my nearly 2 year old MCU cross-comparability thread.
Hi all,
A couple of months ago I bought a second hand car with a Android head unit. It's a pretty old rk3188, MTCD_MX_V2.59, Android 5.1.1. 1024MB. I have been reading quite a lot on this forum to get introduced into the magical world of MCUs and ROMs
The unit was full of apps and very slow. My goal is just to use it for radio and Android Auto. So I did a factory reset of the unit, and bought an Android Auto USB dongle. I am satisfied with the boot time and with Android Auto.
There is just one thing that is quite bothersome. If I set radio channels in the standard Radio app (find a frequency, and then hold a pre-set button until it displays the current frequency) this works fine for the rest of the drive. However, this configuration sometimes becomes lost. I think after the unit has been powered off for a full day or something. Mostly if I shut down the car, and start it again within an hour, the radio channels are still there. If the configuration is lost, it is lost forever, and I have to manually set the pre-set buttons again.
Does this issue sound familiar to anyone? Thanks a lot for you help!
edit: oops, I should have posted this in the MTCD section..