yashsingh1/xdaforums huggingface dataset:
[MTCB Software Development] dsa8310:
Thanks, but it's a Windows tool involved...

Is there a description somewhere for the process?

Better, can you please explain your "recovery" experience?

And, would you be able to make a "dd" of your prepared SD, and publish it, to spare us the risk of using the Windows tool?

Anyway, I hope to never have to use it...

===

And some extra inquiry if you don't mind: do you still recall how your unit booted the nougat firmware? Was there at any time any image on screen? Like the car logo, or/and the boot animation?
[MTCB Software Development] dsa8310:
I am still analyzing the differences between the LP and N firmware, and from the differences between their respective boot.img partition contents, I can see that there are different "context" (framework) files referred to, that are missing from their corresponding system.img partitions.

So this might explain why the LP kernel that I experiment with (kernel+boot) cannot boot the unit through, it hangs somewhere, apparently after the boot animation, visible. That is good, but not good enough.

I could bring the missing files though from the LP system to the N one. Or just rename them? Symlink them?!

This painful process seems necessary because the N kernel&boot leads to no image on screen? Is this true, [MENTION=1415699]pcmender2005[/MENTION], no image on screen whatsoever, during the entire boot process, of the N firmware on your unit?

===

Of course, I could use the N boot.img partition with the LP kernel, then all N's system.img references would be fulfilled. Here it's one dilemma, for me: is partition recovery.img standalone, that is it does NOT care of the boot.img partition content, and will still work independently of the other boot.img partition?

Normally, the answer would be yes, since recovery.img has its own included ramdisk.

Wait a minute, recoveries are independent most certainly, because I did replace the LP recovery with the KK recovery, with no side effects?! Or just because the boot images were all along identical, the replacement was safe?! (we know the current LP firmware works, with its KK recovery)

So, I would really need a safety net here, taking another one for the team would ruin my upcoming vacation for sure... :)
[MTCB Software Development] typos1:
Someone should let him know that it will work on Linux if WINE/Playonlinux is used.

No that wont work, we thought of that a few years ago and even if it did we d have to make the ROM communicate with the MCU.

Would these framework files hes talking about be to do with the different software that MTCD units run to work with the different MTCB MCU ?

He doesnt seem to be aware that the MTCD stuff will have to be replaced with the MTCB stuff, even if the screen worked the ROM wouldnt fully function/function correctly because it will be talking MTCD language to an MTCB MCU.

Maybe it would be a good idea to analyse the differences between MTCB L firmware and MTCD L firmware first ?

Again, what I say will have to be repeated by others so dsa sees it.
[MTCB Software Development] dsa8310:
Good news, recovery is a standalone item.

It also appears that boot.img requires an appropriate configuration since basic stuff happens there. I will take a closer look at it later on this weekend.
[MTCB Software Development] pcmender2005:
Yeah I can do a copy of sdcard on a download for you do you want kk or lollipop? There was no boot image at all always a black screen mate from start to Finnish just sounds. If you get this to work on the units I will give you a nice donation.
[MTCB Software Development] dsa8310:
It appears that there is no longer need for it, thanks anyway, because I do now have a safe environment for testing. Keeping the (KK) recovery unchanged will let me experiment with the boot.img partition content, where all basic stuff seems to happen. For instance, the N boot partition in combination with the LP kernel produces no image at all - as you encountered with the N kernel as well. So it's boot's content that matters, not the kernel. Although the N kernel is also quite bad because it gives no image at all in the full LP context.

I'll dig into it...
[MTCB Software Development] Oldpapa49:
All I have to say is, "This is Really Kool Beans!"
[MTCB Software Development] pcmender2005:
Cheers dsa8310 we do really appreciate what you are doing for us with this rom. You are the only one that has stuck with us on these old MTCC units. Fingers crossed mate.

---------- Post added at 06:29 PM ---------- Previous post was at 06:21 PM ----------

@dsa8310

I have been sent by a member asking.

Would these framework files hes talking about be to do with the different software that MTCD units run to work with the different MTCB MCU ?

He doesnt seem to be aware that the MTCD stuff will have to be replaced with the MTCB stuff, even if the screen worked the ROM wouldnt fully function/function correctly because it will be talking MTCD language to an MTCB MCU.

Maybe it would be a good idea to analyse the differences between MTCB L firmware and MTCD L firmware first.
[MTCB Software Development] dsa8310:
Please refrain from quoting on someone else's behalf. I have my fair share of stalkers, thank you very much! :)
[MTCB Software Development] pcmender2005:
:svetius:
[MTCB Software Development] typos1:
Lol, replying to a thread is not stalking, dont flatter yourself. :)
[MTCB Software Development] dsa8310:
So far, so bad... no progress at all.

Brute force cannot be applied because each test takes an eternity to do, while educated guesses don't seem to help either.

I doubt very much if it's any worth going on. Sorry about that.
[MTCB Software Development] Thhhza:
My GPS works now after commenting out this code, thanks!
[MTCB Software Development] dsa8310:
Odd, can you also check out the output of this command, executed as root (execute su first) in a Termux terminal? When GPS is unobstructed, working, of course.

su
cat /dev/ttyS3 2>/dev/null | busybox sed '/^$GPGGA,.*,.*,.*,.*,.*,[12],.*/q'

Or, easier to type in, just

su
cat /dev/ttyS3

I cannot recall syntax, but I might know it when I see it...

===

Maybe instead of 1 or 2, you get a different digit as the 6th string after the $GPGGA prefix, with comma as separator? Could be 3 (meaning PPS fix)? Others?

===

Maybe I should have use pattern [^0] meaning anything but digit 0, which means invalid GPS fix! I will fix it in the very next release... after testing.

So, where are you located, at the antipodes?! :) Thanks for your feedback!
[MTCB Software Development] typos1:
Personally I think we need to focus on the differences between MTCB/C and MTCD as I think thats the problem - the RK3188/PX3 can run N.

Its just what the differences are - I was expecting a suite of apps that interacted between Android and the MCU, but, apart from a (lower case) mtcservice (which I think is different to petrow's MTCService app) I cant see any.
[MTCB Software Development] dsa8310:
I have updated all firmware images to include a fix in file install-recovery.sh.

People that have customized further their /system/etc/install-recovery.sh file, may simply edit line:

gpgga=`cat /dev/ttyS3 2>/dev/null | busybox sed '/^$GPGGA,.*,.*,.*,.*,.*,[12],.*/q' `

to become:

gpgga=`cat /dev/ttyS3 2>/dev/null | busybox sed '/^$GPGGA,.*,.*,.*,.*,.*,[^0],.*/q' `

(^0 instead of 12 between the square brackets)

The change will better accommodate NMEA GPS data output format, related to the automatic brightness control algorithm.
[MTCB Software Development] dsa8310:
Please update (again) your /system/etc/install-recovery.sh file with the version included above.

I hope the issue is now fixed, and so you will preserve the automatic screen brightness control capability as well.
[MTCB Software Development] typos1:
I knew I d seen MM for RK3188 somewhere !!

Just found it here on Roximo's site (a Russian seller selling Klydes) :

http://www.roximo.ru/upgrade-cardroid

Theres a link that they say is MM for MTCD RK3188, dunno whether its gonna be easier to port to MTCB/C than N or not, but theres Xposed for MM and lots of us use it.

Of course there is the possibility that its a miss-type and its MM for Intel Sofia units, but its worth checking out.

Theres also a couple of links to MTCB/C L from February, not checked it out yet, it could actually be earlier, but be nice to have a newer MTCB/C L image.

Probably a good idea for someone to re-post this post as their own ;)
[MTCB Software Development] EagleSoldier:
"I knew I d seen MM for RK3188 somewhere !!

Just found it here on Roximo's site (a Russian seller selling Klydes) :

http://www.roximo.ru/upgrade-cardroid

Theres a link that they say is MM for MTCD RK3188, dunno whether its gonna be easier to port to MTCB/C than N or not, but theres Xposed for MM and lots of us use it.

Of course there is the possibility that its a miss-type and its MM for Intel Sofia units, but its worth checking out.

Theres also a couple of links to MTCB/C L from February, not checked it out yet, it could actually be earlier, but be nice to have a newer MTCB/C L image."
[MTCB Software Development] Johny DJ:
Wooow nice, will check if its newer today.
[MTCB Software Development] EagleSoldier:
Thx goes to [MENTION=456516]typos1[/MENTION] ;)
[MTCB Software Development] djgus74:
Does it work bluetooth? I can not pair with my cell phone
[MTCB Software Development] typos1:
Does what work BT ?
[MTCB Software Development] djgus74:
Then it does not work in 5.1.1?
[MTCB Software Development] typos1:
BT works on all ROMs.
[MTCB Software Development] djgus74:
Well in my case, every time I put a 5.1.1 rom does not work for me
[MTCB Software Development] typos1:
Strange.
[MTCB Software Development] djgus74:
Yes it's strange. Tested with different terminals and always the same. However, with 4.4.4 without any problems. Is there anything special I should do in the factory settings?
[MTCB Software Development] typos1:
Make sure BT is set to BC6, if that doesnt work I guess you could try the other BT options.
[MTCB Software Development] djgus74:
Okay, I'll check it out and let you know if it worked. Thank you
[MTCB Software Development] dsa8310:
Relax, move along, nothing new to see here... I could "push" the built date of any firmware to 2099 when in fact it's still some early December 2016 version.
[MTCB Software Development] dsa8310:
Scouring the internet may be an enjoyable occupation, and gullible people may fall pray to such tactics. The question is: has your physician recommended this thread to you? :)
[MTCB Software Development] typos1:
Lol, there are places to look for MTC ROMs, Roximo is one of them, Klyde's software repository is another, you login to that everyday . . . well you did until they changed the password !

Right, so it IS old then, thought it may be, hence the "not checked it out yet, it could actually be earlier" bit.

Hes missed the crucial point though - a possible MM ROM for RK3188.
[MTCB Software Development] dsa8310:
My recommendation to all users: if you really have anything new to contribute, open a new thread. For this thread, I will answer only legitimate error reports related to my firmware, in the future. However, development for MTCB/MTCC rk3188 5.1.1 versions is apparently over...
[MTCB Software Development] EagleSoldier:
My physician recommended me some colorful pills :D

No I am joking, I think you are the only one person in the english forums who can make it real -> Bring us MM or L on our devices.

Me personaly dont need MM or L on these devices, because the RAM.

I am using the opengapps Rom since 1 week and Im very happy.

But I will go back to your 4.4 Rom because this one is the best for my unit (3188 1GB Ram).

Best regards :)
[MTCB Software Development] typos1:
Lol, ta for stating the obvious :)
[MTCB Software Development] dsa8310:
Right, wasn't you! :)

Just don't feed the trolls.
[MTCB Software Development] typos1:
Havent seen any trolls in this thread, just some of us trying to get MM or N working.
[MTCB Software Development] Thhhza:
Will try that out when I go to work this morning. I live in Melbourne, Australia. Not quite the antipodes but close :)
[MTCB Software Development] dsa8310:
Yes, it was my incomplete implementation, based on some limited European experience. Hopefully it's solved now.
[MTCB Software Development] dsa8310:
Don't let the latest flare of "fake news" make you miss the update from post #109. It's recommendable, especially for people living at the antipodes! :)
[MTCB Software Development] typos1:
Lol, "fake news" ? - a post explaining that an L image has been found, dated February, but that it MAY be from earlier/hasnt been tested and also an RK3188 MTCD image labelled "MM" that MAY or MAY NOT be MM is hardly fake news, more like unbiased reporting. :)
[MTCB Software Development] typos1:
Just checked the MTCD image marked as "MM" on Roximo's site and its not MM, but L, sadly.

Interestingly I also found that MTCD ROM Builder found here : https://xdaforums.com/android-auto/...ns-development/tool-mtcd-rom-builder-t3475444 also appears to work with MTCB/C ROMs !

Well, I successfully used the tool to mount and open an MTCB/C image (as long as its renamed "dupdate" as MTCD images are), I did not attempt to make a ROM, so cant verify that it will compile an image correctly, although theres no reason to suppose it wont.

Looking at the images I can see that it is true that there is a lot that is very similar between MTCD and MTCB/C - almost all of the MTC apps are the same (well they have the same titles at least), its just finding out why an image doesnt appear on the screen when an MTCD ROM boots on an MTCB/C SoM and what is it that makes one ROM MTCD and another MTCB/C.

Anyway, it looks like ANYONE may now be able to make an MTCB/C ROM using MTCD ROM Builder, well if you dont use Linux you may need to install it on Windows in a virtual machine or something similar.

Maybe [MENTION=3590033]Malaysk[/MENTION] or [MENTION=2127754]booroondook[/MENTION] would be able to tall us the differences between MTCB/C and MTCD ? - they both build ROMs for both types of unit, although I dont think their English is that good which might make it tricky asking. I have pmed Malaysk about it.

I happen to have an MTCD unit in my possession, it went through my mind to remove the screen and put it on my MTCC unit to see if there is a picture, I wont do that, but I got to thinking again about Joying last year saying that upgrading MTCB to L required changing the screen, I really think they just tried an MTCD image on an MTCB unit and got the problem [MENTION=1415699]pcmender2005[/MENTION] got when he tried N - no picture. But why no picture ? Different screen on MTCD that needs different drivers ??
[MTCB Software Development] Oldpapa49:
Well, I work with LED/LCD panels almost everyday. I can tell you that if the panel lives in the same design, it could possibly work, even if different vendors providing they use the same pin-outs.

But, different resolutions not to good..
[MTCB Software Development] typos1:
The resolution shouldnt be a problem, theyre the same as MTCB/C - 800x480 and 1024x600.

Anyone know what part of Android is responsible for the video out ? I thought the kernel had something to do with it but [MENTION=1550408]dsa93[/MENTION]10 has tried tinkering with that.
[MTCB Software Development] dsa8310:
A final touch to the brightness control algorithm, of general interest:

install-recovery.sh

If brightness seems stuck at the wrong value (e.g. night time instead of day time or viceversa), beside waiting for the system to get in sync (which happens anyway, every 15 minutes, I think), then removing files /data/gps/dsa/longitude and latitude (rm /data/gps/dsa/l* in a terminal, or with a file explorer) and then powering off (with the volume/power button) for 10 seconds (and then powering back on, of course) will trigger immediate brightness synchronization (as opposed to before, when a reboot was required).

The first, OP, post has been updated accordingly, with firmware including the new version of file /system/etc/install-recovery.sh.
[MTCB Software Development] dsa8310:
A Reminder To All Thread's Polluters

Motto: Trolling with a troll is trollful. They are trollless! :)

To all thread's polluters, a reminder that nowadays we have got a forum for our head units, and not a mere thread where all stuff was grouped together.

As thread's OP owner, I find it disturbing that the noise made by a few users would distract the rest of us from focusing on thread's purpose as stated in its title. It's beside the point whether they are simply naive or hardened trolls, of course.

So, if you think that you have found for our MTCB/MTCC rk3188 units the next version of firmware, other than 5.1.1, by all means, go debate it to a different thread, good luck to you, and... don't let the door hit you on the way out! :)

===

Forgot to mention, first reply should come, promptly, from the hardened troll on duty, whoever that may be, posing as a righteous... troll!
[MTCB Software Development] typos1:
Anyone can post in any thread on xda as youve been told before, there are no "polluters" or "trolls" in this thread, only people interested in their firmware.

It should also be noted that YOU changed the title so it related to 5.1.1. firmware only, AFTER we ALL - including YOU - were discussing porting 7.1.1. to our units, so initially ANY of us that were discussing porting 7.1.1. - including YOU - were sticking to the original thread title.

Its seems rather unreasonable to change the title AFTER you and others were discussing 7.1.1. and then moan about the people discussing 7.1.1. !

The "owner" of this thread is XDA developers.

Seeing, that, after giving up almost before you started trying to get 7.1.1 to work, you now dont care about it, I m happy to start a new thread, but I shall, nevertheless continue to post here and in other threads if I choose. :)
[MTCB Software Development] typos1:
Witson are now selling RK188/PX3 MTCD units and SoM upgrades with 2GB RAM and 7.2, which reminds me, last month a member on here said he was talking to a factory that said that they could supply MTCB/C RK3188.PX3 SoMs with N and 2Gb RAM, who knows if they will ever materialise or not, but would be nice if they did.
[MTCB Software Development] karadas87:
My device is mtc kld6 5.1.1 1 gb ram, can only load gapps while updating, microg only. I will be happy if you give me information.
[MTCB Software Development] dsa8310:
Follow links in first post. Give a try to the Open Gapps version as well, it requires no setup from your part.
[MTCB Software Development] ghoter:
to dsa8310

Is it possible to make Open Gapps ROM from Joying 4.4.4 firmware with Poweramp (Jetaudio) and Viper4android early start? Maybe you can advise on how to do it yourself? Sorry for my bad english.
[MTCB Software Development] dsa8310:
If firmware is rooted, you could do it yourself, from a terminal (as root) or with a root explorer. Just unpack the corresponding Open GApps package (on PC), prepare a folder with items that will go to the /system partition, and place them on SD for replacement on HU.

But why don't you check out one of the existing firmware in the first post?
[MTCB Software Development] ghoter:
Thanks for reply. You LP firmware on my Joying HU worked very unstable, still restarted on boot. V4A don't work with my favorite convolver presets. Poweramp - great. Xposed MTC radio don't work. MyMTCService work not correct. And Joying 4.4.4 firmware interface for mi is more aesthetic. With Open Gapps It should be very fast.
[MTCB Software Development] dsa8310:
It is supposed to restart on boot. Did you wipe all from recovery? If not, do it now.

I don't know about Xposed MTC or MyMTCService. However, a very well working xposed is included in either image. And there is a built-in MTC-Service 2.38, absolutely necessary.

When it comes to aesthetics, a Joying launcher could replace the KLD one, probably.
[MTCB Software Development] typos1:
Definitely, I ve tried all launchers and they work.
[MTCB Software Development] Johny DJ:
I can report that MyMTCService works well on Dsa's rom without any problems...
[MTCB Software Development] ghoter:
Yes, i'm vipe all when install firmware and later from recovery, but HU still twice restart on could boot. About mtc-radio:

https://xdaforums.com/android-auto/mtcb-software-development/xposed-modules-units-t3263966. This module is important for me.

The biggest problem is V4A, with enabled convolver effects V4A use too much RAM resources on LP.

It would be easier for me to have a Open Gapps or MicroG fast an clear 4.4.4 ROM with correctly working xposed modules and V4A.

Thank you for your understanding.:)
[MTCB Software Development] typos1:
You could always scrap Veiper4android and do the 7floorsound mod, I havent bothered with viper since I did it, theres just no need for it anymore.
[MTCB Software Development] ghoter:
Joying now offers HU's with surround digital amplifiers, but on my HU Joying rk 3188 1GB V4A is my choise.
[MTCB Software Development] typos1:
Viper just adds a loads of fake sound effects, but fair enough if youre happy with it. Another suggestion would be a usb dac or the 2Gb RAM upgrade. Or to add openG to 4.4.4. yourself, cant be that hard, its only removing some apps and adding some others.
[MTCB Software Development] ghoter:
Thank you for your support, but all variants are to complicated for me.:(.
[MTCB Software Development] dsa8310:
Really? Double restart should happen only once after (each) "wipe all" from recovery.

Check the xposed modules section, is mtcservice 2.38 enabled? If so, do you see your correct MCU version in the Settings/About/Information screen? At least when no other xposed modules are added by you.

If the issue happens after adding certain MCU xposed modules, add them one at a time, reboot, and find out which one is causing the problem. Then I will check that module out, and I will try to figure out why the apparent interference with mtcservice-2.38 (which handles dual reboots) happens.
[MTCB Software Development] dsa8310:
One xposed module should always be enabled: mtc-service-2.38. It is configured thanks to the two restarts. And it should stay that way. Same thing irrespective of version (either MicroG or Open GApps).

Well, maybe this firmware is not for your unit... :)
[MTCB Software Development] ghoter:
That's why I'm trying to convince you to create custom 4.4.4 ROM:)
[MTCB Software Development] dsa8310:
Yes, tough luck, I cannot promise anything, since my support to version 4.4.4 has been discontinued a long time ago.
[MTCB Software Development] ghoter:
Hope dies last.
[MTCB Software Development] dsa8310:
Maybe you should seek advice in a different thread. BTW, what is your MCU string?
[MTCB Software Development] ghoter:
No, no. My HU is Joying MTCB rk 3188 1GB Android 4.4.4 (Joying 20160328 firmware) for Ford Mondeo mk4.

Tomorrow I will put screenshot with MCU.
[MTCB Software Development] dsa8310:
OK. Until tomorrow, what resolution is your screen? (800x480 or 1024x600?)
[MTCB Software Development] EagleSoldier:
800x480 plz :)

I am waiting for so long, I love your 4.4.4 Rom

like to donate you a beer....
[MTCB Software Development] ghoter:
1024x600
[MTCB Software Development] dsa8310:
Resolution doesn't really matter... if I still recall anything about it. :)
[MTCB Software Development] typos1:
Well you could remove the google apps for him and add the openG ones, its not that hard.

[MENTION=8425335]ghoter[/MENTION] ask [MENTION=6041319]dsa8310[/MENTION] which apps he removes (I m on his ignore list so he cant see my posts or quotes of me) and I ll see if I can do it for you, I need to test an app for making ROMs anyway.
[MTCB Software Development] War-Rasta:
Hey guys, I have an KLD RK3188 with an 800x480 resolution. I tried flashing the Open Gapps version through recovery but I keep getting an error saying I have a bad file. I think it might be a bad download but I compared the checksum from the file on the USB with the file on my computer and they are the same. Could somebody post the MD5 for the img file after extraction or/and both rar files?

I currently have Malaysk's LP 5.1.1 ROM (in case that makes a difference).