[ROM][RK3066/RK3188][SD/HD] Malaysk ROMs Android 4.4.4 for any yet known MTCB-Device

[mikejclark]

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
New from September 18, 2016 for RK3066 800X480 (41 version)
Strongly recommend to do after installation recovery Wipe Data (penultimate paragraph) because it has changed the location of the system software in the partition is not the system (now all the additional applications and launchers safely removed from the Settings -. Applications if you do not need)

Could someone explain this please. Does this mean wipe data from recovery, so you lose all settings? Thanks

Sent from my GT-I9505 using Tapatalk

 

[typos1]

Could someone explain this please. Does this mean wipe data from recovery, so you lose all settings? Thanks

Sent from my GT-I9505 using Tapatalk

Yes, but you have to do it if you want FUSE.

 

[mikejclark]

Yes, but you have to do it if you want FUSE.

Ok thanks

Sent from my GT-I9505 using Tapatalk

 

[oscyp]

Could someone explain this please. Does this mean wipe data from recovery, so you lose all settings? Thanks

Sent from my GT-I9505 using Tapatalk

Wiping data means losing all of your settings and customization.
But if you were using any other FUSE ROM from MalaySK before - wiping data is not necessary (I did just an update without data wiping and besides that some things are just missing in a new ROM - like XposedMTC module, or Next Launcher, the rest is working fine and all of the setting were preserved).

So if your previous ROM was FUSE ROM - you can do just an update, but if this is the first FUSE ROM that you are going to use - you have to do the full wipe.

 

[mikejclark]

Wiping data means losing all of your settings and customization.
But if you were using any other FUSE ROM from MalaySK before - wiping data is not necessary (I did just an update without data wiping and besides that some things are just missing in a new ROM - like XposedMTC module, or Next Launcher, the rest is working fine and all of the setting were preserved).

So if your previous ROM was FUSE ROM - you can do just an update, but if this is the first FUSE ROM that you are going to use - you have to do the full wipe.

Great thanks. I also updated from previous version of this rom so won't bother wiping data. Cheers

Sent from my GT-I9505 using Tapatalk

 

[xWarrock]

Hi

i flashed the MalayskRom on my erisin 2046, working very fine!!

but screensaver, the km/h display does not work, it stays at 000 km/h .. :/

 

[moddedkodi]

Ok found it, search for XposedMTC. There is an option to put the volume indicator in the statusbar.


Sent from my SM-G935F using XDA-Developers mobile app

would be kind if you could post the info or link here for other .yes i did do a search

 

[rdavidowski]

Hi Malaysk

I received a replacement unit from Pumpkin model RQ0265, it is a 10.1 inch screen unit. It came with MCU 2.91. Well my problem is that I flashed your ROM 4.4.4 for RK3188 1024X600 Version 19 and my screen touch sensor has the X axis inverted. If I touch the screen on the right it reflects the touch point on the left side of the screen. The Y axis UP/Down is working like it should. I tried flashing older MCU (2.85 and 2.83) same thing and also tried MCU 2.97 also same thing. Now the thing is that if I flash the latest Malaysk 5.1.1 then the X axis gets corrected and it works like it should. I will like to run Malaysk 4.4.4 because 5.1.1 is sooooo slow and buggy. Can you please help me fixing this issue with the touch X axis being inverted on Rom 4.4.4?

 

[typos1]

Hi Malaysk

I received a replacement unit from Pumpkin model RQ0265, it is a 10.1 inch screen unit. It came with MCU 2.91. Well my problem is that I flashed your ROM 4.4.4 for RK3188 1024X600 Version 19 and my screen touch sensor has the X axis inverted. If I touch the screen on the right it reflects the touch point on the left side of the screen. The Y axis UP/Down is working like it should. I tried flashing older MCU (2.85 and 2.83) same thing and also tried MCU 2.97 also same thing. Now the thing is that if I flash the latest Malaysk 5.1.1 then the X axis gets corrected and it works like it should. I will like to run Malaysk 4.4.4 because 5.1.1 is sooooo slow and buggy. Can you please help me fixing this issue with the touch X axis being inverted on Rom 4.4.4?

5.1.1 is much faster than 4.4.4, but Malaysk's version is slower than stock, @dsa8310's mildly modded stock and @booroondook's 5.1.1. Have you tried the other custom ROMs ? If they work it would establish where the problem lies, ie with your unit or with his ROM.

You dont have a Pumpkin RQ0265" by the way, there is no such thing. What you have is a Klyde unit, sold by Pumpkin. I m guessing here because youve left off the MCU manufacturer identifier (the letters and number before the number.) If it is indeed a Klyde (KLD) unit then there is an MCU update to upgrade it to an MTCC unit.

 

[rdavidowski]

5.1.1 is much faster than 4.4.4, but Malaysk's version is slower than stock, @dsa8310's mildly modded stock and @booroondook's 5.1.1. Have you tried the other custom ROMs ? If they work it would establish where the problem lies, ie with your unit or with his ROM.

You dont have a Pumpkin RQ0265" by the way, there is no such thing. What you have is a Klyde unit, sold by Pumpkin. I m guessing here because youve left off the MCU manufacturer identifier (the letters and number before the number.) If it is indeed a Klyde (KLD) unit then there is an MCU update to upgrade it to an MTCC unit.

Thanks for responding. And yes I know it is a KLD. MCU versions 2.91(Came from Factory) and 2.97(Update) are both identifying the unit as MTCC. Still I flashed MCU versions 2.83 and 2.85 which identify the unit as MTCB but the touch sensor on the X axis still is inverted no matter what version of Malaysk Rom 4.4.4 gets installed on the unit. As soon as I install Malaysk Rom 5.1.1 it gets corrected so I a am deducing that is something with 4.4.4 Roms from Malaysk. Malaysk 5.1.1 does not play good with google maps or OK Google, they are slow as a snail and barely usable, that is why I say it is slow. When I try them on Malaysk 4.4.4 ver 19 even with the X axis inverted they run very fast. Also the DVD/CD application and Netflix App do not work on Malaysk 5.1.1 but they do on Malaysk 4.4.4. So this is the reason I want to run Malaysk Rom 4.4.4. Everything that I need runs on Malaysk 4.4.4 much better but I need to fix the Touch Screen sernsor X Axis. Can you help me with this or there is a setting for this on the Rom?

 

[typos1]

Thanks for responding. And yes I know it is a KLD. MCU versions 2.91(Came from Factory) and 2.97(Update) are both identifying the unit as MTCC. Still I flashed MCU versions 2.83 and 2.85 which identify the unit as MTCB but the touch sensor on the X axis still is inverted no matter what version of Malaysk Rom 4.4.4 gets installed on the unit. As soon as I install Malaysk Rom 5.1.1 it gets corrected so I a am deducing that is something with 4.4.4 Roms from Malaysk. Malaysk 5.1.1 does not play good with google maps or OK Google, they are slow as a snail and barely usable, that is why I say it is slow. When I try them on Malaysk 4.4.4 ver 19 even with the X axis inverted they run very fast. Also the DVD/CD application and Netflix App do not work on Malaysk 5.1.1 but they do on Malaysk 4.4.4. So this is the reason I want to run Malaysk Rom 4.4.4. Everything that I need runs on Malaysk 4.4.4 much better but I need to fix the Touch Screen sernsor X Axis. Can you help me with this or there is a setting for this on the Rom?

I ve not heard of this before. I would try @dsa8310's and/or @booroondook's ROMs to see if it effects them.

 

[PiotrekPoland]

How to turn on RDS?? RDS I do not work

 

[Wolf Hamburg]

in factory settings (pw=126)

 

[rdavidowski]

I ve not heard of this before. I would try @dsa8310's and/or booroondook's ROMs to see if it effects them.

I will try them both now and report back to you immediately. But remember DSA and Booroondook are 5.1.1 Roms they probably very different form Malaysk 4.4.4 being Kit Kat and not Lollipop.

 

[typos1]

I will try them both now and report back to you immediately. But remember DSA and Booroondook are 5.1.1 Roms they probably very different form Malaysk 4.4.4 being Kit Kat and not Lollipop.

Both are on the fileserver in my signature, its easier to install booroondook's that way.

As I said earlier - Malaysks ROM is quite laggy, booroondooks less so, dsa and factory are much faster than KK, so if youre looking for a faster L ROM then try those 2.

You are the only one that I know who has reported this before - everyone else has been able to use both KK and L with perfect touchscreen operation.

What is your full MCU version ? KLD, KLD6 etc

 

[rdavidowski]

Both are on the fileserver in my signature, its easier to install booroondook's that way.

As I said earlier - Malaysks ROM is quite laggy, booroondooks less so, dsa and factory are much faster than KK, so if youre looking for a faster L ROM then try those 2.

You are the only one that I know who has reported this before - everyone else has been able to use both KK and L with perfect touchscreen operation.

What is your full MCU version ? KLD, KLD6 etc

It is MTCC-KLD6-V2.97 but I also have tried MTCC-KLD6-V2.91 and MTCB-V2.85 and MTCB-KLD6-V2.83. All of the MCU's have the same Touchscreen symptom with any Malaysk 4.4.4 version.

 

[typos1]

It is MTCC-KLD6-V2.97 but I also have tried MTCC-KLD6-V2.91 and MTCB-V2.85 and MTCB-KLD6-V2.83. All of the MCU's have the same Touchscreen symptom with any Malaysk 4.4.4 version.

Yes, but your problem is that you found Malaysks ROM to be laggy, so youve tried his KK ROM and found a touchscreen problem not reported by anyone before. My suggestion is that you try the 3 other L ROMs that are available (factory, dsa's and booroondooks) as so far L is the only version that your screen woks correctly with.

Its best practise also, to run the latest fully working MCU, which for you is KLD6 v2.97, the MCU does not have anything to do with the touchscreen, that is controlled by Android.

 

[rdavidowski]

It is MTCC-KLD6-V2.97 but I also have tried MTCC-KLD6-V2.91 and MTCB-V2.85 and MTCB-KLD6-V2.83. All of the MCU's have the same Touchscreen symptom with any Malaysk 4.4.4 version.

Both are on the fileserver in my signature, its easier to install booroondook's that way.

As I said earlier - Malaysks ROM is quite laggy, booroondooks less so, dsa and factory are much faster than KK, so if youre looking for a faster L ROM then try those 2.

You are the only one that I know who has reported this before - everyone else has been able to use both KK and L with perfect touchscreen operation.

What is your full MCU version ? KLD, KLD6 etc

It is MTCC-KLD6-V2.97 but I also have tried MTCC-KLD6-V2.91 and MTCB-V2.85 and MTCB-KLD6-V2.83. All of the MCU's have the same Touchscreen symptom with any Malaysk 4.4.4 version.


I installed DSA Rom and the X axis inversion got corrected as when I install Malaysk 5.1.1. So I have to say that is something on Malaysk's 4.4.4 Roms that is causing this X axis inversion on the KLD (Pumpkin RQ265 10.1 inch Screen Head Unit) with MCU MTCC-KLD6-V2.97. Or any MCU version that I have installed so far. Can Malaysk get a look at this? I will be very grateful. Thanks

 

[Oldpapa49]

It is MTCC-KLD6-V2.97 but I also have tried MTCC-KLD6-V2.91 and MTCB-V2.85 and MTCB-KLD6-V2.83. All of the MCU's have the same Touchscreen symptom with any Malaysk 4.4.4 version.


I installed DSA Rom and the X axis inversion got corrected as when I install Malaysk 5.1.1. So I have to say that is something on Malaysk's 4.4.4 Roms that is causing this X axis inversion on the KLD (Pumpkin RQ265 10.1 inch Screen Head Unit) with MCU MTCC-KLD6-V2.97. Or any MCU version that I have installed so far. Can Malaysk get a look at this? I will be very grateful. Thanks

Can anyone say "rudder settings" in factory. That causes the touch or settings swapping

Sent from my SM-G930T using XDA-Developers mobile app

 

[rdavidowski]

Can anyone say "rudder settings" in factory. That causes the touch or settings swapping

Sent from my SM-G930T using XDA-Developers mobile app

Are you asking or are you suggesting me to try that?