yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] surfer63:
When I say share, I mean attach them to a post. Having to check all these images is pretty annoying.

Anyway: You have a 100% FYT unit running a somewhat older firmware ROM and running the "old" MCU firmware.

It should be possible to flash your unit with a Joying stock ROM, or with the gtxaspec custom ROM. If your supplier simply assembled the unit from FYT and did not add anything special, you are fine to go.

Make sure you have a firmware from your supplier to flash your unit in case it does not work after all.
[FYT Android Head Units] the converted:
I know that must have been beyond annoying, but I have no way of getting copied text off the head unit to be able to share it here, so I apologise for the headache, and I am very grateful for your help with my situation.

What ROM would you recommend as being the best overall? There is no way I'll be able to get a stock firmware from my supplier because the seller of the unit is literally the least helpful bunch of people I've ever had the misfortune of having to deal with, so guess I'll just have to roll the dice with a ROM and pray for the best.

Thanks again for your help surfer63.
[FYT Android Head Units] IG_Vasilich:
why just not copy that file to USB stick and post it here as an attach?
[FYT Android Head Units] surfer63:
Thank you. I was reluctant to answer, not because I was more annoyed, but more in desperation. If you don't even have the skills to copy/mail/whatsapp/dropbox/googledrive, etc. a file from an android device, then a custom rom is way over your head. Don't install it!

Anyway, for the other question: You obviously have an old MCU firmware, but one that is not a 100% equal (calendar date wise) to one of the Joying ROMs. This would mean that you need the firmwares for MCU versions <9.20 (so the 5.25). But I can't find the Sofia upgrades anymore on the blog page. The last Sofia version was of 26 January 2018 (or so), so that would be the best stock rom.

The best custom rom is then of course the v3 (as the v4 is actually another beta although it might even function better then the v3).
[FYT Android Head Units] dyabolikarl:
Not sure when i last posted but it's been at least 10 months i think. Want to report my rom still runs fine. Although i had the one which kept the lights on for 5 minutes after turn off. Hasn't been an issue :)

I am downloading v9 3a to keep as a backup as it seems development has stopped. Thanks for all the work by gtx and surfer :).

Has anyone updated thier joyings yet to a newer model?
[FYT Android Head Units] salmannazim0:
MCU is "SBD_(R76)_90_C6R76_V1.00_CAN(ALL)AMP"

Hi everyone,

i have same "" MCU is "SBD_(R76)_90_C6R76_V1.00_CAN(ALL)AMP""" based android 6 setup.

Last night i have installed this MCU Update "" 2018_01_JY_1024x600_MCU9_20 ""

https://www.joyingauto.com/blog/post...ftware-update/

the updated was 100% successful but main problem is

when android player is start the screen in continuously blinking and show me this message

"" ui and MCU does not match(jy) "" "when i low brightness the screen blinking is stop "

how can i restore may old MCU SBD_(R76) or remove error message which shown on screen

plz help me

(sorry ma English in not good )

below my android player picture

https://xdaforums.com/pic...ictureid=58071

https://xdaforums.com/pic...ictureid=58072
[FYT Android Head Units] luismiguelmimi:
hello to all some of you can give me a hand I need to know if after trying I have managed to install the new ROM. I leave a photo of the information of the unit.

Thank.

Enviado desde mi Redmi Note 3 mediante Tapatalk
[FYT Android Head Units] patky77:
Hello,

Can i use this with Intel Atom 4QuadCore, GPU4D: Mali-450 MP4 ?

Seller info: Intel & RK, SOFIA-3GR, basic frequency: 4Quad-core intel ATOM 1.2G

thank you
[FYT Android Head Units] surfer63:
It is not possible to say that based on this info. It is highly depending on the MCU and software manufacturer.

Attach the files /system/build.prop and, if available, the files /system/app/fyt.prop and /system/app/fyt_build.prop, to a reply post.

If you do not have the last 2 files on your system, it is unlikely you can use this custom rom.
[FYT Android Head Units] patky77:
Thank you for your replay.

Attached file, please find what i can see after power on. I can not get any file from it.
[FYT Android Head Units] surfer63:
This is not useful.

Is your unit bricked?

Did you already flash the custom rom and does your unit not start anymore?

If so: contact your supplier.
[FYT Android Head Units] patky77:
I hope this is not a brick. A just made a factory data reset. After restart get the above information.

Az én iPhone készülékemről küldve a Tapatalk segítségével
[FYT Android Head Units] kampfschachtel:
do I need to root the clean install of the latest joying release before installing this Rom?

Can I do the rooting via the extra APK enabling adb and then superuser apk that is provided by surfer63?
[FYT Android Head Units] surfer63:
Yes, it needs to be rooted.

Yes, you can enable adb via the JET apk and then the superuser rooting (not the SuperSU).

A faster way to enable adb is BEFORE you flash the ROM firmware, you edit the config.txt on the usb stick/sd-card and add "service.adb.tcp.port=5555" as a line (or before you copy everything to the usb-stick/sd-card).

In that case adb over tcp/ip will automatically be enabled after the flash.
[FYT Android Head Units] kampfschachtel:
thanks.

All went smoothly through, Joying update, root, custom install... till the installing of gtx rom BUT then

the "team Win recovery project" came up and I got stuck.

What do I need to do here?

fixed it: had the firmware unzipped on the stick but it was still in the folder gtx rom, its not in the root where it must be. Needed to copy all the files from the unzipped folder gtx rom directly from the usb stick to the root folder of the USB Stick. Now it worked:laugh:

So first feedback:

the joying noble price goes to gtxaspec. Thanks so much to you and all that contributed to this for this incredible work.

Wow, everything is fast, responsive and painless...first time a complete setup like I want it took me less then 2 hours, standard till now was 3 days and half was not working or like I wanted.

what a difference and I didn't do any tweaking till know plus my loved automate and the Viper4android is finally working on the joying. Was thinking about getting upgrade to PX5 but not needed at all after that ROM. I was stupid to stay so long with the crippled release 5th May 2017...

the only thing so far: I want to use Automate as launcher but its not possible, I set it as launcher in the settings but the nova launcher seem to oversteer it somehow. Anybody an idea how i can fix this?
[FYT Android Head Units] kampfschachtel:
could anyone please provide a download of latest joying dash cam app. have the joying dash cam and had it running before updating to GTX rom.

It did what I want, so wanna install it with the gtx Rom if possible.
[FYT Android Head Units] kampfschachtel:
having problems to understand/follow Q&A for google voice to make hands free calls, Please help.

Q: Can I use google voice to make hands free calls?

A: You sure can. Use the "Voice Search" app to dial a number using your voice, once at the Google App screen, click on the hamburger menu, and then select GV CallHandler 4 Joying. Make sure your unit is set to a DPI of at least 161dpi or greater, and then clear data on the google app. After you reboot, you should be able to make calls.

my difficulties:

1)Which "Voice search app" do you mean? ok..google dail "Charly" didn't work, I get a list of research about "dail charly"...

2)then in google app screen, hamburger menu is on the buttom right but I cannot select GV CallHandler 4 Joying. I don't find the menu/task/point where I could select/choose it...
[FYT Android Head Units] surfer63:
See here.

---------- Post added at 08:49 AM ---------- Previous post was at 08:45 AM ----------

(Currently not near my unit.)

You can change almost everything via Settings.

Go to settings -> apps.

Check the "default apps". As far as I can remember it should also have a default phone app. You should be able to change that if there are more apps that can act as phone app.

Same for your earlier launcher question: You can also select a default launcher in this screen.
[FYT Android Head Units] kampfschachtel:
found the default apps under settings menu of joying, here I could switch the default launcher to automate, that's solved.

But still stuck on voice dail , due to gtxaspec I have to go in the google app screen to the hamburger menu and select the GVhandler but there is no hamburger ->settings -> apps or GVhandler to select/choose

also in the hamburger-> info is no app or settings menu
[FYT Android Head Units] carburngood:
Can I install this ROM?

This is what I have under device info - am I able to install this ROM safely?

Brand is Funrover, 2Gb version stereo linked here:

Android Version

8.0

CPU Info

CPU: Intel ATOM 4QuadCore(x86), GPU4D Mali 450 MP4, X86

Baseband version

SF3GR_M-26.3_cpeg_rk-r2p_bc2-20160629_111639

System Info

APP 1024x600 2018-06-06 22:50:08

MCU Version

2018-06-02 12:16:25 FAD_(R76)_90_D1_V1.0_CAN(All)_AMP

CAN Version

Unknown

Car Application

Car Application Information

Serial number

00000000
[FYT Android Head Units] surfer63:
Not the right info. See post #2005 on how to give info. Only one page back.
[FYT Android Head Units] creapetime:
Hello,

I just want to give a feedback of a Solution that worked for me:)

I bought a new Xtrons TS702l and I found out, that the Stock Software is very disappointing.

It was really hard for me to see through the Jungle of Rooting Methods and Roms for Joying and not Joying Devices, so I decided to share my Way.

The TS702l is NOT a MTCD Model and not a Joying, but it has to be treated as a Joying Radio. There are also Joying Models wich look pretty similar to the TS702l.

I rooted the Device via the Adb over Wifi Method, but after first try the Super User was not working right.

It helped to reinstall the Super User App as a normal App (not System App). But after reinstalling once you can change the App back to a System App without loosing function.

After this I installed the Gtx Rom directly via custom and it worked perfect. I did not flash the Joying Firmware before.

When I started the Rom I got a yellow Bar wich you can disable with the Xposed Tweaker Module.

Thanks to all people who made this Rom possible :good:

Maybe some useful Information about the TS702l:

SOM: 6011/Wifi/C

Microcontroller: STM8S207C8T6

MCU Version: 2018-01-13 10:51:29 XZC_(R76)_90_C9R76_V1.00_CAN(ALL)_AMP

Android Version 6.0.1

System Info: APP2017-12-25 13:38:50

Build ID: sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.bsp.20171215 153906 release-keys
[FYT Android Head Units] lotte67890:
How can I find out what MCU SW Version my Joying Unit has when running this ROM? And is there a way to update the MCU only without flashing the original ROM?

Thanks

L
[FYT Android Head Units] psylock79:
Radio interrupted when using Waze navigation

Hi Guys

I have had a search around the forums but I can't find the problem or the solution to this problem.

If I have radio playing and I launch radio all appears fine.

But as soon as I launch waze on the Joying unit and it either provides an alert or a turn by turn instruction the radio is stopped.

It does not then continue once the instruction has been issued as expected.

My only option is to relaunch the radio or re-select the station which then plays as expected. But as soon as the next instruction is provided the radio is permanently interrupted.

Anyone else have the issue?

Any ideas on how to resolve?
[FYT Android Head Units] tbd@immigrantsong.de:
WIFI

I've had continuous issues with the wifi that it was not connecting to my network. Neither at home, nor with the Joying dongle. After many tries I was finally able to establish a stable connection with the dongle and was quite happy. Until after a few weeks it stoppes working again.

Troubleshooting I noticed that the Wifi channel had changed, I reset it to channel 3 (or something) and once again it worked. Possibly the WLAN-driver in the Joying has issues connecting to all channels, possibly its radio interference in my car.

Question to others, have you had similar issues?
[FYT Android Head Units] trueppp:
Compatible?

Here are the files, am I compatible? If not, anyway to installed Xposed?
[FYT Android Head Units] etrefal:
I switched channels a few times since I got the Joying unit, and never noticed any difference... it's mostly a bad connection everytime. :) My router is not placed well for a connection to my car, and the Joying's wifi antenna is in a really bad environment, as it is surrounded by metal reinforcements behind my dash. A second access point in the garage made a big difference though, as it is only a few meters from the car. Note that I don't have a separate dongle to connect to wifi, only the integrated wifi connection.
[FYT Android Head Units] surfer63:
I guess it is safe to flash the gtx rom, but gtxaspec is actually the only one who can be really sure to answer this.

For me it is the other way round: Based on info I could have said that you definitely can't flash the unit, but that is not the case.

The fyt.prop clearly shows it is for another manufacturer (ro.build.fytmanufacturer=39, where Joying=43) but for the rest it seems to be equal.

I can't say much about the MCU firmware though.

I had hoped gtxaspec would step in, but I haven't seen him for quite some time.

The Xposed install is experimental on the Android 6 Sofia units. You could be succesful, but may not.

Make sure you always have a stock firmware at hand to be able to reflash your unit.
[FYT Android Head Units] trueppp:
Thanks, but I beleive if i cannot get to recovery, then I cannot install Xposed right? Also how can I install Xposed?
[FYT Android Head Units] surfer63:
Have you rooted your system?

Did you download the custom.apk to replace the standard recovery?

Did you read the first, second and third post of this thread?
[FYT Android Head Units] trueppp:
Yes, i rooted with the instructions from JET,

custom.apk is installed, but I get stonewalled after that. Do I need to replace my stock firmware with a Joying firmware

first?
[FYT Android Head Units] surfer63:
What do you mean with stonewalled?

What happens or doesn't happen?
[FYT Android Head Units] timnop:
Yes, I never had any problems with wifi on the Joying until I installed this ROM. I use mobile hotspot on my phone for the unit to get wifi while I'm driving. The connection never seems to last more than 10 minutes or so, and then I notice the music stops (pandora) and my wifi indicator in the notification bar is gone. When I go to the wifi settings it's on and scanning (doesn't see my hotspot). Usually, if I toggle my hotspot off and then back on, it will then show up and reconnect. Also sometimes if just wait a while, it will reconnect on it's own. I am very happy with this ROM otherwise and hope I can find a fix for this issue.
[FYT Android Head Units] trueppp:
It doesnt go to recovery, just reboots.
[FYT Android Head Units] trueppp:
With a usb keyboard got a bit further but still bugs in TWRP says cannot find files on usb
[FYT Android Head Units] trueppp:
Yay I got it to boot to recovery after doing "install gtx rom" , it hung for a long time on loading recovery, si i resert, now its doing white screen after boot logo, will try to put back factory firmware. cannot get back to twrp
[FYT Android Head Units] james272:
this rom work like charm with Viper? any viper option working or some option not working? any recommend option or setting? thanks
[FYT Android Head Units] skedar.corp:
Hm, i have a problem with my unity...

I have a Sofia 3GR Car "Generic" but its like the same Joying system, the joying passwords and the "root tool" works too.

So, i make a update in my firmware to install your custom rom, but i have a problem here.

After make the update, i have a "warning" message in my screen: "MCU is not JY and etc" and a chinese message about my "DVD" unity...ok, i make the changes in a arquive with root and this message of MCU is gone, the DVD i cant understant because its chinese and this stay in my screen...BUT my radion dont work and my sound have a type of "noise".

This is like a "click" and its make my music stop everytime in 1min or less....but now is time to install the custom and hope to fix this problems ok?...no

I cant install the custom firmware because its show me a two error messages about key/signature verification or some like that and abort.

My MCU unity is: FY_(NOR)_90_C9_7706_6023_Newlap_18E

and my DVD: R-86C-096I-NC-NP-1.0-SI2-IPOD

Sofia 3GR Car (sofia3gr_car_64)

Rockchip SF3GR_M-26.3_cpeg_rkr2p_bc2-20160629_111639

IMC RPC-RIL 1.0

sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.build.20170615.204111 release-keys

Android/sofia3gr_car_64/sofia3gr_car:6. 0.1/MMB29M/build06152044:userdebug/release-keys

Bootloader: BOOTCORE_VER

Java VM: ART 2.1.0

OS: Marshmallow (6.0.1) SDK: 23

rk30sdk
[FYT Android Head Units] surfer63:
[MENTION=520205]gtxaspec[/MENTION]

You disable a number of services in the stop_services.sh.

I now want to do the same from the JET apk for users who do not want to flash a custom rom (Sofia) or where no custom rom is available (PX5).

(And also disable some system and FYT apps which can't be disabled from the Settings)

However, from that stop_services.sh you use commands like:

stop ap_logfs
stop apk_logfs

This means it is first started by one of the init.<whatever>.rc scripts (boot image ramdisk I believe) where it does

on property:persist.service.aplogfs.enable=1
restart ap_logfs

on property:persist.service.aplogfs.enable=0
stop ap_logfs

(same for apk_logfs), and then you stop it again in your script.

Why not simply set the property (once), like

setprop persist.service.aplogfs.enable 0
setprop persist.service.apklogsd.enable 0

same for

setprop service.adbec.enable 0

No need for a stop_services.sh script (maybe not for all services. I have to check), no need to stop an already started service, and easy to restore by means of a (rooted) setprop command.

Is there a specific reason you do it like this? I'm now doubting between the setprop method (my preferred one) and your method, but ... (many sleepless nights on this choice as you can imagine :) )
[FYT Android Head Units] james272:
looks like this rom has many problem. all people shout some error.

anyone can success install this custom rom?

i also encountered some error.

because of viper i want to install this rom but i think it better i quit install.

what is best setting for viper?
[FYT Android Head Units] surfer63:
I do not understand where you get the idea that this rom has many problems. It is an excellent rom.

And many persons already installed the rom. If you, next to this forum, also follow the German forums and Russian forums, you see that users are very enthusiastic.

Viper is troublesome on Joyings as Joying tries to prevent users from using it.

The custom ROM is the best alternative to at least get some Viper functionality. On the stock ROM it doesn't work at all.
[FYT Android Head Units] surfer63:
To answer my own question:

The approach I mentioned is fairly common on a lot of ROMs, but not on the FYT ROMs (or maybe not on cheap Chinese ROMs?).

So we do need a a stop_services.sh.
[FYT Android Head Units] gtxaspec:
Yes, the boot image recreates the init.rc files on every boot, there is no way to remove the persist without re creating the boot image.
[FYT Android Head Units] surfer63:
Thanks,

And on to the next question.

In your custom ROM you set the governor to performance and the cpu clocks to the max frequency (and stop ituxd). That's the only thing that I do not really appreciate. If your fan fails you might have a melted CPU within a minute, also because ituxd is not running. And personally I do think the Google interactive governor on these Android ROMs of 6 and newer, functions real fine.

But of course I do understand the wish/desire of many users to do this.

What do you think of a "mechanism" for the install-recovery.sh in the preboot_clock function like

if [ ! -f /sdcard/interactive.txt ]
then #file does not exist
"do the max_cpu setting"
else #file does exist
"do nothing, or in other words: use the default interactive settings"
fi

So if the user does not create the /sdcard/interactive.txt file, the unit will be pushed to its limits.

So by default, in your ROM, it will be on max performance. And if a user creates that text file, the system will run at its default settings.

No difficult changes to the install-recovery.sh

(And of course if the else does nothing, that else statement is actually not necessary. It is just to explain "the flow")

Or use a property in the fyt_build.prop like you are already doing, like "ro.build.maxperformance=1" for default performance setting.

and check that with getprop in the install-recovery.sh

That property could also be set from your Custom.apk (to on (1) or off (0))
[FYT Android Head Units] gtxaspec:
I've tested this on the 5009 and 6026 with NO fan extensively, but then all CPUs are not binned alike so some may perfom worse under max clock.

How did I test? On a sunny HOT day with the car direct in the sun with Max clock locked running loadgen on the command line. Survived for 6 hours on 5009 and 6026 so I called it a win. CPU hit 100C plus... survived! Lol

Anyway we only clock the room fast during install and during boot... ONLY unless the user enabled max performance mode.
[FYT Android Head Units] etrefal:
That's what I understood from past conversations: the clock is set at the maximum speed only during the install, and the regular governing mechanism is working after that - I did not select the option for maximum performance.

I have the governor set to performance mode, but the clock set between 728 MHz and 1,2 GHz, and with a heat sink and fan combo, it survived the scorching summer we had here without problems. The maximum temperature I saw was around 65C, which is very good.

Thanks again for your work!
[FYT Android Head Units] henrysinn:
Hi all / [MENTION=520205]gtxaspec[/MENTION] & [MENTION=805590]aaron19953[/MENTION]

Stuck with Live Wallpapers that I do in fact want.

Have executed front page instructions along with reading #930 #1012 #1013 & #1328

Have done the copy-paste of "Live Wallpapers" and "Live Wallpaper Picker" folders from /system/vendor/oem to /system/priv-app, set permissions to 0644 to the apk's AND 2 folders in /system/priv-app , rebooted, but still get "App isn't installed" when I try to load a wallpaper

Any succinct instructions? Ideas?

Bamboozled..

Thank you all
[FYT Android Head Units] surfer63:
Yes, you are right. I forgot that. sorry.

---------- Post added at 11:04 AM ---------- Previous post was at 10:50 AM ----------

The apks need permission 644. The folders need permission 755, NOT 644.
[FYT Android Head Units] henrysinn:
Thanks

Now have Live Wallpaper working

Problem was failure with

"cp -R /system/vendor/oem/LiveWall* /system/app" (I had root)

"Read-Only file system" error for each directory when attempt to copy them took place.

Installed Root Explorer (My Favourite) and did a manual copy-paste to /system/app (not /system/priv-app)

Didn't need to get in to check or change permissions. It just worked after the paste!
[FYT Android Head Units] james272:
Hello

I finally installed successfully!

What is best possible v4a setting with this rom?

When i set turn on convolver option i heard sound lagging.

Any recommend setting?

Thanks
[FYT Android Head Units] amadare:
The only problems I seem to encounter are due to the carwebguru interface and they get resolved quickly enough. This rom has been rock solid for the 8 months I’ve had the head unit. Viper working fine here. Using alpha4 and it hasn’t done any of the pops or skips as happened on the previous versions.
[FYT Android Head Units] etrefal:
What are the differences between 9a3 and 9a4 ? I've been on 9a3 for a good while now and V4A is jerky unless you only use one or two options....