[FYT Android Head Units] surfer63:
Quite some fyt settings are stored as properties. And most of these are stored like *fyt* properties, so if you do a

getprop | grep -i fyt

you will see quite some settings.

However, some are stored as *sys* properties, like for example the navi app -> persist.sys.navi.packagename

(or use my HWGet_info.apk and search through the properties.txt to find the relevant ones)

If you are root you can easily change these settings yourself.

Another location of the settings is in /sys/fytver.

Below a list of config files in that folder (proudly stolen from the HWGetinfo from [MENTION=10130634]faisaljed18[/MENTION] who used the HWGetinfo.apk as I do not have a SC9853i). Note that some files are kept open when using the unit, so you can't modify them. Next to that: you need to be absolutely rooted to change them. 90% of the files are identical over the Sofias/PX5s and SC9853i FYT units, but of course there are differences.

I can't share info on contents for your new side panel settings as I do not have that on my PX5

Gpios
TurnOffLcdc
acc_on
airplane_mode
appplatform
audio_type_name
backcar_mirror
backlightctrl
bl_en
bluetooth
boardtype
boot_flags
cfg_position
colorled
current_limit_gpio
dvd_sys_mode
encryption
fan_en
fm_type_name
fyt_bin_version
fyt_car_reverse
fyt_tw9992_pwr_rst
fyt_uuid
fyt_video_err
gamma
gps_pwren
gps_rst
led
little_hom
mute3702
muteAMP
platform
platform_info
reset8288
resetGPS
rotation
setlcd
sound8288
sound_effect_ic_reset
sound_mix
sql_platform
sqlbtmode
subplatform
touchdebug
video_control_position
video_ntsc_pal
video_position
video_rotation
video_signal
video_vertical
zygotetrace

Edit: On the older panels you only had a number of limited colors: "a b c d e f g h"

You could easily change these with, for example:

echo -n "a" > /sys/fytver/colorled

---------- Post added at 12:49 PM ---------- Previous post was at 11:53 AM ----------

I do not know whether your tried jadx-gui or something like that, because in that case it will never work to recompile it. You need apktool (perhaps in combination with jadx-gui to find the code and put that in the smali code).

If you decompile a system signed apk with apktool, you also need the framework-res.apk from /system/framework.

So copy that to your computer as it is needed, and note that it is firmware version dependent.

Do

apktool if <path_to>/framework-res.apk

Then do the

apktool -d <apk>

and when done do

apktool -c b <apk>

. You need the "-c" to use the original signing.

And with regard to moronic programming: There are lots and lots of examples of that. Some is based on old android frameworks and code and simply "fixed" to make it work again, instead of rewriting it using the correct framework/code. Some is targeted at compilation for SDK 4.2 level, because otherwise it won't work when using a newer Android SDK version level, etc. etc. Their screen layouts are originally based on Swing for pc and not Android layout. They have written their own translation code, instead of switching to Android layouts which give you so much more flexibility (and removing the need to compile different firmwares for different resolutions).

And still it works most of the times :) But it also makes it sometimes very hard for themselves to bug track things.