yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
Please share the lines you have for your current apps in the skipkillapp.prop.

Sorry. I can't answer if you need -14 or -15. I have not experienced with it as I do not care whether apps are killed or autostarted.

The point however is that the number should only determine the priority. Lower priorities should work. As such it is not a problem to use -14 or -15. You will not brick your unit or so.
[FYT Android Head Units] thierry34:
com.syu.ms	= -15

com.syu.ps	= -14

com.syu.us	= -14

com.syu.ss	= -14

com.syu.dvr	= -13

com.syu.canbus	= -14

com.syu.odb	= -13

com.android.systemui	= -14

com.android.phone	= -15

com.android.bluetooth	= -15

com.android.launcher1	= -14

com.android.launcher2	= -14

com.android.launcher3	= -14

com.android.launcher4	= -14

com.android.launcher5	= -14

com.android.launcher6 = -14

com.android.launcher7	= -14

com.android.launcher8	= -14

com.android.launcher9	= -14

net.dinglisch.android.taskerm = -13

com.glgjing.stark = -12

com.fvision.camera = -12

com.tprns3 = -12

org.prowl.torque = -12

com.syu.widget	= 0

com.syu.gpswidget	= 0

com.syu.air	= 2

com.syu.car	= 2

com.syu.unicar= 2

com.mapgoo.diruite=5

com.mapgoo.diruite:remote=5

com.ecar.assistantnew=5

---------- Post added at 05:33 PM ---------- Previous post was at 05:29 PM ----------

other thing, i noticed that since i updated my firmware with september firmware, my amps turn off about 40 seconds ans not 5 minutes as the june firmware. next ,when i stop the car and remove the keys, the screen goes black and the sound turn off about 2 or 3 seconds .. it's just a remark !! :) :) :)
[FYT Android Head Units] mclaudio:
hello

hope someone can help

since i cannot root my device, is there anyway to setup so that when i receive a bluetooth call, i can go back to waze?

yesterday i made a call and during the call i wanted to go the waze but was not alllowed

altough if i am in waze and receive a call, bluetooth call appears on a bar and let me see the screen at the same time

btw any mod so that pictures on phone appear on the bluetooth dialer also on the unit?

thanks in advance
[FYT Android Head Units] surfer63:
If you have set Waze as your Navi app, tapping the Navi button on your screen should allow you to go back to Waze. But also: some apps can be allowed to take over the phone function. I use Magic Earth and Osmand+. For both I can allow them to make/receive calls. It means that you see a bar on the bottom of the screen, but it is actually not the Joying dialer. So I am IN that app. Google Maps can do that as well and I assume Waze might be able to do is as well too.

Did you give Waze that authorization when Waze asked for it during first loading it? Because if you did, you are in Waze with a phone call overlay at the bottom. Therefore: you cannot go to Waze because you are already in Waze.

I do not know of any mod that shows your phone pictures during the call or in the contact list. If you use Google Contacts instead of the BT app contacts, you do see the picture.
[FYT Android Head Units] mclaudio:
i will make a short video

---------- Post added at 10:49 AM ---------- Previous post was at 10:48 AM ----------

but if i use google contacts will it make the call over bluetooth? i also have sim card for data in it...
[FYT Android Head Units] surfer63:
A video of what? Either you can not remove that phone dialer bar because it is the BT app, or the phone dialer bar is part of Waze. Nothing to change there.

I made a main server mod that should enable to put the Joying bar also in the background, but some users mention that it does not work.

And if your navi app has taken over the phone bar (like mentioned above), it will certainly not disappear because it is part of your navi app.

Yes, it should make the call over bluetooth. The sim card is only for data. The FYT units do not support phone calls over the sim card.
[FYT Android Head Units] thierry34:
my skipkillapp file is ok ?
[FYT Android Head Units] surfer63:
I am sorry. Yes, it is OK.
[FYT Android Head Units] mclaudio:
hi. can you teach how to extract my current apk files from flash file rom so that i can try to mod them?
[FYT Android Head Units] surfer63:
Mentioned in the 2nd line of post #2: "Use the (English) version of ApkPack.exe (english version attached) to unpack/repack an Allapp.pkg. (It also works with wine on Linux/MacOS)"
[FYT Android Head Units] mclaudio:
i am sharing this repository,...

maybe useful for someone

https://yadi.sk/d/umCvHqCDzHccr
[FYT Android Head Units] rigattoni:
This repository is nothing for user of the FYT9853i units... :confused:

So it might be useful for other units, but not for this one... and by the way, this repo has been posted a lot of times in different threads now, outside of this one.
[FYT Android Head Units] mastrv:
Just wanted to add a little more info about this, in case others find this.

I found out that there is an additional step required to make the System UI Tuner option show up. You have to long press on the settings icon in the notification area. You will see a toast message that System UI Tuner has been added or something like that. If you do this a 2nd time, it will offer to remove the System UI Tuner option from the settings menu. I'm assuming you can add it back by doin this again.

Also, the System UI Tuner does not show up in the Developer Options, as I stated, but at the bottom of the System option at or near the bottom in blacked out text. I got to that screen by long pressing the CarWebGuru settings to go to the full settings and not the TEyes customized settings.

Found out when re-flashing the firmware. There was also mention that System UI Tuner either won't show up or have no effect if the animations are turned off in Developer Options but I did not test this.
[FYT Android Head Units] surfer63:
You learn everyday .... ;)

@xjesus posted here a few days ago a link to how to assign another function to your steering wheel app (Gracias). The steering wheel app does not allow you to assign the BACK key (and its function) to your steering wheel learning. It is completely missing (don't ask me why).

So based on the post on 4pda (thanks to 4pda user booroondook), which I had missed completely, I also created a mod for the steering wheel learning app.

See image for the original apk:

And the image for my mod adding the BACK functionality (disabling the HANG_UP functionality):

In case you want to flash it: See attached. I also added the original version in case you want to revert the change.

As usual: All my sc9853i mods are on my github repository: https://github.com/hvdwolf/SC98531BinRepo/

In this case under mods: https://github.com/hvdwolf/SC98531BinRepo/tree/master/mods
[FYT Android Head Units] mastrv:
I recently flashed to a modified CC2 firmware based on 2020.10.31 and all seems to be working properly. The post on 4pda is found here: https://4pda.ru/forum/index.php?s=&showtopic=938749&view=findpost&p=101300663

It had manufacturer 43 in fyt.prop and I changed it to 95 for my SPro. I'm just finishing setting it back up as before I flashed with apps and settings and all seems to be working properly. The main reason I flashed this is to get functionality for long key presses. Prior to doing this, I flashed other firmware, the first of which had the MCU flies to flash.

The OBD paired without any modifications. The Bluetooth value in config.txt or fyt.prop is set to 1, the normal for TEyes. To my surprise, the pairing popup came up and it connected successfully. The TEyes OBD app doesn't seem to work...the OBD modded apps don't work either. However, I successfully used Torque on the head unit to connect to the OBD adapter...good.

The CC2 launchers seem to be there and working, but I'm using the 2.x version of CarWebGuru. Mine is set to 1024 x 600, I believe. The GPS is working well with 3m accuracy. The Google Assistant is working properly...in the other thread referred to, it seemed that there were problems making Google Assistant (GA) work, but I have not experienced those issues. Just had to set GA back up and it works by both manually invoking it through a shortcut, a steering wheel control and by saying "Hey Google". I get a visual feedback that I was heard. I'm currently working out how to get GA to make calls...not sure this will be possible.

I also have the modified radio working as indicated previously in this thread. I looked through the code with jadx and there were several config parameters that I'm experimenting with. Will post results if/when there is anything of interest.

So, one of the reasons for this post is to inform of the steering control app for the buttons that is available in the firmware I just flashed. Attached below is the tutorial video that is included with the app.

Mine shows up a little differently from the video. In the video, it looks like another button is added as you program the buttons. However, in mine, there are many "buttons" available to be programmed. Can be seen in a screen capture on the previous page of this thread. The short and long presses work. However, some of my buttons are treated as the same button, even though the numbers at the top are different. I believe it is due to the changing temperatures. The button values at the top also change as the passenger compartment warms up. Others in 4pda have reported the same. I think I'll work on this issue when the weather warms up as I believe I'll have to work with the wiring or add resistors as others have done. Don't know if this issue can be "fixed".
[FYT Android Head Units] jackk111111:
Help please. i update for error rooted version. Now screen Need check Active id: 1 area: 2.
[FYT Android Head Units] surfer63:
More info needed!

Which unit, which firmware version are you on, which rooted image did you use.

The simplest would be to only flash with a unrooted boot image. The second option to simply reflash your unit with the Joying firmware for your unit.
[FYT Android Head Units] mastrv:
FYI, someone on 4pda has posted that they successfully installed EDxposed. No other information yet other than a screen capture of it installed. Image attached here. I'll post more info when/if I get it.
[FYT Android Head Units] mastrv:
The user said they didn't do anything special to install EDxposed. He installed it from Magisk. He also said that not all (xposed) modules worked with it, though.

This means you'll need root to install it. I'm not too familiar with Xposed or the available modules. So, I'm not sure whether it's worth installing it or not. Now if someone would build a module for the sc9853i FYT head units that are useful, that could convince me to root my head unit and install EDxposed...for example, a module that intercepts calls to the dialer and re-routing them to the bluetooth dialer :)
[FYT Android Head Units] surfer63:
I built the XFytTweaker xposed module (https://xdaforums.com/t/xposed-inte...-to-tweak-your-fyt-based-joying-unit.3748009/) (see my signature). That one was for Sofia and PX5. I guess that one works for the most part still on all sc9853i and uis7862 models as FYT hardly changed anything. And I guess also on all FYT based models: Joying, T'eyes, NaviFly, Kingbeats, etc.

That would also allow again for the ACC_ON and ACC_OFF events. And possibly as well for Google voice feedback, which normally did no longer work after rooting.

I might root my unit and also try it out.

Edit: It might need some minor additions as now with the DSP modules, the DAC module is no longer necessary and the BT phone module is no longer full screen either during a call.
[FYT Android Head Units] mastrv:
Back to the topic of the Google Assistant not making voice calls and displaying "App isn't installed".

From my reading up on Android, I believe that is being displayed as the intent that the Google Assistant is calling is not handled by any application on the head unit. Now to determine what the intent is.

I found a Logcat reader on the play store that will function without root. Through adb you enable a tcpip port and then the app connects to it through remote debugging. The app is found in the play store at: https://play.google.com/store/apps/details?id=com.tananaev.logcat

Once I've determined the intent, perhaps GVC CallHandler can be modified to be useful in this situation.

On the Google Play store page for the GVC CallHandler at: https://play.google.com/store/apps/details?id=com.judlis.googlevoicecallhandler4joying, there are screen captures. When I try to run the GVC CallHandler, I don't ever see this screen. I only see the settings screen when I invoke it. Not sure why, though.

Hopefully, this will lead somewhere.
[FYT Android Head Units] mastrv:
I finally got back to the Voice Call issue. I was able to find a message in the log that explains the issue. A specific intent was being called for a specific package. I believe it's the package that is missing..."com.android.server.telecom" is the package being referenced by the intent that is being invoked...which does not exist, from what I can tell.

I found a few apks for Oreo, not specific to sc9853i, on APKMirror and APKPure but they would not install. Not sure why.

I'm not sure if it's possible to install this from another architecture or manufacturer. Any ideas?
[FYT Android Head Units] surfer63:
Not for another architecture, but noarch would mean it is 100% java.

You need the ones from 8.1, not the 8.0 versions.

Most probably this apk needs system rights which it will not get as it is not system signed, and most probably that's the reasonwhy it wil not install as Android blocks that.

You can try to "install" it directly by copying it via an lsecpudate script.

If it doesn't work you need another lsecupdate script to remove it.
[FYT Android Head Units] mastrv:
Perhaps there is a way to install it through adb and to give it the rights it needs? Not too familiar with adb so don't know how to do this and how to figure out which rights/permissions it needs. Probably through the manifest?

I used adb to give rights to a dpi changer apk and also to start on a different ip address for the nologcat apk to work. Just did this today and they both worked properly...so without rooting.

I successfully loaded the drivers for the unit a while ago...from 4pda.
[FYT Android Head Units] bambapin:
Can you post the complete Log line that contains the Intent invocation?

I would like to understand if it is possible to decode also the Intent parameters.
[FYT Android Head Units] mastrv:
Here's most of it. I just noted it down in notepad at the time:

android.intent.action.CALL dat=tel:xxxxxxxxx flg=0x1000000000 pkg=com.android.server.telecom (has extras)

The telephone number is obfuscated...don't know what the flag represents without looking at the telecom code.

I've found a couple of telecom 8.1 apks to try and I've fgured out permissions from the apks using aapt2 and figured out how to install app using adb...and assign permissions.

Will try later and provide results and more details from the log.
[FYT Android Head Units] bambapin:
Thanks, maybe you don't need to install the native android.server.telecom if you are sure it's not present in the ROM.

In my opinion the problem is due to the fact that the Intent sent by Google Assistant is "qualified", that means force the packageID, while that intent in ur HU is handled by the app com.syu.bt.

Probably the same technique used in FYTStarter could work: an app with the ID android.telecom.server that does nothing but routing the original intent to the package com.syu.bt.

I haven't had a chance to test it on the headunit, and it probably won't work, but if you want you can try this mini app which only does the Intent route.

Indeed i'll test myself later or tomorrow.

EDIT:

I just tried, the app does not install on my HU because an app with package ID "android.server.telecom" is already present.

@mastrv Is there any other Intent in the log after the one you saw ? Maybe it's a subsequent call that fails.
[FYT Android Head Units] mastrv:
@bambapin the error is 1 or 2 lines after the intent request and references the telecom server. Perhaps the telecom server in our hu is not complete or correct, for some reason. Otherwise, you'd think the ROM would come with a dialer to dial out using the sim if/when you had a sim in it. I'll paste more of 9the log later.

I'll also pull the existing telecom server and see what I can see. Any idea on how to list activities or intent filters?

I'll also do a voice call from my phone and compare logs and the telecom server. I did a voice call successfully before but it's running Android 10.

Fyi, I also loaded the xda version of the Google dialer which ran...can't remember what happened though when I tried dialing out. I'll put in a sim and try again.
[FYT Android Head Units] bambapin:
Yes, of course it is possible but what is strange is that the "app not installed" error message is very specific.

I usually use jadx-gui with the APKs ( https://github.com/skylot/jadx/releases/tag/v1.2.0 ), it's quite fast and allows you to read the manifest.
[FYT Android Head Units] mastrv:
OK. I pulled the telecom apk from the HU and compared it to other Android 8.1 telecom apks that I was able to find. The one on the HU does not seem complete. It is definitely missing the intent-filter in the manifest. I used jadx to look at the manifests.

I then had a look at the manifest for an Android 11 telecom apk and I think I found the problem. It has an intent-filter for the android.intent.action.CALL that is being called. It's specified in the manifest. For the version from the HU, there is no intent filter for android.intent.action.CALL

So, I'm going to try some of the other 8.1 telecom apks to see what happens. The only use cases that I can think of that are useful are voice calls using assistant, making calls through the bluetooth dialer manually and receiving calls. If those work, then I think that there would not be any other issues.

I also thought about other issues. If the telecom apk from the firmware is the only one to use, and it is "correct", then it could be some kind of mismatch between the assistant app and the Google app and the version of Android. I'm not sure if this is possible, as the min/max sdk versions should handle it. I pulled the version of Google Assistant on the HU and it did not seem correct. The one that I have installed I obtained from an earlier TEyes firmware version. I may uninstall it and install the latest from the Play store...I'll look at this more closely after trying various telecom apks.

The 8.1 telecom apks look much more complete. There are ones from various companies that look like a much more complete similar to more recent ones from Android 9.0, 10.0 and 11.0 I'll try that to see what happens.

If anyone finds a Telecom apk by Google for 8.1, please post it.

Edit: Attached Telecom.apk that was pull from HU and two other ones I found to replace it.
[FYT Android Head Units] bambapin:
Try this one, it should handle the CALL intent.

I had extracted it a long time ago from an old Joying ROM image: the .zip contains the apk and the OAT files.
[FYT Android Head Units] mastrv:
The manifests are different...the Joying one includes the intent-filter being called. However, I can't see any actual java code in either of the apks using jadx.

What is the OAT for? Do I need to do anything with this? I'm going to be using adb to install / replace the Telecom apk. However, I don't remember seeing anything regarding installing OAT files in adb.

From what I can tell, it looks like the OAT file will be recreated by the HU the first time the Telecom.apk file is installed or accessed.
[FYT Android Head Units] bambapin:
Yes i know the manifests are different , that's why it is possible that it could handle the Intent.

The problem is that it is old and the MCU firmware was changed several times...

The target folders structure on the HU filesystem should be:

system/priv-app/Telecom/Telecom.apk

system/priv-app/Telecom/oat/x86_64

You need root to mount rw /system and the replace the original files by a filemanager (you can use Total Commander from Windows and connect the HU through its adb plugin).
[FYT Android Head Units] mastrv:
I'm hoping this doesn't rely on the MCU, but you could be right.

My HU is not rooted. I had root before but chose not to root on the last firmware flash. A few odd things always seemed to happen when rooted that don't happen when unrooted...such as Chrome stopping to work and Google Play not downloading apps/updates any more.

I'll first try with command line adb. The install function has a replace flag, -r, that should work. There's another flag to automatically grant permissions, -g, but I'm not sure if that's still supported. I'll try that, if needed.

I didn't know about an adb plugin for Total Commander. The Total Commander site says the plugin works even when not rooted. I'll try that if the command line doesn't work or just to test...later. Don't normally use Total Commander. I use Midnight Commander on Linux.
[FYT Android Head Units] bambapin:
I also decided not to use root anymore because of strange problems, among other things with Google assistant.

You can try the adb install way but I don't know if it makes you replace a system apk without root, there is also a risk that the current classes in the HU OAT directory are not compatible with the replaced APK... in any case it is worth a try.

Root was needed with the total commander adb plugin not to make the plugin work, but to allow you to make /system writable.
[FYT Android Head Units] mastrv:
OK. I finally have the Joying Telecom installed and I'm getting further, I believe. Maybe, very close to making it work.

After having to re-install the adb drivers, I proceeded. Was getting a message similar to USB device not recognized.

I tried installing through adb but I was getting a weird error "can't open non-file" and I figured it was because /system was not mounted as rw.

I then tried to root using Magisk the way I had done it previously but it did not work. I made a boot.img but Magisk was not able to modify the image, for some reason.

Next step, I created an lsecupdate script. This eventually worked, but I think I fried an sdcard in the process. I was going back and forth to my car quite a few times testing the script. At one point, it did not work and I saw an android laying down before rebooting. Everything was going smoothly so I figured it might be the sdcard. I have a bunch of 2GB and 4GB cards that I bought very cheaply that I use for these kind of things and for my single board computers. Found a local seller on Ebay where I bought 15-20 of these sdcards for $10. Back to the testing...With a new sdcard, it removed the old Telecom and OAT files, copied the new ones and then updated the file modes.

Now, I no longer get "App isn't installed". Great.

When saying "Call Mom & Dad", what happened was started the XDA version of the Google Phone that I had installed. Excellent. Wanted the request to go to the Bluetooth dialer, so I uninstalled the XDA Google Phone. Now, I get a toast message "No app was found to handle this action." I believe that this means that we should be able to have something like GVC CallHandler that handles the correct action, can be set as the default for calls that forwards the request to the Bluetooth dialer.

Another thing that occurred to me was to reinstall the XDA Google Phone, insert a sim and then try to make a call. Interesting results. The interesting thing that happened was the call went through. However, I don't think the audio / mic is working properly. Will test this more thoroughly later.

Can someone modify the GVC CallHandler?

Addition: Attached is the lsecupdate script I used. I also included my original Telecom, for those interested, as well as the new Joying one provided above. Update for yourself, as needed.