yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
When it comes to replacing apks, JET can only fully function on a rooted unit. There are some "non intrusive" functions that also work on non-rooted units, but that won't help you here.

As described in post #1 and post #2, you can create your own Allapp.pkg, also with a modded apk, but there is one big naming issue to take into account!

The radio app on your Sinosmart is called "190042001_com.syu.radio.apk". The one on real Joyings is called "190043001_com.syu.radio.apk". They are exactly the same but have a different name. If you simply flash one next to the other, both will not work anymore as both have the same internal package name being "com.syu.radio". So if it doesn't work you have no radio at all.

I will add an example to post #2 how to do this, as it is really nothing more then simply renaming the apk and then do the exact same steps, but it can be vital to do that.

I will post a remark when I have the example ready.

_____________________________________________________________________

EDIT: I added an example (3) to post #2 of this thread on how to flash a Joying modded app to your FYT compatible. And to be complete: Read post #1, #2 and #3 before asking possibly unnecessary questions.
[FYT Android Head Units] surfer63:
I created a small and really quick & dirty (and unsharp, sorry) video on Youtube to show what scrolls on your screen when flashing such a mini Allapp.pkg.

See here: https://youtu.be/VV_EpYShesM

I also added that Youtube link to post #2 of this thread.

Like said: it is quick and dirty but I do not want to spend more time on it.
[FYT Android Head Units] acidikjuice:
Thank you for sharing this method. I was able to easily update the radio and apply the extended lists of apps you provided in the first post. I was also able to update from September to December firmware with this method.

I would like to update the skipkillapp.prop to test some other apps. How can I do this? I was able to extract and pack a small Allapps.pkg like your examples. However, I can't find skipkillapp.prop. I attempted to extract Allapps from the stock Joying firmware, but it never finishes. Is that normal?

Can I make a new skipkillapp.prop, place it in the Allapps directory, pack that and flash it just like that? Can someone post a complete skipkillapp.prop file (I did not see on github, sorry if I missed it but would appreciate a link).
[FYT Android Head Units] surfer63:
This is the new way to do that on the SC9853i models, but I still do not know if I am successful myself. User [MENTION=3558292]thierry34[/MENTION] has also experimented with it, but did not have good result. I asked him to check some data, but never heard back from him.

I mostly use Magic Earth as navi app. Sometimes it is still there after deep sleep and sometimes it is not. I do not understand yet why that happens.

See attached my skipkillapp.prop
[FYT Android Head Units] thierry34:
sorry if i didn't give you feedback. i modified my skipkillapp files with differents apps with -11 or -12 (tpms ,tasker and other) but it didn't work well. i changed option, i installed FYT starter and FYT startersetup and selected 4 apps.(tpms,DVR, torque and Neutron). it works,but ,when i turn on car, unit open 1 or 2 or 3 apps, never do the same. one time tpms ,dvr and torque, other time dvr and neutron, other time only one apps... it's never regular.

i would like that when i turn on unit, the 4 apps will open.

i have a question, i modified the skipkillapp files. i update the firmware with 28/11 firmware. when i flashed the firmware, skipkillap file was return to original file or not ? idem for the allapp file.
[FYT Android Head Units] surfer63:
If you flash a full Allap.pkg, everything will be overwritten including the skipkillapp. If you open the full Allapp of 28-11, modify the skipkillapp and repack the Allapp.pkg, you get a full flash with your skipkillapp. That is also what I did but with uncertain success.

Like mentioned: Sometimes magic earth (which I use as navi app) is still there after deep sleep and sometimes not. It is very confusing (and annoying).

What some people do:

- Assign Tasker / Macro Droid / Easer, or some other "automation" app to the Navi app setting.

- Auto open the Navi app (=> your automation app)

- Let your automation app start other app(s) (trigger: automation app fully opened/initialised; action: open one or more apps)

This method has been posted by several users as a succesful approach. Of course you will sacrifice your navi app coupling.

And still another option to try if fytstarter gives uncertain results:

- Let FYT starter (only) start your automation app

- Let your automation app start other app(s) (trigger: automation app fully opened/initialised; action: open one or more apps)
[FYT Android Head Units] thierry34:
i modified the 2 files before flashed the 28/11 firmware. Now, after flashed the 28/11 firmware , i have the original allap ans skipkillap files in my unit ? isn't it ?

i'll test the automation option like you said.
[FYT Android Head Units] surfer63:
That was my question to you in the first place :) : If you use a file manager or a terminal and go into /oem/app, you will find the skipkillapp.prop. You can easily see if it has your changes or not.

Mine had my changes.
[FYT Android Head Units] thierry34:
ahhhh !! ok lol !!! i'll see that tomorrow ! thanks
[FYT Android Head Units] thierry34:
After updating 28/11 firmware, skipkillap. Prop file was original file.

I vérified this morning
[FYT Android Head Units] gamer765:
So... I've been in talks with joying the past few weeks. I've bought a few additional units for some of my other vehicles. I've also tried requesting some source code for the com.syu.bt app but have constantly hit a hard wall. They keep saying they don't have any source, and honestly, after going through the decompiled code, I believe them. The code is pretty generic and pretty messed up. There's switch statements everywhere covering all different kinds of cases ranging from different kinds of hardware, to different kinds of vendors. I believe the only say that joying has, is regarding to the skin and a few customizable options, which is all set up in the AndroidManifest.xml file. If you happen to have a Sofia unit, the code is in there and porting the bt mod should be no problem. For our unit, it seems the bt pairing code runs deeper and spans across multiple classes, again, behind switch conditionals.

Edit: Check this out, i sourced a com.syu.bt from another OEM/reseller and check out the signatures on the apk compared to the one on our Joying units. Both signatures are the same despite being different "brands"
[FYT Android Head Units] acidikjuice:
Has anyone posted a no-kill config and/or rooted boot image for the Joying December update (2019-12-22)?

I don't know how to make a no kill version, I assume Surfer63 can make it? Is the instructions for this posted somewhere?

I do understand how to patch the image myself for root but the ApkPack software (for whatever reason) never succeeds at unpacking the stock Allapps.pkg (I can unpack and pack smaller files, so something is up with my system). If someone could please post the stock boot image for 2019-12-22, i'd gladly post back the root version.

PS: reason for root: restart accessibility services after deep sleep
[FYT Android Head Units] surfer63:
Where did you find this update? The latest one I can find is the 2019-11-28 version
[FYT Android Head Units] acidikjuice:
I'm sorry, I didn't find anything. I'm on 11-28. I got confused because my APP version says 2019-12-22. What is up with that? Anyways, sorry for the confusion. Nothing to see here (except my screen shots)!

Is the APP version updated when we alter the image or something?
[FYT Android Head Units] surfer63:
You have been busy I see, but I guess you do not have a working BT mod yet.

W.r.t. Joying: I'm absolutely convinced they do not have the source code. Joying is a reseller of FYT units with FYT software and do not even have developers even though they say "our developer ...". I once confronted them really hard with this as I had several fixes and asked them (already knowing the answer): "Why is your developer not simply adding my fixes to your apks?". Then they admitted they are also dependent on and bound to their supplier, being FYT.

As China is the country of "copy what you can copy", I think FYT also keeps there source code completely to themselves.

And that you find a com.syu.bt that is exactly the same as the Joying one, doesn't surprise me either. I only repeat it: China is the country of "copy what you can copy" :). That is also internally in China.

(And off-topic: In China most of MS Office is illegal and they finally allowed upgrading to Win10 for all users as more than 75% of all Windows versions in China is illegal. Like Bill Gates said for China: "It's easier for our software to compete with Linux when there's piracy than when there's not. Are you kidding? You can get the real thing, and you get the same price.". So Microsoft gave up on piracy in China. It is a big shame.

and that's from me, a long-time Linux user)
[FYT Android Head Units] gamer765:
Alright, I think I got it, it was actually easier than I thought. I just kept tracing the error logs to see where they get called from until I reached the place where the connection magic happens. I tested by connecting a Bluetooth speaker to the radio, it says pairing successful but it doesn't route audio to it, but I'm not surprised considering the radio is not really expecting it. I'll try a ps4 controller tomorrow.
[FYT Android Head Units] blinger:
How did you go with the PS controller?
[FYT Android Head Units] AnzacExodus:
Yeah how are you going with the Bluetooth Gamer?
[FYT Android Head Units] ojuniour:
yoo share the apk whenever possible please.. I'm trying to connect to led bluetooth and other bluetooth devices...

Thanks
[FYT Android Head Units] mashrom:
Hi,

I'm using poweramp for audio player instead of the stock one. Next track from car switch works only if the app is onscreen. However, if poweramp is on the back ground ie minimized, it doesn't work. Stock app works either ways. Is they a solution that I can get it work while minimized?

Note: the HU is rooted and it is ZHAN platfrom

Thanks!
[FYT Android Head Units] mastrv:
Hi all. I have another Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i model, the Teyes SPro 4/64 version. I've been reading about this similar Joying model through several threads here. It sounds like many of the things that apply to one of these models may apply to others.

Here's one tidbit that I found in another site. Can make things easier to customize or to perform, especially for those that can't do some things themselves. Foe example, deleting a file without root.

The following talks about the ability to have shell scripts as part of the regular flashing process. Post says the script is launched at the end of the flashing process. I haven't tried this myself and cannot verify whether this is correct or not, but I have no reason to doubt it.

The remainder of this post is cut and paste from the other site:

1) Create the folder lsec_updatesh in the root of the flash drive .

2) Put the file in this folder lsec.sh , which is a shell-script.

3) Do not forget to put our favorite lsec6521update file in the root of the flash drive .

Result - at the end of the flashing, the lsec.sh script will be executed.

Notes:

- the script is executed with root-rights, the command is issued from the root of the file system ( / );

- the PATH variable is set like this: /sbin:/system/bin:/vendor/bin

- during the execution of the script, the path to the root of the flash drive is interpreted as /storage/sdcard1;

- before running the script, the main file systems are mounted on the "read-write" to their regular folders (/cache, /system, /data, /vendor, /oem, /lsecfs), so you do not need to write additional mount commands;

- in the header of the script you need to specify the interpreter - #!/system/bin/sh;

- setting variables is not supported (and I can not understand why);

- pseudo-variables (for example, $(pwd) , $(mount) , etc.) are supported;

- technically, the script run can be combined with the main or partial firmware (6521_1.zip, Allapp.pkg), or separately, with combined use, the script is run after 6521_1.zip and Allapp.pkg.

Practical application: making patches, an alternative to creating the Allapp.pkg package . Plus, unlike Allapp.pkg, it is possible to work with all file systems and folders, as well as delete unnecessary files.

An example of a script that implements the replacement of the Settings.apk application with an analogue that originally lies in the app folder on a USB flash drive and has a file name different from the original:

#!/system/bin/sh
#
rm -rf /oem/priv-app/Settings
rm -f /data/dalvik-cache/x86_64/oem@priv-app@Settings@Settings.apk@classes.*
mkdir -p /oem/app/NewSettings
cp -rf /storage/sdcard1/app/NewSettings.apk /oem/priv-app/NewSettings/
chown -R 0.0 /oem/priv-app/NewSettings/NewSettings.apk
chmod 0755 /oem/priv-app/NewSettings
chmod 0644 /oem/priv-app/NewSettings/NewSettings.apk
[FYT Android Head Units] mastrv:
Possible alternative to FYTStarter.

While going through setting up my new head unit, TEyes SPro which is similar to Joying SC9853i, I was trying to figure out how to put a lock screen that required a password of some kind. I succeeded, to my satisfaction, and will post that later. However, while doing that I found that I needed some way to start the lock screen. Here's what I found after looking at FYTStarter:

There are some Android apps that will provide a way to see more of the standard setting options. Seeing all settings is important and by default, the TEyes firmware is a modified settings app which only shows some settings. Tried these apps and they worked to show all settings...however not needed.

I later installed CarWebGuru (CWG) and decided to use it as my default home app/launcher

I also found that CWG has a method to show all settings without having to install any other applications found in 1st point. CWG has a settings button/icon to access the CWG settings. If you keep that icon pressed, the complete settings will be displayed...no need for another app.

Some text is blacked out while others are not.

Some may or may not be accessible.

I have not tried or tested all of them...this is only about apps to start at boot.

Follow these steps to get to the right place:

Select "Battery", which is visible.

Scroll down to "Auto launch management" which is darkened found under a heading "App Battery Settings" which is visible. Two options are found that are both darkened: "App Auto Launch" and "App Secondary Launch".

Select "App Auto Launch" and a list of all installed apps, I believe, are shown with darkened text. Each app has a toggle to determine which apps will launch on a cold boot.

Turn toggle on for those apps to start automatically at boot.

Now this doesn't have any ordering or scheduling or delays possible and this may not start the apps at the time you expect. However, this is a good option for a basic setup or to start a more complex setup where Tasker or Macrodroid or something like that starts and then controls other activities.

I'm not sure what the difference is between "App Auto Launch" and "App Secondary Launch" and what "App Secondary Launch" specifically does.

I used the above to start the lock screen successfully on boot, which is all that I was really looking for at this time.
[FYT Android Head Units] surfer63:
Thanks for sharing this. I will test.

Where did you find this? on 4pda?

You everywhere specify spaces between commands/paths, like "#! / system / bin / sh;"

Is this part of the syntax, or just coincidental?

I can imagine they have a very reduced (non-Posix) shell interpreter in the recovery partition, which only supports a very limited set of commands/variables/etc.
[FYT Android Head Units] surfer63:
This is indeed at cold boot. The Joying units have "deep sleep". It meens they 90% of the time do not cold boot but "wake up". Before going into deep sleep almost all apps are killed. There is no "boot completed" event after coming out of deep sleep so, CWG will not be triggered to start the apps.

FYTStarter is triggered as an (Joying wake up after deep sleep) app when coming out of deep sleep. It does this by mimicing an app that is still started after deep sleep but is no longer on the non-Chinese market units. When FYTStarter is started, it automatically starts the configured apps.
[FYT Android Head Units] mastrv:
For the spaces after the slashes, let me clarify...the text in my post is a cut and paste of the translation of the post from 4pda...not the actual text. When I viewed the original post without translation there were NO spaces after slashes. I have gone back and removed the spaces after each slash. Also removed the space after the $ where needed.

Yes, this is from 4pda. When I was searching for a head unit, I was unaware of the Joying. At the time, it seemed the TEyes SPro had what I was looking for and, from what I could tell, frequent updates, sufficient documentation and great community support in 4pda. There are 3 or 4 threads there about the head unit. TEyes make several head units and it looks like they are the same or have become the same as they continued production and/or development of their units. When I started following the main discussion forum, there were under 400 pages. Now there are about 950 pages. They have a forum related to purchasing, installation, accessories, hardware modifications and the main discussion forum. Another reason was that the vendor provided a dash surround for the head unit and looks like a factory install. I've had to repin the provided harness and add a connector for my factory amplifier. Hopefully, no issues.

I have been testing and setting up the head unit on the desk in my den and I've figured out most of what I wanted to do. There are a few items remaining but I've started taking apart my dash. Items remaining are:

Add fan to rear of unit

Set up with Low Voltage Disconnect module to prevent dead battery

Test internal microphone and if inadequate, connect OEM external microphone

Obtain and replace the touch panel so that LEDs change colour, if possible

Fix issue with OBDII module not pairing

FYI, I used HW_GETInfo and it indicated that the Teyes SPro is an FYT unit.

Sorry about the deviation from topic. I've got a few other posts coming related to the topic :)
[FYT Android Head Units] ojuniour:
Any chance of removing the bluetooth pairing limitation regarding certain devices.. I read somewhere that within the code they searched for specific strings relating to "OBD" or something like that...
[FYT Android Head Units] mjd1975:
Hello,

Can someone tell me how I can fix my 10.1Joying Android 8.1 Intel Airmont SC9853i 4GB+64GB?

I have a problem with bluetooth. When I connect my phone it works good, but when I turn the ignition off and leave the car for a couple of hours and I come back, it's not possible to connect my phone again. I need a hard reset and start the unit again and than it's possible to connect again. I have this problem also with the odb2 adapter, not only with my phone.

Someone a solution for this problem?

Thanks for so far..
[FYT Android Head Units] Android49:
Can I have this Allapp.pkg Sir?

My joying HU is JY-VO101N4GS-R
[FYT Android Head Units] surfer63:
I don't have that one anymore. (Besides that: the mainserver mod is really firmware version dependent. I can't remember which firmware version that was and you don't mention your own.)
[FYT Android Head Units] Android49:
Is this the version sir? I got this from Joying Site/ 9853i OS 1024X768 Rotate Screen 2019.11.28.zip
[FYT Android Head Units] surfer63:
That is the latest firmware indeed, but as said: I don't have that allapp.pkg anymore and it was definitely for an older firmware version. It was only meant as a test to see what is possible.

The radiomod and the mainserver mod can be downloaded as Allapp.pkg and flashed from the 3 post of this thread.

The others can simply be installed.

oandbackup, terminal emulator can be downloaded from F-droid or the Play Store.

HWOneKey can be downloaded from my signature.

magisk manager can be found on several places.
[FYT Android Head Units] mjd1975:
I find the solution already. In the skipkillapp.prop I chance the value from the BT apk to 15 instead of -15

And it's working fine now..
[FYT Android Head Units] mclaudio:
Hi. I need to clean cache from reverse cam. What is the file ? Thanks a lot

Enviado do meu SM-N975F através do Tapatalk
[FYT Android Head Units] mastrv:
I'm trying to see what can be done about OBD module pairing.

Surfer63, I tried the Joying Tools you created. One of the options in it is to force the pairing popup to display. I'm wondering if that's what's occurring in my case. When I pair with my Android 5.0 phone, I get a popup on the phone, enter the code and it pairs successfully. With the head unit, I see the OBD module when scanning. When trying to pair (i.e. they call it Linking), I never get a popup and it ends with a message that linking failed.

I was wondering if you could provide details about the function in the Joying Tools that forces the pairing popup. I tried using that function in the Joying tool but it did not have an effect. Perhaps I can try the same method and see if that has any effect.

I don't want to purchase the OBD module where I bought the head unit only to find that it doesn't work either. I've read that this has happened to a few people on 4pda.
[FYT Android Head Units] surfer63:
This popup display is to make sure that you get a popup when a BT device is found and can be paired. This does not always happen. Next to that: FYT/Joying crippled BT and that's why hardly any BT devices can be found and paired. That is why you do not get the popup.

Quite recently we had a "break through". See #1609 and #1611 of this topic: https://xdaforums.com/android-auto/...roid-8-1-intel-airmont-eight-t3897206/page161
[FYT Android Head Units] Soiski71:
Adding RDS info into Notification bar

Hi Surfer,

I was think to look into possibility to add the RDS info into the notification bar. Some info I dug up so far suggests that text needs to be converted in bitmap so it can be shown there. Do you (or anyone else) here have any experience of such coding and would that be done in the radio.xml part or in some other function ?
[FYT Android Head Units] surfer63:
No, that's not true. It is just text. When I wrote the Xposed modules for Sofia and PX5, I also added text to the notification bar. Just as a string: the time is displayed as a string and I simply added my text (the CPU temperature) to that string with some formatting.

There is no Xposed for the SC9853i and I have no idea how to do it now. But it is not a bitmap.
[FYT Android Head Units] mastrv:
Thank you Surfer63. The information in the other thread helped and I can now pair my OBD module and use it in Torque.

FYI, for others, you only need to pair it. You don't connect to it through the bluetooth menu. After pairing with it, other apps, such as Torque, can be used to connect to it.
[FYT Android Head Units] tchleb:
Do you know whether the 4g module deactivation also works with fyt compatible devices?

Which command can be used to reactivate the 4G module?
[General Questions and Answers] update.freak:
Hello everybody,

I am looking for an app with which I can sync my music from the NAS to my smartphone.

Unfortunately, FolderSync is eliminated because no SMB2 is supported

I tested Synchronize Ultimate, which is pretty slow

I do not want to take Syncthing because an additional app on the NAS is required

Does anyone have good suggestions for other apps / options for sync?
[Tilt, TyTN II, MDA Vario III General] bammyman:
Hi guys

I have a almost new tytn2 on orange I would like to sell.Price is £180.In excellent condition and unlocked as well.Thanks
[Tilt, TyTN II, MDA Vario III General] ChumleyEX:
I would suggest you use EBay to protect yourself and your future buyer.
[Tilt, TyTN II, MDA Vario III General] CraZyLiLbOy:
If you want buy/sell, go to ebay.
[Tilt, TyTN II, MDA Vario III General] dimushor:
did you sell the phone?