yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] amadare:
I thought for a4 somehow he used pieces from a previous joying release that allowed the v4a to work properly a4 exists right? I’m not just imagining it? I can’t see anywhere to show the exact version I’m running.

I’m headed to work and don’t know what’s saved on my home network.
[FYT Android Head Units] etrefal:
Ah yes... I was under the impression that it was not an "as ready" release... I think [MENTION=520205]gtxaspec[/MENTION] never found the exact components that made a difference to Viper, and we never got another version after that...

I'll check it out, maybe it'll be better than 9a3...

Thanks!
[FYT Android Head Units] henrysinn:
YouTube Vanced

Successfully installed YouTube Vanced

Followed the yellow brick road at https://xdaforums.com/android/apps-games/app-youtube-vanced-edition-t3758757 and used TWRP to flash with success.

Yes, yes, I know, anyone watching video whilst driving probably needs to be put behind bars..

For me, it's an activity for when I'm parked waiting for someone and/or doing A/V demos (another story) in the car (also parked).
[FYT Android Head Units] surfer63:
gtxaspec used the latest January 2018 ROM as base for his custom rom. Viper last worked correctly on the May 2017 ROM.

As far as I know the 9a4 is based on the May 2017 ROM to check whether it would allow for Viper and at the same time be just as stable and good as January 2018 based roms.

The 9a3 was a beta but can be considered as a stable release.

The 9a4 was really again a beta, or maybe even alpha.
[FYT Android Head Units] etrefal:
Ok, so by installing 9a4 I might see old bluetooth bugs coming back...

Thanks for the clarification!
[FYT Android Head Units] surfer63:
I do not know whether he mixed "things" from both ROMs or used a "pure" May ROM
[FYT Android Head Units] carburngood:
Build.prop Attached

OK I retrieved the build.prop from my device - can anyone please confirm / deny that this ROM is compatible with my head unit?

Link to unit if this assist in any way:

https://www.aliexpress.com/item/Fun...timedia-Player-For-Mazda-CX7/32865777392.html
[FYT Android Head Units] surfer63:
Yes it is compatible, but I have 2 remarks.

Your head unit is a compatible Sofia 3GR unit build by FYT and having the software of FYT. Your build is a 6.0.1 slightly older than the latest 6.0.1 ROM for Joying.

First remark: You don't share your MCU version. Please show that one as well as it can lead to annoying errors (yellow bars) in the top of your screen.

second: Your link points to an Android 8.0.0 model presumably on a quad-core Sofia 3GR.

Based on your build.prop you have a 6.0.1 version but was it sold to you as an 8.0.0 version?
[FYT Android Head Units] carburngood:
Yeah they've given me a few firmwares to try as I have a very weird issue where I have sound (GPS, key tones,etc.) if the radio app is open, as soon as I exit the radio app all sounds go silent - which is a bit of a problem. The system info lies about what Android version it is as well, not terribly happy about that. MCU and other info below:

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:
This is indeed a lie as your build.prop clearly mentions

ro.build.display.id=sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.bsp.20180726.190227 release-keys
ro.build.version.sdk=23
ro.build.version.release=6.0.1
ro.build.description=sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.bsp.20180726.190227 release-keys
ro.build.fingerprint=Android/sofia3gr_car_64/sofia3gr_car:6.0.1/MMB29M/bsp07261903:userdebug/release-keys

This "ro.build.version.release=6.0.1" is what normally is displayed in your system info.

But on the other hand your MCU is

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

This is much newer than any Joying Sofia 3GR has at this moment.

Given the issues you already have I would be very careful and have one of those Funrover firmwares at hand if you still decide to flash your unit with the v9a3.
[FYT Android Head Units] carburngood:
Thanks for the heads up - if I try this firmware and it bootloops, how do you get in to recovery as there's only the touch buttons on the left hand side? (and the reset hole I guess)
[FYT Android Head Units] surfer63:
Like I mentioned Yesterday in another thread (relevant portion):

Another user mentioned that you should remove sd-cards/usb-sticks and that when you reset the unit 3 times and it goes into "recovery pink/purple blinking" that only at that time you should immediately insert your usb-stick/sd-card.
[FYT Android Head Units] carburngood:
OK cool - if I know how to get the old 'official' firmware back that makes me a lot more confident giving this firmware a go.
[FYT Android Head Units] sjorsbusscher:
Starting problem

Hello,

Yesterday i installed the rom on my joying unit.

Now i have the following problem:

When i turn my key to the first position, the radio starts from sleep mode.

But when i start the engine itself the radio reboots.

With the stock rom i didn't had this problem.

It seems also that my radio is turning in sleepmode quicker when i shut down the car, maybe that is the problem.

Does anyone have an solution for this problem?
[FYT Android Head Units] surfer63:
You don't mention where you are located. But the last 2 days it has become considerably colder in quite some areas in Europe (also in the Netherlands).

If you have a bad battery in your car this is exactly what will happen. Starting your car will drain so much power, and thereby lower the voltage, that your radio will reboot.

Check your battery voltage and how much it drops when you start the car.
[FYT Android Head Units] sjorsbusscher:
Yeah i'm from the netherlands, and it's true that it is colder.

But the problem didn't occur with the old firmware.

And with the old firmware when i took my keys out, the unit remained active for 2-3 seconds. Now it shuts down immediately.
[FYT Android Head Units] surfer63:
Can't answer your first issue with the starting other than what I already mentioned. Maybe the custom rom draws more power when starting as it does run all cores at full speed during start.

The second is due to removed services which keep the screen on for a little longer.

Don't be fooled by this though. The screen switches off immediately but android is stopped in a controlled way taking up to 4 minutes. The stock ROM did that and that has not been changed with the custom rom.

It is only a "cosmetic" change you observe.
[FYT Android Head Units] sjorsbusscher:
Okee thanks for the quick response.

I will keep an eye on it and wil make sure my battery is in good shape.

I'm very happy with the rom btw

Also is it possible that the rom shuts down programs when i start others? And is it possible to make sure it doesn't?
[FYT Android Head Units] surfer63:
All task managers on all Android ROMs do that when memory gets too full/overloaded or (badly written) programs in the background require to much performance.

Please be more specific.

do you experience it?

Do you want Android to stop programs?

Do you want to prevent android from stopping programs?
[FYT Android Head Units] sjorsbusscher:
Yes i experience this sometimes

For example i have an app running for alarming me for speedcams, this is an app i want to keep active.

I want to prevent android from stopping certain apps.
[FYT Android Head Units] surfer63:
Check in Settings your app settings and switch off optimizing for that app
[FYT Android Head Units] dalu:
hello,

I wanted to try this rom, so I installed fresh android 6.0, I made root, then installed a custom APK, I clicked on INSTALL CUSTOM, then in VERIFY RECOVERY, everything ok, then I click on INSTALL GTX ROM, device reboot and open TWRP, it does not install automatically. OK, I try to manually install from TWRP, but I get this error (picture). Anyone have any idea what I'm doing wrong? ( my gtx rom 5009_gtx_v9_alpha_3.zip is on pendrive)
[FYT Android Head Units] Joshdaboss1994:
Have you tried redownloading the file, your file may be corrupt
[FYT Android Head Units] surfer63:
You should UNZIP the 5009_gtx_v9_alpha_3.zip to your pendrive, not simply copy the zip itself to the pendrive.
[FYT Android Head Units] dalu:
now works ;) thank you!
[FYT Android Head Units] carburngood:
Thanks for all your info - as I haven't found a way to root my unit this ROM may be a no-go for me. Do you think there's any chance the Joying firmware would work with my unit? (Entirely at my own risk of course)
[FYT Android Head Units] tro_m:
ist there any way to update to 8.0?
[FYT Android Head Units] Kyle M.:
Hi everyone, sorry I'm a bit late to the party.

I've been sifting through this thread, and I'm also getting an error when trying to install TWRP through the Custom apk. The number on the top is 2131427376 and it says something along the lines of "Signature verifcation FAILED Twice!"

Has anyone tried the Custom apk from a PX5 unit with Android 8.0?

not sure if it matters but my unit's SKU is EU-JY-BO123P4
[FYT Android Head Units] surfer63:
You were lucky in not bricking your unit. The TWRP recovery image contains the software for your specific architecture. The Custom.apk is plain java and works on every android. But the recovery of the gtxaspec ROM is specifically for the Joying Intel Sofia 3GR with that specific motherboard.

You can't use an Intel based recovery on a ARM based PX5 with a different motherboard.

I do have 2 PX5 TWRP recovery images but I still don't dare to flash them to my unit. I can give you the link and you may try them if you like :D, but I don't dare to yet.
[FYT Android Head Units] Kyle M.:
Woops! Well if you ever need to check if your apps are idiot-proof, you know where to find me :laugh: I think I saw it somewhere saying if it fails it goes back to stock, that's probably why i tried it.

I would be tempted to try your recoveries, I'm just wondering what's the chances of bricking it irreparably.
[FYT Android Head Units] surfer63:
They are not my recoveries and I really don't know what will happen..

If you want to try look here: https://twrpbuilder.github.io/downloads/twrp/

and put px5 in the search bar.

Or you can try to build it yourself from here. (I needed to use tinyurl as the original url is too long for XDA)

Actually this will upload all the necessary stuff to that site and the developers will compile a TWRP recovery for you.

EDIT: Note that the above mentioned PX5 recovieries could just as well be for MTCD units or those PX5 mediaplayers for TVs.
[FYT Android Head Units] Kyle M.:
Cheers. I'll take some time to think about it cause it's my only unit and I remember how much of a ***** it was to install it (because i had the brilliant idea of making the usb ports come out of the ashtray).

I wonder if there's anyone with a similar unit to mine who's tried those recoveries before.

God i miss having my garage next to the kitchen!
[FYT Android Head Units] Kyle M.:
Sorry to bother you again, but you know much better than I do about these head units.

I've decided it might be worth giving it a shot with TWRP. Should I mess up the recovery, is there any way to recover the original recovery or will it end up a painful reminder every time I get into my car? Do you know anyone who's broken these things before and got them fixed please?

I have a soldering iron as well should it need breaking into. I'm aware of Murphy's law.
[FYT Android Head Units] surfer63:
gtxaspec is really the expert on this. I'm not.

When I received my unit I made backups from all partitions as partition images using dd, also from the recovery partition. That's also what gtxapec used when he did not have his own, now deceased, PX5 unit.

As long as your unit boots normally, you can write experimental recovery images to the recovery partition and try to boot in recovery.

If it doesn't work, you simply reboot and it will get back to Android.

And then you can try to "dd" another recovery.img and see it it boots to recovery.

However, if you make one mistake and write to the wrong partition or write over the partition boundaries you are in deep problems. It has occurred once to me resulting in a hard brick, although I still don't know what went wrong. I filmed all my steps and I did it correct (I think). Since that time I don't try anymore.

Especially as I think that the PX5 rooted and with Xposed and JET, doesn't need a custom rom. Of course that takes more steps then simply flashing a custom ROM, but it is OK for me.

I made quite some custom ROMs from android 2.1 to Android 4.0 and then stopped. And now it has become way more complicated for our FYT models due to the signing of all images. As an "exercise" I already created a custom rom, which is not that hard, but it doesn't have the proper FYT/Joying signing, so I can't flash it.

I also looked at our current PX5 recovery and recompiled it without the signing, but I did not flash that one yet. To overcome that signing.

As mentioned: It is an interesting thought, but I don't think it necessary for our PX5 units.

And gtxaspec did not really give insights, but I'm afraid this tricky experimenting hard bricked his unit.
[FYT Android Head Units] Kyle M.:
I agree, in principle, that rooting, Xposed and JET pretty much covers most of what most of us will ever need. However, there's plenty of shortcomings in the manufacturer's ROM (including the latest one from last month which I just flashed yesterday) that although present relatively small problems, they occur frequently and to an extent they become annoying. Not to mention the possibilities with a custom ROM are endless and very very tempting. Few years ago, after putting TWRP on a samsung s3 phone and played around with various ROMs, it was so customisable and perfect that not only the phone survived me and my various experiments, I ended up handing it down to my mum where it lived on for another couple of years while I was in another country.

So basically what you meant in the first part of your answer was, that as long as I make sure the recovery images are only written in the recovery partition and it doesn't mess up the boot, it should be ok, right?

And I imagine once they got hard bricked, they were only good for the bin?

[MENTION=520205]gtxaspec[/MENTION] Hello, would you be so kind as to give me your advice on the matter, please? Thanks
[FYT Android Head Units] surfer63:
Yes and yes.

-- Removed and moved to the correct PX5 thread, as not to confuse users and make them do stupid things to their Sofia 3 GR unit --

-- This continues here --
[FYT Android Head Units] wanb1i:
Isn't it possible to to temporarily "boot" the twrp recovery, instead of flashing to accomplish whatever task, then reboot and have stock recovery again? I know I did this on other Android devices.
[FYT Android Head Units] ptolomeo:
I have some issue with the Radio App. I have latest 9.3 ROM version with the NOKILL mod.

However, if I switch off the car while listening to the Radio App, when I turn on the car again, it reboots and starts with the Android logo and all that stuff.

If I switch off the car while using music (Poweramp) this never happens.

I've been reading about low battery issues (could be) but after several weeks the diagnostic is, that the radio App (for whatever reason) makes the Joying headunit to boot up.

I tried different Radio Apps (using surfer's app) with no luck. Even the 8.0 based radio app boots the headunit.

What could I do? Is there any other (even commercial) app that can work like Joying's Radio App? It's very annoying, specially because it takes a minute or two while booting to have the rear view cam available, and that's bit annoying.

Thank you very much in advance.
[FYT Android Head Units] rafabad:
hello, my head unit setting is:

MCU 2017-10-25 18:11:24 JY_(_R68)_90_C9_6686_5009_CAN

SYSTEM 2017-11-01 10:53:25

APP 1024X600 2017-11-09 19:19:02

I would like to know what I have to do before installing this rom, and so my headunit can be compatible
[FYT Android Head Units] sea3pea0:
OBDLink SX (usb) works!

After trying a bunch of different bluetooth obd 2 adapters, I finally found an adapter that actually works reliably with this rom/joying head unit. I had nothing but trouble with the various bluetooth adapters I tried including the cheap blue Elm 327 generic one and the OBDLink MX+. They would work for a little while and then quit responding. Finally after trying a usb obd adapter, the OBDLink SX, I have a working obd adapter for use with this joying head unit running GTX V9a3
[FYT Android Head Units] pafo42:
Trying to find out if this would work on my JY-UMS03N, I don't know where to lookup "FYT SoM"

Thanks in advance
[FYT Android Head Units] surfer63:
What do you mean with " if this would work"?

And yes: You have a FYT SOM. You can find entries for FYT in the /system/build.prop like

ro.build.host=fyt
ro.fyt.sys.version=95024
ro.build.fytid=FYGrp01
[FYT Android Head Units] pafo42:
Ah great, I ment if my device was compatible with this ROM, didn't know where to look for that info.
[FYT Android Head Units] bonisaw:
MCU error

Hey folks.

So... I haven't updated my unit (JY-HM121N2) for quite some time and decided it was time to do a mega update: OS, iGO, maps, apps etc.

I decided to get it up to date with the stock firmware to then install gtx... which I did, but just after I tried that, I got that stupid MCU error on top in chinese with the stock rom. I may have downloaded the wrong one. I have MCU 2017-10-25 but downloaded the <5.25 instead of 9.20>.

I did download the 9.20 version and installed that, but the error persisted.

I did install gtx, but the error persisted. (the overheat issue happened to me and the unit was bootlooping, had to turn off the car for some time to cooldown, booted on 1st try after)

I saw in this thread that if you downgrade to Sep/Nov 2017 firmwares and then upgrade to Jan 2018 to then install gtx, it solves the problem... but I do not have older versions. GTX's mirrors are down.

Would anybody know of any other solution or have an older version mirror? (I tried to search as much as possible, apologize if this has been answered already)

What happens if I just get rid of /system/mcu? Are these files used or are they there only to be used for updating?

Also tried to contact Joying itself to see what they say, but the language barrier is quite a gap for them, still waiting for an appropriate answer from them as well.

Thanks...

Update 1: I saw some people saying to use XSofiaTweaker / XFytTweaker to hide the yellow bar. This does works but when I boot it still goes to the MCU error screen. Radio is not working too. When SuperSU prompt comes up asking if I allow an app to become root, I cannot click anything. It's a complete mess...

Update 2: Joying sent me a MCU that fixed the issue. I am now running GTX with their MCU. Radio works, BT works, Wifi works. All good so far. Need to do more testing though.
[FYT Android Head Units] nimdrock:
hi!!! I had the same issue, I really search in everywere and I cant find the solution..... Have any ideas?
[FYT Android Head Units] surfer63:
You both have now the custom ROM with Xposed. You can install XFytTweaker (or the older XSofiaTweaker) module.

It has an option to hide the Yellow bar. It is a "non-critical" error but it is really an annoying one. The best would be to have your MCU updated by ONLY flashing a new MCU to it.

See here.
[FYT Android Head Units] nimdrock:
Thanks for the answer, Im looking for ZHAN MCU, but didnt found anything.

Radio dont work, the audio cuts a few second constantly, beside the MCU and UI version (that is solved) appears another message like it that says something about DVD and a few chineese symbols.... Im really confused right now...

Edit: I dont find the Stock rom. Here is head unit info
[FYT Android Head Units] dalu:
Hi,

I have a message (like on the picture) once every few starts, can I turn it off/disable - this self-test, because this procedure takes time and the reversing camera does not work. Why is this happening (I always fully launched my HU)?
[FYT Android Head Units] surfer63:
Somehow, when you switch on your contact and start your car, there is a power dip which makes your unit reboot uncontrolled. When this happens 3 times in a row, your unit detects this as possible cause for errors and does a controlled reboot where it can close and restart "everything" properply.

Most probably your car has a bad battery which causes this.
[FYT Android Head Units] aplusmiami:
On my notification bar I lost all my soft buttons so I can't quickly access settings within the unit. I'm running car launcher however I reverted back to the stock launcher joying with the same results. Anyone have a clue how I can get my soft buttons back on the pull down notification bar?
[FYT Android Head Units] surfer63:
Car launcher does this indeed,. However, when you put back the stock launcher it should really display them again. Did you reboot?
[FYT Android Head Units] aplusmiami:
I went back to the stock launcher cold booted the unit and my pulldown soft keys are back. As soon as I switch back to car launcher they went away. Now I know I have run car launcher with the pull-down soft buttons what happened to them?
[FYT Android Head Units] wanb1i:
Seems to me the launcher is not seeing the soft buttons. I don't have that problem because I use Nova Launcher Prime. It's the most flexible launcher out there. You can make your display look exactly the way you want it. Then you can back it up so if you ever have to update or reflash, it's easy to get your display back. Then freeze /disable all other launchers.
[FYT Android Head Units] surfer63:
Please ask in the car launcher thread. There are the ones who might know. You're posting in the wrong thread.

Edit: if car launcher does not make this possible, you can always add "qemu.hw.mainkeys=1" to your build.prop to enable the soft keys (and qemu.hw.mainkeys=0 to switch them off)
[FYT Android Head Units] tiagofernandex:
Delete
[FYT Android Head Units] PsychoMcSatan:
Still not working for me. Decided to do a clean wipe and reinstall everything, but still no go with Live Wallpapers. I suspect issues with the included launchers as I see multiple "Wallpaper" options under Settings->Display. I froze them with Titanium Backup so things are now cleaner, but live wallpaper picker still says "Stopped working" on first try, and then just blinks and does nothing on second try. I've tried switching to Nova as well as Google Now launchers.

Also, not too comfortable with Android (obviously), but I see Live Wallpaper and Live Wallpaper Picker under /system/vendor/ as well as /vendor/ . Do these need to be moved or just copied? Why are there two copies... or are these mirrors?

Willing to do another wipe and reinstall if I can get foolproof steps. Or perhaps a Titanium Backup of a working Live Wallpaper Picker might work if I tried to restore?