[ROM][RK3188][HD] Malaysk ROMs Lollipop 5.1.1 for any yet known MTCB-Device

Dreadnaughtz

Member
Jul 7, 2016
16
2
0
What's involved in creating a ROM for a MTCB Headunit? Can I pick up a vanilla AOSP ROM (say v6.0) and cook in all the libraries, app, etc using an older ROM (say v4.4.4?)? I'm I missing something big here?
 

TT_Vert

Senior Member
Sep 11, 2010
1,799
226
0
What's involved in creating a ROM for a MTCB Headunit? Can I pick up a vanilla AOSP ROM (say v6.0) and cook in all the libraries, app, etc using an older ROM (say v4.4.4?)? I'm I missing something big here?
There is another layer of coding that acts as a conduit between the hardware (MCU) and the android OS.
 

Dreadnaughtz

Member
Jul 7, 2016
16
2
0
There is another layer of coding that acts as a conduit between the hardware (MCU) and the android OS.
Good point. But the MCU is a separate file to the ROM. Could I use reuse the existing MCU firmware and cook a new ROM based on my logic above? (I assume the MCU firmware could be used on higher versions of Android as long as the API command used are still available)
 

jbleasdale

Senior Member
Feb 16, 2007
101
24
38
Is there any way to get a 1TB portable drive to work with a MTCB unit using this ROM? Would it work if I could add power to the portable drive?
I'm planning on getting this MTCB KLD unit....

http://www.ebay.com/itm/8-2-Din-And...944270?hash=item43eef68d4e:g:i3oAAOSwH6lXQ8sl

Any and all advice is very much appreciated. Thank you
This should work fine, although I would recommend using an SSD if possible.
I have a 480GB SSD connected to my Joying unit running the Booroondook ROM (and previously Joying stock) with no issues.
I did use a traditional HDD previously and, while it worked, it was so slow to index my music library (30k tracks) that I moved up to the SSD with much better results.
If you are using it mostly for video (and therefore far fewer files) an HDD should be fine.
 

mswguitar

Senior Member
Apr 14, 2009
76
32
0
Las Vegas
Anyone else having an issue with Google Maps taking forever to start up with this ROM? Sometimes it take several minutes to come up, especially if I start it from a Directions widget. These worked fine on KK but it's basically unusable on this one.
 

THXWOW

Senior Member
Aug 12, 2008
60
9
0
This should work fine, although I would recommend using an SSD if possible.
I have a 480GB SSD connected to my Joying unit running the Booroondook ROM (and previously Joying stock) with no issues.
I did use a traditional HDD previously and, while it worked, it was so slow to index my music library (30k tracks) that I moved up to the SSD with much better results.
If you are using it mostly for video (and therefore far fewer files) an HDD should be fine.
May I ask how precisely you got it to work?
What is your setup like?
Thank you
 

jbleasdale

Senior Member
Feb 16, 2007
101
24
38
May I ask how precisely you got it to work?
What is your setup like?
Thank you
I have a VW Golf Mk6 + Joying HU + Sandisk 480GB SSD.

The Joying HU has 2 x USB socket cables from the rear which I routed through into the back of my glove box. The SSD is connected to the USB socket at the end of one cable using a cheap USB to SATA adapter. This needed to be a USB2 only adapter as the MTCB devices don't seem to cope with USB3. Once connected this just sits in my glove box.

The SSD is automatically mounted shortly after the HU boots (nothing required to make this work).
I use PowerAmp for my music collection and tell it to index only the SSD. I also configure it not to scan on startup, meaning that the SSD is accessible very shortly after the unit boots.

I take the SSD plus adapter out of the glove box every week or so and sync it with my music collection at home then, once back in the car, tell PowerAmp to perform a rescan, bringing its library up to date.

Works really well - I always wanted to have my full music collection (+cover art) in the car and am really pleased with this setup.