yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] dsa8310:
Updated, slightly improved:

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

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

mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar

mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar

Could be installed without "wipe all", only if overwriting the previous microg version.

===

Upgraded links have been moved to post #354. A recommended update!
[MTCB Software Development] elyl:
I have a KLD6 MTCB unit, do I need to flash a different MCU before I install DSA's ROM? I think I have 2.86 at the moment. Not sure if I should flash an MTCC one or not (and is it right that I can use KLD9 on my KLD6?)
[MTCB Software Development] typos1:
You dont NEED to, but MTCC KLD9 v2.98 will mean the radio app finally stores stations and generally its best to have the latest MCU, yes you can use it on your unit.
[MTCB Software Development] elyl:
Cool, thanks! And can I still use the 2.98 version even if I flash a KitKat ROM?
[MTCB Software Development] typos1:
Yep.
[MTCB Software Development] dsa8310:
WiFi Discussion

The internal wifi card works well, and even better with an external antenna.

Further improvement, with an external USB wifi adapter. Here there are two issues: finding a supported adapter and having it selected as default instead of the built in one.

The wifi USB adapter should be chosen based on its idVendor:idProduct pair, among those listed in this file:

SupportedDevices.txt (n.b. device 0bda:8176 is on list, actually the default wifi device; 0bda:8175 is NOT - it landed there inadvertently, as a mean of patching out, from kernel, of the real wifi device which would become disabled - it was a quick hack for disabling the internal wifi (very efficient)... sorry about that, it's gone now). It's an extended list including also 3G modems, other devices, different from the wifi ones, but a site like WikiDevi would help with identifying an available wifi device.

It should also work effectively, based on the existing kernel built in drivers (which are rather outdated), so it's a matter of luck. I found such adapter, it's the Edimax EW-7612UAn V2, on list with id 7392:7822.

Enabling the external USB device could be done via software, or by removing (un-soldering) the internal wifi card and by making an extra, external, USB port out of it (I did it, just get a proper +5V supply to it, instead of the existing +3.3V pin; the other (three, incl. ground) data pins are OK).

The easy, software way, is done by including in script /system/etc/install-recovery.sh an "unbind" command (for the internal wifi card), which should be executed whenever the USB system is powered on (I guess) (execute "echo 2-1.2 >/sys/bus/usb/devices/unbind") Placement in script, I can specify it, if interested. The "ugly" hack for disabling wifi, mentioned above, would work as well, unless the external USB wireless adapter would have the very same (0bda:8176) id (e.g. the so called Odroid WiFi Module 3, untested as yet, but promising, with detachable antenna?).

Finally, is it worth doing it? The answer would be yes for people really having trouble with the internal wifi, or trying to improve throughput with a better external device.

I did it hoping to get rid of wifi errors during a big map downloading for TomTom GO. But it did not work as expected... Puzzling enough, while wifi gets disabled, exactly as before, like the internal card did (with three error messages caught by "dmesg"), the downloading could be switched over to wired Ethernet, which I have, with an external USB Ethernet adapter -- USB also! --, and it continues then unabated, so it's not the USB system at fault, what is it?! A thermal thing?! Search me...

I will test the wifi system outside TomTom as well (with busybox wget ...), and I will keep you posted.

===

It's solved, the DWC OTG driver was raising the errors, but I found a workaround which fixes the wifi, making hardware mods pointless (unless having a defective internal wifi card and/or hoping better speed with an external wifi usb adapter).
[MTCB Software Development] dsa8310:
WiFi Workaround

This updated

install-recovery.sh

script includes a wifi workaround that guarantees downloading of arbitrary lengthy data (e.g. a big TomTom map) without fiddling manually with the wifi settings (on/off).

If using an external wireless USB adapter, that is on a different port, an adjustment is necessary (string 2-1.2 becomes 2-1.4), understandably, and as well as for disabling the internal wifi card.

This version is a necessary upgrade.

---------- Post added at 10:08 PM ---------- Previous post was at 09:50 PM ----------

For convenience, the updated images, including the wifi workaround in the latest install-recovery.sh script:

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

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

mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar

mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar

Links have been updated in post #396.
[MTCB Software Development] dsa8310:
I hope it was not just my HU having wifi transfer issues, but I am glad I could fix it, at least for myself, anyway. :)

Pausing a 6 GB map downloading, repeatedly, switching manually wifi off and back on, was unbearable.

I am not particularly proud of the USB reset workaround (with usb_modeswitch), it could mean that the USB controller is somehow "overstretched", but it was an effective remedy.

===

How to check out the issue and its fix: make a big transfer, say 500MB, with any suitable app, or in a terminal (Termux) execute "busybox wget -O /dev/null <a big file URL>", and watch for the wifi icon in the top bar: after about 100MB it will shortly disappear, and in 5 seconds, on average, it will come back, and wget will continue the briefly stalled transfer. Disappearance is caused by the DWC_OTG error, reappearance is the fix kicking in, automatically. Once in error/fix mode, the sequence will happen repeatedly until the transfer (happy) ending. Thankfully, TCP/IP is a resilient algorithm... :)
[MTCB Software Development] Oldpapa49:
[MENTION=6041319]dsa8310[/MENTION], thanks for your work and efforts on the ROM. Very much appreciated.

I still do not know if you are still upset with me, but I always liked what you have done, for your self and others.

Wayne
[MTCB Software Development] dsa8310:
Wayne, it was NOT the users but the forum policies and their abuse that bothered me. Water under the bridge, though I can't "see" you still... :)
[MTCB Software Development] EagleSoldier:
Hi [MENTION=6041319]dsa8310[/MENTION],

thank you very much for your hard work :)

Love your work.....

Is there a chance to get a dsa 4.4 Rom with MicroG ?

5.1 runns god and fast, but 4.4 better and faster :)

Best regards
[MTCB Software Development] dsa8310:
No, I am sorry to disappoint you, but I cannot maintain other versions than my own.

But if you have a rooted 4.4 KK (and xposed), simply remove the Google stuff (say, with a root explorer), as described on MicroG's official site, do a wipe all from recovery, and then proceed with installing the MicroG apps. That is exactly what I did, but working directly on ROM's system (and oem) partition(s).

If not, upgrade to 5.1.1 Lollipop, it's fast&furious, even without (my) 2GB of RAM...
[MTCB Software Development] typos1:
NOUGAT !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Well, sort of - I ve discovered that., as well as selling RK3368/PX5 octacore Marshmallow MTCD units, Hotaudio have released an RK3188/PX3 quadcore MTCD unit that runs Nougat and has 2Gb RAM.

This means there are now MTCD Nougat images around, surely it would not take that much to make and MTCB/C version ??

Hotaudio MTCD threads :

https://xdaforums.com/android-auto/...t/dasaita-android-7-1-1-headunit-px3-t3588871

https://xdaforums.com/android-auto/...asaita-mcu-updates-rockchip-px5-octa-t3575155

Latest MTCD RK3188 ROM :

https://yadi.sk/d/umCvHqCDzHccr/RockChip PX3/Android 7.1?force_show=1

[MENTION=6041319]dsa8310[/MENTION] might very well be interested in this, unfortunately I am on his ignore list so ANY mention of my name will not be seen by him, if anyone wants to quote this post with all mentions of my name REMOVED, so he sees it, feel free . . .
[MTCB Software Development] Jacklad:
Hey DSA! I finally got your MicroG setup to work - did a little reading and found that if the BlankStore id generator doesn't work with your regular gmail account, if you set up a new account on a device that is currently running Gapps, it should give you an Android ID that will work on the Android Market sign in - it took a few tries and a few errors from the .bat file to generate an ID, but it worked - once I signed in with that ID in the market, it still gave me the opportunity to sign in to the Google apps is use (Maps, PLay Music, Gmail, etc.) with my normal account info - so far, working great, and super snappy - it's by far the only 5.1 rom that I have been able to actually use as a daily driver on my 3188 unit - thanks so much DSA - l know you've only taken a couple of stabs at this version, but so far I'm super happy! Looking forward to future tweaks and updates -
[MTCB Software Development] dsa8310:
I did generate the AndroidID with my regular gmail account by setting the "less secure app - to ON" configuration, here: https://myaccount.google.com/lesssecureapps?pli=1

Then command "java -jar android-checkin.jar <email> <password>", run on PC (Linux), gave me the necessary AndroidID (before the less secure configuration, it did not, it failed with an error, suggesting the required/mentioned configuration setup).

===

BTW, the Yalp Store app is included in this release and could be used with Yalp generated credentials to download all your apps (but the already paid ones).
[MTCB Software Development] pcmender2005:
[MENTION=6041319]dsa8310[/MENTION] ;72710067]NOUGAT !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Well, sort of - I ve discovered that., as well as selling RK3368/PX5 octacore Marshmallow MTCD units, Hotaudio have released an RK3188/PX3 quadcore MTCD unit that runs Nougat and has 2Gb RAM.

This means there are now MTCD Nougat images around, surely it would not take that much to make and MTCB/C version ??

Hotaudio MTCD threads :

https://xdaforums.com/android-auto/...t/dasaita-android-7-1-1-headunit-px3-t3588871

https://xdaforums.com/android-auto/...asaita-mcu-updates-rockchip-px5-octa-t3575155

Latest MTCD RK3188 ROM :

https://yadi.sk/d/umCvHqCDzHccr/RockChip PX3/Android 7.1?force_show=1
[MTCB Software Development] Tumke32:
I guess its not possible to make a mtcb/c rom with nougat. Otherwise there would be already marshmallow running at our devices. The Lollipop rom for rk3188 was official released for rk3188 mtcb/c machines, mm and nougat not (and will not).
[MTCB Software Development] pcmender2005:
They said that about lollipop wouldn't run on a MTCB 3188 but it does thanks to dsa3180 making it so.
[MTCB Software Development] typos1:
The RK3188 IS capable of running MM and N, it IS possible to make MTCB/C, no one has so far, but it IS possible.
[MTCB Software Development] Tumke32:
If you look it that way...yes then its possible. But all the custom roms released are based on a official android release from the Chinese carstereo software developers for mtcb/c.

It never happend before that someone made a custom android rom from the scratch for mtcb/c. So i believe it will never happen.

Maybe dsa can say something about the difference in the mtcb and mtcd roms. Maybe its possible to make a hybrid version of the mtcb and d rom.
[MTCB Software Development] dsa8310:
Right... If it was that easy, all Android devices would upgrade at the pace new Android versions are released. Pity...
[MTCB Software Development] typos1:
It is possible but way beyond my talents (well not without months of work using the internet for reference and I dont have the time) - I ve seen many devices have ROMs ported from other related devices far less related than the RK3188 MTCB SoM and RK3188 MTCD SoMs.

We know N will boot and run on an RK3188 (there are RK3188 tablets running it too) the hardest part would begetting it to run the apps that talk to the MCU correctly.

I dont think that any the devs who work on MTCB/C and MTCD ROMs at the moment have the skills to do this, I think they can only mildly modify existing ROMs - NOTE : this comment IS NOT meant to be derogatory to those devs.
[MTCB Software Development] typos1:
This is the best ROM for any MTC unit I ve seen and it has a screen lock !! :

https://xdaforums.com/and...2#post72727357

pity its only for MTCD.

(Feel free, anyone to re post this with all mentions of my name removed so a certain person can see it).
[MTCB Software Development] Tumke32:
E

I think dsa3180 absolutly made the best rom for lollipop. But dsa3180 did not invent the Lollipop rom for rk3180, It is based on an official release.

That said. Im verry happy with his latest rom, i think the first good working and fast Lollipop rom for MTCB/C
[MTCB Software Development] Jacklad:
Soo, how do I get to developer settings on DSA MicroG ROM - don't see where I can tap to get menu - sorry if this is somewhere in the billion threads, but I have done a few searches and can't find it - and it's probably the easiest thing....
[MTCB Software Development] Johny DJ:
[MENTION=6041319]dsa8310[/MENTION]

Is there any chance to get bluetooth icon visible all the time not just when connected, because sometimes the bluetooth is connected but the icon is not showing in statusbar...?
[MTCB Software Development] dsa8310:
Search me... :)
[MTCB Software Development] Jacklad:
Two small issues so for with MicroG ROM - Android Market crashes, have to retry a bunch to get it to stick when launched - also, getting the "app not responding" message when using Google Maps, but app is up and working fine - happens just about every time -

Can i sideload the actual Google Playstore, or does that defeat the purpose?

Other than that, thing seems pretty solid - as I've said before, in my opinion the ONLY 5.1 ROM I've tried that can truly be used as a daily driver - thanks again DSA!
[MTCB Software Development] Oldpapa49:
Hope someone corrects me if I'm wrong, But..

MicroG is a GoolePlay replacement.. Rather I think YALP is the replacement.

Apps that you paid for will not load via YALP.

The MicroG process is to remove Google stuff.. and replace it it with MicroG. The reason for GAPPS I think.

The folder that shows up as Market is the placement for Google Play I think. And I think it is a non functional app????

Myself I'm at a bit of lost on it. The last time I installed I did a bit better and little more understanding on how-to do it.

The ID part I'm still at a lost. But be on vacation in a few days and will not be using the car with the radio in it.. Taking the Red Challenger.. 3K miles to be added..
[MTCB Software Development] Jacklad:
The Android Market does function - for me it just takes a few tries to get it to connect and work - it will show installed apps & apps that have available updates -
[MTCB Software Development] dsa8310:
I know about this behavior. For steady operations I use Yalp Store, INCLUDED.

As I mentioned before, Phonesky.apk (also included in the OEM partition) is necessary, in my case, to make TomTom "connect" to the Internet - for its initial setup, map & voice downloading. Afterwords I re-replace it with BlanketStore.apk (again in the OEM), to avoid error messages.

There are threads/installers that deal with a more complete installation of all MicroG services together with Google Play Store (phonesky).

It's up to individual users to configure their HU since all MicroG apps could be replaced/removed (entirely) at will, as I did not put them in the system partition, on purpose.
[MTCB Software Development] elyl:
I've just installed DSA's ROM and am having some serious wifi issues. It won't connect to a hotspot for any longer than a second. I had no problems previously (stock or Malaysk's ROM), and could connect fine to the hotspot in my house from the car, or the one on my phone (in the car).

Any suggestions? I'm amazed at how quickly DSA's ROM boots and would hate to go back.
[MTCB Software Development] dsa8310:
Well, I "touched" networking in two places: file /system/etc/install-recovery.sh (probably not your case), and file /system/framework/services.jar - main suspect for you.

Try to use the original services.jar file. Use a root explorer to replace it.

===

What the new services.jar does is explained in post #253. So I don't think that it should be a problem for anyone. But if you say so, revert to the original. I need the new one, for my wired+wifi setup.
[MTCB Software Development] typos1:
As I said before you can flash any MTCB ROM on your device providing you pick one that matches your screen and processor type.
[MTCB Software Development] Candlemass:
Updated ROM for Eonon GA5153F (RK3188 Quad-Core - 800*480) with MCU: MTCB-ZD x.xx (original was MTCB-ZD v2.68 but haven't flashed this one to know the current MCU version) included, from EONON :

http://sbo2.net/cs_serial/ZD_RK3188_P_20151127.7z
[MTCB Software Development] typos1:
What unit is it, who is the ROM from ? - Eonon are just resellers, check your settings/about screen to see what unit you have.

EDIT: oops sorry, yours is a ZD unt, didnt see that !!
[MTCB Software Development] x-fashi0n-r0mance-x:
I have a problem since I flash the latest version of joying 800x480 RK3188 is reverse my touch and my touch frontage button no longer works ...

My MCU file is a MTCB-KZ-v2.81 do I flash the MCU Joying contained in the ROM ?

A solution ?
[MTCB Software Development] Candlemass:
Yes, it's a ZD unit. The most important thing is to get hold of that MCU for anyone interested, because it doesn't exist in the MCU db of the forum.
[MTCB Software Development] x-fashi0n-r0mance-x:
hello, I have a problem my touch screen is reversed from left to right?

Help me please
[MTCB Software Development] facar4:
Reversed from left to right

You must enter the setting on your car stereo Setting/Driving Setting/Reverse X-Mirror Off, leave it unchecked

[IMG="Setting/Driving Setting"][/IMG]
[MTCB Software Development] x-fashi0n-r0mance-x:
My problem :

https://www.youtube.com/watch?v=1-s3omB6myQ
[MTCB Software Development] m00n61:
Request a replacement. This is a hardware issue. Probably some sort of misaligned display connection cable but not something you can solve on your own.
[MTCB Software Development] x-fashi0n-r0mance-x:
I contacted the support they have provided to me by email Update / MCU original files I reflash my car stereo and alignment is perfect but when I flash a custom ROM or stock I have axis reverse Y, but Why ?

PS : Sorry for my English
[MTCB Software Development] Oberbergler:
Download Link

I found a download link in a italian forum:

https://mega.nz/#F!KMZnXTJC!zDFMlP4qgxEE6vQxt8rrrw!3QhFWAiA
[MTCB Software Development] lotherius:
Is it possible to upgrade without a wipe? I already have the 2GB mod firmware and lots of things installed.... Titanium Backup is so unreliable (it tends to lose configurations on apps recently)...
[MTCB Software Development] x-fashi0n-r0mance-x:
NEW Rom Joying Android 5.1.1 :

Date: Feb 22, 2016

Joying RK3188 Quad-Core - 1024*600 resolution can be downloaded at : https://mega.nz/#!8xZBBQqZ!QxgsIP0umdNLoaTSFjEmIvNqcv_vNiTm5dNXItKMPRg

Source : http://www.carjoying.com/Joying-blog/12.html
[MTCB Software Development] typos1:
Great news, now we gotta see if it works on other versions, they claim it wont, cant see why not though.
[MTCB Software Development] dc5daft:
According to the guys on the 4pda forum this is still kit kat and not 5.1.1 :(
[MTCB Software Development] typos1:
Oh :(
[MTCB Software Development] Musicman1973:
Joying Android Update from October (800x480).

I have downloaded it, but i can`t unpack it.

Winrar says that the file is unknown or defect !

Can you please reupp this Software ?

Thank you !

Best regards.
[MTCB Software Development] typos1:
Where did you download it from ?
[MTCB Software Development] Musicman1973:
I have downloaded it from this Thread here.

Joying RK3066 Dual-Core - 800*480 resolution

Joying RK3066 Dual-Core - 1024*600 resolution

These two are defect.

For the RK3188 Quad-Core the Files are ok !
[MTCB Software Development] Vitalit:
Hi i search Pumpkin 7" RK3188 1024*600 Factory Firmware.

Gesendet von iPhone mit Tapatalk
[MTCB Software Development] elyl:
It was actually the last ROM, not the most recent one you just posted. I'll try flashing your most recent one... I'll see about the MCU too. I have a KLD6, and I installed version 2.98, but I now see that's for KLD9, so I'll try the KLD6 2.97.
[MTCB Software Development] Johny DJ:
I tried but a lot of your posts doesn´t exist anymore so I couldn´t find anything related to bluetooth icon...
[MTCB Software Development] dsa8310:
I don't know, never do two changes in the same time... The latest firmware is in post #354.
[MTCB Software Development] typos1:
It doesnt matter that you have KLD6 - the most up to date MCU is MTCC KLD9 v2.98 and this works for ALL MTCB and MTCC units apart from some KLD and KLD5 (at last it allows storing of station names in the radio app).
[MTCB Software Development] dsa8310:
No, I never changed anything related to BT. So, either a functionality preexisted, or I don't add it, in principle.
[MTCB Software Development] elyl:
I'm still having wifi issues, even after clean flashing the lastest DSA ROM. Any more suggestions?
[MTCB Software Development] dsa8310:
Read post #380 - switch to the original services.jar file.
[MTCB Software Development] dsa8310:
BTW, the Ethernet Droid app can switch between wired and wireless networking, although the user interface is indeed "all jacked up"; but fortunately the On/Off button (for Ethernet) is accessible in the right side of my 800x480 screen: off for wired means on for wifi and vice-versa.

So, yeah, my "ingenious" services.jar modding is not necessary, after all... It doesn't hurt either.
[MTCB Software Development] elyl:
Yeah, I'm still getting the same issue when I switch the services.jar file.
[MTCB Software Development] dsa8310:
Well, then choose a different firmware for your HU...

You may also replace /system/etc/install-recovery.sh (with a root explorer, make sure it remains executable, owned by root) with this file: install-recovery.sh, it's the non wifi workaround version.

(then reboot)

This one: install-recovery.sh
[MTCB Software Development] elyl:
OK, this is weird. I can now connect to the wifi network in my house. I am still getting the same issue connecting to the wifi hotspot on my phone (S8). I'll do some more experimenting. Thanks for your help so far... I don't want to use any other ROM now!
[MTCB Software Development] dsa8310:
How should I put it: it had happened only to you. :)

===

The MicroG stuff is not "perfect" yet: for instance, apps bought via Play Store cannot verify their licensing, e.g. Poweramp - but fortunately, being launched early from install-recovery.sh (if present), as a service, it will work nonetheless, until the associated app is opened - then it stops playing, claiming that the licensing cannot be checked out (and only a reboot makes it play again).
[MTCB Software Development] Johny DJ:
My licenced poweramp is working and also verify licence from playstore I just have to reboot once that poweramp sees the licence, but I also had to do this without microG.

I am using microG as system app and 5.1.1. Playstore with disabled itself update and its working also I see paid apps on playstore and can download them.