yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
!! MD_Edition-CC3_2K_May2023. An integrated MD-Edition for the T'eyes CC3 !!​

!! Only for T'eyes CC3. Do not touch this firmware if you do not have a T'eyes CC3 !!​

Fully untested. I don't have a T'eyes and can simply not test.

It is a complete firmware as T'eyes integrates everything in the 6315_1.zip, so I can't even deliver a kernel only zip.

It comes integrated with the FMC apk from Mario and the modded com.syu.ms apk from Mario (see post #1 and his website).

The updatecfg.txt comes with "twipe_cache" and not "twipe_data". If you want to, you can change that for yourself.

This firmware is free, so I will not "twipe_cash" you. (sorry, very lame joke, but I could not resist it)

You can download from mega.nz: https://mega.nz/file/IAEjwJgY#hCNaj8rRiFhSSbAPY7-9Ycqd3m0jm5UKNj0-1_lmnCc

It is based on the CC3_2K_May2023 version downloaded from T'eyes Australia: https://teyes.com.au/pages/firmwares

This is fully on your own risk, but you will NOT hard-brick your unit.​

If it flashes fine, but does not function correctly, simply flash with an original firmware.

In case you get an error during the flashing with a red message and counter like "rebooting in 450 seconds" or so, simply remove the USB-stick and connect a USB-stick with a correct firmware (that same, but original CC3_2K_May2023?). Take a paperclip, needle or something else "pointy" and reset your unit. It should flash your correct firmware.

If not: reset it 3 times. Every time you see the boot logo, immediately reset it. As said: do this 3 times. Then the unit will go into recovery mode and flash whatever is on the USB-stick.

Let me know (but I'm sure you will)
[FYT Android Head Units] surfer63:
OK-Edition foreign kernel 20230617 for 7862 units.​

The OK-Edition is the Optimized Kernel Edition. It is essentially the same as the MD-Edition, but not rooted.

I took the FYT foreign kernel of 17 June 2023.

All the optimizations from Mario are in this kernel.

- Optimized memory management for 4/6/8 GB.

- ADB more optimized

- Quicker A-GPS lock

- Force of GPU use for very old apks when GPU's were not standard in "phones" and these apps are not "auto-switching" to GPU use

- Removal of the WellBeing apk

Changelog (to Mario's previous release):

- kernel version 17 June 2023.

- Not rooted.

- Added Documentsui to system/system/app.

- Changed supl serverport back to 7275 (from 7276) for improved security as it is the encrypted port.

- Added hosts file from https://winhelp2002.mvps.org/hosts.htm ("Blocking unwanted Connections with a hosts file").

- Fixed partition sizes in "dynamic_partitions_op_list" when using the somewhat smaller FYT "clean and lean" kernels.

Disclaimer: This is BETA just like Mario mentions for his builds.

Note: This is only for the 7862 units. There is not a new kernel for the uis8581a (as far as I know).

Kernel only: "OK-Edition_FYT_foreign_20230617" 6315_1.zip.

This one is tested and works for me. As I do not have/want Waze I can't test the Waze functionality in the main widgets of the newer launchers.

How to flash it:​

= If you already have the mario Dantas kernel installed (with or without fmc or com.syu.ms is not relevant):

Simply copy the 6315_1.zip with an up-to-date lsec6315update and a config.txt to a clean USB-disk. No updatecfg.txt or other file is needed.

= If your system does not have the Mario Dantas kernel yet, you need to download Mario's kernel (post #1) to your computer. Read the instructions in the zip and unzip it to a clean USB-disk.

Then copy "my" 6315_1.zip to the USB-disk replacing/overwriting the somewhat older kernel from Mario.

= If it doesn't work.

Simply flash Mario's previous kernel back on to your unit or an "original" unmodified kernel.

As always: The first boot after the flash takes longer as APKs need to be optimized. So don't worry and be a bit patient.

Allthough this is not really off-topic, I am now "polluting" Mario's thread with builds that are not entirely an MD-Edition. I will think about that.
[FYT Android Head Units] Clandaries:
When on latest VVE you get this red warning and have to flash VVE again.

I will test tomorrow with original CC3 firmware and let you know. But maybe someone is faster :)

Thank you.
[FYT Android Head Units] surfer63:
When on latest VVE, I do not really see the use to move to my version, but that is up to you.
[FYT Android Head Units] Clandaries:
I love to play around :)
[FYT Android Head Units] mrchloo:
@surfer63 Do you want me to continues sharing the newest kernel "domestic version"?
[FYT Android Head Units] surfer63:
Both the foreign and the domestic kernel please. The foreign kernel is much easier to handle.
[FYT Android Head Units] mrchloo:
mostly domestic version easy to get. I will share both if got.
[FYT Android Head Units] mrchloo:
7862 domestic version 20230724.

7862国内系统no root 2023.7.24.zip

drive.google.com
[FYT Android Head Units] surfer63:
OK, thank you.

The domestic kernel requires 800 MB of Google stuff to drag in, and to change all references to Chinese language/country codes/etcetera to US English.
[FYT Android Head Units] surfer63:
Nice. The rooted kernel has a rooted boot image, as far as I can check (not time enough yet). I don't like that and it doesn't work with the "switch root on/off" from Mario's MD-Edition.
[FYT Android Head Units] mrchloo:
ok
[FYT Android Head Units] surfer63:
@mrchloo

With regard to the "domestic system kernels" (国内系统).

Of course they miss all the Google stuff, but I do find other apks like "HwNearbyCar", "HwDMSDPDevice", "HiSight" and "HiViewLite".

I can't find references in normal apk stores, so I assume they are only for the Chinese market (and I can't search in Chinese).

What do these apks do? Should I remove them?
[FYT Android Head Units] mrchloo:
it is hicar Chinese app. I think the app can be removed...

文档中心

device.harmonyos.com
[FYT Android Head Units] Pino1966:
Hi, I would leave it in because there are users who have huawei and as you know, the new huawei smartphone no longer have GSM services, and I personally would like to test it if it would work with my huawei 40 pro hicar
[FYT Android Head Units] mariodantas:
Honnestly @surfer63 , you can do whatever you want here, green light for you, and if you consider to publish your own kernedl, simply open your new thread and I'll pin-it on the top of this one !

All os us love your job here, and everyting you do for the community
[FYT Android Head Units] mariodantas:
By the way fellows, do onyone here experienced probles doing fytbackups from FMC ?, yesterday while testing mine didn't the backup and I see in LOGCAT that one file fom the carlink/lib/arm64 folder have access denied in read mode, even if GFMC can read root files, this particular file can't be read ! I'm working on that at my rithm
[FYT Android Head Units] mariodantas:
I'd like to learn about this, how to calculate new size if I intend to add some stuff to system, elable, product etc ????
[FYT Android Head Units] surfer63:
OK. I will leave them in. At least for the time being.
[FYT Android Head Units] surfer63:
Which library? Something being actively used during that backup?

Currently I stupidly use the latest Mekede M6Pro "dynamic_partitions_op_list". That one is largely sized and has enough space "for everything".

So no intelligent recalculation at all :).

I am working on making the scripts more universal based on an extended config.ini. So that you can work from:

a "full" kernel (from some full up-to-date firmware from Mekede/Joying/etcetera)

a foreign kernel (almost full)

a domestic kernel (no Google stuff and "China oriented")

An also with a setting for a "rooted" or only "optimized" kernel.

When ready I will share my scripts, but they are currently a work in progress (and might stay that way ;))

Next to that: the elable and completely integrated stuff for T'eyes is currently not part of it. I think it can be added, but it's not at the moment.
[FYT Android Head Units] mariodantas:
Maybe I didn't check if loaded, but anyway I think it doesn't matter as FMC only reads the file: libaaudio_cp.so
[FYT Android Head Units] mariodantas:
Surfer, can you please share the file if you dont mind of course ?

P.D. In the past I was trying to "calculate" when creating MD-EDITION but never reached a good result, always getting ERROR while flashing !
[FYT Android Head Units] surfer63:
That one is used by the carlink apk. Newer firmwars come with that library inside the apk. I would not worry about it.
[FYT Android Head Units] mariodantas:
Yes I understand, but in this case We haven't a really FYTBACKUP as 1 file isn't included.

Well I'll check what's wrong while reading this one !
[FYT Android Head Units] surfer63:
See attached. zipped as otherwise I can't attach it.
[FYT Android Head Units] mariodantas:
Thanks @surfer63

Found the issue with file, it was the permissions (no read permissions for root ?, strange)

So I decided to add the 3rd line to the following script (of course after copying the new carlink to the unit:

chown -R 0.0 /oem/app/190000000_com.syu.carlink
chmod 755 /oem/app/190000000_com.syu.carlink
chmod 644 /oem/app/190000000_com.syu.carlink/lib/arm64/*
chmod 644 /oem/app/190000000_com.syu.carlink/190000000_com.syu.carlink.apk
[FYT Android Head Units] phibes9000:
Mario, I am running your firmware and am trying to solve a parking sensor issue. I am sure it’s the canbus box, but wanted to check your firmware doesn’t affect that function.

If you have the source code for the class/function that handles that I would appreciate it as I can read the canbus data in parallel, might be able to debug. Are you on github?
[FYT Android Head Units] erricomanuel:
Hi Mariodantas… You are really good, many and many "Thanks", for sharing your Magnificent work with us, Thanks to you or on the road of this adventure of the Android car radio that takes me great. A thousand thanks…
[FYT Android Head Units] erricomanuel:
Installed on generic unit CPU uis7862s 64bit 8-core (2x ARM Cortex-A75 @ 2.0 GHz, 6x ARM Cortex-A55 @ 2.0 GHz) 8 Gb Ram 128 Gb ROM. 2K 2000 x 1200 dpi. I'm considering the change so far so good. I would like to know if I can flash it again with another bootanimation.zip created by me.
[FYT Android Head Units] surfer63:
Yes. Only the lsec6315update and your bootanimation.zip on the USB-stick.

Or a simple reflash with your bootanimation added will do it as well, but takes longer.
[FYT Android Head Units] erricomanuel:
Thank you very much, for your answer before installing it, could you tell me what are the characteristics of the bootanimation.zip file, just to understand and not make a mistake and after that it doesn't start anymore
[FYT Android Head Units] surfer63:
The bootanimation.zip is a standard functionality of Android. There is a myriad of "HowTo's" on the internet, and this is not the place to explain it here.

So google.
[FYT Android Head Units] erricomanuel:
Already done. Thank you...
[FYT Android Head Units] Astur_Torque:
It is barely understandable in English.. imagine in other languages hahahaha!
[FYT Android Head Units] mariodantas:
What are you talking about ?
[FYT Android Head Units] ronald_w.:
Hello Mario. First of all, thank you for providing a firmware for FYT8581 devices. I have flashed the latest firmware today and still have the problem with locking the device. Even though root access is enabled, I get an error message that root access is not possible. What am I doing wrong?
[FYT Android Head Units] Astur_Torque:
I was talking about default FYT translation in settings menu
[FYT Android Head Units] Fredday:
Hello surfer63, I installed your OK-edition and it seems to work great. However the MD manager becomes unusable as it says it's not his firmware. I forgot to turn off root before I installed your OK-edition so do your safety measures still apply to it? Since I now can't undo the root setting as the MD manager doens't work anymore.
[FYT Android Head Units] surfer63:
What is the MD manager? Do you mean the FMC apk (Fyt Management Center), or the SuperUser apk?

I assume you mean the FMC app (Fyt Management Center). The FMC checks a property "persist.sys.mdedition=true" set inside the "/system/system/etc/prop.default".

That one is also set in this OK-Edition 20230617 kernel, so it must work apart from the rooting itself. I also add that to every kernel to make it work with Mario's FMC apk (with or without rooting).

So, this morning I got in the car with 3 USB-sticks.

I first flashed Mario's MD-Edition kernel and switched on the rooting, rebooted and rooting worked. I did NOT switch off rooting.

Then I inserted the 2nd USB-stick with this OK-Edition 20230617 kernel and flashed it. Afterwards the FMC app simply worked, but it is no longer rooted and SuperUser does not work.

Then I took the 3rd USB-stick with the latest YHCL OK-Edition kernel from my new thread and flashed it. And FMC still works and it is not rooted.

I create all kernels simply using Mario's "persist.sys.mdedition=true" inside that modded "/system/system/etc/prop.default" to make FMC work on it.

And with regard to: "Since I now can't undo the root setting as the MD manager doesn't work anymore." That is even stranger.

The SuperUser.apk is copied by Mario's scripts to the /oem/app partition and I do not remove it, so it is still there. But as the rooting binary and service has been removed, that SuperUser apk does not work anymore (like I described in my 2nd and 3rd flash).

The fact that the SuperUser apk is still on the unit, does not mean it is still rooted.

I will add some explanation to the 2nd post of my thread.
[FYT Android Head Units] Fredday:
Hello Surfer I'm attaching pictures to show what I mean. As you can see it tells me this is not the md software hence I can't do anything anymore with the fmc as it only gives me the cancel option and forces me out the app. Also would you like to continue this conversation here or in the other thread you made?
[FYT Android Head Units] surfer63:
Yes, it might be better to continue in the other thread. Please also try with the YHCL OK-kernel.

After testing that 20230617 OK-kernel this morning (and it works for me), I also unpacked the kernel to check for the property and it is really there.

So please flash with the YHCL one: only the kernel and the lsec6315update.
[FYT Android Head Units] phibes9000:
Bump. Got buried.
[FYT Android Head Units] surfer63:
Of course Mario does not have the source code of the FYT applications. It is the same as we would ask you for the source code of the Samsung or Motorola or Apple system apps.

And his firmware is exactly the same firmware as is running on the units with some added memory optimization (an xml file), rooting, and his own app to run as background app and have system access.
[FYT Android Head Units] Moldeb:
Update using the OK package went well!
[FYT Android Head Units] phibes9000:
Does that mean that canbus integration for parking sensors, the parking sensor display is an app? If so, which one?

Is the canbus stream available through an API or OS level function?

I.e. what stack do I need to debug?
[FYT Android Head Units] j0hn83:
In the settings there is an option called "Protocol Print" which displays ALL canbus messages received but it is just a lot of hex numbers flying down the screen really fast.

There is also an app called FYTCanbusMonitor on github that displays the canbus codes the head unit understands as intents.

The app is explained a bit more in this thread

That's about it.
[FYT Android Head Units] marchnz:
Not on holiday. In what context is that relevant to this thread
[FYT Android Head Units] fagner:
hello, does anyone know any method or application that shows the battery votage? i have a mekede m600s
[FYT Android Head Units] j0hn83:
No that isn't available on the FYT platform.
[FYT Android Head Units] Clandaries:
My Teyes head unit shows it. The Ekiy with CC3 firmware can show it to. So this must be firmware related.
[FYT Android Head Units] surfer63:
Yes, that is correct.

Battery Voltage (U_BATTERY_VOLTAGE) and Low Battery Voltage (U_LOW_BATTERY_WARN) are read by the CANbus app.

So the firmware should be able to dsiplay it
[FYT Android Head Units] kiralema:
Hi guys, first of all thanks a lot mariodontas for creating such a wonderful firware mod & serfer63 for maintaining this thread, and for doing a lot of work and helping the community with their uis7862(s)/ uis8581 FYT headunits.

I have successfully installed the latest Mario's MD-edition firmware on my ATOTO S8 Ultra 7". Everything runs well including the autoruns, and "do not kill" functionality. It was a pretty fast installation! I was also impressed that root actually works on this unit despite what others were saying about the locked bootloader in new kernels of ATOTO S8:

https://xdaforums.com/t/rooted-atot...thers-using-magisck-joying-signature.4260303/

So overall, I am very happy! :)

I only run into one question - for some reason, when clicking on the "Manage Launchers" button in FMC, it gives me a warning - "Please enable ROOT schema first!" even though the root has been enabled (see the picture attached). I also noticed, that "AUX" app (com.syu.av as determined by Superuser) keeps asking for root access. As soon as it is granted, "Manage Launchers" becomes accessible in FMC. I can't quite figure out why AUX app is important for managing launchers and why root access is required for this app. Any comments?

Thank you again!
[FYT Android Head Units] laoyang88:
change mic gain in FMC instead doing it in texteditor

This is very important, I hope to increase mic gain to the highest value
[FYT Android Head Units] mariodantas:
Te random app (in your case AUX) is from the beginning of FMC, I have trouble asking exclusive root acces for FMC, even if I spent days trying to search the solution I didn't find it yet, and it takes its root rights in the name os other app (random) !
[FYT Android Head Units] kiralema:
Thank you Mario for your reply.

If I understood you correctly, the only way FMC can get the SU rights at the moment is to act in the name of some random app (in my case AUX). If that's the case, I guess it's ok then. My concern was a possibility of some potential malware in the kernel that is asking for SU rights when it is not supposed to.

P.S. I hope your mom is doing fine.
[FYT Android Head Units] mariodantas:
Love you fellow, she is fine, they removed the node and now she goes radiotherapy.

For the random app I'll take it in hands soon and try to fix all these stuff and even add some new features !
[FYT Android Head Units] Tahvaja:
Another newbie here 👋

I'm fed up with the poor performance of my unit and hope that the MD Edition would solve some of the problems. First I want to make sure it fits my unit:

If so, I have a couple of questions:

a) Is this still the right place to start: https://fytfactory.mariodantas.com/fmc-platform/

b) I am using Car Launcher Pro/Theme leather. I guess it will work with the MD Edition, as well as other apps I've installed from Google Play. (I don't need Waze) What about all the other personal settings I've tweaked so far?

c) The main thing I want to improve is the mic sound quality. Will the MD Edition enable some adjustments the unit is lacking now? If so, has anyone actually managed to improve the phone audio quality with those settings? I've already tried adding these lines to config.txt (Thank you @surfer63 )

persist.sys.zlink.mic.vol=9.9

persist.audio.mic.senstivity=1

persist.btmic.gain=10

persist.btspk.gain=7

d) If still relevant after the MD Edition installation & tweaking the microphone settings, I would be willing to try the "Mic fix" which I've read a bit about here and there. I haven't found any proper instructions on how to install it. Could anyone help me in the right direction? I will remove this question if it's not appropriate in this thread.
[FYT Android Head Units] mariodantas:
Well I was trying to edit the config.txt (via upcoming FMC new feature) located in /oem/app (wich is in reality /fem/app) with no success, adding mic sensivity and other stuff, makes my screen rotate by 90deg, so I suppose that I can release the feature but after modifying the config.txt in interactive mode (checkboxes, sliders etc...) I'll create a zip for the lsec flash method !
[FYT Android Head Units] Tahvaja:
I'm so glad that there are guys like you who are able to unlock the potential of these devices! Could you please confirm if my device is compatible with MD Edition FW?
[FYT Android Head Units] surfer63:
We need more info than this to see if your unit is a FYT unit and compliant. We can see it is a uis8581a, but that doesn't make it a FYT. so please share some images from your system info and not from car launcher.

However, these microphone settings are only work-arounds (if it is a FYT). They improve it slightly but it really stays terribly bad. without other measure.

Before taking the time to explain that we first need more system info.
[FYT Android Head Units] Tahvaja:
Ok!
[FYT Android Head Units] surfer63:
OK.

With regard to your questions:

a) Yes.

b) All settings remain as by flashing the MD-Edition only the app cache is removed, and if you flash it for the firstm time you can even remove the updatecfg.txt

c) Like said: it is only a workaround.

- If you have a new unit, you have a setting to disable the internal microphone. An external mic is always better BUT the internal must be disabled otherwise it gets even worse. To check if you have a new unit see this image (from Teyes Australia).

- If you have an old unit:

- see thread "General FYT based Spreadtrum uis7862(s) (unisoc ums512) & uis8581a (sc9863) - Q&A, Mods, tips, firmware", post #1, Q&A 12

- Or more irreversible: this youtube video (also Teyes Australia)

d) See c) ;)
[FYT Android Head Units] Tahvaja:
So I guess I'm good to go! Unfortunately my unit is the older one, so the int mic cannot be disabled. Also, according to Teyes Youtube video, removal can only be done by desoldering. I'll have to continue on that subject in a different thread.

Thanks!
[FYT Android Head Units] surfer63:
Or use the "taping off" solution I also pointed you to.
[FYT Android Head Units] Tahvaja:
Right. I just translated the Russian text and had a quick look at the instructions. Doesn't seem too difficult! By the way, is there any harm in turning off the internal microphone? Apparently the audio goes through the external microphone in all cases anyway.
[FYT Android Head Units] surfer63:
In the "older" units, the circuits are not separated. It means that both circuits are always used. What makes it worse is that they have different resistance values.

If no external mic is connected, only the internal is used (no power/current can run over the external).

If the external is connected, and you do nothing about the internal, both are used giving worse results, due to difference in resistance.

By taping off the internal, or completely removing it, only the external can be used as no power/current can run through the internal. That "should" improve it when the mic is placed correctly.

Using a better microphone helps, but using a top-notch microphone is of no use at all. Quality will never be very good.
[FYT Android Head Units] Tahvaja:
Edit: I installed it and everything seem to work alright. But there was an issue at the end of the installation process. Is this something I should worry about?
[FYT Android Head Units] Matt Devo:
that's normal/expected and can be ignored
[FYT Android Head Units] surfer63:
One more remark with regard to question a).

Unfortunately Mario has been away for some time for private reasons.

In the mean time, I more or less took over and continued his work.

No extensions, no added functionality, no improvements, just newer kernels:

https://xdaforums.com/t/kernel-fyt-...y-with-fmc-or-sebs-modded-com-syu-ms.4610985/

When Mario is "full in function" again, his site will be the major place for kernels again (well, it actually still is).
[FYT Android Head Units] farfromhere94:
Hi. Can i get your help. Im trying to flash this firmware to my 7862 fyt. But everytime i tried it gives me this error.

System have not enough space.

Start update bootabimation fail

Update after error.

Then it just proceed to reboot the player after 5 minutes.

Not sure what else to do right now.

Really would appreciate any help given.