Related
I have a headunit in my car with Android 6.0.1 from the manufacturer KSP and I have been looking in the forum but I really do not clarify much. My intention is to activate a screensaver and a program for detection of radars so that it run immediately after starting the unit; with this I would already be happy (the unit erases the software in memory when it comes out of sleep mode).
I discover this files in my stock rom of the radio (see photo). It can help me for my problem?. How I can do it?
Silver_ said:
I have a headunit in my car with Android 6.0.1 from the manufacturer KSP and I have been looking in the forum but I really do not clarify much. My intention is to activate a screensaver and a program for detection of radars so that it run immediately after starting the unit; with this I would already be happy (the unit erases the software in memory when it comes out of sleep mode).
I discover this files in my stock rom of the radio (see photo). It can help me for my problem?. How I can do it?
Click to expand...
Click to collapse
I don't know. First you can try opening the files. They should be readable.
Hi, I have an px5 xtrons and a problem with the clock on Android 8 (stock and malaysk rom) When I restart the car the unit have the old time of shutdown. (Unit connected to battery and no problem with android 6) Canbus is set on my model car and I have this problem, but if I set canbus model to none the clock works ok. I try to change canbus box but same issue. Anyone have a solution? Thanks
edit: even with the last malaysk android 6 rom same problem. Is it possible to solve putting downgrade version of clock app?
AlexRuhl said:
Hi, I have an px5 xtrons and a problem with the clock on Android 8 (stock and malaysk rom) When I restart the car the unit have the old time of shutdown. (Unit connected to battery and no problem with android 6) Canbus is set on my model car and I have this problem, but if I set canbus model to none the clock works ok. I try to change canbus box but same issue. Anyone have a solution? Thanks
edit: even with the last malaysk android 6 rom same problem. Is it possible to solve putting downgrade version of clock app?
Click to expand...
Click to collapse
I've had the same issue for probably the past year or so when I first started playing with custom roms. I'm pretty sure it happened after doing an MCU update. I have GS PX3 MTCD running hal9 rom. I've tried disabling network time etc but no difference.
When booting the headunit the time appears to be correct, then it changes to the wrong time, then after a few mins when either GPS or wifi has got a connection it corrects itself. I haven't tried changing the canbus model in factory settings as it's already correct.
I've found that the Clock app from Google works. All other including the stock clock keeps the shutoff time.
same problem here after upgrading Xtrons PX5 unit to Android 8.... it seems that somethings changed in CAN-Bus communication. Where bevore the car could write the correct time into the HU it's not possible anymore and the wrong (stucked) time get written into the Dashboard. The time will not synced when the HU is in standby (fastboot)... but will synced within 1 minute if i make a full boot.
dud89 said:
I've found that the Clock app from Google works. All other including the stock clock keeps the shutoff time.
Click to expand...
Click to collapse
hi, can you explain in more detail haw you managed to make clock work with google clock app?
i have installed it but no changes. the clock still shows old shutdown time
Hi I'm having the same issue with my xtrons head unit. Did anybody figure out a fix for this?
Hello,
I have the same problem. I have tried to add clock app to the whitelist, (mtce-utils) but It doesn't work. The canbuis I don't know is working correctly, Torque applicacion can not detect ODB unit and I can not view any value.
I set the clock to get the time from GPS only and I ve never had a problem.
typos1 said:
I set the clock to get the time from GPS only and I ve never had a problem.
Click to expand...
Click to collapse
Yes, but it only works if you have GPS connection (outdoor). If you are into garage there is no GPS udpate.
I have XTRON PX5 unit with Malaysk 8.0 and I have set the following things on whitelist:
com.android.settings
com.android.providers.settings
com.microtek.hctwidget
com.android.deskclock
com.cyanogenmod.lockclock
I have used mtce-utils ehitelist and Graser Daisata Xposed modules and none of them works.
I have connected the unit to the battery to avoid losing memory.
What can be the problem?
Thanks!
Same problem here :|
Android 6.0 clock also not working
As of 11/30/2018 after doing an MCU update 2.83 for Android 6.0, my clock also stopped syncing with the car's when turning it back on. It also display the last time right before the car was turned off.
Turning on/off GPS update or network update or setting the clock manually makes no difference and does not fix issue. Hope to see a solution to this.
If you revert back to the original MCU version, does the clock start working normally again? I'm assuming it would... I would just revert back to the original MCU version and be done with it. Unless, of course, there is some specific fix in the newer MCU that you needed?
greygoose82 said:
As of 11/30/2018 after doing an MCU update 2.83 for Android 6.0, my clock also stopped syncing with the car's when turning it back on. It also display the last time right before the car was turned off.
Turning on/off GPS update or network update or setting the clock manually makes no difference and does not fix issue. Hope to see a solution to this.
Click to expand...
Click to collapse
Did you export you MCU config before updating the MCU ?
I don't mind reverting back to the original MCU version I had but the problem I had with that one was my audio kept going back to sounding like mono instead of stereo each time I started the car. When I played video or music sound would only come out on my right door speakers. I kept having to do a factory reset each time to get it to come out at both sides.
I haven't browsed through the forum enough to see if anyone else experienced similar issues or if there were fixes for this.
greygoose82 said:
I don't mind reverting back to the original MCU version I had but the problem I had with that one was my audio kept going back to sounding like mono instead of stereo each time I started the car. When I played video or music sound would only come out on my right door speakers. I kept having to do a factory reset each time to get it to come out at both sides.
I haven't browsed through the forum enough to see if anyone else experienced similar issues or if there were fixes for this.
Click to expand...
Click to collapse
You could try the latest MCU, they may have sorted it out, you dont say what unit you have.
You could also try updating to Ore, it may also be fixed in the latest ROM.
Thanks I'll have to give it a try. My unit is the HA 2150 V600 with the px5 chip.
HI did anybody manage to sort the clock issue out on the headunits thanks
I have been having this same issue for a long time and hoping to find a fix for it.
I have tried the Google Clock app, that did not work.
I have updated my MCU from Ver 1.81 to 2.65 to 2.75 and now on 3.0.1. None of these MCU versions fix this issue.
I have also tried the V2.75_sp and no change (Did not think this would help with this issue, but tried it anyways)
On each of the MCU versions above, I have tired multiple roms (Stock, Malyask and Hal9K) and no luck fixing the problem.
The only time I have been able for this to work is if I have wifi enabled and connected to a Hotspot and Network time sync selected in the settings/Date&Time. With this configuration the time sync works everytime.
Now when the time does not Sync and if I open the GPS Plus app, the time displayed in the app is correct. So based on this, the only thing I can think of is that somehow the time from GPS is not being pushed to the clock app.
Guys I think I found the solution, at least it works in my case. What happens actually is that the unit is set to autosleep and not to shut it down. So when the unit goes to sleep, everything freezes including the clock time. When you put back the key contact, the unit goes back to live and all the apps start again from the moment when they went to sleep.
The solution which seems to work in my case, is to set the unit to shut down after I turn off the engine. Of course, it takes around a minute to turn on back when I put the contact key, but because the whole unit has been shut down, when it starts again it checks also the time clock and it syncs with either the GPS time or with the network provider time zone (depends what you have set). In my case I use the GPS time zone and with this workaround everything works well now.
It's not so much the MCU updates but the actual system update. Going backwards to the 20171214 system update will get the clock working fine again and should work with the most recent MCU update (my instance). With this version I didn't have to bother with changing the auto sleep or shutdown settings since it's an inconvenience to wait for a full minute for the unit to boot up. Also did not have to change GPS or network time sync either. I turn the key ON and the clock just works right away.
Hello all I need help!
Just bought a seicane H286 MTCE_HF_V3.07_1 9" android 9 everything looks good except for the clock. everytime I turn off the engine and the time is 2:15pm, when I turn the engine back on 30mins or however long later the clock is starting at 2:15pm and counting. I toggled update time with GPS on/off, I toggled update with carrier on/off but nothing work. The only time it's update the time with GPS is when I reset the unit. really frustrating with tech support they keep insisting that the unit is automatically update time with gps! If anyone have any solution please help. thank you.
Yes, this is a known issue, search forums for details on update or contact reseller for support/update.
hello, even my autoradio (wondefoo) rh3368 mtce_cz, cpu octacore cortex-a53 @ 1.5 android 9 has your same problem ... surely there is a software bug, the seller told me that he will send me an update. .. ps to the most expert: is it possible to downgrade from android 9 to 8 without risking ?
ilfn143 said:
Hello all I need help!
Just bought a seicane H286 MTCE_HF_V3.07_1 9" android 9 everything looks good except for the clock. everytime I turn off the engine and the time is 2:15pm, when I turn the engine back on 30mins or however long later the clock is starting at 2:15pm and counting. I toggled update time with GPS on/off, I toggled update with carrier on/off but nothing work. The only time it's update the time with GPS is when I reset the unit. really frustrating with tech support they keep insisting that the unit is automatically update time with gps! If anyone have any solution please help. thank you.
Click to expand...
Click to collapse
I recently purchased a 10.1 Seicane H2038 rk3368 unit that seems to be using the same MTCE_HF_V3.07_1 firmware. I also had an issue with the time being incorrect when returning from sleep. I was able to correct the issue by updating the android OS to the latest available (in the Daisata updates thread) HA_px5_9.0_ota(20190521) - please note that that this performed a data reset when applying.
There appears to be a newer PX5 HA_px5_9.0_ota(20190528) firmware posted now that I have not tested, but I assume that should work as well:
https://forum.xda-developers.com/an...asaita-mcu-updates-rockchip-px5-octa-t3575155
I did not upgrade the MCU firmware.
If I know how to root it I can install clocksync and have it automatically sync the clock to gps signal
ilfn143 said:
If I know how to root it I can install clocksync and have it automatically sync the clock to gps signal
Click to expand...
Click to collapse
Or read the second post....
ilfn143 said:
Hello all I need help!
Just bought a seicane H286 MTCE_HF_V3.07_1 9" android 9 everything looks good except for the clock. everytime I turn off the engine and the time is 2:15pm, when I turn the engine back on 30mins or however long later the clock is starting at 2:15pm and counting. I toggled update time with GPS on/off, I toggled update with carrier on/off but nothing work. The only time it's update the time with GPS is when I reset the unit. really frustrating with tech support they keep insisting that the unit is automatically update time with gps! If anyone have any solution please help. thank you.
Click to expand...
Click to collapse
yesterday I installed the version ha_px5_9_ota and the problem of updating the timetable has been solved, the only problem is that as equalization power and audio volume is less than the original rom.
I solved it by rooting it and using tasker. What I found out was whenever I toggle location on and off the timeupdate to gps time, so I used tasker to toggle it.
First I rooted by using adb method found here: https://forum.xda-developers.com/an...5-mtcd-e-head-unit-discussion-thread-t3734189 (very helpful to watch the youtube video)
be sure to install hacker's keyboard from play store and use notepad++ on your pc. not sure why regular keyboard didn't work in terminal emulator. I had to root twice for it to work.
install tasker, in profile I set "Display State" to "on" so every time I turn on the car it'll run the task. In task I set it to wait 5 seconds, turn off location, wait a second and turn it back on.
go back to adb on pc and run command: adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
that's it! now whenever I turn on the car it'll take a couple seconds to set the correct time.
hello, I have finished configuring everything and I must say that I am very satisfied with this version, if I can afford to give you some advice ... try installing it also because it seems better to receive gps satellites and do not need other applications to update the 'schedule.
My hu has Carplay built in and don’t want to risk it with a new rom
would it be the carplay?
mrt.angelo69 said:
would it be the carplay?
Click to expand...
Click to collapse
Apple Carplay
ilfn143 said:
First I rooted by using adb method found here: https://forum.xda-developers.com/an...5-mtcd-e-head-unit-discussion-thread-t3734189
Click to expand...
Click to collapse
Which method exactly?
kebul said:
Which method exactly?
Click to expand...
Click to collapse
Post #3
Any body have any version of mtce_hf plz
Hello everyone. I received an updated Firmware directly from seicane for their head unit. This is Android 10 update for the 2/32 GB unit. Everything seems to be working great so far on unit. If you would like to try it for yourself please feel free to download and install. I'm not too tech savvy so if you have any questions I'll answer them the best I can. Thought I would share for anyone to update their own unit if possible
PLEASE BE ADVISED YOU USE THIS AT YOUR OWN RISK!
I will not be held responsible for any damages done to your own unit.
Thank you!
https://drive.google.com/file/d/1Q9ns_Nojpl-8WAIvqgd0DMklUZJsjt7p/view?usp=drivesdk
I have a seicane radio in my ram truck, everything works well but I can't change the balance or fader, any ideas on how to correct this?
Sent from my VS996 using Tapatalk
moeduss said:
I have a seicane radio in my ram truck, everything works well but I can't change the balance or fader, any ideas on how to correct this?
Click to expand...
Click to collapse
What version of Android?
C75 said:
What version of Android?
Click to expand...
Click to collapse
Android 8
Sent from my VS996 using Tapatalk
moeduss said:
Android 8
Click to expand...
Click to collapse
Try installing this app on you HU and see if it works for you.
https://play.google.com/store/apps/details?id=jp.pioneer.mle.soundtune
Ok,
So I got a on some recommendations here.
now what? Are there any custom roms I can use?
I would recommend read trough the forums...
And no, there are no modded Android 9 Roms at the moment.
You have to wait for Hal9k_ and Malaysk to come out with one when they are done.
LinkseD said:
I would recommend read trough the forums...
And no, there are no modded Android 9 Roms at the moment.
You have to wait for Hal9k_ and Malaysk to come out with one when they are done.
Click to expand...
Click to collapse
I've spent hours on the forums but there is so much out there its hard to get a handle on. the last unit I had was a nu3001 and was a bit more straight forward.
I'm not sure I care about android 9 if there is a ROM I can put on mine that is android 8 or whatever I don't care as long as it de-china-fied. I'll continue to look but was hoping for a quicker answer as I'm about to pull the trigger on buttoning up the car with wiring and dash....
Thanks!
Stormbringer! said:
I've spent hours on the forums but there is so much out there its hard to get a handle on. the last unit I had was a nu3001 and was a bit more straight forward.
I'm not sure I care about android 9 if there is a ROM I can put on mine that is android 8 or whatever I don't care as long as it de-china-fied. I'll continue to look but was hoping for a quicker answer as I'm about to pull the trigger on buttoning up the car with wiring and dash....
Thanks!
Click to expand...
Click to collapse
Your px6 came with android 9 anyway. There is no custom roms for px6 at the moment. With that said, android 9 is what I'm running (px5) and has been the most stable out of any modded ROM available from Hal9k or anyone else. You'll need to wait before a modded release is issued . They are being worked on.
For the time being, you could install FCC Launcher for A9. There's a thread in the forums here.
Sent from my SM-N920W8 using Tapatalk
Furthermore you could root your unit aswell. Even it is just possible by using SuperSu at the moment with Android 9.
Youll find the guides in the forums.
i have orderd one to, same as in first post.
can anyone say if tomtom or tomtom nds is working on this unit?
geldorf said:
i have orderd one to, same as in first post.
can anyone say if tomtom or tomtom nds is working on this unit?
Click to expand...
Click to collapse
I have the Dasita max6 as well, and can confirm: TomTom works perfectly.
S1W-brn said:
I have the Dasita max6 as well, and can confirm: TomTom works perfectly.
Click to expand...
Click to collapse
thanks.. yours is also px6 processor?
Yes, latest version px6
My Dasaita Px6 head unit has been working flawlessly for a little bit less than a month aside from a few disconnects with Android Auto.
However, today my head unit crashed 2x. Each time I heard a speaker popping distortion noise for a second and then the head unit restarted.
The only app that was running was Spotify with the unit connected to my phone's hot spot. Weather was about 60F so it wasn't a very hot day.
Has anyone encountered this before and if so, do you know what might be causing it?
rubberchickenmob said:
My Dasaita Px6 head unit has been working flawlessly for a little bit less than a month aside from a few disconnects with Android Auto.
However, today my head unit crashed 2x. Each time I heard a speaker popping distortion noise for a second and then the head unit restarted.
The only app that was running was Spotify with the unit connected to my phone's hot spot. Weather was about 60F so it wasn't a very hot day.
Has anyone encountered this before and if so, do you know what might be causing it?
Click to expand...
Click to collapse
could be a wiring issue or might need to factory reset the unit. I think everyone should factory reset as soon as they get the unit anyway.
lennylen said:
Your px6 came with android 9 anyway. There is no custom roms for px6 at the moment. With that said, android 9 is what I'm running (px5) and has been the most stable out of any modded ROM available from Hal9k or anyone else. You'll need to wait before a modded release is issued . They are being worked on.
For the time being, you could install FCC Launcher for A9. There's a thread in the forums here.
Sent from my SM-N920W8 using Tapatalk
Click to expand...
Click to collapse
I'm having the same issue and was blaming Malaysk mod for this...
Have you solved the issue? I will go back to stock and factory reset everything next week (is there a MCU factory reset option?).
I too have experienced the same exact problem and it happens once or twice a day. The UI freezes for a few seconds then there is a loud crackling sound coming from the speakers for another few seconds followed by a crash and reboot. It appears to happen randomly when I'm interacting with apps and more than likely is not heat related since it's been only a few degrees above freezing here and has happened only a few minutes after turning on my car. I've also had freezes where the UI and all buttons stop working but the radio keeps playing and only a forced reboot fixes it. I'm on Malaysk full mod and plan to go back to stock to do some troubleshooting and see if it's hardware or software-related.
jwallsuva said:
I too have experienced the same exact problem and it happens once or twice a day. The UI freezes for a few seconds then there is a loud crackling sound coming from the speakers for another few seconds followed by a crash and reboot. It appears to happen randomly when I'm interacting with apps and more than likely is not heat related since it's been only a few degrees above freezing here and has happened only a few minutes after turning on my car. I've also had freezes where the UI and all buttons stop working but the radio keeps playing and only a forced reboot fixes it. I'm on Malaysk full mod and plan to go back to stock to do some troubleshooting and see if it's hardware or software-related.
Click to expand...
Click to collapse
I tried going back to stock and changing many different MCU versions with the same exact issues you are describing: freezing or rebooting in the first few minutes after starting the car.
Today I had another new issue: I had one of the described freezes but after shutting down the car the display of Dasaita went black but the touch buttons remained on (LEDs on). I had to disassemble the HU to unplug the power cable... This is not a small bug anymore, this is a huge issue, I am trying to contact support with no answers. Did you find a solution or have any suggestion?
Do you have stock recovery? Do you know how to install stock recovery?
I also would like to factory reset MCU setting but I have no idea how to do it. Did you change any setting in factory settings menu? I'm worried that it could be something there.
The Android Attorney said:
could be a wiring issue or might need to factory reset the unit. I think everyone should factory reset as soon as they get the unit anyway.
Click to expand...
Click to collapse
I have the same issue sometimes my HU crashes with popping sound. I blame MCU 3.37 but i am not sure. Maybe i should re-update it without cfg settings files because i flashed it with exported MCU settings and put the cfg file next to the img file when i flashed the new MCU
matrixx1 said:
I have the same issue sometimes my HU crashes with popping sound. I blame MCU 3.37 but i am not sure. Maybe i should re-update it without cfg settings files because i flashed it with exported MCU settings and put the cfg file next to the img file when i flashed the new MCU
Click to expand...
Click to collapse
Where do you get the cfg file? I always flashed MCU without cfg file but maybe we could get a cfg file from a device with no issues and flash it alongside the MCU.
Frankk said:
Where do you get the cfg file? I always flashed MCU without cfg file but maybe we could get a cfg file from a device with no issues and flash it alongside the MCU.
Click to expand...
Click to collapse
You create it for your unit from factory config menu. Or document factory settings before updating MCU, right. Perhaps search for more info or read wiki.
marchnz said:
You create it for your unit from factory config menu. Or document factory settings before updating MCU, right. Perhaps search for more info or read wiki.
Click to expand...
Click to collapse
Thank you, I'm going to read it, but I assume that the cfg file you create from the factory settings menu is a backup of your current configuration, not a real clean factory configuration, am I right?
Frankk said:
Thank you, I'm going to read it, but I assume that the cfg file you create from the factory settings menu is a backup of your current configuration, not a real clean factory configuration, am I right?
Click to expand...
Click to collapse
Yes but actually the only thing i changed is SWC settings for Canbus so i can configure it manually.
matrixx1 said:
Yes but actually the only thing i changed is SWC settings for Canbus so i can configure it manually.
Click to expand...
Click to collapse
You have a Dasaita MAX6, right?
If yes, can you send me a dmcu.cfg file generated with your device?
If you changed only that setting it is pratically a stock configuration, I think I changed something more...
I'm not sure if it is the normal behaviour but when I update the MCU or if I wipe data from recovery or if I do a factory reset from system settings, the MCU settings are never changed. My custom configuration is never overwritten or deleted.
Thank you,
Francesco Comi
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