yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Petarkco:
I've tried editing the firmware so that apps like DAB-Z aren't killed so easily but it seems that it hasn't made too much of an effect. DAB-Z will open in the background when I start the car in the morning but the app won't actually load, I have to switch to it to get it to start.

Is this expected or is there anything that I can change?
[FYT Android Head Units] surfer63:
What do you actually want?

That the app isn't killed ór that it starts when your unit starts?

DAB-Z itself has in its settings under General: "Automatically start when USB device has been found". That event happens on every cold boot and warm boot as USB devices are disconnected and reconnected on (un)sleep and boot.

Your FYT uis7862 has in its Settings under "User" (one from the bottom), the option "Application Setting". That allows you to autostart any app on cold boot or warm boot.

From my point of view you don't need the nokill option at all.
[FYT Android Head Units] Sarsbucket:
Im assuming your APK worked properly, and I do not have an FYT based system. If that is the case, can you point me to the right thread? Im somewhat new to modding android based devices, but I want to know what I can do with the system I have. Im also going to assume either of the backup scripts linked in this thread will not work for me either. I will keep looking for more info in the meantime.

Its an SPRD UMS512_1H10_Natv, TS10 4+64, 10 quince tart API 29

FW : TS10.1.2_20210301.141702_THEME1

MCU : TS10.1.1-300-10-A4C689-210129(GD330)
[FYT Android Head Units] Moldeb:
Check in BT settings whether the OBD adapter is listed under paired devices. If it is paired, OBD apps such as Carscanner can be configured to connect to it. If it is not listed under paired, you need to pair. If that does not work with the BT standard module (1, 7, whatever), try BT module 0 in config.txt as described above and it should pair. If you change the BT module, you will likely have to re-pair your smartphone as well but then everything should be working.
[FYT Android Head Units] Fredday:
Ok thanks, so I just need to adjust the config file together with an isec6315 file right?
[FYT Android Head Units] Moldeb:
As described in Post #2 or so.
[FYT Android Head Units] Dietama:
hello i need some help, recently i buy m6Pro my radar reverse stop working, any help sir ?

this is my radar socket 🥲
[FYT Android Head Units] Fredday:
Sadly no luck. BT even became worse as it would link with my phone but wouldn't play music from it anymore and so on. I also tried to change to '1' but then it wouldn't even scan. Guess my obd dongle they delivered is just faulty.
[FYT Android Head Units] surfer63:
That's exactly why it is mentioned in post #1

This thread is NOT meant for:

buyers advice (is this one better than that one?)

4G providers, DAB+ modules or DAB+ software (see here for DAB-Z by @realzoulou), Navradio+ (see NavRadio+ ported to UIS7862-FYT devices by @KoTiX2 , sub-woofers, OEM cameras, OBD devices, TPMS or other peripheral devices.

ABSOLUTELY NOT for posts about "what is/are your favorite app(s)?"

Questions about repairs, warranty and the like. That is between you and the reseller. Questions about interchangeabilty of hardware are OK.
[FYT Android Head Units] InElement:
Apologies, I didn't think this qualified as a favourite app question, as it was more of a general setup question in my mind. I did read the post — I'll make sure to keep my comments/questions more technically-oriented in this thread.
[FYT Android Head Units] surfer63:
Added a Q28 in post #1. my Bluetooth knowledge in general is OK, but BT inside the units is not my strong point. In case of additions/corrections, let me know.
[FYT Android Head Units] mikemat.pl:
After several changes of different firmware, almost all works perfectly.

I have a problem with Bluetooth. When I call someone or want to listen to music from my phone, I can't hear the sound in the speakers. Also no other sound can be heard from the phone via BT.

The phone's microphone transmits sound normally via BT and the caller can hear me.

Is there a setting in config.txt or in android itself on the station that needs to be changed ?

Regards

MM
[FYT Android Head Units] Fredday:
Yes, I had the same issue when I was playing around with the bluetooth settings. Simply check in your config.txt for this: sys.fyt.bluetooth_type=1

The last number can be 0, 1 or 7 so simply change the one you have now with any of those 3 and try again.

Simply flash with the config.txt and an updated isec file.

Note that you will have to re-pair with your phone everytime you change this setting.
[FYT Android Head Units] mikemat.pl:
Can i flash only new config? How can i do that?
[FYT Android Head Units] surfer63:
Copy ONLY the lsec6315update and your modified config.txt to a USB-stick and put that into the unit
[FYT Android Head Units] kemdau:
Hi everyone,

I have an panel L10P8-MIPI-SAT095BO30I42R19-7705N_720X1280 20230524, I can't find LCDconfig.cfg for this panel so please help me (I would like to use this panel for other unit)
[FYT Android Head Units] surfer63:
Attached the "L10P8-MIPI-SAT-SC7705_720X1280". It should be OK, I think.
[FYT Android Head Units] kemdau:
I already tried this file but no success. My panel is SC7795N
[FYT Android Head Units] surfer63:
Then why do you say it is L10P8-MIPI-SAT095BO30I42R19-7705N_720X1280 20230524?
[FYT Android Head Units] Fredday:
Alas! I give up on my obd2 dongle, no matter what I do it never shows up on either my unit or smartphone. Even though it does work as it's getting power and shows that it's searching for other BT devices.

So this leads me to believe that either the obd2 dongle is faulty? Or is it that the obd2 dongle is using an outdated BT protocol and that's why it's not showing? Is there a way to find out if this is the case? I'm reading mixed reviews online stating bluetooth 5.2 should be backwards compatible with older bluetooth devices so it's unclear to me.
[FYT Android Head Units] kemdau:
Sorry, it's correct 7705N not SC7705N, anyway, I tested your file but still black screen.
[FYT Android Head Units] surfer63:
OK.

I have 144 config files where 12 are SC7705 version, but not one 7705N.
[FYT Android Head Units] kemdau:
I have one full unit FYT with this panel, do you know how to extract this config file from system ?
[FYT Android Head Units] surfer63:
No, I don't. But I haven't searched either.
[FYT Android Head Units] gordgelin:
it is possible to extract, but before that we can try to find correct one. go to system info and press System Info line and make screen shot of the information inside green rectangle. there you can see proper config name
[FYT Android Head Units] surfer63:
He mentioned that he already has a black screen.
[FYT Android Head Units] gordgelin:
but if he has black screen there is nothing to extract already. i thought he has other working unit to extract
[FYT Android Head Units] 舒特黃:
Looking forward to the masters sharing cc3 2k 360(7862) help to extract the system kernel from the new 6315_1.zip
[FYT Android Head Units] surfer63:
For what reason?

The YHCL kernel is of likewise release date/time. So why extract the T'eyes kernel?
[FYT Android Head Units] 舒特黃:
Thanks for the reply Master You are right!

In fact, the system kernel of 7862 is fine,

As shown in the attached picture, my system is a bit old
[FYT Android Head Units] Clandaries:
Now that it is posdible to install Whatsapp on our head units and connect it with our Smartphones it is posdible to make speech messages via the head unit but the mic is so low again.

Is it somehow possible to per config to boost the volume for WhatsApp?

Like persist.sys.whatsapp.mic.vol=

Can this work?
[FYT Android Head Units] warata:
hello

Is it possible to command "toggle split screen" from FytHWOneKey system call? What syntax do I need to use?
[FYT Android Head Units] kemdau:
Here is config for this panel in other mainboard. Please help.
[FYT Android Head Units] kemdau:
Yes i have other unit to extract config panel file if possible ?
[FYT Android Head Units] gordgelin:
contact me via PM/conversation. i will try to help
[FYT Android Head Units] karkoura:
any Telegram group for 7862 ??
[FYT Android Head Units] mastrv:
Best to keep things here to share info. Telegram is probably good for specific issues or long or detailed discussions where, hopefully, summary and conclusions are posted back here.

My 2 cents.
[FYT Android Head Units] karkoura:
wise words
[FYT Android Head Units] kemdau:
Thanks for help. It's ok now. I attached my LCDconfig for L10P8-MIPI-SAT095BO30I42R19-7705N_720X1280
[FYT Android Head Units] since1469:
您好，我是9853的，到現在為止一直受益於您的信息。

目前我這裡收到的機器據說是真正的android 12，

因為我收到的固件包名稱，以及啟動文件和allapp密碼完全不同。連直接安裝ui都無法安裝。

問了廠子說要改成這樣了~

不知道有沒有辦法知道壓縮密碼？

（如有需要我可以上傳固件）
[FYT Android Head Units] surfer63:
This forum is manadatory in English. Use that, if necessary via Google translate.

As you have a sc9853i, this firmware will never work as it is for a uis786.

Even apart from the fact that that an sc9863i is a 64bit Intel and the uis7862 an arm 64bit Rockchip.

Passwords for the AllAppUpdate.bin are in post #2
[FYT Android Head Units] gordgelin:
password for AllAppUpdae.bin changed with Android 12 release but even if you know it you can't just change there anything like before. They are trying to prevent all the old good ways of modification approaches. So for now you stuck with stock firmware. Units with Android 12 just staring to appear here and there so you have to wait while it spreads and we get to know it better

you can share your firmware of course
[FYT Android Head Units] Clandaries:
I just wrote with a seller where i maybe want to buy a 13 inch head unit if it is possible, when i buy now buy their Android 10 head unit, to upgrade to Android 12 in the future.

They really tried to tell me that they have real Android 12 with API 29. Sometimes i think they dont even know what they sell..

And now they dont say friend anymore, now they say brother :)
[FYT Android Head Units] gordgelin:
you know what this mean )))
[FYT Android Head Units] lucianoboci@gmail.com:
i have the same prob on Range rover sport
[FYT Android Head Units] farhanito:
can i restore a backup to a different screen resolution device?

i have made AllAppUpdate backup from my 1280x800 device and planning to restore it to my other 1280x720 device.

both have the same fyt.manufacturer (1)

thanks
[FYT Android Head Units] gordgelin:
no, some apps are resolution (launchers, radio, music apps etc) and hardware (equalizer) dependent so better do not do it if you are not sure. but you can try of course if you have original firmware to restore device
[FYT Android Head Units] since1469:
OK~ tks

What I mean is that I bought an android 12 machine now, and the current password is completely different from the boot file~~

It may not be so fast to wait for the password to come out.

I can upload firmware if needed

Thanks
[FYT Android Head Units] since1469:
There are indeed 12 machines now~ for real

But the compression password and change method, even the ui cannot be changed, and the signature is also different
[FYT Android Head Units] since1469:
Yes, thank you for your reply.

For now, we can only wait,

After reading the signature, it is also different, and there is no recovery, so there is no way to root.

only through adb
[FYT Android Head Units] Clandaries:
Yes, but API 29 is Android 10. So if a seller tells you they have real Android 12 with API 29 its fake, or am i wrong?
[FYT Android Head Units] gordgelin:
yes, nowadays they already have android 13 api 29 )))
[FYT Android Head Units] tlf55:
Hi guys, i have a Mekede M500S for my GOLF MK6 but the screen is washed out, i tried some settings in factory : VCOM and AVDD but it doesn't do anything is that normal ? on my old unit (on my old car FORD MONDEO) this settings was the settings i changed to have better gamma calibration.. Here it does nothing, so is it normal ? Or do i need to change anything else to have a better gamma calibration ?
[FYT Android Head Units] Latif444:
Hello,

I have got 1200X2000 FYT UIS7862

the problem i have is the landscape of the app when i use the font is too small to us it like in Youtube or google map.

any idea how to change it ?

Thank you
[FYT Android Head Units] sly2:
I bought a Mekede M700S. Inside is the S version of the 7862, but I have a big problem with it. The USB ports have stopped working. I installed the following where the USB still worked:

- MD without maintenance kernel with root

- Peace OS

- mod ms

- DAB-Z for DAB+ USB dongle

- DVR software for USB DVR

It ran normally at the beginning, DAB+ was great, and either I set something wrong or the USB ports broke. Nothing is recognized on USB, not even the firmware updates on a flash drive. I tried the 4 x reset trick and nothing, but picture comes up with message "No command" or something and the system boots normally. I tried the method of 4pda with USB hub reset (I have root), but without success... Otherwise everything works fine without problems.

Does anyone of you have an idea if this could be wrong settings or a hardware problem?

the data is similar to the picture on the post #2630, only screen is qled 1280x720

Thank You
[FYT Android Head Units] nurex:
i have a new Mekede M700S QLED

I have a problem with the USB. An hour ago the USB ports were still working, now all USB ports are no longer working. Why is that???

USB sticks, DAB+ and TPMS are no longer recognized
[FYT Android Head Units] sly2:
it's like my problem, but no one answered until now
[FYT Android Head Units] papero1159:
Hi,

Being ignorant on the subject and even though I have read and reread the posts without understanding much, I prefer to ask my question directly, having a sinosmart 7862s purchased in may 2023 , I would like to replace the firmware with one

( conserving steering wheel controls) that does not block the google assistant call function and correct others block that the manufacturer has installed in the firmware.

Is this possible?

Thank you

Ps: sorry for bad English
[FYT Android Head Units] nurex:
I also have the M700S with QLED and also had the MD kernel on it.

It's 2 days old
[FYT Android Head Units] sly2:
I think, it's hardware fault, but maybe the kernel is not 100% compatible...
[FYT Android Head Units] surfer63:
If it worked fine before it is unlikely that it is due to the MD kernel.

If you can't flash it with the 4x reset option and that error, the recovery couldn't find a good firmware on the USB-stick, or no lsec6315, or a corrupt USB-stick. The first to do is to do a checkdsk on your uSB-stick and check the rest.

"had the MD kernel on it"? Not anymore?

Then what did you flash it with afterwards?

And what is 2 days old? your unit? or that you flashed it with MD-kernel? or 2 days after you replaced the MD-kernel?

Be specific !

The uis7862 and uis7862S are the same chip. It can be that the USB-kernel drivers have slightly changed or expanded.

If you mange to get your USB-stick correct or the USB-stick configuration, you can try to flash it with the MD-kernel from the YHCL firmware from this thread. That one is based on a uis78962s kernel.
[FYT Android Head Units] sly2:
I checked my USB-Stick many times, because I tried all to back the USB to life the last 3 days...

I checked, that I can flash kernel direct from intern flash and I will try the YHCL kernel...

and send the kernel through wifi goes quick :)

thank You! :)

the strange thing was, it worked normally at the beginning, with DAB+, DVR and USB stick on the three USB ports and it came, i think, after a reboot or return from deep sleep, but i'm not so sure about that
[FYT Android Head Units] nurex:
The unit is 2 days old and yesterday evening I flashed the MD kernel with a new USB stick. The MD kernel is still in the unit now. I have already reset to factory settings, but the MD kernel still remains in the unit. Is there a way to flash via Wifi
[FYT Android Head Units] sly2:
You have to copy the kernel with wifi or bluetooth to the root of the internal flash... i think, that's enough, and if not, then also lsec6315update

I will check it tomorrow morning and then I will get back here
[FYT Android Head Units] nurex:
then I can download the kernel directly from the head unit with the Internet browser into the internal root.

ok, I'm waiting for your reply. I have to work all day tomorrow and I won't be able to test it until tomorrow evening
[FYT Android Head Units] surfer63:
That is a way to do it, but not the preferred way.

Better use a USB-stick.
[FYT Android Head Units] sly2:
when it works...
[FYT Android Head Units] Pino1966:
Hi guys, I also have the certain problem with the stick, since I flashed the MD kernel, that the usb stick is no longer recognized, have not mentioned anything until now, because I thought it would be due to my sticks
[FYT Android Head Units] nurex:
Ah ok, so the hope is rising that it's really just a software/driver problem from the MD kernel. 👍
[FYT Android Head Units] 03hdfatboy:
Reflash it, but add the OEM all app update to it. I corrected an after flash Bluetooth issue that way. If USB isn't working, does it have an SD slot?
[FYT Android Head Units] tlf55:
So no one have this issue about VCOM and AVDD doing nothing and not changing anything about the screen color ?

Does MD kernel have kcal feature ?
[FYT Android Head Units] laoyang88:
Maybe change the mic gain here. I don't have root. Please try it. Feedback result
[FYT Android Head Units] sly2:
I flashed the YHCL rooted kernel, but after that no changes, maybe I have to flash AllAppUpdate.bin too. Maybe the apps from PeaceOS are too old for this unit?

I will try it today afternoon.

Copying only the 6315_1.zip don't starts the update, I had to copy lsec6315update, my config.txt, updatecfg.txt and my fyt.prop to the flash root and reboot the unit.
[FYT Android Head Units] surfer63:
If you want to flash "something" from the usb-stick you always start with the lsec6315update.

And then it is up to you what you want to add.

Please read the documentation in post #1 and #2. It seems that you are now in a trial & error mode and only have some partial knowledge.

It is no use to anyone of us answering your questions or making remarks on your statement.

You "complained" earlier that "nobody had "answered". Users get tired of this if you don't do your "homework".
[FYT Android Head Units] sly2:
I have read the whole thread here and the first posts many times, only with 6315_1.zip and lsec6315update the update not started... and You know, my USB ports are not working and I can't use an USB flash drive...

I try really to do my "homework" first and seek for informations not only here, but I will try to read more and more...
[FYT Android Head Units] surfer63:
You are right that you mentioned that your USB ports do not work when running the "normal" system, but they do work when you flash something from USB.

And sorry that I was too harsh in stating that you hadn't done your homework.

The current PeaceOS zip file is based on an Android 8.0.0 launcher from the PX5 (before the SC9853i and before the uis7862/uis8581a). That means it might not support "some things" the newer launchers for the newer firmwares do.

Next to that: In the PX5 time only 2 USB ports were supported. All the new units (having newer firmeware) have 3 USB ports. This might be another reason in combination with that old launcher, but that is just a guess and maybe completely wrong. After all, you were always able to expand the ports with USB-hubs . Did you try all 3 USB-ports? Next to that: some USB-ports are 6-wired, some other are 4-wired, so less intelligent.

@LLIyT_HuK just released a beta launcher34 (Android 10/SDK29) for PeaceOS in the Russian "community". It is optimized for 2000x1200, but will work for 1280x720 but needs some finetunig there. You might try that one with your current setup and USB ports.
[FYT Android Head Units] sly2:
As I have already written, I used the 3 x reset method without success. It always came "no command" and I tried the USB stick on all three ports, and yes one USB port is 4-wired and two next USB ports are 6-wired with stickers USB1 and USB2. My USB stick works with computer but I will format it and try again.

This with an external USB-hub is a good Idea, I will try it!

I had PX5 before, is now in the box :)

I will look at the russian board for the new launcher and try it, I have today time for this all.

Thank You very much :)
[FYT Android Head Units] nurex:
I only flashed the MD kernel and no USB works. So this can't be because of PeaceOS. I will flash the complete original complete firmware later and report
[FYT Android Head Units] surfer63:
I have a Mekede M500S and I use the optimized YHCL kernel with the "MKD M6PLUS-UI29R-4L-8502k-20230602-lzp" AllAppUpdate.bin (so an M6Pro application layer on a normal uis7862).

Everything works.

Currently building two new kernels based on the EKIY 20230718 kernel. I will try to test this afternoon.

Edit: Note that when you use the M6Pro AllAppUpdate.bin you must still use the config.txt from your normal unit.
[FYT Android Head Units] nurex:
I have flashed OEM firmware and there is an error message with the build.prop every time. I can't flash the MD kernel anymore, there are only error messages
[FYT Android Head Units] surfer63:
You should not try to flash the fyt.prop. Why dod you do that?

If you want to have the correct fytmanufacturer id and some other properties, you copy it out of the fyt.prop into the config,txt.
[FYT Android Head Units] nurex:
I just flashed the factory firmware because my USB ports don't work either.
[FYT Android Head Units] nurex:
Can you do that again with the build.prop? If so, how?
[FYT Android Head Units] sly2:
are the usb ports working now?

btw. You flashed a full system with AllAppUpdate and You should flash only kernel, I think...
[FYT Android Head Units] surfer63:
No, you can't.

Those prop(erty) files are read by the system.

The FYT application later comes after the system and reads the fyt.prop and config.txt.
[FYT Android Head Units] nurex:
Nein, USB ohne Funktion. Ich hatte zuerst den Kernel geflasht, aber es gab viele Fehler. Als letzte Lösung habe ich dann die Werksfirmware geflasht...
[FYT Android Head Units] sly2:
I think, I wrote in english, aber was solls, ich antworte auf deutsch. Das ist ziemlich schlecht und sieht mir wirklich nach einem Hardwarefehler aus... :(

Ich habe mein Radio ausgebaut und versuche jetzt zuhause etwas zu erreichen. Jetzt werde ich den neusten Kernel von Surfer63 ausprobieren.

here the translation for all others:

This is pretty bad and really looks like a hardware failure to me.... :(

I removed my radio and now I'm trying to do something at home. Now I will try the latest kernel from Surfer63.
[FYT Android Head Units] nurex:
in deutsch liest es sich doch schon viel angenehmer 😅👍

Kannst mir ja ma berichten wie es mit dem Kernel läuft.
[FYT Android Head Units] nurex:
So this error with the build.prop when flashing will now always remain? I think I'll throw the unit in the trash.... without USB, it's useless for me. I strongly assume that the USB problem for me is a software error
[FYT Android Head Units] sly2:
kannst Du dein System überhaupt starten?

can you boot your system at all?
[FYT Android Head Units] nurex:
yes, I can use everything normally, except for the 3 USB ports and no GPS Fix
[FYT Android Head Units] surfer63:
Are you now talking about the build.prop or the fyt.prop?
[FYT Android Head Units] nurex:
Sorry fyt.prop
[FYT Android Head Units] Pino1966:
Hi everyone, what kind of sim card can you use with mekede m600s fyt116, nano or micro and how is it plugged in, thanks for your help
[FYT Android Head Units] nurex:
My M700S apparently has a problem with fyt.prop when flashing. What happens if my unit can't read it? Then, among other things, USB would also be gone, wouldn't it?
[FYT Android Head Units] George2005:
I'm looking for the "F-CAM" application for FYT based unit which allows to show picture either from front camera or rear camera (even the reverse gear is not active). I've found that such application is available on PX5/PX6 units but I've not found nothing similar in my new FarCar S400 unit.