General General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware

Search This thread
By:
Advanced…
bog20

bog20

Member
Feb 4, 2023
5
0
Try change your Canbus setting to "Raise->Honda->CRV->2015-Now (Mid-High)", the first one "Raise" depends on what brand of canbus devices you have gotten.

Hello
Thank you for your quick response.
I have tried all Honda models and the temperature is always in Farenheit.
I suspect that the problem is in Canbus.apk in the Joying Firmware. I had the Canbus box connected to the Joying Radio with Android 8.1 and it worked, I could switch from Farenheit to Celsius and vice versa without any problems.

CanBus Box.jpg
 
surfer63

surfer63

Senior Member
May 4, 2010
4,779
2,275
Zwolle
github.com
bog20 said:
Try change your Canbus setting to "Raise->Honda->CRV->2015-Now (Mid-High)", the first one "Raise" depends on what brand of canbus devices you have gotten.

Hello
Thank you for your quick response.
I have tried all Honda models and the temperature is always in Farenheit.
I suspect that the problem is in Canbus.apk in the Joying Firmware. I had the Canbus box connected to the Joying Radio with Android 8.1 and it worked, I could switch from Farenheit to Celsius and vice versa without any problems.
Click to expand...
Click to collapse
Maybe not. The new units also have an apk to configure certain settings inside your car via the CANbus, like car menu language, your C/F, etc.
Did you already have a look at that one?
 
bog20

bog20

Member
Feb 4, 2023
5
0
surfer63 said:
Maybe not. The new units also have an apk to configure certain settings inside your car via the CANbus, like car menu language, your C/F, etc.
Did you already have a look at that one?
Click to expand...
Click to collapse
I did that, I checked all possible settings, the outside temperature is in °Celsius, the temperature of the radio cpu too. Only the climate temperature is in Farenheit, sometimes the temperature is shown very briefly in °Celsius.

In the Civic forum, people have problems switching from °Celsius to Farenheit.

Screenshot (53).png
 
Last edited:
J

j0hn83

Senior Member
Jan 5, 2012
104
45
Have you checked the app called "Vehicle Settings" for anything related to C/F?

The contents of the vehicle settings app changes between different car makes/models chosen in the canbus settings. It contains some additional canbus settings for some models.
For some makes and models the vehicle settings app disappears completely.
So it might be worth trying different Hondas and returning to the vehicle settings app in-between each try.
 
bog20

bog20

Member
Feb 4, 2023
5
0
j0hn83 said:
Have you checked the app called "Vehicle Settings" for anything related to C/F?

The contents of the vehicle settings app changes between different car makes/models chosen in the canbus settings. It contains some additional canbus settings for some models.
For some makes and models the vehicle settings app disappears completely.
So it might be worth trying different Hondas and returning to the vehicle settings app in-between each try.
Click to expand...
Click to collapse
OK
I'll try that tomorrow and report back.
Thanks
 
P

pir8man

Senior Member
Nov 25, 2007
320
87
Samsung Galaxy S21
Samsung Galaxy S22
I cannot get hosts_add_blocker.zip to function.
I get a permission error mounting /system as rw.
using: lsec6315update and 7862lsec.sh from inside the zip.
on UIS7862 FYT device running 12-09-2022 kernel (MD Edition from Mario Dantes).

I also tried manually copying with root access via Root Explorer and total commander. Both fail.

not sure if this is because of newer lsec6315update v7.82, or ???
I cannot use lsec6315update v6.32 as it refuses to run when it sees the newer kernel.
 
F

fabiodedo

Member
Feb 18, 2011
22
4
Hi, I couldn't find the solution to my problem (if any...):
the bluetooth app that manages phone calls on mekede m700s is really worth it, can it be replaced with some other app?
is there a way to have contact names in recent calls list? the names appear only in the contacts directory but not in the call log (only the numbers appear).
Thanks everyone for any solutions
 
surfer63

surfer63

Senior Member
May 4, 2010
4,779
2,275
Zwolle
github.com
pir8man said:
I cannot get hosts_add_blocker.zip to function.
I get a permission error mounting /system as rw.
using: lsec6315update and 7862lsec.sh from inside the zip.
on UIS7862 FYT device running 12-09-2022 kernel (MD Edition from Mario Dantes).

I also tried manually copying with root access via Root Explorer and total commander. Both fail.

not sure if this is because of newer lsec6315update v7.82, or ???
I cannot use lsec6315update v6.32 as it refuses to run when it sees the newer kernel.
Click to expand...
Click to collapse
Why didn't you read the first posts? They clearly mention that in the new super-partition model the /system can't be made read-write.
 
  • Like
Reactions: marchnz
M

matsonjb

Member
Jan 29, 2009
15
1
So I'm trying to figure out my new radio. I have two conflicting numbers; I found this information as I am looking into flashing my radio but having issues trying to find a proper firmware.

My radio shows an MCU of HYI and yet a Serial Number of 53 so I am confused for what to look for as I mod.

1. FYT = 51 ro.build.fytmanufacturer = 51 MCU HYI ZWNAV Yulbro car multimedia Store
2. FYT = 53 ro.build.fytmanufacturer = 53 MCU ZHAN WINCA FARCAR DAYSTAR UNISON

I'm trying to enable bluetooth for ODB2 and I am having issues with the typical flashing as I get errors while I am pushing the firm.

Any thoughts?
 
  • Like
Reactions: marchnz
P

pir8man

Senior Member
Nov 25, 2007
320
87
Samsung Galaxy S21
Samsung Galaxy S22
matsonjb said:
So I'm trying to figure out my new radio. I have two conflicting numbers; I found this information as I am looking into flashing my radio but having issues trying to find a proper firmware.

My radio shows an MCU of HYI and yet a Serial Number of 53 so I am confused for what to look for as I mod.

1. FYT = 51 ro.build.fytmanufacturer = 51 MCU HYI ZWNAV Yulbro car multimedia Store
2. FYT = 53 ro.build.fytmanufacturer = 53 MCU ZHAN WINCA FARCAR DAYSTAR UNISON

I'm trying to enable bluetooth for ODB2 and I am having issues with the typical flashing as I get errors while I am pushing the firm.

Any thoughts?
Click to expand...
Click to collapse
run FYTbackup on your oem setup... read ro.build.fytmanufacturer from the files cretaed on usb stick
edit allappupdate.bin to match in new firmware package..
 
  • Like
Reactions: marchnz and surfer63
D

DexterMorganNL

Senior Member
Dec 1, 2010
1,066
173
Does someone have a newer version from Carlink? I got a new phone, and ever since Coolwalk is out Android Auto keeps disconnecting. No idea what's the issue this time?

But perhaps there is a newer version already released from Carlink?
 
P

pir8man

Senior Member
Nov 25, 2007
320
87
Samsung Galaxy S21
Samsung Galaxy S22
  • Like
Reactions: DexterMorganNL
D

DexterMorganNL

Senior Member
Dec 1, 2010
1,066
173
pir8man said:

190000000_com.syu.carlink_test.apk

drive.google.com drive.google.com
make sure you have updated system apk for the app apk to talk to.
Click to expand...
Click to collapse
Thanks, but the version I have installed is newer: this is still Carlink 2.21 and I have 2.22 installed.

It was shared on 7 October 2022 in this thread. But I'm guessing my issue is related to Xiaomi, because my backup phone which runs Pixel Experience worked fine with Android Auto.
 
P

pir8man

Senior Member
Nov 25, 2007
320
87
Samsung Galaxy S21
Samsung Galaxy S22
DexterMorganNL said:
Thanks, but the version I have installed is newer: this is still Carlink 2.21 and I have 2.22 installed.

It was shared on 7 October 2022 in this thread. But I'm guessing my issue is related to Xiaomi, because my backup phone which runs Pixel Experience worked fine with Android Auto.
Click to expand...
Click to collapse
Yep, thats the latest. i did some app work today. when I finished I updated carlink from 2.21 to 2.22.
might also be the new phone. and update there might fix it also.
check signal strength
 
Last edited:
  • Like
Reactions: DexterMorganNL
Y

yokala

Member
Oct 6, 2016
49
11
Google Pixel 5
I just found out that FYT HW Onekey had a recent update and it's a game changer, you an now run an Automate flow from your steering wheel buttons.

github.com

GitHub - hvdwolf/FytHWOneKey: App to modify the hardware buttons on FYT units (Sofia3GR/PX5/sc9853i/sc9863a/uis7862)

App to modify the hardware buttons on FYT units (Sofia3GR/PX5/sc9853i/sc9863a/uis7862) - GitHub - hvdwolf/FytHWOneKey: App to modify the hardware buttons on FYT units (Sofia3GR/PX5/sc9853i/sc9863a/...
github.com github.com

Just install LlamaLab automate from the play store (the app doesn't require accessibility services or root, just normal permissions) and create flows to do whatever you want.

play.google.com

Automate - Apps on Google Play

Automate almost any task on your device
play.google.com play.google.com

For example, I made a flow to toggle split screen, another to launche 2 apps in split screen, and yet few others just to run an app.
For those interested, to enable split screen with Automate, you need to create an 'interact' block, and fill these settings :
action : 'toggle splitscreen (Android 7-12)',
package : 'com.android.systemui'.
 
  • Like
Reactions: marchnz
M

matsonjb

Member
Jan 29, 2009
15
1
pir8man said:
run FYTbackup on your oem setup... read ro.build.fytmanufacturer from the files cretaed on usb stick
edit allappupdate.bin to match in new firmware package..
Click to expand...
Click to collapse
Thank you for the assist. Also thank you @surfer63 for this thread.

Since I am not a CS major or anywhere near it besides rebooting the router; I installed HWinfo and got this

[ro.build.date]: [2022-09-26 09:52:21 Monday]
[ro.build.date.utc]: [1664156992]
[ro.build.description]: [ums512_1h10_Natv-user 10 QP1A.190711.020 39109 release-keys]
[ro.build.display.id]: [QP1A.190711.020 release-keys]
[ro.build.fingerprint]: [SPRD/ums512_1h10_Natv/ums512_1h10:10/QP1A.190711.020/39109:user/release-keys]
[ro.build.flavor]: [ums512_1h10_Natv-user]
[ro.build.fytfontsize]: []
[ro.build.fytid]: [FYGrp01]
[ro.build.fytinputmethod]: [com.google.android.inputmethod.pinyin/.PinyinIME]
[ro.build.fytisbootopen]: [1]
[ro.build.fytlivewallpaper]: []
[ro.build.fytmanufacturer]: [1]


Biggest thing is that last line. I tried to use the FYT MC to backup the apks as there are a lot of specifics for my GT-R screen.

My goal is to clean up the installed firmware and app package and make it more stable. I know OP mentioned no BT devices, but I'm looking to enable that as I also have a CANBUS device to work with.

Definitely learning a lot as I read the threads and enjoy an adult beverage.
 
Last edited:
You must log in or register to reply here.

Similar threads

G
General ROLL-UP -Joying 2GB - Sofia ( Non MTCB/MTCD )- Tips, tricks and mods
Replies
2K
Views
261K
surfer63
surfer63
kramttocs
Atoto S8 General Discussion
Replies
1K
Views
232K
Tam4511
Tam4511
T
General New Joying Android 10 UIS7862 Octacore 1.8GHz (4GB RAM, 64GB flash)
Replies
927
Views
199K
T
teeter477
K
Software Development [Dev] New "NavRadio+" ported to UIS7862 and sc9853i FYT devices.
Replies
831
Views
76K
K
KoTiX2
surfer63
General Modding your Joying/FYT SC9853i unit without root
Replies
792
Views
109K
T
tarsonis666

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 3
    surfer63
    surfer63
    DexterMorganNL said:
    As far as I understood, in order for it to work you need to put it on a usb stick. I tried it, by replacing the radio app in another modified radio app which had a zip file available to patch the radio. However the lsec6315update file is outdated, so that didn't work. I also already looked into this APK, and though of adding radio logo's for the Netherlands. But once again, I have no knowledge of that.

    I only think this modded version looks so much better, than how the stock radio looks and unlike Navradio: these really replace the stock radio, so the launchers don't get crippled.

    It has some logos of German Radio stations already included, but not all of them: I unpacked the APK, to see the logos.
    Click to expand...
    Click to collapse
    You are in the Netherlands. That means every 10~20 kilometer another frequency for the same radio station on a radio app that does not support Alternate Frequency.
    I did it once for my favorite 5 radio stations for a 50 km circle.
    It was a terrible amount of work for a ****ty radio app without Alternate Frequency working, so I still had to switch every x kilometer to another button for the same station. I had the 18 preselected for only a few radio stations for the several regions.
    So I switched to DAB: stations are automatically found (service following as it is called on dAB), automatic download of logoś and other images (currently playing song) and other info.

    Please forget this radio app or its mods. It will always stay frustrating untill those Chinese programmers get AF correctly programmed (They do not know the concept of Alternate Frequency, as it is not used in China)
    View
    2
    surfer63
    surfer63
    You put multiple different questions in one topic. Please sum tem up instead of making one long story.

    You can't use the hotspot and Android Auto at the same time.
    When wanting to use Android Auto:
    • You first need to connect via Bluetooth
    • Then connect via USB and follow the instruction to couple Android Auto and select wireless
    • Then disconnect USB
    • Next time it will connect via wireless.
    Did you do these steps?

    Troubleshooting:
    • Rebooting your phone/unit
    • Turning off Bluetooth and turn it back on
    • Toggling Airplane mode for a few seconds
    • Forgetting your car’s Bluetooth pairing and re-pairing your phone

    Forget the hotspot. You cannot use use Android Auto and the hotspot at the same time (to support the 20 friends in your car that drive with you?)

    You can download an 8581a firmware from Mekede (M100/M150 or M3 pro, if already available) and extract the kernel from it.
    Joying does not sell 8581a, only 7862 units.
    View
    2
    D
    DexterMorganNL
    I got Android Auto working again
    surfer63 said:
    You put multiple different questions in one topic. Please sum tem up instead of making one long story.

    You can't use the hotspot and Android Auto at the same time.
    When wanting to use Android Auto:
    • You first need to connect via Bluetooth
    • Then connect via USB and follow the
    Click to expand...
    Click to collapse
    When connecting wired, you better first disable the wireless Android Auto by going into developer settings. They ( Google ) removed it from the main settings menu of AA, and hid it.

    The reason you should do this: is because when the unit supports wireless AA, it will conflict with the USB cable. It might still attempt a wireless connection, even though connecting the USB.

    But you should be able to setup Android Auto wireless as: just the thing is, sometimes there are issues with wireless. That's why it's recommendable, to do the setup of Android Auto with a wire.

    I'm not 100% sure if you could still setup a WiFi hotspot on the 2,4Ghz band? Because I'm capable to setup a WiFi hotspot, while still being connected to WiFi on my phone. However your headunit can't be connected to WiFi, while using Android Auto wireless.

    I have the experience that using a WiFi hotspot and Android Auto on your phone, would increase the change of Android Auto crashing. In the beginning when I had this headunit, I did both use Android Auto wireless and my hotspot was on. It might be possible? But I can't recommend it.

    I'm sorry if I've explained myself wrong, I'm Spanish and my English isn't very good... First of all, thank you very much for answering me. I don't want to use the hotspot, it's a configuration created by the Car Link 2.0 app and I think it's causing a bug with bluetooth (I think). I want to connect an iPhone via wireless and the bluetooth of the radio disappears and it is impossible to link any device. If I manually turn off the hotspot created by the Car Link app and force close the Bluetooth service in settings, then the radio's bluetooth seems to be re-established and the iPhone can connect with CarPlay.
    Click to expand...
    Click to collapse
    CarLink creates this hotspot, for your Android Auto connection: perhaps you should take a look in the settings of CarLink?

    I however have never had the issue, that Carlink disconnects the Bluetooth connection while using Android Auto. But I have no experience with iPhones and CarPlay.
    View
    2
    surfer63
    surfer63
    dishe2 said:
    Thanks! I saw that but I still don't understand where to find it. I don't see a png called anything like that anywhere in the firmware or on my headunit in the file manager currently. In fact, the only png files I'm finding are wallpapers.
    Click to expand...
    Click to collapse
    It is not a set of pngs on the system. They are inside the com.syu.us.apk as resources. Unzip the apk, alter the pngs and then rezip the apk.
    View
    2
    surfer63
    surfer63
    dishe2 said:
    Ahhhh, ok. I see there's a whole complex process to unpack and repack the bins on the first page here. I am pretty sure I saw an png floating around on its own once before, I don't understand how I saw that if this is the case. I definitely never did all that before.

    I'm wondering, is it possible to just take that png off an installed system and then update it without flashing? Perhaps using ADB on an connected laptop? I feel like this might require a lot of trial and error to get the lines right and all this packing/unpacking seems like too much hassle.
    Click to expand...
    Click to collapse
    You don't need to unpack the bin. Simply copy the apk of your system with something like TotalCommander or so.
    Then unzip it, indeed change all the pngs, and rezip it.
    First try to simply install it as an update from SD-card. If that doesn't work, copy it onto your system using an lsec script.
    There is no "one single" png floating around.
    It is indeed a lot of work.
    View
  • 35
    surfer63
    surfer63
    Last revised: 11 January 2023.

    This thread is supposed to become a "one fits all" thread about FYT based Spreadtrum uis7862 (Unisoc ums512) head units and its software, modded or not. The first few posts will be "collection" posts for all kind of info but will also link to other useful information that might be added later or in other threads.
    Part of the tips, mods, etcetera are also valid for FYT based sc9853i and sc9863a (uis8581) head units, and even for the older PX5 and Sofia-3GR.

    DISCLAIMER: Every action you do on your unit is on your own responsibility. I will help where I can (and probably a lot of other users as well), but I am never responsible.


    This thread is meant for:
    • Discussing firmwares (see post #2), modded firmwares, mods and rooting (not advised).
    • Tips, tricks, mods to improve the general usability of your unit.
    • Try to solve design errors/flaws where we expect that these Chinese resellers/suppliers will not do it.
    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.
    Always first check the offical websites (if any) of the resellers in case of technical questions. Also: First contact your reseller in case of hardware issues or (not working) accessories.

    General unit information

    CPU: uis7862 (ums512). Specs/Benchmarks/Info. (Also allows you to compare with other CPUs).
    Android version: Android 10 (API/SDK 29); Fake Android 11 (still API/SDK 29). (Android level is a simple property. Always check at the API/SDK version)
    Producer: FYT
    WiFi: 2.4GHz and 5GHz. This 5GHz is really a benefit. Not only because of its faster 5GHz speed, but also because the 2.4GHz and BT negatively influcence each other dropping perfomance sometimes to 10% of "real" 2.4GHz. (Valid for all models without 5GHz, FYT or not).
    Bluetooth: V5.1
    Resellers: Atoto, Ebilaen, Eki, Farcar, Funrover, Idoing, Isudar, Joying, Junsun, Mekede, NaviFly, Sinosmart, T'eyes, Winca, Zhan. There are more resellers, but not all of their models might be FYTs. Same for some resellers in this list.


    Q&A - Questions & Answers

    Q1: I already see uis7862 units having Android 11 and even Android 12, what about it?
    These Android 11 versions are fake! The Android version is still Android 10 (API/SDK 29), but the Android version as displayed is a simple property which you can set to Android 11 (or 12 or 31 or 227). The API/SDK versions determines the real Android version. Don't believe statements like "we updated ...". Always look at the API/SDK version. If it says API/SDK 29 it is is Android 10. Real Android 11 is API/SDK 30.

    Q2: What are the several passwords on these uis7862 FYT units?
    • Factory menu / Developer options: 3368
    • Backlight Current Adjustment: 5768
    • Door lock interference: 0000
    • To change home launcher: 8086
    • Developer password: 7788, or tap 7 times on "About".

    Q3: Are all these (uis7862) units compatible? Is all (uis7862) firmware compatible?
    The uis7862 units based on FYT are all hardware compatible. Differences in audio chip, radio chip with or without RDS, DSP chip (DSP 14-band (low end) or DSP 32-band or not at all) are supported by the software. There are minor differences in MCU and firmware, which need to be taken into account when flashing firmwares,and sometimes also for flashing mods. This is all based on the so called reseller id.

    Q4: How compatible are FYT units over the years (uis7862 (ums512) vs uis8581a (sc9863) vs sc9853i vs sc7731 (uis8141e) vs PX5 vs Sofia3GR)?
    When it comes to firmware you really have to look at the CPU and reseller id (see below). Part of the "user apks" are quite exchangeable. When it comes to settings, behaviour, tips & tricks, etcetera, these units are mostly compatible over the entire range through the years and almost all settings are the same when it comes to (uis7862(ums512), sc9863a(ums8581a), sc9853i, px5, sofia3gr). So please take a look at Q&A, tips, info Roll-up (Joying) FYT SC9853i before asking questions.

    Q5: What is an MCU? What does it do?
    MCU stands for MicroController Unit (in this case). The MCU is a "CPU" itself with embedded (flashable) firmware that functions as interface and "translation" layer between the Android software and the hardware layer (Radio chip, Amp chip, DSP chips, etcetera).
    The MCU has some I/O lines to the hardware of the unit. A number of digital IN lines (ACC, headlights, reverse, parking brake) and digital OUT (antenna power, amplifier power) and a few analog IN lines (steering wheel 1 and 2). This overview is not complete.
    So actually your unit comes with the Android firmware (Android itself and the additional FYT unit programs) and with the MCU firmware. That MCU firmware is not always packaged with new firmware updates. Note that all these Chinese units use this MCU firmware instead of using Google Androids Automotive System.

    Q6: Can I flash firmware from another FYT uis7862 supplier to my FYT uis7862 unit?
    NOT directly, but with some tweaks: Yes. Read post #2 carefully and especially section VIII.

    Q7: Can I flash the MCU firmware from another FYT uis7862 to my uis78962 unit?
    NO. I repeat: No. If you really, really, really, really know what your doing then to some extend: Yes. Otherwise: Don't even think about it.

    Q8: How do I unpack/repack this AllAppUpdate.bin?
    See post #2 section II. (AllAppUpdate.bin).

    Q9: What is an AHD camera?
    AHD stands for "Analog High Definition". It has nothing to do with your screen resolution itself, but it is for your camera (1280x720 and 1920x1080). It requires it's own micro-processor for decoding in the unit. AHD cameras are therefore only supported on units that specifically mention this. You can however connect a "low res" DVR camera (720x576 or 720x480) to an AHD unit.

    Q10: Can I mod my unit? Are there custom firmwares available?
    Yes, you can mod your unit to some extent. See the posts about the AllAppUpdate.bin and 7862lsec scripts. There are no custom firmwares available. There are modded firmwares available. These contain some tweaks, minor layout changes and sometimes solve bugs, but are actually still the exact same firmware.

    Q11: Can I root my unit?
    Yes, you can. There are at least 3 possible ways to do this, but I don't recommend rooting. Not because rooting is tricky, or making your unit unstable, but rooting brings nothing. It only makes your unit less safe as malware, etcetera have a much better chance to attack than on a non-rooted unit. You can mod some things easily yourself without (!) root. When rooting Google voice feedback is crippled as media channel 4 is somehow "blocked". Viper audio doesn't work properly and brings nothing extra on these DSP units. Anyway: Google for yourself if you still want to root your unit as it is possible if your really want it.

    Q12: How do I disable the internal microphone when using an external microphone?
    See this post. Note that there is a difference for units after approximately August 2022 (Pro models) and units before that time.

    Q13: I flashed a firmware from another unit and now I have a big yellow bar with red text "ui and mcu does not match". What can I do?
    To start with: I know it should be "ui and mcu do not match", but that "does" is CHenglish. The reason for this is that the ro.build.fytmanufacturer is different for the several resellers and you used an AllAppUpdate.bin from another reseller. You now have several options here:
    1. You still have the original firmware and can extract the ro.build.fytmanufacturer from it (or you know it from the top of your head).
    2. You have no clue about this ro.build.fytmanufacturer and you don't have the original firmware anymore.
    In case of (1), you could:
    • use the script Change Fytmanufacturer (bullet #3) that directly updates this ro.build.fytmanufacturer inside the fyt.prop on your unit.
    • open the AllAppUpdate.bin (next post, topic II) and change the ro.build.fytmanufacturer and repack it again and flash that AllAppUpdate.bin
    • Or simply flash the oroginal firmware, get the ro.build.fytmanufacturer and start all over again.
    In case of (2) you have to flash the entire original firmware again ór use the script (link added later) to update the fyt.prop directly and try a number of ids until you have the correct one (There are not so many).

    Q14: I want to replace my boot animation and/or boot logo. How do I do that?
    Copy the lsec6315update binary and your bootanimation.zip and/or your LOGO.bmp onto a clean USB-stick and connect it to your unit. It will only flash your bootanimation and your boot logo.

    Q15: When my unit (cold) boots, the radio is always started. Can I prevent this from happening?
    You can't stop this. Not on a Joying and not on any other unit. And note that the radio app is actually only an interface that forwards commands to and receives data from the radio chip via the MCU. It is not an active app like your mediaplayer that does everything in Android.
    When the unit boots, the hardware is up and running long before Android is. That means that the radio chip and amplifier are already working before Android has even booted. That is why you hear the radio. And that is why every manufacturer starts the radio app on boot: to enable you to mute the radio channel from the app.
    The radio is never switched off as it cannot be switched off. It is only muted.

    Q16: Do I have a FYT unit or not?
    Use my HWGet_Info.apk. It will immediately show a lot of FYT properties (if it is a FYT) and give a zip with a lot more info as well.

    Q17: If I want to create my own scripts then which binary do I need and which script should I create?
    BinaryUnitScript
    lsec6315updateuis7862 (ums512)7862lsec.sh
    lsec6316updatesc9863a (uis8581a)8581lsec.sh
    lsec6521updatesc9853ilsec.sh
    lsec6523updatesc7731 (uis8141e)lsec.sh

    You can make "Universal scripts" by simply using all binaries and create/duplicate all scripts and copy them onto one USB-stick (or inside a dowloadable zip). The unit will automatically select the correct binary and accompanying script.
    The binaries and scripts are "incompatible" on other units.

    Q18: My GPS reception is bad. What can I do?
    • If your car already had GPS, buy a "Fakra C Adapter Plug to SMA Male GPS" adapter (example) and use your cars GPS antenna (mostly on the top of the roof). 99% sure it is better than those cheapest possible GPS antennas you get with these units.
    • Buy a better GPS antenna. On Aliexpress you can buy a 32 dB or 38 dB antenna from 6-26 euros that are much better. Secondly: the standard GPS antennas come with long cables that loose signal.
    • The standard antenna: First check whether your SMA connector is firmly connected. Mostly it requires a little more force to fix than your fingers will yield.
    • The standard antenna: Check for a broken cable. Is it nicely curved or does it somewhere has a sharp bend.
    • Do not put it under large metal plates or metal reinforcement beams under your dashboard. Mostly it functions just fine below your dashboard, but not if you put it directly under a big metal beam/bar.
    • Place the antenna itself horizontally to give it the best "view".
    Q19: All my apps are killed when my unit goes into deep sleep. Can I prevent this? Or: How can I always start the XYZ apk when I start my car?
    • First of all read bullet #8 from my other "info" thread, but do NOT use solution 2, made for a sc9853i, for your uis7862.
    • In the Settings apk, go to "User" -> "Application Settings". In that menu you can autostart applications on cold boot or coming from (deep) sleep mode.
    • Use FYTstarter from @bambapin.

    Q20: I use Total Commander, FileXplorer or any other advanced file manager but can't write to my external USB-stick or SD-card. Why?
    You do need the documentsui.apk for it (deprecated as of Android 12). For whatever reason FYT doesn't compile it into their firmware. This DocumentsUI for Android 10 will help you. Install it, open it once and afterwards your filemanager will use it once to request access to (the root of) the USB-stick. When using another USB-stick (having another internal ID), you will have to give access to that USB stick as well. Same when you have formatted your USB-stick.

    Q21: I have a unit without active cooling (a fan) but still would like to cool my unit as it gets really hot and starts to throttle down giving terrible performance (and reduced life span). How can I add a cooling fan?
    You can buy a 12V PC-fan. Select a slowly spinning, ball bearing fan to make it as silent as possible. Connect it to the 12V AMP wires. From the Settings -> Sound, you can enable/disable the AMP. In this case that will start or stop the fan.

    Q22: I use a non-FYT Launcher (Nova, WebGuru, Agama, etcetera), but recently it always switches back to a FYT launcher or another after sleep / reboot / other actions.
    Go to: Settings - Device - Applications: Disable the Digital Wellbeing App

    Q23: I need a SIM/Carrier to work with my FYT unit and my provider
    • make a text file named "IMEI0" (no extension)
    • edit it to put in two IMEI values that are valid and compatible with your provider. (one for each SIM slot)
    • copy to USB stick and plug it into your unit
    • Your unit will (should) show a notification "imei changed".
    After reboot your unit should have the new IMEI in the settings. (thanks to @j-5)

    Q24: How do I enable splitscreen on these units?
    See post #1394 for an explanation with screenshots.
    ==================================================
    (End of Q&A - Questions & Answers)


    FYT Settings explained

    Thanks to @hanichl for first write-up.
    Thanks to @mastrv for corrections and further additions.
    Thanks to @leo06 for corrections on GPS mix Setting/explanation.
    Thanks to @daviddosa for further additions.

    Note these are FYT Settings, which means it doesn't matter whether you have a Mekede, Joying, T'eyes or any other FYT unit. Note also that many settings are the same whether you are on a FYT uis7862, uis8514a, sc9853i, PX5 or Sofia 3GR, althought the number of settings have increased in newer models.
    T'eyes also has a site with instruction videos, which are still 90% up-to-date. See here.

    SETTINGS​

    WLAN​

    • Wlan (same as stock Android)
    • Data Usage (same as stock Android)
    • SIM Info (same as stock Android)
    • More (same as stock Android under Advanced Networking)
      • Mobile Network
      • Hotspot & Tethering
      • Airplane Mode
      • VPN

    DEVICE​

    - Display
    • Brightness Level ( brightness for day and night mode )
    • Wallpaper ( change wallpaper )
    • Auto Blackscreen ( black the screen after xx seconds/minutes )
    • Displayed NET Switch ( shows the connection speed in upper taskbar )

    - Sound​

    • Keypad Tone ( On/Off: emits tone when pressing a key )
    • LOUDNESS ( Not entirely clear, but most proabably the same Loudness setting as on a HiFi installation before DSP was introduced, or for units without DSP )
    • AMP ON/OFF ( switching amplifier mode ). Note: In case your unit has a cooling fan installed, the setting AMP ON/OFF is also there to switch the fan On or Off on older units (brand units: before approximately July 2022; for brandless units you never know)
    • Power Conditioning ( absolute output volume from 0 to 60, all other audio settings are relative; if you think your audio is already too loud at position 5 (or so), you can decrease the absolute volume output here which means that Volume 5 is now lower )
    • Subwoofer ( set subwoofer volumes )
    • Equalizer ( set sound frequencies with equalizer )
    • Speed Compensated Volume ( set sound volume depending on the actual speed )

    - GPS​

    ( set / shows GPS modes GPS / GLONASS; mode 1 -> GPS only; mode 2: GPS + GLONASS )​

    - Apps​

    ( show / remove installed apps; same as stock Android )​

    - USB Video Output Setting​

    ( Some resellers sell external USB-connected DVD-players. This settings allows you to correct over/under scanning )​

    - USB Device Start​

    ( None / Carlink - application to start when USB device is connected )​

    GENERAL​

    • Press any key to start ( When you long-press the "Off" button on the top-left button array of your unit, your screen will switch off (but your unit does not go into deep-sleep). When you set this setting to ON, your unit will switch on again when pressing any button of your unit)
    • Brake wire for video in motion (Incorrect Chinese translation: (Dis)Allow display of video during driving )
    • Auto-start Navigation ( auto start navigation > needs Navi app to be set accordingly )
    • OSD Time ( on / off in notification bar)
    • Mirror view on reverse image ( if backup reverse cam is installed, and the video is 180 degree turned, this will switch to normal mode )
    • Mute audio when reversing ( decrease sound level if rear gear is processed, not completely mute )
    • Sound reduction when reversing ( reduces the sound when car is in reverse gear (driving backwards). Only works when previous Setting switched to ON )
    • Backlight control ( switches the leds behind the (soft-)buttons On/Off : or by switching on/off headlights, or based on time )
    • Default volume switch ( When your unit starts, do you always want to have the same default volume to start with )
    • Default boot volume ( sound volume which is preset on boot process; only works if previous setting switched to ON )
    • GPS Mix ( ON = Will reduce/mute media/radio when "speaking" navigation instruction; OFF = media will not be reduced/muted when navigation app issues instruction ). Some other translations than English mention this as "audio mix between navigation and media". Note also that most modern navigation apps have a setting themselves to mute or even shortly pause the media player when issueing a navigation instruction.
    • Sound mixing scale ( Set volume of background audio when "navigation speaks" (for example: Volume currently 10 so navigation uses 10, background music uses volume set here ). Only works if "GPS mix" setting (one above) is set to ON.
    • Lantern settings ( set the colour palette for the hardware buttons LED )
    • Steering wheel setting ( Configure the steering wheel buttons; only for non-Canbus systems. Canbus systems are hard-coded )
    • Navi app ( app to start when NAVI Button is pressed AND to auto-start navigation ... see 3rd point ..
    • Map Data Copy ( Old setting for iGo to copy maps from internal memory to SD-card, so that it doesn't get deleted on a new firmware install )

    FACTORY​

    (requires password/pincode 3368)
    • Touch check
    • Original Car Agreement ( These settings are mostly controlled by the CANbus. The number of options can vary per CANbus type and can also work or not work per CANbus type. The number of options will be very limited without a CANbus. )
      • External Temperature ( shows external temperature in notification bar when CANbus is present)
      • Automatic start and stop ( ?? )
      • Radar Display ON/OFF ( Incorrect Chinese translation: Enables/disables the "beep" sound when too close to an object, so no display but sound )
      • Reverse Parking Line ( In case of a reverse camera show the parking lines )
      • Static Track ( Shows static reverse parking lines in case you don't want or have the "curving" parking lines )
      • Reversing track reversal ( If your reverse camera's left/right postion is reversed )
      • Max Reversing Angle
      • Door ON/OFF ( shows if a door is open )
      • Drivers Door position ( left / right drivers position )
      • Rear Door Exchange ( Similar to Drivers door position, but for back doors )
      • A/C Information ON/OFF ( Shows changes if you change AirConditioning temperature/ blower speed/ etcetera )
      • Car Audio Type ( AUX / IPOD-TV )
      • Reversal Previous And Next ( This reverses your CANbus steering wheel next/previous behavior (Spotyfy is known for this) )
      • Reversal Volume ( Reverses the Volume +/Volume - in case your CANbus steering wheel volume keys/arrows work the other way round )
      • Protocol Print ( When on, this displays the CANBUS messages overlayed on the screen )
      • Temperature unit switch ( Celsius/ Fahrenheit )
      • CAN box upgrade (updates software in CANbus decoder; Be careful: this can soft-brick your decoder)
    • Car Model ( define the canbox manufacturer, params )
    • Back MIC switch -> When set to "On" the internal microphone is switched on, but only new M6 pro hardware. When set to "Off" the internal microphone is switched off. Use this "Off" setting when you have an external microphone connected. Do not use both microphones at the same time as it will only give you worse microphone performance. If you have an old(er) firmware and not the new M6 pro, you need to use this trick as described by Vitaly (@gordgelin ).
    • Antenna normally on ( In case you have an electrically retracting / extending antenna. This will extend the Antenna when ACC switched on . OR some cars need constant 12V on the Antenna )
    • HD reversing video format (Try this in case you have an AHD camera on a non AHD unit, or the other way round).
    • Boot Screen logo
    • Set Screen
    • Touch Screen Calibration
    • Panel Key Learning
    • Front View
    • Cancel the reverse into the front view (If you have back and front camera, it will switch to front camera when "leaving" the reverse gear)
    • MCU Panel Key (Set buttons like Band/Radio, Phone, Music) on the side of the screen to On/Off.
    • Unknown sources ( allow apps to be installed from unknown sources )
    • Door lock interference
    • Reverse power supply (Be careful !: Switch functionality of Cont and ACC inside radio)
    • Volume balance settings
    • MCU upgrade (Only upgrade the MCU firmware; Be very carefull to ONLY use the firmware for your type of unit)
    • Backlight current adjustment (Set display brightness but be carefull. It can blacken your screen entirely. There is no safe low position. passwd: 5768)
    • Home Launcher Selection (Option to chose one of installed FTY launchers. passwd: 8086)
    • USB Error detection
    • USB protocol selection
    • A key to export ( exports Settings to /mnt/sdcard/SettingsConfig as json file, but how to import this )
    • Single 360
    • Activation
    • DVD Update
    • TV Type
    • Video Output Settings
    • OBD
    • Sleep mode Setting (Switch off head unit or switch to deep sleep, when ACC is turned off)
    • 360 switch
    • Backup Test
    • Plug In Serial Device Setting

    USER​

    • Location (same as stock Android)
    • Security (same as stock Android)
    • Language And Input (same as stock Android)
    • Google Settings (same as stock Android)
    • Backup And Reset (same as stock Android)
    • Account (same as stock Android)
    • Delay Power Off When ACC Off (After ACC of the delay time to put unit in sleep or off: OFF / 3 sec / 10 sec / 3 min)
    • Application Setting ( which applications you want to auto-start when you start your car and unit )

    SYSTEM​

    • Date And Time
    • Accessibility
    • Developer Options
    • About Device
    • Device Info
    ==================================================
    (End of FYT Settings explained)



    Mods, useful software, tweaks for your system, etcetera.
    Some will be added later

    • Backup the firmware of your unit (see post #4). Useful if you do not have a firmware yet for your unit.
    • Disable or (re-)enable the mediaplayer at startup/wakeup (bullet #2).
    • Change Fytmanufacturer script to correct the fytmanufacturer id after a flash with another resellers AllAppUpdate.bin bullet #3).
    • DocumentsUI for Android 10. Without it you can't write to an external USB drive with other file managers. That is because the documentsUI is missing. Install it, open it once and afterwards your file managers can use it to get access.
    • Android Shortcut Settings: This program by Mario Dantas gives you access to some hidden settings in the (FYT) head units.
    • Mario Dantas (@mariodantas ) created/build the website "uis7862 FYT Factory":
      • A great and very extensive collection of launchers for FYT models and also a collection of (un)rooted kernels for your unit. (Read post #2 section III "The 6315_1.zip" for more info on kernels and how universal they are.)
      • He now also created a new firmware (MD-edition) that after flashing gives you some very handy and essentials options for on-the-fly rooting and root access for selected apps, starting apps from boot, make firmware backups, save your /data/data partition, etc.
    • @seb21 made a modded combination of the com_syu_ms.apk and a Config.apk. This combi allows you to change the "hard-coded" steering wheel buttons in case you have/use a CANbus and add "no kill" functionality. See Modded syu.ms.apk.
    • getinfo script. This is in fact an extension of my HWGetInfo.apk, but as an lsec script. It gives more info than the HWGetInfo.apk as it runs as a flashable script thereby having full access to the system.
    View
    27
    surfer63
    surfer63
    Last revised: 03 February 2023.

    More about Firmware(s)​

    This post is valid for FYT uis7862 (ums512) units running Android 10 or fake Android 11.

    Contents of a firmware zip:
    • 6315_1.zip: The zip file contains all "standard" Android software, drivers and apks. It also contains the the boot.img; the system/vendor/oem partitions and a few other things. This 6315_1.zip "should" be interchangeable between all 800x480, 1024x600 and 1280x720 models. I don't know for the special resolutions, Tesla like units or rotable units. Probably they are by now also compatible.
    • AllAppUpdate.bin: Special file that contains all FYT apps (This can be (un)packed with any (un)zipper, but I prefer 7-zip). This file also contains special files with reseller specific configs. This one is only interchangeable between the same reseller-id, unless you change that reseller-id.
    • config.txt: file comparible to the build.prop which can contain additional properties.
    • lsec6315update: The binary that really does the update
    • oem: (OPTIONAL, DEPRECATED) Folder containing some additional apps. These are not automatically installed, but can be found in folder OEM in your internal memory (internal SC card called USB). Do not confuse this with the oem partition where the AllAppUpdate.bin will be installed to. I use this folder upon flashing to add some of my preferred apps that I want to have available, but not directly installed. Note: Nowadays the preferred location for these kind of apps is in the vital-app folder inside the AllAppUpdate.bin.
    • updatecfg.txt: Contains instructions for the flashing process
    • Stm32ud.bin: (OPTIONAL) binary to flash the MCU
    • GD32_E230_64K_Flash.Hex: (OPTIONAL) the hex file that contains the MCU firmware itself.

    I. (Factory) Firmwares

    (Please share official (!) download links for other resellers so I can add them here).

    * Modded Firmwares:

    See for compatibilty between firmwares the below header "Compatibility between firmwares".
    ==================================================================================



    Some commands that can be put inside updatecfg.txt
    Code: 
    twipe_all     # Wipe entire system
twipe_data    # Will wipe data partition (but not /sdcard, internal memory). Wiping the /data partition will wipe all config, all 3rd party apps and updates of system apps. This is the same as a "reset to factory defaults"
twipe_cache   # Will wipe the cache of the apps thereby removing the temporary files that are stored for those programs.
twipe_sd      # Will wipe internal memory /sdcard (but not the data partition)
dellapp       # Remove all 3rd party apps
make_updates  # Make an upgrade U-disk boot file
test          # test unit and firmware before flash

    Some properties that can be put inside config.txt. Say you live in Brazil and you want your locale settings immediately on Brazil, you can add that. As a second example we take a "Tesla style" unit which is actually a rotated horizontal unit:
    Code: 
    ro.product.locale = pt_BR
ro.sf.swrotation = 90
    Or you want to improve the microphone function a little, you can add or modify the following lines:
    Code: 
    persist.sys.zlink.mic.vol=9.9
persist.audio.mic.senstivity=1
persist.btmic.gain=10
persist.btspk.gain=7
    If you decide to download a 4pda Russian modded firmware, make sure you remove the settings from this config.txt file that makes this a Russian firmware (unless you are Russian, but in that case you probably would not be here).

    II. AllAppUpdate.bin

    The AllAppUpdate.bin is actually a password protected zip archive. You can use any zip, but preferably 7-zip for your platform (Linux, MacOS, windows) to create, modify or extract it.

    Specifications: zip format, non-compressed (store), password 048a02243bb74474b25233bda3cd02f8
    Unzip is simple: you only need to specifiy the password.
    When (re)creating a new AllAppUpdate.bin, make sure you follow the specifications.

    Inside this AllAppUpdate.bin you will find all FYT based apks and libraries and next to that also two other files: fyt.prop and skipkillapp.prop.
    • The fyt.prop is identical to the build.prop but gives the option to add extra properties or replace/modify properties in the build.prop. And the fyt.prop contains the ro.build.fytmanufacturer=<xy> and the ro.fyt.uiid=<z>. This is in 90% the only distinction between the several firmwares.
    • The skipkillapp.prop contains apps (package names) with values from -15 to 15.
      When going into "deep sleep" the packages not mentioned in this list will be killed. Applications in this list with positive values will absolutely be killed (unstable otherwise??). The ones with higher values first. The ones with values 1 and 0 as last, where the app with value 0 will be the last killed before going into deep sleep.
      The apps with negative values are considered system apps and will not be killed. In this case the most negative number (-15) has the highest priority. My assumption (not tested, not verified) is that negative numbers approaching 0 might be killed if the system needs the memory?
      So in other words: If you do not want that some of your apps are killed, you can add them to this "skipkillapp.prop" by their package name. Say you use @realzoulou's DAB-Z app, you would add a line for DAB-Z (com.zoulou.dab). Or for example if you are a Tasker user, which is normally killed as well:
      Code: 
      com.zoulou.dab = -10
net.dinglisch.android.taskerm = -10
      (I would suggest not using values like -15, -14, -13 to make sure you do not really interfere with the real system apps).
      And then you need to add this file (again) to your own AllAppUpdate.bin
    NOTE: In the previous version for the sc98531 you had the Allapp.pkg. You could put one or a few apks in there and it would simply only install/overwrite the apks inside that Allapp.pkg. The AllAppUpdate.bin will always completely erase the FYT apks on the oem partition. This means that you either need a full AllAppUpdate.bin with your (modded) FYT apk(s), or (advised) use the 7862lsec.sh script approach to only add/overwrite/remove one or a few FYT (modded) apk(s).

    NOTE 2: In the "main server" apk com.syu.ms, there is now inside assets/property an new file called unkill_app.txt. I "think" that file now contains the apps that should not be killed upon going into sleep mode. I still don't have my unit and I am actually not interested at all in "unkilling" apps, but it might be useful to test with this file.
    ==================================================================================


    III. The 6315_1.zip
    (Inside also "III-a. More details about the files inside the 6315_1.zip and how to decompress and unpack/"open" them" and "III-b. Recompress uncompressed images from the 6315_1.zip to squashfs format for small (!) and easy access. (Not for flashing.)")

    The 6315_1.zip contains the "standard" Android software for this unit. This is more or less what every "plain vanilla" Android 10 release will contain, without additional apks (Compare it with standard Android where Samsung adds a lot of Samsung apps). This is the "base" firmware as you download it from the Android website and compile it.
    Note: Mentioning that this is "standard" Android is actually wrong. FYT modified the USB and bluetooth stack. In effect: they crippled it to only allow the USB and BT devices that they consider "allowed".
    Note 2: They also added drivers to this "plain Vanilla" Android to support their hardware, mostly through the MCU.

    This 6315_1.zip is theoretically identical for all FYT uis7862 units and can therefore be used on all FYT uis7862 units. (DISCLAIMER: Experimenting with this falls under your own responsibility).
    You can unzip the 6315_1.zip and replace the boot.img or modify the install script in "META-INF/com/google/android/updater-script", and then rezip it.
    All the other files in the zip are system signed files, which means that you can further unpack them, but not modifiy and recreate as you will never get the signing certificates from FYT.
    Other files inside the zip are mostly used to create and install the necessary partitions where the system software and Android software is installed to.

    III-a. More details about the files inside the 6315_1.zip and how to decompress and unpack/"open" them

    You will find for example the system*, vendor* and other "pairs of three" files. Next to these files you will see a number of bin files including the u-boot files, which are the bootloaders. You can consider these u-boot files like the BIOS on older, or UEFI on newer pcs.

    As example we look at the system.new.dat.br, system.patch.dat and system.transfer.list files. This set actually contains the system partition. The system.new.dat.br is a brotli compressed image. The patch files can contain patches and is implemented after the system.dat (but on our firmwares always empty). The transfer.list contains the "blocks" on how the system partition should be created.

    Let's unpack such a set of files.
    First we need to "brotli decompress" the system.new.dat.br (note that this binary doesn't show output and takes quite long).
    Code: 
    brotli -vd system.new.dat.br -o system.new.dat
    Now we need sdat2img to convert our created system.new.dat "sparse data image"(1) into a "disk image file"(2) being system.img. Note that sdat2img is a python script, so we need python as well (standard on linux, unix and MacOs).
    Code: 
    sdat2img.py system.transfer.list system.new.dat system.img

    On linux/MacOS we can now easily "mount" this system.img image file and check the contents:
    Code: 
    mkdir system
sudo mount -o loop system.img system
ls -Rl system

    (1) sparse image: To make the images smaller, and to reduce transfer time, Android generates system.img, vendor.img and other img partitions in sparse format. The image is split into chunks of multiples of 4096 bytes. Any chunks that contain no useful data are marked as "Don't care" and no data is sent.
    (2) disk image file: A disk image (file) is a type of file that contains an exact copy of a certain disk or partition. On Android (and linux) these are mostly ext4 partitions/disks but can also be Fat32/squashfs (compressed, often used in older Androids)/DMG (MacOS, also for installers)/NTFS, etcetera.


    III-b. Recompress uncompressed images from the 6315_1.zip to squashfs format for small (!) and easy access. (Not for flashing.)

    So you have your brotli compressed system image (system.new.dat.br) of approximately 500MB, which you can't use at all in this state.
    And you have uncompressed it to a system.img of 1.3GB (see previous section), which you need to "mount loop" to view it contents.
    Can I do this differently?
    Yes, you can with squashfs (explained for linux and/or MacOS), for which you first have to install the squashfs tools.
    Mount your system.img like mentioned above and then create a squashfs image.
    Code: 
    sudo mount -o loop system.img system
sudo mksquashfs system system.img.sqsh
sudo umount system

    Now you have a squashfs compressed system image of about 550-600 MB instead on an uncompressed system.img of about 1.3GB.
    To examine its contents you mount it like
    Code: 
    sudo mount -o loop system.img.sqsh system

    ==================================================================================


    IV. Some info on partitions

    This info is referring to the partitions being created from within the 6315_1.zip.
    Starting with Android 10, Google introduced "dynamic partitions". Below a quote directly taken from the Dynamic partitions page.
    Dynamic partitions are a userspace partitioning system for Android. Using this partitioning system, you can create, resize, or destroy partitions during over-the-air (OTA) updates. With dynamic partitions, vendors no longer have to worry about the individual sizes of partitions such as system, vendor, and product. Instead, the device allocates a super partition, and sub-partitions can be sized dynamically within it. Individual partition images no longer have to leave empty space for future OTAs. Instead, the remaining free space in super is available for all dynamic partitions.
    Click to expand...
    Click to collapse
    Apart from the /oem partition and a few others, the /system, /vendor and /product partition are read-only. In earlier FYTs, you could use the lsec script to make them read-write and then modifiy content, add/remove files/apks, etcetera from these partitions. The big disadvantage for modders with these new dynamic partitions is that you can't make them read-write anymore.


    V. The lsec_updatesh folder, lsec6315update binary and 7862lsec.sh script (and what about "universal" scripts)

    The flashing process consists of a number of steps:
    1. flashing the core/kernel software (6315_1.zip)
    2. flashing the unit applicable apps and libraries plus initial properties (AllAppUpdate.bin)
    3. scripts that do "post flash" activities.
    The "flashing" executable/binary also starting the scripts, is the lsec6315update file on a uis7862.
    A USB-stick used to execute a script on a uis7862 should contain:
    Code: 
    lsec6315update
lsec_update/7862lsec.sh
"stuff that needs to be copied/moved/installed"
    Practical applications:
    • Making patches, an alternative to creating the AllAppUpdate.bin file by simply specifying an apk (or so) in your script.
    • Delete unnecessary files or applications (who uses the calculator app?), or overwite/change files like the fyt.prop, config.txt or others.
    • Set properties that normally require root/admin rights.
    • Create a nearly flashable backup using this script (to be added) by creating backups of your FYT apps and config files and immediately zip them to an AllAppUpdate.bin and add some more necessary files.
    • Creating backups of your partitions using the dd command. This can be handy on a device for which you do not have a firmware yet as backup.
    • Rooting your unit, also if you do not have a firmware from your supplier.
    • Make a "modded" ROM by simply doing all kind of modifications after the "normal" firmware flash using the 7862lsec.sh script.
    • Flash a new config.txt to your unit: Simply copy your modified config.txt and the lsec7862update binary onto a clean USB-stick.

    For more info on writing scripts, see below.
    ==================================================================================
    Creating your own lsec script to copy/replace a modified FYT apk.

    If you want to create your own script to flash a modified FYT apk to your unit to replace an existing FYT apk, you can use the following steps.
    Below is described for a uis7862 (ums512) and for a uis8581 (sc9863a). These units are compatible.
    On your USB-stick you need to have the following files.
    Code: 
    lsec6315update                       (binary)
lsec6316update                       (binary)
lsec_updatesh                        (folder)
        7862lsec.sh                  (shell script)
        8581lsec.sh                  (shell script)
OEM_APP                              (folder)
        190000000_to_be_replaced     (folder of the apk)
                190000000_to_be_replaced.apk  (some apk we want to replace)
    Inside folder "lsec_updatesh" you have to create two shell scripts (on Windows NOT with notepad, but a good ascii editor).
    The binary "lsec6315update" and shell script "7862lsec.sh" are for a uis7862.
    The binary "lsec6316update" and shell script "8581lsec.sh" are for a uis8581.
    (You can do the same for two other type of FYT units: the "lsec6521update" and "lsec.sh" for a sc9853i. And the "lsec6523update" and "lsec.sh" script for a 7731. Note that these two units are also compatible. I have created scripts (for other purposes) that contain 4 binaries and 3 scripts, as the lsec.sh script is the same for the sc9853i and the 7731).

    Note that for replacing FYT apks, the 7862lsec.sh script and the 8581lsec.sh script can be identical as they use the same firmware when it comes to AllAppUpdate.bin.
    Let's say we have an apk called 190000000_to_be_replaced.apk.
    The following is for ALL 7862 and 8581 FYT units, but not T'eyes units. Those T'eyes guys do it differently (and let you pay for a lot of things).
    On ALL the other non-T'eyes FYT units, the apks are installed in folder "/oem/app" inside their own folder "190000000_to_be_replaced". In that folder we then copy the "190000000_to_be_replaced.apk".
    We use the following template for our script.

    Code: 
    #!/system/bin/sh

#Remove the current app data/program cache/cache. This is only necessary for some applications, but it never harms
rm -rf /data/dalvik-cache/profiles/190000000_to_be_replaced
rm -rf /data/data/190000000_to_be_replaced
rm -rf /data/dalvik-cache/arm64/*190000000_to_be_replaced*
#
# Copying file to /oem/app
#
cp -r /storage/sdcard1/OEM_APP/* /oem/app/
#
# Updating folder/file access rights
#
chown -R 0.0 /oem/app/190000000_to_be_replaced
chmod 755 /oem/app/190000000_to_be_replaced
chmod 644 /oem/app/190000000_to_be_replaced/190000000_to_be_replaced.apk

    If your script needs to do other things you can take a look at some of the scripts in my github repository.


    See this post #228 for more info about the "The lsec_updatesh folder and lsec.sh script" as it was used on the SC9853i (and now again on the sc7731 (uis8141e).
    ==================================================================================


    VI. Compatibilty between uis7862 (ums512) Firmwares

    As mentioned under the relevant topics above:
    • The 6315_1.zip should be identical between all uis7862 units. Of course newer releases can contain updates, etcetera.
    • The AllAppUpdate.bin is application wise compatible between same aspect-ratio compatible screens like 800x480, 1024x600, 1280x720. The great separator here is the ro.build.fytmanufacturer property. If you flash an AllAppUpdate.bin from a Mekede firmware (with id=1 or id=116) to a Joying (with id=43 and lately also id=1) or vice versa, you might get a perfectly working unit, but a big yellow bar in the top of your screen mentioning that the MCU is incompatible. However, due to real differences in MCU firmware (which is in general not compatible), you might also encounter serious issues. Not because the software is incompatible, but because it behaves differently on another MCU.
    • The optional MCU firmware. This is definitely NOT compatible!

    So what can you do when seeing upgrades from other suppliers?
    1. You could take the 6315_1.zip if it "seems" to be (far) more up-to-date than your currently installed system (/system, /vendor, /product). You can copy it to a clean USB-stick and copy the lsec6315update binary onto the USB-stick and flash it to your unit. In case of doubt, always ask
    2. If it contains a (much) newer AllAppUpdate.bin, you could unzip it, find the fyt.prop and update the ro.build.fytmanufacturer id to the id in your original firmware/fyt.prop and repack the AllAppUpdate.bin. Then you copy to a USB-stick:
      • the just (re)created AllAppUpdate.bin.
      • an "update.cfg" containing "twipe_all (preferred) or "twipe_data".
      • the original or a modified "config.txt" onto it.
      • the lsec6315update onto it
        In case of questions, always ask.
    3. Another option will be described here, but not ready yet

    Some remarks about current "seemingly different" FYT units.
    • The uis7862 (ums512) versus the sc9863a (uis8581a) : These units are compatible on AllAppUpdate.bin, but note the ro.build.fytmanufacturer. That is also of importance here. They are NOT compatible on kernel/core level so you can't flash the 6315_1.zip (uis7862) or 6316_1.zip (uis8581a) to each other. However, with above mentioned measures you could flash a newer AllUpdate.bin from a uis7862 onto a uis8581a, or vice versa.
    • The sc9853i versus the sc7731 (uis8141e): Also these units are compatible on AllAppUpdate.bin, but note the ro.build.fytmanufacturer. That is also of importance here. They are NOT compatible on kernel/core level so you can't flash the 6521_1.zip (sc9853i) or 6523_1.zip (sc7731) to each other. However, with above mentioned measures you could flash a newer AllUpdate.bin from a sc9853i onto a sc7731, or vice versa.
    ==================================================================================


    VII. FYT firmware types over the different CPU configurations

    To be written.



    VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller

    To start with: If you do not have a T'eyes unit, do not flash T'eyes firmware. T'eyes uses all kind of paid extensions, which you can only activate by paying and registering your T'eyes' unit id (which you do not have of course because you do not have a T'eyes). Next to that: If you do not use their extensions, the "normal" programs like Google Voice/Assistant can be blocked.

    Before flashing:
    First heck the FYT reseller id of your firmware. Install a good file manager like Total Commander. Go to /oem/app. In that folder you will find a file fyt.prop (In Total Commander, right-click the file, "Open As" -> Text".
    • Inside this file you will find a line with ro.build.fytmanufacturer=43, where the number is the id of the reseller id of your unit (43 is Joying). Write down that number!
    • Inside this file you will find a line with ro.fyt.uiid=<x>. Write down that number as well!
    Another option to get all this info is running my HWGet_Info.apk on your unit which will immediately show some FYT properties and give a zip with a lot of info. This zip file is completely anonymous and does not contain any user data!

    Inside that same folder /oem/app you will find the file config.txt. Copy it to a USB-stick and save it carefully. In case you still have the original firmware of your supplier, you can find inside that zip/rar file the same config.txt. Make sure your have the config.txt belonging to your unit!
    If you copy a firmware from another reseller, or a modded AllAppUpdate.bin, this config.txt may have more or optimized options. Some options from the config.txt from your unit must be copied into the config.txt of this new firmware before flashing.
    The options that need to be copied from YOUR config.txt into the new config.txt:
    • Find the line ro.sf.swrotation=xy (values 0, 90, 180, 270) . Use the value from YOUR firmware in the config.txt for this new firmware.
    • find the line with sys.fyt.bluetooth_type=x. The value is normally 0 or 1, but can sometimes even have other values. Use the value from YOUR config.txt for this new firmware.
    What option to flash do I have:
    There are 3 options to flash:
    • Full firmware
    • System/kernel/core only: this is only the 6315_1.zip
    • Application software: this is only the AllAppUpdate.bin (plus some additional files).
    Actually you have a few more options:
    • You can flash a new bootanimation.zip and/or boot logo to your unit by copying the lsec6315update binary and your bootanimation.zip and/or your LOGO.bmp onto a clean USB-stick (This does not work on Teyes units unless you use the Vincent Vega mods from @gordgelin).
    • You can flash a new config.txt to your unit by only copying that config.txt and the lsec6315update binary onto a clean USB-stick.

    Create the USB-stick for flashing:
    • For a System/kernel/core only flash, copy the lsec6315update and the 6315_1.zip to a clean fat32 USB-stick. Connect it to your unit and flash it.
    • For an Application software flash, copy the lsec6315update, AllAppUpdate.bin, updatecfg.txt and config.txt to a clean fat32 USB-stick. Connect it to your unit and flash it. Note the above mentioned fyt.prop and config.txt
    • For a Full firmware, copy the lsec6315update, 6315_1.zip, AllAppUpdate.bin, updatecfg.txt and config.txt to a clean fat32 USB-stick. Connect it to your unit and flash it. Note the above mentioned fyt.prop and config.txt
    During flashing, let the software do its job and don't start playing with buttons, knobs, air conditioning, etcetera. After reboot wait 3-8 minutes more for some post-flash steps.



    IX. If everything goes wrong and your unit ends up in a boot loop or doesn't get past the boot logo.

    - Download a fresh firmware from your reseller.
    - Unzip it to an SD-card/USB-stick (as normal)
    1) Simple solution: Put the USB-stick/SD-card in your unit and wait till it reboots and starts the flashing.
    2) More complex softbrick:
    • Put the USB-stick/SD-card in your unit
    • "push" the Reset (RST) with a paperclip or something like that.
    • When the boot logo appears, reset the unit again. Now the flashing process should start.
    3) Most complex softbrick:
    • Put the USB-stick/SD-card in your unit
    • "push" the Reset (RST) with a paperclip or something like that.
    • When the boot logo appears, reset the unit again. Now the flashing process should start.
    • Sometimes you need to reset up to 3x times.
    • If after 3 times resetting the flashing still doesn't start, your recovery partition is damaged.
    (or use your self created backup using the script from post #4)
    View
    18
    surfer63
    surfer63

    Backup the application data of your uis78672 (ums512) unit (or your sc9863a (uis8581a) unit).​


    This is especially useful if you do not have an official firmware from your supplier yet. The kernel/cores are universal on these FYT uis7862/uis8581a units, but the AppUpdate is not.

    This works on both the uis7862 and the uis8581a. I don't have this ui8581a unit but it is actually the same for these two types of FYT units.
    It does not backup the 360 camera setup/config!
    It will actually also make a backup of your sc9853i unit, but there it requires some extra follow up steps. Next to that: There are already many firmwares that can simply be downloaded.

    This script will create a directly flashable backup!

    Backup script

    • Unzip the contents of this zip onto a clean usb-stick.
    • Insert it into your unit and let it reboot.
    • It will make a backup of the specific firmware part into folder BACKUP onto the USB-stick (which should therefore have >1GB free space).
    • When it is done, you will have four (4) files in this BACKUP folder: AllAppUpdate.bin, config.txt, lsec6315update or lsec6316update, and updatecfg.txt
    • If you copy these four files to a clean usb-disk and also copy an 6315_1.zip (for uis7862) or a 6316_1.zip (for a uis8581), you can always restore your unit to its factory settings.

    Restore option I:
    For a uis7862: Copy the AllAppUpdate.bin, config.txt, lsec6315update, updatecfg.txt from the BACKUP folder onto a clean USB-stick. Insert that one in your unit and let it flash your unit.
    For a uis8581: Copy the AllAppUpdate.bin, config.txt, lsec6316update, updatecfg.txt from the BACKUP folder onto a clean USB-stick. Insert that one in your unit and let it flash your unit.

    Restore option II:
    In case option I still gives you an unstable system, you need to do a complete flash. For that you also need to flash a new kernel/core.
    • Download the universal kernel/core for uis7862 (current version: 07 December 2021). (For uis8581 download yourself)
    • Unzip it to the same USB-stick which you used in "option I". This means that this content will be added to the USB-stick. It will not replace the content.
    • Insert that one in your unit and let it flash your unit.
    View
    11
    M
    mariodantas
    HAPPY NEW YEAR FYT-ters !
    View
    11
    S
    seb21
    BeeFGee said:
    Thanks for the good idea!
    Unfortunately in my case, the cars SWC are all through CANBUS and so I haven't connected the KEY1/KEY2 inputs to the HU at all. In so doing, I am relying on the CANBUS manufacturer to intepret those button presses as "mode, vol +, vol - ", which is unfortunately unable to be remapped at the moment.

    I may just install a simple aftermarket remote to the KEY1/KEY2, to use my current SWC controls, AND the after market ones in parallel. Then I will remap the after market buttons, to whatever I want, eg. Button 1 = Spotify, Button 2 = Tidal etc ".

    Will update if I manage to get the parts off Aliexpress soon!

    Cheers!
    Click to expand...
    Click to collapse
    Hi.
    Maybe i have solution for you.
    I have modded the ms.apk to add some extra functionality. One of the extras is to modify Canbus based Steering Wheel Controls. The mod is two part : modded ms.apk and settings app.
    All info is in explanation.txt file.
    You must replace your syu.ms.apk with this modded apk. Mod Config App.apk is normally installed as every apk.
    View

New posts