Database Info

[APP] Navigon MobileNavigator for Android

I know there are a few Navigon threads but they are for other phones than the Nexus and quite old. The Navigon site says there is a try and buy, but it doesn't show on the market. Not sure if it's because I am rooted. Whatever, I have bought the app anyway because I have had good experiences with the Navigon units here in the states in the past.
So far the app has installed and when running it for the first time, Navigon says it will download about 2gb's of data (thank god I just bought a 16gb microSD lol). Also it is recommended that the phone be in a charger and connected to a wlan so a constant connection can be held to download such a large file. Also danger of being throttled lol by tmo lol...but thats another thread altogether.
So far so good downloading but it's 15% done with 36 min to go on the download. Thank goodness my boss just installed a wireless router in the office!
I'll update with any new news on the product once downloaded.

Went home for lunch and used Navigon for the first time. Out of the box, the voice prompts are WAY to low. I could hardly hear anything. I maxed out the app volume and no change. I then went to the sound settings and maxed out everything, prior, I had my notifications tone set pretty low, but once I maxed the notification sound, the Navigon came to life!! Kinda silly IMO. Not media but notification volume!?
Next I figured I turn on my bluetooth and connect to my blueant S4. I have the 1.5 software (downloading the 1.6 update now). And the Navigon does route to the S4 but also the handset itself! I'll update if the blueant update fixes that or not.
Now using it as a plain jane navigator, I think is on par with the Navigon products I have used in the past. It works pretty well, but the newer roads have not been updated as of yet, but google maps have the updated/newer roads. I am in San Antonio, about a half hour from the downtown area so there is a lot of new roads being built.
Conclusion:
The short and dirty of it is that the Navigon is pretty steep in price (~$39.98USD) for the first two weeks and then increases in price to a whopping (~$59.98USD). Is it worth it? I'd say try co-pilot first because 1. it's cheaper even with the traffic add-on and 2. You can always try Navigon after you decide if co-pilot doesn't jive with what you want to do.
The only other plus is that if you cannot get a cell signal to run the navigation (a la google nav), you can use the downloaded 2gb file as a guide and the app will reconnect once it receives a signal.

how does it handle music apps. I mean if you have music playing on, does it pause the music (or reduce music volume) during voice guidance?

arkavat said:
how does it handle music apps. I mean if you have music playing on, does it pause the music (or reduce music volume) during voice guidance?
Click to expand...
Click to collapse
Haven't tested that part out yet. Will report back once I do. Thanks for reminding me, even though I do not really use the music player in the car all that much.

Music a no-go...
...when used with Navigon. Both are on at the same time and no volume lowering is done on the music side when the prompts are spoken.

kpjimmy said:
Next I figured I turn on my bluetooth and connect to my blueant S4. I have the 1.5 software (downloading the 1.6 update now). And the Navigon does route to the S4 but also the handset itself! I'll update if the blueant update fixes that or not.
Click to expand...
Click to collapse
Hi, I was wondering if you got a fix for this or not? I'm getting the same problem with my Desire HD - I'm not sure if the problem is the phone, the S4, or Navigon. The S4 came with 1.6 firmware so there's nothing to upgrade to. I've emailed both Blueant and Navigon support, but my 24 hour trial period is up, so I've uninstalled for now.
Hope you can help! Thanks.

preacher65 said:
Hi, I was wondering if you got a fix for this or not? I'm getting the same problem with my Desire HD - I'm not sure if the problem is the phone, the S4, or Navigon. The S4 came with 1.6 firmware so there's nothing to upgrade to. I've emailed both Blueant and Navigon support, but my 24 hour trial period is up, so I've uninstalled for now.
Hope you can help! Thanks.
Click to expand...
Click to collapse
No same issue when updated to 1.6 on the blueant. Currently Navigon is my backup navi.

Thanks. I emailed Navigon, who said they don't support A "Bluetooth audio only" option, but CoPilot handles the audio perfectly. Unfortunately it doesn't seem nearly as good at finding routes.
Do you know if this is this specific to the S4?

preacher65 said:
Thanks. I emailed Navigon, who said they don't support A "Bluetooth audio only" option, but CoPilot handles the audio perfectly. Unfortunately it doesn't seem nearly as good at finding routes.
Do you know if this is this specific to the S4?
Click to expand...
Click to collapse
Not 100% but I found that the Navigon uses the same tones from the notification settings. Meaning one needs to increase the volume on the notification settings to hear the voice prompts rather than media, which I think would best fit. If they did that, the navigon software may work via bt audio, but I am no coder, but just speculating.
I am now using this as my backup navi because in some areas in TX, there are very spotty territories for 3g even edge coverage for tmobile usa, so having this is a plus in my opinion, but was it worth the hefty pricetag? I have to say no if you are looking for this as a primary navi software. I would rather pay some additional cash for a dedicated gps unit.
BUT, using this had me thinking back to my Sony Ericsson days where I used a gps puck to use as a gps navi. amAzegps.com First off its friggin free lol, worldwide coverage, multilanguage support and pretty accurate for a free gps. I haven't used this in a few years but I am glad it is still around. It is a nice proggy. I would suggest all who cannot use google or want to try an alternate navi program.

Thanks, that's interesting. I noticed that CoPilot's changelog specifically listed fixes for BT handsfree, so I guess they are more interested in compatibility with different BT devices. I can understand it's hard for Navigon to ensure compatibility with every bit of hardware, but this particular problem does seem to be due the way they stream the sound to the BT device, so must be fixable.
I'm using CoPilot now, and it works well enough, but if I choose to go a different route to the one suggested, rather than calculating a new route, it keeps telling me to do a U-turn around and go back. Still, I don't use the satnav every day, so it's probably good enough for what I need.

Just got an update on the Navigon. Not sure what the update was. No changelog I can find and I could not find it in the market anymore for some reason.
On vacation right now attending my brothers wedding out of state. So I'll report back if there were any changes.
Anyone else?

Unfortunately I gave up and switched to CoPilot, but I did learn here that the CarUI app on the market has a fix for the bluetooth issue, if you start MobileNavigator from CarUI.

Some Questions before i buy

Hey
about to pull the trigger on getting one of these for myself, just hoping to get a few questions answered before i do
how well is media control handled by the watch, is it capable of at playing or pausing media from 3rd party media apps? (i dont like the standard android or samsung offer so use an alternative)
is it capable of playing videos on the watch screen from either locally stored or internet streamed sources?
i have read a couple reviews on poor connectivity between the watch and the phone, constant dropping of the connection and if the battery drains completely it requires a factory reset to become usable again
anyone experienced anything like this or have advice around it?
if anyone who has one and is kinda enough to answer these questions for me it would be greatly appreciated

Also another question that came to mind
how functional is the mapping app for the watch?
can i look up a destination on my phone with google maps and have that information relayed on the watch?
(i ask this because i know the watch uses a different maps app and not sure how well it works with google maps)

kalys said:
Hey
about to pull the trigger on getting one of these for myself, just hoping to get a few questions answered before i do
how well is media control handled by the watch, is it capable of at playing or pausing media from 3rd party media apps? (i dont like the standard android or samsung offer so use an alternative)
is it capable of playing videos on the watch screen from either locally stored or internet streamed sources?
i have read a couple reviews on poor connectivity between the watch and the phone, constant dropping of the connection and if the battery drains completely it requires a factory reset to become usable again
anyone experienced anything like this or have advice around it?
if anyone who has one and is kinda enough to answer these questions for me it would be greatly appreciated
Click to expand...
Click to collapse
I use the media controls with PowerAmp, Spotify and Google Play, which works very well together (play,stop, previous, next and volume).
I haven't tried viewing videos on the watch, but I've read that it too works well using a File Manager app found in the Gear app store.
When I setup the watch for the first time I had major connectivity issues, however that was corrected after a reboot of both the watch and the phone.

kalys said:
Also another question that came to mind
how functional is the mapping app for the watch?
can i look up a destination on my phone with google maps and have that information relayed on the watch?
(i ask this because i know the watch uses a different maps app and not sure how well it works with google maps)
Click to expand...
Click to collapse
There's no simple way to go from google maps on the phone to the watch. You can just start with Here maps on the phone, though, which gives you the same thing. The Here-maps app works, though establishing the watch-phone connection can take a few tries. Here maps is a pretty solid navigation app on the phone, and offers free downloads of maps globally, so you're not always dependent on a data connection. When you set up the navigation on the phone, you get turn-by-turn directions on the watch, with a buzz as you approach each turn. More useful walking or biking than when driving, in my experience.
There's also a paid watch app called Gear Navigator which uses google maps data for turn-by-turn navigation. It's innovative and keeps getting updated, though in my experience a little unstable.
---------- Post added at 05:04 PM ---------- Previous post was at 04:55 PM ----------
kalys said:
Hey
about to pull the trigger on getting one of these for myself, just hoping to get a few questions answered before i do
how well is media control handled by the watch, is it capable of at playing or pausing media from 3rd party media apps? (i dont like the standard android or samsung offer so use an alternative)
is it capable of playing videos on the watch screen from either locally stored or internet streamed sources?
i have read a couple reviews on poor connectivity between the watch and the phone, constant dropping of the connection and if the battery drains completely it requires a factory reset to become usable again
anyone experienced anything like this or have advice around it?
if anyone who has one and is kinda enough to answer these questions for me it would be greatly appreciated
Click to expand...
Click to collapse
About connectivity: the couple of times I've drained my battery I have not needed a factory reset, and in the month and a half I've had my Gear S2 classic, most connections work most of the time. But I do wish the connections were more reliable: I have had problems, usually fixed by just turning the watch off and on (no reset), and sometimes rebooting the phone. The hardware and interface are so great, it raises some people's expectations for performance very high, and then they get disappointed by the small bugs. So if you buy, know that it works, it's cool, but it could be more reliable, and with luck might improve over time with updates.

I have found the Bluetooth connection to be very good. Much better than the LG Urbane 2nd Edition LTE. Because the BT is so good on my S2 that I never really needed to use WiFi on the S2, and because the wifi on the LG Urbane was not great and I was testing wifi on the Urbane, I did discover that I wasn't getting notifications on the S2 over wifi. I factory reset the S2, and it has been great since then. When I turn Bluetooth off on my phone. S2 goes into Standalone for 15 or so seconds and then goes into Connected Remotely and notifications and such work perfectly. When I turn BT back on on my phone, S2 goes into Standalone for a few seconds and then into Connected via Bluetooth. That's how I expect it to work.

Unbelievable. Oneplus claims that a bug is now a feature.

Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!

I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie

MJFox78 said:
I have the same problem with my Huawei Watch and my cars hands free system
I tried to disconnect the watch with Tasker as soon as my hands free system connects, but it never worked reliable (because the watch connects again immediately and takes over the call functionality)
I guess we need to wait until we get Android Pie because as far as I know this problem is solved with Android Pie
Click to expand...
Click to collapse
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.

nabbed said:
Here, check this out.
Me:
When two BT devices capable of telephony functions are connected, the second one connects as "Connected (no phone)", and its telephony function cannot be used.
Example (picture attached). If Huawei Watch is already connected, when Jabra Talk attempts to connect, it will connect as described above, and one cannot make or receive phone calls on Jabra Talk (but still can on the watch.)
Oneplus support:
Thank you for taking the time to send us this email as well as the screenshot that you provided. I understand that you want to use both of the Bluetooth devices for easy access and getting in touch with loved ones for helping us keep on track with our daily activities.
I would like to inform you that the OnePlus 6 can actually connect to two Bluetooth devices. However, by default, you can only choose one for making and receiving calls. Just choose which you preferred to use by toggling the "Phone calls" under each setting of the Bluetooth devices.
This bug was not present in 5.1.5. They introduced it in 5.1.6/7.
This bug is present in all Pixel phones because it's a buggy Google code that Google simply does not care to fix.
Samsung fixed this in their phones.
So, I am guessing OP had this fixed in 5.1.5, but then they just lazily copied and pasted that Google garbage code.
And they don't know how to fix it now. So now it's a freaking feature.
UNBELIEVABLE!
Click to expand...
Click to collapse
if Google's code is garbage, I suggest you stop using android and start making your own good code!

nabbed said:
I hope so. But I'm not that hopeful - I think it's a Google bug, and they simply don't care to fix it.
Meanwhile, I have to disable the phone functionality on the Watch so I can use my hands free car kit.
It's so disappointing, especially since this stuff always worked with Samsung phones, OOS 5.1.5 (the bug was introduced in 5.1.6/7) and even the early Pixel, pre Android 7.0.2.
Click to expand...
Click to collapse
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all

kewlest22 said:
if Google's code is garbage, I suggest you stop using android and start making your own good code!
Click to expand...
Click to collapse
I had a Pixel XL for over a year. Only kept it for Project FI. Bug ridden POS.
Sold it for half going price just so I could feel clean again.
Even if Samsung *used* to have sluggish Touchwiz in the past, at least it didn't have deal breaking bugs.
Don't even have to make my own code - some XDA roms had fixed this bug, as opposed to Google.
MJFox78 said:
I disabled the phone functionality too
I had a Samsung phone before as well (Note 8) and with that I had no problems with my hands free kit but instead the smartwatch lost the phone functionality after a few hours so I always had to reconnect it (basically the same problem but the other way round)... it's very frustrating that such a pretty basic thing doesn't work properly
I also tried this app: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect
but it didn't seem to make any difference, it didn't seem to make anything at all
I read that Android Pie is able to connect to more than one Bluetooth headset at a time so this should fix the issue after all
Click to expand...
Click to collapse
I am almost positive that if you had a somewhat similar problem on a Note 8, it's probably Google's fault.
I don't really use the 2 BT phone functionality for more than 30 min on average, but I've never had any problems on Note 7, GS6 or GS9, or even on a Pixel pre 7.0.2 android, when this bug was first introduced.
After 7.0.2, bluetooth stuff just broke everywhere. This bug, constant disconnects and reconnects, for some people music skips, for some doesn't even work, BT UI in Settings just crashing etc.
It's like Google replaced their BT programmer with a monkey at that point, or even a monkey's nephew.

So just because you cannot use 2 Bluetooth devices simultaneously to make phone calls, it's a deal breaker??? Lmao please please please go back to Samsung so we don't have to hear the whining anymore. Good luck with those bootloaders

General Q&A, tips, info Roll-up (Joying) FYT SC9853i

Last revised: 09 May 2020.
The models are manufactured/assembled by Joying, but the motherboard/MCU is made by FYT who also "make" the Android and system apps for the units. There are a number of FYT compatible units available, like Joying, Sinosmart, Zhan, Funrover, Flyaudio, Witson, T'eyes and multiple "unnamed/unbranded" units. Not all of the units of these companies are FYT units though.
This thread is not for discussing your issues in case "things" don't function or questions like "How can I ../ How do I ../Where can I find ../ etcetera. There are other threads for that. If you have good tips yourself, please add them.
Almost all Q&As and tips are collected from other or much older posts. Too many people to mention. Thanks all!
I hope this will remain a "work in progress"!
#1. Passwords:
Factory menu / Developer options: 3368
Backlight Current Adjustment: 5768
Door lock interference: 0000
To change home launcher: 8086
#2. Where can I find the latest (and/or older) firmwares for my Joying unit.
You will find them on the Joying website www.joyingauto.com inside the blog: Updated firmware.
#3. Should I always upgrade to the latest firmware?
Theoretically: YES. Bugs are fixed. New features are added. But..: sometimes new bugs are introduced.
#4. Are there other Howto's, Q&As, Tips available?
The Joying blog at https://www.joyingauto.com/blog/
The Youtube Joying Boyka channel.
The official Joying forum: https://forum-joyingauto.com/
Modding your Joying/FYT SC9853i unit without root: https://forum.xda-developers.com/an...modding-joying-fyt-sc9853i-unit-root-t3974357
#5. Will all my apps and data still be there when I flash my unit with a new firmware?
That depends on the contents of the file "updatecfg.txt" in the firmware. See the explanation in post #1 of Modding your Joying/FYT SC9853i unit without root
#6. Can I root my unit?
Yes, you can. See HowTo: Root Joying SC9853i Head Unit.
#7. I have my unit rooted. How can I (relatively) easy install mods or tweak my unit?
Use the "Joying_Extra_Tools" app (also JET apk) which allows you to install Radio, Bluetooth, main server (nokill) mods and tweak/optimize (immersive mode, overscan, DPI, etc.) your unit.
#8. All the apps are killed when the unit goes to deep-sleep. Can I change this?
The unit does indeed kill all apps upon going into "deep sleep", apart from a few system apps.
Solution 1
(No root required) By modifying the "skipkillapp.prop" as described in both post #1 and post #2 of Modding your Joying/FYT SC9853i unit without root, you can change this.
Solution 2
(No root required) Install a nokill mod using a prebuild flashable image from post #3 of the thread "Modding your Joying/FYT SC9853i unit without root". This mod deactivates the "kill_all_app" function in the main server app.
Solution 3
(root required) Install a nokill mod (using the JET apk). This mod deactivates the "kill_all_app" function in the main server app.
"Solution" 4
(No root required for "starting apps" activity) If you simply want "your" app available after deep sleep, a much "cleaner" way to do this is to use @bambapins FYTStarter apk that lets you autostart apps on "waking up" of the unit. See post #1149 of the "Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 32GB flash)" thread.
Alternative: You can assign any app to the "Navi app" setting inside the Joying settings. You can use Tasker/Easer/Llama/MacroDroid/Condi/Etcetera to start apps/do actions, etcetera after wake-up. Note that for some of these actions you need root access.
#9. I do not really care that apps are closed on going into deep sleep, but can I start some apps on waking up after deep sleep?
Like above topic: (No root required for "starting apps" activity) If you simply want "your" app available after deep sleep, a much "cleaner" way to do this is to use @bambapins FYTStarter apk that lets you autostart apps on "waking up" of the unit. See post #1149 of the "Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 32GB flash)" thread.
If you are rooted you can use FYTStarter to start the accessibility service. 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.
#10. Can I make modifications to the apps on my unit without root?
On these SC9853i units, you partially can. See this Modding your Joying/FYT SC9853i unit without root
#11. Are there Custom ROMs for this unit?
No, currently not. It is unlikely they will be created, but you never know.
#12. The unit starts some default apps on certain hardware keys or "system actions". Can I change this (without root)?
Yes, you can for a number apps and a number of SRC/MOD Steering Wheel keys. see the "FYT HW OneKey app". It doesn't need root, but will also work with root.
#13. I did something stupid and now my unit is in a boot loop or does not get past the boot logo. Help!
See post #4 in the "Modding your Joying/FYT SC9853i unit without root" thread.
#14. The Bluetooth app can only pair a few number of devices. Can I change this?
Yes, but your device needs to be rooted. @seb21 has modified the Bluetooth app (based on 17 Sept 2019 firmware) which allows to pair any OBD device. See this post in the "Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 32GB flash)" thread. This BT-app will only work till the next reboot, then it is completely disabled!
See also #27.
#15. Sleep mode: How much power is used? How long will it last? When does it really switch off?
This is mostly based on the previous Sofia 3GR and PX5 units, but I don't think it has changed as there was no change either between the (2) sofia model(s) and the PX5 model.
When switching off the unit it is not immediately in "deep sleep" mode. This takes about 30~60 seconds (on the PX5/Sofias ~4 minutes). In this period power usage is about 0.5~0.75A. When in "deep sleep" mode power consumption drops to 0.01~0.02A. A healthy battery can take this for at least a month.
After 5~7 days your unit will still be completely switched off resulting in a cold boot on starting your car. Just to make sure your battery is not drained. Nobody did ever exact measurements of this "switch off" period.
#16. A 3 seconds push on the PWR button switches off my unit, or a drag down (2X) from the notifiction bar enables me to shutdown the unit. Is there a difference with the Contact "switch off"?
Yes, there is. Pushing the PWR buton or dragging down the notification bar to shutdown the unit will only shutdown Android, not the hardware, and the energy consumption will still be above ~0.5A, but also makes it awake instantly. Switching off the car using your key, will bring the unit to "deep sleep". Then it will take 1-2 seconds to wake up again.
#17. I have a VW/Skoda/Seat unit with CAN-bus, but no Steering wheel buttons on my steering wheel. Will a 3rd party Steering wheel controller work?
No, not directly. These units come with a "VW motherboard" and do not listen to the Key1/Key2 wires, but only to the CAN-bus. Disconnecting the wires from the CAN-bus to such a 3rd part SWC-controller will not help.
The best solution requires some technical skills and involves an Arduino Micro-Pro device and is described in the [Joying for VW] Universal steering wheel controls with arduino by @bambapin.
(For a PX5: Another option is to resolder a resistor on your motherboard as described here).
#18. On long drives or high external temperatures (in the tropics) my unit doesn't work fluent anymore and apps start "stuttering" (voice) or slowing down. What is happening?
Install an app that wil monitor the temperature of your unit. The chips/motherboards in these units can get really hot. The CPU will "throttle" itself to lower CPU-cycles to cool down. Another problem of too high temperatures is that the lifespan of the unit will be shortened. And still another issue is that these units are "cold soldered", meaning that due to tension in the soldering due to the high temperatures, CPU soldering connections might be broken causing a non-functioning or mal-functioning unit. There are several threads on this forum giving examples of heat-sinks, fans and combinations of both.
#19. How can I use split-screen on this unit?
solution 1
Use the "Touch Assistant apk", which is the "white dot" floating top-left in your screen. It has a split-screen option and it remembers! that you are in splitscreen mode.
Solution 2
Start your "first" app and "second" app. Go to the task-manager (rectangle) in the top-right of the notification bar. It will show your active and last-used (but possibly closed) apps. Drag your "first" app to the left. In the right window you will now find the task manager with the other apps. Select the app you want on the right. (Of course this also works the other way round if you drag your first app to the right).
Note: This version only supports a 50%/50% split. Some Androids support 33%/66% splits as well.
#20. With every key press I hear this annoying beep. How do I remove it?
Solution 1
BEFORE (re)flashing your unit, edit the file “config.txt” from the firmware zip.
Add the line "ro.fyt.amp_switch=0" (or change that line from "ro.fyt.amp_switch=1" to this "ro.fyt.amp_switch=0")
Solution 2
1. Open the Settings app
2. Go to Device -> Sound -> Keypad Tone
3. Switch it off
#21. What is the default DPI on these units? Some apps/fonts seem too big or too small for the screen.
The default DPI is 160 for the 1024x600 units. Some screens are 1280x720. Some badly written apps (including my own JET apk) do not display correctly. On the 1280x720 screens you could go to a DPI of 180 or 200. Above that the Joying/FYT apps will not be displayed correctly. Changing the DPI is currently only possible if you have your unit rooted!
#22. When my unit boots, the radio is always started. Can I prevent this from happening?
You can't stop this. Not on a Joying and not on any other unit. And note that the radio app is actually only an interface that forwards commands to and receives data from the radio chip via the MCU. It is not an active app like your mediaplayer that does everything in Android.
When the unit boots, the hardware is up and running long before Android is. That means that the radio chip and amplifier are already working before Android has even booted. That is why you hear the radio. And that is why every manufacturer starts the radio app on boot: to enable you to mute the radio channel from the app.
The radio is never switched off as it cannot be switched off. It is only muted.
#23. Can I modify the lines/frames I see when having a reverse camera and driving backwards?
Yes, you can, but not from the app or Settings.
Unzip "190000000_com.syu.us.apk".
In /res/drawable you will find dl1.png to dl35.png, and dr1.png to dr35.png (left and right). These are used for the "frames" when driving backwards.
Change them, but keep the same resolution (size).
rezip the apk
use the "Creating an Allapp.pkg ..." from the "Modding your Joying/FYT....". Or in case you have rooted your unit you can directly replace the apk on your unit.
(There are more "frame" images in there, but I have no idea how to use them. Of course you could rename them if you want to use these)
#24. I only want to flash the MCU firmware, not the rest of the firmware. Can I do that?
There can be several reasons why you want to do this. Only(!) copy the "Stm32ud.bin" and the "lsec6521update" to a clean FAT32 formatted USB-stick/SD-card and put it in your unit. The flashing will start automatically.
#25. I want to flash a new firmware, but NOT the MCU firmware
Use your firmware of choice but remove(!) the "Stm32ud.bin" from the USB-stick/SD-card before flashing.

#26. Google Contacts sync? DON'T DO IT !!
When you flash your unit, you will most probably setup your Google account (Settings -> User -> Accounts). By default most of the synchronizing is switched on, including the Contacts sync.
Disable this as soon as possible!! Already since 2016 this is a bug in the FYT software. With sync on, the unit will delete all your contacts. (see video by John Molberg).
How to prevent this?
After setting up your google account, immediately disable Contacts sync.
When connecting your phone with your unit via Bluetooth, you can enable contact sync via BT.
Once your contacts have synced, I advice to alsodisable contact synv via BT. (Press the gear icon when connected and disable contact sync).
Note: After firmware flash always check your Google accounts contacts sync again. (The 20200407 erased my contacts again)
Tip: Export your contacts before firmware flash.
See this youtube video from John Molberg about the deletion.
#27. Improved Bluetooth Pairing (still far from perfect)
This is not a great solution. It is more a simple work-around.
Before flashing your firmware, you should update one line in the config.txt.
Set line "sys.fyt.bluetooth_type=1" to "sys.fyt.bluetooth_type=0". Now flash the firmware.
If you already flashed the firmware, you can do a "config.txt flash only" using my zip attached to this post.
See also #14.
#28. Order of Bluetooth pairing
Say you have an OBD2 dongle, it sometimes pairs immediately and it sometimes doesn't.
Disclaimer: Some will never pair. The Bluetooth ID-string need to contain OBD.
But:
your dongle is compatible, but it will still not pair.
your dongle is compatible but it will only pair using pincode 1234 (or whatever code).
First in the BT contect settings "forget" your paired phone(s). (Not only unpair but really remove them).
Now pair your OBD2 dongle. If necessary, first set the pincode in your unit to the pincode of your OBD2 dongle,
After having successfully paired your OBD2 dongle , you can now pair your phone(s) using the same pincode.
#29. Google Play Store does not start downloading.
This is a very annoying problem which I have regularly. It can be solved though.
Below options can be tried starting from the first. if it doesn't work, try the others one by one.
In the Play Store app, tap the "hamburger" menu (3-lines top-left) and select "My apps and games" (But probably you were already there). Remove all apps from the update-queue. Reboot.
Turn off auto-update for your apps.
Go to Settings->Apps, and clear cache and data from the Google Play Store app. Reboot/retry.
Go to Settings->Apps, and clear cache and data from Google Play Services (You might need to enable "show system (apps)"). Reboot/retry.
Uninstall Google Play Store updates.
Switch off downloading "only via Wi-Fi" (if also using a SIM card or if you can download via the hot-spot of your phone).
Turn off 4G data transfer and turn it on again (if you use the hot-spot from your phone, turn Wi-Fi off/on and/or mobile data off/on).
Sign out of your Google Account, restart your head unit and sign in again.
And you can look at this Google support article, or this one (more steps ..)

#2 reserved

#3 reserved

Nice Thread, will help a lot of people!

great thread!

Thank you for this! I realize you don't want people asking questions in this thread but more about posting solutions, so i'll attempt to add two I think are missing and you can always add your input:
Q: Everytime the head unit enters deep sleep, apps granted the Accessibility permission (such as Tasker, Automate, Launchers) might lose this permission. Anyway to prevent this?
A: This is due to services being shut off (post) when the MCU calls for deep sleep. There is no way to stop this. However, you can use FYTStarter APK (here) for restoring accessibility or other issues between 'deep sleep'.
Q: Third party apps and external keyboards are unable to control volume or other media controls. How to overcome?
A: Volume and some other keys/controls are preempted by the Joying/FYT software. You need to interact with the Joying/FYT services to control these aspects. This post here shows an example apk that can interact with Joying/FYT services to control volume and other aspects (and another version here and some easy to use apk for volume that are tested working here). You can write your own APK using same methods or take advantage of this apk to send intents/commands to control volume and so on. You can use Tasker or Automate to provide this control to other things. For example, use Automate to intercept 'VOL UP' from an external keyboard and then use APK command to send 'VOL UP' to Joying/FYT service (and thus restoring ability to control volume from external controls like Joycon controller or external keyboards).
Q: How can I interface Steering Wheel Controls (Can Bus or other) not supported by Joying/FYT drivers
A: You can always use Joycon interface adapter (http://www.exinterface.com/cpjexr/) to convert SWC and CAN bus commands into USB keyboard inputs. The Joying/FYT work with this but you do need to use third party apps to map keyboard inputs into meaningful actions (start an app for example). As mentioned in above Question, media keys might not work directly from keyboard (unable to control volume for example) and you need to work around that with additional APK, but it can be done.
Q: is there anyway to setup so that when i receive a bluetooth call, i can go back to [other app]?
A: If you have set Waze or [other app] as your Navi app (via Joying settings menu), tapping the Navi button on your screen should allow you to go back to Waze. But also: some apps can be allowed to take over the phone function. Example is Magic Earth and Osmand+. For both I can allow them to make/receive calls. It means that you see a bar on the bottom of the screen, but it is actually not the Joying dialer. So I am IN that app. Google Maps can do that as well and I assume Waze might be able to do is as well too.
Did you give Waze that authorization when Waze asked for it during first loading it? Because if you did, you are in Waze with a phone call overlay at the bottom. Therefore: you cannot go to Waze because you are already in Waze. (Quote from Surfer post)

i've got a question.
if i download the lastetst version of update without never updating nothing, it will be ok?

maor23 said:
i've got a question.
if i download the lastetst version of update without never updating nothing, it will be ok?
Click to expand...
Click to collapse
I really don't understand what you are asking.

surfer63 said:
I really don't understand what you are asking.
Click to expand...
Click to collapse
i see there is many version of updates there, and i ask if i can only update with the last version or should i go over one by one with the updates ?

maor23 said:
i see there is many version of updates there, and i ask if i can only update with the last version or should i go over one by one with the updates ?
Click to expand...
Click to collapse
All updates are full updates. You can skip all intermediate updates and immediately go for the last version.
Note though that you have to look at the MCU version: G32 or G32 (assuming you have a Joying SC9853i)

surfer63 said:
All updates are full updates. You can skip all intermediate updates and immediately go for the last version.
Note though that you have to look at the MCU version: G32 or G32 (assuming you have a Joying SC9853i)
Click to expand...
Click to collapse
How can i know my mcu version? Like i see, in the last update from april 2020, there is only one link to download so i guess it good for all versions, no?
I also want to get some tips of it, maybe some recommended apps and etc..

maor23 said:
How can i know my mcu version? Like i see, in the last update from april 2020, there is only one link to download so i guess it good for all versions, no?
I also want to get some tips of it, maybe some recommended apps and etc..
Click to expand...
Click to collapse
There is no MCU update in the latest firmware, so you are correct.
No tips about recommended apps. Other threads are for that.
And personally I consider it ********. Everyone has his own preference for certain apps.

surfer63 said:
There is no MCU update in the latest firmware, so you are correct.
No tips about recommended apps. Other threads are for that.
And personally I consider it ********. Everyone has his own preference for certain apps.
Click to expand...
Click to collapse
so how can i know if i need os update or mcu update?

maor23 said:
so how can i know if i need os update or mcu update?
Click to expand...
Click to collapse
Check your system info.
You only need an OS or MCU update if something is bothering you. If everything works fine for you, don't bother to upgrade.
For me the necessity to upgrade is two-fold:
fixes for bugs that bother me like Google voice call. But after 3 firmware upgrades claiming they fixed it, they still haven't fixed that. Although I hardly answer to calls in the car, and almost never make calls, it is terribly annoying that every other brand unit (MTC, QD, Atoto, etc) can do that, including all built-in car brand media-systems, but not the FYTs.
Android security fixes. It is still not clear to me whether FYT includes security fixes in their new firmwares by patching their code with the offical Android security fixes. As I hope they are doing that, I still flash every new firmware to my unit. But that's just a blind hope that they do apply the security patches.

surfer63 said:
Last revised: 22 December 2019.
The models are manufactured/assembled by Joying, but the motherboard/MCU is made by FYT who also "make" the Android and system apps for the units. There are number of FYT compatible units available, like (of course) Joying, Sinosmart, Zhan, Funrover, Witson and multiple "unnamed/unbranded" units. Not all of the units of these companies are FYT units though.
This thread is not for discussing your issues in case "things" don't function or questions like "How can I ../ How do I ../Where can I find ../ etcetera. There are other threads for that. If you have good tips yourself, please add them.
Almost all Q&As and tips are collected from other or much older posts. Too many people to mention. Thanks all!
I hope this will remain a "work in progress"!
Passwords:
Factory menu / Developer options: 3368
Backlight Current Adjustment: 5768
Door lock interference: 0000
To change home launcher: 8086
Where can I find the latest (and/or older) firmwares for my Joying unit.
You will find them on the Joying website www.joyingauto.com inside the blog: Updated firmware.
Should I always upgrade to the latest firmware?
Theoretically: YES. Bugs are fixed. New features are added. But..: sometimes new bugs are introduced.
Are there other Howto's, Q&As, Tips available?
The Joying blog at https://www.joyingauto.com/blog/
The Youtube Joying Boyka channel.
The official Joying forum: https://forum-joyingauto.com/
Modding your Joying/FYT SC9853i unit without root: https://forum.xda-developers.com/an...modding-joying-fyt-sc9853i-unit-root-t3974357
Will all my apps and data still be there when I flash my unit with a new firmware?
That depends on the contents of the file "updatecfg.txt" in the firmware. See the explanation in post #1 of Modding your Joying/FYT SC9853i unit without root
Can I root my unit?
Yes, you can. See HowTo: Root Joying SC9853i Head Unit.
I have my unit rooted. How can I (relatively) easy install mods or tweak my unit?
Use the "Joying_Extra_Tools" app (also JET apk) which allows you to install Radio, Bluetooth, main server (nokill) mods and tweak/optimize (immersive mode, overscan, DPI, etc.) your unit.
All the apps are killed when the unit goes to deep-sleep. Can I change this?
The unit does indeed kill all apps upon going into "deep sleep", apart from a few system apps.
Solution 1
(No root required) By modifying the "skipkillapp.prop" as described in both post #1 and post #2 of Modding your Joying/FYT SC9853i unit without root, you can change this.
Solution 2
(No root required) Install a nokill mod using a prebuild flashable image from post #3 of the thread "Modding your Joying/FYT SC9853i unit without root". This mod deactivates the "kill_all_app" function in the main server app.
Solution 3
(root required) Install a nokill mod (using the JET apk). This mod deactivates the "kill_all_app" function in the main server app.
"Solution" 4
(No root required for "starting apps" activity) If you simply want "your" app available after deep sleep, a much "cleaner" way to do this is to use @bambapins FYTStarter apk that lets you autostart apps on "waking up" of the unit. See post #1149 of the "Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 32GB flash)" thread.
Alternative: You can assign any app to the "Navi app" setting inside the Joying settings. You can use Tasker/Easer/Llama/MacroDroid/Condi/Etcetera to start apps/do actions, etcetera after wake-up. Note that for some of these actions you need root access.
I do not really care that apps are closed on going into deep sleep, but can I start some apps on waking up after deep sleep?
Like above topic: (No root required for "starting apps" activity) If you simply want "your" app available after deep sleep, a much "cleaner" way to do this is to use @bambapins FYTStarter apk that lets you autostart apps on "waking up" of the unit. See post #1149 of the "Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 32GB flash)" thread.
If you are rooted you can use FYTStarter to start the accessibility service. 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.
Can I make modifications to the apps on my unit without root?
On these SC9853i units, you partially can. See this Modding your Joying/FYT SC9853i unit without root
Are there Custom ROMs for this unit?
No, currently not. It is unlikely they will be created, but you never know.
The unit starts some default apps on certain hardware keys or "system actions". Can I change this (without root)?
Yes, you can for a number apps and a number of SRC/MOD Steering Wheel keys. see the "FYT HW OneKey app". It doesn't need root, but will also work with root.
I did something stupid and now my unit is in a boot loop or does not get past the boot logo. Help!
See post #4 in the "Modding your Joying/FYT SC9853i unit without root" thread.
The Bluetooth app can only pair a few number of devices. Can I change this?
Yes, but your device needs to be rooted. @seb21 has modified the Bluetooth app (based on 17 Sept 2019 firmware) which allows to pair any OBD device. See this post in the "Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 32GB flash)" thread.
Sleep mode: How much power is used? How long will it last? When does it really switch off?
This is mostly based on the previous Sofia 3GR and PX5 units, but I don't think it has changed as there was no change either between the (2) sofia model(s) and the PX5 model.
When switching off the unit it is not immediately in "deep sleep" mode. This takes about 30~60 seconds (on the PX5/Sofias ~4 minutes). In this period power usage is about 0.5~0.75A. When in "deep sleep" mode power consumption drops to 0.01~0.02A. A healthy battery can take this for at least a month.
After 5~7 days your unit will still be completely switched off resulting in a cold boot on starting your car. Just to make sure your battery is not drained. Nobody did ever exact measurements of this "switch off" period.
A 3 seconds push on the PWR button switches off my unit, or a drag down (2X) from the notifiction bar enables me to shutdown the unit. Is there a difference with the Contact "switch off"?
Yes, there is. Pushing the PWR buton or dragging down the notification bar to shutdown the unit will only shutdown Android, not the hardware, and the energy consumption will still be above ~0.5A, but also makes it awake instantly. Switching off the car using your key, will bring the unit to "deep sleep". Then it will take 1-2 seconds to wake up again.
I have a VW/Skoda/Seat unit with CAN-bus, but no Steering wheel buttons on my steering wheel. Will a 3rd party Steering wheel controller work?
No, not directly. These units come with a "VW motherboard" and do not listen to the Key1/Key2 wires, but only to the CAN-bus. Disconnecting the wires from the CAN-bus to such a 3rd part SWC-controller will not help.
The best solution requires some technical skills and involves an Arduino Micro-Pro device and is described in the [Joying for VW] Universal steering wheel controls with arduino by @bambapin.
(For a PX5: Another option is to resolder a resistor on your motherboard as described here).
On long drives or high external temperatures (in the tropics) my unit doesn't work fluent anymore and apps start "stuttering" (voice) or slowing down. What is happening?
Install an app that wil monitor the temperature of your unit. The chips/motherboards in these units can get really hot. The CPU will "throttle" itself to lower CPU-cycles to cool down. Another problem of too high temperatures is that the lifespan of the unit will be shortened. And still another issue is that these units are "cold soldered", meaning that due to tension in the soldering due to the high temperatures, CPU soldering connections might be broken causing a non-functioning or mal-functioning unit. There are several threads on this forum giving examples of heat-sinks, fans and combinations of both.
How can I use split-screen on this unit?
solution 1
Use the "Touch Assistant apk", which is the "white dot" floating top-left in your screen. It has a split-screen option and it remembers! that you are in splitscreen mode.
Solution 2
Start your "first" app and "second" app. Go to the task-manager (rectangle) in the top-right of the notification bar. It will show your active and last-used (but possibly closed) apps. Drag your "first" app to the left. In the right window you will now find the task manager with the other apps. Select the app you want on the right. (Of course this also works the other way round if you drag your first app to the right).
Note: This version only supports a 50%/50% split. Some Androids support 33%/66% splits as well.
With every key press I hear this annoying beep. How do I remove it?
Solution 1
BEFORE (re)flashing your unit, edit the file “config.txt” from the firmware zip.
Add the line "ro.fyt.amp_switch=0" (or change that line from "ro.fyt.amp_switch=1" to this "ro.fyt.amp_switch=0")
Solution 2
1. Open the Settings app
2. Go to Device -> Sound -> Keypad Tone
3. Switch it off
What is the default DPI on these units? Some apps/fonts seem too big or too small for the screen.
The default DPI is 160 for the 1024x600 units. Some screens are 1280x720. Some badly written apps (including my own JET apk) do not display correctly. On the 1280x720 screens you could go to a DPI of 180 or 200. Above that the Joying/FYT apps will not be displayed correctly. Changing the DPI is currently only possible if you have your unit rooted!
When my unit boots, the radio is always started. Can I prevent this from happening?
You can't stop this. Not on a Joying and not on any other unit. And note that the radio app is actually only an interface that forwards commands to and receives data from the radio chip via the MCU. It is not an active app like your mediaplayer that does everything in Android.
When the unit boots, the hardware is up and running long before Android is. That means that the radio chip and amplifier are already working before Android has even booted. That is why you hear the radio. And that is why every manufacturer starts the radio app on boot: to enable you to mute the radio channel from the app.
The radio is never switched off as it cannot be switched off. It is only muted.
Can I modify the lines/frames I see when having a reverse camera and driving backwards?
Yes, you can, but not from the app or Settings.
Unzip "190000000_com.syu.us.apk".
In /res/drawable you will find dl1.png to dl35.png, and dr1.png to dr35.png (left and right). These are used for the "frames" when driving backwards.
Change them, but keep the same resolution (size).
rezip the apk
use the "Creating an Allapp.pkg ..." from the "Modding your Joying/FYT....". Or in case you have rooted your unit you can directly replace the apk on your unit.
(There are more "frame" images in there, but I have no idea how to use them. Of course you could rename them if you want to use these)
I only want to flash the MCU firmware, not the rest of the firmware. Can I do that?
There can be several reasons why you want to do this. Only(!) copy the "Stm32ud.bin" and the "lsec6521update" to a clean FAT32 formatted USB-stick/SD-card and put it in your unit. The flashing will start automatically.
I want to flash a new firmware, but NOT the MCU firmware
Use your firmware of choice but remove(!) the "Stm32ud.bin" from the USB-stick/SD-card before flashing.
Click to expand...
Click to collapse
Hello ! did you have found how to replace Joying setting app from original android settings app ? thank you !

Lucasmrn said:
Hello ! did you have found how to replace Joying setting app from original android settings app ? thank you !
Click to expand...
Click to collapse
No. That is no longer possible. That was only possible on the Intel Sofia models.

surfer63 said:
No. That is no longer possible. That was only possible on the Intel Sofia models.
Click to expand...
Click to collapse
Thank you for reply, and I have a last question, I have put other firmware ( Teyes SPRO). Firmware was very good and fully functionnal except bluetooth.
I have mod allapp.pkg and fytmanufacturer with my number of head unit, the message "ui and mcu does not match" disapear is very good, but i don't now how to configure my Bluetooth for recognize in this firmware.
Bluetooth version is: GOC_V1.0/2019:07:18:16:59:52_gocsdk2
When i put other firmware he say: "unknow blink" How i can solve it ? mod file ?
Thank you for help.

Lucasmrn said:
Thank you for reply, and I have a last question, I have put other firmware ( Teyes SPRO). Firmware was very good and fully functionnal except bluetooth.
I have mod allapp.pkg and fytmanufacturer with my number of head unit, the message "ui and mcu does not match" disapear is very good, but i don't now how to configure my Bluetooth for recognize in this firmware.
Bluetooth version is: GOC_V1.0/2019:07:18:16:59:52_gocsdk2
When i put other firmware he say: "unknow blink" How i can solve it ? mod file ?
Click to expand...
Click to collapse
The only reference I have is the bluetooth "blink_config.ini" inside "/system/res/bluetooth". Please check the differences between your original file and the Teyes SPRO file.
I am also very interested in this. Last week (or so) I already wrote that the T'eyes Pro FYT software seems to be way ahead of the Joying software. Can you share some insights? Pros? Cons?
Does Google voice calling work? And did it work on the Joying firmware?

surfer63 said:
The only reference I have is the bluetooth "blink_config.ini" inside "/system/res/bluetooth". Please check the differences between your original file and the Teyes SPRO file.
I am also very interested in this. Last week (or so) I already wrote that the T'eyes Pro FYT software seems to be way ahead of the Joying software. Can you share some insights? Pros? Cons?
Does Google voice calling work? And did it work on the Joying firmware?
Click to expand...
Click to collapse
Thank you for Help my friend, I will try now. I don't Have a Joying head unit, it's a Ullgo head unit with fytmanufacturer = 108
I will get back to you quickly with specific details, link and all informations i can give you. I have test many sort of firmware on this forum but translation is very difficult on russian forum : https://4pda.ru/forum/index.php?showtopic=936715. This russian forum is a big library for mod our SC9853 head unit !
But I will test the best and after i will get back
Sorry if my english is bad. I'm French

Question Disable Bluetooth Autoplay? Still?

I recently upgraded from my trusty Note 8 and am finding the new Android version to be completely underwhelming (a common theme, I'm finding). I can't really think of any actual improvements to my daily user experience and two things have gotten worse enough that I have been researching solutions to them to no avail. The first is the main topic of this thread. My older Bluetooth car stereo (not Android auto, but apparently that is equally as broken) sends an "autoplay on connect" request. No individual app autoplay setting seems to matter, it is a system problem. On the Note 8 this was also the case, however it would only actually play if the app was open (present in the task switch windows). This was occasionally annoying but now it is much much worse. What happens now on the S22U is that apps I have long since closed will just appear to open zombielike and autoplay. Even when I am in the middle of opening a music app, e.g. a podcast that I was listening to yesterday will just start playing because it was the last used app.
I can't believe that it's 2022 and Android doesn't just have this fixed yet it has been underdeveloped for YEARS now. Why can't it just be a system wide setting? And why on earth does it insist on playing audio even if it was PAUSED before Bluetooth is disconnected? I have a feeling there is nothing I can do about this, but I wanted to vent.
I mentioned there was a second most annoying issue with the new version of Android. This is that the "double tap to switch" to previous app window is inexplicably slower than it used to be, to the point you might as well not use it. I used to do that constantly and it was very effective. Why on earth they removed this feature is beyond me.
If anyone has a current solution to either of these problems please lmk.

I've also have this issue... Both with the Pixel 6 Pro and same thing when I switched to the S22 Ultra. I'm inclined to think it's an issue specific with Android 12. On my Pixel 5 (using Android 11), autoplay when connecting to bluetooth worked every time. Even with having setup a Bixby routine to autoplay upon connecting to a specific bluetooth device, it does not always work... It's frustrating.