I just bought my first ever Android phone, Acer Liquid Zest Plus.
It's not quite working in the limited ways I was hoping it to work.
First, I drive a Honda, which has handsfreelink system for connecting the phone to the car. The phone connects to handsfreelink ok, but then shows some weird behavior, in that when using the car's controls to place a call through handsfreelink, handsfreelink immediately apparently hangs up the call (i.e. the car's display shows that it hung up the call). However, this does not actually hang up the call on the phone itself, as the call gets placed nonetheless and when someone picks up on the other side, I can have a conversation through the car's audio system. Seems to almost work, but the weird behavior just described means that I can't hang up a call without pulling the phone out of my pocket and hanging it up from the phone (as opposed to hanging up using the car's controls) while driving, which takes a lot away from the point of it all.
What could be the issue with this? Note that I had a Blackberry Passport before, which used to work all as intended with handsfreelink, and my family member's iPhone 7 Plus also works as intended with handsfreelink. Is it that my Acer Liquid Zest Plus does not have the necessary bluetooth profile/stack to works with Honda's handsfreelink? Is it that handsfreelink proprietary to Honda and uses something unique, as opposed to being a generic bluetooth device of the kind? Is a bluetooth device link this, used by other auto manufacturers, feature the same generic bluetooth thing, or is this something only Holda can possibly answer for me?
Could updating the phone solve this issue? If so, how? I go into Settings -> About phone -> System updates and it tells me that my device is up to date (I did not update it since pulling it out of the box). I notice that it's on Android 6.0 , and a quick Google search showed some discussions that it is highly unlikely that the phone will get newer Android update. The "Android security patch level" shown in "About phone" says December 5, 2016. That's a long time without a security patch. Should I, and is it possible to, update the phone?
I've heard of rooting an Android device and installing custom Roms before. Where can I find a guide for my device and the custom Rom files? I am hoping this might solve my issue with handsfreelink.
I know I am all around the place with my questions, but essentially, the issue I am having is that bluetooth connection to my car's audio system does not work as expected, and I am wondering how I might fix it. I am wondering if an OS update (either official version by manufacturer or a widely-used custom Rom) might solve this issue, or simply adding an extra bluetooth profile to the phone.
A solution would be awesome, but I'd be asking too much if I was hoping for that. Instead, if anyone can just provide me some pointers in terms of how to do research on what I should be doing to solve this, or clarify some concepts (to the extent you can tell I got it wrong from reading this post) for me, it would be really appreciated.
I've already been to Honda's handsfreelink website and Acer's support page for this product and there's nothing helpful there.
Thank you very much.
ACER
monotious said:
I just bought my first ever Android phone, Acer Liquid Zest Plus.
It's not quite working in the limited ways I was hoping it to work.
First, I drive a Honda, which has handsfreelink system for connecting the phone to the car. The phone connects to handsfreelink ok, but then shows some weird behavior, in that when using the car's controls to place a call through handsfreelink, handsfreelink immediately apparently hangs up the call (i.e. the car's display shows that it hung up the call). However, this does not actually hang up the call on the phone itself, as the call gets placed nonetheless and when someone picks up on the other side, I can have a conversation through the car's audio system. Seems to almost work, but the weird behavior just described means that I can't hang up a call without pulling the phone out of my pocket and hanging it up from the phone (as opposed to hanging up using the car's controls) while driving, which takes a lot away from the point of it all.
What could be the issue with this? Note that I had a Blackberry Passport before, which used to work all as intended with handsfreelink, and my family member's iPhone 7 Plus also works as intended with handsfreelink. Is it that my Acer Liquid Zest Plus does not have the necessary bluetooth profile/stack to works with Honda's handsfreelink? Is it that handsfreelink proprietary to Honda and uses something unique, as opposed to being a generic bluetooth device of the kind? Is a bluetooth device link this, used by other auto manufacturers, feature the same generic bluetooth thing, or is this something only Holda can possibly answer for me?
Could updating the phone solve this issue? If so, how? I go into Settings -> About phone -> System updates and it tells me that my device is up to date (I did not update it since pulling it out of the box). I notice that it's on Android 6.0 , and a quick Google search showed some discussions that it is highly unlikely that the phone will get newer Android update. The "Android security patch level" shown in "About phone" says December 5, 2016. That's a long time without a security patch. Should I, and is it possible to, update the phone?
I've heard of rooting an Android device and installing custom Roms before. Where can I find a guide for my device and the custom Rom files? I am hoping this might solve my issue with handsfreelink.
I know I am all around the place with my questions, but essentially, the issue I am having is that bluetooth connection to my car's audio system does not work as expected, and I am wondering how I might fix it. I am wondering if an OS update (either official version by manufacturer or a widely-used custom Rom) might solve this issue, or simply adding an extra bluetooth profile to the phone.
A solution would be awesome, but I'd be asking too much if I was hoping for that. Instead, if anyone can just provide me some pointers in terms of how to do research on what I should be doing to solve this, or clarify some concepts (to the extent you can tell I got it wrong from reading this post) for me, it would be really appreciated.
I've already been to Honda's handsfreelink website and Acer's support page for this product and there's nothing helpful there.
Thank you very much.
Click to expand...
Click to collapse
Acer is just the brand and few software smartphonne.they just order big amount of phones and sell them. the phone shows as Shanghai Huaqin Telecom Technology Co.,Ltd),have seen this on my old --vodaphonne-.The only emergenncy update from january 05 2018 and this is as far you go with ACER. YOU will never get any update .The name LIQUID is there PR name of there LAUNCHER,that´s all.ROOTING??? no point,waste of time no one will till today do it. Have the same phone and feel that I did a mistake and lost money.ACER stopped to sell smartphones. If you want to modiffy the phone the LAWNCHAIR launcher is good ,aswell others. But keep in mind that will be always android 6 and no security updates
Freudeauf2 said:
Acer is just the brand and few software smartphonne.they just order big amount of phones and sell them. the phone shows as Shanghai Huaqin Telecom Technology Co.,Ltd),have seen this on my old --vodaphonne-.The only emergenncy update from january 05 2018 and this is as far you go with ACER. YOU will never get any update .The name LIQUID is there PR name of there LAUNCHER,that´s all.ROOTING??? no point,waste of time no one will till today do it. Have the same phone and feel that I did a mistake and lost money.ACER stopped to sell smartphones. If you want to modiffy the phone the LAWNCHAIR launcher is good ,aswell others. But keep in mind that will be always android 6 and no security updates
Click to expand...
Click to collapse
your bluetooth -you have to install a app from third party and then configure the rest in the app and in setting device.Importend timer schould be always set as on in bluetooth .Standard is few minutes.good luck
---------- Post added at 02:23 PM ---------- Previous post was at 02:06 PM ----------
Freudeauf2 said:
your bluetooth -you have to install a app from third party and then configure the rest in the app and in setting device.Importend timer schould be always set as on in bluetooth .Standard is few minutes.good luck
Click to expand...
Click to collapse
To keep all your apps uptodate I use from FDROID app the YALP STORE ,there you can in settings update your system apps,as I sad this is the way as far you go with ACER. Hope it helps
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
Update 25-11-21: My friend told me that there are already some hardware-based physical tools that implement JTAG (IEEE 1149.1). I couldn't be able to say more about this because know nothing about electronics. (Those are very scarse to get where I live).
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based? Something resembling the POST (Power-On Self-Test) performed when a computer boots up, but be it done for testing and information gathering arbitrarily.
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!
ppdmartell said:
I'm recently entering this world of mobile phones and I was struggling with a phone which was unable to get the carrier signal. And a friend of mine which has been in this world for like 6 years now said: "It has to be a problem with the modem (hardware integrated component to communicate with the carrier)". By the way, he reached this conclussion after several practical testing without any successfully result. Coincidently he had a complete board for that cellphone model and after a replacement, the phone was able to have reception (also call and receive). But this was a radical solution, like formatting a PC because of one of the installed programs is just misbehaving.
So my doubt: Is there any hardware testing or diagnostic tool capable of interact with each (or several) components on the board and performance several actions and get their status?
For instance, let's say, before replacing the entire board from the example before, we were aiming to check the integrated modem status and if possible send instructions to send and receive instructions from the carrier. Can this be done? Be it this testing and diagnostic tool software or hardware based?
Full disclosure, before replacing the entire board we hard reset and also flashed the phone, without any successfull outcome. We spent like 4 days banging our heads against the wall. With such a hypothetic tool we could have saved ourselves a lot of time and effort. Maybe such a tool already exists and here I am posting out of ignorance. In both cases, any help is appreciated.
PS: I used the term modem in this post but I don't truly know if this is the proper term to refer, my apologies in advance.
PS1: I stumbled upon this tool named PC-Doctor but the Android version has to be installed in the phone's Android OS. But almost all phones we receive are close to dead (logo stuck, boot loop, FRP bypassing required), so installing an APK probably would not be an optimal solution here.
Thanks in advance!
Click to expand...
Click to collapse
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.
Droidriven said:
When you say modem, that could be taken to mean two things.
1) it could refer to the radio, the actual radio hardware component.
2) it could refer to the modem software that is part of your stock firmware and controls the RIL(Radio Interface Layer).
Typically, when we in this community say "modem", we are referring to the modem software. When we are referring to the hardware, we say "radio".
In the case of your device, it could be that you had the proper radio hardware and that it was "able" to function but possibly your modem software was not correct. Or it could have been that you did have the correct modem software installed but your radio hardware component was actually damaged or not able to function.
If it was an issue with improper modem software, you could have potentially downloaded and flashed the correct modem software to solve the issue.
If it was an actual fault in the radio hardware, switching the motherboard or at least unsoldering the radio component and replacing it with a new radio component is the correct solution.
If the device was from a different country/region or if the device was from a different carrier than the carrier that you were trying to activate it with, it was probably just a case of needing to flash a compatible modem software to work in your country/region or on your carrier network.
Yes, there are tools to diagnose the hardware but they are generally software based and are useless to diagnose the device if it doesn't at least power on and function in some manner. I know there are android apps available that can be used to test/diagnose the internal hardware components but they all probably require rooting the device.
It stands to reason that there should be various PC software based android hardware component testing/diagnostic tools that are used via connecting the device to PC but I've never looked into that or ever had a need for them.
As for hardware based tools to test or diagnose Android based hardware components, I'm not versed in what they could be, but I'm fairly certain that they exist and are used, it would not make any sense if they did not exist.
A Google search for:
"Android hardware testing and diagnostic tools"
Should find lots of tools to start researching.
Click to expand...
Click to collapse
Honestly I didn't know radio was the proper term to refer that hardware component. Now I do and thanks to you.
However, in this case I just used a practical problem to communicate my idea. I should have expressed myself in a better way. The underlying issue was the diagnostic tool itself, and not the radio problem I used, maybe like some sort of low-level query-based tool to test and diagnose the components.
And I also should have done some research in google before posting here too. Maybe I got lucky. Just in case I could find any solution to my issue, I will gladly post it here.
Thanks for the reply.