[ROM][RK3066/RK3188][SD/HD] Malaysk ROMs Android 4.4.4 for any yet known MTCB-Device

[mblue199]

You could always just wait until it's finished booting before activating the BT on your phone.

Thanks for the reply...i just let the phone's Bluetooth always on and it connects automatically.
So i was thinking about a way for the head unit to delay the searching for the Bluetooth device till it completely booted

 

[oldman_58]

Thanks for the reply...i just let the phone's Bluetooth always on and it connects automatically.
So i was thinking about a way for the head unit to delay the searching for the Bluetooth device till it completely booted

There is a startup program PVC i think, you should be able to set the start after other events.

 

[mblue199]

I see...but what is the name of it and how to delay it.
Sorry for being not that expert

Sent from my GT-I9295 using XDA-Developers mobile app

 

[halloj]

I have installed it from original to Malaysk, i have done wipe data and cache, i have activated the modules in Xposed.
I installed the canbus included in the package.

Have you selected the correct can-bus in factory settings?

 

[souliferi]

Have you selected the correct can-bus in factory settings?

Thanks halloj, do you can tell me what are the different option to configure canbus in the factory settings?

 

[halloj]

Thanks halloj, do you can tell me what are the different option to configure canbus in the factory settings?

Go in to factory settings 126 and select the correct can-bus for your car.

 

[Brendo]

Hi...is there a way that can make the headunit Bluetooth connects to my phone only after the headunit is booted complete...as it connects to my phone while i have a phone call but no sound comes out as the headunit still booting

More a flaw with how the device is designed. The hardware is independent of android (mcu is what allows them to interact), so Bluetooth etc starts up on it's own, then android takes over. It can be annoying, but generally is only a few seconds (or have to disable temporarily via phone dialer to continue talking on phone, then switch back on once hu is booted)

Hi Everybody,

I have installed the last firmware of 12 June 2016, it's all ok but i have a problem with the steering wheel controls ; they are set to default controls but if I want to change I can not set the steering wheel , I click on the desired function on display than i click the button but is not associated with any physical key.
Does anyone have the same problem?
Thanks!!!!

You can't reprogram buttons if using canbus, only if using swc wires

 

[halloj]

More a flaw with how the device is designed. The hardware is independent of android (mcu is what allows them to interact), so Bluetooth etc starts up on it's own, then android takes over. It can be annoying, but generally is only a few seconds (or have to disable temporarily via phone dialer to continue talking on phone, then switch back on once hu is booted)

You can't reprogram buttons if using canbus, only if using swc wires

Aha, I misunderstood his question. Of course you're right.

 

[MiLe-SB]

As i love the screensaver GPS clock carbon orange but currently are changing to a Nexus7 tablet as headunit with 6.1.1 - would there be any way to get the screensafer running under these conditions. App od (better) widget does'nt matter so much.
I searched all the GPS apps in the playstore but could'nt find anything wich is as simple, informative and elegant as this.

 

[bsavoir22]

I don't think the screensaver would work outside of these headunits as a lot lot of the apps are mtc* related. You could try to get the apk off there and try it, but I highly doubt it is going to work.

Sent from my SM-N930T using Tapatalk

 

[War-Rasta]

I have an RK3188 800X480. I had this ROM installed (the June 12 version) but it started to freeze from time to time. I did a factory reset and it was OK for a while but it started doing it again so I decided to flash the ROM and the MCU again.

It went well but after that it won't boot and I can't get into recovery. It shows the first logo, but when it goes to the second one (the animated one) it says "Erasing". It stays there for about 10 or 15 minutes and then it reboots and the same thing happens again.

Has anybody had this happen to them? I tried to get into recovery using the reset and power button combination but all it does is reboot again into the same screen.

 

[Oldpapa49]

I have an RK3188 800X480. I had this ROM installed (the June 12 version) but it started to freeze from time to time. I did a factory reset and it was OK for a while but it started doing it again so I decided to flash the ROM and the MCU again.

It went well but after that it won't boot and I can't get into recovery. It shows the first logo, but when it goes to the second one (the animated one) it says "Erasing". It stays there for about 10 or 15 minutes and then it reboots and the same thing happens again.

Has anybody had this happen to them? I tried to get into recovery using the reset and power button combination but all it does is reboot again into the same screen.

Something corrupted, thats why it is erasing. Then it tried to reload what it had and you decided to stop it again, so it will repeat. It takes some time for it to fix up.
The other might be you need to clear data and cache ..
I had that happen when I thought it was taking to long.. I have since learned to leave it for some time.

 

[War-Rasta]

I did let it finish, but after it finished it just rebooted to do the same thing. I've let it finish several times (I drove to work this morning while it just kept doing the same thing over and over again).

I think clearing data and cache (like you said) would fix it, but it won't go into recovery.

 

[pa.ko]

I did let it finish, but after it finished it just rebooted to do the same thing. I've let it finish several times (I drove to work this morning while it just kept doing the same thing over and over again).

I think clearing data and cache (like you said) would fix it, but it won't go into recovery.

In other thread (about new LP Closed) there are some info on how to extract recovery partition from ROM image. Ask people there for hints how to push it via ABD if possible. Also you may ask around for TWRP recovery (you will need USB keyboard / mouse as it is not supporting touch screen).

After fixing recovery, download my and Ron again. Make two independent downloads and validate that both copies are identical to be sure you have good copy.

Unfortunately ROMs published here don't have md5 checksum. So you have to use above tricks to be o the safe side.

 

[MasouDNouroozI]

Inaccessible

How can I guide myself I install this ROM on the head unit.
I do not have access to recovery mode and is not activated.

---------- Post added at 06:35 AM ---------- Previous post was at 06:26 AM ----------

How can I guide myself I install this ROM on the head unit.
I do not have access to recovery mode and is not activated.

Hold the RES key and power key, do not enter the recovery mode

---------- Post added at 06:44 AM ---------- Previous post was at 06:35 AM ----------

How can I guide myself I install this ROM on the head unit.
I do not have access to recovery mode and is not activated.

---------- Post added at 06:35 AM ---------- Previous post was at 06:26 AM ----------



Hold the RES key and power key, do not enter the recovery mode

I think recovery is locked into the head unit.
Sometimes Bears Android image display that is just lying.
The message at the bottom reads:I think recovery is locked into the head unit.
Sometimes Bears Android image display that is just lying.
The message at the bottom reads:
" no command "

---------- Post added at 07:01 AM ---------- Previous post was at 06:44 AM ----------

System info:
APP 1024*600 2016-07-14
MCU Version:
2016-03-25 19:13:27 GMI_60_C6R_7706_5008_CAN(MazaDa)
DVD Version:
2016-05-06 10:40:34 R-86C-096I-NC-1.0-P12-IPOD
BT Version :
GOCB8_V1.0/2016:06:15
CAN Version:
Unknowm
Serial number :
00000000
Android version:
4.4.0
cpu info:
Cortex-A9 1.6 GHZ

 

[miffymiffy]

How can I guide myself I install this ROM on the head unit.
I do not have access to recovery mode and is not activated.

---------- Post added at 06:35 AM ---------- Previous post was at 06:26 AM ----------



Hold the RES key and power key, do not enter the recovery mode

---------- Post added at 06:44 AM ---------- Previous post was at 06:35 AM ----------


I think recovery is locked into the head unit.
Sometimes Bears Android image display that is just lying.
The message at the bottom reads:I think recovery is locked into the head unit.
Sometimes Bears Android image display that is just lying.
The message at the bottom reads:
" no command "

---------- Post added at 07:01 AM ---------- Previous post was at 06:44 AM ----------

System info:
APP 1024*600 2016-07-14
MCU Version:
2016-03-25 19:13:27 GMI_60_C6R_7706_5008_CAN(MazaDa)
DVD Version:
2016-05-06 10:40:34 R-86C-096I-NC-1.0-P12-IPOD
BT Version :
GOCB8_V1.0/2016:06:15
CAN Version:
Unknowm
Serial number :
00000000
Android version:
4.4.0
cpu info:
Cortex-A9 1.6 GHZ

This rom is not suitable for your device. MTCB only!

 

[MasouDNouroozI]

This rom is not suitable for your device. MTCB only!

:crying:
No solution?

 

[flieswithhawks]

Had anyone here tried using the A.R.I.S.E. sound mod with their head unit? I'm interested to know. Thanks.

http://forum.xda-developers.com/and...d-systems-auditory-research-t3379709/page1277

 

[snake_08]

Sandro, i am Brazilian. I need your help to set easyconnected on my s6edge.

Guys, I have found how to solve the Mirror function not working stating that you have 0 activations. It is not needed to put any file anywhere.
I have two phones (LG G4 and Huawey Nexus 6P), both on Marshmallow (6.0.1) and both work perfectly fine with the 3.4.X version of the Easy connected app. Using USB or WiFi connection.
The only needed action is to uninstall the old server app FROM YOUR PHONE.

If you have ever tried the old (or even a newer version) of the easy connected app to connect your phone, it installs two apps in your phone. An "easy connected server" app and a Drive Mode App(or something in Chinese letters).
The drive mode is just a stupid app that is supposed to have a car interface, you can safely unninstall it after it is installed. The server App is the one that is very important. It is the one responsible for sending the screen information from the phone to the HU, and also to receive the touch information from the HU.
The old server version installed on your phone is the one giving you trouble. And it is giving these certificate errors.

Whenever you are trying to install a new version of the EasyConnected app, remember to uninstall the old version of the server app (on your phone) and then restart the process.
If I had this info earlier, it would save me a lot of trouble.

The server App does not appear in the normal App drawer, you have to go to:
Settings->Applications->all installed to find it. Simply click it and choose to uninstall. (Easy Connected Server)

After that, restart the process to connect your phone again (remember, the first time you have to use the USB connnection) and it will be installed again. It even auto-update itself after installation.
Also remember that you have to have USB debbuging (under developer options) active all the time.

Sorry for the long post, but I wanted to give you all the info necessary. I'll also let some words below so people can find this post in search.

EasyConnected, Easy connected, Mirror function, mirroring, display

If I helped you, please click on Thanks button

 

[est3ban129]

hi, I need firmware for my radio 11-RQ0255E-ES

amazon.es/gp/product/B01FLQTVT8/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1

I have bootloop on android logo...

i.imgur.com/IZDsuM7.jpg

Thanks