yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] PieterD82:
Unfortunately i don't think the simple solution of unplugging the canbus connector will be a workable solution since the wife got used to the parking lines on the back up camera following the steering wheel position drawing a turn circle. It gives me that extra insurance the wife won't give the back of the car a unique shape, if you know what i mean ;)

The settings of the canbus are not set to Opel, but to some other GM branded car, Opel or Astra isn't even listed there. But i will follow your advice, @surfer63 I will see if i can change it to something else, although i'm a little hesitant in doing that because i don't know if it's dangerous to change that and if this device then has the potential to mess with the brains of the car.
[FYT Android Head Units] Spastro:
Been thinking of getting one of these android 8 units in 10.25 mode I found fairly cheep.

I know android 8 is fairly old now, but would you guys using this recommend this head unit once it's updated to joying latest rom available for the unit?

Is there a custom rom somewhere that upgrades it to a higher android release?

Would only really use it for Spotify and Google maps.

Might buy real cam and OBD2 reader.

What are your thoughts ?

This version is $270 Aus

New android 10 unit is $510 aus
[FYT Android Head Units] PieterD82:
So, in a previous post i wrote that this thing seems to mess with my canbus and just change the way the car's start/stop system works (or doesn't work) I said that toggling the option in the car's setting through this android device re enabled, or updated the setting to the car. as i said, i like the start/stop system as it is in fact a fuel saver (i drive a lot). So i had a brainwave. In the settings of this device you can select the default navigation app and if it should start on boot/wake-up. So i went and got @surfer63 's FYTStarter app and just put that as the "navigation" app. I then let it start the settings app, the Car Info app and Waze, so every time i get in the car, these 3 apps start as before only waze would.

I've been driving around with that setup now for a little over a week and it works like a charm. the car does it's start/stop-thing like it was intended to do so from the factory. I'm aware this is a bodged solution, but it works and i'm sort of happy with that.

I've attached a picture of that, with 2 other random ones, just for the heck of it.
[FYT Android Head Units] surfer63:
This is not my app. This (great) FYTStarter app is nade by @bambapin .
[FYT Android Head Units] PieterD82:
Oh, sorry. My bad.
[FYT Android Head Units] GuFontt:
Hi everybody, I have a Joying 6.2 inch in my car and a SWC wired controller on left side of steering wheel, connected at KEY 1 wire. Today I bought another SWC control, wireless with receiver and placed on console, and I've installed on KEY 2 wire. To be fully functional for me, I want to set both SWC controls to adjust Vol+ and Vol-, but I can only set one of them with SWC settings app.

There is some way to set resistive parameters manually inside any .txt or .conf file?

Thanks in advance!
[FYT Android Head Units] Spastro:
Sadly this didn't work for me.

Installed first 2 Apks.

set phone permissions.

Set GVC as default caller.

Tested.

App not installed still.

Installed zip file update.

Seems to works for a few calls.

Restarted head unit and tested again. Now when Google tries to call the custom phone dialler keeps crashing.

Reckon there is a way to fix?

Thanks
[FYT Android Head Units] PieterD82:
Hey there,

I also recently installed a second SWC to my unit. I installed it on KEY1 however. I'm not 100% sure on this (i'm making an assumption now) but i do believe that these buttons have the same resistance for what they do.

In case you didn't know, a set of SWC buttons are just completing a circuit with a resistor value per button so it's perfectly fine to have multiple SWC' on KEY1

So, long story short: Connect your secondary SWC to KEY1 instead, even if another one is already connected to it. The resistor values should be the same if in your case you want the buttons to do the same anyway.

Additionally:

If this method does make both SWC's work but you find that you can only program one of your SWC's at a time and loses the setting for the first. Then you will need to get a set of resistors and a multimeter. Take both SWC's out of your car and onto the bench. Connect one of them to your multimeter and measure each resistance value of the buttons on the first SWC and do the same for the second one. If these values are not identical then you will have to make sure they are by changing the resistance values of each button so both units have the same resistor value for each button.

You will have to do this by wiring in, or taking out (hopefully not) resistors. I recommend you use blue resistors (https://www.google.com/search?q=blue+resistors) because they have a tolerance of 1 to 2% whereas the beige ones around 5%

PS: make sure you connect your SWC to the ground of your unit directly.
[FYT Android Head Units] mastrv:
Let's try to figure it out in the thread so others can benefit with this.

I just went out to the car to make sure it still worked :) It still does! Yay! When I make a voice call, usually the first time I try a voice call, it just ignores it, I believe. Then it seems to work each time after that.

Make sure you have updated your Google app and Google Assistant app. You don't need to clear defaults or reset anything else after that. Make sure you have also installed and updated the latest Google Contacts app as I believe Google Assistant uses it to lookup. This may be the, or one of the, issues.

OK, what model head unit do you have and what firmware are you using / running with? Have you rooted?

Also, please list the steps you tried and the messages displayed with as much details as possible. So, for example, when you say you installed the 2 apks, please list the names and which post you downloaded them from, etc. You should be using everything from post #620, https://xdaforums.com/t/modding-your-joying-fyt-sc9853i-unit-without-root.3974357/post-84814233.
[FYT Android Head Units] Spastro:
Hey Mate. Thanks so much to help me troubleshoot this. Fingers crossed it will work for my model as well.

Google App Details

Google App, Google assistant and google contacts is as up to date as i can get them according to play store.

Google App is on 12.28.8.23.x86_64

Google Assistant is on 0.1.187945513

Google Contacts is on 3.49.2.383700152

Head Unit Details

Joying 10.25 Inch Android 8.1.0

Not Rooted (Would like to keep it that way)

MCU: 2019.09.07 10:40:57 JY_53_C63L_G32P48F64_Vwe: 1.0

CPU: Intel X86_octor-Core 1.8GHZ SC9853 4 +64GB

Installed Files.

The three files mentioned were downloaded from your post as linked above.

Original Issue.

When using google assistant, google would tell me there was no app installed.

Following your instructions.

Installed both the GVC+CallHandler+4 APK and the Custom GVCBluetoothPhone Handler APK.

I made sure both these applications had phone access within Android Settings.

I now tested several times, but google constantly told me no app installed.

installed telecom server.

Proceeded to install telecom server from flash drive by unzipping the contents to the root of a empty spare drive.

Install completed without issues. Now when i insert the flash drive back into my computer to check if the backup of the original files are there so i can revert if needed i can see i have the following files listed.

LOST.DIR (empty folder)

lsec_update

lsec6521update

Returning back to the head unit now that the telecom server is installed i tested google assistant again.

First time nothing happens as you had mentioned.

Tried Again then everything seems to work perfectly.

Here is where my problem starts.

Now If i restart the headunit completely for example to test what happens after the car has been off for a few days and try again.

Google assistant initiates the call as per before but then i get a pop up saying CustomPhoneDialer has stopped.

I have the option to open the app again however even if i do this and repeat the process to call someone the Custom Phone Dialer always crashes.

Thanks again for all the help.
[FYT Android Head Units] mastrv:
You probably meant lsec_updatesh was now on your flash drive. That should be a directory. Please zip up the directory and post it.

As far as the steps you've taken, they seem correct. If you can have a look at the log or also post it, that should help narrow down the issue. The error should be noted in the log.
[FYT Android Head Units] Spastro:
Hey mate.

Used a logcat capture tool I found on the playstore to grab the logs. I didn't have root or a method to hook it up to my laptop so I hope I was able to capture enough information.

Lsec_updatesh

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com
[FYT Android Head Units] mastrv:
@Spastro The log doesn't help. I was having a look at the code and I think I know how to change it to show a message instead of causing the error. It will take me a while to re-install the dev environment, to make the change and test it.

One question, when you say "reboot" do you mean completely or from sleep? There's a setting of whether to completely reboot or just to sleep the head unit so that it quickly restarts. Which is yours set to?
[FYT Android Head Units] Spastro:
Mine is set to sleep.

But occasionally I don't drive for a few days at a time. So the radio will turn off compleatly.

So when I was testing I did a reboot from the menu in joying as a test.
[FYT Android Head Units] Spastro:
Hey mate. Managed to get any further?
[FYT Android Head Units] mastrv:
Attached is a debug version of the apk. You'll probably have to uninstall the existing one first. I'll have to go back and figure out how I signed it or just create new keys, etc to create a release version.

I just went out to the car to test it. Now, when an error occurs, a toast message pops up and says an unhandled error occurs and then displays the text message part of the exception.

I was getting an occasional error and the message says that it couldn't find the GVC call handler...interesting. When I try it again, it works. Odd. I'll have to figure out if that can be addressed.

Anyway, you should at least now see why it's failing on your set up. Let me know and I'll see if it can also be addressed. FYI, I set the Toast message to stay visible for as long as possible (i.e. "Long") but it's still kind of short...pay attention or maybe take a video while you're testing so you can look back on it.
[FYT Android Head Units] Spastro:
Hey Mate, thanks again for all the work.

Uninstalled the custom dialer and installed your new debugging version.

Gave the customer dialer phone access.

Tried making a call and it failed the first time as expected. Tried again and it worked.

On my joying head unit. I restarted the device to emulate what would happen if the car was left off for a few days as i dont drive everyday.

When the head unit restarted i tried voice calling again and got this error. Now this will continue to happen and never work again no matter how many times i try.

Now if i reinstall the GVC Call Handler apk it will start to work but again breaks as soon as the head unit restarts or in real life cases turns off completely after a period of none use.
[FYT Android Head Units] mastrv:
I tried a few things and have not been able to determine why that activity cannot be found.

Still looking into it.

I'm thinking of trying to modify the code to not use the googlevoicecallhandler4joying at all.

...still working on it.
[FYT Android Head Units] Spastro:
You're a legend mate! Thanks for all the help.
[FYT Android Head Units] shahin_pz10:
Hello guys,

I have a problem with my sc9853i android device that was made by other manufacturers. I need to disable developer mode to use an application that wrote to use OBDII but it is not successful because it will be on every time that I disable it so I can not open the application.

Thanks to your helpful comments I already changed the ROM to joying 2020.04.07 version. But the problem still exists.

I tried to root my device using this tread and I was successful, also I installed this APK to change Joying settings to android default settings to disable developer mode forever, but as I open Joying extra tools app the button that changes between original and Joying settings disappear.

Would you please help me to solve this solution?

Thanks!
[FYT Android Head Units] Spastro:
Been playing around with it yesterday to see if I can work anything out.

Everytime I start the car and try you voice dialling I get the error I posted above about the manifest.

Happens everytime regardless if the car was turned off for a few mins and the headunit goes into standby mode or if the car is off for a few days and the entire headunit goes off.

Once that error pops or before trying to initiate voice calling as I just turned the car on, if I open the joying GVC and leave it running in the back ground and try initiate voice sailing again it works.

Everytime.

However doing this, Google assistant brings the joying GVC app to the front and the joying phone controlls appear at the bottom .

When I hang up the joying GVC remains on the front and I need to tap the home button to return.

After a call if I clear all recent apps from background and try voice calling again Google assistant will once again tell me to check the manifest.
[FYT Android Head Units] mastrv:
Interesting observation.

I think I've found a possible reason for the error. On one post on a developer's forum, where someone had the same error occurring, someone suggested that if the activity being called doesn't handle errors/exceptions properly then the error can occur. A few comments seemed to have fixed their issue based on that.

So perhaps the GVC app doesn't handle what is being attempted.

In any case, I haven't had too much time to work on this especially with the hot weather...the garage was extremely hot. It's a lot cooler now and I'll probably be getting back to this. Still working on it!
[FYT Android Head Units] Spastro:
Really appreciate, at least for now if I just manually start both apps and leave them running in the background everytime I start the car at least it works.

Not ideal but it works.

Thanks again for looking into it.
[FYT Android Head Units] ant_thomas:
Interested about this one - since the official firmware update has twipe_all in the updatecfg.txt file.

I'm guessing that means a firmware update puts us back to factory?

Considering I've got the headunit to a point where I'm fairly happy with the setup, would be annoying to have to do all that again.
[FYT Android Head Units] surfer63:
Yes, it puts you back to factory.

When making programs that do change the way they use their settings/preferences, you write an update method that takes care of this when moving to a different settings/preferences configuration. This to do proper housekeeping and keep your settings clean. FYT doesn't do that, or at least didn't do that.

You can of course simply remove the twipe_all from the updatecfg.txt, but in the past we have seen many cases of program crashes, program errors, program functions no longer functioning, unit freezes, unit crashes, etcetera because of this. Lately they seem to have this better under control, or simply start writing to new preference/setting variables and no longer use the old ones. This is considered ugly, but enables also going back to an older version which will simply use the older settings.

So be brave and test without the twipe_all. If the unit stays stable and works fine after one week, then please share with the forum from which version you came and to which version you upgraded.

If it isn't stable (after 1 hour, 1 day, ..) simply flash it again using the twipe_all.
[FYT Android Head Units] ant_thomas:
Thanks for the info.

I'll remove the line and give not wiping a go and report back at some point
[FYT Android Head Units] mashrom:
Excellent mod! For the orignal app how the city name is determined if I want to keep the same orignal GUI? Can't find the same menu of City Name as in your mod.

Thanks
[FYT Android Head Units] mastrv:
If I remember correctly, it should still be there but it's not obvious. I don't have my original radio installed any longer and the following is mostly from memory.

There are a number of icons/buttons on the screen...probably bottom of the screen. This is actually scrollable although it's not obvious. Swipe left and a number of other buttons will show up. I believe the last one on the right is an edit button. Press it and a popup shows up. In the popup, press the text on the top left status/title bar. This will then show a dialog box where you can type in the name of the city. I think capitalization and spaces are important here. This will match exactly whatever is in the "cityName" field in the JSON file specified in the other post you replied to.

Note that there are also radio settings. You can access those through the button next to the edit icon described in the previous paragraph. One of the settings is something like Region. I don't think that affects the cities but it affects how the radio frequencies and frequency changes display and occur. Remember the values on the Settings, if you want, and then just try things until it works the way you want.

Post a screen shot or a picture of your radio settings. I'll be able to confirm it.

Let us know how it goes.
[FYT Android Head Units] Spastro:
Hey mate. Just figured I'd pop in and see if you had any luck or if there is anything I can do with my limited knowledge to help.
[FYT Android Head Units] mashrom:
Thanks for the reply. In the oringal Radio app nothing there is related to the city setting. I clicked every where in the channel edit page and nothing poped up. I'm attaching a snapshot if it refreshes your mind with.
[FYT Android Head Units] mastrv:
Haven't had a lot of time to work on it. I haven't abandoned it yet...still on my to-do list.
[FYT Android Head Units] mastrv:
It looks like the version of the radio apk that you are using doesn't include the functionality to specify the city.
[FYT Android Head Units] surfer63:
Wrong answer. Deleted.
[FYT Android Head Units] mastrv:
Yes, this is different from the radio app that I'm using. I have a TEyes SPro/CC2 which is an FYT unit similar to the Joying.

This is the popup that I get when editing the stations available to the Radio app. I click on the top left and a prompt to enter the city is displayed. In the following image, it's currently set to Toronto. The app then populates the available stations from the JSON file where the city name matches the text that the user enters:

I'm not sure whether or not the app I use can be used on the Joying models. I posted the apk for the radio I use earlier in the thread...page 29 or 30, I think.
[FYT Android Head Units] surfer63:
It should. I already did that "long time ago" before I purchased a DAB+ module.

I removed my previous post. You are absolutely right, you do need the T'eyes radio app and it works like you describe.

The Joying apk doesn't have it. It is too long ago that I myself modded that radio app, since I started using a DAB+ module.

(And it is a huge load of work if you live in a country (the Netherlands) where the same FM-radio station can have 10 frequencies depending where you are. Also because the RDS-AF is incorrectly implemented on all those FYT radio apks, so it doesn't autoswitch to a stronger "Alternative Frequency")

The "radio_freqs.json" in the Joying app is slightly simpler than in the T'eyes radio app as it misses the fequency logo, and that source code is also missing in the Joying apk.

Sorry for the wrong info in my previous post about the Joying apk. I deleted it. The description of how it works was also wrong as that was based on another radio app for the phone.

Not my best day ;)
[FYT Android Head Units] pajo985:
Hi!

Is maybe something like this solution to our Bluetooth problems?

BT dongle

Is it possible to connect this to Joying USB port and connect for example BT headphones, or OBD or something else through it?

Thanks :)
[FYT Android Head Units] surfer63:
Very short: No.

Has already been tried with numerous BT-USB dongles.

It is not the BT device itself. It is simply blocked in the firmware.
[FYT Android Head Units] pajo985:
Ah, thank you :)

And another question then.

Do you by any chance know if OBD2 dongle with WiFi connection could connect to Joying, and simultaneously have 4G network?

I am afraid that because WiFi hotsopt from OBD dongle headunit would think that this is preferred connection for data, so it would cut off 4G?

Thank you
[FYT Android Head Units] surfer63:
I do not understand. The OBD has wifi and 4G?

The principal is simple. The device offering the hotspot has 4G running and puts a WiFi or Bluetooth hotspot on top of that.

Devices using that WiFi do not need 4G.

So if your Joying has 4G and can setup a WiFi hotspot, that will continue to work and the WiFi OBD dongle should be able to connect.

Of course this is theoretical. Testing in practice will proof it, and you never know with these Chinese units.
[FYT Android Head Units] dbmgreen:
Hi all @surfer63 would the software linked in this thread work on the following unit? Just dble checking before I go ahead.

Joying sent me updated firmware which downgraded my modem to 3G. The new baseband details after I flashed what they sent me are..... FM_BASE_18A_RLS2_ISHARKL2_W18.37.1 P1|sc9853_modem/05-09-2019 11:29:15 Marlin2_17b_iot_W19.35.2/marlin2_cm4|08-27-2019 08:43:27

3G is unworkable really? Need to get my 4G back, happy to try this F/W?

The old details were:

Device Status

Android version

8.1.0

Baseband version

FM BASE 18A RLS2_ISHARKL2 W18.37.1 P3|sc9853_modem|04-16-2020 11:35:23

Marlin2_17b_jot W19.35.2|marlin2_cm4|08-27-2019 08:43:27

Build number

OPM2.171019.012 release-keys

System Info

APP 1280x720 2020-06-23 09:44:56

System Application Info

System Application Information

CPU Info

CPU:Intel X86 Octa-Core 1.8GHz SC98531@4.0GB(Memory) +64 GB(Storage)

MCU Version

2020.04.03 09:51:11 JY_53_C63L_G23P48F64 Ver: 1.0

Bluetooth Version

BLINK 2161 RELEASE0/2020:06:15:19:03:51 blink

CAN Protocol Version

V3.28.015BYPS

Serial number Unknown

Machine Quick Response Code

150100434b544d3452008cc3eef16500Device Status
[FYT Android Head Units] mastrv:
Hey @Spastro. I had a chance to work on this a bit. I've removed the call to GVC and call the bluetooth intent directly.

It seems to work well except for the first time you try to make a call through Google Assistant. After the first time, it works each time. That first time, it just doesn't do anything. So I say "Call Mom & Dad" once or twice the first time it'called

I'm thinking about ways to handle this. Here's the new CustomPhoneDialer. What I did to install it was to uninstall the old one, uninstall GVC 4 Joying app and then install the new CustomPhoneDialer. After installing it, I went into the permissions for the app and gave it the listed permission. I think there was only one. Following that, I made it the default phone app when asked.

Here it is:
[FYT Android Head Units] dbmgreen:
I guess the other question, does anybody have

Baseband version

FM BASE 18A RLS2_ISHARKL2 W18.37.1 P3|sc9853_modem|04-16-2020 11:35:23

Marlin2_17b_jot W19.35.2|marlin2_cm4|08-27-2019 08:43:27

on their device, and can I they point me to their firmware , and can I use the tools in this thread to update mine back to this version?
[FYT Android Head Units] Spastro:
You bloody legend mate! Seems to be working well , both after normal standby and after a full restart.

Yup. First time needs to be done twice but I can live with that if it got no further then this! Would happily shoot ya a few bucks for a beer.
[FYT Android Head Units] dajetzi:
Hello,

I like to download apkpack.exe but could not find a source.

http://mirrors.gtxlabs.com/joying/3_Misc_Tools/ApkPack/ is not working anymore.

Does anyone have a working link?