yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
Second answer.

I wanted to give it a quick look, but it is not even possible to download a CC3 firmware if you do not have a system id.

That's so terribly commercial.

And then they have all those closed platform software inside ,requiring T'eyes machine codes.

As said: I wanted to give it a quick look, but never will I do this for such a unit. It's like Apple with their closed environment.
[FYT Android Head Units] Clandaries:
teyes australia. There you can download without id
[FYT Android Head Units] mrchloo:
sorry to inform you that Waze is no more working in the launcher navigation window. I have reverted to the older kernel which is Working fine and thank you for your effort.
[FYT Android Head Units] gordgelin:
Somehow i do not remember any messages from you recently. The best way to contact me is via telegram, please contact me there
[FYT Android Head Units] surfer63:
That is really strange. That has absolutely nothing to do with the kernel, but with the launchers in the AllAppUpdate.bin.
[FYT Android Head Units] surfer63:
I see. It is indeed possible to do the same for the T'eyes firmware.

However, somewhere Mario wrote that T'eyes uses a different method to sign the T'eyes 6315_1.zip. They use "version 1" and the other resellers use "version 2", or the other way round.

I guess it is somewhere in his Fyt-firmware-workbench thread.
[FYT Android Head Units] gordgelin:
Almost 99% opposite - it is related to system framework, and only 1% for launchers which basicaly only turn pip window on and off. Since about march 2023 some internals of pip window have drasticaly changed and now pip window works completely different. They even had to disable splitscreen function for app which is set to pip, etc because of this, and since waze never worked fine at all on these devices (any many others) now it works even worse 😂
[FYT Android Head Units] surfer63:
Thanks for teaching me again something new ;)

I had no idea, but the new MKD system partition indeed comes with a new framework compared to the "old" one that Mario used in his early March kernel.

I did test quite some things but did not think of the PIP window at all.

I will update my "release" post.
[FYT Android Head Units] Clandaries:
Got my update. Just downloading it 👍
[FYT Android Head Units] surfer63:
I only use Nova launcher, but I just tested the launcher34 and I still have Google Maps working in the Navigation window. Is it only non-functional for Waze?
[FYT Android Head Units] gordgelin:
it may affect any sensitive app, not only waze, but you can never know before you try.

i think you understand PIP window itself is not a mode any app supports
[FYT Android Head Units] mrchloo:
FYI. I tried to get the kernel updated to 2023/6/17 international version the Waze working like usual too..
[FYT Android Head Units] gordgelin:
maybe they fixed something but i doubt. for now i see endless complaints about waze and some other apps issues on latest roms, also waze itself is not very stable, will look into this version, but i'm still waiting for "normal" July version not to waste time on previous :)
[FYT Android Head Units] Matt Devo:
it honestly baffles me that anyone uses the garbage launchers these units ship with :LOL:
[FYT Android Head Units] surfer63:
link please?

Edit: Never mind. I found it, but that date is the "release" date, not the build date. The build date is 10 May 2023.

Next to that: the public one misses allmost all Google apps, just like the 04 July 2023 public kernel.
[FYT Android Head Units] mariodantas:
Indeed it's a bug, thanks for report, will fix it ASAP
[FYT Android Head Units] Daanlt:
Hi,

i have small problem with my HU (FYT116) , FW update went ok. In control center i have enabled root and i have working it ok.

Now i want to disable root and its not working. I press button disable and it stays with button 'Disabling root services..' and notthing happens. No restart, no msg, nothing. Waited for 30min.

After next HU boot i have green message on screen 'Enabling root services'
[FYT Android Head Units] mariodantas:
Let me check that !

Plkease tell me if Superuser is still present ? (installed I mean) ?
[FYT Android Head Units] Daanlt:
Yes still available
[FYT Android Head Units] mariodantas:
No bugs from my side, will continue checking for something and come back to you ASAP
[FYT Android Head Units] marchnz:
Just some feedback from a week of use;

- start at boot - works (like the built in FYT app application) however apps remain killed after sleep resume do not start

- accessibility permissions - still get turned off after sleep

- start minimized - not working

Question - why kill apps at all on transitioning to sleep - is it at all necessary?
[FYT Android Head Units] mariodantas:
Added to mu bugs (to ckeck) list

Please remind that:
[FYT Android Head Units] mariodantas:
Sorry, my mistake

Was testing my MD-EDITION with @seb21 modded com.syu.ms (which do not kill anything if enabled in his own application) and didn't take it in count, now I revert to original MS service and indeed everything is being killed when going into sleep mode, only activities are restored by now (Option on FMC 2022-01-26) on wake up.

I'll implement snapshot of running services (with their allowed permissions) before enterning in sleep mode, to be restored late on wake up (as activities do).
[FYT Android Head Units] mariodantas:
Fixed but not yet released, will provide a custom "com.syu.ms" with MD-EDITION and advice users that it will OVERWRITE their existing "com.suy.ms", also explain how to disable MD-EDITION's "com.syu.ms" update before flashing.
[FYT Android Head Units] Moldeb:
Assuming this is not the same as @seb21 's, is it compatible or do I need to uninstall that to avoid e.g. SWC config issues? Will probably use option to not install yours for now. But may forget in future ;)
[FYT Android Head Units] mariodantas:
You can avoid provided com.syu.ms and keep using @seb21 one, MD-EDITION is compatible with the mod !
[FYT Android Head Units] Moldeb:
Understood - but what if I forget to avoid? SWC settings lost then?
[FYT Android Head Units] mariodantas:
You can't, check the 1st post fellow !
[FYT Android Head Units] Moldeb:
Cool, I see it has now been changed so I can just go with No Mainservice and don't have to disable/comment - so indeed nothing to forget :)
[FYT Android Head Units] Moldeb:
@mariodantas fyi so this is the message...
[FYT Android Head Units] mariodantas:
Oh thanks I'll check that ASAP !
[FYT Android Head Units] lowridincrew,:
Just installed on my pops 11.6" Joying radio with resolution of 1920x1080. So far so good. I'll be tinkering with it more
[FYT Android Head Units] PaY87:
Thanks for your work!! I will install the update soon. The first version was already great. Cool would be an option to change mic gain in FMC instead doing it in texteditor. This way it would be easy to changr mic boost.

Also if there is anything to save time and date it would be so cool. On my citroen i always have to wait for gps time update. I double checked the connection, but all is okay ... My PX6 didnt had this issue.
[FYT Android Head Units] mariodantas:
Implemented in 2022-01-30, you can use the FMC_UPDATE if you already have MD-EDITION kernel !
[FYT Android Head Units] mrchloo:
@surfer63
[FYT Android Head Units] surfer63:
My "Edit" was at the same time as your reply. That public one misses almost all Google apps.

Edit: And I don't have access to your link.

Edit2: And now I have access.
[FYT Android Head Units] mrchloo:
it is non china version and now can access the link.
[FYT Android Head Units] surfer63:
now I also understand the difference in the "domestic" and the "foreign" downloads (if you translate the Chinese characters).

I do see a difference in the services.jar in the framework (referring to what @gordgelin said) and the generated files, but I don't think I simpy can exchange them.
[FYT Android Head Units] surfer63:
Anyone knows what the "ro.syu.callpipshow=1" does in the later firmwares?

I mentioned that Google Maps still works in launcher34 when I tried that, but not after a reboot. Then the navigation area was empty.

If I then start Google Maps and return to the home/main screen, the launcher shows Maps again.

Does this property "ro.syu.callpipshow=1" autostart "something"?
[FYT Android Head Units] gordgelin:
i do not think so, since it says "call pip show" i assume it has something to do with how bluetooth app shows calls - maybe fullscreen vs popup

edit:

it seems i'm right :)
[FYT Android Head Units] surfer63:
I have already the modded kernel ready (once you have the scripts, it is 10 minutes analysis, type five scripted commands and wait an hour (I work on two "slow" (for this work) Raspberry Pi 4 servers.).

But I didn't have time to test and I don't know if I can test before tomorrow evening, and I don't want to share it completely untested.

@mrchloo: It is indeed almost exactly the same as the Mekede/Joying firmware kernels. But it misses the central system carlink library, and some audio and NFC libraries. The NFC libraries are useless anyway on these units, but the missing carlink system library is strange as it is the "foreign" kernel. (Of course I added them)

I know that Google is "forbidden" in China, but does that also mean you can't use Android Auto in China? And is that the reason that the carlink libraries are not in this kernel? (And neither inside the "internal" China kernel, also missing all google software, but I suppose that is obvious)
[FYT Android Head Units] mrchloo:
just tested for carlink..... it's working
[FYT Android Head Units] gordgelin:
imho they just cleaned some obsolete carlink/zlink junk since most recent carlink lilbraries included with carlink apk
[FYT Android Head Units] surfer63:
There is indeed also zlink stuff (junk?) in the older kernels.

I will remove it. I was thinking of still copying it, but I will not do that.

With regard to the carlink libraries. The ones with the red line behind it were "missing" in the newer kernels. As I also packed a "complete carlink updater" lsec script some time ago for other users, I can now definitely eliminate these libraries from the kernel.

As you can see there is also a "libcps_7862A12.so". Does that mean there will really be a real Android 12 for our 7862 models? The Joying SnapDragon units are Android 12, but that is not a 7862.

Again: thanks for your information (although it does mean I have to recreate the kernel. Good that I did not have time to test yet ;))

(I answer here extensively as I hope Mario will take over again in the near future)
[FYT Android Head Units] xtmzone:
Hello.

I saw on youtube that is a nice interface.

There is any link for that firmware ? is undestrand is not free, but where i can find ?

Thanks.
[FYT Android Head Units] gordgelin:
there already is real android 12 for 7862 but it is is not stable for now and all the other oem software is mostly the same we have now. and also it is not possible to officially upgrade a10 to a12 via usb so i doubt any manufacturer will offer such update, probably only new devices will have it. also almost all current development we have is useless for android 12 - they are trying to close all possibilities for 3rd party modifications, but will see
[FYT Android Head Units] gordgelin:
you can contact me via telegram for that
[FYT Android Head Units] fagner:
Hello, has anyone tested android 12? there's a build available already.
[FYT Android Head Units] Clandaries:
https://xdaforums.com/t/kernel-fyt-7862-and-8581-kernel-md-edition-with-fmc.4542673/post-88776351
[FYT Android Head Units] Clandaries:
So it would be possible to make this Kernel work with Teyes.

Another question.

Mario has the possibility to turn the dark mode on and off, in his kernel/firmware.

Is this somehow possible via install script?

Until now i have to use an app to turn on WiFi-ADB on my CC3 and then send this command to enable dark mode: adb shell settings put secure ui_night_mode 2

and to disable dark mode: adb shell settings put secure ui_night_mode 1

from my PC or Laptop.

Thank you :)
[FYT Android Head Units] surfer63:
I have now tried to create an MD-kernel based on the 17 June 2023 foreign kernel delivered by @mrchloo, and also created ones based on the 4 July 2023 domestic kernel where I put in a lot of Google stuff, and that Mekede Pro kernel of 13 May 2023.

The 04 July and the Mekede one from post #757 work fine, but the 17 June version constantly soft-bricks my unit (5 times now where I tried small changes every time) with a flashing error which must be a corrupt system partition. I have no clue why that happens. The unmodified 17 June kernel flashes just fine.

Concluding: so far no newer kernel than the "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp" kernel which is a 13 May kernel which is newer than the current kernel from Mario, but might not work with Waze in the FYT Launcher windows.
[FYT Android Head Units] j0hn83:
We cannot upgrade from Android 10 to Android 12 with these builds.

They are only for units that come preinstalled with Android 12.

These units have been tried. Many of the mods, tweaks, etc we do to these units so not work at all on Android 12 so even if it was possible to update I for 1 would not be doing so unless this can be overcome
[FYT Android Head Units] marchnz:
What is preventing or restricting flashing a generic FYT uis7862 image on a Teyes kanged FYT unit?
[FYT Android Head Units] gordgelin:
nothing, but in case this device is cc3 (or its versions) this will softbrick device

and list of incompatible devices may increase any moment so it is better to check everything twice when dealing with such heavily branded units
[FYT Android Head Units] marchnz:
What causes the softbrick @gordgelin ? Could be be related to boot loader?
[FYT Android Head Units] fagner:
Hello goodnight

Could you make available the _mods folder that mario dantas uses? with the tweks modifications and etc
[FYT Android Head Units] truongcp:
My launcher has problem with map window, it does not fit in the original window. I tried to flash the original firmware, then update to factory A12 update, then to FMC but this issue still occurs. Does anyone has experience with this.

Thank you!
[FYT Android Head Units] surfer63:
Long answer, you are warned.

I normally make everything I do open source and share it and/or push it to my github. This however is Mario's work which I reverse-engineered and altered to my liking.

I don't have Mario's _mods folder and I don't know what it contained. I simply unpacked his MD-kernel and the kernel it was based on and did a complete "diff -bur" on every partition. I took his FYT Factory scripts and based on the diffs I altered the scripts to make the new kernel an MD-kernel. By now I changed and added multiple things. Of course I do not know Mario's current MD scripts.

Again: I will not share my _mods folder and scripts as it is based on Mario's work. I consider that unfair to Mario.

As soon as Mario agrees to put it "public", I will share it here in the forum, like I always do with my "own" work. If you have read my "General FYT based Spreadtrum uis7862(s) (unisoc ums512) & uis8581a (sc9863) - Q&A, Mods, tips, firmware" and you are knowledgeable with Linux and bash scripting (but you can do it also with Python which makes it cross-platform), and you know the ins & outs of the diff command, you can do it "easily" yourself.

The _mods folder is different per kernel as every new kernel needs to be diffed again to find the differences, although these differences are sometimes negligible and sometimes must be ignored.

The MD kernel I made based on the "domestic" internal China kernel (from 4 July 2023) had a _mods folder containing almost 700MB mostly Google stuff, but also some other files missing.

The MD-kernel based on the "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp" (post #757) only contains 5.2 MB (5 files) where 4.8MB is taken up by the DocumentsUI.apk. But other modifications are in the scripts.
[FYT Android Head Units] surfer63:
What resolution is your unit?

What is that FMC firmware?
[FYT Android Head Units] truongcp:
I'm using Medeke M700s plus with 2K resolution.

FMC firmware is 2023-06-FYT_7862_FIRMWARE_MD_EDITION .
[FYT Android Head Units] surfer63:
The background image (as it is only an image) is not aligend with the actual window.

Please contact Mekede in this case.
[FYT Android Head Units] aiui:
what kind of software are we talking about, I'm very new to software but I'm always in the mood to test new things
[FYT Android Head Units] surfer63:
⚡ МОДИФИКАЦИИ ⚡

🧙‍♂️ Разработчик — Виталий (gordgelin)

vk.com
[FYT Android Head Units] surfer63:
To add to this: I don't like rooting at all, as I have already mentioned so many times ;)

Mario's kernels use the old Superuser approach, which we used on the Sofia and the PX5, which is actually really unsecure. For which reason I have already flashed my own unit again with the clean, original "7862_foreign_system_20230617" kernel.

@gordgelin uses Magisk which is a much newer, improved and more secure rooting option.

But rooting simply makes your unit less secure and Google does all it can to prevent users from rooting with every new Android version.
[FYT Android Head Units] gordgelin:
also in recent versions of my mod you can choose whether to flash root or not
[FYT Android Head Units] Clandaries:
OT. Have written aiui via pm, to not do to much OT.

But @gordgelin would love to see your project here on XDA.
[FYT Android Head Units] gordgelin:
i will take it into consideration :) also i need to check xda rules on paid software
[FYT Android Head Units] aiui:
yes it was good even because my business computer won't let me enter your website and on my cell phone it's all very confusing
[FYT Android Head Units] mariodantas:
@surfer63 you can do whatever you want with MD, also share in your own github (kernels and even my scripts, no worries about that)

I'll be out of business for a while, too many personal problems this year to allow enough time to try to improve things.

P.S. If you need my scripts to compare with yours, I can feed them to you, no probs !
[FYT Android Head Units] Moldeb:
Just a heads up as at least for me this was news: exFAT seems to be working now. Wouldn't use it for flashing but have music on a 128GB USB stick which came as exFAT and I forgot to format to FAT32 as I was used to. Simply works... don't know whether this is just a feature of the newer kernel or Mario's work (I use Mario's latest MD edition).
[FYT Android Head Units] gordgelin:
exFAT seems to be supported for a while already in stock firmwares, but only FAT32 is guaranteed to work 100%

also, it is better to use MBR over GUID, devices partitioned with GUID structure seem to work way worse with these units
[FYT Android Head Units] surfer63:
Hi Mario. Thanks.

I will "clean up" your/my scripts (my mess) a little and share them somewhere as a kind of MD-FYT-FACTORY-FIRMWARE 2.1 scripts or so.

All the best to you. Keep your head up.
[FYT Android Head Units] Clandaries:
Don't forget us Teyes user 😉
[FYT Android Head Units] marchnz:
Might be easier on devs to just replace with another FYT unit without seller lockins?
[FYT Android Head Units] marchnz:
Surfer63 is a legend.
[FYT Android Head Units] mariodantas:
Ohh yes sir, agree with you

For T'EYES users I guess that is almos impossible (from my POV) as all the OEM apps are inside the ELABLE partition and some symlinks in system point to some files there (i.e. config.txt)
[FYT Android Head Units] surfer63:
I don't understand why that makes it impossible. It is just another partition to handle. And once the config.txt has been written to elable it can't be changed anymore.

Please correct me if I'm wrong.

But you also mentioned somewhere that Teyes uses signing version 1 and all other FYTs signing version 2, or the other way round. Can you give a short explanation, if you want?
[FYT Android Head Units] mariodantas:
Well I guess that for T'EYES users, everytime you can't update onnly the kernel, because elable contains also apps, never tested a t'eyes kernel without AllAppUpdate.bin (not needed of course) to see if it deletes /data/data when flashing.

Having doubts about that and not having any T'EYES unit to test I never tried the adventure of course

For the config.txt even in T'EYES the elable config.txt is a simlink so "normally" you can relplace it using the lsec6315update.

But as I said, T'EYES is another workd, too proprietary for my knowledge !
[FYT Android Head Units] surfer63:
Much too proprietary anyway.
[FYT Android Head Units] badwhip:
what project does he have?
[FYT Android Head Units] mariodantas:
New release today:

2023-07-25

Added: Czech language

TYPE: FMC-UPDATE
[FYT Android Head Units] mariodantas:
Someone asks me in PM if I intend to launch MD-EDITION with June kernel, well afread discussing with well informed and hard knowledge people here (in PM), and reading the thread, it seems that the June Kernel isnt't stable, so lets wait until someone delivers a stable 6315_1.zip, this will alolow me to release MD-EDITION with new kernel, but honnestly I think that our FYT units almost in EOL, see many snapdragons, and K706 units in Aliexpress
[FYT Android Head Units] Matt Devo:
the latest stable release seems to be the Mekede 2023-06-02 one, which uses a kernel built on 2023-05-23. That's probably worth the effort to rebase / update?
[FYT Android Head Units] surfer63:
That's the one I released in post #757.
[FYT Android Head Units] Matt Devo:
yep I tested it and worked fine for me, but I saw others had some issues with the stock launchers and the map widget? So that's why I was asking
[FYT Android Head Units] surfer63:
Yes, one user mentioned that he could no longer use Waze in the map widget. So that is what I added as remark.

Multiple users, including myself, use Google Maps in that area and that works fine.

By now I already removed the MD-kernel as I don't like the unsecure Superuser/su approach.
[FYT Android Head Units] Moldeb:
Do things that need root in MD (e.g. lock system/vanity mode) still work? I remember there are a couple of functions in FMC that need root. I don't fancy root and would be glad to live without - but these functions are nice to have...
[FYT Android Head Units] Matt Devo:
any plans to re-release w/o root? I personally have no use for it, just want the other improvements
[FYT Android Head Units] surfer63:
From the FMC apk you can switch root on or off. So if you need it, you switch it on and reboot. If you don't need it anymore, you switch it off and reboot.

But it is not only the rooting. Also a few system parameters are switched to their "unsafe" position, like the "ro.secure=1" to "ro.secure=0".

This has two effects: with value 1 it means your boot image is protected, without it it is not. When your system is rooted in this "old-fashioned" way it means you will get in a boot loop if your system is at "1". But it was intentionally meant to give you immedate root access via ADB (on "0").

So with "0" your boot image is not protected (I personally don't care), but anyone getting access to your unit via ADB has immediate root access.

That would be extremely simple, but a number of FMC functionalities would no longer work.

Which improvements do you mean?:

- Faster GPS lock due to the use of the Google supl server?

- Improved memory management on 6GB and 8GB models?

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

- Removal of well-being apk?

Something I forget?
[FYT Android Head Units] Moldeb:
Thx, will update next week as I don't use Waze anyway. Just Gmaps and Here...
[FYT Android Head Units] Matt Devo:
all of those please :)
[FYT Android Head Units] surfer63:
I could have guessed that ;)