General Modding your Joying/FYT SC9853i unit without root

[PieterD82]

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!

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.

 

[mastrv]

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

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.

 

[Spastro]

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.

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.

 

[mastrv]

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.

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.

 

[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

 

[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?

 

[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.

 

[Spastro]

@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?

Hey mate. Managed to get any further?

 

[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.

 

[Spastro]

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.

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.

 

[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.

 

[Spastro]

You're a legend mate! Thanks for all the help.

 

[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!

 

[Spastro]

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.

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.

 

[mastrv]

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.

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!

 

[Spastro]

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!

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.

 

[ant_thomas]

Some commands that can be put inside updatecfg.txt

twipe_all # Wipe entire system
twipe_data # Will wipe data partition (but not /sdcard, internal memory). Wiping the /data partition will wipe all config, all 3rd party apps and updates of system apps. This is the same as a "reset to factory defaults"
twipe_sd # Will wipe internal memory /sdcard (but not the data partition)
dellapp # Remove all 3rd party apps
make_updates # Make an upgrade U-disk boot file
test # test unit and firmware before flash

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.

 

[surfer63]

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.

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.

 

[ant_thomas]

Yes, it puts you back to factory.

Thanks for the info.
I'll remove the line and give not wiping a go and report back at some point

 

[mashrom]

To modify the radio stations, open the apk with 7-zip. Do not add or remove files. Only update the existing files. Keep the file names the same. This will be the easiest way to add/modify stations.

Modify the radio_freqs.json file within the res/raw directory. You can add entries or modify existing entries. Use a text editor that uses Linux type formatting, such as Notepad++. Each entry is something like:

"freqName": "KLOS Rock Station",
"freqLogo": "CA50",
"freqNum": 9550,
"cityName": "Los Angeles",
"userRadios": []

freqName is the text displayed for the station.

freqLogo is the filename of the station image. For example, in the above, the image file would be named CA50.png

freqNum corresponds to the radio station frequency. When tuned to 95.5MHz FM, then this information is displayed.

cityName corresponds to the city name that must be specified so the station data is used. For example, when "Los Angeles" is specified for the radio station, all stations that have cityName of "Los Angeles" will be used. You specify your city by going into the radio settings by clicking on the little disk image on the bottom of the radio screen...2nd from the right.

Make sure you don't miss or add any quotes. If you do, the whole file may be ignored as it won't be valid JSON format. If you're curious about JSON, there are many examples and lots of info found by Google.

Only 18 (6 x 3) stations can be selected for display on the screen. You can choose to only have 18 entries of your choice or all of those in you area. When scanning for stations, all entries that match will display the logo you specify.

For station logos, replace existing files in the res/drawable-nodpi-v4 directory with the logo file(s) you provide. They should match the same format as those you replace. Some formats may not work. If the image has an issue or can't be found, a default image is displayed.

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