yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] swanie2000:
Put the joying stock ROM on USB, and connect to head unit.

Reboot the head unit(reset switch) and wait.

May have to reboot and wait, up to 4 times, but it should start back up, and begin loading Joying ROM.
[FYT Android Head Units] merdok:
Like some of the others I have ran into issues trying to dirty flash from v6 to v7. The unit boots into twrp, so i am not certain that I am revert back to Joying. I tried to apply this update while on lunch hour so have not tried to poke at it too much.

Should I try and flash something from the USB or try and reset with Stock Joying update?
[FYT Android Head Units] btrax:
I had exactly the same thing. I turn off my car and waited half an hour (not in the car ^^) and when i went back to my car, the HU booted normally.

After that I did :

via custom.apk :

- Flash Custom Recovery

- Install GTX ROM

And that worked :)
[FYT Android Head Units] gtxaspec:
If you can boot into TWRP, put a flash drive with the gtx ROM and it will automatically install.
[FYT Android Head Units] Lowen SoDium:
I have this same issue. What is the correct SU version that worked for you?
[FYT Android Head Units] hidroela:
i ran into issues upgrading from v5 to v7

at first try from custom apk didn't boot in to twrp , on second try it did but after installation it went in to the android boot for ever.

v5 was running just fine

have to start all over again
[FYT Android Head Units] texastwurkteam:
Trying to load up the Joying ROM and it gets to about the same point where the V7 ROM crapped out and then I get stuck here. Any ideas?
[FYT Android Head Units] gtxaspec:
That means you are still on the custom recovery. Use a flash drive with the gtx ROM. You don't have to go back to stock
[FYT Android Head Units] merdok:
My issue might be caused having more than one USB drive plugged in? I noticed in the debug lines that it was complaining about 5009_60_gtx.zip

I pulled out my music thumb drive and tried to reboot to recovery to hook that script again.. but it didnt work for a 2 or 3 attempts and got pulled away from work call. the debug option didnt show it was attempting to do anything.

I kind of doubt this is the case since I didnt get any error from extracting the file, but is this the correct md5 for v7?

4a565bf969304fff34d00231a550120d
[FYT Android Head Units] Lowen SoDium:
Does the custom.apk work with SuperSU at all anymore or does it require the other SuperUser root method?
[FYT Android Head Units] merdok:
It did not work for me with SuperSU. Surfer63 script to install Superuser worked for me. https://github.com/hvdwolf/Joying-RootAssistant/releases/tag/20180107
[FYT Android Head Units] gtxaspec:
Just a quick note that because you are dirty flashing, the precompiled dalvik cache is not copied, and due to gapps being upgraded from earlier versions, the first few boots might take upward of 20 minutes... No need to worry about the unit restarting during this process.
[FYT Android Head Units] gtxaspec:
Yes, only have one drive plugged in at a time.
[FYT Android Head Units] texastwurkteam:
Stuck back on here for the past 30 or so minutes; the place it first froze up. It's still doing the ravey light show but making no progress. I guess my only option is waiting?
[FYT Android Head Units] gtxaspec:
Negative. Reboot the unit and start again. Make sure you have a good USB flash drive. That means twrp was not able to be loaded.
[FYT Android Head Units] texastwurkteam:
Weird, the drive seems to be functional as I have wiped it for the Joying again and then back to yours. I'll have to give it another shot later on. Just a few questions since I won't be off work for a while. Since this same event keeps occurring at the same installation interval is there anything that you or anybody can think of to prevent it? I even tried going back to the stock Joying in the previous picture and that wouldn't work. It only seems to show activity when I plug the GTX USB back in, but it goes through a few steps and hangs here every time. That was the same spot of the initial dirty flash that it got stuck on.

I'll definitely give it a few more goes but if it doesn't wind up working, what would be the best course of action since neither the Joying or your ROMs are showing progress? Thanks again for all your help on this :good:
[FYT Android Head Units] tOz666:
I dirty flashed V7 from V6 (that was dirty flashed from V5) and no problems so far! It did optimize dalvik for 20 minutes or so like [MENTION=520205]gtxaspec[/MENTION] said.

Fixed led lights, and is smooth as always. Thanks.
[FYT Android Head Units] texastwurkteam:
It finally wound up working after the third or fourth try. Kept all my apps and settings but I can only access stuff from the drop down menu and the entire thing is extremely slow. Some of the buttons won't function properly and I can't access my home/launcher screen. It's just completely black until I go to the menu. Keeps saying Setup Wizard crashed on boot
[FYT Android Head Units] gtxaspec:
Try a clean install... Sorry the dirty flash is not 100% perfect :/
[FYT Android Head Units] texastwurkteam:
Nah it's all good man. Frustrating but that's what I get for testing it out. What would be the best course of action to go about fixing this in my particular situation? I have the Jan Joying update on a USB but it doesn't do anything when I plug it in. The only thing that I can access is the drop down Android menu you get from dragging your finger down near the top. No possible way that I've found to access anything else without auxiliary equipment
[FYT Android Head Units] gtxaspec:
Can you drag down to enable wifi? You could run some adb commands to reinstall gtx.
[FYT Android Head Units] texastwurkteam:
Yeah I was able to. I somehow got it working. When installing V6 it gave me the option and I chose 5009_60gtx since it has gtx in the name. I noticed during the update screen that it was pulling from 5009_60 and since that was first, I figured that's why it was pulling from it. After I deleted 5009_60 from the USB drive it was almost instantaneous and it updated and rebooted with full functionality, save when I hit the reset button a gabjillion times. Thanks for all your help on this, again.
[FYT Android Head Units] gtxaspec:
Hello [MENTION=8939882]derekbunch[/MENTION], could you try updating to joying january release and try custom to install? Maybe the bootloader didn't get updated when you installed the December release. that could be why you arn't able to pass verification!
[FYT Android Head Units] derekbunch:
Is there somewhere other than carjoying.com that I can get the ROM? I haven’t been able to able to access the site for the last month. I think the site is down
[FYT Android Head Units] gtxaspec:
Sure, lemme find the links I will post them here.
[FYT Android Head Units] gtxaspec:
FYI...updated Q/A section with links to stock joying roms...upload is in progress. Link sends you to google drive folder. enjoy!
[FYT Android Head Units] CODEONETEAM:
[MENTION=520205]gtxaspec[/MENTION], hi, you need to pull ALL strings to the strings.xml to create a normal localization, including console output, since I do not even have access to the new GUI items:
[FYT Android Head Units] christian51:
GTX CustROM

Hello,

I have successfully flashed my Joying UMS03N with the ROM V7.

Is it possible to reinstall the Joying settings? I need the brightness setting of Display with the possibility of brightness adjustment via the headlights. I Switch the brightness control with a switch. My settings are dispay bright for daylight and LED on or dislpay dimmed and LED off at night.

Thanks for the good ROM!
[FYT Android Head Units] gazenbeek:
can i install this on my unit ?

Bway 9 Inch Headunit

Model Name: BW-90910

OS Android 6.0.1

CPU:Intel ATOM X86 Quad-core 1.2 GHZ Sofia 3GR

RAM 1GB DDR3

​ROM 16 GB

Resolution 1024*600.Capacitive Touch Screen

Built in Sygic map

Solution Sofia

Sound processor TDA7388

Build Number : Sofia3gr_car_64-userdebug 6.0.1 MMB29M Eng_build_20170815_121351 release keys
[FYT Android Head Units] luciusfox:
You turn the led *off* at night? That seems odd, since night is the only time when you can't see what the buttons actually are, and therefore is the only time it even makes any sense to turn them on.
[FYT Android Head Units] christian51:
LED off

Yes, I turn off the LED at night because the LEDs dazzle me. At night I dimm the screen and turn off the LED. For switching I use a separate switch.
[FYT Android Head Units] gtxaspec:
hello! reaching out to some of the users who get the MCU DOES NOT MATCH overlay. Which MCU do you have? Are you using a JOYING branded unit? Does everything work correctly with the ROM?

If everything works fine, investigating whether to patch via exposed to block that overlay from being displayed. I know you can change the fyt manufacturer MCU code in /system/app/fyt.prop (which was introduced in v6, to fix various issues) to match your MCU. it's curently at 43 (JY)
[FYT Android Head Units] SynMaki:
Alright, finally installed my cooling mod. Whoever is intrested how i did it: https://imgur.com/gallery/xHrkt

Anyway, i did this mostly for Viper. And its better than before but i still notice some sound stutterings from time to time.

what ive already tried:

-checked the temps(not going over 40 degrese)

-set the min CPU clock to the max.

-checked the temps again (not going over 50 degres)

Cant viper run "normally" on these devices?

by the way, im using spotify with downloaded music.
[FYT Android Head Units] btrax:
Hey, I have a strange behaviour (but I think it's not because of the ROM ).

On your ROM there is no Music Player so I installed Poweramp. Everything works but if Poweramp is in background (for example I have Waze in foreground) and with the steering wheel button or on the HU I press Next, it start spotify and play spotify music instead poweramp. I have to kill Spotify to run poweramp properly. any idea ?
[FYT Android Head Units] dyabolikarl:
No input but nice mod !! :)
[FYT Android Head Units] gtxaspec:
i have the same problem...sometimes. I think it's caused by sofia server, but I can't be sure yet. track backwards and track forward presses get sent to the wrong media application. Does anyone have any issues like this? I will do some debugging on this for the next release.
[FYT Android Head Units] btrax:
And If you pull back the Music App, do you think you'll have the same behaviour ?
[FYT Android Head Units] gtxaspec:
so, I'm thinking that sofia-server sends the media buttons to whatever application you launch FIRST. for instance, if i open play music first, then DI.FM or some other app, the buttons get sent to play music. what I do next is FORCE STOP play music, and now all buttons get sent to DI.FM ( whatever app you opened last ) try this method.
[FYT Android Head Units] btrax:
I find This method too but for example, even if spotify is not launched, I turn on my car, i launch poweramp, put it to background and change the music it will launch the spotify app in background and play the next song. I never tried on stock ROM (I had just spotify for music) so i can't tell if it's a bug from the roiginal firmware or it's your rom ^^
[FYT Android Head Units] gtxaspec:
happens on stock too. always was annoying for me.
[FYT Android Head Units] surfer63:
Did you assign in the settings spotify as default media player app?

or did spotify ask that and you said "allowed"

Sorry. Didn't see the last replies.
[FYT Android Head Units] btrax:
^^ Np :)

I think default app is PowerAmp because when i pushed the button Media on the HU (before installed Poweramp) nothing happened, and when I installed POweramp and press Media button, it launch PowerAmp.
[FYT Android Head Units] kkaaffee:
They added Android Auto.

https://www.joyingauto.com/blog/post/joying-intel-sofia-android-car-stereo-software-update/
[FYT Android Head Units] surfer63:
Why do you think that? I can't detect it from the page.
[FYT Android Head Units] kkaaffee:
my bad, didn't read properly.
[FYT Android Head Units] edit:
[MENTION=2550900]surfer63[/MENTION] , [MENTION=520205]gtxaspec[/MENTION]

I detected an very annoying bug that [MENTION=3076686]gustden[/MENTION] managed to overcome on the December version of it's Sofia NoKill Mod. doing this "- Media keys - Modified code to only send media keys to the active media player. "

Thing is when I press play and have PowerAmp active if fine but when there is Deezer or another player in the background, while pausing 1 player the others starts... then if I press pause again the second player pauses and the first one start.... and it never ends... cannot pause unless I end task them.

I think the issues comes from the [MENTION=2550900]surfer63[/MENTION] implementation of the NoKill mod.

Please fix it when you have the time, thank you !
[FYT Android Head Units] surfer63:
That could very well be. The Kill function in the sofiaServer is really one function, but it is called from 3 other functions. Gustden made modifications in those 3 functions and disabled the call to this kill function from those 3 functions.

[MENTION=7838245]realzoulou[/MENTION] modified the November Sofiaserver by only disabling this one function. I did the same for the December version.

So the 3 "calling" functions are still the original ones in our mods and in my xposed modules.

I will have another look at Gustdens modifications.

Edit: wait a minute. You mention " [MENTION=3076686]gustden[/MENTION] managed to overcome on the December version".

You mean the September version? Or is there a December version by Gustden?
[FYT Android Head Units] gtxaspec:
Bingo. Sofia server at it again..
[FYT Android Head Units] gtxaspec:
I think he's referring to the media keys problem, sending the keys to the wrong media app
[FYT Android Head Units] edit:
Now I can't tell for sure if the mod that I am using right now it's made by [MENTION=3076686]gustden[/MENTION] or [MENTION=3917592]DBestman[/MENTION] but one thing I know for sure... it works on the December firmware perfectly

Most likely it's made by [MENTION=3917592]DBestman[/MENTION].

---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------

I think [MENTION=2550900]surfer63[/MENTION] sends a broadcast with the play/pause keys and all the mediaplayers that pick it up react to it... and that leads to a bit of chaos :)
[FYT Android Head Units] gtxaspec:
He hasn't touched the media keys... It's Sofia server itself. It's a bug on the stock ROM.
[FYT Android Head Units] surfer63:
That one was indeed made by [MENTION=3917592]DBestman[/MENTION] and he copied the Gustden mods.

That's correct. The media keys follow the exact same principle as gustdens mods did. So it either is a general bug always in the mods and therefore also in the xposed modules, or it is indeed in the stock joying ROM.
[FYT Android Head Units] gtxaspec:
Yeah, Sofia server. Gustden did specifically fix the media keys bug it in one of the last releases of his mod. Might be worth looking at if you have the time.
[FYT Android Head Units] x3rb3ru$:
The deel sleep issues I had when using the NoKill and GTX Rom seem to be solved when using the XSofiaTweaker software. It seems just pausing the music when ACC_OFF was enough for the dirty app to go to sleep succesfully (I presume it was BlackPlayer Audio player causing the issues). Also for the first time in a year my music resumes when starting the car without pushing any buttons... (could've solved this earlier but was a bit lazy) So atm I couldn't be happier:)

Big thumbs up to every developer making the best out of these Joying devices!
[FYT Android Head Units] SynMaki:
So, got a few questions since i installed my cooling mod.

Viper sometimes seems to work(man, what a plus with it) but for that i need to set the govenor to performance.

Ive currently got no kill mod installed, bcs there are some toughts about it:

- If i set the govenor to perfomance mode, will it keep running at full clock speed even in standby? If so, someone know the power consumption?

-will this cause a cold boot? just tought it maybe results because the software think its a "bad" app

-any other way to keep the performance mode on start? good app suggestions?
[FYT Android Head Units] rilerale:
Hi,

mcu update is not working.

file can not be searched

how can the mcu update be done?
[FYT Android Head Units] gtxaspec:
What version of ROM? Which MCU are you trying to update?
[FYT Android Head Units] gtxaspec:
Cpu goes idle no matter what speed it is at, same power consumption.

No, cold boot is usually caused by an app with no kill mod enabled.

Yes, edit /system/bin/install-recovery.sh change interactive to performance

I run in performance 24/7...the unit is night and day running at max clocks all the time...smooth as butter.
[FYT Android Head Units] surfer63:
In the V7 inste install_recovery.sh you load mcud

/system/vendor/bin/mcud &

I assume it is lbdroid's mcud. Why do you load it?

What does it do and does it not conflict with the SofiaServer?

It has one advantage though. We were talking about the up/down/(fast)forward/(fast)backward keys on the Steering wheel which need to be captured.

The mcud writes unidentified key presses to the logcat.

dump_packet("UNIMPLEMENTED key", data, len);

So if the mcud doesn't know those keys either, it will write them to the logcat.
[FYT Android Head Units] gtxaspec:
It is lbdroids... My solution to preventing boot loops during dirty flash, or delayed boots... App optimizations that take forever and the system reboots due to Sofia server not running... Once the system has fully booted to the desktop, we stop mcud, and restart Sofia server.

Mcud sends the heart beat while the system is busy.

up/down/(fast)forward/(fast)backward are already captured on canbus devices and mapped appropriately. It's the non standard keys that need to be mapped, like on some VW and others that have like 15 keys on the wheel.
[FYT Android Head Units] surfer63:
Clever! :good:
[FYT Android Head Units] jorxru:
Very happy with the rom v7 congratulate him for the work I have the problem with the mobile synchronized tells me ok google I still can not make calls , the bluethooth joying application synchronizes the contacts and from it if I make calls but ok google does not work. I think it's a samsung 8 problem worse I'm not sure anybody with the same problem?
[FYT Android Head Units] surfer63:
Due to the way this started with referring to the NoKill (and the NoKill only), I made the wrong conclusion.

I mentioned that Gustden stopped the call to the NoKill function from the 3 parent functions, while realzoulou and myself only stopped/skipped the NoKill function itself.

I still don't understand why Gustden is doing that, as in those 3 functions that is the only thing he is doing.

But that is not the place where he changed the mediakey behavior.

The mediakey fix is somewhere else located. He replaced both mediaKey methods from

private static void mediaKey(int n) {
ToolkitApp.mediaKey(0, n);
ToolkitApp.mediaKey(1, n);
}

private static void mediaKey(int n, int n2) {
Intent intent = new Intent("android.intent.action.MEDIA_BUTTON");
intent.putExtra("android.intent.extra.KEY_EVENT", (Parcelable)new KeyEvent(n, n2));
App.getInstance().sendBroadcast(intent);
}

to

private static void mediaKey(int n) {
ToolkitApp.onKey(n);
}

private static void mediaKey(int n, int n2) {
ToolkitApp.onKey(n2);
}

Up till now I did something to replace a method or skip a method, now I have to make a modified call to another method. I have not done that yet (edit: make a call from the Xposed module back to the original app methods) and it might take some time.

(And just for information: I use(d) jadx to decompile to java but the problem is that jadx could not decompile the modified methods, so I switched to apk2java.)
[FYT Android Head Units] edit:
Guys can you please link me to that Bluetooth Mod that displays a miminal interface while you are on a Navigation app... I searched like crazy and I don't seem to find it anymore.

The default one displays those 2 rows of numbers that are completely useless and take a third of the screen covering me map,

Or if you can find a way to put the app in the background.... that would be great :)

Thank you !
[FYT Android Head Units] rilerale01:
Mcu Trouble with v7

Selektion mcu vor my Car

Everything okay, then Restart

Hangs in mcu Update.

Search Button without function.

Maybe search Button ist linker to syu Filemanager?

Syu Filemanager does Not Exit in v7 GTX

Grettings

Gesendet von meinem MI PAD mit Tapatalk
[FYT Android Head Units] Fredheg:
Hello I tried to install v7 with the same USB stick as v5. But I became error

Signature failed

I have unzip the file to the root

Any idea ?

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[FYT Android Head Units] yebokmj:
I'm on V7. Is there any way to use the Joying HD front camera for other software? I read something about the kernal keeping us from using other cameras, but I have the Joying one. I tried installing dashcam 2.0 and it's just showing connecting do I need to install Joying's DVR app first? I'd ideally like to be able to run the camera with Track Addict.
[FYT Android Head Units] SynMaki:
Alright, just gave it a try, seems like i did something wrong.

im guessing i need to reinstall the rom? I just changed it "live" with a restart after it

just to make sure i will make there chages:

GTX "Setting scaling governor to perfomance"

echo perfomance |

tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

log -t GTX "Setting perfomance governor option go_highspeed_load"

echo 80 |

tee /sys/devices/system/cpu/cpufreq/perfomance/go_hispeed_load

log -t GTX "Setting max performance level for Mali GPU"

echo 4 |

and reinstall the rom with the modified file?
[FYT Android Head Units] liquidini:
same problem!
[FYT Android Head Units] surfer63:
Flashing not correct

[MENTION=520205]gtxaspec[/MENTION]: I know you had the exact same message from [MENTION=2697655]farmerjohn[/MENTION] about a failed flash.

This afternoon I tried to dirty flash the V7 from the V4.

Using the custom.apk V4.6 I wrote the recovery and verified it.

Set the option to dirty flash

Then rebooted using a usb-stick with the V7.

It got the android with its open rotating belly and the blue progress bar at the bottom.

And suddenly the unit went dead. At least that's what seemed to happen. I waited 25-30 minutes but nothing happened. So I switched off the contact. I removed the usb stick and switched on the contact.

Nothing: no glowing hardware buttons, nothing. I waited another 5 minutes and resetted my unit and that worked (or seemed to work).

I got the 3x pink flashing and the 4th time the buttons stayed pink constantly.

I resetted the unit again and the same happened: 3x pink flashing and the 4th time the buttons stayed again pink.

I then removed both my sd-cards, attached the usb-stick with the V7 again and rebooted.

It flashed again 3x pink and then I got the Android logo with the "3x not booted successfully".

I immediately removed the usb-stick and let it reboot again.

And (hurrah!) it booted again into android. It was still the V4 and the keytone was back and my radiostations gone, but at that stage I couldn't care less.

Any explanation?

Edit : I numbered the steps. I'm not exactly sure about 10 and 11. It was quite a confusing situation.
[FYT Android Head Units] gtxaspec:
Weird, so you are still on custom recovery after you booted back to v4?

Scenarios like that have happened to me, with some bouts of stuck or repeating flashing purple, but a click of the reset button always fixed it for me.

Looks like nvram corruption, as the bootloader reads the bcb and then puts it into nvram upon reboot (not a good design lol)

I think you are safe to try to reinstall.
[FYT Android Head Units] surfer63:
I did not check to be honest. All in all it took quite some time and it is still very cold, so when it was up again I was happy and went inside.

I will check tomorrow whether the custom recovery is still in place.
[FYT Android Head Units] gtxaspec:
We need to get you a Dev unit!!!
[FYT Android Head Units] surfer63:
No thanks :) I already think I'm spending way too much time on it.
[FYT Android Head Units] gtxaspec:
Lol haha yeah same here...the next project is lbdroid's 960 based unit...hoping to release a "stable" version of the gtx ROM soon...