yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
I created a "minimally customized" rooted rom for the Joying based on the CC2 of 2020-12-04 and based on @gamer765 allapp.pkg (thanks for the great work you did!!) with some minor extensions.

I flashed it about an hour ago and so far it works OK. I want to do some further testing and tweaking.
[FYT Android Head Units] yokala:
Cool ! Did you managed to make SWC and stock launcher to work properly ?
[FYT Android Head Units] surfer63:
SWC works for me but I don't have a CANbus controlled one. I have a resistance based 3rd party "clipon" SWC on my steering wheel.

With stock launcher I assume you mean the launcher4, not the SPRO launcher (launcher3). The SPRO launcher3 works fine for me. I did not test the launcher4 yet as both you and gamer765 mentioned that it didn't work on the 1280x720 screens. (And with regard to my modifications: I also set the launcher3 as default launcher for the ROM)
[FYT Android Head Units] yokala:
Oh ok, I have no ideal why my SWC didn't work as I don't have a CANbus controlled one neither.
[FYT Android Head Units] mastrv:
The long press was added only to cc2 as a differentiator between spro and cc2, I guess. There was an mcu update that supposedly was required for this and once flashed could not unflash it. The mcu update was in the April firmware and they then stopped including it and advised people to flash that one first and then the newer firmware. I believe there was a patch or alternate mcu update to work around that...for or related to kingbeats, another fyt unit...on 4pda. I believe it's in the 9853i thread. A link to the thread can be found on the main 4pda spro/cc2 discussion thread. I believe there is info for it in the sticky post at the top of one or the other thread.

FYI, I'm running the Dec 2019 spro firmware with carwebguru and poweramp and I don't think mine has crashed a single time. I have mine set to turn off each time instead of sleeping. I also updated my radio to have local stations and I believe it's the joying Style radio...horizontal with icons for stations.
[FYT Android Head Units] Bronchi:
Hello,

I have an fyt intel airmont unit. I successfully managed to mod server apk to include some new apps in nokill app using this guide. THANKS!

The last thing I want to achieve is integrating with my built in hands free system in my car since it has great microphone. Here’s the problem:

my built in hands free system is plugged to android radio using AUX. When I open AUX app I can hear all good, but I have to open it manually. Is it possible to add AUX package name to one of these txt files so AUX would have like priority over other playing apps? Perfect solution would be to listen to Spotify etc. and during incoming call aux would take priority over any other sound app, so I guess it’s similar to Navi app.

For any clue thanks in advance.
[FYT Android Head Units] surfer63:
You were completely right! My steering wheel keyes functioned so I did not even look at the the app.

I just did and tried to modify something but that doesn't work at all.

So I took the FYT steering app, replaced the black background with the blue background from the Teyes app, and flashed it.

Now it works again.

What to do:

Unzip the fyt_steer.zip and flash it.

After reboot go into settings -> apps. Select app steering wheel control and remove Cache and data

Learn your keys and voila: it works again.

I will add this FYT app to my custom rom
[FYT Android Head Units] surfer63:
The aux app is the com.syu.av apk.

You need to add it to the navi_app.txt

Normally it is definitely not in there, but if you want to use it for your phone calls, you should add it.
[FYT Android Head Units] mastrv:
Crruptoff - in the first post it is indicated that using this file no longer works to hide the no sim icon in the status bar.

There is an alternate method that I'm now using that works. Using the built-in, I believe, system ui tuner, this can be toggled off. This was something talked about on 4pda. The system ui tuner allows several minor customizations. 4pda indicated you can bring it up by holding down the system settings icon in the status bar pulldown. However, that did not work for me. I found it in the Developer Options near the bottom. It is in blacked out text but is still functional.

I was originally using a sim directly in the Teyes SPro but to get higher speeds and better coverage from my provider, I changed to get internet from my phone as a hotspot. The SPro does not support some of the LTE frequency bands that my provider uses.

I'll try to put up a screen shot of the system ui tuner page. I'm trying to get Google Assistant to take them but no luck yet. Can't remember the exact error message now. Maybe I'll post a picture.

Oh, and Happy New Year!
[FYT Android Head Units] surfer63:
Please do.

Note that the T'eyes firmware blocks and disables GoogleAssistant in favor of their own T'eyes voice. That is the reason I went back to Joying firmware. I hate it to have to enable GoogleAssistant on every reboot/fast boot in the Settings..
[FYT Android Head Units] mastrv:
I'm still using the Dec 2019 TEyes firmware. It is stable and I found that the newer versions of the firmware offered little or no extra features that interested me. Mine does not have the TEyes voice control. It has Google Assistant enabled by default. When I say "Hey Google", I get a visual cue that it Google Assistant heard me.

I'll post the screen shot(s) / picture(s) shortly.
[FYT Android Head Units] mastrv:
Here are the screenshots. I forgot about the little touch assistant app that can take screenshots. You can see the little circle in the top left of each image, which is the little app. Screenshots:

Home page which shows SIM/data icon missing

When I long press the settings icon in the lower right, I get the normal Android System settings. Scrolling to the bottom shows "System UI Tuner" in dark text. I thought it was in Developer Options, but I was mistaken

When I select that, I get that app starting showing "Status Bar" and "Do not disturb". Select Status Bar. Not sure what Do not disturb does

The two pages show the options/toggles available. I turned off "Mobile data" to hide the SIM/data icon

I've also attached a screen shot of the modified radio that a member on 4pda helped me customize with stations from my area. He had made a black/red highlighted one for a Kia which fits great for my Kia.

I'm in the process of trying to modify the status bar so that the clock is larger. I think that involves modifying the System UI Tuner apk which corresponds to the attached screenshots. It's from a more recent TEyes firmware, so not sure what that will do.

FYI, I have the 4/64 TEyes SPro.
[FYT Android Head Units] mastrv:
Here are a couple of screen captures with the new SystemUI apk. The apk was from 4pda. I simply replaced the apk in the /oem/priv-app/SystemUI directory with the new one.

I haven't completely tested it out yet, but it seems like options are the same. After replacing it, the status bar updated with the new one. So far, looks like the size of the clock is changed, which is what I wanted.

I've soft of gotten used to the old one. Haven't decided if I really like the new one yet or not. Will know after driving around with it. Not much space left for the other icons when phone is connected.

On to the next project. I'm going to try the steering wheel control (SWC) app from more recent CC2 firmware files. They support long presses. For my setup, I have an interface module between the TEyes SPro and the harnesses. The interface module can supply short and long presses. I'm hoping the newer steering app will just work. With the existing app, I have to keep an SWC button pressed before I can select a function for it. This prevents me pressing the button quickly. The newer SWC app interface is changed to allow both. Screen shots follow:
[FYT Android Head Units] mastrv:
Here's a screen shot with the icons for the phone displayed. It has the additional microphone, battery and bluetooth icon displayed where the battery and bluetooth icon are displayed in colour.

In addition, shown is what happens with an incoming call. Instead of going to the fullscreen bluetooth phone screen, you can answer or decline the call. I believe an image from contacts displays, if the contact corresponding to the phone number, is available. You can also display a keypad to enter digits, if needed. It didn't look like what you'd think a keypad looks like but two rows of numbers...didn't really pay attention. Not sure what the button with the two horizontal arrows does. Didn't try it.

I thought I was going to make changes to the MS (main server) apk for this to happen but was pleasantly surprised. However, this did not happen when the radio app was playing. Possibly due to me changing the standard radio app to the new one. It displayed this panel on Waze and PowerAmp and when they were both in split screen. I believe the panel also displayed on the CarWebGuru home page but can't remember.

When I answered the call from Waze or PowerAmp, the music that was playing was muted or turned down and then came back up when I hung up the call.

Another thing that I'll be doing is changing the ring tone. If I'm not mistaken, this has already been done previously in this thread.

Still working on changing the steering wheel control app. I've collected several replacement apps to try. It sounded like some others tried unsuccessfully, so I'm prepared for this not to work.
[FYT Android Head Units] surfer63:
Maybe I have to disappoint you. A lot of apps nowadays (music players, navigation apps, etc.) have their own phone access (and/or contacts access), and also request that permission on install. If you check via the Apps Settings (or via the Play store) if they have phone access and/or contact access, you might see that they have that access and they (mostly) use the default phone "widget" for that. This is a "minimized" widget. So if a call comes in, it is not handled with the default phone client, but with the builtin phone-client (widget) of the app. The Radio app doesn't have that and does start the normal phone interface.

Yes, it has, It is also in one of my downloadable flashable "images" with some explanation, but it is actually very simple.

Please note that this is also based on interaction with the MCU, so these "several replacement apps" might not work at all.
[FYT Android Head Units] mastrv:
For the phone widget, I was thinking this was a system function that displayed that panel. So, I believed there was a configuration file that listed the apps/packages that the system would use to determine whether or not to display the widget if the package is found in the config file or the full phone app if it is not found. If what you say is correct, then I can live with and am happy with the existing functionality.

For the steering app, I was thinking it may still work for my specific situation. Now, the default steering app does not have a way to enter a short press and a long press for a button. With my interface module, when I do a short press, a specific value is sent to the head unit. If I continue to press the button, the interface module can be programmed to send a second different value to the head unit. With the newer steering app that allows to specify a short and long press for a specific button, I was hoping that it would work in my situation. I'm not aware of how the steering wheel app interaction with the MCU will occur in my specific situation. I'll just have to try it and see. I don't have high hopes but it can't hurt to try.
[FYT Android Head Units] mastrv:
Further about the phone widget...in 4pda, there were a couple of posts about it. I believe someone asked about setting up so that the widget shows up in other apps as well. One person suggested modifying the calling_show_btapp.txt file for this to happen, while another person suggested that modifying the navi_app.txt would produce that result. This was another reason I believed it was possible. However, there was no follow-up discussion about the results of doing changing those files.

Those two files are property files in the ms file.
[FYT Android Head Units] surfer63:
I am almost 100% sure that the navi_app.txt is not the correct file. That file is used to register navigation apps that need "audio focus" as soon as they start using the media channel to produce sound (the navigation instructions or possible traffic lights/speed traps/etc.). Of course you can also put other apps like Google Voice (is already in there) , Bestee, aCapella, T'eyes voice (is already in there), or speed trap warning software, or other voice/media apps (I have put a lot of those apps in my extended ms apk).

The purpose of the navi_app.txt and how it is used from the ms app, has nothing to do with the BT app or another "HFP client".

I know absolutely nothing about the calling_show_btapp.txt.

However, when I google translate that text file I get:

#When a call comes in the following application status, pull up the Bluetooth phone application, otherwise enter the Bluetooth PIP display
#% at the beginning, indicating that the behavior is a regular expression
%com\.syu.#All applications starting with com.syu
%com\.fyt.#All applications starting with com.fyt

Of course it is google translated and might be wrong, but to me this seems that the standard BT app is called for all syu and fyt apps. But the BT app itself is not specified.

The BT app is called in several places of the MS app using several intents for several reasons. I guess you should look which method (function) is calling that calling_bt_show_app.txt, and then search further how the BT app is called (I did a really quick check as one of the intents of the BT app is com.syu.bt.PhoneActivity, but that one is nowhere used in the ms app)
[FYT Android Head Units] mastrv:
I read the translations. I've kept thinking about this and it just occurred to me. The system is invoking the bluetooth popup panel/widget as specified in this calling_show_btapp.txt file...at least for the ones I've seen and am interested in.

The comment for the regular expressions says that for all com.syu.* and com.fyt.* applications/packages, bring up the full Bluetooth call handler. This includes the radio, which is the one I was mentioning. For all others, 3rd party applications for example, show the bluetooth panel/widget. This is happening for Waze and PowerAmp and CarWebGuru as well as when they are in split screen. Working as the comment suggests.

You've examined the MS app and it seems that the file is not used or that there is no functionality for it. I haven't looked at it. The apps I've decompiled usually look like they're obfuscated and I can't follow those...easily. It should be easy enough to modify the calling_shot_btapp.txt file in the MS app to see the results. If you remove the com.syu and com.fyt regular expressions, then all apps should display the bluetooth panel/widget, including the radio, etc. If this works as expected, either all syu and fyt apps need to be listed or the regular expressions need to be modified to exclude any apps that one is interested in.

PS: Just to make it clear, the comment says PIP, which is Picture-In-Picture, which I'm calling a panel and you've called a widget.
[FYT Android Head Units] surfer63:
Use jadx-gui > 0.9 to open the apk. After loading select from the menu Tools->deobfuscation.

You are right. It is indeed easy to remove those entries and try it. I didn't think of that.

And we both give PIP a wrong name ;) Actually it is called "multi-window mode" in the top-layer of the screen.
[FYT Android Head Units] mastrv:
So, I removed both entries for com.syu.* and com.fyt.* from calling_show_btapp.txt and the radio now shows the popup panel when an incoming call comes in while the radio is active. I believe removing com.syu.* would have been enough. An alternative is coming up with a regular expression to exclude one or more apps. I was reading up and the most straightforward regex to do this is to use a "look around" function. I'm not sure if the SPro or Android 8.1 supports look arounds in regex...not all Regex engines support it. I'm putting a hold on this, for now, as it now is functioning as I want it. In addition, this is only a concern when a call comes in and at worst, all incoming calls will display the popup instead of going to a full screen BT.

As for the steering app change, I also tried several newer steering apps that allow both a short and long-press to be programmed for steering wheel buttons. The app ran and recognized when buttons were pressed. However, when trying to select a function for any button, whether it's for short or long press, the function was recognized that I was pressing it but did not set that function. Next steps for this are to review app and see what happens when the function is being set. Also, to review options for the MCU, which I believe is tied to the short/long pressing of the steering wheel controls.

PS: Thank you for the info about jadx. I believe I have used it previously a few times. I did not know about the de-obfuscation function.
[FYT Android Head Units] surfer63:
It supports some sort of regex. Using %\. before or after (or both) in a name makes it a wildcard.

%\.google. would find every package "starting with something" with google in the name
[FYT Android Head Units] mastrv:
I've put reviewing the steering app on hold.

While reviewing these recent items, I came across something I was trying to solve...making calls using Google Assistant by saying "call mom & dad".

When I was trying this previously, I was getting something like "Can't make calls yet". I then read about the dpi and the fact that making calls was meant for phones and not tablets. Tablets, it seems, have a default dpi of 160 dpi. So, I checked with an app and sure enough, that was the dpi.

Some comments indicated setting the dpi to anything over 160 would do the trick. So, I set it to 161 and sure enough, I no longer get "can't make calls yet". However, now I get "App isn't installed." message. The response indicates that the Assistant has recognized the request, though. There is a checkmark beside the command. There is also a button that says something like "make a call". When I press that, it does actually make the call successfully. Odd.

Things I've tried for "App isn't installed":

Install GVC call handler...didn't work

I installed Syslog to review the system logs. Haven't viewed them yet. Tried to send them by multiple methods to my desktop PC/Lan but was not able to.

Reviewed if any others have had this problem. Seems like there have been others-not many, but no resolutions.

I noticed that when I switched the dpi to 161, the split screen functionality changed. At 160 dpi, I was able to split 50/50 for two supported apps. I could also moved the dividing slider so that it was a 67/33 split. When I switched the dpi to 161, I could only split 50/50. I was worried that I had to choose either 161 dpi if/when the solution to making a call with Google Assistant or choosing 160 dpi to keep the 67/33 split. When I switched back to 160, the 67/33 split returned AND, trying to make calls with Google Assistant was still responding with "App isn't installed" instead of "Can't make calls yet".

So, does anyone know the solution for "App isn't installed" when making calls with Google Assistant.
[FYT Android Head Units] yokala:
Anyone knows a way to have an app launching 2 apps at the same time in split screen ? There is some in the play store that works fine but it creates a shortcut (activity I guess) on the home screen. My problem is I use Agama Launcher and it doesn't allow such a thing, it can only launch apps. Maybe I can call the shortcut using tasker secondary app or something ?
[FYT Android Head Units] mastrv:
The "Screens" apk from the play store is probably the one your talking about. You can add a shortcut to the CarWebGuru launcher. Is there any specific reason you want to stick with Agama? You may be able to set up CarWebGuru to look like Agama, if it's the look you like. Here are a couple of youtube videos of Agama and CarWebGuru:

(at 0:43 shows main screen)

(at 0:34 shows screen like Agama)

Note that I would recommend the older version of CarWebGuru. The older one (v 2.x) had several free built-in themes that you can switch between easily. In the newer version (v 3.x) had the built-in themes removed and a pay-wall with ads and such added. Seemed to have lower resolutions for things too. You can find older versions in multiple places. Here's one:

CarWebGuru Car Launcher old version

Download older versions for CarWebGuru Car Launcher APK

carwebguru.en.aptoide.com

You can probably do the same using Tasker or Macrodroid but then you'd probably run into the same problem in Agama...how to invoke Tasker or Macrodroid to perform the function?

If you really want to stick with Agama, you'll have to figure it out or keep looking for someone that can do it or did it. If you figure it out, please post solution for others to benefit.
[FYT Android Head Units] yokala:
Well I used Tasker and it works just fine. Install Split Screen Launcher from the play sore, and in Tasker create an event Secondary Tasker app opened, task applications > shortcut > Split Screen Launcher and you will be prompt to create a new shortcut with the 2 apps of your choice. Save and apply the task and it's good to go. Don't forget to enable Tasker and Split Screen Launcher accessibility in FYTstarter to make it work.
[FYT Android Head Units] bambapin:
If you are rooted you can use FYTStarter to start the accessibility service, i don't think that adding the app to the nokill could avoid the service being disabled.

More precisely, it is not necessary for root to be kept active: it is enough to install and launch FYTStarter only once, while you have root. Later, even if you remove root, the app will still be able to start the accessibility services.
[FYT Android Head Units] mclaudio:
Thanks

altough i tried several times but not able to get root -(
[FYT Android Head Units] yokala:
Hi,

If I play music with Spotify, when going to deepsleep the music dosn't pause right away. Is there a way to do send "pause" event when the screen goes off ?

I tried Tasker but I couldn't find a suitable trigger for ACC_OFF (I used USB disconnect but there is a delay so it doesn't help me).

If I put Tasker in the Allapp.pkg, it will be install as a system app and I could use ACC_ON or OFF as a trigger somehow ?

Thanks !
[FYT Android Head Units] surfer63:
No. It also needs the the same signing as the Joying apps to be able to use the Joying generated ACC_ON/ACC_OFF broadcasts (as of Android 7.x)
[FYT Android Head Units] yokala:
Oh ok, so is there a way to pause the music when the screen goes off ?
[FYT Android Head Units] thierry34:
do i put only the skipkillapp file with torque,cpu...) and delete all files in the allapp.apk? when i"ll update , it will just update the skipkillapp file on the unit ?
[FYT Android Head Units] surfer63:
If you have all apps in the Allapp + a few more of your own, it will be a full flash.

If you have only your apps in the Allapp.pkg, the system will only add or update those apps.

I created an Allapp.pkg only containing the radiomod and the mainserver mod. Two files, nothing more, resulting in a 7.4MB Allapp.pkg. I put that one with the lsec6521update on a USB-stick.

In one of the other tests I put the radiomod and the mainserver mod, oandbackup, terminal emulator, HWOneKey and magisk manager. Resulting in an Allapp.pkg of 18MB and copied that with the lsec6521update on a USB-stick.

Both flashed without a problem. The radiomod and mainserver mod were replaced. The others simply added.
[FYT Android Head Units] thierry34:
ok , i succeded to update what i wanted (add allapp modified with only app i want to add to skipkillapp file, but it doesn't work when i turn on unit.

only tasker open but says there was no actif profil but others app don't open.

i put -12 to 4 app and -13 to tasker in skipkillapp file.

it's too bad , i must open the 4 apps one by one to every start up ...

do you think i can put -14 or -15 ?