yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] typos1:
As usualI I ll be putting the ROMs on the fileserver for everyone.
[MTCB Software Development] EagleSoldier:
Where is the donate button ? :D

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
[MTCB Software Development] Oldpapa49:
I have the 6/28 one.. MicroG I guess. Getting Gapps..

Thanks bud.

Like to donate as well..
[MTCB Software Development] dsa8310:
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)
[MTCB Software Development] 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.
[MTCB Software Development] dsa8310:
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)
[MTCB Software Development] ankerede:
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
[MTCB Software Development] dsa8310:
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)
[MTCB Software Development] elyl:
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.
[MTCB Software Development] dsa8310:
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.
[MTCB Software Development] 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?
[MTCB Software Development] mouscolo:
problem iam facing now i cant play music while using google maps, any help?
[MTCB Software Development] Oldpapa49:
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 [MENTION=6041319]dsa8310[/MENTION]
[MTCB Software Development] 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! :)
[MTCB Software Development] Oldpapa49:
Exactly what I did. A setup that I have never seen before had to be done. Great Job.
[MTCB Software Development] dsa8310:
It's Open GApps' merit, not mine. Once the setup is done, everything else falls into place.
[MTCB Software Development] warata:
hi dsa I have one request as well.

I want HU to automatically stop google play music(or any other music player apk) when it starting the mtc-radio(or when HU goes to sleep).

This function can be granted by tasker, but I think that many people want to include it in ROM.
[MTCB Software Development] typos1:
Hes talking about the LP and the N kernel here, but I ve recently got an MTCD unit as well - I ve flashed the MTCD N test ROM on it and it ran fine (more free memory than L), but the kernel was 30.1.01+, this is the same kernel as L. Unless its a different version of 30.1.01+ ?

Anyway, I thought I d flash a "retail" image (MTCD units with RK3188/PX3 SoMs + 2Gb RAM have just gone on sale) and what I ve got is a blank screen, the buttons flash when the right buttons are pressed to get into recovery, even though this is an MTCD unit I m also getting a blank screen ! Of course it could just be coincidence.

I wonder whether [MENTION=6041319]dsa8310[/MENTION] and [MENTION=1415699]pcmender2005[/MENTION] used the "retail" ROM I ve just tried and not the earlier test ROM, if so maybe we could get a picture ?

Where did you get the version of N you tried [MENTION=1415699]pcmender2005[/MENTION] ?
[MTCB Software Development] thivamero:
+1000 :good::good::good::good::good:

This is a very good idea , the rom would be perfect with this.

Once on two when I put the default player, it tells me that it does not find the file or that the path of the file can not be found and therefore it play the next song... I do not know how to use tasker so poweramp that I adore, does not cut the radio and it is annoying

thanks
[MTCB Software Development] pcmender2005:
I tryed this one mate.

https://xdaforums.com/android-auto/...t/dasaita-android-7-1-1-headunit-px3-t3588871
[MTCB Software Development] typos1:
Right, there are a few versions in that thread !
[MTCB Software Development] pcmender2005:
The file name is HCT2_rk3188_7.1(20170426)
[MTCB Software Development] typos1:
Ah, ok, thats the test version, oh well thats that theory out the window then, lol . . .

. . . unless its the other way round and I flashed an MTCB/C version on my MTCD unit, I guess that may be possible (there are rumours that one company is making a 2Gb RAM N RK3188/PX3 MTCB/C SoM).

Fancy testing ? Lol
[MTCB Software Development] pcmender2005:
I will test anything to get n on our units mate.

---------- Post added at 01:29 PM ---------- Previous post was at 01:23 PM ----------

We're did you get ur MTCD unit from [MENTION=456516]typos1[/MENTION]
[MTCB Software Development] typos1:
ebay.
[MTCB Software Development] dsa8310:
Nah, Poweramp does yield audio focus to whatever other audio source takes over.
[MTCB Software Development] Johny DJ:
There is a poweramp xposed apk that stop the poweramp when opening the radio...or via versa...
[MTCB Software Development] dsa8310:
I have included the newer&better (KK) recovery.img in the firmware images from the OP.

Now both LP and KK images have an identical partitioning that would facilitate switching between them without delays - until you make up your mind . BTW, for me it's the Open GApps version, Kit-Kat.
[MTCB Software Development] thivamero:
for me too thanks it's very good
[MTCB Software Development] KaMu1219:
Did anyone get voice control in TomTom GO working? There is a button in settings of TomTom where you can switch on/off voice control, so it seems as voice control is supported in the Android version of TomTom.

But wake-up phrase "Hallo TomTom" (german) doesn't work.
[MTCB Software Development] elyl:
Are you running the KK version on your own system now instead of LP?
[MTCB Software Development] dsa8310:
Yes.
[MTCB Software Development] typos1:
Interesting, why the change after a year of L and 2Gb RAM ?
[MTCB Software Development] OverLordOfYou:
Dumb questions but would like an answer

I'm running Malaysk Feb 2017 RK3188 800X480 version 21 on my radio.

I was thinking on installing the 5.1.1 version you have on here but 2 things I have questions on.

1. To install would it be wiser/ better to go through recovery and install that way or do the "software upgrade" through the menu in settings?

2. There's part 1 and part 2 on the download update. So to be clear I need to install "update" with part 1 (with full wipe) then install "update" with part 2 right after ? - never had to do 2 updates back to back so trying to make sure those links aren't just mirrors.

3. Any screenshots of what everything looks like (main menu, clock etc)?
[MTCB Software Development] typos1:
1) Doesnt matter theyre both the same thing.

2) Put both parts in the same folder and right click "extract here" on the first part, it will auto extract both parts into one image.

3) No, it looks exactly the same as stock
[MTCB Software Development] dsa8310:
1)Use recovery. 2)Unpack the two parts on PC, you will obtain file update.img. 3)No, it's a classic KLD.
[MTCB Software Development] rockuman_ex:
I'm using one of your early build 5.1 (2016 august or something like that).

If i were to upgrade to your latest Open GApps version, should i wipe anything in recovery? or should i just flash?

And will i lose any data?
[MTCB Software Development] air0ne:
Hi there,

I'm trying to install your rom but I'm stuck at the loading screen (in loop).

I have a RK3188 MTCC KLD6 1Go

Did a wipe data and then installed it with clear all

Any idea what's happening?

Thx for helping me

---------- Post added at 06:37 AM ---------- Previous post was at 05:56 AM ----------

Nevermind... It took a while but succeeded in installing the rom... and I must say... it's much faster than the KK from Malaysk :D

Thx a lot for this release !!!
[MTCB Software Development] dsa8310:
Well, you should install firmware firstly, then immediately after it reboots, and just before the first start-up, re-enter recovery and perform a wipe all.

The idea is to do wipe all after the new/differently partitioned firmware is already flashed (by the first recovery run).

Then reboot and do the long restart, followed by a onetime automatic reboot, and then you enter the onetime Google setup (in case of the Open GApps version, recommendable), and so on. Though a MTCC unit will have a slightly different scenario because it must not overcome the screen display issues that are encountered by the MTCB units.

===

You may do a wipe all right now (followed by reconfiguration), just to be sure that all cache, data partitions are properly formatted. Same may be attained from the Settings/Storage menu, without the inconvenient of reconfiguration, but a wipe all from recovery seems a sure bet.
[MTCB Software Development] rockuman_ex:
So i dirty flashed this over my October 2016 firmware, all good, but i didn't see any speed increase.

So decided to flash and wipe all and start over.

Can feel the speed improvement straight away.

One thing bothers me is the auto brightness configuration.

How can i disable auto brightness completely?
[MTCB Software Development] Thhhza:
Hi dsa8310,

This didn't work for me but I finally had some time today to get the output of the GPS messages in the terminal window. Screen shots attached.
[MTCB Software Development] dsa8310:
Wow, you really are from the... different NMEA syntax!

I will add the $GNGGA case (beside the existing $GPGGA) as well, asap.

Thanks again for your feedback.

===

Ouch, right now, even the previous fix is wrong... I did not test it through...
[MTCB Software Development] dsa8310:
Upgrade of script /system/etc/install-recovery.sh:

install-recovery.sh

A must. It fixes the location algorithm used in brightness control by adding all NMEA syntax cases.

For convenience, firmware is updated in the OP.

DO NOT UPGRADE YET! Go ahead, update now.
[MTCB Software Development] dsa8310:
Please make sure that you get the latest script from post #213 above, there was a second iteration until the final release.

Essentially you get $GN... prefixed strings instead of $GP... ones, so now both cases are handled in an (even) optimized script.

(read my PM as well)
[MTCB Software Development] dsa8310:
Update to LP/mtcservice, to version:

mtcservice-2.50.apk

It's bumped to v2.50 just to skip a range of KK/mtcservice updates (v2.42 is latest for KK).

Recommended update as it will warn to reboot ASAP, via a toast message, about either an initially generated ro.serialno parameter, or a subsequent change of it (in preferences), whenever the service is (re)started (this happens at activity start as well, if enabled) or its activity gets paused (hidden).

No change of ro.serialno, no toast at all, as before.

To keep the two LP & KK versions in sync, I have also made a dummy derivation of class SwitchPreference, unnecessary under LP, but helpful as a workaround for a KK bug related to (vertical) scrolling in the preferences screen, when switches get reset with no apparent reason, just by scrolling.

Let me know if it has happened until now (in v2.38), because I cannot recall it...

I remind the role of ro.serialno - useful for TomTom GO internet access validation; should be kept same at the time of first TT GO run, for future map/voice updates.

However, do your utmost to register at least once as an installer of TT GO in the Play Store, otherwise validation will still fail. I have learned, from a discussion in the KK thread, that an xposed module, called Device Faker, would help with overcoming the issue of Play Store treating the HU as an unsupported device.

===

Firmware update in the OP will come at a later time.
[MTCB Software Development] iselfdevi:
How can we disable the auto dimming feature?
[MTCB Software Development] dsa8310:
See post #39 from the KK thread, and comment in post #139.
[MTCB Software Development] Thhhza:
Can confirm it's fixed now, thanks!
[MTCB Software Development] typos1:
Is this a typo ? :

https://www.chinavasion.com/china/w.../2_DIN_Car_DVD_Player/Android-5.1-Car-Stereo/

An RK3188/PX3 Android 6 stereo ! Looks like MTC

EDIT: it is MTC, but a note at the bottom says the processor has been changed to Intel Atom, so its an MTCD Intel Atom, oh well.
[MTCB Software Development] Johny DJ:
Could be... I just made modified update images for myself and I think if you use boot, kernel, kitkat recovery and system image from 6.0. could work on our mtcb/c units.

If someone wants to try I can build one...?
[MTCB Software Development] typos1:
I just edited my post, they changed the processor to Intel Atom but didnt put it in the title. :(

Happy to help with 6 or 7, I think 7 is more of a goer cos theres MTCD RK3188/PX3 7 now - [MENTION=1415699]pcmender2005[/MENTION] has already got an MTCD N ROM booting but a black screen, he could hear sounds though which sounds positive, he was gonna do it again and get some dmesgs and logcats, but not heard back yet, [MENTION=6041319]dsa8310[/MENTION] gave up on it.

I m happy to help try and get N working, deffo count me in, love for all of us to work together to do it :)

Three are some posts about it in this thread, cant remember what recovery was used in the end, maybe a good idea if you read them to see.
[MTCB Software Development] pcmender2005:
I have asked them to find out for us mate
[MTCB Software Development] pcmender2005:
I will try for you mate I have a mtcc but it's a 800 res
[MTCB Software Development] typos1:
I edited my post, its an MTCD Intel Atom. :(

Any luck with the logcats and dmesgs ?
[MTCB Software Development] pcmender2005:
No not yet mate my son became a dad over the weekend.
[MTCB Software Development] typos1:
Congratulations !

We dont want that one its for Intel, it wont work.

There are MTCD RK3188/PX3 Nougat ROMs in this thread, read it and your ll see, you can try them I think it was the first one that [MENTION=1415699]pcmender2005[/MENTION] got the black screen on, thats the one you want to try and ideally with the recovery that he used, maybe he can add a link and tell you what he did ?

There should only be minor modifications needed to make MTCD RK3188/PX3 N work on MTCB/C RK3188/PX3 units.

Please, read this thread, theres loads of info about it from a few weeks ago.

---------- Post added at 06:30 PM ---------- Previous post was at 05:50 PM ----------

In the MTCD RK3188/PX3 N ROM I found a file called "android.microntek.serial MTCD" I m sure the MCU has some control over the screen and I was wondering if replacing this file with the equivalent one form MTCB/C devices would help get a picture.
[MTCB Software Development] BrokenSpring:
Hello @ dsa8310 . Great Rom. Amazing work on it. I have installed it on my Pumpkin 7" double din but not really had time to play with it yet. It does feel much faster than the previous roms i have run on the unit.

I do have a few small and possibly stupid questions.

1. Once installed is there any extra setup to be done to have the open Gapps version working or is it just out the box all setup?

2. I still see the play store there does it need to be removed or replaced witht the open gapps store?

3. Are all the google sevices already disabled to speed things up or do we need to do that?

4. Does anybody have the latest TomTom GO apk so we dont have to use device faker to get it downloaded?

5. Will the mtc manager used in the malaysk rom and screenclocks still work on this rom or will extra setup be required.

Thank you in advance.
[MTCB Software Development] typos1:
Its all ready to go, no apps to remove, nothing needs replacing, you may have to set up google play on first boot.

Dont think you need device faker I think Tom Tom shoudl show up, but you may need to follow [MENTION=6041319]dsa8310[/MENTION]'s posts about settings up Tom Tom to get it working.

Yourll have to try the Malaysk apps and see.

BTW you dont have a Pumpkin unit, Pumpkin are sellers only, to find out what unit you have go to settings/about device, the letters after "MTCB" or "MTCC" will tell you what unit you have.
[MTCB Software Development] BrokenSpring:
Hi, great news so all's up and running as it should :good: :D

I got as far as the initial google setup and reboots, quick music file play and searching the app store for tom tom go which was not showing up.

The rom definately moves much smoother between apps, so can't wait to play with it more.

Unfortunatelu on baby duties till fri eve so will play with the rom properly over the weekend.

There were quite a few issues with bluetooth connectiong to obd devices, is that still an issue on this rom or is all ok?

Is the factory settings password still 126?

Yes sorry i can't fully remember what version it is ( could be mtcb-klg6) or i could just be making up numbers :laugh:
[MTCB Software Development] pcmender2005:
Just came across rockchip open-source don't know if it's any good for any devs.

http://opensource.rock-chips.com/wiki_Main_Page
[MTCB Software Development] typos1:
Interesting.
[MTCB Software Development] Johny DJ:
To get all the xposed modules to work you have to replace Mtcmanager in privapp with september rom from Dsa or Malaysk one.
[MTCB Software Development] dsa8310:
As mentioned in the OP, with the Open GApps version, a onetime Google comprehensive setup will be triggered automatically at first full run - but don't forget to "wipe all" from recovery before.

===

By tomorrow a new LP firmware will become available, a recommended update.
[MTCB Software Development] typos1:
Did you look earlier in this thread for the N ROM that worked with a blank sceen ? :)
[MTCB Software Development] dsa8310:
New firmware, using [MENTION=6114030]Petrows[/MENTION]' latest mtcservice, slightly adjusted to our needs, from post #87, and the new separate xposed module from post #94, has become available in the OP.

Upgrade by firstly updating mtcservice to v2.60, then,

without another reboot,

go directly to recovery and update the whole firmware without "clear all" or "wipe all" -- preserving all configurations, if your previous firmware was mine as well.

If installing the firmware for the first time, do a "wipe all" afterwards.

You will benefit from all the developments in mtcservice (e.g. Spotify support) that we lost in transition, while still defeating, with the mtcxp xposed module - configurable - the botched attempt of Klyde at selling their MTCC units as "incompatible" with our MTCB ones.

Read also post #97 about the significance and role of mtcservice-2.60 and mtcxp-1.0.

===

And I am back under LP - Open GApps (firmware has been tested)... :)

===

And yes, LP is switching between apps seamlessly, while KK has its breaks, affecting, for instance, the background play.
[MTCB Software Development] Johny DJ:
Yes I did check everything and also tried to figured out what is wrong but with no luck, because the lib files are showing to different locations like lollipop ones, will check again later, but I also think that android 7 bring optimizations we want.
[MTCB Software Development] typos1:
I think also we need to know the differences in software between MTCB/C and MTCD to help et it to work.
[MTCB Software Development] dsa8310:
A reminder to all party crashers and thread polluters, please debate firmware versions other than 5.1.1 elsewhere.

Okay pumpkin(s)? :) https://www.youtube.com/watch?v=H42jVUavXiA
[MTCB Software Development] pczao:
I agree with you. There is a lot of noise in the thread.

Another thing is people telling others what to do. Why don't you do yourself?
[MTCB Software Development] typos1:
Yawn.

It was you who changed the thread title to "5.1.1." after engaging in discussions about Nougat yourself, pumpkin. :)
[MTCB Software Development] Thhhza:
Agreed, I don't see why this thread has to keep being pestered with talk about Nougat when there's already a dedicated Nougat for RK3188 thread: https://xdaforums.com/android-auto/mtcb-android-head-unit-general/nougat-t3623303

Whatever this thread may have been at one point, it's clearly now just about dsa's 5.1.1 ROM.
[MTCB Software Development] dsa8310:
Right, it never was about anything else but my (5.1.1) firmware. The other peer thread of mine is about my other (4.4.4) firmware.

I can ignore ignoramuses but not all users can filter out noise. So other discussions should be hosted elsewhere.

That official development for our units has been phased out, it's disturbing to recall, old news...

Who let the dogs out?! :)
[MTCB Software Development] rockuman_ex:
It's a pity that I'm still on his ignore list... For whatever reason... So i can't ask questions....
[MTCB Software Development] typos1:
No, it was originally about "RK3188 firmware" and you discussed Nougat.

Just post as normal as if you werent on his ignore list, thats what I do, hopefully another user will ask for you.
[MTCB Software Development] dsa8310:
I have also released the MicroG enabled KitKat 4.4.4 firmware for MTCB/MTCC, rk3188 units. People interested in testing it could pick it up from post #107.
[MTCB Software Development] thivamero:
The LP version with micro gapps works very well for the moment, I managed to activate my poweramp
[MTCB Software Development] warata:
Well then I'll report the result of the new firmware (KK-microG) test.

Boot time obviously a few seconds faster than openGver.

Unfortunately I could not sign in to my Google account.It stops at the scene of the attached image(sign in button doesn't work).

Of course I've enabled both Xposed and fakegapps.