No problem. In the meantime I installed a fan and used a modified MS.apk from gordgelin 4PDA. Now I can use the Fan-Control-App of Teyes, that's very nice. The fan then doesn't always run continuously, but only switches on at 55°C CPU temp.
General General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware
- Thread starter surfer63
- Start date
No problem. In the meantime I installed a fan and used a modified MS.apk from gordgelin 4PDA. Now I can use the Fan-Control-App of Teyes, that's very nice. The fan then doesn't always run continuously, but only switches on at 55°C CPU temp.
Yes, I have seen that one from @gordgelin . I only hear the fan with the motor switched off and with the car ventilation switched off. The fan is so quite that I can't hear it in other situations, let only when driving with engine, tyres and wind noise, and/or with the radio or player on. So I leave it on all the time.
Yes the fan is very quiet, the app is actually unnecessary, but I have to try everything^^ Also, the modified MS.apk fixes the bug that the Bluetooth app can not be minimized and is always in the foreground when making calls.
@mariodantas
I have tried it again. With my Isecupdate, the following appears:
And with yours it's almost the same:
Check Update package signature error and not allow installing update, please use legal system.
Root is not so important for me but it would have been good to have it for some functions.
Maybe someone else here has an idea too?
Last edited:
I may be misremembering, but I believe I saw in the 4pda thread that test keys can't be used to zipsign anymore with the new lsecupdate
edit: Looking at the 2nd post, there's no mention of needing to zipsign anything. I swear I needed to last year when I manually applied magisk to the boot image. Maybe it wasn't necessary
edit: Looking at the 2nd post, there's no mention of needing to zipsign anything. I swear I needed to last year when I manually applied magisk to the boot image. Maybe it wasn't necessary
Last edited:
I have compared the two ZIPs. In the original no certificates are stored and the installation works. In the rooted file suddenly appear certificates and it does not work. It should then actually work with the deletion of the certificates or?
No, it's the 6315_1.zip itself that needs to be zipsigned.
IIRC, I read that with the new updater, they're no longer allowing the test key being used to do so. It's hard for me to search the 4pda thread though since I don't know Russian and can't translate whatever search terms appropriately.
I could be completely confabulating though...
edit: not crazy after all: https://4pda.to/forum/index.php?showtopic=1000996&st=13360#entry116493465
I also recall some discussion where someone claimed to have been able to downgrade. Again, not finding it right now, and question its validity, since I imagine it would've otherwise made it to the first post, supplanting the no-downgrade warning.
This doesn't help you since you're already on the new bootloader / recovery, but perhaps the other components of a "core" 6315_1.zip could be compatible enough / combined with older versions to preserve the ability to flash testkeysigned updates. For now, I see why everyone is hesitant to flash July+ cores.
That said, based on what Teyes has stated, it looks like the new updater is the first step in eventually supporting OTAs for our devices.
edit: Found this: https://4pda.to/forum/index.php?showtopic=1000996&view=findpost&p=115765392
Maybe it's possible to downgrade to june11, and whereever from there
edit: Hmm, I'm on june27 right now, and was able to root fine.
Attachments
Last edited:
mariodantas
Senior Member
I like fake Android, that gets you some extra discount on platforms like AliExpress: so I dont mind it. Actually I think they might stop with this practice, when more buyers file a dispute on AliExpress.
Only a warm-up of the existing fakes, with renewed release date ?? As before this can only be applied, when most actual "full" firmware is installed before. And again, this A12 should only be necessary to get USB-tethering ??? Gets more and more to nowhere
I successfully flash rooted 6315_1.zip and flash magisk, im very familiar with magisk but now i have no idea what to install next...
I only needed root for my Huawei 4G USB Modem to work via PPP3 Widget app, so anything else is just out of my priority but if there are apps or modules that can be useful for rooted Head Unit, please enlighten me..
I only needed root for my Huawei 4G USB Modem to work via PPP3 Widget app, so anything else is just out of my priority but if there are apps or modules that can be useful for rooted Head Unit, please enlighten me..
This is the one I want and it's a sc7862 also or Phoenix automotive has some better looking UI
Attachments
Have a look at the famous collection of UIs from @mariodantas in Post #368 :
"Hi, my little contribution for 7862 and 8581a"
Fyt Factory
Before asking how-to and so on, please carefully read Posts #1 and #2 .
It also depends on how well the CANbus functions are documented and implemented in the CANbus controllers. The same FYT unit/software in one car only has the option to display the airco settings, and in another car (Ford for example has well documented their CANbus protocols) can even actively change airco settings and the like.
I read through the entire post (hours) I wasn't sure because of the factory # and what not. I appreciate your response and will go back an check, I guess I was looking for clarification from a pro.
Thank you
Yes, I understand this but that brings up another question. Will different brand canbus have different options for the same vehicle, do some communicate better than others?
Yes, I suppose so. There are 4-5 most used controller brands used on these units where the suppliers provide one CANbus controller for "this" car and another for another car brand.
I do not know if anyone has a clear overview of which one is best for a specific car/brand.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3
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)2
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.2
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.2I got Android Auto working again
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.
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.2You 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.
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. -
35Last 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.
- 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.
General unit information
Q&A - Questions & Answers
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.
27Last 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
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:
Or you want to improve the microphone function a little, you can add or modify the following lines:Code:ro.product.locale = pt_BR ro.sf.swrotation = 90
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).Code:persist.sys.zlink.mic.vol=9.9 persist.audio.mic.senstivity=1 persist.btmic.gain=10 persist.btspk.gain=7
II. AllAppUpdate.bin
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.)")
IV. Some info on partitions
V. The lsec_updatesh folder, lsec6315update binary and 7862lsec.sh script (and what about "universal" scripts)
VI. Compatibilty between uis7862 (ums512) Firmwares
VII. FYT firmware types over the different CPU configurations
VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller
IX. If everything goes wrong and your unit ends up in a boot loop or doesn't get past the boot logo.
18Backup 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.
1111
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.
