yashsingh1/xdaforums huggingface dataset:
[MTCD Software Development] masri1987:
so, i've avoided most problems on this rom until today

I am on v6 , dirty flash from V5 ( clean flash on v5)

Bluetooth was pairing with my phone fine, until today, the head unit no longer is seeing my phone or vice versa, and when i put it in pairing mode it doesn't see the head unit.

I noticed the name of the bluetooth profile for car unit was erased and pin is missing as well

any ideas? I cannot re-pair
[MTCD Software Development] sterod:
Force Immersive Mode which forces an app to go full screen, hiding the status bar.
[MTCD Software Development] Vencoko:
I've just flashed the latest MTCD rom with no problems over the USB and system update function. No errors at all for now, everything is working just fine.

Here is a video, so you can have an idea, havent play much: https://www.youtube.com/watch?v=sB_s9oMDeb0
[MTCD Software Development] kamikaze2112:
Did you update over the stock rom, or from a previous version of this rom?
[MTCD Software Development] dongali:
I tested v5 and v6 for several days each. In the end, I downgraded back to v4 and it has been stable so far (3 days)without the bugs present in v5 and v6.

v5 would randomly erase itself so I had to redo everything. It would also randomly start up to a blank black wallpaper with nothing on it which forced me to do a hard reset to fix for it to be usable again.

v6 didn't erase itself (yet?). But the blank wallpaper bug is more frequent on this version. Once in a while I would lose steering wheel and panel key functions which required a hard reset to fix.

MCU of my head unit: KSP
[MTCD Software Development] Vencoko:
Updated over stock factory rom.
[MTCD Software Development] raptor18:
Would it be possible to add the possibility to disable the internal microphone of a MTCD unit? Or is this impossible as it needs to be done to the lower level firmware?
[MTCD Software Development] mpalastea:
is it possible to disable speed showing in status bar, in CarMod launcher?
[MTCD Software Development] Flockrock:
Anybody knows how to setup the russian autostart app to start an app in background after booting? Just need the name of the option.
[MTCD Software Development] w0rdie:
Helpful post -- thanks.
[MTCD Software Development] CadillacMike:
agreed, v4 is rock solid for me, I probably will stick with it
[MTCD Software Development] -=Jeff=-:
I have used v6 in my car, that said it dont drive the car much but so far I am very happy with it. only thing I noticed was if I change anything in factory settings, many other settings reset (just caught me off guard) . I am happy with the brightness of the screen and how well it dims at night with lights on.

I have not seen any issues yet (not saying they will not happen though) I went from V4 to V6 when I installed
[MTCD Software Development] w0rdie:
Rock solid isn't how I would describe it but the reported woes from people who are using v5/6 sound brutal.
[MTCD Software Development] sterod:
This isn't because of Malaysk ROM, it's a defect in the way the MCU operates. I've reported this to the Joying tech support and they don't really seem interested in fixing it. When I told them that the radio presets are lost whenever you touch the Factory menu or reassigned steering wheel control keys do you know what their answer was to me? "Well try to limit how often you do that." No joke. If they'd simply store the settings in an XML file on the internal storage that could be backed up and restored when needed we wouldn't have this problem but they are too lazy to do anything about it
[MTCD Software Development] erik077:
Anyone ?
[MTCD Software Development] -=Jeff=-:
Yeah I figured it was a joying thing, not Malaysk.. I was just surprised when that happened.. sort of annoying, but livable
[MTCD Software Development] sterod:
Google is your friend.

http://xdaforums.com/wiki/Generic_Android_Head_Unit/MCU_Explained

you update it by placing the dmcu.img file in your sdcard folder and running the About / System Updates command. It should detect the file and offer to reboot and upgrade.
[MTCD Software Development] nixfu:
So, after running V4 for a few months with no issues. I decided to try V6 on my joying unit.

I installed with a full system wipe/clean. I am very experienced with this stuff having a MTCB for years and running many versions of Malaysk's custom 4.4 ROMS on it, before getting this MTCD unit.

TWICE now in 2 days, after about the 4th time I use it, it goes into an endless loop of crashing as soon as it gets to the launcher and then goes right back to the boot animation, then launcher flashes on screen and then back to boot animation.

I wonder if it is v6 or the fact that I am trying out the carmod launcher for the first time after having use the JY launcher always before. Is the carmod launcher prone to crashes?

I hardly did much else as far as setup to the thing because I was waiting to see if v6 was stable. I enabled the exposed titlebar modules, and I installed google maps and waze I think is about it before it started doing this.

Anyone else using the carmod launcher? It does seem to have pretty good performance though I have to admit.

I am going to try one more time using the JY launcher and see how long that install lasts. If it does the same thing I guess it is back to v4 for me as well.
[MTCD Software Development] sterod:
I've explained this a few times already. Don't go directly to 6 from anything prior to 5 or even OEM. Upgrade to 5 first, enable xposed modules, even if you aren't using them, then install 6. 6 has that bootloop issue and it's because of the xposed framework.
[MTCD Software Development] hans1983:
I've used V5 now since it came out and tried V6 for a couple of days, but it didn't appear stable.

- the phone-buttons didn't work and no pop-up of the phone conversation showed if you were on a call, the bluetooth connection did work however

- sometimes the unit would simply not respond to any of the hardware buttons, but did react to the soft buttons. Only a reset would solve this issue.

- sometimes the media player wouldn't show anymore, although music did play

- Tomtom Go doesn't appear in the Play Store anymore. Probably solvable by installing the apk separately, but considering the other bugs, I haven't put any effort in trying for now.

So for now I've rolled back to V5. Hopefully V7 has these issues ironed out again.
[MTCD Software Development] nixfu:
Ok, since I already wiped my system, I will try that before going back to v4.

Do I need to:

a) do a "system clear/wipe"

b) install v4

c) install v5 (enable xposed) (without clear)

c) install v6 (without clear)

or can I skip v4 and just wipe/install v5 as a 'base' to install v6 on top?

My suggestion for V7 is [MENTION=3590033]Malaysk[/MENTION] to make a v7 MTCD 5.1.1 build WITHOUT xposed installed already into the ROM by default, since it is so unstable, and just put the installer apk into the OEM or something so it can be manually installed or not by the user. Right now you can't uninstall xposed because it is included in the ROM. My guess is that v5 and v6 would be fine if you could uninstall/not install this new unstable xposed. It is probably xposed startup that is causing the crash on boot.
[MTCD Software Development] sterod:
I've never tried skipping version 4 but what I can tell you will work for sure is to do a full wipe from the power up recovery menu and install version 4 then once four is installed install version 5 from the about system version screen, no wipe required, then enable the Xposed modules, reboot one more time to make sure that you don't have a boot loop with V5, then finally if it is all good install version 6 from the about system versions screen.
[MTCD Software Development] NaviPR:
[MENTION=3590033]Malaysk[/MENTION] and others

Guys, honestly I'm kind of fed up with this at the moment.

EVERY TIME I have tried to install Malaysk's ROM on a KGL unit, IT BECAME BRICKED.

I ALWAYS use the recovery, update with wiping all data, etc. etc.

So far I've bricked a few units even though I have been following the instructions to the letter!

I bricked one unit, had to replace the RK3188 board... then I bricked another one, replaced the board inside it... decided to install the ROM again, perhaps something went wrong and it wasn't my fault... BRICKED AGAIN. Now I have a headunit that was bricked... two times in a row!!

Has anybody else been having these kinds of problems?? I'm using the 25.07 ROM from the repository, because [MENTION=3590033]Malaysk[/MENTION] 's Russian filesharing server does not work for me.
[MTCD Software Development] Malaysk:
From July 25 firmware for the devices MTCB !!!!!! - http://huifei.fs-fileserver.de/cont...RK3188 1024X600/5.1.1 FUSE 1024x600 Malaysk /

From July 24 firmware for the devices MTCD !!!!!! - http://huifei.fs-fileserver.de/content/firmware/MTCD CUSTOM ROMS ONLY NOT FOR MTCB /RK3188/

You installed a wrong firmware!

How to restore the device - http://xdaforums.com/showpost.php?p=67184851&postcount=50
[MTCD Software Development] NaviPR:
I have downloaded the ROMs from this directory:

http://huifei.fs-fileserver.de/cont...RK3188 1024X600/5.1.1 FUSE 1024x600 Malaysk /

Are you saying this is actually MTCB??

Somebody should REALLY clean up that file repository... so nobody else makes the same mistake...
[MTCD Software Development] Malaysk:
1. On the first page of the specified link to the file sharing download firmwares for MTCD -

2.All files are signed for some devices they are intended. For example - dupdate_5_1_1_FUSE_1024X600_800X480_RK3188_05_MAL_25_07_2016_MTCD
[MTCD Software Development] masri1987:
pretty sure it says MTCB in the file name
[MTCD Software Development] cat2115:
Pure Android 5.1.1

RK3188 Cortex A9 Quad Core

Built in DDR3 2GB Internal Storage, 16GB NAND Flash

MTCD_KGL_V1.10_1

Can I install this ROM? If yes, do I need to start from Version 1 then update to v2, v3, v4 and finally v5? or I can start with v5 since no custom ROM ever installed? As I read, a few post, i notice v6 is buggy.
[MTCD Software Development] dongali:
Yes this rom will work with your unit because it's an MTCD. However, make sure you are able to access recovery. for my MTCD-KSP head unit it's by holding the power button for a while until the panel leds flash 3 times, then immediately let go of it and press it 1 more time.

In my personal experience, the most stable version is v4.

You can try sterod's sequential flashing suggestions and try your luck with v6:

Flash from stock to v4, reset cache & clear data through recovery, flash to v5, reset again through recovery, activate xposed + modules, reboot, flash v6, reset, activate xposed + modules. Done.

Good luck
[MTCD Software Development] Vencoko:
A little report here.

Usind MTCD-JY-UL124 5.1.1 - headunit

Installed the latest Malaysk ROM v6 few days ago through system update with USB stick over the stock ROM. Everything worked fine wifi, bluetooth, gps, music, video - everything. Didnt checked the xposed modules at first, installed few apps from play store - so far so good. Today i was making another customizations and stuff and checked the xposed modules aswell, after reboot i entered the continues boot loop and was forced to do wipe system from the recovery. Did that and after the system was ready again the first thing i did was to check the xposed modules plus installed few other modules, after that did the reboot and the system loaded normally, than i installed some apps, do some stuff and customizations, rebooted 4-5 times and no problems till now. Everything is working flawlessly, no complains, will see in the next days.

Question: I'm using a phone with 2 sim cards and the bluetooth is only synching the contacts from one sim card. How to synch both sim cards ?
[MTCD Software Development] nixfu:
It seems the current opinion is:

a) v4 is quite stable, many people have run that for months and still run it. you can install that by doing the "system wipe/clean" and install/clear over top of factory

b) V5 is unstable and will crash/bootloop etc.

c) V6 is also unstable BUT, if you install V4 clean as above, then install V5 on top of it (without a clean/wipe), and THEN install v6 on top of that (without clean/wipe), some say that ends up working.

If you want the most stable use V4, if you want to try the latest but are prepared to reinstall again maybe over and over, then try v6 as above.
[MTCD Software Development] cat2115:
Not sure which one or what OP mean by download "screen off button or w/out screen off button. "
[MTCD Software Development] dongali:
There is a button on the status bar at the top of the display that allows you to turn off the screen but keep the unit running. You can choose if you want this button or not.
[MTCD Software Development] CadillacMike:
oh wow, thanks, I had no idea what that was
[MTCD Software Development] dedafmonteur:
Is v4 better than the latest stock version for mtcd? Ifso, what is better?

I have the latest stock version rooted and i am thinking about v4
[MTCD Software Development] zoxenrbg:
I brick my mtcD with you...

I use wipe data setting. I can boot but only have android in cercle.

Can you help me please, how to go to recovery ? I have a GS model.

Thank's you for you help...

And NOT compatible with ALL mtcD.
[MTCD Software Development] dongali:
The first boot after flash can take 10 minutes to finish. Also in the first post it stated you need to be able enter recovery mode before even attempting flashing this rom...
[MTCD Software Development] zoxenrbg:
I know for the boot but nothing, boot and have a black screen after the "android" logo of boot (animated logo).

I will look again the fist post.

How can have a factory ROM ? I search for backup it before my brick but no really how to...

Thank's

---------- Post added at 02:58 AM ---------- Previous post was at 02:51 AM ----------

Sorry, Hi again ;)

I bought a cable. I have to plug in USB Facade me?

Can you tell me how to get my brig?

With RKBatchTool v1.7 or SD_Firmware_Tool?

With rk3188-64bit-win8 and launch RKBatchTool. And after-?

It will work?

Can you help me ? This is the 4th MTC(b or D) I brig with Malaysk.

I'm really silly. I take the right version and still the same problem. But the advantage of Xposed ... I'm stupid to have tried yet! 4 Brick for a lot of money and time ... Idiot idiot !

Help me please.
[MTCD Software Development] ikerg:
Mtcd version of Malaysk is compatible with all mtcd models.

If you mix mtcd hardware with MTCB software and vice versa you will have a beautiful bricked device.

It is stated several.times along the two main threads for mtcd units

If you have low knowledge it is better to have the things as they are until you read and figure out how everything works.

People with bricked units have been reported to restore the system by using rockchip tools for flashing.

Please read a little bit.

You will need a cable to connect it to PC (I don't know which cable you need). you have to install the rockchip drivers

Once connected to the pc you will have to start the flashing tool rkbatchtool 1.7) and the tool.must detect your device as mass storage (if not something wrong with your drivers or try other USB port). With the switch button you will make the device to boot as loader device (recovery) and the tool shall report that the device is detected as loader device.

Then you will have to select the firmware dupdate.img and flash the image

Once finished the flashing the device will boot again with the new firmware.

I never tried this method on mtcd unit but I did on other rk3188 devices (tv sticks(

Enviado desde mi D6603 mediante Tapatalk
[MTCD Software Development] -=Jeff=-:
Not sure if this is in Malaysk's ROM, if it is, I could not find it:

I found an Audio timeout setting (for the screen saver essentially)

I also found a delay in shutting the unit down completely

What I did not find is a delay to 'off' Meaning if I shut the car off the unit goes to sleep, when I start the car within the delay shut down it is basically like coming out of sleep. Currently it does it twice on starting the car ( Due to Crank time) . I know I can add a capacitor for x amount of time. but is there a setting in the ROM?
[MTCD Software Development] zoxenrbg:
Thank you for your help. I spent the night above. I will try to continue.

I always checked the versions since I use a B on time... for 3 out of 4 is not my fault I did everything perfectly ...

I'll keep you informed with the computer ...
[MTCD Software Development] NaviPR:
Argh! Thanks guys!

You are heckin' great, and I am a friccin doofus. Never in my life have I made such a basic mistake, until now.

Thanks for pointing this out for me... guess I was too fast to download that software!
[MTCD Software Development] aarick:
So I manage to kill my physical button again. I wonder if it is mtdc tools causing it. That was the last thing I installed and did a reboot and it all stopped working. I was at the same time checking out other launcher too..
[MTCD Software Development] raptor18:
Good that you solved it because i was going to not flash a new rom because of you :p
[MTCD Software Development] sterod:
Is anyone else experiencing horrible bluetooth call audio quality? The audio is essentially all "mid range" no highs or lows, has crackling noises and sounds just terrible. The people I am speaking to also say that my voice comes through poorly. All other types of audio sound fine though (radio, a2dp, mp3, etc). I'm wondering if this is just another part of their poorly optimised and implemented BT profiles.
[MTCD Software Development] -=Jeff=-:
I have yet to try out the bluetooth connection to make a call while in the car.. I will try it though
[MTCD Software Development] raptor18:
One of the most important features and it barely works. When will the Chinese learn to listen to us
[MTCD Software Development] mlkemac:
I unfortunately did the same thing.

I've followed your restore procedure, and I get the "lollipop multi-media on-vehicle navigation system" screen, but it will not go past that.

I tried using v4, v5, v6 of your MTCD. all with the same result. any advice?

Thank you
[MTCD Software Development] gunmoule:
Same here. Horrible Bluetooth call quality. Overall call experience is: barely usable. The interface is not really user friendly, the internal microphone sucks and the sound is bad with crackling noises.

I have read somewhere that attaching an extension cable to the external microphone input somehow helps. I mean just an extension cord with nothing attached, the longer the better.

I still have to try it but you can give it a shot too.
[MTCD Software Development] -=Jeff=-:
I tried my Bluetooth for a call.. Seems ok..

I had the external mic from my Newsmy connected, apparently the mic was bad and did not work. first attempt I had nothing. after dis connecting the mic I could speak and the other end would hear me.

I did have an issue. I was using rocket player and I got a call and there was no notification to accept. I have not messed with the OEM music app, but want to figure out the best app for music that will work when I receive a call.

If I end up needed a headset for calls I am okay with it, as I do like some of the functions of the radio..
[MTCD Software Development] Malaysk:
You are 100 percent sure that you have a the device MTCD ? When you insert a bootable SD card into the unit, you will find yourself in recovery? You can take a video like you to flash the device?

Why is no one wants to read the first page and go directly to flash firmware the device?
[MTCD Software Development] dongali:
[MENTION=3590033]Malaysk[/MENTION]

Is it possible for you to make a v6 of your rom but without Xposed? It seems to be Xposed that is causing several bugs. Your v4 has been quite stable but it's not as fluid as v6. It would be amazing if there are 2 branches of Malaysk roms- one with Xposed and another without.

By the way, I found a stock rom from xtrons that seems to be the latest version based on it's filename, maybe this could potentially be a new base for v7? (I do not know what is the MCU of dmcu.img in the .rar)

Link to 8-5-2016 stock MTCD rom: www.xtrons.com/firmware_updates/latest-Android-5.1-20160805.rar

Thank you for the great work so far!
[MTCD Software Development] Malaysk:
I do before version 7, will soon lay out an updated version 6.5. I rewrote a lot there. Fixed selection of GPS applications and a lot of changes. I'm her tested. I have it working fine. True test runs at home. My the device is at home and test it turns out deficient.
[MTCD Software Development] aarick:
Physical Button Issues (Stop working), incl. steering wheel buttons

I can't seem to narrow down which configuration is causing this issue, but here is a summary of my issue that I hope someone will be able to shed some light on:

MTCKeys enabled in xposed(might be disabled, need to run check again later) + Buttons remapped in Panel Button Study: Buttons working as expected

Installed MTCDTools. Setup a few button bindings. Reboot. Physical Button stopped working. - Uninstall MTCDTools and reset panel button study and reboot to fix button issue

Freeze MTCKeys in Titanium backup, Buttons remapped in Panel Button Study. Reboot. Physical Button stopped working. -Reset panel button study and reboot to fix button issue

So I am interested to know if:

-MTCKeys is required to ensure Buttons remapped in panel button study works?

-Can MTCKeys work with steering wheel buttons?

-MTCDTools causing conflict?

ANyone have idea on what my issue are and how to be able to remap my steering wheel buttons to work with other apps?
[MTCD Software Development] raptor18:
What are the reasons it is important to know how to enter recovery mode on our units?

Is it to flash the firmware or to know that i will be able to fix any flashing errors?
[MTCD Software Development] Malaysk:
del
[MTCD Software Development] dongali:
Google translated from the thread Malaysk posted on 4pda.ru

Testing.

NEW on 09/16/2016 - Version 6.5

Strongly recommend to do after installation rekaveri Wipe Data (penultimate paragraph) because it has changed the location of the system software in the partition is not the system (now all the additional applications and launchers safely removed from the Settings -. Applications if you do not need) Added new module for Xposed - copy the folder with the settings on the SD card (GPS - card) by changing its settings to fit your needs. Everything is inside the archive.

Download - https://yadi.sk/d/tImGhwCUvE7SV
[MTCD Software Development] Tracker95:
Is the Bluetooth issues fixed with the latest version?
[MTCD Software Development] -=Jeff=-:
download 6.5 link shows nothing there.
[MTCD Software Development] sterod:
That's odd, you're right, its gone. This one (taken from the first post) seems to work though.

https://yadi.sk/d/bmKtJzv_vF3mc

---------- Post added at 08:37 AM ---------- Previous post was at 07:52 AM ----------

Guys don't install this new version 6.5.

[MENTION=3590033]Malaysk[/MENTION] you really need to fix the Xposed bootloop issue. I was running version 6 and I installed 6.5 exactly the way your instructions say. I entered the factory recovery menu and chose the option to install from SD card and delete and then on the next reboot I also did the wipe. Everything was working fine until I enabled the status bar Xposed module. As soon as I did that on the next reboot I am now stuck in a boot loop as you can see in the YouTube video below. This is extremely frustrating now I have to reload version 4 then 5 and then 6 to get back where I was. Please fix ASAP, thank you

https://youtu.be/Lt9Xd1Keuwc
[MTCD Software Development] aarick:
Hope v6.5 will fix my physical button issue. Thanks.
[MTCD Software Development] Malaysk:
I think the blame Next Launcher !!! I have set as the default launcher another. And I'm fine!!!

UPD : Although the I have now tried to install NEXT launcher, and I'm good to download.