MTCB/MTCC rk3188 (5.1.1) Firmware with an xposed set of MTC apps

[tariqkhan.co.uk]

Thank you for the help here!
I'll try that when I go for a drive after work.

As for the HW modd, it's the 7floor modification, which provides a better sound from our MTCC. The SW is already installed, even thought it's disabled in Xposed since the HW is still stock.
"Basically what we need to do is to re-route the I2C control bus of Sound Processor from the MCU to the Android Board."

Do you know if there is a YouTube video filming how the hardware mod is carried out?

 

[ode_joy]

Do you know if there is a YouTube video filming how the hardware mod is carried out?

You should already know the author's Topic, I suppose:
https://forum.xda-developers.com/an.../mtc-sound-controlling-bd37xxx-sound-t3234660

And the only KLD post about this modfication (my MTCC is KLD MCU):
https://forum.xda-developers.com/showpost.php?p=63520630

There's also a youtube video for KGL with this modd:
https://www.youtube.com/watch?v=tOr9TUaOqOI

Hope I've helped!

 

[descargas1000]

Hi, the rom is very fast, but my modem 3g does not works in this rom.
I need change or add something in the configuration rom?

 

[ode_joy]

Does anyone has the "Element" option on Settings, to change the LED colour available? Did you change anything?

 

[typos1]

Does anyone has the "Element" option on Settings, to change the LED colour available? Did you change anything?

You ahve to enable it in factory settings and reboot about 5 times for it to appear. It Wil only work if you actually have RGB LEDs.

 

[ode_joy]

You ahve to enable it in factory settings and reboot about 5 times for it to appear. It Wil only work if you actually have RGB LEDs.

Yes I have. When with malaysk ROM, the factory settings was as RGB and the LEDs where white. Changed in factory to R and it appeared at the time.
I'll try your method, even change to R to RGB and vice-versa. Thank you!

BTW, I've installed Car Launcher, and like to set the music app, but only appears as option YouTube (only media APP I've downloaded).
Wondering if anyone has another better music APP and managed to set as default in this launcher...?

Enviado do meu A0001 através do Tapatalk

 

[descargas1000]

Hi,

i want to use in this rom the program klwp for the wallpaper, but i get the message "your device lacks live wallpaper support, this app cannot work without it."
How can i solve this?

i attach the image.
Thank you!

i66.tinypic.com/2hgfmhj.jpgxxx

 

[Johny DJ]

You have to pull out from full version wallpaper apps because I deleted a lot of apps for better performance.


Sent from my iPhone using Tapatalk

 

[appex47]

Hi,

i have installed your ROM its work very well, but i have an problem with the youtube app. I have installed it from the google play store and i watch an video i have the highest quality of 480p with the malaysk rom i had 720p. I tried apps like yourtube+ or App Settings there i changed the resoulution to a higher one and i had the option for 720p but its looks very ugly. Anyone know how to fix the problem?

 

[NaviPR]

Interesting software, but there seems to be a number of issues with it.

The first unit we tried it on was a KLD 5.1 RK3188 (for a Mazda CX-5, but that doesn't matter here).

During the first installation we used the microGaps version. When it was done, no modules or software was installed besides the DSA MTC module in Exposed. No "Disable software", no nothing.
Then we tried openGapps. Something weird happened here, because the software reacted as if it was installed on a smartphone, because before it booted it gave us a welcome screen, typical of what you would see running an Android phone for the first time. After that we used the guide but there was absolutely no way to connect to the Play Store.
After that we ran the first software again - microGaps - this time it all went fine, with all the modules and we could access the Play Store.

Afterwards we tried installing the microGaps version on a KGL 5.1 RK3188 (this time for an Audi A4).
The first install started fine, but within a minute it completely BRICKED the RK3188. There was no response from the unit. At first, the LED lights in the front panel worked by themselves for a couple of minutes, but then died. We couldn't get it into recovery, using Malaysk's recovery cards didn't work. We had to replace the processor.
We tried installing the software and the same thing happened AGAIN.

Why is this not installing properly on KLD units at the first try and why did it brick a 5.1 KGL RK3188 - twice?

 

[tariqkhan.co.uk]

Interesting software, but there seems to be a number of issues with it.

The first unit we tried it on was a KLD 5.1 RK3188 (for a Mazda CX-5, but that doesn't matter here).

During the first installation we used the microGaps version. When it was done, no modules or software was installed besides the DSA MTC module in Exposed. No "Disable software", no nothing.
Then we tried openGapps. Something weird happened here, because the software reacted as if it was installed on a smartphone, because before it booted it gave us a welcome screen, typical of what you would see running an Android phone for the first time. After that we used the guide but there was absolutely no way to connect to the Play Store.
After that we ran the first software again - microGaps - this time it all went fine, with all the modules and we could access the Play Store.

Afterwards we tried installing the microGaps version on a KGL 5.1 RK3188 (this time for an Audi A4).
The first install started fine, but within a minute it completely BRICKED the RK3188. There was no response from the unit. At first, the LED lights in the front panel worked by themselves for a couple of minutes, but then died. We couldn't get it into recovery, using Malaysk's recovery cards didn't work. We had to replace the processor.
We tried installing the software and the same thing happened AGAIN.

Why is this not installing properly on KLD units at the first try and why did it brick a 5.1 KGL RK3188 - twice?

Not sure about the bricking? or the KGL?

I've been running the MicroG version for a while now and have installed it twice. Xposed modules are disable by default and you have to activate them yourself. I find this convenient as I don't actually need all the installed modules and actually delete a few of them. I was sure to follow the install instructions very carefully though. My unit is also a KLD.

 

[typos1]

Interesting software, but there seems to be a number of issues with it.

The first unit we tried it on was a KLD 5.1 RK3188 (for a Mazda CX-5, but that doesn't matter here).

During the first installation we used the microGaps version. When it was done, no modules or software was installed besides the DSA MTC module in Exposed. No "Disable software", no nothing.
Then we tried openGapps. Something weird happened here, because the software reacted as if it was installed on a smartphone, because before it booted it gave us a welcome screen, typical of what you would see running an Android phone for the first time. After that we used the guide but there was absolutely no way to connect to the Play Store.
After that we ran the first software again - microGaps - this time it all went fine, with all the modules and we could access the Play Store.

Afterwards we tried installing the microGaps version on a KGL 5.1 RK3188 (this time for an Audi A4).
The first install started fine, but within a minute it completely BRICKED the RK3188. There was no response from the unit. At first, the LED lights in the front panel worked by themselves for a couple of minutes, but then died. We couldn't get it into recovery, using Malaysk's recovery cards didn't work. We had to replace the processor.
We tried installing the software and the same thing happened AGAIN.

Why is this not installing properly on KLD units at the first try and why did it brick a 5.1 KGL RK3188 - twice?

Pointless using the openGapps one if youve only got 1Gb RAM, use microG, you obviously didnt set it up right. The welcome screen is normal.

I ve installed this ROM many times and not had a problem like that. Sometimes for whatever reason flashing can go wrong, I was going to suggest thats happened to you, but to get it again suggests there might be something wrong with your motherboard. No one else has reported it bricking their unit.

 

[Johny DJ]

I have KLD mazda 5 rk3188, no problems and tested all of them before release, no problems...
Try to flash twice in a row if doesn’t boot, should be ok.


Sent from my iPhone using Tapatalk

 

[NaviPR]

Not sure about the bricking? or the KGL?

I've been running the MicroG version for a while now and have installed it twice. Xposed modules are disable by default and you have to activate them yourself. I find this convenient as I don't actually need all the installed modules and actually delete a few of them. I was sure to follow the install instructions very carefully though. My unit is also a KLD.

I didn't say the modules were disabled. They were not INSTALLED.
When I first installed the firmware through recovery with formatting (like I do with any other update) no other module was installed besides dsa's module. Nothing else was on the list besides that one.
Just wanted to clear this up.

Pointless using the openGapps one if youve only got 1Gb RAM, use microG, you obviously didnt set it up right. The welcome screen is normal.

I ve installed this ROM many times and not had a problem like that. Sometimes for whatever reason flashing can go wrong, I was going to suggest thats happened to you, but to get it again suggests there might be something wrong with your motherboard. No one else has reported it bricking their unit.

Every flash goes fine, then all of a sudden two CPUs die one after another.
When was the firmware ever dependent on the motherboard?
This is a MTCB unit, so everything should work fine.

In all cases where flashing a new firmware caused problems, like errors or straight up bricks, only the CPU suffered, and 100% of the time after we replaced it a new firmware could be flashed without any problems on the same board.

I have KLD mazda 5 rk3188, no problems and tested all of them before release, no problems...
Try to flash twice in a row if doesn’t boot, should be ok.

Well, it worked both times, just the modules didn't install at first.

 

[tariqkhan.co.uk]

I didn't say the modules were disabled. They were not INSTALLED.
When I first installed the firmware through recovery with formatting (like I do with any other update) no other module was installed besides dsa's module. Nothing else was on the list besides that one.
Just wanted to clear this up.

OK, sorry, misunderstood what you were explaining.

I followed the advice of erasing 3 times before updating the ROM. I think typos1 has mentioned to do this before. Either way, I am not sure why it is not working for you. I do not know of any other users who have experienced similar issues to you either.

 

[typos1]

I didn't say the modules were disabled. They were not INSTALLED.
When I first installed the firmware through recovery with formatting (like I do with any other update) no other module was installed besides dsa's module. Nothing else was on the list besides that one.
Just wanted to clear this up.

Every flash goes fine, then all of a sudden two CPUs die one after another.
When was the firmware ever dependent on the motherboard?
This is a MTCB unit, so everything should work fine.

In all cases where flashing a new firmware caused problems, like errors or straight up bricks, only the CPU suffered, and 100% of the time after we replaced it a new firmware could be flashed without any problems on the same board.

Well, it worked both times, just the modules didn't install at first.

Sorry to hear of your problem.

The modules have to be installed, its no big deal.

I suggested the motherboard because many, many people have used this ROM (including me, I ve flashed it on several different units) and not one person has reported this problem, you said you have a new SoM and it happened again, so I think this points to the motherboard (the ROM and SoM having been eliminated).

Or its some other unknown problem. If it was just a blank screen I could suggest its an MCU issue and maybe @dsa8310's MCU fooling trick has failed meaning the screen is blank.

 

[NaviPR]

OK, sorry, misunderstood what you were explaining.

I followed the advice of erasing 3 times before updating the ROM. I think typos1 has mentioned to do this before. Either way, I am not sure why it is not working for you. I do not know of any other users who have experienced similar issues to you either.

No problem
I skimmed the thread a little bit and also haven't found anyone with the same problems as me, so I thought I'd ask to see if anybody experienced similar problems.

Sorry to hear of your problem.

No biggie, fortunately we had some CPU's to spare, but to be honest it made us get scared of installing this firmware on other MTCB RK3188 KGL units.

The modules have to be installed, its no big deal.

I suggested the motherboard because many, many people have used this ROM (including me, I ve flashed it on several different units) and not one person has reported this problem, you said you have a new SoM and it happened again, so I think this points to the motherboard (the ROM and SoM having been eliminated).

Or its some other unknown problem. If it was just a blank screen I could suggest its an MCU issue and maybe @dsa8310's MCU fooling trick has failed meaning the screen is blank.

Both times the update failed after about a minute; in both cases there was nothing we could do, like go into recovery and such. The LEDs also stopped working.

 

[azuman]

Hi guys. I installed last 3.9 update, opengapps version, but I don't know why, after installation, I have lost, or better said, I don't have the notification bar on top, doesn't appear... Is there any way I can get it to appear? Dunno what happened... thanks!

 

[tariqkhan.co.uk]

Hi guys. I installed last 3.9 update, opengapps version, but I don't know why, after installation, I have lost, or better said, I don't have the notification bar on top, doesn't appear... Is there any way I can get it to appear? Dunno what happened... thanks!

You need to follow the instructions in the first post. It states that you need to enable an exposed module.

 

[azuman]

You need to follow the instructions in the first post. It states that you need to enable an exposed module.

thanks. I know about that, did it already before (had the microg version instead) but dunno why the status bar doesnt appear... all the xposed modules are activated, and tried deactivating them, rebooting, and activating them again and rebooting, but no luck... I guess i'll have to reinstall again :S hopefully a dirty flash, as I don't want to re-install all my apps! thanks again!