yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] marcus82:
In what sense home launcher?

...

If I click om developer options, a password is asked to me and nothing happens after typing one

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] julien_blanche:
these are the all passwords belong to joying head unit, if dev password is not working then try soft reset the unit

Factory Settings: 3368

Developer Settings: 3368

Back-light current adjustment: 5768

Door lock interference: 0000

To change home launcher: 8086
[FYT Android Head Units] marcus82:
Where can I change launcher, please?and what's doors interferences?

Inviato dal mio ONEPLUS A6003 utilizzando Tapatalk
[FYT Android Head Units] julien_blanche:
launcher option should be in either general settings or factory settings menu, door interference is pop-up alarm on the screen that when you open your car's door but your car's can-bus needs to be support that feature..
[FYT Android Head Units] marcus82:
mmm the strange fact is that after put a password of these to enter into developer options, nothing happens . I'm not sure that these options are usable like smartphone

EDIT: are you able to listen radio or DAB radio using ANDROID AUTO? cause on my head unit ANDROID AUTO pause DAB radio
[FYT Android Head Units] marcus82:
hi guys, I'm quite scared that my radio has a big issue... the GPS doesn't work well and I don't know how to fix it.
[FYT Android Head Units] Busk07:
Check if your date, time & timezone are set correctly. If they're not, that can lead to issues with quite a few apps.
[FYT Android Head Units] marcus82:
'm quite sure that the date is correct but I check. The gps has worked the first day and stop... I had a problem wigth my SIM but now I've 30 gb then the A-GPS should work... The fix is so slow and poor..infact moving with my car I loose the signal.. do you think I've an hardware issue or I can solve it with factory reset?
[FYT Android Head Units] surfer63:
Did you check the cable? We've seen before it is a broken cable.

Does it curve nicely when you try to gently bend it, or does it have sharp corners?
[FYT Android Head Units] marcus82:
I've used 2 antenna with 2 different cables...
[FYT Android Head Units] bambapin:
Hi Julien, i had a chance to install the 8.14 update only now and unfortunately Google's voice feedback still doesn't work on my HU after the root (I tried both with your .zip and with one made by me).

To be clear, the Google Assistant responds correctly to "ok google" but then it doesn't speak at all, only textual answers. Same thing in Maps, you can give voice commands but there is no way to make it speak after applying Root.

I was thinking that if your HU works, there must be something different in the HW configuration, for example your HU has the DSP?
[FYT Android Head Units] julien_blanche:
Hi, have you tried the uninstalling the assistant and install it again ?
[FYT Android Head Units] bambapin:
Yes, uninstalled and reinstalled: assistant, google, maps and text to speech (also if i don't think it is used) but no luck.

After unrooting they speak again, that's driving me mad :mad:
[FYT Android Head Units] surfer63:
Magisk manager also has the "MagiskHide" as Google doesn't like rooting of devices. And some apps simply do not work when they detect that the device is rooted. Maybe Google assistant does the same.

Have you already tried Magiskhide to hide root from the Google apps? It is part of the Magisk(Manager).apk
[FYT Android Head Units] bambapin:
Yes i also tried to hide all the google apps but without success.

BTW i don't think it is just because of the root presence, i have other devices rooted and Google voices work flawlessy...

The last time i looked at the logs i saw a lot of errors related to audio/video codecs, and i had the idea that something goes wrong during the rooting process and the system is left in a dirty state, maybe some symbolic link to some libraries, don't know.

The comparison of the boot.img before and after the patch is useless, you should be able to compare the original filesystem with the one after the patch... the problem is that the original one without root is not easy to analyze :confused:
[FYT Android Head Units] bersercci:
I’ve struggled with this for months. Done my fair share of complaints to help desk, but no cure.

For me, even if I do a full reset and reinstall sw, it only takes to install Spotify from apk and start it once, it will autostart every time after deep sleep (even if app is closed before sleep).

I haven’t rooted as it seems to open a world of other problems with google voice etc. You can try to work around the problem, like map a steering wheel button for home (jus easier to get to home screen) or try to use Tasker as autostart navi app and create profile to go home on wake from deep sleep (haven’t found a suitable trigger though...)

I have a Pumpkin px5 based hu on my daughters car and it is much more a product whereas Joying is more of a project.
[FYT Android Head Units] georgebest:
There is a newer update. 17 September. They sent it to me.
[FYT Android Head Units] surfer63:
I received it as well Yesterday. I would not spread it yet as Joying did not put it on the blog yet. And there is really no changelog (yet).
[FYT Android Head Units] thierry34:
i installed rads in my joying unit but waze freezed again and temp goes up until 70-80 degrees. i installed 2 fans and now ,it's ok. with the same config (waze ,TPMS, music, daschcam) temp max 60/65 °. i just had to modify the unit hood because fans are too wide .i don't hear them when unit is on. it's cool !!!! : o: o
[FYT Android Head Units] thierry34:
what's news in this new firmware ?
[FYT Android Head Units] surfer63:
I don't know. They didn't tell me. I flashed it, but don't see a difference either. But I only have my unit a few days now and hardly used anything on it.

MCU binary (Stm32ud.bin) is identical, but the flashing leaves everything as it is. Everything on internal memory still there. All installed apps, config and data also still there.

Finally a real OTA like upgrade like you are used to on your phone.

Of course: if you did use another launcher, like I also did, you need to reconfigure that, but it is still on the system. And actually you could tweak that from the config.txt but I was not sure whether CarWebGuru would still be on my system or not.

I already made the main server mods (will adapt JET very soon) and flashed my modded radio and the new main server mod to the unit as described in this thread, which I wrote Yesterday.

Flashing is again faster compared to a PX5, and flashing on the Sofia 3GR was taking over 20 minutes.
[FYT Android Head Units] seb21:
[MENTION=2550900]surfer63[/MENTION]

Have you maybe rootet it and checked Maps and Assistant voice output ?
[FYT Android Head Units] surfer63:
Not yet. I was tempted to try "everything", but I had a family weekend ;)

As I almost wake up early I could do/try some things early morning.
[FYT Android Head Units] surfer63:
Just received feedback from joying about the new firmware.

I did have this indeed on the August 14 firmware. Now I have to test it on this firmware version.

Edit: and of course Joying is talking about unrooted units.
[FYT Android Head Units] bambapin:
If you have time to check, there was also a problem with the audio mixer related to google assistant (unrooted rom).

Below the text of the email i sent to Joying support in July and a sample video:

Example video: https://youtu.be/Y5Jpe5FfpHQ

Italian audio but english captions :cowboy:
[FYT Android Head Units] surfer63:
I'm not 100% sure but I think it is exactly the same very long running issue, already since the Sofias. It was tackled in the XSofiaTweaker/XFytTweaker xposed apps.

See for example here: XFytTweaker.java, line 384.

Now that we can't use Xposed anymore on Intel 8.1, combined with the obfuscated and "moving" code in the main server apk, we need to think of something else. Maybe another hack in the main server apk, just like the "BT to background" and "nokill" ( I will document that by the way, so others can do the same if I win the lottery and decide to buy a brand new car with nice builtin head unit ;))

Personally I hardly ever use Google voice feedback so I had not encountered it yet on the SC9853i.
[FYT Android Head Units] bambapin:
Yes it can be related, i think this problem is in the way the server identifies the app that currently has audio focus, probably the setStreamVol is called at the wrong time.

In the folder asset/property of com.syu.ms.apk there are several files which can be used to drive server behavior (audio_foucs_app.txt, tip_sound_app.txt..)

For example by adding com.google.android.googlequicksearchbox to the player_mutex_app.txt file the google news were not muted anymore, but then there were different side effects...

Were these files also present on Sofia?
[FYT Android Head Units] surfer63:
Yes. these files were also on the Sofia, but at that time we did not know what the "player_mutex_app.txt" was for. I only know now that you tell it to me :). So thanks.

and what do you mean with "side effects"?
[FYT Android Head Units] bambapin:
Mainly the navi voice no longer had priority and was no longer reproduced until the news app had finished reading.
[FYT Android Head Units] thierry34:
did joying tell you when the last firmware would be on their blog ? i would like test it !!! :RÉ:RÉ
[FYT Android Head Units] ricanxd:
Anyone else using their new dash cam? I don't see any option for the app to auto launch. I did an update to the app as well which added a bunch of extra featured, but nothing with auto record.
[FYT Android Head Units] thierry34:
i use it. when i turn on the car, the dashcam starts automatickly. I put a minisd card of 8 gb. she makes videos of 2 mn. i don't need to start applcation.
[FYT Android Head Units] ricanxd:
I see the light flashing on the cam, but I don't see files being recorded until I open the app. Is yours showing the app in the notification bar without opening it?
[FYT Android Head Units] thierry34:
not in the notification bar and i need to open app to see picture.
[FYT Android Head Units] ricanxd:
Ok I'll recheck. Seems like files aren't being saved unless I open app
[FYT Android Head Units] thierry34:
I asked joying to send me new firmware but it's the chinese national Day holidays. Wait to thé 5th october.
[FYT Android Head Units] surfer63:
If you are so desperate :)

https://drive.google.com/file/d/1akWMxEmd7rjfR7ZBY6p1HcXHBcvlQ4oc/view
[FYT Android Head Units] thierry34:
:rire::rire::rire:

thanks you !!!!
[FYT Android Head Units] tangcla:
Has anyone used something like AAGateway to obtain Android Auto wireless functionality?
[FYT Android Head Units] surfer63:
I rooted my unit running the new 2019-09-17 firmware (see downloadable zip here).

So far, so good, but please note that after rooting the Google voice feedback doesn't work anymore, just like in previous releases.

I will probably unroot it again. Now that it is quite easy to flash your unit with mods, I might do that.
[FYT Android Head Units] julien_blanche:
Without xposed framework on these head units and considering modding applications there is not so much gain with rooting for standard users i think..

Have you checked whether rgb wheel color issue resolved or not on sep firmware ? I guess i am gonna put correct rgb.png file inside settings.apk just in case..

Also can we make an assumption by looking inside the skipkillapp.prop file about last opening application automatically every time when you turn on the head ? Maybe system writes something to open last app to that file all the time to recall...
[FYT Android Head Units] surfer63:
Not close to the unit currently, so I can't check for the rgb.png file at this moment and didn't think of it.

Upon coming out of "deep sleep" the main server apk always starts a number of apps. Some of these apps are not available in our firmware and "look really Chinese", so maybe they are for the Chinese market. [MENTION=575209]bambapin[/MENTION] and myself discussed about this much earlier in this thread to see what options it would offer.

[MENTION=575209]bambapin[/MENTION] wrote the "Fytstarter.apk" that has the package name of one of those apps not available in our firmwares. It means that his Fytstarter app is always started after deep-sleep. In his Fytstarter apk you can configure any apk (installed on your system of course) to be started as well as the Fytstarter does that for you.

I use thap app myself. That is also a reason why I don't use the nokill mod myself. [MENTION=575209]bambapin[/MENTION]'s app is a much cleaner approach. And it only starts what I want to be started.
[FYT Android Head Units] rigattoni:
Hmmm... don´t find anything about the fytstarter.apk.

Do you have a link, please? :)
[FYT Android Head Units] surfer63:
I'm sorry. It started in this thread and then it continued in "[Joying for VW] Universal steering wheel controls with arduino" and one of the off-topic posts contained the apk.

See post #28 in that thread.
[FYT Android Head Units] bambapin:
Hi, you should already have that app, we talked about in the Rooting thread post #45 , i re-post the apks here.

Basically the FYT-Starter apk contains both the Setup entry point and the default one that is used to automatically start the apps at ACC_ON.

If your launcher shows only 1 entry in the app list, you can install the second apk (FYTStarterSetup) which starts the setup screen directly
[FYT Android Head Units] rigattoni:
:cyclops: I think I become old :silly:

...and yes I have these apps, but not used for a longer time.

Thanks mate.
[FYT Android Head Units] Guyzer73:
[MENTION=2550900]surfer63[/MENTION] and [MENTION=575209]bambapin[/MENTION]

Thanks for all the hard work and experimenting you're putting in to this to make this HU more user friendly.

Having absolutely no software programming skills whatsoever I will try both the FYTstarter.apk and your Allapp.pkg modding but have a question to the above. You state that the FYTstarter.apk has used one of the package names not available to us,and I assume the modified Radio.apk utilises the original package name for the radio and therefore becomes the 'default system radio app' replacing the original one? If that's the case could one in theory modify other Android Apps (media players) to utilise the correct package name thereby replacing the original one and becoming the default media app(s) when selecting via the "source" button on the SWCs??

I think I know the answer will be 'no', because otherwise it would have been done;), but would be interested to understand why, if you could spare the time and give a layman's terms answer.

Cheers and thanks again for all the help and work you've put in.

Cheers

Guy
[FYT Android Head Units] surfer63:
The answer itself is short: yes (but the explanation quite long).

That mechanism is used by my FYTHWOneKey.apk. That apk was actually created to "grab" the functionality of the hardware keys (radio, dvd, media (music), EQ). It does this by defined "aliases" that have the same package name as the joying apks., This package name is used to start the apk programmatically, as the main server apk normally does. So my apk has as "aliases" like com.syu.music and com.syu.video and com.syu.eq. So when an apk is programmatically started by its package name, and Android detects that 2 apks have the same package name, Android will ask which app to start with a "just once" or "always" option.

So you can use any media player, configure that package name in my apk as replacement for the Joying music player (logical option, but other possibilities are possible), and as of that moment android will ask which one to use ("just once" or "always"). As it is based on the hardware keys, only few apps are configured as only few apps are assigned to hardware keys

W.r.t. the radio: That is a very difficult one. The radio apk actually does nothing. When the unit is rebooted, the radio hardware(!) starts to play 0-2 seconds after "power on". Only for that reason the radio apk is also started at reboot, taking 20-40 seconds. That's why you hear the radio even before Android is ready. And then you can use the radio apk to give the MCU the command to mute the radio channel, as that is what happens. The radio is actually always on, but the channel is muted or unmuted.

So if you replace the com.syu.radio with an alias, you will never be able to stop the radio as the radio app is no longer automatically started, unless you tap the radio app icon, in which case the radio app will be started. If you only reboot once a month, you only have to really tap the radio app icon to be able to stop the radio and on any other occasion your app will be programmatically started by my apk.
[FYT Android Head Units] hugorafael:
Hello guys, need help finding out which manufacturer made my HU.

Recently bought in Brazil a model that is sold here as Aikon Atom, but it's just a rebrand from some Chinese.

It has this spreadtrum processor along with 2gb ram and 16gb rom

Stock apps like radio and bluetooth has com.syu in their name, so perhaps it's a Joying?

Attached are some pictures from settings

View attachment 4834457View attachment 4834459

View attachment 4834479
[FYT Android Head Units] surfer63:
It's not a Joying, but maybe/possibly a FYT compatible (Joying is a FYT compatible).

Use my HWGetinfo apk (see my signature) to get some more in-depth info and share it with us.
[FYT Android Head Units] hugorafael:
Here, I think it is FYT compatible and its a ZHAN

But I might be wrong
[FYT Android Head Units] surfer63:
Yes, it is a Zhan (manufacturer id 53) and it is a FYT compatible.
[FYT Android Head Units] hugorafael:
Thank you so much,

One more question if you dont mind, now That i know what kind of beast I am dealing with, what can I change about it? Can I update using Joying FW? Does Zhan provide something? Couldnt find their website

The thing that has been bothering me the most is the bluetooth app, cant connect to obd2 device, is it possible to custom ROM something that will have android bluetooth settings unlocked (Manufacterer locked everything)
[FYT Android Head Units] Guyzer73:
[MENTION=2550900]surfer63[/MENTION] , many thanks for taking the time and patience and explaining all this to me (and others who'll find it useful):svetius:. I shall RTFM your links in your signature and compose my thoughts before posting on the mods thread you have created. However, I will say if I understand correctly what you've written the a lot of my problems can be solved with existing solutions you or others have developed and will hopefully allow me to complete this somewhat complicated build both physically and software wise.

Thanks again:good:

Guy
[FYT Android Head Units] surfer63:
One more?? ;) I see 3 at least.

You can root your device. Seearch for "howt rooting SC9853i". There it is explained how to do that.

After rooting you can use my JET apk to install some modded apps.

I have no idea what Zhan or any other brand provides.

The BT app on the FYT models is for a lot of people a pain in the backside. It only hard-coded connects to some "approved" devices, which the suppliers sell. The total concept of universal connections via BT is killed with this approach, especially as they also removed the BT settings from the settings app and put it totally crippled in the BT app.

There is no custom rom (yet?) for the FYT SC9853i.

W.r.t. the BT app: On the Sofia we had a programmer who had removed the restrictions in the BT app. That was nice, but I have no idea how to do that. But in that case you do not need a custom rom, you would only have to replace the BT app the way I described here.
[FYT Android Head Units] czarekurb:
Is someone calling Google Assistant working ?
[FYT Android Head Units] surfer63:
It is working for me on the latest 2019-09-17 release. This version will be released around 5 October (as was mentioned somewhat higher in this thread). I also put up the (unofficial) link somewhat higher in this thread.
[FYT Android Head Units] czarekurb:
I have this version but it doesn't work, do you need to set something?
[FYT Android Head Units] surfer63:
The first time it didn't call, but mentions/asks something like what to do or how to do that or "I can't currently call" . The BT icon was already visible in that specific screen below the message, so I tapped it and then it called.

Next time it called "automatically"

Edit: Google Assistant only works (at least for me) if you have a network connection. When I get in the car I immediately switch on my phone hotspot and share it with the head unit.
[FYT Android Head Units] bambapin:
Maybe you have to apply the "crruptoff" tweak described in the [MENTION=2550900]surfer63[/MENTION] Modding Thread to disable the embedded 4G.

On my HU with that tweak it works now (on previous ROMs it didn't work but i hadn't applied the tweak).

EDIT: i assumed you were asking about phone calls through the assistant
[FYT Android Head Units] hugorafael:
Haha I got carried away, but thanks a lot for your response
[FYT Android Head Units] davemazo:
crruptoff tweak

Is the crruptoff file a txt file so I just have to add "fixwifi" and nothing else to it.

Sorry for the daft question but doing this sort of thing fills me with dread. I have never been able to make phone calls with this Joying unit using Google Assistant
[FYT Android Head Units] bambapin:
Yes it is just a text file (without the .txt extension!), just put it on the root of the SD card next to lsec6521update and the other files.
[FYT Android Head Units] davemazo:
Thanks bambapin, so I open the file with notepad, type in "fixwifi" (without the quotes) and save it
[FYT Android Head Units] bambapin:
Yes

Inviato dal mio SM-G965F utilizzando Tapatalk
[FYT Android Head Units] davemazo:
crruptoff

Thanks again, just wanted to make sure. No more stupid questions
[FYT Android Head Units] seb21:
Bluetooth app that can connect to any OBD II device.It is modified Joying Bt app from 17.09 firmware.

Instructions :

Backup your original BT app,you will need it.

Copy the modified app to your folder with the original.

Don't reboot now !!!

Run BT app,scan for your device and pair it.

Delete or rename modified BT app and put back your original BT app.

The last step is needed because Joying somehow is blacklisting modified BT app, after reboot it will not longer show in launcher.

But once paired device stays paired even with the original app .

Becaue the OBD device is show in system as "OBD" ,proably it will not work with special OBD devices that are needed with some apps like Vscan MDx36 and others.

Torque works flawlessy.
[FYT Android Head Units] surfer63:
Very nice work.

About the app not being shown in the launcher after reboot.

I assume you used apktool to change the string OBD in the smali code to something else.

Did you use "apktool -c b" to rebuild it, or only "apktool b". If you didn't use the "-c" the apk is no longer signed. The "-c" builds the apk with the original signing, which is necessary for a system app.
[FYT Android Head Units] czarekurb:
Will the telephone ringing work with 4g active? I care about 4g
[FYT Android Head Units] seb21:
I use Visual Studio 15 with smali plugin. It easy in use ,load apk ,edit code and build back to apk. The ms.apk changed with this method work fine.

Will have to try with Apktool.

You thinking well with the "OBD" part. I replaced "OBD" string with empty string "" .

Using startsWith with empty string gives allways TRUE :)