yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
On the Sofia on Android 5.11 and 6.0.1 we had a person called Treel. He made a BT mod that could pair "everything". He wrote the "pair all" code in java, compiled that, decompiled it into smali and then fitted it somehow into the BT app and recompiled it. I never understood how he did it.

So yes, it should be possible but I don't have a mod for you and I can't make it either.

Sorry, but I will not create a video. Creating a mod is different everytime. The decompile and recompile is always the same, but that is one command for each: simple as that.

The modding itself is different everytime and especially if the code is obfuscated in the 8.1 apks, compiled with sdk 27+.

Also: I am a linux user and only use Linux to do "these kind of things", and I guess you are a Windows user.
[FYT Android Head Units] Soiski71:
I have been know to dabble different platforms ;)

1st trials successful on creating own versions based on your mods. Thank you for them!

For the Radio Mods (https://hvdwolf.github.io/Joying-RootAssistant/RadioMods-examples.html), how would one start to build anything like that for the 8.1 version and yúse your update method to import them?

I think this is still the far most used screen (at least for me) and would really like to touch up the graphics on it. Any pointing of direction with this item.

Thanks, Sami
[FYT Android Head Units] surfer63:
This is a howto I wrote for the android 5.1.1/6.01 radio mods.

Although outdated 80-90% is still valid. There is an 8.1 radio mod (my mod) which you can find here (both mods are identical, but for naming convention on the sc9853i use the 190043001_com.syu.radio.apk). You can have a look at that one and compare it with the original (here).
[FYT Android Head Units] Soiski71:
Thank you for path. Next hobby of mine :)

Is there a way to see the modded layout somehow ( like in emulator etc) how the new "raw/radio_ui.json". / "radio_ui.json" would draw or does it need to be done via compiling, installing ( aaand finding error...:D) and going it through again.
[FYT Android Head Units] surfer63:
You do need the compiling (or zip again if you only replaced images), but you can test it in any emulator. Simply set the resolution of the emulator to 1024x600 or 1280x720 and test. Of course you can't "access" the radio hardware and the related functions, but you can see where your controls come. Final test is on your unit (and again ... maybe)
[FYT Android Head Units] Hammerhand.17:
I posted it already in Poweramp forum, but it I understood it well A12 limits are not yet imposed.

Even there, it has an option called "legacy file access" to use previous method, but in our units is disabled because it uses this method by default.

I will post your message, though.

I had thought about this issue: why every app asks about access permission but this one doesn't, even when it's specifically for that? But don't know how to solve it
[FYT Android Head Units] joekingcool:
I'm trying this on my hizpo hu. Android 12. I can't get Telcom to install. Other 2 apps installed ok. If I try to manual dail with mct sailer app it says closes app. Any suggestions?
[FYT Android Head Units] seumina:
i have sc7731e fyt1 unit. i want to update only config.txt file.

what should i do?
[FYT Android Head Units] surfer63:
Just put the lsec6521update binary and your modified config.txt on an empty usb-stick
[FYT Android Head Units] seumina:
thanks
[FYT Android Head Units] seumina:
UIS8141e - sp7731e_1h10_native how to root. i dont have rom. Seller does not give support or any file
[FYT Android Head Units] surfer63:
This thread is specifically about "modding ... without root". If you want to root, search for the rooting threads.
[FYT Android Head Units] pir8man:
RE: Post#228

I cannot get hosts_add_blocker.zip to function.

I get a permission error mounting /system as rw.

using: lsec6315update and 7862lsec.sh from inside the zip.

on UIS7862 FYT device running 12-09-2022 kernel (MD Edition from Mario Dantes).

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

not sure if this is because of newer lsec6315update v7.82, or ???

I cannot use lsec6315update v6.32 as it refuses to run when it sees the newer kernel.
[FYT Android Head Units] mastrv:
Wrong thread. This is only for older model head units. These are not for newer models...won't work. Check thread for newer models.
[FYT Android Head Units] tarsonis666:
I read FYTStarter quite often in this thread but not once mentioned where to get it. No link here. Playstore doesnt have it. The author's profile does not have a thread for it. Can someone provide the app please?
[FYT Android Head Units] surfer63:
This thread, post #1, QA #8

This thread, post #1, QA19

Search better next time. It is even mentioned on more places.
[FYT Android Head Units] tarsonis666:
Thanks a lot. I wouldn't have found it under this threads to be honest.
[FYT Android Head Units] khiconit:
I got error when patch the laucher

Anyone can help me ?

I using SC 9853i 4GB RAM 32GB ROM

android 10
[FYT Android Head Units] surfer63:
Wrong thread. Sorry, correct thread ;)

What did you use to update.

Did you only patch the launcher apk? Or do you mean you flashed a new firmware?
[FYT Android Head Units] khiconit:
Hi,

I want to install the launcher and add some apk files to system.
[FYT Android Head Units] surfer63:
The launcher? Which launcher?

Did you read the first posts of this thread?

And you mention an error? You don't show us an error, only a successful flash.
[FYT Android Head Units] ducthang83:
I have a problem with editing software coming from CC3 October 29, 2020 for FYT devices that I didn't have before

Can you please help fix this error?

config file is the cause
[FYT Android Head Units] ducthang83:
Bạn đến từ Việt Nam phải không?
[FYT Android Head Units] khiconit:
Đúng rồi bạn ơi
[FYT Android Head Units] ducthang83:
you made in vietnam hai phong
[FYT Android Head Units] mashrom:
Hi I've SC9853i FYT HU and I've a problem with the original phone app. I can call through BT on 3G/4G with no problem, but it can't progress with any voip calls like Microsoft teams calls it just stops at the beginning of the call.

In my another car I have the newer version of FYT but on UIS7862 processor the app is working like a sharm with microsoft teams!

I flashed the dilar BT app from the new one on the old platformand it didn't help. I even flashed with another firmware from Joying and it didn't help either. Any advice on how to fix this issue please.
[FYT Android Head Units] fahrenhayt46:
hi

multimedia does not open after applying the update file.

how do i upload old files?
[FYT Android Head Units] mastrv:
This post you quoted was more than 2 years ago.

It was for an older model TEyes CC2. Is that what you have? Please post system details/photos.

This has nothing to do with "multimedia" and I'm not sure what you are referring to.

I'm not sure I can help you after so long a time.
[FYT Android Head Units] fahrenhayt46:
Hello again,

The system was restarted with the reset button. And now I can make calls with google assistant. :D

Thank you..
[FYT Android Head Units] athankani:
Do yo know the factory code ?
[FYT Android Head Units] surfer63:
3368
[FYT Android Head Units] jokerpzo:
@surfer63 i got same problem

do you have any update for this?

with new kernel (or any device newer than 12/09/2022), can not run command mount -o remount,rw /system

i already tried with su command before, but still fail :/
[FYT Android Head Units] surfer63:
This will not work on a 7862. You took the instructions for a sc9853i where you could indeed do this.

The uis7862 (and usi8581a) are on Android 10 and use the super partition structure which means that the system partition can't be mounted rw.

You must unpack the kernel, unpack the system partition, modify the system partition, expand it, repack the system partition and repack the kernel.

Or you take my optimized kernel which also comes with the ad blocking host file.
[FYT Android Head Units] jokerpzo:
thank for your answer :x
[FYT Android Head Units] ODIN679:
Hello,

I tried to use config.txt to change mic gain and some other settings, now mic sound is worse...

How can I reset the config.txt settings to default?
[FYT Android Head Units] surfer63:
Check your original config.txt
[FYT Android Head Units] ODIN679:
Where can I find it? Seen on the roms I use and its not present.... no I did not backup....
[FYT Android Head Units] surfer63:
Then simply use the same config.txt tart you modified, but now with the original values.
[FYT Android Head Units] ODIN679:
I used an empty config txt that I created with values found in this forum.

If I place an empty config.txt does it clear?
[FYT Android Head Units] surfer63:
No, don't do that.

Use below numbers.

persist.audio.mic.sensitivity=1

persist.btmic.gain=7

persist.btspk.gain=7
[FYT Android Head Units] ODIN679:
Thank you!!
[FYT Android Head Units] aimeriza:
I have a rooted sp9853i_1h10_vmm (ATOTO S8). Changed the launcher to AGAMA and everything worked as it should. Changed back to the launcher3 default by uninstalling agama and now my reverse camera doesn't activate the display to automatically switch to the rear cam app. I can only access the rear camera by manually opening the Rear camera app and then it will turn on once i put it in reverse (camera gets 12v). I think this is something to do with the "keep alive" settings but I have tried flashing AllAPK.pkg and reflashed successfully, short of completely reinstalling and deleting the entire unit, not sure what else to try. Properties.txt from FYT tool shows me this, maybe it will lend a clue. The unit has multiple input cables, the other one shows as "6" but the rear camera as NULL. Posting some of the outputs here but i have the full file available:

[ro.fyt.m_VideoIC]: [6]

[ro.fyt.m_back_VideoIC]: [NULLLL]

[ro.fyt.m_front_VideoIC]: [0]

[persist.sys.cam.3dnr]: [true]

[persist.sys.cam.arcsoft.filter]: [true]

[persist.sys.cam.ba.blur.version]: [6]

[persist.sys.cam.battery.flash]: [15]

[persist.sys.cam.beauty.fullfuc]: [false]

[persist.sys.cam.eois.dc.back]: [false]

[persist.sys.cam.eois.dc.front]: [false]

[persist.sys.cam.eois.dv.back]: [true]

[persist.sys.cam.eois.dv.front]: [false]

[persist.sys.cam.facebeauty.corp]: [2]

[persist.sys.cam.filter.highfps]: [true]

[persist.sys.cam.filter.version]: [2]

[persist.sys.cam.gif]: [false]

[persist.sys.cam.gps]: [true]

[persist.sys.cam.new.wideangle]: [true]

[persist.sys.cam.normalhdr]: [true]

[persist.sys.cam.photo.gallery]: [true]

[persist.sys.cam.pipviv]: [false]

[persist.sys.cam.refocus.enable]: [false]

[persist.sys.cam.scenery]: [false]

[persist.sys.cam.sfv.alter]: [true]

[persist.sys.cam.timestamp]: [false]

[persist.sys.cam.unfreeze_time]: [280]

[persist.sys.cam.vgesture]: [false]

[sys.fyt.back_video_ic]: [NULLLL]

[sys.fyt.bluetooth_type]: [1]

[sys.fyt.ec_version]: [6]

[sys.fyt.front_video_ic]: [TP2850]

[sys.fyt.platform]: [6521]

[sys.fyt.serialdebug]: [off]

[sys.fyt.subplatform]: [1]

[sys.fyt.upname]: [6521_1.zip]

[sys.fyt.video_ic]: [TP2850]
[FYT Android Head Units] surfer63:
Update of 2019-09-17-com_syu_ms-ORG_extended.zip

The unkillapp.txt inside the 190000000_com.syu.ms.apk contains the apks that are not getting killed upon sleep. The default Joying/FYT launchers are of course part of this list.

So I added the most commonly used launchers on the Joying units to this list as well (as of 9 December 2019 18:00 CET (17:00 GMT)).

Maybe some of the issues with these 3rd party launchers are because they also get killed every time.

(Note: these apps are of course not added to the nokill version as that one doesn't kill any app, so that would be useless)

# Several 3rd party launchers
ru.speedfire.flycontrolcenter #FCC Car launcher
com.iflytek.autofly #FCC voice plugin
altergames.carlauncher #AGAMA car launcher
com.autolauncher.motorcar.free #Car launcher free
com.autolauncher.motorcar #Car launcher pro
com.softartstudio.carwebguru #Car web guru launcher
gb.xxy.hr #Head unit reloaded
gb.xxy.trial #Head unit reloaded trial
com.teslacoilsw.launcher #Nova launcher
com.teslacoilsw.launcher.prime #Nova launcher prime
is.shortcut #Evie launcher

See post #3.
[FYT Android Head Units] Soiski71:
APK Compile error

Hi, I have now tested both in Windows and in Ubuntu the use of Apktool (2.4.1). On both the decompile works great but when trying to compile after graphics change) I get the same errors in Win and Ubuntu ( attached pictures). Can you see if you get the same problem on your side. ( I was using the modded version of your Radio).

Thanks and I do appreciate you not being my personal apktool helper ;)
[FYT Android Head Units] surfer63:
This sometimes occurs with new .webp images and sometimes with 9-patch images (the new resizable bitmap images).

You can see in the decompile step that you have an issue with 4 .webp files which apktool can not correctly handle.

S: Could not decode file, replacing by FALSE value: drawable-nodpi-v4/broadcast_list_ic_tab_pressed.9.webp
S: Could not decode file, replacing by FALSE value: drawable-nodpi-v4/my_radio_ic_tab_normal.9.webp
S: Could not decode file, replacing by FALSE value: drawable-nodpi-v4/my_radio_ic_tab_pressed.9.webp
S: Could not decode file, replacing by FALSE value: drawable-nodpi-v4/broadcast_list_ic_tab_normal.9.webp

They are replaced by 0-byte dummies (FALSE values). If you look inside "190043001_com.syu.radio/res/drawable-nodpi-v4", you will find:

0 dec 9 18:33 broadcast_list_ic_tab_normal.9.webp
0 dec 9 18:33 broadcast_list_ic_tab_pressed.9.webp
0 dec 9 18:33 my_radio_ic_tab_normal.9.webp
0 dec 9 18:33 my_radio_ic_tab_pressed.9.webp

What you now need to do is unzip the radio apk to some other folder. From this unzipped folder from the same "res/drawable-nodpi-v4" folder, you copy those 4 files back into your decompiled radio apk into "190043001_com.syu.radio/res/drawable-nodpi-v4".

Then you can recompile again.

Edit: I simply forgot about this and it is not in the HowTo as it did not occur on the old 5.1.1 and 6.0.1 apks.
[FYT Android Head Units] Soiski71:
APK Compile error

OK, yes. 4 Images unzipped and reintroduced into same folder, but still the error (Though slightly different).

Nothing else changed, just replace the 4 images back. As the error still referte to the same images Do I need to change something also in the refered xml file ?

E:\Apps\JOYING\190043001_com.syu.radio>apktool -c b e:/apps/Joying/190043001_com.syu.radio
-c/--copy-original has been deprecated. Removal planned for v2.5.0 (#2129)
I: Using Apktool 2.4.1
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether resources has changed...
I: Building resources...
W: e:\apps\Joying\190043001_com.syu.radio\res\values-nodpi-v4\drawables.xml:3: error: Resource entry broadcast_list_ic_tab_normal is already defined.
W: res\drawable-nodpi-v4\broadcast_list_ic_tab_normal.9.webp:0: Originally defined here.
W:
W: e:\apps\Joying\190043001_com.syu.radio\res\values-nodpi-v4\drawables.xml:4: error: Resource entry broadcast_list_ic_tab_pressed is already defined.
W: res\drawable-nodpi-v4\broadcast_list_ic_tab_pressed.9.webp:0: Originally defined here.
W:
W: e:\apps\Joying\190043001_com.syu.radio\res\values-nodpi-v4\drawables.xml:5: error: Resource entry my_radio_ic_tab_normal is already defined.
W: res\drawable-nodpi-v4\my_radio_ic_tab_normal.9.webp:0: Originally defined here.
W:
W: e:\apps\Joying\190043001_com.syu.radio\res\values-nodpi-v4\drawables.xml:6: error: Resource entry my_radio_ic_tab_pressed is already defined.
W: res\drawable-nodpi-v4\my_radio_ic_tab_pressed.9.webp:0: Originally defined here.
W:
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:\Users\samis\AppData\Local\Temp\brut_util_Jar_6019981112115378690.tmp, p, --forced-package-id, 127, --min-sdk-version, 8, --target-sdk-version, 21, --version-code, 1808080943, --version-name, 1.0, --no-version-vectors, -F, C:\Users\samis\AppData\Local\Temp\APKTOOL9190324829375612401.tmp, -e, C:\Users\samis\AppData\Local\Temp\APKTOOL6183192504824709941.tmp, -0, arsc, -I, C:\Users\samis\AppData\Local\apktool\framework\1.apk, -S, e:\apps\Joying\190043001_com.syu.radio\res, -M, e:\apps\Joying\190043001_com.syu.radio\AndroidManifest.xml]
[FYT Android Head Units] Soiski71:
APK Compile error ...contd.

Found out also that the 4 erroring file are in good shape in folder drawable-hdpi-v4 ( + additional other files) might this be confusing the compile some how...

Seems that the fix is to delete the folder values-nodpi-v4 and then recompile :)

I'm learning so much again and having fun :)
[FYT Android Head Units] surfer63:
Yes, the "e:\apps\Joying\190043001_com.syu.radio\res\values-nodpi-v4" including its contents, should be removed.

With the orginal images copied in, it should now work. I just tested myself.

Please note that the hdpi images might be different from the nodpi images. Those mdpi, hdpi, xhdpi, etc images are for a specific dpi. Do not simply copy those into the nodpi folder unless they are indeed equal.
[FYT Android Head Units] Soiski71:
APK Compile - signing docus ?

Just a question what process do you use to sign the documents ?
[FYT Android Head Units] surfer63:
If you used "apktool -c b", you do not need that as you have already resigned with the original signing (-c). Only separately sign if the modified apk does not work.

All apps are signed with the firmware signing. It is better to keep it like that for many reasons.

So if neccessary, you can use signapk just like with the rooting (look there for the files).

java -jar SignApkv2.jar testkey.x509.pem testkey.pk8 input.apk output.apk

On linux take care of uppercase/lowercase.
[FYT Android Head Units] gamer765:
Could you send me that mod? I might be able to replicate that mod for our devices. I'm pretty good at code injection in smali. I'm the author of the popular Pandora mod with built in downloader and tagger. I'll probably be able to shoehorn it in.
[FYT Android Head Units] surfer63:
Great. I will search "my archives" and send you a PM with the mods, some code and a (very) minimal explanation.
[FYT Android Head Units] surfer63:
I forgot that I can't add attachments to PMs.

However, :rolleyes: the attachments are too big. But I keep it now in this post for "the rest of the world".

the android studio files

https://drive.google.com/open?id=1mkTeTKhXfQL5o0CW3FQaifpUPl8-UqxE

for the old original apks (note: Android 5.1.1 or very early 6.0.1 apk)

https://drive.google.com/open?id=14V6CyQJhRNvf7lS8fHjWCCGP6i7uR8Yp

And the explanation from Treel:
[FYT Android Head Units] Soiski71:
APK signing with -C not working

Seems that -c option is not in use anymore in the newer versions ??

E:\Apps\JOYING>apktool -c b e:/apps/joying/190043001_com.syu.radio

-c/--copy-original has been deprecated. Removal planned for v2.5.0 (#2129)

I: Using Apktool 2.4.1

I: Checking whether sources has changed...

I: Checking whether resources has changed...

I: Copy original files...

I: Copy AndroidManifest.xml...

I: Copy META-INF...

I: Building apk file...

I: Copying unknown files/dir...

I: Built apk...

I'm going the long way and need to resign them ;9 What Apktool are you using ...does it work there ?
[FYT Android Head Units] gamer765:
Thanks for the files, I'm familiar with his method of compiling since thats what I used to do to compile my pandora mods. Ill take a look at it when time permits.

Edit: Taking a quick look at it during some down time at work, it's a lot of code, but from a quick readthrough some of the files, it looks like he implemented the entire bluetooth functionality into this test app so he conduct on device tests. I could be wrong, but thats just from a quick look. Good thing you included original and modified apk files, I can just decompile them and do a diff of the files and see which files were actually modified and roll my own brew. Good to have the source code too since reading smali is sometimes a b*tch.
[FYT Android Head Units] surfer63:
It did work. Deprecated does mean that they prefer you not to use it, and it will be removed in the next main version. For you it worked.
[FYT Android Head Units] gamer765:
Just a quick question, did anyone actually buy the OBD2 dongle from Joying? I'm reading through the stock bluetooth app and im taking a quick guess that the dongle they sell is made by "gooddriver". If you do have it, please post device info of the dongle. Makes it so much easier to debug.

Edit: Found the dongle being sold online by "gooddriver"

ELM327 OBDII
[FYT Android Head Units] thierry34:
i had buying mine on ebay for 3,99 euros this summer and it works very well !!!!

i didn't find the same now but for example :

https://www.ebay.fr/itm/OBD2-Super-...957127?hash=item4d9bd5ba47:g:lyIAAOSwkLBc8Pzj
[FYT Android Head Units] Soiski71:
But running the apk created with that phrase ( I agree it does not give any errors ), when trying to install it to BlueStacks emulator it gives error : " Apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES" hence I concluded that it does not work. If I run the same file through the ZipSigner then the apk installs it nicely.

I guess its mysteries that I will figure out one day :D
[FYT Android Head Units] gamer765:
When you pair the OBD dongle to your radio, what is the device name?
[FYT Android Head Units] thierry34:
i need to go to my car. i,ll tell you tomorrow ;);)
[FYT Android Head Units] yzf750:
Save your money and buy it Amazon, exact same one Joying is selling for 6 dollars less.(13.99 vs 20.00)

https://www.amazon.com/obdator-Blue...r_1_1?keywords=elm+mini&qid=1576129354&sr=8-1
[FYT Android Head Units] gamer765:
Ok, so im making some progress in understanding whats going on with the mod, was having trouble at first since I didn't have complete files, its a pretty big mod, lots of stuff was cut and other stuff added. This is going to take me a few days. It is currently almost 2am here on my end of the world. I can probably finish this on my days off.
[FYT Android Head Units] surfer63:
Don hurry, take your time. Everyone is curious, but you're the only one doing it. So everyone simply has to wait.
[FYT Android Head Units] thierry34:
DTVbluetooth. It's the name i have
[FYT Android Head Units] gamer765:
Thanks, forgot to mention though that the Bluetooth name check was kinda irrelevant after reading into the code some more. I've already decompiled the APK back to its Java code and have started to write in my own skeleton code. No ETA as of yet and no clue if it'll work anyways. I'm thinking it will since there doesn't appear to be much difference in the classes going from 6.0.1 to 8.1.0

Update: Finished writing my code, now injecting it into the stock app and will test.
[FYT Android Head Units] gamer765:
[MENTION=2550900]surfer63[/MENTION], can you pack this into an apk for me? I'm having trouble packing the resources. Needed to decode resources to modify AndroidManifest.xml. The classes.dex file is in the zip. Im going to sleep now. Havent been able to test. Would love to hear some feedback.
[FYT Android Head Units] mclaudio:
Hello to all

I am getting error downloading updates. How can I identify the url where the update is coming? Thank you very much

---------- Post added at 11:14 AM ---------- Previous post was at 11:08 AM ----------

http://imgur.com/gallery/i4rgVcm
[FYT Android Head Units] Soiski71:
New Radio skin for 8.10

Finaly,

It took a while as "everything" was new for me. Thanks to Surfer63 for his patience with my questions.

I had problems on using the original signing of the file so reverted to ZipSigner software. Hopefully it works for you.

On my unit you just need to install the APK to get the new skin, not other upadats required.

Comments much appreciated!
[FYT Android Head Units] mclaudio:
Hi. Does it show RDS messages?

Enviado do meu SM-N975F através do Tapatalk