yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
I don't know. Registration is automatic, but not functioning anymore.

His last working version is the 20-09-2023.

That is: if you have already registered.

I don't know about that permissions either.

But even registered, it does not work entirely correct. I wanted to use the screen lock and then fmc mentioned it found multiple email registrations. It wanted me to remove all accounts or do a reset to firmware settings or a complete reflash: No way!

Edit: The code is highly obfuscated and completely unreadable (for me).

If someone has an apk as close after 2 April, it might help.
[FYT Android Head Units] the.nid:
I just installed an Ekiy T7 unit in my truck (RAM 1500) and tried flashing this firmware. It seems to work fine, but I cannot find the "FYT Management Center" app after installation. The APK doesn't appear to get installed. Is there an install log that gets written somewhere?

Also, since the install script is also removing the existing "*com.syu.ms*" APK I'm concerned that the new one isn't getting written.

I would appreciate any and all pointers here.
[FYT Android Head Units] czekson:
This is my first post, so i would like to say Hi (sorry for bad english anways)

@surfer63 do your FMC works (or have been working?). Maybe there is a solution for registration problem. If your FMC worked, maybe you can import configuration files from FMC, where we can manually enter registration data. I know, that is maybe a insult for marios work, but for now... I already flashed MD kernel with service, i don't know which kernel i have in my OEM kernel files, so i don't know that i can bring back original kernel. Quote from first post:

From 2023-04-01, Kernel MD-EDITION (not FMC updates) will be released.

based on Kernel 2023-02-27 with the latest lsec6315update file.

You WILL NOT BE ABLE TO ROLLBACK to kernels released before November 2023.
[FYT Android Head Units] spectra9:
Is it ok to flash the root script shared on this post after flashing this kernel?
[FYT Android Head Units] surfer63:
No. The MD-Editoion come with the SuperSu rooting mechanism.

@Gordgelins Universal Root install Magisk.

If you want an optimized kernel you should have a look at this thread.

It has an optimized kernel without root, an optimized kernel with a SuperSu root (Like this version) and an optimized Magisk rooted kernel.
[FYT Android Head Units] spectra9:
Thx surfer. I have the 8581 and have flashed MD kernel from this thread. So should I flash the rooted version from yours? I believe this use SuperSU. Or can I flash the OK version and later flash Gordgelins root script to get Magisk?
[FYT Android Head Units] j0hn83:
There's an OK version pre rooted with magisk in that thread.
[FYT Android Head Units] spectra9:
I only see Magisk rooted one for the 7862 in the 1st post. For 8581 only non rooted OK and rooted MD are available
[FYT Android Head Units] surfer63:
Yes, that is correct. There is not a magisk version for the 8581.

You need to flash the OK version and then use @gordgelin 's universal rooting script.

But why do you need root?

I made the OK version as I personally don't want root. I use the OK version.
[FYT Android Head Units] Moldeb:
I can update apps, no problem. The few messages are no reason to freak out - it's beta...
[FYT Android Head Units] spendaccia:
I known i can update application but the message sometimes remains fixed on the screen.
[FYT Android Head Units] mariodantas:
I still working on that, I the next release I'll remove the blue / green / yellow toasty messages when you install / uninstall applications

Also I found the developper message issue

But found an annoying issue: System lock can not work as I can't grand admin privileges to FMC (I think that is because the unit is already connected to a google account),

I'm testing in a factory reset unit to check if this is the issue for the Lock issue
[FYT Android Head Units] spendaccia:
Ok. However thank you always for your work.
[FYT Android Head Units] mariodantas:
New release today:

2023-02-01

Fixed: Lock screen doesn't work ?: Instructions are provided when clicking on the button.

Fixed: Annoying Toast "Developer.... ....update.notification" message when install / uninstall apk

Added: Open Android settings option to menu

TYPE: FMC-UPDATE or MD-EDITION-UPDATE
[FYT Android Head Units] Trayal:
I just wanted to thank you, sincerely, for implementing the lock/unlock feature. It's something that I've sorely missed on these units, and I've always scratched my head at why security features have been removed in the first place. I'll be getting this installed on my Mekede unit as soon as I have the time.
[FYT Android Head Units] marchnz:
McLovin it.

Assessibility permission sticking.

Kill app restarting

Unit behaving well with mod.

Ability to lock.

For my unit this means; Waze, JBV1 and Torque all running when I need it without having to check every drive.
[FYT Android Head Units] PaY87:
Update to 2023-02-02 successfull. The changelog only shows 2023-02-01. I like the new button style in FMC.

Why need the Google account removed before we can use lock? Thanks!
[FYT Android Head Units] mariodantas:
FMC must get admin privileges before any logged account (you know, google stuff...). Admin privileges needed to lock buttons, SystemUI and other ways to interact with Headunit !
[FYT Android Head Units] PaY87:
Alright, maybe I manage to try it out tomorrow! Thanks buddy
[FYT Android Head Units] Moldeb:
Updated to MD 02-02-2023 (no Mainservice + @seb21 01-02-2023) everything seems to work fine. Thanks much @mariodantas and @seb21, great pieces of work!
[FYT Android Head Units] mariodantas:
New release today:

2023-02-06

Added: Unlock unit by BT device connection.

TYPE: MD-EDITION-UPDATE
[FYT Android Head Units] marchnz:
Appears I commented too soon.

Leaving device sleeping approx 7 hours, apps are killed.

Might look to add to file list that implements no kill instead.
[FYT Android Head Units] mariodantas:
Did you check FMC setting for NOKILL function Enabled ?
[FYT Android Head Units] PaY87:
Cant get lock device to work. I removed Google Account and when I click on lock nothing happens. I checked that FMC has admin rights, too.

Is it possible to exclude some apps from nokill? Or set a delay before they start? So that sd card is ready for the apps.
[FYT Android Head Units] marchnz:
Yes, although it could be that the app itself is crashing.

Probably best the app is restarted via your fine mod or using the factory app.

I have a 6gb model, so thinking memory isn't an issue.

Would you consider sharing the details to Kernel mods, this would enable the community to self mod and contribute modded kernels.
[FYT Android Head Units] yokala:
I finally took the time to install the firmware on my unit and after 2 weeks of usage I just want to say thank you Mario, you did an awesome work, everything is working great on my side !
[FYT Android Head Units] strakell:
I'm also using the MD rom since the first day, so far so good!

I really appreciate your hard work and I'm very thankful!

P.S.

I'm impatient for your system UI teaks!!

Thank you Mario.
[FYT Android Head Units] mariodantas:
New release today:

2023-02-13

Fixed: Russian translation

TYPE: FMC-UPDATE
[FYT Android Head Units] PaY87:
Great news! Will try to install it tomorrow. Fingers crossed that lock will work with the update :)
[FYT Android Head Units] czekson:
@surfer63 , please tell me what im doing wrong.

Due to problems with MD kernel and registration in FMC i would like to bring back stock firmware, but when i try to flash stock firmware (checked, works before flashing md kernel) it tells me that can't read config.txt. I would like to bring back stock firmware, then flash your's OK kernel. What i'm doing wrong?
[FYT Android Head Units] surfer63:
Do a checkdisk or fresh format of your USB-disk. Then copy the config.txt back onto it.

And can you read the config.txt properly?
[FYT Android Head Units] czekson:
Thank you for help.

I have done full fat32 format, and still the same.

I tried to make some changes in config.txt so i was sure it was my fault, but when i put stock config.txt it still tells that can't read. Maybe my problem is that i flashed MD FMC with Mainservice, so the config.txt is replaced with other file? But when flashing full stock firmware with kernel it should run as well, or im wrong?
[FYT Android Head Units] j0hn83:
Nope.

It doesn't matter what was flashed previously, a correct config.txt should flash if done correctly.

Maybe post the contents of config.txt or upload the file?

Don't use Windows Notepad to edit it. I use Notepad++
[FYT Android Head Units] czekson:
So i flashed entire stock firmware and its works.

Blame on me, becuase i unzipped allupdate.bin, then zipped it with modifications, but...

I zipped a catalog AllAppUpdate to allappupdate.bin, it should be in .bin root.

But no2: Why there is a error about config.txt if problem may be in AllAppUpdate? :O

Tomorrow i will try to flash it again with correct root AllAppUpdate.bin.
[FYT Android Head Units] spectra9:
Well, I saw that some of the functions in FMC require enabling root first, so I was thinking if I enable root somehow, then I'll be able to use them. It's just curiosity mostly, I don't know if it will work or even if it's worth to make it work lol
[FYT Android Head Units] czekson:
You won't be able to use FMC due to registration problem (you can't enable root permission without register). Leave MD FMC for now and use other way.
[FYT Android Head Units] spectra9:
Yup, that's why my idea was to enable root another way, like by flashing surfer63's OK kernel and enabling root afterwards. Maybe then FMC will see that root is already enabled and some of the root only features will work. I don't know if it's a stupid idea or if it will even work though
[FYT Android Head Units] czekson:
Give it a try. Root unit and install FMC apk manually, to check it.
[FYT Android Head Units] surfer63:
No, that will still not work.

FMC wants to be registered, but that doesn't work anymore.

Rooting or not, has nothing to do with it: registration does not work anymore.
[FYT Android Head Units] spectra9:
Well turns out I don't have to try anyway. With a stroke of luck, it finally allow me to register lol
[FYT Android Head Units] Gscipione:
How did you register? Because I have this problem
[FYT Android Head Units] spectra9:
Nothing special really, I think it's just pure luck. I was just warming up the engine, and I started FMC just for kicks. First time I try to register, nothing happens, as usual. Then as I was about to stop the engine, I decided to try a second time and it just worked. I get the email immediately, enter the code, and now it's registered
[FYT Android Head Units] surfer63:
I always tell people not to cross-post, but now I do it myself as the question came in another thread post, but the answer should actually be here.

Mario's latest version has a wrong platform test resulting in a "incompatible device" error on our non-Teyes units. I fixed that some time ago by reverse engineering Marios fmc app to check for the correct FYT platform..

The second "error" is that it wants to register. As Mario probably removed part of his server APIs, this does not work anymore either.

See image below. Click to get full sizee. (Sorry in Dutch). That registration doesn't work either.

I tried to bypass this entire screen, but could not succeed. Nowadays all java (via jadx-gui) is obfuscated and the same for smali.

What I now did is when you click "Cancel", it will not stop the app but continue (I removed the finishAffinity() and system.exit(0)).

I did that Yesterday.

If you want to test, please find attached an installer. Unzip it to a clean usb-stick and flash it.

Note: Mario already mentioned that his version is beta, so this is certainly beta. It will not do any harm to your system, but it might not work entirely correct. I tested some of the functions myself and screen lock doesn't seem to work without registration. I will see if I can work-around that as well. As I don't have (or want) a rooted system, I did not test the root functions yet.

Let me know what you find. It already took quite some time which I didn't want to spend on it on it in the first place. And it might be easier to write a simplified version of Marios fmc app after all as some functionality is relatively easy to copy and some other functionality is a shortcut to default Settings, or hidden settings (hidden by FYT but still in the Settings app).

The big advantage is that it allows you to couple one device via Bluetooth in the normal settings, and another device via the bluetooth 2 settings (as our units have 2 BT chips: a Realtek (Qualcomm in 7862S) and built-in sc7862 BT chip. That single functionality I personally like most ;)
[FYT Android Head Units] Clandaries:
Does it work when rooted with Magisk?

i would love to use the darkmode setting.

Thank you.
[FYT Android Head Units] surfer63:
Yes, it does although I did not try dark mode.

This morning, after writing above post, I installed my Magisk-Kernel again, and fmc gets immediately root access.

But fmc only works with Magisk in the last 2 versions as far as I can remember.
[FYT Android Head Units] badwhip:
So what i liked about mario program it allowed my atoto to keep accessabilties on even after boot which allowed some of my apps to work without having to go in menu and rechecking it everytime on boot. also it allowed me to have apps that were running during sleep will this modded fmc allow that? i plan to try it.
[FYT Android Head Units] marchnz:
Absolutely no disrespect intended - it would be more helpful to share the information or source like surfer63 does, over developing as a closed source, because more are then able to learn and share as the developer moves on.

The same is happening with the MTCD platform 'mods' - Malaysk and hals mods, although the difference is they reused the work of others mostly.
[FYT Android Head Units] Gscipione:
I tried to install the new fmc by @surfer63 but I have still problem of the registration. I think that I will make a clean installation in this week to see if works
[FYT Android Head Units] surfer63:
That's what I mentioned: registration doesn't work and will not work until Mario fixes his server. You need to "Cancel" the registration and then the app will continue.
[FYT Android Head Units] surfer63:
It looks like fytfactory.mariodantas.com is now also down.
[FYT Android Head Units] badwhip:
surfer63 does the program you have allow apps to start up after sleep and to keep accessibilty on after sleep?
[FYT Android Head Units] surfer63:
My program? which program?

And you don't need a program like fmc to start aps after sleep. That is default functionality from FYT. I never understood why Mario built that into his app.

Settings -> User -> Application Setting ( which applications you want to auto-start when you start your car and unit ).

And keep accessibility on after sleep? I have no idea.

Accessibility is also ruined by the Velvet apk which is removed from the modded kernels. But every now and then the Play Store does a fresh install of it. We can't stop that.
[FYT Android Head Units] badwhip:
well i guess i was thinking of your modded kernel. on atoto radio we can only set one app to auto start and that app is designed to be a navagation app we cant start other apps. mario programmed allowed any app to start and any app to be started after sleep. his app also allowed accessibility to stay on all the time so it made the atoto radio work so much better.
[FYT Android Head Units] surfer63:
OK. I didn't know it was different on the Atoto. That is indeed Mario's fmc then.

In /oem/app is the pwctl_config.xml. If you add programs to that file, they will be autostarted on cold boot or after deep sleep.

You can write an lsec script and add your own apks to it.
[FYT Android Head Units] surfer63:
Some background on how Mario programmed his fmc app​

(and note that I don't have the code. This is some reverse-engineering and building the kernels).

He signed it as a "platform signed" app which means it has the first level of being a system app (but without extra rights).

To give it the elevated rights that a system app has, it has to be pushed/installed as a system app in /oem/app.

To give it even more elevated rights, it has to be pushed as a private system app in /oem/priv-app (what Mario's installer does).

Due to increased platform security as of Android 9 (or was it already A8.1 ?) you also have to "register" it in "system/system/etc/permissions/platform.xml" (done via his and my kernels via the "system-user-whitelisted-app" entry, to really give it the elevated priv-app rights).

To be able to control power management as not to be swiped out, you have to again "register" it in "system/system/etc/permissions/platform.xml" (done via his and my kernels via the "allow-in-power-save" entry.

To make it automatically start from boot or deep sleep, it needs to be added to /oem/app/pwctl_config.xml (as explained in previous post and done via his and my kernels)

To be able to react on the "BOOT-RECEIVED" intent, it has to be a system app as well and that permission has to be requested.

And to be able to use "hidden APIs" (google for it), it has to be registered in "/system/system/etc/sysconfig/hiddenapi-package-whitelist.xml" (done via his and my kernels). But don't ask me why he needs that one and where he uses it. That was introduced in Android 9 and furter expanded/changed in Android 10 (our units level) and Android 11.

"Everyone" might be able to push an apk to /oem/app or /oem/privapp, but giving it really the necessary system rights requires to modifiy the always read-only /system partition. That can only be done by (re)creating it and flashing the kernel: thus with a modified kernel.

That's why Mario's fmc app no longer needed root access for some functions after he created his MD-Edition and added the necessary entries to some of the /system xml files.
[FYT Android Head Units] edris90:
Is there a download mirror available to compensate for Mario's website being down?

I've been going back and forth through the XDA forms that I having trouble finding the FMC downloads.
[FYT Android Head Units] nectaire:
FYT 7862 AND 8581 FIRMWARE MD EDITION - Google Drive

drive.google.com

Mario's Google drive link.
[FYT Android Head Units] edris90:
Thank you very much.
[FYT Android Head Units] binary_boy01:
Hello, any updatenon this?
[FYT Android Head Units] j0hn83:
Any update on what?

@LLIyT_HuK is just saying what the error messages mean. There's nothing to update.

If you have 1 of those error messages you need to say what it is (there are 3 different errors in the post you quoted) and what you have tried to fix it.
[FYT Android Head Units] binary_boy01:
Hello,

You are right, sorry for the lack of details. Solved my problems with manufacturer I'd set to 116 in fyt.prop and installed a shared com.syu.apk.. All checks good now.
[FYT Android Head Units] mariodantas:
I'm alive fellows, everything is on again
[FYT Android Head Units] Specy01:
Welcome back Mario, I hope you have solved your problems as best you can 🤗
[FYT Android Head Units] mariodantas:
No more wife, living alone with my servers
[FYT Android Head Units] Specy01:
I'm really sorry. I wish you the best of luck
[FYT Android Head Units] dingmel:
Hi Everyone. I'm on a Mekede M300s 2K, running MD's custom kernel with Root activated. I recently noticed that the native android Files app was missing. i was trying to grant USB drive access to other applications. I don't recall when it may have been accidentally removed by myself as I recall it being there before this (silly me).

Anyway, i've scoured the net looking for a means to reinstall DocumentsUI.apk, but its not in the root folder under priv-apps, neither does downloading a custom APK online work. There was a method described here https://community.oneplus.com/thread/564141 which i tried, but it doesn't work as well. I believe it might be due to the android versions being different?

I've had no luck getting it reinstalled. Might anyone have suggestions on how I could restore the default DocumentsUI file without restoring? Thank you!
[FYT Android Head Units] Moldeb:
Recommend reading the FAQ, link is right in #1 under Mods, useful software - https://xdaforums.com/t/general-fyt...s8581a-sc9863-q-a-mods-tips-firmware.4396339/
[FYT Android Head Units] dingmel:
truly a RTFM moment for me. Thank you so much for helping solve what has been puzzling me for days in a few moments. somehow google's "documentsui.apk" search pointed everywhere except here, and it never occurred to me that it was removed after flashing the custom kernel. lesson learnt.

Thank you kind sir.

edit : welcome back sir @mariodantas . Hope your life takes a turn for the better !
[FYT Android Head Units] Moldeb:
Actually I doubt that - it's typically missing on FYT with OEM firmware also. FYT comes with a crippled file manager.
[FYT Android Head Units] rickthecabbie:
Awwww yeah,now that's what i was hoping for!

Ummm yeah, that was not on my bug report at all☹️. sorry to hear that, my good man. Been there, done that. Granted, I initiated the process, it still sucks.

That said, I am really glad to see you back. Your work is some of the best, and I look forward to seeing what you do next.

Welcome home.
[FYT Android Head Units] labkos:
Welcome Mario I wish that the best
[FYT Android Head Units] hsianice:
您好，我在安裝過程中遇到了問題。
[FYT Android Head Units] badwhip:
my radio hasnt been the same without the mario software great your back
[FYT Android Head Units] badwhip:
are you able to register the software yet?
[FYT Android Head Units] mcvive:
yes, registration is working again and his site is also accessible again

7862/8581 FYT Factory by Mario Dantas
[FYT Android Head Units] badwhip:
So I still can’t register I have checked all my junk mails etc and tried another e-mail but I still don’t get the email to register is there something I can try? I have my other radio already registered 6 months ago but I assume you can register two radio with same email.
[FYT Android Head Units] haixuling:
I don't think it's a good idea to need to register and then use because the registered server is personal and unstable. Many programs on FYT devices can be used without registration
[FYT Android Head Units] 3PI:
Super Mario.

I am very happy for your return
[FYT Android Head Units] i7even7:
Greetings

You guys are still not able to register the unit right?

It has been days since I can't register
[FYT Android Head Units] badwhip:
i cant register at all. tried reloading all software. never get an email.
[FYT Android Head Units] Adamados:
According to the fyt.prop my manufacturer code is 116

ro.rk.install_non_market_apps=true
ro.build.fytmanufacturer=116
ro.build.fytfontsize=
ro.build.fytlivewallpaper=
ro.fyt.uiid=4
ro.build.fytinputmethod=com.google.android.inputmethod.pinyin/.PinyinIME
sys.fyt.warnning=false
ro.fyt.usb_enable=1
ro.fyt.defvol_boot=18
syu.persist.ahd=1

Which edition should i use?

FYT 95 TEYES MD-EDITION or FYT 1 and 31 MD-EDITION ?
[FYT Android Head Units] j0hn83:
Neither.

FMC currently cannot be registered. There is something up with the Mario's server that authenticates his app.

This prevents the entire kernel from running and requires you to start again and flash your unit all over with another kernel.

There is a way to bypass his registration but I'm not a fan of publishing this while he is back active on the forum. It was bypassed previously because Mario had been away for a long time.

We should give him time to fix his work.

I recommend you use

[KERNEL] FYT 7862(S)/8581 optimized root prepared Magisk-EDITION​

until Mario fixes his registration issues. It is very similar.

You don't need to worry about the fytmanufacturer id changing as it's only a kernel.

You could then install FET (Fyt Extra Tool) which is similar to Mario's FMC app.
[FYT Android Head Units] comiflor:
Will this firmware work on a 1920x720 no name (AliExpress) FYT unit wit 7862s ?
[FYT Android Head Units] surfer63:
As long as it is really a FYT: yes.

Note thought that Mario's kernel is now beginning to be slightly older and might not contain all the latest updates in drivers, especially for the 7862S versions.