yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] dishe2:
I don't recall if the Atoto has an active cooling system, it might not, but it worked fine and never did this in the summer heat here on my previous car. The car accident happened at the end of December, the middle of the winter here in NY. I had it for about 9 months working perfectly fine before that, this problem only started when I transplanted it into a new version of the same car.

RE: wiring and connections, I soldered wrapped and shrink tubed them- I actually reused the same harness as it was the same vehicle (same generation, just a few years newer). I had a factory JBL amp in both cars so I needed a crux interface adapter which comes with its own wiring, all of that came from the same car, just plugged into this one using the same harness.

But that being said, I've heard someone mention that theirs also had trouble resetting and they blamed a poorly wired connection and/or suggested checking fuses. I'm curious as to why that might cause this- if the unit were randomly turning itself off, that's one thing. But it's just the apps and data being deleted. Why would just that delete and not have the rest of the storage get corrupted?

I'm not 100% sure how this works, but I feel like all the storage is on one physical microchip and then partitioned in software, so why would the unit factory reset itself during a short?

It retained the data when it was sitting in my garage for 2 weeks after pulling it from the wrecked first car, so it is obviously non-volatile memory. The non-volatile storage should also include the system and user storage, which both seem to survive these resets. Basically, the rest of the storage space is fine. If I add apps to my own update using @surfer63 's methods in his thread, it will survive the hard resets... it is just my data partition, like the bootloader or something panicked and decided to factory reset itself BUT ONLY THAT PARTITION. It's very odd behavior. I've never seen another Android device do that.

The only thing I can think of, is that perhaps after the accident there was a short in the original car's electrical system. The front end got smashed, radiator and alternator was toast... it's possible that it sent a shock or short through the whole car. But the question is... why only the data partition?

Again, I don't want to take over Mario's thread, but I appreciate your help and suggestions!
[FYT Android Head Units] afterinfinity:
I didn't get to thank you yet so thank you so much for your work. I can't even begin to imagine how many you have helped but haven't replied to this thread. Like I did.

For me and anyone else who encounters the same problem; I have had an app (installed very few so might be more) that refuses to work when MD firmware is installed. It shows an error about root being detected. I'm going to test out tomorrow the firmware without FMC to see if it works and will report back if it indeed is the cause. I would like to point out my head unit is in no way rooted and the app I installed is from play store.

I wish you the best with the court case!
[FYT Android Head Units] 03hdfatboy:
Other than language added, is there any reason to update?

My ATOTO S8 G2 Ultra is almost perfect thanks to your 2023-04-03__FYT7862_FW. Only issue I have is occasionally Apple Carplay doesn't always connect when I start the truck, shows it waiting to connect but never does. After I press reset, it's good for a few days. Is there something I can do or not do to prevent it? Not a big deal at all, just don't know what causes it.

Thank you For all your hard work.
[FYT Android Head Units] 03hdfatboy:
I have discovered with the Atoto HU, third party launchers and apps caused nearly all the issues I had. Got rid of them and HU was more reliable. Now running Mario's FW and other than occasionally not connecting to Carplay it's perfect.
[FYT Android Head Units] surfer63:
Normally in systems that deal with underlying hardware, you have a HAL (Hardware Abstraction Layer), that is an layer with standardized interfaces that allow all software on top of it to access the hardware in the same standardized way, even on different hardware as that is exactly where this HAL is for (Android apks on Intel/ARM/mips/etcetera, or Linux on top of intel/arm/etcetera) .

The "problem" with these FYT units is that their HAL is actually the MCU. As such that is a good approach for your own closed system and is used in many embedded software environments, but a 3rd party launcher or app doesn't know about this MCU layer and trusts on Android HALs between the android layer and hardware.

The FYT launchers do have some own intelligence built in to deal with the MCU.

And I am afraid these Chinese unit builders will never switch to Android Automotive.

Edit: And when it comes to standard HALs on Android like Bluetooth and USB, they cripple it.
[FYT Android Head Units] labkos:
Hello. Is it compatible with this device?
[FYT Android Head Units] gaur7v:
@mariodantas Thanks for amazing work.

I flashed MD-EDITION today on my 11.6 Inch Joying HU (JY-UQS11N8G-H) and the process was smooth.

My primary goal to install this firmware was to increase font size and this firmware helped it but not completely. I increased the Font scale factor but font of some text fields is not getting affected. Android settings generally have separate setting for Font Size and Display Size but in the FYT app there is only Font scale setting, could this be the issue?

Attaching before and after images
[FYT Android Head Units] 03hdfatboy:
See you got Tom & Jerry, one of my favorites 😎👍 I have every one of them. Watch the very first 1. The lady calls Tom “Jasper” not Tom.
[FYT Android Head Units] mariodantas:
Sorry fellows, I'm not a professional that can provide a 5 stars after sales service to all of you, but you deserve it I have no doubt.

My personal live is just now rolling down the stairs.

From lowest to highest level of mental disaster I'll list the facts below:

1-) Car paintshop in the court

2-) I lost y job

3-) Mother with cancer in advanced stage (I pray I swear)

All of this is obviously personal but I don't have problems sharing with all of you.

In fact I'm away from XDA (and other sites) due to all the probles to handle and my mental going weaker and weaker every day.

Now about FMC:

I've seen some crashes while rebooting device from FMC, someone here can confirm that crashes when you need to reboot the device from FMC ?

Thanks fellows !
[FYT Android Head Units] mrchloo:
New to this, can someone verify for me, is kernel compatable with the hardware ?. tq
[FYT Android Head Units] louforgiveno:
Sorry to hear.

Take care of yourself and your Mother and keep your chin up.
[FYT Android Head Units] mariodantas:
Love your words fellow
[FYT Android Head Units] arca114@gmail.com:
Be strong brother, all of this is to see how strong you are and you won't lower your head because of it, Faith friend, all of these are life's challenges....
[FYT Android Head Units] mariodantas:
Thanks fellow, I appretiate your encouragement, I'll not fall down, in a few days I'll be back to FYT affairs !
[FYT Android Head Units] labkos:
I wish you the best my friend, see that everything will be fine in the end
[FYT Android Head Units] shavenne:
Just installed the MD-Edition on my Joying JY-UQD80N6G-DA.

First unexpected thing: FMC is not there after install. The other thing: I don't have any audio after that. Can't even open the volume control (just stuck at 18).

So it doesn't seem to be compatible (yet?). Is there anything we could do?

Link to the original firmware if neccessary: Link
[FYT Android Head Units] surfer63:
Show us a listing of the usb-stick you used.

the kernel has nothing to do with how the volume is arranged. That is the Android layer talking to the MCU.
[FYT Android Head Units] shavenne:
Your post made me skeptical so I formatted the usb stick and extracted the files to it again (on a windows machine this time instead Mac) and it seems to work now. Audio is working, volume control ist working, FMC is installed.

Either there was something wrong on the usb stick (even I also formatted it before on the Mac, so actually it should have been clean) or it's working now because I installed the new Joying firmware which was released in May 2023 before that. I had something from October 2022 before.

Anyway, thank you :). I'll now investigate if everything else is working.
[FYT Android Head Units] 3PI:
Mario. A big hug, mate

Ánimo!!!
[FYT Android Head Units] mrchloo:
just sharing fyt official release 7862s no 360 1280x720 20230510 firmware.

"公版7862S_国内横屏_非360全景倒车_1280x720_20230510. rar"

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com
[FYT Android Head Units] surfer63:
Thanks.

You mention FYT. Where did you get this one?
[FYT Android Head Units] Clandaries:
Hi,

i ordered an EKIY T7 just to have it here as a test head unit. It should arrive in the next few days.

I also asked EKIY for the latest firmware and MCU.

They gave me this (uploaded it to GDRIVE): https://drive.google.com/file/d/1FYhu-YlEA5-O23aA3Y29wfOnmEcUznzr/view?usp=sharing
[FYT Android Head Units] surfer63:
I downloaded it twice and twice I get a corrupt zip.

When I list the contents I still get the files insize, so maybe it is bacuse zip can't read some chinese signs.

I get the error "245760 extra bytes at beginning or within zipfile"
[FYT Android Head Units] Clandaries:
Same to me but it is possible to unpack the content without a problem
[FYT Android Head Units] mrchloo:
someone is sharing in QQ chat fyt group
[FYT Android Head Units] mariodantas:
New release today:

2023-06-06

Added: Application Settings -> Run previously started applications on wake-up (disabled by default)

TYPE: FMC-UPDATE

Why that ?, I explain, sometime I found that some apps (like CamSam Plus) was dead after system wakeup from a long sleep time (the NOKILL is supposed to keep in in memory but.... for some reason the app passed away), so, when you enable this option, when FMC detects the ACCOFF signal, it stores the active applications and relaunch them (if not already running) on system wake up.

Voilà

Cheers fellows !
[FYT Android Head Units] Moldeb:
Thanks much, Mario - and good to see you keep your head up and are afloat again! Best wishes that these bad things get sorted soon and stop bothering you!

One question if I may: Joying has released a new FW on 15 May (https://www.joyingauto.com/blog/category/updated-files-released/) that comes with a new kernel also and they say no downgrade possible - am I right to assume that your latest version is not yet compatible? Would it be sufficient to use the attached Isec6315update extracted from the new Joying FW to flash your kernel? Or should I wait? Thanks!
[FYT Android Head Units] mariodantas:
Hi fellow, thankns for the kind words, about the latest joying kernel May 2023 and lsecxxxxupdate, let me check that prior to use their updater !

Thanks
[FYT Android Head Units] surfer63:
Hi Mario,

Which kernel are you now actually using? Mekede, Joying, T'eyes, FYT universal?
[FYT Android Head Units] mariodantas:
Last one from March is MEKEDE, provided by Aleksander TYUKHTA
[FYT Android Head Units] olemann96:
Does this device have very slow 4G? Gets 40mbps
[FYT Android Head Units] ps3shitshow:
Hi, I have Mekede 600s purchased from official store on alibaba, Android 12, 128/6gb model. This is the error I get after trying to flash 06 - 06 rom on it, it just rebooted normaly after this screen, also same thing happened when I attempted to do backup with script that is provided in guide, anyone got guidelines or I missed something? And here is link from cpuz verification in case you need more information http://valid.x86.fr/a/a2y5lg
[FYT Android Head Units] surfer63:
You have downloaded the wrong firmware (it is not a ROM). Is it from 06-06-2022 instead of 06-06-2023? As far as I know the last/latest firmwares are from May.

After July 2022 they switched to another lsec6315update (lsec6316update for 8581a). That is the only reason why you get an error like this.

I was put on the wrong foot due to you using the name "ROM".

I assume they changed the lsec6315update and lsec6316update again. And you unit is so new that it requires this new version.

@mariodantas : I assume you need to use the lesec6315update from the latest Joying firmware or the latest FYT public firmware.
[FYT Android Head Units] ps3shitshow:
I am sorry for not mentioning "custom rom", I was trying to give as much information as possible, while I forget to use correct terms. Any way, should I wait for Mario to update something or no? Here is my hwinfo from app, and I also made fyt backup through app, I manualy installed it.

EDIT: If I can install this modification on my unit, can I change default radio and music app in default launcher? I dislike randomizer in music player and I am using NavRadio+ app, seems there is no option to choose default app for those things in settings
[FYT Android Head Units] marchnz:
RTFF
[FYT Android Head Units] surfer63:
Yes, Mario should check this first.

This modded kernel as such does not help you with that altering radio and music player (afaik).

For that you should use either @seb21 's modded syu.ms apk, or my FytHWOneKey apk (in my signature below my posts).

NavRadio comes with its own script to remove the default radio and replace it with Navradio. I do not know though whether it replaces/aliases the radio calls from the launcher. @seb21 's apk and mine do.
[FYT Android Head Units] mariodantas:
Indeed they've replaced the lsec again, I'm checking what they changed between march and may kernels, then when updated I'll provide new lecXXXXupdate file with the kernel
[FYT Android Head Units] mariodantas:
Ok, in MAY kernel they (seem to) fixed the issue that the GNSS driver becomes crazy after receiving a bluetooth call.

That's the only thing I see they improved

Sould I release this kernel with FMC ???
[FYT Android Head Units] dishe2:
Mario! Good to see you around again! Any chance you took a look at that app restore function?

Can't wait to see what comes next!
[FYT Android Head Units] mariodantas:
Hi @dishe2 hope you're doing well, what app restore function ? do you mean OEM apps (FYTBACKUP) ?
[FYT Android Head Units] mariodantas:
New release today:

2023-06-09

New kernel from May 15th, 2023

Kernel level: (seems to be) Fixed: GNSS driver becomes unstable after receiving a bluetooth call

TYPE: MD-EDITION-UPDATE
[FYT Android Head Units] LLIyT_HuK:
Friend, hello! Do you remember our conversation about displaying network voltage readings in the status bar? Did not watch? I wrote to you in TG, but you never read)
[FYT Android Head Units] dishe2:
The user data backup. Remember You sent me some versions to try and attempt a restore, but it never worked!
[FYT Android Head Units] surfer63:
Hi, You use in your kernel the supl server from google on port 7276 instead of the standard supl port of 7275.

7275 is the encrypted SSL port, whereas 7276 is the unencrypted port.

Using 7276 makes it actually unsafer. 7~8 years ago, 7276 was sometimes chosen as it was supposed to be faster, but not nowadays anymore.

Secondly: you changed the supl server to google instead of www.qxwz.com.

For that I am really happy, as the round robin dns-resolving includes 4 servers. Via "whois" (many online sites) one can deduct that they all belong to "Hangzhou Alibaba Advertising Co.,Ltd.".

Maybe it is just a service provided for free, and theoretically ONLY the ip-address should be shared, but I still have slightly more confidence in google (but only slightly ;))

And google is about 4~5 times as fast for me from the Netherlands.
[FYT Android Head Units] surfer63:
I had a deeper look at your MD-EDITION.

Everything you do and modify can be 100% copied to the uis8581a 6316_1.zip.

With regard to the prop files: I assume you use sed or awk commands in your scripts to update and extend the prop files, and the same for the xml files. If you use sed (or awk) to modify/extend the prop and xml files, you do not have to change anything.

If you copy "pre-modified" prop files instead of modifying them, you have to take care of the right architecture (like for example SPRD/ums512_1h10_Natv/ums512_1h10 versus SPRD/uis8581a2h10_Automotive/uis8581a2h10) , but the modifications as such stay 100% the same.

Same for the _fmc apk and the xmls you use for them: Nothing has to change.

Same for su, the rc files and the SuperUser.apk. You do not have to change anything there.

Simply run your scripts on the 6316_1.zip as you would do for the 6315_1.zip. That way you can create an MD-EDITION for the uis8581a as well. You could for example take the latest Mekede 9863-a12-wbt-9-10.rar. Or maybe tyukhta has a newer 8581a version.

I do of course fully understand that you have onther things on your mind right now which are much more important than fiddling with kernels, but I guess this would be "low hanging fruit" where the uis8581a owners also can profit from.

Anyway: I wish you all the best for the coming period.
[FYT Android Head Units] louforgiveno:
This would be awesome!

Thanks @surfer63 for looking into this.

@mariodantas No rush sir! When you can, please do...I'd love to use your work on my unit.

Take care.
[FYT Android Head Units] mariodantas:
I didn't do that because I don't have a 8581 unit to test, but can modify my scripts to handle both 7862 and 8581 indeed !
[FYT Android Head Units] mariodantas:
Indeed surfer !
[FYT Android Head Units] louforgiveno:
Please do when time allows 🙂
[FYT Android Head Units] mariodantas:
Surfer, can ytou send me please the latest 6316_1.zip ? I'll release a test soon, maybe tomorrow !
[FYT Android Head Units] surfer63:
I downloaded the latest 9863-a12-wbt-9-10.rar from the Mekede site. I extracted only the 6316_1.zip as that is what you need and slightly smaller .

It is from "Fri Jan 6 16:41:51 CST 2023".

I uploaded it to mga-nz: https://mega.nz/file/9Nk0DZZR#byoCZXoQvsiO5tzHtPgF7V7uiLD81xSJ825mv3xLKvs

(For others: this is not useful for you)

Edit: And now also the complete 9863-a12-wbt-9-10.rar: https://mega.nz/file/pAMHVbpT#u4iy9kgzYgIOHo_-c6Jnwzk7Dp26rREji56pxIz8Q80
[FYT Android Head Units] mariodantas:
MD-EDITION for 8581 TEST

Ok

1-) BE SURE TO HAVE A COPY OF 6316_1.zip FILE BEFORE ATTEMTING TO FLASH THIS ***TEST***

6316 MD-EDITION

6316 MD-EDITION-WITH-MAINSERVICE
[FYT Android Head Units] ps3shitshow:
Reporting back that MD Edition with Main Service got installed on Mekede M600s. Thank you guys a lot :)

I have question regarding the root:

How do I install Magisk as Root manager? I have app but I think I need boot img to be patched for Magisk.
[FYT Android Head Units] surfer63:
No, do not install magisk. This rooting option is incompatible with magisk. The kernel is "pre-rooted" but you need to switch root on or off in the fmc app. the fmc app will install/activate the superuser apk that can allow/deny root access to your apps.
[FYT Android Head Units] ps3shitshow:
I enabled root rights already and they work fine, thought I could use Magisk and few modules relating to sound quality like DSP module. But this is good enough :)
[FYT Android Head Units] louforgiveno:
@surfer63 or @mariodantas

Quick question.....I'm all set to test this on my uis8581a, i don't have a 6361.zip specifically from whatever firmware my unit contains....i did however grab the updated one you posted which i assume is the same as the md edition....question is do i need (as a fallback) the actual back dated 6361zip my unit shipped with or am i safe to proceed without it?
[FYT Android Head Units] surfer63:
You need "a" 6316_1.zip. You do not need the original one from your firmware. The 6316_1.zip is a universal kernel for the uis8581a. Of course it gets updated every now and then with new Android security fixes, probable updates and fixes in the product partition zip., etcetera.

So if you flash Mario's MD-EDITION and it should not work, you simply download the 6316_1.zip I linked to a few posts up.

That is a fully standard 6316_1.zip which should work on any uis8581a.

You could simply use the usb-stick you already used for Mario's MD-EDITION.

So in case it doesn't work, copy that standard 6316_1.zip onto the USB-stick and remove the lsec_update folder with contents. Then flash it again.
[FYT Android Head Units] louforgiveno:
Thank you sir!

I'll post my results. Have a great day!
[FYT Android Head Units] louforgiveno:
I can confirm this as working!

Just installed on my uis8581a unit with zero hiccups.

Thanks for making this possible @mariodantas and @surfer63

Ahh....another question.....how do i add launchers that i have downloaded from your site mario? I added zip files to sdcard and also extracted the apk's .....trying to add through file manager...i point it to the apk then nothing appears to happen.

Nevermind i got it sorted out.

Thanks again

Thank you
[FYT Android Head Units] mariodantas:
Let me check that

I'm happy that this runs under 8581 !
[FYT Android Head Units] LLIyT_HuK:
Friend, hello! The site is down and FMC can't log in
[FYT Android Head Units] Ant0z:
Hi! I have an amplifier and a subwoofer installed. At the moment of switching off the head unit, the subwoofer emits a loud "bang". I checked with another head unit (not android), no problem. I'm afraid it may break the amplifier or subwoofer at some point. I have FYT 7862. Also, according to the reviews of other users with FYT 7862 have the same problem. Maybe there are ideas how to fix it? Thanks.
[FYT Android Head Units] mariodantas:
We're many in the same situation, I don't know what in the earth does the AMP when shutting down the unit (maybe cheap chinese electronic ?)
[FYT Android Head Units] j0hn83:
I've never come across anyone complain about this, though I don't read every single post.

That doesn't happen with my amp/subwoofer but mine is a weird setup with an spdif signal to a canbus box, which "translates the signal" (their wording) to the head unit.

I'm going to try the spdif out (coaxial) port on my mekede and connect that directly to the spdif+/- from my car wiring and see how that behaves.
[FYT Android Head Units] ludditefornow:
I've had this connection for my factory amp/sub since I installed my 7862 FYT unit and it works fine with no subwoofer popping.
[FYT Android Head Units] surfer63:
I did not hear anything about that on the sc9853i and uis7862 units so far.

This also happened "long ago" on the FYT Sofia-3GR and PX5 units. Maybe you should search in some very old threads (2015-2018).

I can't remember the details (not an audiophile, no external AMP)
[FYT Android Head Units] pasolnx:
Hi, any possibilities change km/h to miles/h speed on launchers?
[FYT Android Head Units] marchnz:
RtFF
[FYT Android Head Units] marchnz:
The fine forums.
[FYT Android Head Units] pasolnx:
FYS
[FYT Android Head Units] marchnz:
Welcome. As always, read first post later. RFPL?
[FYT Android Head Units] mrchloo:
7862国外系统2023.6.17.zip

drive.google.com
[FYT Android Head Units] 3PI:
what version is this? I'm afraid to try
[FYT Android Head Units] mrchloo:
fyt universal version(not china version)
[FYT Android Head Units] arca114@gmail.com:
Hello, today I noticed something when installing the MD EDITION, my Mekede M6Pro Plus radio, significantly loses the radio volume gain, I returned to the original, the gain returned to normal. Has anyone noticed this too?
[FYT Android Head Units] Gscipione:
I have the mekede m6pro and I don't had no problem with the volume gain. Md edition it is perfect for my head unit.
[FYT Android Head Units] arca114@gmail.com:
I don't know why this happened to me...
[FYT Android Head Units] louforgiveno:
Did you check the sound mix settings (while running md edition)?
[FYT Android Head Units] mariodantas:
Thanks for that fellow !
[FYT Android Head Units] arca114@gmail.com:
No.
[FYT Android Head Units] louforgiveno:
If you attempt again, go check those values, might be the reason
[FYT Android Head Units] arca114@gmail.com:
I'll see, thanks...