yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] gordgelin:
he is that one who asked how to make firmware "more google like" some time ago where i explained why moving software from /oem to some random place is bad idea and many apps will be broken, he faced it and just replaced all broken apps with other. teyes activation was received via teyes support as he owns teyes x1 also (dead now)

also his approach with repartitioning leads to losing some sensitive device data which might never be recovered
[FYT Android Head Units] ahmed68:
you always say that my firmware is wrong, you can’t do this, then I see that your firmware is much worse, stop behaving like this, tell the truth anyway, he already knows many people, especially who bought the firmware from you, that they shouldn’t have done it, I can give more than 30 reviews about your firmware
[FYT Android Head Units] ahmed68:
you add vve in super i cant understand you , i can't move all applications from oem but you can move all applications from oem to vve in super i think its to bad to add more part in the super
[FYT Android Head Units] gordgelin:
this is simultaneously false and true statement at the same time

false about super block and true about you can't understand
[FYT Android Head Units] gordgelin:
anyone can do this but this is wrong approach, that is why you had to replace all the broken apps with versions which can work from /product and you know it
[FYT Android Head Units] gordgelin:
better give reviews about those people from 4pda who lost forever (unless they contact support) their original teyes activation when flashed your repartitioned firmware
[FYT Android Head Units] ahmed68:
again you are not telling the truth, show me at least one case, you are not ashamed
[FYT Android Head Units] gordgelin:
you can find some messages in teyes x1 thread addressed directly to you from people who tried your repartitioned firmware and got activation error when tried to go back to stock. so they stuck with your rc2 for now or other mod without original teyes apps

i've warned you about this month or two ago when you created this rom but you ignored and told me it is not my business to worry about these people
[FYT Android Head Units] ahmed68:
almost everyone on the x1 4g forum installed rc2 then returned to stock, no one wrote that there was a problem, I asked to show one example or case , I have more than 30 screenshots that people wrote to me about your firmware
[FYT Android Head Units] gordgelin:
i'll send you direct links to messages at 4pda if you somehow missed them, but is not possible since you answered them
[FYT Android Head Units] ahmed68:
i cant , u can but it here
[FYT Android Head Units] gordgelin:
it will be against xda rules to post links here so i'll send 'em to you directly

chances for activation to be lost forever with your repartitioned rom are 100% but not always it is immediate effect, time depends on device usage scenario, so for sure some people have successfully returned to stock, their luck

i just can't get why you don't understand it since you have lost activation yourself, at least twice from what i know from your 4pda posts...

P.S. sent you some links directly to messenger
[FYT Android Head Units] surfer63:
@ahmed68 and @gordgelin : Please stop this here.
[FYT Android Head Units] Specy01:
I repeat it too, Surfer anticipated me. These last posts are not nice to read in my opinion. Thank.
[FYT Android Head Units] gordgelin:
@Specy01, @surfer63 sorry guys i tried my best, hope this will not happen again
[FYT Android Head Units] ahmed68:
I want to write instructions about activating the system after replacing emmc , everyone should understand that activation is tied to uuid , uuid is formed from cid emmc , when replacing emmc that there was no plant reboot, two blocks from your dump are needed

l_fixnv1 and l_fixnv2 , you must clear the firmware from the old uuid To do this you need to activate adb through the developer menu then reboot into fastboot , then execute the following commands in turn :

fastboot erase uboot_log

fastboot erase sysdumpdb

fastboot erase metadata

fastboot erase misc

fastboot erase l_runtimenv1

fastboot -w

I took all these commands from SPD_Research_Tool , I recommend formatting more fytdata and lsecfs , only in fytdata the monitor configuration is saved and needs to be restored , lsecfs will keep the old activation file , If there is anything unclear, write to me, I will help .I didn't format uboot .
[FYT Android Head Units] gordgelin:
this is correct, without this original data emmc replacement not possible at the moment

this is terribly wrong, please never ever do this under any circumstances on your original rom
[FYT Android Head Units] gordgelin:
and this part is generally useless, but won't do any harm
[FYT Android Head Units] gordgelin:
this is blink activation, as you can read from .blink folder name, nothing to do with device activation
[FYT Android Head Units] marchnz:
I'm super interested to hear the technical details of what is being discussed.

Could this discussion progress and talking just the technical points?
[FYT Android Head Units] ahmed68:
maybe you're right but what if in fytdata save old uuid and lsecfs have old .license.dat and .serialNum.index
[FYT Android Head Units] marchnz:
No problems. So good to have you here. That goes for both, and where there is technical disagreement, that's good to make your point known!
[FYT Android Head Units] ahmed68:
Of course I didn't mean to offend anyone, if this happened I'm very sorry
[FYT Android Head Units] marchnz:
Great reply! I for one really appreciate the technical discussion you guys bring!
[FYT Android Head Units] gordgelin:
if it is someone else's dump and not your original then yes, fill free to format, there will be no difference
[FYT Android Head Units] ahmed68:
now I want to understand how ResearchDownload generates l_fixnv1 and l_fixnv2 , only these two blocks are needed to replace emmc
[FYT Android Head Units] gordgelin:
my take is simple - i'm opposing his approach with changing original partition layout what leads to losing some device exclusive data with high probability of future problems especially with heavily branded units like teyes. and also his approach with moving oem software to different partition (f.e. /product) since many chinese apps with external resources will stop working 'coz resources paths are often hardcoded into app and sometime even deep in the system, he already faced it and "resolved" by replacing all these apps with simplier versions which do not require strict install path. i do not see any reason why any of these apps should be somewhere else since this is one of that very platform related things which makes difference between fyt and some generic chinese phone with same cpu
[FYT Android Head Units] gordgelin:
it does not. it just reads out original device data and "puts" it back after flashing done, so if device is already dead, flashing will not help
[FYT Android Head Units] matrixx1:
Hi I lost the option to put apps into split screen. If you press the recent button to get the apps to be shown there was on top of every app a button so you can put them into split screen. I don't have this button anymore, it's gone. Did anyone faced this issue? Is there a solution?
[FYT Android Head Units] Specy01:
Today I updated my Navifly M700S (fyt 7862) with the firmware of the Mekede site (kernel of 23/09/23 and app of 07/09/2023) as you can see from the photo

I do not remember if it has already been described before, but, among the settings appeared the setting "fan setting" that I had never had before, see photo

Acting on this setting the options are: "do not turn" and "always run"

Despite acting on one of the two options it seems that the option does not work that is, it always remains on "do not turn", even if the HU is restarted as you can see from the video, the setting does not change. Is it a bug? Or does it happen to you too?

Excuse me but I can't put in the post the video.

However, among the apps, there is an app called "fan" and from here you can make the fan work as you want, at least so it seemed to me for that little time I tried it

Another new setting that I found in the settings is: "temperature left and right exchange", I still haven't tried it, but I set it to on.

@surfer63 if you think it appropriate you can update your first post with the new settings.

I hope I was helpful.
[FYT Android Head Units] heavyhms:
My m6 8/256 has

ro.build.fytmanufacter = 116

mcu è 2022.10.29 16:05:46 YIN_53_L6315_N32P48F64_E60_V:1.0

What is the manufacturer?
[FYT Android Head Units] faria:
FYT unit, "manufacturer" = Mekede/Navifly.
[FYT Android Head Units] Specy01:
I am not very experienced but I can tell you that your features are very similar to my Navifly M700S (Fyt 7862) 8-128GB. Also my ro.build.fytmanufacter = 116 but my MCU = 2021 10 09 and is also a Yin_53_L6315 as you can see from the photo. So obviously my version of MCU is older than yours. I put it back here for convenience but I had already put it back a few posts
[FYT Android Head Units] profkerim:
hello, I know sorry, maybe it is also indicated but I do not understand, in reference to the post # 2 to disable the player I have to insert in a stick only isecupdate6315, or I must also insert the isec_update folder with the 7862? Also if after flashing with this update, I insert original update and the config.txt file, the player reactivates again? If so, does that mean I always have to have isecupdate with disable player to flash other options? thanks and sorry
[FYT Android Head Units] heavyhms:
What is the application settings menu? I can only switch on or off (by default are all off)?

Another question: I have two different wallpaper (one with light on and one with lights off). I can use custom wallpapers, but i I switch car light revert to default one (my car has only ui34 installed). How I can save wallpapers?
[FYT Android Head Units] Aran:
These are the applications that auto start when the unit (cold)starts.
[FYT Android Head Units] heavyhms:
Thankyou, do you have a similar wallpaper issue (reset to default wallpaper switching the car lights)?
[FYT Android Head Units] surfer63:
Yes, That is a bug/feature of the new PIP-window launchers. They have day/night mode, but they do switch back to their internal day/night backgrounds thereby overruling whatever background you had chosen.

For this we already modded launcher34, the most used one, to block that day/night mode switch (although as such it is a very good addition to the launchers).
[FYT Android Head Units] heavyhms:
Thank you, actually I'm trying CarLauncher pro to remedy the lack of cystomization of stock launcher. What is the difference from the stock on the customized launcher34 ?
[FYT Android Head Units] surfer63:
See my modded Launcher34 thread and the PeaceOS thread.
[FYT Android Head Units] lovefull:
help me please. my switch backup camera does not have an option. What should I do? Makes me the application 360 panorama unusable.
[FYT Android Head Units] laoyang88:
How to choose wallpaper？(one with light on and one with lights off)
[FYT Android Head Units] surfer63:
Somewhat deeper in the settings you have somethin like "original app" (I don't have my car close at the moment), you can switch on/off air conditioning notifications, door open/close, volume up/down and forward/backward (steering wheel), and parking sensors.

Those parking sensors on/off has nothing to do with the reverse camera.
[FYT Android Head Units] Petarkco:
Is there an easy way to navigate 4da to find their firmware with it all being in Russian?
[FYT Android Head Units] surfer63:
Most modern browsers allow you to "auto translate" pages. Searching is then still difficult, but if you put a normal translate page (google translate) next to it and you search for your search term like "steering wheel" (or some minor modifications) and translate that to Russian, and use that to search, you can get quite far.
[FYT Android Head Units] AxesofEvil:
Does anyone have old (maybe 9853i) versions of the com.syu.ms APK? This APK seems to be responsible for communication with the ardware, but the most recent versions are optimized/obfuscated, and decompiling leads to useless function names that are really frustrating to trace. I am trying to learn how the com.syu.canbus APK (which is not obfuscated) gets the canbus data (in the hopes that I can write my own app to access this info), and it would be really helpfu to see what syu.ms is actually doing. I am hoping to find a version that was not optimized and has meaningful variable/class/function names
[FYT Android Head Units] surfer63:
Did you try jadx (gui)? It has a "de-obfuscate" option. Works quite wel..
[FYT Android Head Units] AxesofEvil:
Thanks, that does indeed look helpful. I think I prefer the decompilers used by "Bytecode-Viewer" but it looks like jadx can deobfuscate java without the decompiling step. I will play with it some more.
[FYT Android Head Units] seb21:
Here you have 9853i ms.apk. I don't remember from which firmware version it came, but it was one of the latest before obfuscation.
[FYT Android Head Units] hanichl:
@surfer63 and all other cracks: is there a way to knock-out the formatting of Data/data on Joying firmware updates ? If yes - howto ??? If no - why not 🧐🧐
[FYT Android Head Units] surfer63:
I think it is hard-coded into the lsec binaries. This now due to the dynamic partitions.

EDIT: when using a hex-editor on the lsec6315update, it is one of the first actions done. That is if I interpret the code correctly.

Next to that: there now also seems to be a twipe_cache option.
[FYT Android Head Units] hanichl:
thanks, then this behaviour should be in all concerning firmware updates, not only a special implementation of Joying, more a general for all 7862 firmwares, right ??
[FYT Android Head Units] surfer63:
Yes, for all. the lsec6315update (for the uis7862) is the same over all FYT uis7862 units.

And as in the EDIT above:

when using a hex-editor on the lsec6315update, the wiping of /data/data is one of the first actions done. That is if I interpret the code correctly.

Next to that: there now also seems to be a twipe_cache option.
[FYT Android Head Units] Pfeffernuss:
Well that's a shame then, will have to go through it all again as there is another firmware update released :-)
[FYT Android Head Units] mariodantas:
Yes it exists and it works
[FYT Android Head Units] mrVuHoa:
Does anyone know how to change the assistant app? I am using swc key to launch the voice assisstant, everytime it's open toppal voice app and I want to change to another voice assisstant.

Thanksl
[FYT Android Head Units] Petarkco:
Hopefully someone can go through it and see what has changed if possible.
[FYT Android Head Units] mariodantas:
You can upgrade using "twipe_cache" in "updatecfg.txt" file like the example below

#test
twipe_cache

But all the contents of the /oem partition will be wiped anyway as new apps may comme in the AllAppUpdate.bin file, using twipe_cache you don't loose your previously installed apps neither your data (music videos doc etc....)
[FYT Android Head Units] surfer63:
So this means that you MUST put this into the updatecfg to prevent your 3rd party apps and settings, and storage being wiped (which is not done be default anyway. You specifically need twipe_sd for that)? Is that correct?

Some of the twipe commands work like: do this, but automatically not that. Is that here the same?
[FYT Android Head Units] mariodantas:
Didn't test with more than 1 command per run, but upgrading firmware in the past with twipe_cache and the ONLY command, my apps were in place !
[FYT Android Head Units] surfer63:
Will try that this weekend. So far I hadn't upgraded my unit especially because I had to redo everything again. And I did not encounter serious things that required a firmware flash.

Also because Mekede updated their kernel on May 6th and their AllAppUpdate.bin on May 17th.

Note: Does anyone know if Mekede mentions updates anywhere. I download occasionally and then simply check the contents, but it would be much easier to get a notification or so.
[FYT Android Head Units] Pfeffernuss:
Without that command all apps are in place as well, but as /data/data is wiped one has to setup everything again afterwards.

So with this command both apps AND their respective settings remain unaltered?
[FYT Android Head Units] surfer63:
You can't do it the normal Android way, that will only work until the next day/night shift.

What you can do is:

unzip Launcher34

in res/drawable-nodpi-v4 replace the def_bg.png and def_bg_n.png (night)

rezip the launcher.

Same for the other new launchers (27, 29, 34, 46, etc.), but wallpapers might have different names.
[FYT Android Head Units] 82crni:
does uis 8581 (bmw) have android auto option?

thank you
[FYT Android Head Units] surfer63:
Yes. wired and wireless.
[FYT Android Head Units] heavyhms:
I have this error when I try to make a backup on my M6Pro with the appbackup script from the post 4. How to solve?
[FYT Android Head Units] surfer63:
I am not sure. Everyone gets this error. The problem i also that 7zip is very inconsistent when it comes to error logging.

Check your zip to see if it does contain errors on opening. See how big it is and if it seems to contain all files.

I only saw once a corrupt zip but that was because of a corrupt usb-stick.
[FYT Android Head Units] heavyhms:
backup folder has 4 files: allupdate.bin can be extracted witch 7-zip without error. When i had the error during backup, after some minuts i had a power cycle to reboot radio (because text report the operation as concluded). Is correct or after some other minutes wil reboot by herself?
[FYT Android Head Units] 82crni:
тhank you, i will try tomorow
[FYT Android Head Units] surfer63:
I rewrote the scripts and changed from 7zip to zip, store symbolic links as links and do not try to get the linked file/folder, and added logging.

See post #4 again. Note that a "AllAppUpdate.bin.log" file is created (see also "After Backup" section in post #4.) and also added that file to the BACKUP folder.

Please let me know.
[FYT Android Head Units] heavyhms:
Thank you. After script execution, radio reboots automatically or I must shutdown and restart the car?
[FYT Android Head Units] surfer63:
After script execution you get again that green increasing counter, telling you to remove the usb-stick. Normally wait about 4-5 seconds and then remove it. Your system will automatically reboot.

And thanks for mentioning it. This is so "standard behavior" to me that I did not even think about mentioning it. I will add it to post #4.
[FYT Android Head Units] Gymnae:
Hi there,

just wondering about this bit. I'm in contact with a seller who offers a 2.0 GHz 8/128 EKIY T900 with an 2k screen but also claims it only supports BT 5.0. Looking at post #1 and this, I'd assume that it should at least, in Hardware, support BT 5.1 - I've asked what kind of Bluetooth chip they're using, waiting to hear back from them.
[FYT Android Head Units] surfer63:
He could be right. There are "old" type motherboards with the new 2.0 GHz CPU but the "old" RealTek 5.0/5.1 BT chip, and "new" type motherboards with the new 2.0 GHz CPU and the new Qualcom 5.2 BT chip.
[FYT Android Head Units] Gymnae:
I received some screenshots of the device (yes, this is without a 2k upgrade screen), but that doesn't help me in seeing if its BT 5.1/2 or 5.0.

At least I can, kinda, deduce that it's a uis7862(s) - and that they are not faking the Android version

EDIT: Are there downsides between 5.0 and 5.1 in regards to CarPlay or connecting a BT OBD dongle? The Mekede Marketing is all over their QC 5.1 chip, but I also read about bugs...
[FYT Android Head Units] heavyhms:
This is my log: allappupdate.bin can be extracted without issue.

Just a info: the key, disconnected 4 seconds after green prompt, request a automatic checkdisk when connected to pc (no errors found)
[FYT Android Head Units] surfer63:
That error is due to the fact that you did not properly unmount/remove/eject the USB-stick. The FYT software doesn't do that.

In such a case the "dirty bit" is set on the USB-stick, simply meaning that someone did not remove it properly.

Windows (and all OSes) detect that and want to check the USB-stick.

Normally when nothing is written to the USB-stick, it actually never goes wrong. That is also why I say to wait 4~5 seconds to make sure "lazy writes" have been performed as I do not know if the FYT software and shell do a "sync", before saying "that they are ready".
[FYT Android Head Units] Kaelub:
How do you do split screen? I have it enabled in developer settings. On my old ts9 topway unit, you just hit the recent apps button and then hold down on the app for a second, then drag to either side. My new unit is FYT1 7862uis natv with a 1280x720 resolution and it won't do it. I even tried changing the config.txt to have split screen=1. Anything else I should try, or are some units not able to do split screen?

I have another monitor connected using a coax to USB, and that works as a secondary display, but id still like to get split screen working.
[FYT Android Head Units] j0hn83:
Has anyone come across an issue where the head unit dials a number automatically upon their mobile phone pairing via Bluetooth?

It seems like every single time I get in my car and drive away it automatically dials the last dialled number. I can't work out if it's my phone or the head unit that's doing it.

I'm going to upgrade the kernel and firmware this week to see if that solves things.
[FYT Android Head Units] Gymnae:
I was sent this picture, I think it's indicative of a Realtek BT chip. Are there downsides to having only BT 5.0?
[FYT Android Head Units] danilaur:
in bt call why i cant see my agenda name ?
[FYT Android Head Units] faria:
you have a canbus decoder installed in the unit?
[FYT Android Head Units] rodney.oliveira:
Hello friends.

Greetings from Brazil.

I would like to ask for help with the bluettoh part of my FYT control unit 2000x1200.

I read several topics before deciding to post this message and some procedures helped me a lot! I thank you all.

My case is related to bluetooth. When I receive a notification on my cell phone, the music that is playing stops playing for a few seconds and then comes back. I tested on 2 devices, Galaxy Note 20 Ultra and Note 10. I already changed the bluetooth setting sys.fyt.bluetooth_type to 1,7 and 8 and the adapter stopped working, so I returned it to default = 0 (the only way the solution is manually select cell phone media output)

I tried to disable the Bluetooth audio option on my cell phone but the calls don't work correctly, even though I keep the calls option checked.

Is there any setting that allows the Bluetooth function to play media in the background without the need to have the application open on the multimedia center or another way for notifications to not pause music playback?

I forgot to mention that Bluetooth cannot connect to more than one device at the same time and also cannot pair with other types of Bluetooth devices, such as gas paddle, OBD...

The Bluetooth anchorage option is also not saved, I activate it but when I disconnect the cell phone it automatically deactivates.

Thanks!
[FYT Android Head Units] faria:
please post you unit maker/model.

For connecting obd dongles follow this instructions:

Go to the phone app and reset the bt settings.

Pair the obd dongle first then pair the phone etc.
[FYT Android Head Units] rodney.oliveira:
hello friend. Thanks for the answer, I'll try this way with the OBD. Here's an image of the settings:

Is it possible to find out the manufacturer with these images or do I need to check another way?
[FYT Android Head Units] old.splatterhand:
Hej guys, i'm asking myself if someone can give me the LCD panel files for my headunit?

My unit works fine at the moment, but i want to have it here at hand in case something goes wrong.
[FYT Android Head Units] fourlo:
Czy układ z tego wątku będzie pasował do mojego radia? Mój procesor to Spreadtrum UMS512
[FYT Android Head Units] faria:
Here are 2, an old an a new one.