I need to lower the microphone gain.
My audio codec is clipping becouse of incoming PCM samples saturated from
the mic. I don't need AGC becouse it doesn't work well with my app.
I just need to manipulate the mic gain via software.
Is there a way to do it? I'm using waveform audio api ti capture voice.
Actually the gain is too loud !!!
Thanks.
Anyone knows?
OK, I don't have the answer. But since no one is responding I'll try to give a few ideas that might help.
First, I have a hp6315 and an apache. Under settings, they both have a utility to enable/disable AGC. The ipaq's utility is labeled "ipaq audio" if you disable agc, you can then configure the microphone gain. This gain is stored in the registry. I think searching for gain or audio will find it. The apache doesn't have this. searching for audio, gain, wav, volume in the apache registry doesn't find anything that looks like microphone gain. I guess this is a "value added" thing from hp. But you could try searching anyway.
Then there's the mixer API. This is the way that user level apps are meant to control the audio. Works great on the desktop. Use mixerGetNumDevs() to find out how many devices you can control. On the h6315 mixerGetNumDevs returns 0. I haven't tried the apache, but I can remember a few years ago reading that many (most?) devices return 0. Oh well, hopefully you'll have better luck. However, there are two mixers that are implemented on the pocketPC the question is how to access them.
see this link for info on the mixers
http://blogs.msdn.com/medmedia/archive/2007/01/12/what-do-you-mean-by-mixer.aspx
Here's a link that shows the relationship between the mixer api and the other mixers, wavedev2 mixer, and software mixer.
http://msdn2.microsoft.com/en-us/library/ms923709.aspx
You'll notice that the the mixer api interacts with the mixer in the device driver not the software mixer in the WaveAPI.dll. You'll so notice that this section on audio drivers has pages for MDD/PDD drivers and Unified Audio Model (UAM) drivers. Platform Builder for WinCE 5.0 comes with a sample for each of these model drivers. Both models handle WAV_IOControl Messages. There are two types of messages, IOCTL_MIX_MESSAGE for the mixer, and IOCTL_WAV_MESSAGE for the rest of the driver. It looks like these IOCTL_MIX_MESSAGE are the way the mixer API controls the mixer. In the MDD/PPD sample they can be used to set WPDMX_MIC_VOL and WPDMX_LINEIN_VOL. In the UAM driver it's AC97_MIC_VOL and AC97_LINEIN_VOL. Perhaps sending the right IOCTL will solve the problem.
This blog entry
http://blogs.msdn.com/medmedia/archive/2007/01/03/windows-ce-audio-driver-samples.aspx
seems to say that a wavedev2 sample is available now. Also, while the WinCE 5.0 page above only metions two models the corresponding wince 6.0 also talks about wavedev2. I suspect if you got the current version of platform builder for WinCE 6.0 (trial version is free) you would have get the sample code for wavedev2, which is likely to be the best documentation of how this works. Amazingly, the drivers aren't that hard to read.
Both of the functions waveInMessage() and waveInSetProperty() are available to user apps. Hopefully both should be able to change the microphone gain if you can set the parameters properly. While most of these things are about windows CE, I think most (or all) apply to windows mobile 5.
Windows mobile 5, likely uses wavedev2 devices not MDD/PDD or UAM drivers.
Another interesting page about wavedev2 audio is here:
http://blogs.msdn.com/medmedia/archive/2007/01/04/the-wavedev2-gainclass-implementation.aspx
If your able to succeed or even learn more, be sure to post it back here.
I said a lot so I probably got something wrong. Anyone, please feel free to correct anything.
mixerGetNumDevs() returns 0 on my device
I can't find any registry entry which suggests microphone gain manipulation.
Perhaps i just need to send a waveInMessage properly.
I'm getting confused, should i implement a driver for this?
How do i know what kind of driver is running on my device and what messages
does it accept?
Thanks.
i think this may be what you need(?)
use a registry editor, (phm do a good free one)
hkey_local_machine/software/htc/audiogain (and audiogain 0 and 1 and 2)
try playing with the settings in there, soft reset to take effect
I don't have that keys on my HTC, should i create it?
Do you mean audiogain0 audiogain1 audiogain2?
Thanks.
see the attached screenshot, if you don't have those settings to adjust, a similar/same question was asked last night in a other thread, with different answers here
http://forum.xda-developers.com/showthread.php?t=306655
Looks like the cab file from the link provided by bbobeckyj just sets those audiogain registry settings. I don't have those settings on my apache. I don't think adding will help, but "you never know".
If you want to use waveInMessage() or waveInSetProperty() search for them at microsoft. You'll find there are a few parameters that you don't know. Read though the sample drivers that you can get with platform builder. See what values they expect, and which one cause them to change the microphone level. Try calling the function with values from the sample driver. While there is no guarantee that they use the same values, it's like that they do. I would start with the wavedev sample.
I don't know why microsoft doesn't seem to allow access to the source without agreeing to download all of platform builder, but it looks like that's the only way to get it. You can download the trial version for free. The source often helps if your trying to fingure out how something really works.
Uhmmm, i havn't found any download link about platform builder for windows CE 6.0. I've only found the 5.0.
Should't the trial be free?
Thanks.
I need to fix audio gain in my Itel Experience Phone (Windows Mobile 6.0 Pro)?
Please help.
I need to mute mic while on a call. Anyone has a idea of how may i do it?
Thanks
moved to the right forum, please post in the correct forums.
This is a little project i've been working on and i thought it was ready enough to be released into the wild. Below is the readme file. I think it covers everything for now. Before posting please read the first 3 posts - especially post 3 - if it is obvious that you haven't done this i will not respond with any form of help and i don't not expect any of the users to do so either.
----------
Included with this zip file are several .cab, .reg and .xml files that will automatically configure your NRGZ28 energy rom when XDA_UC runs upon first boot after flashing.
Included are the following configuration files
activesync.xml
This will configure your MS Exchange settings. Editing with your personal settings is required. Look for the username, server, domain and password tags at the start of the file
aGPS.reg
Enables aGPS
BackLight.reg:
Sets backlight to auto. There are some other settings included for dim and light off times when on battery and AC power aswell
bt_ident.reg
Sets the Bluetooth Identity. Edit the deviceid line to suit
copy.mscr
Copies files from the copy2root folder to the matching location in device storage. A My Documents folder with My Ringtones and My Wallpapers sub folders have been created already. Place you ringtones and wallpapers in these folders. There is also an application data folder which contains a coreplayer config.xml and a program files folder which contains a myPlayer options.ini. Feel free to create more. Thanks to nrfitchett4 for providing this script.
Del.mscr
This file will remove all unwanted ringtones, wallpapers and any other files you decided to add. Edit as you need to. N.B any readonly files will need attributes changed before they can be deleted.
DisableSenseVsync.cab
Disables Vsync in sense increasing the framerate thus making it faster
HD2MemTweaks.cab
Increase's glyphcache size past the bsb tweaks and advanced config defaults, incrases filesystem cache size and a few other bits. This cab file is optional. Delete it if you don't want it. Thanks go out to g.lewarne for documenting the tweaks
HTCAlbumIgnore.reg
Stops the sense music player playing ringtone files from \My Documents\My Ringtones\ and \storage card\ringtones. Copy the examples
if you want to add to it.
M3PH HTC Location Service Enable.cab
Enables HTC location Service and automatically excepts the TOS
ident.reg
Changes the phones identity at first boot. If NRGZ28 won't make it sensible i'll make it so we can customise it . Editing required. this one is pretty obvious
Palringo.reg
Sets up palringo, sorta, change [email protected] to your user name and it should show up at sign in. All you need to do is enter your password
QuickGPS.reg
Enables and configures QuickGPS with the defaults
Ringtones.reg
Configures the ringtone, sms tone and email tone. Needs some editing but you only need to change the file name for each entry, not the
path. The Ringtone2 entry allows for second ringtone to be added to the list of usable ones so you change them with too much fuss.
Also enables flashing light on sms reception for 5 minutes.
wifi_setup.xml
wifi settings. Edit required. This link should help you set it up (see post 3 for details on how to edit)
M3PH Enable Time Auto Update.cab
Enables NTP
Volume.Reg
Sets the volume levels. You can use this one or export your own from HKEY_CURRENT_USER\ControlPanel\Volume
Windows live.reg
Pretty much configures windows live. You do still need to enter your password and you will also need to do atleast one manual sync before Sense will create the mailbox on the email tab but otherwise it works
Opera User Agent String folder
See the readme.txt in that folder
Sense Folder
If you put your wallpaper in this folder it will be installed as the sense default. Just rename it to sense_wallpaper.png.
Start Menu folder
Copy Start Menu shortcuts here
----------
If you like this or any of my other work click the "donate to me" link above my avatar
----------
REMEMBER THIS COLLECTION OF FILES IS PRESENTED AS IS UNDER THE GNU GPLv2. IT IS BETA SOFTWARE AND COMES WITH NO WARRANTY OR ANY FORM OF OFFICIAL SUPPORT. I, M3PH, SHALL NOT TAKE RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSE THAT MAY OR MAY NOT OCCUR TO YOUR DEVICE.
Change Log
Change Log:
1.1.1 Final
Removed Keyboard sensitivity tweaks
Removed opera memory tweaks
Added more palringo settings
Added Quick shutdown settings
1.1 Final
Updated volume.reg to default to seperate system and ring volume controls.
Removed all tweaks now included in Energy roms dated nov30 and newer. I will leave v1.0 posted for a while so people that like to install older versions still get the benefit
1.0 Final
Added Windows_live_settings.reg. You will need to edit it as prescribed on page 16 but it will work.
Added Improved GPS settings.cab. This is untested by me but i trust scabes24 enough to know he's not going to pass on unreliable tweaks
Improved M3PH Location Service enable.cab: Added an extra registry setting that should trigger Manila to showing it's on. This is doubtful but even if it doesn't the file does work
Added alarm_settings.reg: This is only an example file. You will need to export your own settings but this should be a reasonable starting point
Removed readme.txt: It was a habit a picked up from Linux development practices and was pointless for this project
Removed time.reg permanently because there is nothing changed in the registry when it is enabled.
--- Pre Final releases
Tips and Tricks
What follows are some tips and tricks i have found that i'm not going to include for whatever reason but thought some people might find handy or notes on what settings do what and their options.
Q. Can i delete file xyz using xda_uc because i like to have as much space as possible?
Yes you can. i found this link. All you need to do is create a file in the xda_uc folder with the extension .mscr which contains the following:
Code:
delete \test.txt, TRUE
or
Code:
deltree \test, TRUE
Obviously change test to the file or directory you want to delete. For more details check out the provided link above.
Q. The default wifi.xml doesn't match my configuration and i can't find a resource that tells me what are valid values for the options?
A. See this link and this one. As a note if you use WPA2 you need to use <parm name="Authentication" value="6" /> and WPA2-PSK is 7
Q. The exchange settings in activesync.xml aren't how i like them. Can i change them?
A. Sure can! Here's a link to the documentation
Q. I use a [enter service name here] and i want to create an xml file to configure it when i update my rom. Can i do this?
A. Thanks to microsoft developing WAP provisioning to an incredibly encompassing level you can do almost anything. See this link
Q. I want to make a cab file out of all my changes. How do i this?
A. There are many ways but i think this is the best one i've found because it doesn't involve any third party software and is really simple. All you need is the windows mobile sdk, which can be found here. You may also need visual studio but i'm not sure
Making either is very simple. You just pass a normal XML file to makecab and give it the name of the output file you want. The one trick is that the XML file must be named _setup.xml. If you call it something else, makecab will succeed, the CAB or CPF file will be generated fine, and then it will fail with a cryptic error when you try to use it. Beware, the documentation doesn't make this very clear.
The syntax for making a CAB file is:
Code:
makecab _setup.xml config.cab
Click to expand...
Click to collapse
Q. Wow you really do know a lot about this sort of stuff. How can i learn?
A. Well i don't know that much at all really, i just learn fast. Most of the stuff you see here was obtained from or via this MSDN article: http://msdn.microsoft.com/en-us/magazine/cc500581.aspx
Q. Is there a way to boost the performance of Opera in terms of memory/speed?
A. Yes, this cab will force Sense to unload when launching Opera, allowing for better performance while browsing. (When exiting Opera, Sense will then reload) (thanks to Scabes24 for this one)
Code:
[URL="http://www.megaupload.com/?d=O5O1RE97"]Enable Opera Max Memory Tweak.cab[/URL]
Q. I've installed the Opera tweak and everything is working fine, but the page loading seems very slow. Is there a way to improve this?
A. Yes you can, the following registry tweak will enable almost instantaneous web page loading in the web browser. It apparently enables wireless N mode but seems to work with cellular data too. Go to:
HKLM/Comm/BCMSDDHD1/Parms
11nModeDisable = Change from 1 to 0 (thanks to Scabes24 for this one aswell)
Q. My wifi hotspot uses EAP certification and i can't use it because the phone gives me a certificate verification failure error. What can i do?
This was posted in the energy rom thread
NRG, after weeks of not being able to connect to my work wireless network because I was getting a "certificate is from an unknown authority" error, I finally got it working. Can you add this key to your ROMs?
[\HKLM\Comm\EAP\Extension\25\]
"ValidateServerCert"=dword:00000000
This is where I found the answer:
http://social.msdn.microsoft.com/for...-3ebe003aa996/
Click to expand...
Click to collapse
Thanks to oppressa for hunting this one down. The tweak is included as an option in EXCT as M3PH EAP Cert Disable.cab
Here are some locations where 3rd party apps store their values. These were provided by angusc
CodeCity Time settings and Key Code:
[HKEY_CURRENT_USER\Software\CodeCity\CityTime]
Ageye G-Alarm settings and keycode:
[HKEY_CURRENT_USER\Software\ageye\G-Alarm]
Ageye G-Profile settings and keycode:
[HKEY_CURRENT_USER\Software\ageye\G-Profile_v1]
SK Manager settings and Keycode:
[HKEY_CURRENT_USER\Software\sk\smgr]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:S KSM]
SlingPlayer Login Details:
[HKEY_LOCAL_MACHINE\Software\Sling Media\SlingPlayer\SlingAccounts]
SPB Language Cards key code:
[HKEY_CLASSES_ROOT\CLSID\{F5C24D33-742A-41BC-BC22-1195BC138ECE}]
SPB Traveller Key Code:
[HKEY_CLASSES_ROOT\CLSID\{7D562A74-A69B-45F5-8D1F-20DABDCE2C76}]
SPB Wallet Key Code:
[HKEY_CLASSES_ROOT\CLSID\{A79D1B0D-2F6A-4E7E-AF94-5EEBC8BFD684}]
Sprite Back-up Key Code:
[HKEY_LOCAL_MACHINE\Software\Sprite Software\Sprite Backup]
RSS Hub Settings and Feed Storage Locations:
[HKEY_CURRENT_USER\Software\Ilium Software\RSS Hub]
SPB Traveller Settings:
[HKEY_CURRENT_USER\Software\Spb Software House\SPB Traveler]
Today Wall Paper Location:
[HKEY_CURRENT_USER\Software\Microsoft\Today]
KeyBoard Config by Tarkim (Settings):
[HKEY_LOCAL_MACHINE\Software\KeyboardConfig]
Resco Explorer Settings:
[HKEY_LOCAL_MACHINE\Software\Resco\Explorer]
Palringo Settings:
[HKEY_CURRENT_USER\Software\Parlingo\Settings]
Click to expand...
Click to collapse
The FAQ
Q. Will you include xyz tweak for me?
A. Only if it's a common one or one that i haven't thought of
Q. I use xyz program and i want to have the config file included in your great collection. What do ya' say?
A. See above but you could always spend 10 minutes tracking it down and then creating a folder in copy2root for it
Q. Why is the bluetooth identity the only tweak for BT you include?
A. Because everyones setup and hardware is far too different for it to be worth it. Also, Although you can export the pairings importing them may not be possible due to the way the bluetooth security protocols work.
(More To Come)
Happy to try this, thank you for cobbling everything together.
wow
this would be so handy, i hate spending time making your phone how you like it. I don't flash as often because i get too comfortable with the current configuration.
thanx M3PH
btw: without NRGZ28 i would have sold my HD2 7 months ago
grumpylad said:
Happy to try this, thank you for cobbling everything together.
Click to expand...
Click to collapse
No worries. I did it because i was getting annoyed with spending ages setting everything up and even more annoyed with people not reading the energy rom FAQ properly (i'm guilty of that too). I used the pre-release version last night after flashing the latest energy rom and it saved me in the region of an hour to an hour and a half. It's not perfect by a long way. Things like the sms led notification is enabled and some people may not like that but is is easily reverted with bsb tweaks.
My plans for the next version is to have all the reg files converted in to cab files for they can be removed and i'll tidy up the readme a bit.
One thing i would like help with though is the FAQ. Can the first few people take notes of any problems or questions they have and things or that nature.
Thanks everybody
Thank you, I'll try it out with the new Energy release. I'd be happy with the reg files to import it doesn't even need to be a cab!
Thanks!
lantern20 said:
Thank you, I'll try it out with the new Energy release. I'd be happy with the reg files to import it doesn't even need to be a cab!
Thanks!
Click to expand...
Click to collapse
Cab files are better because they can be removed and Reg files can't. So if one of these files causes a problem your stuck and that's why it's labeled as alpha software. Also labelling it as that will scare off the less experienced users from trying it and doing themselves a mischief.
V0.2 will be all cab files as far as possible but don't expect a release until 0.1 has had a thorough real world testing.
oh. it is better ,if i find this post eight hour ago.
it drives me nuts ,everytime i get into a new nrg rom.
thank you very much.
Great idea man, thank you so much for this!
Thanks a lot for this! It will definitely save me a lot of time after a rom update. I just have to hope I've set them up correctly and dont break something
Hello
This project is a very good project, I hope is work well
Is it compatible with other language ?
Ex : "Start Menu" folder in WWE Rom is "Menu Démarrer" In FR
Good luck.
@+
diamond_cbr said:
Hello
This project is a very good project, I hope is work well
Is it compatible with other language ?
Ex : "Start Menu" folder in WWE Rom is "Menu Démarrer" In FR
Good luck.
@+
Click to expand...
Click to collapse
no sorry as it stands it's wwe only. If you want to convert it to french and send it over to me i will post it.
yeoldgreat, if you would like to pm me your changes i will look them over.
Overall i'm really pleased with the response so far but i really do need everyones help with composing the faq because for me this works fine (apart from the unteseted bits because i haven't used them yet) so can all of you please, please, please make some notes on your progress and keep posting those questions
M3PH said:
Overall i'm really pleased with the response so far but i really do need everyones help with composing the faq because for me this works fine (apart from the unteseted bits because i haven't used them yet) so can all of you please, please, please make some notes on your progress and keep posting those questions
Click to expand...
Click to collapse
My temptation would be to assume that the FAQ is written for me if I can install and get it working anyone can. For instance in the wifi detailing where the various parm's can be found would make it much easier to install. Very happy to install on what you have and pass back any questions assumptions.
As I frequently flash(ROM's only) I can help with refining the documentation.
grumpylad said:
My temptation would be to assume that the FAQ is written for me if I can install and get it working anyone can. For instance in the wifi detailing where the various parm's can be found would make it much easier to install. Very happy to install on what you have and pass back any questions assumptions.
As I frequently flash(ROM's only) I can help with refining the documentation.
Click to expand...
Click to collapse
Sweet, thanks. That is exactly the sort of thing i'm looking for, because it's been over a year since i did any kind of manual writting i'm pretty rusty. It also doesn't i developed most of the parts in just over 24 hours working on my phone and not my pc everything is a bit scattered in my mind. That's the reason why the readme looks the way it does. It all came out in a bit of a splurge.
The wifi script is one of my older scripts and it took 3 attempts to get right and now i can't for the life of me find the resource on ms technet that i used.
I'll probably have a sitdown over the weekend and have a rerun through the readme and make it a bit more detailed. If i can make it as easy to install as possible then the faq won't be such an important thing
How many people want me to include a coreplayer config.xml in the next version? i've got one that works perfectly with myplayer and turbo3d.
Nice Work
I used a number of these to flash the latest Energy Rom and it worked out great. Very smooth! It will be interesting to see what is added on in the future. Thank you for putting the time in and starting a new thread.
jamesdee said:
I used a number of these to flash the latest Energy Rom and it worked out great. Very smooth! It will be interesting to see what is added on in the future. Thank you for putting the time in and starting a new thread.
Click to expand...
Click to collapse
I'm taking suggestions for additions. So how about one?
Very interesting sir!
I am going to flash the new Energy ROM either tonight or tomorrow and so will chuck this in with it.
I wont use several of them as I dont use those aspects, but those I do will return with feedback.
I have been frustrated with this as well.... fingers crossed.
Really this should be on the developers forum, but I cannot post there.
New 7" Chinese satnav, WINCE6.0.
cdFFM-0.3.5 put on TF card and run.
Errors in lines 2251, 2277, 2264, 2270, 2258 for info seem to be links, probably already there - pointing elsewhere.
After reboot many menu items don't work, run MortScript.exe (in root directory of ceFFM), this will allow the scripts to work thereafter, and the menu items work (note some are dummies - useful for modding).
It doesn't boot unless you do the simple kludge below.
To boot into ceFFM use "Navi Path" button to point Navigation to CEMenu.exe (in root directory of ceFFM), then check button takes you to cdFFM, then you can use "Navi Path" button to "Auto run GPS when startup" and you are straight into ceFFM.
[My path was SDMMC\cdFFM-0.3.5\CEMenu.exe, for example].
You then need to edit the navigator link in the programs directory.
In my case it was iGO8 so I edited SDMMC\cdFFM-0.3.5\PROGRAMS\iGO8.lnk to point to my navigator program like this:
23#"\SDMMC\iGO8\iGO8.exe"
The 23# is the number of characters in "\SDMMC\iGO8\iGO8.exe" (+1 for some reason)
Please note that quite a lot of the menu items in ceFFM are capable of brikking your device.
Now a question
OK, I know its poor form to reply to your own post but...
Two things still not sorted for this satnav:
1) A 480x800 version of NaviPlayer. I don't know how to set the skins to work.
2) The satnav will not load .CAB files. Even if I put wceload.exe and run it pointing to the required file, it just claims the .CAB file is not valid. I've tried quite a few, and I think they are. I presume its a means to prevent people modifying the device. Stand alone .exe's work just fine. Anyone got a fix for this, its really irritating!
If wceload.exe fails, and then probably only signed .CAB-files are accepted. Workaround: Allow installing unsigned .CAB-files. You do this by editing device's registry as
following:
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001001"=dword:00000001
"00001005"=dword:000000DE
"00001006"=dword:00000001
"00001017"=dword:00000010
"0000101a"=dword:00000001
"0000101b"=dword:00000001
HTH
jwoegerbauer said:
If wceload.exe fails, and then probably only signed .CAB-files are accepted. Workaround: Allow installing unsigned .CAB-files. You do this by editing device's registry as
following:
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"00001001"=dword:00000001
"00001005"=dword:000000DE
"00001006"=dword:00000001
"00001017"=dword:00000010
"0000101a"=dword:00000001
"0000101b"=dword:00000001
HTH
Click to expand...
Click to collapse
That's neat...
OK, not that unexpectedly I find no entry \security\policies\polices .
"security" is found:
use\comm\security
machine\comm\security providers
machine\comm\security
machine\software\microsoft\Rpc\securityService
value: machine\software\Rpc ="DCOM Security"
machine\software\internet explorer\security
value: machine\software\internet explorer\security\basic = "security name"
machine\software\internet explorer\security\NTLM = "security name"
"policies" doesn't appear at all.
I found a reference to "username = guest", but neither appeared anywhere else.
I did spot in machine\OEM that value "app" is a path that points to the OEM menu system (main.exe).
May be possible to intercept here (if you wanted).
root\.cab is set to name "@"=64 value "cabfile"
hmmm... nothing that leaps out at you ...
bother!
farmeroz said:
That's neat...
OK, not that unexpectedly I find no entry \security\policies\polices .
Click to expand...
Click to collapse
Create it!
OK I did that, rebooted.
A bit scary as I haven't added such things before...
Still doesn't work.
Attempting to 'run' nitro.cab (nitrogen renamed) fails
However the OS claims that there is no application associated with 'nitro'.
However .CAB is a cabfile under \root\
and a cabfile default icon is \SDMMC\ceFFM-0.3.5\system\wceload.exe,-101
shell\open\command is \SDMMC\ceFFM-0.3.5\system\wceload.exe\"%1\"
So (whilst I haven't a clue) I would expect .cab files to be spotted.
farmeroz said:
OK I did that, rebooted.
A bit scary as I haven't added such things before...
Still doesn't work.
Attempting to 'run' nitro.cab (nitrogen renamed) fails
However the OS claims that there is no application associated with 'nitro'.
However .CAB is a cabfile under \root\
and a cabfile default icon is \SDMMC\ceFFM-0.3.5\system\wceload.exe,-101
shell\open\command is \SDMMC\ceFFM-0.3.5\system\wceload.exe\"%1\"
So (whilst I haven't a clue) I would expect .cab files to be spotted.
Click to expand...
Click to collapse
Use Win32 "MSCEInf" utility (it's freeware, google for it) to extract any .CAB file, if "wceload" doesn't work for you. After having extracted the .CAB, you are able to copy the application/data to any location of your choice at mobile device.
Oooh... That looks like a solution....
Didn't work. Can't see why though.
Hmmm. That editor shows (XML)
[Version]
Signature = "$Chicago$"
CESignature = "$Windows CE$"
Provider = "BenThon"
surely chicago is a win9x version?
I thought I had, but reading the long Nitrogen thread I don't think I did.
There doesn't seem to be a version for wince5/6, that's downloadable from anywhere, even though it exists somewhere because people have run on wince5 systems. Microfi is overworked...
I was somewhat under the impression that mobile was +- same as CE, but clearly not.
Signature="$Chicago$"
simply tells you the machine's OS the cab was built on[
I guessed that, sadly after I had posted.
Basically for my satnav I need a music player to play in the background, easily reachable from iGo8 (using megaduck99 skin, I have now got just how I want it!) nav screen and back. Really all I ever want to do is skip to the next track, as with 1000+ MP3's, sometimes you just aren't in the mood for some of them. Naviplayer (if it had an 800x480 skin) is finger usable for this whilst driving. Then (with bluetooth) I can just plug the satnav into my car radio (FM is rather poor quality) and utter perfection .... (who needs CD's these days?).
I'll have to have another stab at working out how to run the skins on naviplayer.
Your front end, particularly with the wealth of apps, is excellent. I have now put it on a no-name 7" netbook I use to backpack with, and now realise how slow it is compared to the more modern ones. Good enough for emails etc though.
NB I have been starting (manually) by running CEMenu.exe rather than ceFFM, is that what you intended?
To reskin NaviPlayer it merely suffices to have a folder named "mpskin" containing the files for the required skin copied from the examples given.
Its not immediately obvious because there is no default skin file provided (eg the small gold one it defaults to).
The fonts aren't quite right, either size or location
I have come across a bug in some of the apps. If I open notepad and the file-open, the entry box is not within the screen just far enough off that you can't grab it to pull it down. This is also the case in word. Doubtless somewhere there is a file that sets the position, any ideas? Annoying because I can't edit the mpskn.skn file....
Modified MP3P.SKN inside NAVIPLAYER\MPSKIN
This should work for all the 'Simple 3.1" skins.
If you want a button to appear when minimised you will have to adjust the button size/position/etc .
This is done in/with [MAIN_MIN_WINPOS]
If you have a larger button (as I do) then you will need to make a button of the appropriate size to replace the one in
BACK_MIN.BMP
I haven't done one yet, for iGO8 it will need to be under the bluetooth one, and similar size.
Hope this is useful.
NB I have no loader files for NaviPlayer (last good mod), I got it included in ceFFM.
;====Modified MP3P.SKN
[MP3 INFO]
MP3_Ver=1.0
[MAIN_WINPOS]
Width=800
Height=480
[MAIN_MIN_WINPOS]
Left=66
Top=0
Width=60
Height=24
WidthOne=1
[TRACK_POS]
Left=572
Top=129
Width=60
Height=14
SubValue=17
[TIME_POS]
Left=188
Top=129
Width=90
Height=14
SubValue=17
[SEEK_POS]
Left=212
Top=152
Width=373
Height=9
[INFO_POS]
Left=280
Top=189
Width=150
Height=9
;SubValue=0
[STATUS_POS]
Left=387
Top=375
Width=64
Height=38
[TITLE_POS]
Left=218
Top=65
Width=366
Height=20
[VOLBAR_POS]
Left=466
Top=272
Width=162
Height=6
[PEEK_POS]
Left=173
Top=250
Width=250
Height=28
SubValue=7
[VOLSLIDER_POS]
Left=466
Top=271
Width=162
Height=10
SubValue=3
;[TIMESLIDER_POS]
;Left=216
;Top=179
;Width=369
;Height=10
[PLAYOPT_POS]
Left=561
Top=184
Width=147
Height=12
SubValue=30
;====================
;Button Position
;====================
[BT_PLAY_POS]
Left=331
Top=330
Width=140
Height=150
[BT_STOP_POS]
Left=474
Top=285
Width=178
Height=49
[BT_PREV_POS]
Left=147
Top=396
Width=180
Height=84
[BT_NEXT_POS]
Left=474
Top=396
Width=178
Height=84
[BT_OPEN_POS]
Left=0
Top=102
Width=140
Height=73
[BT_MODE_POS]
Left=661
Top=342
Width=139
Height=138
[BT_ALBUM_POS]
Left=0
Top=182
Width=140
Height=73
[BT_EFFECT_POS]
Left=660
Top=485
Width=130
Height=70
[BT_EQ_POS]
Left=661
Top=182
Width=139
Height=73
[BT_PRESET_POS]
Left=661
Top=261
Width=139
Height=73
[BT_MULTI_POS]
Left=0
Top=23
Width=140
Height=73
[BT_VOLDN_POS]
Left=147
Top=342
Width=180
Height=50
[BT_VOLUP_POS]
Left=474
Top=342
Width=178
Height=50
[BT_MUTE_POS]
Left=0
Top=261
Width=140
Height=73
[BT_EXIT_POS]
Left=661
Top=23
Width=139
Height=73
[BT_MINIMIZE_POS]
Left=661
Top=102
Width=130
Height=73
[BT_SHUF_POS]
Left=0
Top=342
Width=140
Height=138
[BT_MIN_NORMAL_POS]
Left=0
Top=0
Width=60
Height=24
[BT_MIN_NEXT_POS]
Left=62
Top=0
Width=4
Height=24
[BT_MIN_MUTE_POS]
Left=68
Top=0
Width=4
Height=24
;==============================
; IMAGE LIST
;==============================
[IML_NUMBER]
Width=16
Height=12
[IML_STATUS]
Width=32
Height=38
[IML_PLAYOPT]
Width=49
Height=12
;==============================
; COLOR Type : BGR (0xffffff)
;==============================
[COLOR]
Info=0xffffff
Title=0xffffff
Seek=0xffffff
PeekLeft=0xffffff
PeekRight=0xffffff
VolumeBar=0xd14a00
;==============================
farmeroz said:
Please note that quite a lot of the menu items in ceFFM are capable of brikking your device.
Click to expand...
Click to collapse
You really experienced it? If so then you should specify them here to clarify things.
ceFFM's Original Thread
jwoegerbauer said:
You really experienced it? If so then you should specify them here to clarify things.
ceFFM's Original Thread
Click to expand...
Click to collapse
Sorry for the delay, HDD MBR problems....
No, I didn't brick my machine, I am very cautious. However being able to play with the registry, hexeditors etc, is potentially hazardous.
Hmm, on reflection its a combination of not knowing what they all do, and not knowing my way round winCE. Ie ignorance.
String not closed
China gps KENMOO 7', wince 6. Hello, excuse my English. Trying to install ceFFM, the installation begins, but then the message: String not closed (mising quote)
Line 3631 (\ SDMMC \ ceFFM.mscr)
If (key EQ "Startup), and it's over. I can modify anything? Installing on SDcard. Thank you.
Last revised: 07 June 2023 (reason: added info for the uis8581a)
This thread tries to be a "one fits all" thread about FYT based Spreadtrum Unisoc uis7862(s) (Unisoc ums512) and uis8581a (sc9863) 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 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
To start with: the uis7862 and uis7862 are 100% identical and compatible. The 7862s is just the same CPU but slightly faster.
Hardware
CPU uis7862 64bit 8-core (2x ARM Cortex-A75 @ 1.8 GHz, 6x ARM Cortex-A55 @ 1.8 GHz)
CPU uis7862s 64bit 8-core (2x ARM Cortex-A75 @ 2.0 GHz, 6x ARM Cortex-A55 @ 2.0 GHz)
CPU uis8581a 64bit 8-core (4x ARM Cortex-A55 @ 1.6 GHz, 4x ARM Cortex-A55 @ 1.2 GHz)
CPU: uis7862 (ums512) versus the new uis7862s (ums512). Specs/Benchmarks/Info. (Also allows you to compare with other CPUs).
CPU: uis8581a (ums sc9863) versus the uis7862. Specs/Benchmarks/Info. (Also allows you to compare with other CPUs).
Android version: Android 10 (API/SDK 29); Fake Android 11 & 12 (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
Firmware
Firmware always comes with an update/flash binary, a kernel zip, an application layer bin and a few config and additional files/scripts.
The kernel, which contains the basic Android layer with drivers and kernel modules is inside the 6315_1.zip for a uis7862, and inside the 6316_1.zip for a uis8581a.
The update/flash binary is the lsec6315update for the uis7862, and the lsec6316update for the uis8581a. Those lsec update/flash binaries check for the right hardware and the right kernel zip. For example: You can't flash the kernel zip from a 782(s) CPU onto a uis8581a.
The application layer is the AllAppUpdate.bin. It is 100% compatible over the uis7862(s) and uis8581a. Note that FYT is bad in multi-resolution. Although the application layer should be compatible, they make differences for all resolutions to 1280x720 and those for 2000x1200. Also the Tesla units get apks with other resolutions and an extra aircondition apk. Funtionally they are 100% identical.
Resellers:
Atoto, Ebilaen, Eki, Farcar, Funrover, Idoing, Isudar, Joying (only uis7862), Junsun, Mekede, NaviFly, Sinosmart, T'eyes (only uis7862), Winca, Zhan. There are more resellers, but not all of their models might be FYTs. Same for some resellers in this list.
A few remarks about which CPU to choose (my vision).
The UIS8581a is in general 15~20% slower than the "standard" uis7862, which is again about 5~10% slower than the "new" uis7862s.
What will you notice in real life: Almost nothing!
When to chose a uis7862(s)? If you have a 2000x1200 resolution screen, I would go for the 7862 or the 7862s. Bigger screens require faster CPUs. The 8581a is strong enough to "power" such a screen, but here you might notice the difference when fast screen rendering is required. This is not for video, but in case of navigation apps that need to calculate long routes or calculate/redraw every split-second for example, but nowadays with OpenGL rendering in those apps it might not be an issue at all.
If you compare the uis8581a with the previous intel airmont sc9853i, which FYT no longer makes, the uis8581a is again ~20% faster than the sc9853i. I never had the idea that my previous sc9853i was slow, on the contrary.
Go for 4GB memory or more. 3GB might be enough for a "light user", but you might experience delays in starting new apps as other apps first need to be stopped/swapped out.
Note that these units still come with EMMC flash memory, like in cheap phones, instead of the (much) faster UFS (in better phones). So loading apps from storage will not be much faster on a 8581a versus a uis7862(s).
Q&A - Questions & Answers
Q1: I already see uis7862(s)/8581a units having Android 11 and even Android 12, what about it?
These Android 11 & 12 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(s) and uis8581a) units compatible? Is all (uis7862(s) and 8581a) firmware compatible?
See also above under "General unit information".
The uis7862(s) units based on FYT are all hardware and software compatible. Also the uis8581a units based on FYT are all hardware and software 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.
Firmware always comes with a kernel (uis7862(s) -> 6315_1.zip; uis8581a -> 6316_1.zip) and the application layer AllAppUpdate.bin. The kernels are only compatible for that CPU. The application layer is compatible for the usi8581a and the uis7862(s)
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 (or uis8581a) supplier to my FYT uis7862 unit (or 8581a)?
NOT directly, but with some tweaks: Yes. Read post #2 carefully and especially section VIII. Note that you cannot flash a uis7862 kernel to a ui8581a and vice versa.
Q7: Can I flash the MCU firmware from another FYT uis7862/uis8581a to my uis78962/uis8581a 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:
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).
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?
uis7862: 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.
uis8581a: Copy the lsec6316update 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?
BinaryUnitScriptlsec6315updateuis7862 (ums512)7862lsec.shlsec6316updatesc9863a (uis8581a)8581lsec.shlsec6521updatesc9853ilsec.shlsec6523updatesc7731 (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.
Q25: How do I change the ringtone (and/or thereby lower it in volume) on these 7862(s) and uis8581a (sc9863) units?
See post #1951 on how to do this. (This is an absolute shameless copy of a 4pda post by tyuktha and Monkey_D_Luffy. All credits go to them.)
Q26: How do I make a screenshot (instead of a reflecting, not so good and not always sharp, smartphone photo).
Drag down the status bar at the top of your screen.
Drag it a second time further down.
In the top right you will find a scissors icon.
This scissors icon can be used to make a screenshot.
Your screenshot will be saved in "Pictures/screenshots" on your internal memory.
==================================================
(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 that 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.
Joying now also wrote an online manual on the JOYING FACTORY SETTING USER MANUAL and the JOYING STEREO SETTING USER MANUAL.
SETTINGSWLAN
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 (Strange Chinese translation: (Dis)Allow display of video during driving . It means when handbrake is not used.)
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 in reverse gear, does 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 ( When car is put in reverse gear, it will show the reverse camera or an image with edges of your parking sensors (if you have them))
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 (Change how far the parking lines curve. This to adjust it correctly to your camer/car)
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.
Disable airconditions app on Tesla style uis7862/8581a units.
Last revised: 28 May 2023.
More about Firmware(s)This post is valid for FYT uis7862(s) (ums512) and uis8581a (sc9863) units running Android 10 or fake Android 11 or 12.
Contents of a firmware zip:
Note that the firmwares for the uis7862 and the uis8581a only differ on the flashing binary and the kernel zip. Configuration files are the same. Some resellers deliver a firmware that contain two kernel zips and two flashing binaries, as the flashing binary will only work on the hardware it is intended for flashing the correct kernel zip.
Kernel:
6315_1.zip: the kernel zip for the uis7862(s).
6316_1.zip: the kernel zip for the uis8581a.
The 6315_1.zip or 6316_1.zip 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 for the uis7862 "should" be interchangeable between all 800x480, 1024x600 and 1280x720 models. The same for the 6316_1.zip for the uis8581a. Special resolutions come with specific lcdconfig.txt files.
The binaries that do the flashing of the firmware:
lsec6315update for the uis7862(s)
lsec6316update for the uis8581a.
These are the binaries that do the flashing of the firmware, optionally install a boot image or boot animation, optionally run scrips from the lsec_update folder after the flashing process itself has finished. These binaries can also be used to only flash a boot image, boot animation, or run scripts.
AllAppUpdate.bin: Special zip 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 or use the scripts from post #3, bullet #4.
config.txt: file comparible to the build.prop which can contain additional properties.
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. These are very limited cross-compatible. do not flash these if your do not know exactly what you are doing.
I. (Factory) Firmwares
Mekede Software Download Previous: Mekede Support site
Joying
T'eyes: CC3 | SPRO | CC2+ | General/All
Sinosmart (approx. April 2023)
(Please share official (!) download links for other resellers so I can add them here).
* Modded Firmwares:
Mario Dantas' modded firmware (MD-Edition). (This is an optimized kernel, not a complete firmware.)
See for compatibility 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. You see that we specify 0 from the rotation. This is because android is normally for portrait like screens. Our landscape models have a value ro.sf.swrotation=90 decrees as they are actually 90 degrees rotated. A Tesla style unit therefore is again 0 degrees and sometimes 180 degrees.
Code:
ro.product.locale = pt_BR
ro.sf.swrotation=0
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).
28-05-2023: I added two scripts in post #3 under bullet #4 to let you flash any AllAppUpdate.bin to your uis7862(s) or uis8581a unit.
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 or 6316_1.zip
Again: the 6315_1.zip is the kernel for the uis7862. The 6316_1.zip is the kernel for the uis8581a.
(Inside also "III-a. More details about the files inside the 6315_1.zip/6316_1.zip and how to decompress and unpack/"open" them" and "III-b. Recompress uncompressed images from the 6315_1.zip/6316_1.zip to squashfs format for small (!) and easy access. (Not for flashing.)")
The 6315_1.zip/6316_1.zip contains the "standard" Android software for this unit. This is more or less what every "plain vanilla" Android 10 release will contain, with hardware drivers and kernel modules, but 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 own 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. This 6316_1.zip is theoretically identical for all FYT uis8581a units. (DISCLAIMER: Experimenting with this falls under your own responsibility).
You can unzip the 6315_1.zip or 6316_1.zip and replace the boot.img (and root it) 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/6316_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/6316_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 and 6316_1.zip. Note that T'eyes does it slightly different.
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/lsec6316update binary and 7862lsec.sh/8581lsec.sh script (and what about "universal" scripts)
The flashing process consists of a number of steps:
flashing the core/kernel software (6315_1.zip for uis7862(s) and 6316_1.zip for the uis8581a)
flashing the unit applicable apps and libraries plus initial properties (AllAppUpdate.bin)
scripts that do "post flash" activities.
The "flashing" executable/binary also starting the scripts, is the lsec6315update file on a uis7862(s) and lsec6316update file on a uis8581a.
A USB-stick used to execute a script on a uis7862(s) or a uis8581a should contain:
Code:
lsec6315update (uis7862(s))
lsec_update/7862lsec.sh (uis7862(s))
lsec6316update (uis8581a)
lsec_update/8581alsec.sh (uis8581a)
"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 on a uis7862 or use the 8581alsec.sh script on a uis8581a. Note: 99.9% of the time these scripts are identical as you work on the application layer.
Flash a new config.txt to your unit: Simply copy your modified config.txt and the lsec6315update or lsec6316update 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(s_ units. The same is valid for the 6316_1.zip for usi8581a 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?
You could take the 6315_1.zip (of 6316_1.zip for a usi8581a) 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
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 (or the lsec6316update for a usi8581a).
In case of questions, always ask.
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)
Mods and Tweaks
==================================================================================
1. disable or (re-)enable the mediaplayer at startup/wakeup.FYT mimics the behaviour of many builtin car units that it continues with the player or radio or BT connected phone player, that was active during "switch off". These 2 scripts can disable that behaviour (I want silence when I start my car) or enable it again (default FYT behaviour). This is a shameless copy of @gordgelin scripts with a slight modification where @gordgelin adds the command at the 16th line whereas most standard firmwares have max 8 lines or so. My script simply adds the line to 4th line of config.txt. Works on uis7862 (ums512), sc9863a (uis8581a) and sc9853i (could easily be ported to other FYT units as well).
==================================================================================
2. Script to correct the fytmanufacturer id in the fyt.propIn case you get a big yellow bar with red letters in the top of screen saying "UI and MCU does not match", your fytmanufacturer id (ro.build.fytmanufacturer= XY) is incorrect.. (See also Q13/A in post 1 and section II. and vI. in post 2.
If you still know the original id, you can use this script to correct that entry again without completely reflashing your unit.
Read the README.txt carefully !!
You can download this script: ChangeFytmanufacturer
==================================================================================
3. Script to correct the screen orientation of your unit.Probably you are here because you did not read the Forum well enough (especially "VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller" in post #2 and flashed a firmware to your FYT with a different screen orientation.
What does this script do?
It can set the correct orientation for your screen. This is set by a property called "ro.sf.swrotation=xy", where xy is a value of 0, 90, 180 or 270 . Use the value from YOUR ORIGINAL firmware in the config.txt.
You will find a config.txt with this script that contains the default value for most units being ro.sf.swrotation=90
In case you have no longer your original firmware you simply need to experiment with the above values until you have the right one.
You can download this script: ro.sf.swrotation
==================================================================================
4. Two scripts to flash any FYT AllAppUpdate.bin to your unit.
EDIT: Some of the new Mekede M6Pro models and comparables from other resellers come with an lcdconfig for their 2000x1200 K screens. My scripts below do not take those files into account. I "think" that when you encounter an lcdconfig on the new downloaded firmware, you have to remove it and stick to the one installed on your unit.
What do these scripts do and how to use them
These scripts are for both the uis7862 (ums512) and for the UIS8581a (sc9863a).
The AllAppUpdate.bin, that contains the FYT application layer, is for both CPUs the same.
The scripts make a copy of your current config and use that to flash your unit using that config of your unit.
Some information to start with
FYT units do have an MCU and based on the type of manufacturer you can have a different MCU firmware. This MCU firmware is totally different from the normal downloadable firmware that you can get for your unit having new functionality, bugfixes, etcetera..
The Android layer is universal on FYTs but works slighly different for different MCUs.
How this Android layer should act on the underlaying MCU is determined by a property called ro.build.fytmanufacturer which can have several values.
A second and third property are the:
sys.fyt.bluetooth_type property which is normally 0 or 1, but on the new M6Pro/M6Plus models anything up to 7
ro.sf.swrotation. This property defines the screen orientation and is in 95% of the cases 90 (degrees), for Joyings often 270 and for Tesla screens (0 or 180).
These properties are in the fyt.prop file and in the config.txt file. These files are copied from your unit onto the usb-stick by the pre-flash script.
Important
BEFORE YOU FLASH ANYTHING TO YOUR UNIT, YOU FIRST NEED TO RUN THE "PRE-FLASH" SCRIPT !!
Steps to perform
Take a clean FAT32 formatted USB-stick (or a (micro-)SD-card in some USB reader/writer).
Copy the contents inside the "pre-flash" folder onto the USB-stick (not the pre-flash folder with contents, but the contents inside the pre-flash folder).
Insert it into your unit, let it reboot and go into recovery mode, and wait until the green message tells you that you can remove it again.
Delete the "lsec_updatesh" folder including contents on your USB-stick !
Make sure to keep the "myconfiguration" folder and check its contents: It must contain a config.txt and a fyt.prop. If correct: copy this myconfiguration also to a save place. You never know when you need a backup. If the folder does not contain those files or one of them, then don't continue but ask in the forum.
Copy the AllAppUpdate.bin that you downloaded somewhere onto the USB-stick.
Also flashing the 6315_1.zip or 6316_1.zip?
UIS7862: If you want to flash the kernel as well, copy the 6315_1.zip onto the USB-stick.
UIS8581a: If you want to flash the kernel as well, copy the 6316_1.zip onto the USB-stick.
Now copy the contents of the "flash" folder onto the USB-stick.
Check your "lsec_updatesh" folder. Do you now also have a "lsec_updatesh (1)" folder, or inside the "lsec_updatesh" folder something like a "7862 (1).sh"? It means that you did not delete the "lsec_updatesh" folder on the USB-stick, or that your file manager does not overwrite on copying. In this case: Redo step 4.
Copy (not move) the config.txt inside the "myconfiguration" folder into the root of the USB-stick.
You can now flash your unit using this USB-stick.
Remarks
If you are thinking of using this in combination with @mariodantas' kernel, you need to know what you do. Mario's kernel comes with its own scripts and fmc app. Of course you can combine this if you know what you do, but do not simply copy everything on top of each other on this USB-stick. Please keep it separate.
You can also combine it with PeaceOS, but also in this case @LLIyT_HuK's version comes with it's own scripts. So know what you do.
The flashing script uses "twipe_data" in its "updatecfg.txt". This will clear your settings and all 3rd party apps which you downloaded from the Play Store or sideloaded from other locations. You can disable that by putting a # in front of the twipe_data line, but that is your own responsibility.
Most newer firmwares nowadays come with an lsec script and a fyt_build.prop. This fyt_build.prop comes with a fake property to set Android to 11 or 12. I refuse to go with that absolutely incorrect and despicable behavior and I will not copy it.
Once you have made your pre-flash copy of your config, you can also use the flash script to copy any modified fyt.prop or config.txt to your unit without using an AllAppUpdate.bin.
You can download both scripts in one zip: flash_any_AllAppUpdate.zip
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 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!
appBackup 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.
Awesome, thanks very much, this is a great write-up already!
Better explanation I've seen
I updated the 2nd and 3rd post with some info and added some scripts.
Interesting.
I wonder now what is the use of the extra 2GB RAM in some units if the chips can only "see" 6GB MAX.
@surfer63 Thanks for all of your work! This is great!
Maybe now I can downgrade carlink or figure out a way to change the resolution because with the latest Joying update Carlink 2.0 is HUGE with android auto, it's stuck in 480p and I have the 1920 x 1200 screen.
j-5 said:
Interesting.
I wonder now what is the use of the extra 2GB RAM in some units if the chips can only "see" 6GB MAX.
Click to expand...
Click to collapse
The 6GB is indeed a setting also in the specsheet. I never understood that with 64bit chips. I know that the theoretical 16.8 million terabytes can't be used as we are currently limited to 8 terabytes due to cache and bus limits, but these units should easily address 8-16GB. I assume it was simply a builtin limit as they are actually for light embedded devices. How will you ever put so much memory in a phone, unit or even pc.
The 7862C is the latest version. Maybe that one is now limited to 8GB instead of 6GB
I updated post 2 (More about Firmware(s) and added a paragraph VIII: Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller
In case of unclarities let me know.
barnesk9 said:
Maybe now I can downgrade carlink or figure out a way to change the resolution because with the latest Joying update Carlink 2.0 is HUGE with android auto, it's stuck in 480p and I have the 1920 x 1200 screen.
Click to expand...
Click to collapse
I haven't looked at the carlink app (why use Android auto if you have a full fledged unit in your car), but this sounds like they forgot to pack the hdpi resources into the app.
(Or they think: Which ***** uses Android Auto on one of these great full fledged 1900x1200 units? We will not even add the hdpi resources for such a unit . Using Android Auto in such a unit is like building a very old fm/am radio into a very expensive Tesla, Mercedes Maybach, BMW, etcetera)
surfer63 said:
I haven't looked at the carlink app (why use Android auto if you have a full fledged unit in your car), but this sounds like they forgot to pack the hdpi resources into the app.
(Or they think: Which ***** uses Android Auto on one of these great full fledged 1900x1200 units? We will not even add the hdpi resources for such a unit . Using Android Auto in such a unit is like building a very old fm/am radio into a very expensive Tesla, Mercedes Maybach, BMW, etcetera)
Click to expand...
Click to collapse
Wouldn't the resources be on the phone running Android Auto, not on the head unit running the receiver app. Said app would have to report the display resolution to accurately present the projection from the phone. And the main reason people would use Android Auto is because the interface is designed for safe use while driving and "glanceability" which the tablet layouts for apps like Maps and YouTube Music just don't provide. (The AA apps could do a helluva lot better, mind you)
Another reason might be they just think it looks pretty
Or perhaps they like to continue their music in their headphones once they've parked up and want minimal interruption in the soundtrack to their life, which is there to keep the demons and intrusive thoughts at bay. Maybe they have tinnitus like Baby Driver... My point is you never know with people.
DreadfulDrummer said:
Wouldn't the resources be on the phone running Android Auto, not on the head unit running the receiver app. Said app would have to report the display resolution to accurately present the projection from the phone.
Click to expand...
Click to collapse
I like your comments
Coming back to the above: The previous version displayed correctly.
And having AA perform so badly would immediately have resulted in a storm of AA bugs.
I therefore think it is the carlink 2 app. Somehow it is not reporting something correctly. And I agree with you: it is more logical to expect it doesn't report correctly to AA then that it's hdpi/xhdpi/xxhdpi resources are missing.
surfer63 said:
I like your comments
Coming back to the above: The previous version displayed correctly.
And having AA perform so badly would immediately have resulted in a storm of AA bugs.
I therefore think it is the carlink 2 app. Somehow it is not reporting something correctly. And I agree with you: it is more logical to expect it doesn't report correctly to AA then that it's hdpi/xhdpi/xxhdpi resources are missing.
Click to expand...
Click to collapse
Hey man,
I'm just making my way through the OP. Loving all the info (even if it is a bit of an overload of such you always provide, my dude) particularly the link to Mekede's firmwares. I've had no luck getting the seller to cooperate and send me even the currently installed firmware on my unit. However, I have a K200S, for which there doesn't seem to be any firmware. The page advertises a K-series unit up top, with the knobs below the capacitive buttons either side, but there appears to be no downloads for these units. It seems the M200S runs identical software but I don't want to flash the wrong stuff and gimp my knobs
All I'm really looking to do for the moment is change sys.fyt.bluetooth_type
Can this be done without the firmware?
Cheers
DreadfulDrummer said:
Hey man,
I'm just making my way through the OP. Loving all the info (even if it is a bit of an overload of such you always provide, my dude) particularly the link to Mekede's firmwares. I've had no luck getting the seller to cooperate and send me even the currently installed firmware on my unit. However, I have a K200S, for which there doesn't seem to be any firmware. The page advertises a K-series unit up top, with the knobs below the capacitive buttons either side, but there appears to be no downloads for these units. It seems the M200S runs identical software but I don't want to flash the wrong stuff and gimp my knobs
All I'm really looking to do for the moment is change sys.fyt.bluetooth_type
Can this be done without the firmware?
Cheers
Click to expand...
Click to collapse
I've just seen your instructions on where config.txt is located on the device
I'd always thought it had to be extracted from the firmware! So a simple script could be made to change that 1 to a 0, right?
Any help achieving that would be appreciated, if I could be pointed in the right direction (never made such a script before)
Thanks again, @surfer63
Alright, last one, I swear!
Flash a new config.txt to your unit: Simply copy your modified config.txt and the lsec7862update binary onto a clean USB-stick.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
The "flashing" executable/binary also starting the scripts, is the lsec6315update file on a uis7862
Click to expand...
Click to collapse
My unit is uis8581a2h10. Do I need a different binary?
I've found your Replace_configtxt.zip which contains three different binaries and three different scripts, one of which is 8581lsec.sh so I'm guessing I could use that.
Is /storage/sdcard1 in that script referencing the USB drive on which the modified config.txt and binary would be placed or should I modify that?
Sorry for all the questions (but hey, that's why we're all here, right?)
Also, I'm in New Zealand so apologies if you wake up in the morning inundated with DumbandDummer replied/mentioned/quoted you notifications. I'm trying!
Thanks again
DreadfulDrummer said:
Is /storage/sdcard1 in that script referencing the USB drive on which the modified config.txt and binary would be placed or should I modify that?
Click to expand...
Click to collapse
That was a very short brain disfunction.
You can flash a new config.txt to your unit by only copying that config.txt and, in your case, the lsec6316update binary onto a clean USB-stick. That is enough.
See my newly added Q17 in the post #1 Q&A about the binaries and scripts. And I mentioned flashing the config.txt in post #2 VIII.
surfer63 said:
That was a very short brain disfunction.
You can flash a new config.txt to your unit by only copying that config.txt and, in your case, the lsec6316update binary onto a clean USB-stick. That is enough.
See my newly added Q17 in the post #1 Q&A about the binaries and scripts. And I mentioned flashing the config.txt in post #2 VIII.
Click to expand...
Click to collapse
D'oh! Completely missed that handy table in Q17. Good stuff; well organized. I just got excited and tripped up on all the new incoming knowledge.
So only the lsec6316update and config.txt? No need for 8581lsec.sh?
DreadfulDrummer said:
D'oh! Completely missed that handy table in Q17. Good stuff; well organized. I just got excited and tripped up on all the new incoming knowledge.
So only the lsec6316update and config.txt? No need for 8581lsec.sh?
Click to expand...
Click to collapse
Correct.
And I added that table this morning after your question I had already posted it somewhere else but couldn't remember where (I guess I post too much).