MTCB/MTCC rk3188 (5.1.1) Firmware

[dsa8310]

For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.

Updated on July 3, 2018:
(reason in post #636)

MicroG in post #396, and here:
Mod Edit :- Links Removed

Mod Edit :- Links Removed

Open GApps in post #416, and here:
Mod Edit :- Links Removed

Mod Edit :- Links Removed

They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.

I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible. It also performs a one time nice Google setup of the unit, beginning with language, account, and so on.

Note to all using this firmware for the first time: since it is differently partitioned from what you had before, you must also perform a wipe all in recovery, ideally just before the first startup (to avoid wasting time), or at any time now.

WARNING: MicroG Core and LP don't work well: contacts are not seen from apps like Hangouts, Google/Voice Search, while True Contacts needs local loading of profile & contacts - from vcards on the internal SD. Therefore I strongly recommend the Open GApps version!

Note also that with the MicroG version, the gms core app must be configured, and Hangouts' service called NetworkConnectionCheckingService must be disabled, for Hangouts to work:

pm disable com.google.android.talk/com.google.android.apps.hangouts.service.NetworkConnectionCheckingService

TomTom GO storage support is explained in post #45.
TT GO spoofing is in post #392.

Poweramp's early start&restart is also supported by default.

Phone calls via a BT connected phone could be dialed by (always) selecting the MTC Service(aka Headunit), as the preferred dialer.

MTC Sound direct sound control is readily supported, if the associated hardware mod is also done.

Automatic screen brightness control based on location&time is also implemented by default.

Blank logo kernels are in post #600 (get them while they last).

Developer Mode in post #332.

Firmware is also rooted and xposed.

To those who make outlandish claims about this firmware: they are either trolls or firmware is not for them. However firmware supports all rk3188 MTCB or MTCC units. Make your own judgement, and don't get scared away.

===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...

===
Here's another one: in principle, unless an unlikely bug is reported, I don't reply in this thread to users who are not listed as saying thank you to this post.

===
Mod Edit :- Content Removed

 

[abhi633]

Thanks @dsa8310 .. your rooms are great .. I installed microg rom yesterday . Works great . Will try the new one soon. The only question I have is the performance of both roms similar coz I have 1GB Ram

 

[Oldpapa49]

For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.

MicroG in post #396.

Open GApps in post #416.

They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery.

I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds.

===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...

Hi @dsa8310, is it possible to find what version of your firmware that I have installed in my radio. I think I updated yesterday, but not sure if it the recent one that you posted yesterday.
Maybe a tall tell signature or something to look for.

Again, thanks for your work on the firmware. And I hope this section works out for you.
Wayne

 

[dsa8310]

The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).

The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).

Other than that I don't keep track of versions - it's only the last one that matters.

 

[typos1]

As usualI I ll be putting the ROMs on the fileserver for everyone.

 

[EagleSoldier]

Where is the donate button ?

Thank you very much for your hard work

I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....

So fast and stable, highly recommended.

Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?

Best regards

 

[Oldpapa49]

The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).

The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).

Other than that I don't keep track of versions - it's only the last one that matters.

I have the 6/28 one.. MicroG I guess. Getting Gapps..

Thanks bud.

Like to donate as well..

 

[dsa8310]

Where is the donate button ?

Thank you very much for your hard work

I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....

So fast and stable, highly recommended.

Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?

Best regards

I now use the (pico) Open GApps enabled version. I like it because I don't have to configure things and it is 100% Google compatible. I dislike it because of Google ads' undisturbed presence, unlike the MicroG version that avoids them, partially, at least for my set of apps.

There might be observable differences in their footprint size (necessary RAM) and load of system (background tasks). I can't say for sure, since I have a 2GB RAM (upgraded) unit. Furthermore, I run the same set of apps most of time: Poweramp and TomTom GO which have the same heavy requirements (TT mainly).
Perhaps 1GB units should use MicroG while 2GB ones could afford the Open GApps version.

A technical comparison between versions could be done, in a terminal (termux), with commands like "free -m" (free memory) and "uptime" (busybox uptime) (for load average); "busybox ps", too, if implemented.

But, ultimately, it's a matter of feeling: if you feel that one version is more responsive, feel free to use it.
(switching back and forth is facilitated by the same partitioning, though going through a wipe all in recovery seems necessary)

 

[ankerede]

I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.

 

[dsa8310]

I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.

Have you tried both MicroG and Open GApps? If yes, was it any difference for you?

The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)

 

[ankerede]

Have you tried both MicroG and Open GApps? If yes, was it any difference for you?

The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)

So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps

 

[dsa8310]

So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps

Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)

 

[elyl]

For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.

MicroG in post #396, and here:
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar

mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar

Open GApps in post #416, and here:
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar

oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar

They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.

I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible.

===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...

Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.

 

[dsa8310]

Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.

No, they are not.

It's possible, but then uninstall by hand three apps: com.google.android.gsf, org.microg.gms.droidguard, FakeGapps1.1, and then reboot.

 

[Tumke32]

Hi dsa,

i'm on your latest microg version of your firmware with the playstore. But when i open the playstore and try to connect i get this error: [RH-01]

any idea?

 

[mouscolo]

problem iam facing now i cant play music while using google maps, any help?

 

[Oldpapa49]

Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)

I give it a + for GApps. Still works nice with Google Play and able to use what you paid for with no issues.

Finally got more play time with the latest and I like it.. Using 1G, no upgrade memory at all..
Still need to add a few more apps.. but good to go..

Thanks @dsa8310

 

[dsa8310]

Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).

While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.

I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!

 

[Oldpapa49]

Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).

While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.

I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!

Exactly what I did. A setup that I have never seen before had to be done. Great Job.

 

[dsa8310]

It's Open GApps' merit, not mine. Once the setup is done, everything else falls into place.