yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] PsychoMcSatan:
You don't need that for install. I think he just included it for information if you want to look at the source.
[FYT Android Head Units] Redbullssg:
I just want to make sure. I thought I did everything right the I first time, and it did same very odd things. Don't want to waste another evening trying to recover.. I hope that a new flash drive is all it needed.

Adding a heat sink and fan from my old Alienware computer tower tonight. Hopefully everything will go well, sick of looking at that hole in dash, lmao
[FYT Android Head Units] rilerale:
Hello

I have a problem with the can bus protocol.

the steering wheel remote control is very slow.

It does not matter which protocol I choose.

In the original Rome, the problem is not.

What could be the reason?
[FYT Android Head Units] Redbullssg:
After I reinstalled original Joying, I rooted again, bought a new 32gb flash drive with fat32 formatted and transferred the unzipped gtx files to it. Installed the v4 Custom. Apk on the HU, then was ready to install the rom. Opened custom, inserted the flash drive, hit install custom, then verified, then hit install gtx rom. Twrp opened and then was going through the install , were no errors and then it hung at "extracting OS to /system partition" , and stayed there for over 45min...knew something wasn't right... This is Flippin me out... I'm doing something wrong, don't know what. Perhaps the wrong root?

This time I downloaded "Superuser Sofia3gr-intel" and will try that root. I used a different one before... The one that was listed in this thread.. https://r.tapatalk.com/shareLink?ur...share_tid=3616074&share_fid=3793&share_type=t

Maybe you could link the one I should be using? Please, lol.

I just Installed the newest original joying again, so I'll be ready to start over tomorrow.. Hopefully I'll get this thing up and running soon... Need my tunes...
[FYT Android Head Units] etrefal:
I'm pretty sure the SuperSU method described in the link you mentioned is deprecated - at least with regards to installing the GTX rom. [MENTION=2550900]surfer63[/MENTION] changed the rooting instructions on his JET page to the new method.

I used the package made available by [MENTION=2550900]surfer63[/MENTION] here: https://github.com/hvdwolf/Joying-RootAssistant/releases/tag/20180107. I first installed the JET apk (Joying Extra Tools) to enable adb over wifi, then connected my unit to my house's wifi, and on my computer followed the instructions on the link above to install Superuser (instructions here, also by [MENTION=2550900]surfer63[/MENTION]).

I then followed the instructions to install the GTX rom, and it worked like a charm. I had no SD cards in the unit, and used the left USB port as suggested elsewhere in these forums. The Joying units are finicky!
[FYT Android Head Units] Redbullssg:
Okay, yes, that is the one I just downloaded that I mentioned... I'm crossing my fingers that tonight everything goes smooth. I bet that was the issue
[FYT Android Head Units] Redbullssg:
I'm finally installed!!! YES!!!!! THANKS FOR THE HELP!!!!! It was the SuperSU script that would not cooperate with the ROM.. Used the Superuser apk and everything went as it should! First page should be updated.
[FYT Android Head Units] etrefal:
Happy for you, on with the customizing now! A couple of very useful Xposed modules are available like GpsSpeedFix and XsofiaTweaker, and mods of Joying apps are available in the JET app too - radio mods, Bluetooth among others.

Don't bother with the NoKill kernel mods, as this is now covered in XsofiaTweaker.
[FYT Android Head Units] Redbullssg:
Okay, thanks, I have so much to learn lol...
[FYT Android Head Units] rilerale:
[MENTION=520205]gtxaspec[/MENTION]
[MENTION=2550900]surfer63[/MENTION]

Hello,

I have to ask my question again.

GTX is installing joying ROM V9a3 with Canbus on Ford S-max.

Rom is good

Unfortunately, the steering wheel buttons do not work.

At start, go for a short time.

When it's fully up, the buttons do not go.

It used to be the original Rom.

Xsofia I have already disabled, but not the reason.

Something is blocking the learning wheel buttons in the GTX.

What is the reason.

Have already asked in the CHina RNS Forum for help.

Greetings rilerale
[FYT Android Head Units] rav2113:
will this work?

I have a witison based unit on my accord 2008

can i install this ROM to the unit without bricking?

theses are my specs:

[IMG="image"]https://ibb.co/bBqyao[/IMG]

Due to Bluetooth, WiFi, and as well as nvram patches in the ROM and bootloader, you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM. -> do I flash to joying?? can some one explain please thank you!
[FYT Android Head Units] embalu:
Hi pals,

my problem is that my HU frequently disconnects the USB pendrive during sleep. I start up the engine and the unit doesn't sees the pendrive. I need to physically disconnect and reconnect the drive again. This started to happening to me since the second firmware version of the stock 6.0 firmware, hence I tried GTX joying ROM. The error stayed nevertheless.
[FYT Android Head Units] lotte67890:
Have you tried a different USB Stick or Drive?
[FYT Android Head Units] surfer63:
That is a know "issue" due to the way units go into sleep mode (not only joying, every unit going into these kind of deep sleeps). It only happens with "usb mass storage" devices, not with sd-cards.

You might try stickmount from the play store, but probably need the paid version. You need a rooted unit for that but as you are on the GTX rom you are rooted.

Edit: I never tested it. I just read about it on several other Android head unit forums.
[FYT Android Head Units] rilerale:
Sorry for Post #1465

Excuse me,

I have tested a lot, it's not the GTX Rome.

Even with the original Joying Rome, I have problems with the steering wheel buttons.

rilerale

The steering wheel buttons work with the original Fordradio.

Apparently the Can Bus decoder is broken
[FYT Android Head Units] Redbullssg:
[MENTION=520205]gtxaspec[/MENTION] [MENTION=2550900]surfer63[/MENTION]

I successfully installed GTX V9 Alfa 3. The problem,,,, I really wanted to install V9 Alfa 4test.

I have limited use to a computer for a while, and I have been using my Phone App Tapatalk to research and search, and it doesn't search well... I searched for the term and it kept bringing up the first page of this thread. I asked a few times if this is what I need, yes, no. lost in communication. Anyway, after i finally was able to successfully install it (alfa 3), due to having the wrong Super version (needed "Superuser" and NOT "SuperSU") and causing installation to halt in the middle... So I want to start over and install V4test now that I have the actual direct link to and have been able to download it, but the problem is I am unsuccessful at a stock recovery to the Joying Rom. Or for that matter, even the GTX to clean install. It will either fail and show an error, or just reboot without doing anything. I try to boot to TWRP but it just reboots without . I tried to reinstall the CUSTOM.APK and no difference . I verify stock recovery and says it passed verification for Stock Recovery.... I just keep going round and round with this... What could be the problem?

As I was typing this I was able to recover the GTX rom, but to be honest, I don't know what build it recovered to, I had a thumb drive in my USB and don't remember what Version was on it. How do I know what version it is? I looked at that about in the settings, but not sure what im looking for. Also, I am pretty sure there wasn't a calculator install the last time(v3alfa) on my desktop.

Im going to attempt to recover to Stock Joying and start over... But if anyone can add their input, I would greatly appreciate it.. I don't have a lot of confidence this is going to work....

---------- Post added at 05:27 PM ---------- Previous post was at 05:02 PM ----------

The error Message I when either trying to recover to OEM or boot to TWRP

Supported API: 3

finding update package........

opening update package........

verifying update package.......

E: failed to verify whole-file signature

E: signature verification failed

Installation Aborted

Last Flagged SOFIA6.0!

Error wait here........

then reboots

This is after I either hit Restore Stock, and verify it, then reboot to TWRP, or install Custom, verify , then install GTX ROM, or try to put in my thumb drive with the Newest Joying rom I had on the HU before and try Restore Stock, verify , and boot to TWRP, or from after Verifying and then rebooing manually...... Nothing seems to work.... I am not able to install the OEM Joying Rom to start over....
[FYT Android Head Units] Redbullssg:
Okay, been messing with this thing for over 10hrs now..... Trying everything I could think of, and doing it over and over. Searching the forum for answers... Now, I discovered something, may or may not be a bug. Before when I installed the V9a3 and wanted to recover to the Stock Joying January rom, after I switched to Stock Recovery in the Custom.APK , I went to the System Settings and hit the Back up Restore, and it would crash and say it had to close.... I assumed that you, [MENTION=520205]gtxaspec[/MENTION], blocked it so that we had to use the Custom app and go through the TWRP boot to do it....

Okay, I mentioned before, after many attempts to do a recovery, even reflashing the GTX rom, I thought I accidentally installed the V9a4 because the home page looked different. Well, i think it did, but I never thought of going to setting/backuprestore again. LOL, I just did, and it opened..... Went back to Custom app and Stock recovery and verify , then back to settings / back up restore and reset the Unit with the Stock January rom on flash drive and it did it...

I have to say, I picked the worst weekend to do this, as i figure most of the Peeps are out doing things, and I am here just trying to get this done will I have free time. Always working...

Anyway, going to start all over, again again, and want to thank all ya, especially the guys doing all this hard work..... I want to help in any way I can, and if that is a bug, I hope brought it to attention and helps someone.

okay, now, I down loaded V9a4 and the custom from here but as I mentioned before, I had trouble with the "SuperSU" version to root and the V9a3, and had to use "Superuser" instead. I am wondering what version I will need to root with for V9a4? I'm sure I wont get a reply before I mess around with it, so If I do have an issue, and or figure it out, I will update it here so that it can be confirmed... I will try what I had success with the last time (Superuser) first...
[FYT Android Head Units] Redbullssg:
Installed fine with the Updated Superuser.
[FYT Android Head Units] sanangel:
I just installed the rom, I'm very happy.

But, with each start, I get the message "updating android", any solution? Thanks
[FYT Android Head Units] lexuz:
does your unit go to sleep when you remove the key? Or does it just start like if it was off?
[FYT Android Head Units] sanangel:
It is every time I start the vehicle and the unit restarts again.

The unit shuts down each time you turn off the vehicle for a period of more than 10 or 15 minutes.
[FYT Android Head Units] amadare:
You might need to look at how the power and acc wires are connected. My car can be off a day and when I turn the key on the radio is back at home screen in a second.
[FYT Android Head Units] lexuz:
like said before me, check your wiring. My radio can stay a week in sleep without having to worry about a flat battery.
[FYT Android Head Units] Astur_Torque:
sometimes I notice the ROM goes very slow.. even with fan mod and perfomance gobernor... I don't know why
[FYT Android Head Units] sanangel:
I appreciate your response very much. But this is not the problem... Joying sleeps very well for me.

With the installation of this rom, with each new boot, I always get the message "Android is starting." I've tried to erase data again, but it's still the same ...

I'm also going crazy looking for a way to remove the beep every time the screen is pressed. There is no option "... amp" in the configuration menu ...

P.D. The rom version I installed is v9 alpha 4.
[FYT Android Head Units] sean19661:
You might want to check for duplicate apps in the Rom check your installed Rom or check gtx Rom for them with root explorer use to happen with roms for phones also did you do a dirty flash ?
[FYT Android Head Units] Redbullssg:
The only time does that is if it's been booted or rebooted, not woke up from sleep.

---------- Post added at 02:15 AM ---------- Previous post was at 02:04 AM ----------

[MENTION=520205]gtxaspec[/MENTION] Installed GTX V9a4test, everything seems good, all working that I can tell so far, except the one thing I wanted to work... VIPER is not working. It does nothing, no sound changes when changing settings, EQ, etc..

What could be the issue?

Just installed it in the car. Wish I had hooked up speakers when I had it setting one my desk, lol..
[FYT Android Head Units] gtxaspec:
did you enable the viper module? I know the first time you launch it it asks you to install the library and grant root in order to do so.
[FYT Android Head Units] Redbullssg:
Enable it how? When I opened it, Superuser gave it permissions, and it asked to install the driver.
[FYT Android Head Units] surfer63:
That's correct and then you need to open Viper and enable it.
[FYT Android Head Units] sanangel:
I'm sorry, but I have not understood your answer very well.

Do you want to say that the problem is that my device does not turn off properly?
[FYT Android Head Units] surfer63:
A cold boot means that it was not in sleep mode, but completely switched off. This happens due to a malfunctioning app keeping a wake lock (sometimes simply because it hangs, or one of its broadcasting services still hang). That will prevent the unit going into sleep mode. After approx. 20 minutes the entire unit is really switched off in that circumstance.

When your unit displays on every boot the "android is updating " message, then there are errors in dalvik cache. Most probably the same malfunctioning app is causing that. So please check which additional apps you have installed. First try by uninstalling/reinstalling.

If that does not help, you really need to do a "reset to factory defaults".

Also: If you did a dirty flash, you can run into the exact same issues. As updated apps might use a different setup storing method/database, which conflicts so much that it crashes on that every time. Remedy: Do a "reset to factory defaults"
[FYT Android Head Units] sanangel:
Thanks for your answer.

The truth is that the installation is clean and in fact, after giving the error mentioned, I went back to do a factory reset and I still have the same error with each boot.
[FYT Android Head Units] usa911g:
Does someone has the same problem?? sometimes the unit Resume from Standby, Bluetooth can't Auto Connect the phone, I need manual connect the phone. why??
[FYT Android Head Units] Redbullssg:
Enable, you mean turn it on? I have opened it, turned it on, ticked everything and nothing makes a difference.

---------- Post added at 04:17 PM ---------- Previous post was at 03:20 PM ----------

I just went to the Viper4android official xda thread and found in the trouble shoot /Faq section it said @

4. Why installation fail?

A: Root or SU binary issues. Use latest SuperSU.

5. Why is superuser not supported?

A: V4A does support superuser. Some superuser version have bugs, please use a stable version of it.

It installed, but obviously not working. I have Suoeruser installed. May be that it was compatible enough to install, but not work properly...

Now a question, because I dont know a lot about this stuff and learning, following instructions to a T,,,, to install Super SU, can I do so just by uninstalling Superuser, and reboot, and install SuperSU. Or do I have to start from scratch again and clean sweep and reset reinstall GTX V9a4test?
[FYT Android Head Units] sean19661:
I would reflash stock Rom unrooted do a few wipes

And see what happens from there. I wouldn't flash test Rom too many bugs look for stable Rom
[FYT Android Head Units] Redbullssg:
I was told by [MENTION=520205]gtxaspec[/MENTION]t to use the V9a4test for Viper to work correctly. I've done a unrritted flash to stock rom and did a few wipes deleted all in the folders and started from scratch to install the gtx rom. But, I started with Superuser, and since I didn't have any issue with the install, I stopped there. My main goal is to have Viper full function. So question is now, to install SuperSU, do I have to start from scratch, or can I simply Uninstall Superuser,, and then install SuperSU

---------- Post added at 04:37 PM ---------- Previous post was at 04:31 PM ----------

The only reason I don't wish to go through all that, was because I had a very difficult time getting anything to flash... Never really nailed it down. But think it was flashing from USB thumb drives. Once I put it on my SD card, I had no issue.. But wasn't sure if it was Supersu or SuperSU...
[FYT Android Head Units] sanangel:
Sorry for sure that the question is already answered, but it's 101 pages to reread again ...

Is there a way to restart in twrp ?, I'm in V9a4test
[FYT Android Head Units] surfer63:
The problem is that most rooting options are now installed "system-less" which means that "everything" is installed in the boot image and no longer in /system. The boot image is unaccessible on the Sofia units (and I expect the the same for the PX5 FYT units), which means that we have to install su and system_app in /system (and there are a few other files not relevant for this).

The problem is that Xposed has it's own app_process (_32 or _64) in /system/bin. The SuperSU and Xposed version conflict in this case.

That is why we use an older Superuser which has everything inside the su (200 Kb versus 100Kb for SuperSU), and which does not need an app_process (in /system/bin). So, now we can install the Xposed app_process in /system/bin.

And now with regard to your (XDA's) mentioned errors in Superuser, which are supposedly not in SuperSU: It doesn't matter at all!

May 2017 was the last correct working ROM with Viper. "Everyone" was on SuperSU at that time. Everyone was on Supersu until end of December 2017. lbdroid introduced Superuser somewhere in Sept/Oct 2017, because Superuser is open source and SuperSU is not, and also because it was so much simpler (everything in one su binary) . I then "discovered" that Superuser didn't need a app_process32 and started experimenting with Xposed and Superuser in January 2018.

But since May 2017 and early January, with SuperSU, we also had issues with Viper. It simply is something in the kernel (or alike) from the Joying/FYT units,
[FYT Android Head Units] Redbullssg:
What are we talking about here? Don't know if we are on the same page, talking about the same thing, lol
[FYT Android Head Units] surfer63:
You should create a usb stick with the files from here: https://github.com/superdavex/joyingsofia/tree/master/TWRP_recovery_boot and then reboot into TWRP.

What do you want to do?
[FYT Android Head Units] Redbullssg:
So if I have Superuser on my system, I shouldn't be having any problems as far as that is concerned..... Is it possible to have both, mixed, and possible to Uninstaller it, or them and reinstall it without a complete rom reinstall?

---------- Post added at 06:36 PM ---------- Previous post was at 06:30 PM ----------

Thank you BTW for taking time to help. I've been working on this for days now, lol, and every time I think I'm gold, I find I goofed something up. Not even sure how I have.. I think my issue all along was my USB drives, and I kept thinking it was other things, like myself... All I really want is Viper4android to work, and all else as well, but most of all that.

---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------

All other things seem to be working properly, so far as I can tell since I have had it installed since yesterday, except Viper. I'm about to go out to the car and mess around with it for a while. I just don't know what to do at this point.
[FYT Android Head Units] gtxaspec:
over complicating things, supersu has nothing to do with your installation issue, it was most likely your flash drive or sd card btw.

the basic diagnostic method on these units is simple:

if it doesn't work, undo what you just did. if you can't, then re-install.

in your case, use custom to re-install the custom recovery, and put your flash drive with v9a4 in the unit, and then click install gtx rom. and try again.

thx
[FYT Android Head Units] gtxaspec:
if he has the custom rom installed, TWRP is included on the rom by default, you only need to use the custom app and click on REBOOT TO TWRP.
[FYT Android Head Units] sanangel:
I wanted to try to make a dalvik wipe and cache. I'm getting a little crazy with the "android is getting started - starting applications" and with the fact of not finding the way to remove the annoying "beep" sound every time I touch the screen ...
[FYT Android Head Units] gtxaspec:
Ok let's Begin again...

What exactly is your issue? The unit is not sleeping, and is cold booting every time? Did you install any third party apps after the initial install? Have you tried to re install?
[FYT Android Head Units] sanangel:
Yes, you're right, I think I've explained myself wrong from the beginning.

I apologize

I have installed v9_alpha_4_TEST and it works very well for me. The only two problems I've seen so far are:

1. with each restart of Joying, when starting the rom, the message "Android is starting - starting applications" always comes out. After a few seconds with this message, the rom works fine.

2. I am not able to remove the "beep" from the sound when I touch the screen. I do not have the option "enable amp" in the configuration of the vehicle and I do not see how to remove it.

For the rest, the rom goes very, very fast for me and if I could solve these two problems, I would be very happy.

Thanks for your rom and for your help
[FYT Android Head Units] gtxaspec:
Explain number 1 please...is this each time you force a restart it the unit, or when you turn the ignition key off and on?

2: go to car settings, and the last tab, password is 3368, look for amplifier option, select no amp.
[FYT Android Head Units] Redbullssg:
Select no amp, then while still in car settings goto the EQ settings tab at the bottom and the button will be there.
[FYT Android Head Units] sanangel:
It happens with each new start of the vehicle when Joying restarts, not when less than fifteen minutes have passed and Joying does not restart.

I think what is called going to sleep, is this correct?
[FYT Android Head Units] Redbullssg:
I just finished reflashing the custom GTX 3 separate times. First time, went straight to Viper and opened in. Asked for permissions, and then to update the driver. Did all that it asked. Only other thing I opened was radio, because I wanted to know if by turning it on, or changing any settings, the EQ, etc., if it was making any difference, and there was no difference. It wasn't working... So reflashed, skipped the install of the driver, same thing, no effect. Played with a few things in hopes that somthing would happen. Reflashed one last time, and still nothing.... Also, each time I rebooted after install..

Everything seems to work fine except Viper.. Also, each time, in Xposed, there is no module to tic for Viper...

I'm at a loss...

Only question other that what could be wrong is, I have my entire speaker system hooked up to low level (RCA). Does Viper effect the rca channels?
[FYT Android Head Units] Beatwolf:
Where can we download "V9a4test" version? Please put updates in the first post -thanks!
[FYT Android Head Units] gtxaspec:
You are enabling it in the"phone speaker" area right? Turn master power on.
[FYT Android Head Units] Redbullssg:
If by enabling, you mean turn Master Power on, then yes.. There is headphone,, phone speaker, Bluetooth, etc. I even tried them all...

Phone speaker is what it defaults to open up to.

---------- Post added at 10:26 PM ---------- Previous post was at 10:09 PM ----------

[MENTION=5944015]sanangel[/MENTION] does Viper work for you?