yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
Sorry, long answer.

I wrote that :), but that comes from the Sofia-3GR and PX5 times. This list is a FYT list and based on the OOM mechanism in Android where FYT supposedly gave their own priority.

On the Sofia-3GR and PX-5 it really did work as the nokill file and also in the beginning on the sc9853i.

I think FYT abandonded it and use it really as an OOM list to prioritize apps that should be swapped out/stopped when there is not enough free memory.

The only value is the 0 value which they say will never be stopped.

So, it might still be used as a file for nokill, but in that case the value should now probably be 0 instead of a value between 1~15, as on the old models.

Their com.syu.ms is now completely obfuscated to make it as hard as possible to modify it, but some strings simply need to be strings and they still use a string "killappwhensleep" connected to a "LOCAL_EXCL_LIST". That list might still be the skipkillapp.prop when using a value 0 for your apps.

In the past I made many nokill mods for the com.syu.ms, but now that FYT shuffled the code so much and use one-letter function codes, it is not doable anymore. Note thought that apps are not killed (despite the name), they are stopped via the pm process. This is a more graceful process allowing the app to close correctly instead of simply being killed.

That is my guess based on the recent analysis of the com.syu.ms.

So you might want to indeed update the skipkillapp.prop in /oem/app with an lsec script and give your app a value 0. Trying can't hurt and please report back on your findings.

Anyway, I don't care anymore. If FYT wants to kill (=stop) my app, so be it. If I want it to start again on "waking up" / (re)boot, I add it in the Settings.apk to User->Application Setting ( which applications you want to auto-start when you start your car and unit ). Smart applications nowadays know "where they were", when stopped (not killed).
[FYT Android Head Units] honda2015:
I had asked myself the same question in the past but it seems there is no tangible difference in practice since you can use all USB cords / ports to either 4 or 6 pin sockets. The meaning is data+ and minus, grounding, power+ and minus.
[FYT Android Head Units] matrixx1:
Hello, can someone help me connecting to the HU in usb debugging mode, as the normal procedu6dosent work and don't know what would. I have Mekede M6 Pro Plus with Android 10 (fake 12) pre-3D firmware. I have enabled usb debugging mode under developer settings then connected my laptop with a usb-a usb -a cable. The laptop has adb installed and the Google usb driver. It works with all of my phones with usb debugging enabled. But it doesn't work with my HU. When connected with the laptop and sending adb devices command the list which is returned is empty. I tried out with usb debugging enabled and disabled on the HU, it seems as it wouldn't matter I get the same result. List of attached devices is empty. Does anyone have any guess what could be done?
[FYT Android Head Units] old.splatterhand:
Have you tried the the menu button in the upper right side of developer options?
[FYT Android Head Units] matrixx1:
Hi, thank you, to be honest I didnt see that button, but I also didnt look, so it could very well be there for me too. I will check tomorrow, thanks!
[FYT Android Head Units] Jpm888:
How much ram should I get for a 7862 Navifly unit? Will 4gb be enough?
[FYT Android Head Units] marchnz:
What has been determined from reading thread and forums
[FYT Android Head Units] Jpm888:
Most say avoid 2gb

Not much has been said about 4gb
[FYT Android Head Units] marchnz:
4gb is OK. I have both 4 and 6, I don't think there's a difference.
[FYT Android Head Units] j0hn83:
I have a Mekede M500s which has 4GB RAM.

I never had any issues with lack of RAM on it.

I've since purchased the M6 Pro Plus with 8GB RAM and the difference isn't massively noticeable but it is a little snappier.

My M6 also has a slightly faster revision of the processor at 2.0GHz vs 1.8GHz so that might explain part of the faster feel I get on it.

The difference in price between 4GB and 6GB isn't much and the RAM can't be upgraded at a later date so for future proofing I would probably recommend the 6GB.

It's a shame they bundle the higher RAM with additional storage, forcing the price up. I have 256GB storage but could easily have managed with 64GB.
[FYT Android Head Units] matrixx1:
Hi I tired there was the menu just as on your picture. Unfortunately no matter if I change the setting according to the pictur you posted, nothing happens no usb debugging connection cam be established. Is there any other way? I read somewhere something about userdebug setting. Unfortunately I cannot find it and don't remember if it was related to usb debugging or something else
[FYT Android Head Units] old.splatterhand:
Maybe you should try USB-Debugging over WiFi. As far as I remember, I enabled dark mode for my unit this way.
[FYT Android Head Units] Recoverep:
Anyone seen this issue before and have suggestion to resolve?

Cannot open /storage/sdcard1/AllAppUpdate.bin

Update app extract fail

I unpacked and repacked the AllAppUpdate.bin per the instructions using 7-z (necessary to set manufacturer and UIID).

Tried multiple times: ensured password is set properly, updated 7-z, tried with -m0=Copy and -mx=0, and get the same issue regardless.

Using FAT32 formatted USB drive.

I can unpack the .bin without issue (with password) on my PC.
[FYT Android Head Units] Recoverep:
/deleted
[FYT Android Head Units] surfer63:
So many users reported this. You have a corrupt USB-stick. Do a checkdisk or a reformat or use a new UWB-stick.

Asking this means that you didn't search. Do that first next time.
[FYT Android Head Units] Recoverep:
Thanks for the quick reply, and all your great work on this thread ... I did do a search, but it returned nothing. Perhaps adding this to the QA would help?
[FYT Android Head Units] matrixx1:
I would but Android 10 dosent have the option like in higher versions
[FYT Android Head Units] surfer63:
What do you mean? This is avalaible as of Android 5.
[FYT Android Head Units] matrixx1:
As I couldn't manage to enable usb debugging, I rooted my

Well then I didnt see the switch. To be honest I wasnt thoroughly looking for it as I didnt see the switch where its on A12,13,14 and I assumed there is no feature as of A10. I ended up rooting the HU which was a half sucess, I wrote about it in the other thread
[FYT Android Head Units] Recoverep:
I read more comments regarding USB errors.. I have tried many things in addition to what I posted earlier:

- Full format of multiple 32GB and 8GB USB sticks (ensured FAT32!! not extFAT or NTFS!)

- chkdsk passes (before and after pushing files)

- Always "eject" USB drive, to ensure no issues when removing

- Single partition drive

Still getting the same error. These seem to be quite picky with the USB stick :cry:

Anything else I could possibly be missing here??
[FYT Android Head Units] surfer63:
Download the firmware/AllAppUpdate.bin again. Even though you can unzip it on the PC doesn't mean it is 100% correct.

You could also try to do an integrity check of the archive. Command line zip has the -T option, 7z the t option. Don't know for gui versions.
[FYT Android Head Units] Recoverep:
I finally figured out what the issue was, it was not the USB drives after all ... the 7z command provided in the instructions (II. AllAppUpdate.bin) renders a .bin file of type '7z'. It needs to be of type "zip" for the head unit to read it.

Running this command resolved the issue:

7z.exe a -tzip -mx=0 -p048a02243bb74474b25233bda3cd02f8 ./AllAppUpdate.bin *

I was successful completing Full Firmware of KingBeats K2 UMS512 Octa-Core@4.0G(Memory) + 64 GB(Storage) with Joying 10.0-1280x720_MIPI 2023.8.31. A welcomed upgrade from 2020 firmware, as this includes wireless Android Auto (confirmed working)!

fyt.prop

ro.build.fytmanufacturer=107

ro.fyt.uiid=6

config.txt

#test

bt#CAMRY#0000

sys.fyt.bluetooth_type=1

# ÅäÖÃÀ¶ÑÀÀàÐÍ

# 0£ºÄÚÖÃÀ¶ÑÀ£»

# 1£ºRDA£»

# 2£ºIVT£»

# 3£ºWQRDA£»

# 4: WQBC5

ro.product.locale.language=en

ro.product.locale.country=US

persist.sys.language=en

persist.sys.country=US

persist.fyt.zh_frontview_enable=false

sys.fyt.ec.version=6

ro.fyt.splitscreen = 0

syu.voicehint=false

persist.syu.voicehint=false

ro.fyt.launcher = com.android.launcher6

ro.sf.swrotation=90
[FYT Android Head Units] j0hn83:
It was all unnecessary.

You never had to touch the AllAppUpdate.bin at all.

Leave it as it is with the incorrect ro.build.fytmanufacturer id and add the line ro.build.fytmanufacturer=xxx (xxx being your id) to your config.txt.

This over rules the FYT.Prop.
[FYT Android Head Units] surfer63:
I still need to update the Q&A and HowTo to change this mentioning the config.txt instead of the fyt.prop.

Somehow a black hole in my memory.
[FYT Android Head Units] Snyderspretzels:
Hi everyone, first let me say thanks for this forum. It has been so helpful (especially reading about the settings on first page). This is a well maintained and informative thread dedicated to the 7862 head units.

On to my questions / issues.

I recently purchased and installed a Tesla style head unit in my 2015 Acura RDX. I am providing a link and pictures from HWInfo to this thread. Found out from HW info it's a 7862a so hoping I'm in the right spot here.

I have everything working except I have 2 issues.

1.) The HVAC/Climate control soft buttons don't work or recognize changes made on the physical hard buttons (I can still turn on and control Ac/Heat, but I'm blind in terms of temp control as it doesn't register changes physical button changes on the screen). I have reached out to seller who is sending me a new CanBus box, which she says may be the cause, but I'm somewhat skeptical because when the CanBus box is plugged in and set to RDX, the unit does register and show notifications for when I open doors or trunk on screen. Have the unit set to the proper CanBus in settings per the sellers instructions but still no hvac/climate control on the unit. Wondering if anyone has seen this / has any experience for this.

2.) Even though I changed my unit to Fahrenheit in the settings tab, and I have rebooted the unit numerous times, it stays in Celsius on main screen app and in non working climate control settings when it sometimes shows the temp (which is incorrect) but still in C. Again any tips for this?

Finally, I read all the forums intro pages on Firmware and it seems these units can be flashed with Joying firmware, but this screen has a non traditional resolution of 1024x768 as reported by HW info and I did not see a matching resolution on Joying's web page for this screen size so I'm wondering if flashing a new firmware is out of the question. I honestly was only thinking of going this route if might fix either of the above issues I'm currently having. Need a little clarification on how to flash the firmware for this unit and which firmware is the closet match/best.

Thanks for any help you can provide.

Tesla Style Android Head Unit RDX 2015
[FYT Android Head Units] j0hn83:
Unfortunately there are dozens of head units running the same processor and similar hardware. External apps like AIDA64 tell us very little.

There are multiple different platforms that run the 7862 SoC. (It also isn't a 7862a, the a variant is different).

We need to see a copy of the native Android "About Device" section from within the head units settings, particularly the MCU version.

Regarding your issues, see if you have an app called "Vehicle Settings".

There are often additional canbus settings within that app.

Failing that try picking a different car model from within the canbus selection screen. Sometimes picking a slightly different car model fixes things.

It needs a reboot between each model change.
[FYT Android Head Units] Snyderspretzels:
John thanks for taking the time to reply. I'm attaching pictures of my Android "About Device" settings here with MCU version.

I tried your Canbus selections and have picked other vehicles (other Acura options and a few Honda options) and while it does sometimes change the format/style of the climate control on the bottom, the soft buttons never actually work or correspond with physical buttons.

This has me wondering if a firmware upgrade would help. Thanks for any suggestions.
[FYT Android Head Units] hal752:
Slight odd issue.

I jumped back to the factory rom. The latest apparently according to the seller on Ali express. It's. 2024 build and it came with the latest Car link.

It has however got some different entries on the model select screen. My old one has gone however does display other vauxhall models like the astra K.

Don't suppose I can install a update or another version to replace the one currently allowing me to select my older model?
[FYT Android Head Units] bog20:
Hello

I also have the same problems with my Joying 11.6 inch and Android 10.

The temperature problem was solved after I bought a new Can Bus box (for me the temperature was displayed in "Fahrenheit and not in "Celsius", but the soft buttons on the air conditioning do not correspond to the air conditioning control, no reaction when I press the buttons on the touchscreen.
[FYT Android Head Units] Jpm888:
Any microphone recommendations for a Mekede M500s unit? Or is the included one good enough?
[FYT Android Head Units] surfer63:
I am not 100% sure if the canbus apk is self contained or needs other libraries or data files.

But you could extract the CANbus apk from a previous firmware and flash it with an lsec script to your unit. (Unless you are now talking about your 7870 unit.)

And if it doesn't give you the result you want, you flash the Canbus apk of your current firmware back.
[FYT Android Head Units] hal752:
I feel you maybe right.

I found a screenshot I took which clearly shows my older layout. To me I feel they have renamed it to Regal 2012 to 2019 and 2020 to 2022. They all work but just no longer allow for the Aircon menu (where you can change AC etc) to be displayed as a shortcut apart from the floating icon.

I have a climate button on my actuall AC panel which no longer loads the shortcut either.

It's not the end of the world. It works with everything else.
[FYT Android Head Units] hal752:
I was wondering if someone has had the same predicament I'm currently facing.

I recently swapped to a fyt board and do prefer it over my ts10 and ts18 boards.

I transferred over the screen which is a 12.9 inch 1920x1200 display. Display model is YT129IBLXL001.

The screen on low brightness flickers with anything white. (Google maps / play store etc)

I'm working around this by using dark mode. Thought I would like to work normally.

It's not a mainboard issue as seller tested on several of there's and it has the same effect.

I was wondering if anyone with a mekede pro max had the file which I will try to use.
[FYT Android Head Units] trap63:
How to exit bootwatch or rescueparty on UIS7862? My HU M6 Pro Mekede 2000x1200 is stuck on boot and no reflash is possible after RST4 times. Are there any other solution? tried several times changing USB port but no success. It return message Corrupted file! rescueparty or bootwatch.
[FYT Android Head Units] gordgelin:
if you stuck there your eMMC chip might be dead.

there is no other way to force usb update except 4 resets, also you can try key1 to gnd method.
[FYT Android Head Units] trap63:
do you mean Key1 of SWC?
[FYT Android Head Units] gordgelin:
yes
[FYT Android Head Units] trap63:
tried but returns NO COMMAND......
[FYT Android Head Units] gordgelin:
then probably repair service is your next stop
[FYT Android Head Units] marchnz:
Or wallet :)
[FYT Android Head Units] trap63:
quite good, now I run on M7! M6 in junk...I will recover the capacitor of 10.000 instead 6.800, maybe on M7 is better
[FYT Android Head Units] Gskar90:
Hi guys, I recently fitted a Mekede M600S on my Golf 6 but I have a problem with the parking sensors.

When I put the gear in reverse the rear camera comes on and the small drawing on the left with the sensors, right.

But when I remove the reverse gear, a second larger drawing with sensors appears, as in the attached image. I tried changing a few settings, but I was only able to remove the representations completely or leave them like that. Solutions?
[FYT Android Head Units] surfer63:
Already rebooted?

I have a Skoda Octavia with an M500S and occasionally this happens to me as well. A simple reboot fixes that. (And yes: that is a bug and should not happen at all).

I suppose it is a bug in the CANbus protocols for the VAG cars (but maybe also other brands)
[FYT Android Head Units] Irfanwani:
Can you please share the link for download
[FYT Android Head Units] Jpm888:
I was able to open up my Mekede M500s, I just want to confirm if these are the traces to be cut to disable the microphone?
[FYT Android Head Units] marchnz:
Yes
[FYT Android Head Units] Jpm888:
Thanks!!

I scraped off the two traces and mic works great now, though I didnt try it at speed,

I also added the following values to the config file

persist.sys.zlink.mic.vol=9.9

persist.sys.carlink.mic.vol=9.9

persist.audio.mic.senstivity=3

persist.btmic.gain=9

persist.btspk.gain=7
[FYT Android Head Units] Astralech:
Exactly 8200uF. No manufacturer has a 10000uF capacitor for 25V in this housing size. And the red one installed in the M6 unit does not have the manufacturer's mark.
[FYT Android Head Units] Jpm888:
Hi, what is the setting to prevent the headunit from switching to a non-existent reverse camera?
[FYT Android Head Units] zed69:
Does anyone have a cpu pinout for the UIS7862S CPU board?

My usb has failed but the hardware seems ok from the system usb cable to the pinout on the board!

I was only able to find this
[FYT Android Head Units] surfer63:
Did you even look at post #1, FYT Settings explained, before posting?
[FYT Android Head Units] marchnz:
It won't matter or make any kind of perceived improvement.
[FYT Android Head Units] marchnz:
Credit to the site that starts with a 4 and ends da. If there's any objection to sharing this, pm me.
[FYT Android Head Units] Astralech:
There is also a USB host chip between the processor and the output from the unit.
[FYT Android Head Units] Jpm888:
View attachment 6083510

I give up trying to disable the rear camera while retaining the parking sensors for now unless something new comes up. Reverse something switch in Factory disables the camera but parking sensors and reduced volume as well. I will leave the camera blank and use the radar to fill it in first while reversing

Other settings like Reversing Power Supply, cancel the reverse camera, etc dont seem to do anything with my setup.

The mic is a temporary solution because I cut my mic traces but it works surprisingly well while waiting for a mic that fits in the oem headliner
[FYT Android Head Units] FMode:
Some stupid questions:

Do we have the full datasheets with communication protocols, ... of these chips?

Does Android Automotive support these chips?
[FYT Android Head Units] j0hn83:
You won't get many, if any, after market head units that do Android Automotive.

The 7862 chipset doesn't support it AKAIK.

The newer 7870 does.

These Headunits are basic. They take a few of the cars simple wiring like lights, handbrake, etc and they use pretty sloppy 3rd party canbus boxes to display additional parameters.

Android automotive is an entire OS and needs integrated in to the car by the manufacturer to work correctly.

I've looked in the past and just did a 30 seconds Google search and I can't find a single 3rd party Android Automotive head unit.

What communication protocols were your wanting datasheets for?
[FYT Android Head Units] FMode:
Yes I now the bull**** they do. A peek inside the MTCD schematics shows the unneeded hardware and software they do instead of concentrating to relevant stuff for end user functionality.

Datasheets for radio, amp, dsp, ....

I have and know the TEF6892 in detail..
[FYT Android Head Units] Jpm888:
So I played with the Factory Settings regarding the rear camera

Local Reverse Switch:

When Off: Reverse Camera doesn't appear but parking sensors work, however Radar doesnt work properly because It will appear during a reverse and persist on the screen the entire time because the HU doesnt know that the car is no longer in reverse

When On: Camera appears, parking sensors work, Radar disappears after shifting out of reverse

This setting is not in the first post
[FYT Android Head Units] Matt Devo:
probably because it was only added to the settings in the past 6-9 months or so
[FYT Android Head Units] j0hn83:
Some yes, some no.

There's half a dozen different DSP's I'm aware of, half a dozen amps, numerous radio chips, etc etc.

I have a few head units. The cheapest has fairly low end, budget components. My recent purchase has quite high end premium components. None come with datasheets but I wouldn't expect them to.

Google is your friend for this kind of thing.
[FYT Android Head Units] surfer63:
I was a few days off and had read your post.

I also have this Local Reverse Switch to On.

I now added the setting to post #1 (thanks) and looked at it (based on your issue report) in the past 2½ days. I drove about 500 km but a lot of them in cities and had to use my reverse many times, parking in and out.

I have no issue whatsoever with the distance sensitivity image not disappearing after shifting out of reverse into forward. So I did not add your reported issue to the Settings as it is obviously something local on your device. Nobody has mentioned it before.

And I mentioned it earlier in this thread that I had it very occasionally, but that a reboot fixed it. But I did not have it in the past days or even past months.

What is your setting of the "Radar Display ON/OFF" in Settings -> Factory -> Original Car Agreement?

Mine is set to On.

And what is your setting of the "Cancel the reverse into the front view". If you have that to On and there is no front view camera, then the distance sensitivy image (radar image) might not disappear.
[FYT Android Head Units] Ashraf MK:
Hi..I got problem where I unable to control the volume after flashed to PeaceOS firmware.

The volume indicator is moving by using the side button or steering button but the no changes of sound.

However, the sound can be adjusted by Power Conditioning and EQ setting.

What the problem and how to fix it?

Btw, I’m using kernel 20240109-MKD-M6-20240118-MagiskV270.
[FYT Android Head Units] Pornete:
Hello all, i have a noob question.

UIS7862S is the same with UMS512T ?
[FYT Android Head Units] Matt Devo:
it's literally in the title of the thread and the first post...

(yes)
[FYT Android Head Units] surfer63:
Yes, but your device is not a FYT, so not compatible with all firmware/mods/etcetera mentioned here.

You have a K706. Head over to the Android Head Units sub-forum for support.
[FYT Android Head Units] Pornete:
Thanks a lot
[FYT Android Head Units] hal752:
Hi all.

I have a rooted fyt back on stock rom. Was messing around with magisk and following a few guides online was able to get it to run.

Works fine until unit goes to sleep. Likely being killed in the process.

Only way to get it to turn back on is a complete reboot.

Is there a way to prevent it being killed?

Thanks
[FYT Android Head Units] saudahmedbass:
Hello everyone

My friend has a Nakamichi 5230 10inch head unit

I was wondering if it is indeed fyt based or not

The only information i got from about device is this picture

Can you guys give me a headsup :)
[FYT Android Head Units] j0hn83:
It has a Mediatek MT8163 processor. Definitely not FYT.
[FYT Android Head Units] saudahmedbass:
so if it's not fyt then what forum do i follow?

already searched for mt8163 but didnt find any fan following for this specific model.
[FYT Android Head Units] Moldeb:
Android Head Units would be the forum for you.

OT: I feel a bit sad to see what is labelled Nakamichi nowadays...
[FYT Android Head Units] surfer63:
Correct.

And I added that table this morning after your question ;) I had already posted it somewhere else but couldn't remember where (I guess I post too much).