yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] gtxaspec:
Very strange, I've never seen that error displayed on a joying unit. Can you out line the steps you took to install? We're you on 12 15 build of stock or newer?

You can disable the overlay in settings on MainServer, UI server, process server, and that should make the errors go away.. also XSofiaTweaker has a patch to eliminate that overlay completely.
[FYT Android Head Units] amon101x:
i had that Problem too with the yellow MCU bar. I reinstalled the stock rom (September i think 5.25 MCU Version) after that i installed the january stock and then GTX rom now everything works except the LED after shut down issue
[FYT Android Head Units] pyrlix:
I updated from the January 26 Build. I first updated my device to the most recent version using the Jan-26 9.20 Build, rooted it, installed your updater, then TWRP'd it, installed the rom and boom this.

Good to know that the Tweaker can disable it, its quite annoying since you cannot install apps by hand, Amaze wont run because you need to give it perms and android says it detected an overlay.

Do you have a new or old model? I think i have to use a fairly new Update but dont know, its a JY-VM130N2... i first updated to the January 26 MCU9.20 Version and then updated to GTX Rom.

Off-topic: Greetings from LU :P

What i could try is to "downgrade" to the Joying Jan-26 build with the MCU Version 5.25 and then reinstall everything.
[FYT Android Head Units] gtxaspec:
Yeah I believe you needed 5.25... If you get that error and you have a joying unit
[FYT Android Head Units] amon101x:
Yes my unit is the same as yours. But you have to downgrade it to a version like the September Rom i tried to "downgrade" with the stock january rom and i still got the same MCU error

September Rom or November Rom -> January Rom -> GTX Rom (worked for me in this order)

PS: Moin nachbar :D Falls du noch fragen hast schreib ne PM
[FYT Android Head Units] pg33:
Can I use this rom on an model with digital amplifier?
[FYT Android Head Units] KevinSlark:
Soft Brick?

I got GTX up and running today fairly easily, I'm happy with how everything looks and was working on the bench. Then xposed installer informed me it was time for an update, I wasn't thinking and chose for it to update while Android was booted and not in recovery.

I seem to have bricked my generic FYT6023 (sold by Seicane). It spent an hour on the Android loading screen, I then disconnected the power and let it cool for another hour.

Let it run at Android loading screen for another fifteen minutes with no luck. Then proceeded to attempt to reflash GTX, didn't work due to stock recovery. Then tried to flash stock ROM (12.21.17) and it gets to Customer=1 (I think) and kicks me out of the process.

I've tried doing a hard reset through several methods to no avail. The model I have has physical buttons if that matters.

I'm obviously doing something wrong. Any guidance?
[FYT Android Head Units] gtxaspec:
Two options:

First :try to flash the January stock ROM

Second: get a usb to Ethernet adapter, hook it to the unit via USB and then Ethernet cable to the laptop, set the IP on the laptop to 192.168.65.10

Boot the unit to where it sits on the an Android screen

Then use ADB to connect to the unit

ADB connect 192.168.65.100

Then run the commands :

./recovery_maintenance.sh install_custom

Then reboot with the gtx usb flash drive inserted.
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION], i'm thinking to come up with a solution to install apps as user, instead of system. Plus side will be easy updates and JET should work better. I will have a solution soon I hope.
[FYT Android Head Units] surfer63:
Thank you, but I will change it anyway to make it more stable. When I switched from appinventor to thunkable I also got another package name, and then I rewrote JET to use the new one and simplified it. I can do it even simpler and that is what I want and no longer use the internal package path in /data, but use /data/JET. Once created it will always be there and never change.

Also: when I still made ROMs for Archos tablets I had a number of 3rd party apps that would simply be installed on first boot using the "pm install" command, to install them as 3rd party apps. It uses user data space, but makes it for the users much simpler to uninstall them or upgrade them.
[FYT Android Head Units] KevinSlark:
That worked! Thanks for developing an awesome ROM and for your lightening fast and extremely helpful support.

Keep up the good work, I thoroughly appreciate it!
[FYT Android Head Units] KevinSlark:
Okay... One more question that's over my head.

The generic unit I have came with a DVD drive. I want to remove that drive to use the space for a cooling solution. The JY based apps give me the attached error about a disconnected serial cable. I ensured dvd=0 in fyt.prop, I don't know where to find this code to disable it.

Thanks!
[FYT Android Head Units] gtxaspec:
try ro.fyt.dvd_enable=0 in fyt.prop
[FYT Android Head Units] RoNeReR:
download the xsofiatweaker, and mark to hide mcu error.

it will hide all the overlays messages.
[FYT Android Head Units] gtxaspec:
Nice work.
[FYT Android Head Units] naighba:
Just pushed yes on the xposed update and now I am on a bootloop. What can I do? Thanks in advance
[FYT Android Head Units] buurman42:
Struggeling with google OK, Ok it works, but conversations can't be made. Can you please tell if your fix works, and where te download? Thanks in advance.
[FYT Android Head Units] KevinSlark:
I did this on Saturday. I had to go back to the January Joying update, reroot, and then reflash GTX v9a2.

I haven't found notes on a reliable way to update xposed automatically. I believe that if you do the following it *should* work (no guarantees).

1. tell it to create a .zip to flash in recovery,

2. go through a failed recovery boot

3. hard reboot back to Android

4. Use custom.apk to boot to TWRP and don't make it permanent

5. Install the xposed update .zip via TWRP

6. Reboot

6a. ???

7. Profit!

Option 2: look back a few posts and GTX shared how to fix this with ADB if you have a USB to ethernet adapter.
[FYT Android Head Units] andytuinman3:
You need to reflash the original rom and then go back to gtx. At least that's how I did it when I made the same mistake
[FYT Android Head Units] gtxaspec:
We should make an Xposed patch for the Xposed installer to disable the updates...
[FYT Android Head Units] gtxaspec:
Updating Xposed will not work at all no matter what. It's a special build crafted from the magisk version.
[FYT Android Head Units] gtxaspec:
OK...so I have made an Xposed module which disables the function of the Xposed Installer updating the Framework...will be included with v9a3... no more accidents.
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION] should include it in XSofiaTweaker soon...
[FYT Android Head Units] edit:
Please share it here as an apk. Thank you !
[FYT Android Head Units] gtxaspec:
https://drive.google.com/open?id=1fBA7kXRLNZDKvgPEfLk8BgeWB-ya6Hwc
[FYT Android Head Units] btrax:
Hey, I wonder something. I figured out that the sound from spotify is clearly lower than Music player or radio or BT music. Can we do something to increase the volume as the same volume of the other app ? (for example with a music player, I'm at 20 and for spotify at max 36).
[FYT Android Head Units] SkyBehind:
You can go into Car Settings and then the advanced settings tab (the one where you have to enter the 3368 code) and go to Volume Levels or something like that. There you can adjust the volume levels of the different inputs.
[FYT Android Head Units] ch_swat_89:
HI there

I installed the rom today. Everything good, only one problem (like in joying rom):

If I set "ok google" to "work in all screens" i can't make/reply phone calls. The caller only gets a strange noise.

Is there a fix for this?
[FYT Android Head Units] gtxaspec:
You need XSofiaTweaker, check the other thread. Merely installing and enabling the module in Xposed solves the issue.
[FYT Android Head Units] yebokmj:
Is there any way I can get help trouble shooting the Waze concern I've been having with it loosing GPS signal though the unit has not? Currently on 9A2 I have added passive cooling but have yet to add a fan. Could it be that Waze is just to much of a resource hog compared to Google Maps which works perfectly fine? I'd really prefer Waze for it's user participation that helps with police and other alerts. I have no other issues with the unit. I know my wife's unit also has similar issues.
[FYT Android Head Units] gtxaspec:
I use waze EVERY day. it is my most used app because i have a long commute every day. No problems at all... runs really smooth. I would add a 120mm fan...no need for a heatsink. Then run in performance mode.

what other apps do you have?
[FYT Android Head Units] yebokmj:
I have Waze, BtSsm, Amazon Music, chrome JET and Google maps. I'm using running the first three. How do change to performance mode? I've followed the whole thread and don't remember how. While I have your attention how can I get the unit to have a usable front camera? I have the Joying one and I want to be able to run track addict or Harry's Lap Timer.

Thanks
[FYT Android Head Units] suprman:
I installed this ROM, but I only get sound in the left rear speaker. Can this be something related to this ROM or Viper4Android? The head unit has been out of the car for a couple of months, and the last ROM I installed was from October, but I have never had this problem with the Joying head unit or the stock radio.
[FYT Android Head Units] farmerjohn:
Did you install gtx ROM directly from the October ROM? You have to have at least december or january joying ROM, see first post for details.
[FYT Android Head Units] suprman:
No, I installed January ROM first
[FYT Android Head Units] farmerjohn:
Does EQ-App (fade, balance) work? I had this with V7 (left front speaker), but not with V9.
[FYT Android Head Units] surfer63:
I had something the same but for front-left. When I went into CarSettings in the "audio section", it turned out that the divider(left/right/front/back) was 100% front-left instead of centrally. When I repositioned it and saved it, my audio worked correctly again.

At that time I was just wondering why this had happened, but did not think any further about it.

But maybe it is a setting that the gtx ROM does not correctly pay attention to upon installation, or overwrites, or ...?.
[FYT Android Head Units] gtxaspec:
We don't touch any settings...that's all stock joying settings bugs. I've run into issues like this before, where the BD37073 settings are corrupted on re install and you have to re set all the audio stuff.
[FYT Android Head Units] Astur_Torque:
The base of this ROM is the Joying Juanary or the March one?
[FYT Android Head Units] gtxaspec:
There's a March ROM? Not to my knowledge for our units. the one posted on the joying blog is the Jan ROM.
[FYT Android Head Units] gtxaspec:
really? very strange, it works for me just fine. Did you dirty flash or upgrade from a previous installation?
[FYT Android Head Units] gtxaspec:
I'll release a new version of custom that has the one click performance enabler soon. As far as front camera, I use an analog camera that has analog out that goes into the video in port on the back of the unit. If you have the USB version of the dash cam from joying, it should work as long as you have the right APK, maybe someone else can chime in on that one.
[FYT Android Head Units] gtxaspec:
Strange, I would check the EQ/Fader app try changing the fader, also check the harness connections. I have had issues before where the plug wasn't fully seated in, there were some issues with the unit powering off and no audio ( i remove my unit from the dash almost daily lol)
[FYT Android Head Units] farmerjohn:
Sorry, to be honest I do not remember. I came from V5, might have been a dirty flash to V7. Audio settings were corrupted and the fade/balance setting had a serious lag or didn't react at all. Anyway, all fine with V9
[FYT Android Head Units] gtxaspec:
ahh I miss read, I thought that you stated that it wasn't working with V9. everything (should) work with V9 =D
[FYT Android Head Units] Astur_Torque:
Yes you're right. I confuse it with a new version due to it was published on the 1st of March
[FYT Android Head Units] SkyBehind:
Not sure if this is the correct place to put this, though I do use this ROM v9a2, it may be more general. I also read through this thread (among all the others) and I'm unclear if it speaks to the issue... the auto connect with proximity.

My wife and I both have the Joying Sofie (I believe JY-128 or something). I have an Android, she has an iPhone. Th behavior is the same one both.

When we get in the car, bluetooth connects for phone usage. It shows as connected in the bluetooth phone app on the head unit. Now if I go to setting on the head unit (the android settings) it doesn't show the phone as connected. If I tap it to initiate, it connects no problem. I can then use bluetooth tethering for internet.

Now it's also possible to disconnect bluetooth and have it be connected in the android settings (and use tether) but have the phone app show disconnected (and not be able to use the phone).

I guess my question is, is bluetooth segmented into two different places on the head unit, independent of each other. As in Android settings bluetooth works independently of the Phone App. Is there a way to have it connect on the settings side automatically (so I can use bluetooth tether) just as it does with the phone app?

Any thoughts would be appreciated.

EDIT: Let me add that with my Android, I have managed to get it to autoconnect to both bluetooth using Bluetooth Tethering Manager. I can tether without any apps, it's jus the autoconnect part that doesn't work. I don't think there's a similar app available for iphone, but again once I manually initiate connection, tethering works.

EDIT2: SOLVED! OK, so this issue is in fact solved with the Bluetooth Tether app. I was thinking that it was a client and server side app (which would be a no-go for iPhone), but it does in fact force a PAN connection check upon bluetooth connection. So I tested it a bit and so far it works after car power on. I'm not yet sure about after a full reboot, at the moment I'm thinking it has to be run once.
[FYT Android Head Units] kkaaffee:
how can I proceed in case of bootloop?
[FYT Android Head Units] surfer63:
Get the latest Joying stock ROM and write it to a usb-stick / sd-card.

Insert it into the unit.

Use a sharp needle (or so) to reset the unit, wait till the bootlogo, reset again, repeat.

After 3 times the button leds will blink pink and the Joying stock ROM will be installed.
[FYT Android Head Units] kkaaffee:
After doing those steps I get "Supported API: 3, Last Flaged sofia 6.0! Error wait here ..." and thats it.

Tried with usb and with microsd
[FYT Android Head Units] gtxaspec:
That means it's not detecting the installation media properly. Make sure if you are using usb to remove SD cards. Also try a different flash drive if it still doesn't work.
[FYT Android Head Units] abay1289:
I just had this problem myself when trying to install this room for the first time.

After installing the custom.apk, I opened the app and went straight to installing the gtx rom. I skipped "Install Custom" from inside the app. You might try that step again. Maybe it didn't install correctly the first time.
[FYT Android Head Units] kkaaffee:
It's so weird that it previously worked from that usb drive ... but it's true another drive did the trick.
[FYT Android Head Units] gtxaspec:
I have solved the yellow MCU band appearing...v9a3 will include both versions of the mcuallupdate.bin, one for 5_25 and the other for 9_20... for now you will have to manually copy whatever version applies to you to /system/mcu. researching a method to auto-detect and install the appropriate version.

[MENTION=2550900]surfer63[/MENTION], any idea which units use MCU 9_20? is it the 6021 units...?
[FYT Android Head Units] myxcon:
Mine is 6021 (99% sure) with 5_25 MCU.
[FYT Android Head Units] ste2002:
Mine too (6021 + 5_25 before update from Sept'17 to Dec'17. Now MCU (afair) differs in above numbers, will check later).
[FYT Android Head Units] surfer63:
I don't think so.

Just before my 5009 no longer worked, I was already on 9.20 (as far as I can remember). I think it was in the October/November ROM and everybody could/should upgrade then, no matter whether you had a 5009 or a 6021.
[FYT Android Head Units] myxcon:
You can upgrade the MCU? How can that be done?
[FYT Android Head Units] ste2002:
Now MCU is dated 25.10. MCU was upgraded during FW upgrade, I believe. No yellow ribbons.
[FYT Android Head Units] surfer63:
Should be possible with:

- copy the file "STM8UD.BIN" to the headunit. ( you can find it in the stock firmware )

- press the magnifying glass on the Mcu Upgrade screen. ( the one that pops up every time when you have the yellow Mcu error )

- select the file "STM8UD.BIN" and press update (or upgrade)

- press Mcu Update button on bottom. The headunit will reboot at the end of the procedure. ( the yellow bar will disappear )
[FYT Android Head Units] sterod:
I just got my Joying Intel unit today and installed this ROM, Many apps in Google Play cannot be installed as they state "not compatible with your device". For example, Netflix.

I don't think this is a fault of the ROM, but is there a way around this that is more elegant than exporting the APK from another device? With LineageOS on my tablet I get around this with Magisk to bypass safety net checks, etc.
[FYT Android Head Units] carter.w.jason:
Just got it installed, is it normal during the install, to get to welcom screen, then have screen go corrupt, reboot and repeat that 3 times? That was a scary install, haha.

Got Xposed Additions up and running, so were off to a good start. Feels great so far, root!! Cant wait to tinker more. Thanks
[FYT Android Head Units] gtxaspec:
Not typical, seems like memory corruption. Happens sometimes when we kill zygote during initial boot.
[FYT Android Head Units] a71977:
Hi

I just installed GTX V9a2 and my isssue is that, when i use JET v46 to install radio mods - after reboot nothing happend.

Have missed something here?

---------- Post added at 08:23 AM ---------- Previous post was at 08:22 AM ----------

Hi

I just installed GTX V9a2 and my isssue is that, when i use JET v46 to install radio mods - after reboot nothing happend.

Have missed something here?
[FYT Android Head Units] pyrlix:
You guys are some crazy good lads. I did that now, got rid of the yellow ribbon (on my "RNS"), but the System loses its information about the CAN Box (in my case a RZC VW (L) or so), and i cant put it back without rolling back to the old broken/too new MCU Update. Do i go right in my thinking that i have to fully recover Stock ROM, reroot it and reflash GTX?

Wouldnt be dramatic, but if it has to be done, it has to be done.

Unless I can install the 5.25 MCU via the USB-Method, and copy the whole MCU-Update files that belong to the /sys/mcu folder from a working 5.25 to the current HU.
[FYT Android Head Units] gtxaspec:
Wait for v9a3...soon.
[FYT Android Head Units] carter.w.jason:
Well F me, Xposed Additions breaks sleep, this is not good for me. It would not break sleep on the Joying PX5.
[FYT Android Head Units] gtxaspec:
Which Xposed addition? Xposed itself doesn't.
[FYT Android Head Units] carter.w.jason:
"Xposed Additions" is the module name. Its a button re-mapper app I use alot. I did a force-stop before sleep and the unit still restarts, would only sleep if I remove the module.
[FYT Android Head Units] gtxaspec:
I'll check out the source. Which buttons are you trying to remap??
[FYT Android Head Units] carter.w.jason:
F1 - F12, My SWC buttons acts as a USB keyboard into the headunit. Bench testing with just a normal keyboard right now.

I have found a workaround for the moment. Button Mapper by flar2 has most of the same features and is able to detect USB keys. Though it lacks app context mapping.

....and then the issue with that is Accessibility Services always gets turned off during sleep, which the app needs to work, every android headunit seems to act that way. Any way to change that?

On my MTCB I used Secure Settings to turn it back on, on every boot up.

edit: Accessibility toggles are now staying set. Not sure what was going on. Maybe I need more sleep, break from Android projects. MotoGP vacation coming soon

...I was killing the app from recents, that was resetting the accs service. I'm dumb and too used to the holiness of Xposed
[FYT Android Head Units] etrefal:
Just installed 9a2 over the december 15th ROM, and I'm impressed by the smoothness of the whole thing. I have much customization to work on, but so far it's so much better!

Thanks to the active cooling I installed last year, the install(s) went pretty quickly and without problems. I did a factory reset before flashing the Dec.15th ROM, and went straight to installing Custom and v9a2 after that - I was on the July 2017 update before that, the one that came with my unit.

Thanks [MENTION=520205]gtxaspec[/MENTION] for the excellent work, and [MENTION=2550900]surfer63[/MENTION] for JET! I'm eager to see what v10 will have in stock...
[FYT Android Head Units] gtxaspec:
Don't forget to try XSofiaTweaker!!! That's more good stuff !!!
[FYT Android Head Units] carter.w.jason:
In XSofiaTweaker, can you clarify when "Resume" is triggered? I have not been able to detect it yet, from sleep, call end, etc. Must be doing something wrong, but have triple checked the system call.

Is there any way to trigger "screen off" via intent, shell cmd, ect? I have read that the Mute key does this? but I would like to remap it. On my old system I ran a steering wheel button to inject gesture and turn screen back on.

Last Q, USB DAC support, is the volume mirroring bidirectional? If I was to set a volume level via Tasker would that reflect back onto the SYU value.

Still waiting for my DAC to come in, just very curious.

Thanks!
[FYT Android Head Units] Beatwolf:
Installed GTX Rom yesterday, so far everything seems noticeably faster -great work!

I do have one issue though -the radio app is gone. I installed one of the newest radio mods from JY Extra Tools, and upon a reboot a bit later the radio ran in the background but the app was nowhere to be found. Should I just try to reinstall the original radio apk? Also can anyone commen on some good settings for Viper4Android? Or just go ahead and turn on everything?
[FYT Android Head Units] RoNeReR:
with usb dac mod in XSofiaTweaker u dont need the syu value, all volume options on tasker will work.
[FYT Android Head Units] surfer63:
If you press the HOME button long enough (2-3 seconds?), the Android part goes into sleep mode. The radio hardware like the radio chip, AMP, MCU and the like will still be active, unlike in deep sleep (ACC_OFF) when also these hardware parts are switched off.

So if you activate the Android part of the system again it comes out of RESume.

Yes, The Mute button triggers a "screen off" when pushed for 2-3 seconds. I assume we should be able to find the method/intent doing this, but until now I did not search for it. You are the first to ask.
[FYT Android Head Units] gtxaspec:
yes, v6 will have viper included included.
[FYT Android Head Units] gtxaspec:
[MENTION=8578937]ste2002[/MENTION], if there are any translations for the built-in joying apps, I could also merge those in. Let me know ! Thanks!
[FYT Android Head Units] dyabolikarl:
Good work guys!

Looking forward to new releases.

Seems a LOT quicker than stock.
[FYT Android Head Units] surfer63:
The guys (Thoma and ChineseCrap) on the china-rns forum are making German translations for the Car Settings app, which is in general extremely badly translated in English and even worse in German.

They had the December version completely translated and now the 26 January version has a few new options.
[FYT Android Head Units] CODEONETEAM:
CyanogenMod File Manager

https://xdaforums.com/android/apps-games/app-cyanogenmod-file-manager-apk-v1-0-2-t3058506
[FYT Android Head Units] sosfinger:
Talking about translations, I could help with italian translation if you need it.