yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] kiltym:
I think this is a common requirement, start apps when the unit starts out of sleep. What you ask can be done with the "keys" mod on the ACC_ON event in launcher.sh. https://xdaforums.com/android-auto/android-head-units/joying-2gb-steering-wheel-key-t3543390

Unfortunately that mod also contains the nokill mod. I had asked, and hoped for someone to create a mod for the standard Joying Sophia (Dec and Jan versions) with just the key mod and not the nokill. This would allow any of us to easily start any app at startup, and never worry about the nokill not killing things that Joying (android), needs to have killed. Trying to find the app(s) that causes the unit to go into a deep sleep is more effort then most can devote to this. I tried, and gave up.

The original author of the mod has disappeared, and current devs are focused on the GTX ROM and Xposed. Which is understandable, but I am sure there are a number of people like us who don't have the time/inclination to get into the GTX ROM, but would love to be able to simply start some apps automatically when the unit comes out of sleep. I believe this can be done with the Xposed mod (you can disable the nokill part of the mod apparently), but based on all the information, installing Xposed on Joying ROM is a risky proposition.
[FYT Android Head Units] 5p4rtan:
Ah, wow, thanks for this information. I didnt know that the launcher.sh also could start apps. Amazing.

Im still not that deep into the launcher.sh but Im working on that :D

Yeah, thats exactly my position. Im really glad my HU is working so far and I fear to do changes (especially experimantal or beta state ones).

I would love to change to a GTX ROM but therefore it needs to be stable.

And I agree with you the guys here working on the mods do an amazing work! Thanks again mates! :cool:
[FYT Android Head Units] surfer63:
DBestman did the last mod.The point is that he really copied all changes from Gustden into the mod. That means the keymods, the mediakey changes and the NoKill.

The latter as such SHOULD be a one-liner, but there Gustden made an entirely complicated implementation where he made changes to the 3 calling functions, instead of simply disabling the kill function itself (the oneliner). If he would have used the one-liner, I could easily enable that one-liner again.

But I can't undo his complicated nokill change and keep the rest working, and maybe DBestman can't either. That is the issue: It will take hours to undo Gustden NoKill, while maintaining the other functionality.

It is not that I don't want to do it: A one-liner with unpacking, repacking etc. would take 15-20 minutes. Your mod would have been ready by now.

Undoing the overcomplicated Gustden NoKill would take hours with testing. If it takes hours I prefer to spend that time otherwise.

And yes, the Xposed install is still risky. I use exactly the same script to do the install as the recovery version. Literally the only change is that I install from /sdcard, where the original installs from a USB disk via the recovery partition, but that has nothing to do with what the script does to install, and set the correct (se-linux) authorisations.
[FYT Android Head Units] 5p4rtan:
Did you click on "verify recovery" before "install custom"?

Do you have atached an USB stick with the custom ROM?

Maybe stupid questons, but we need to exclude every little mistake :)

You can also follow GTX video. When he is clicking on "reboot to install stock" you need to click on "Install GTX ROM"

https://www.youtube.com/watch?v=NrHVJJ72qQA
[FYT Android Head Units] neozebulon:
Thank's for your help but the solution of Lowen Sodium has worked
[FYT Android Head Units] petro_ionut:
Serios problem with v8, big lag, on volume key change, nothing works on keys, fresh install.

Car model doesn't update!
[FYT Android Head Units] silver1977:
Hello everybody. Does anyone have problems with calling via Bluetooth. My Samsung s7 is connected, but when I call, the caller does not hear me, I hear it properly. I use gtx v7. I had no problems with the Joying Rom, as well with v6 Rom.

Gesendet von meinem SM-G935F mit Tapatalk
[FYT Android Head Units] pilotbob3:
I had the same problem, clean install on top of January Joying stock. Had to revert back to Joying.
[FYT Android Head Units] farmerjohn:
Is it safe to dirty flash back to V7 coming from V8?
[FYT Android Head Units] Astur_Torque:
Is possible to do automatic BT tethering with GTX ROM?
[FYT Android Head Units] surfer63:
Yes, it is. You can still use lbdroids BTTether apk for that on both your phone and unit, or use another from the play store.
[FYT Android Head Units] Astur_Torque:
nice!!

Once this ROM become stable, I'm going to install it!
[FYT Android Head Units] edit:
[MENTION=520205]gtxaspec[/MENTION] have you managed to have a look at the Viper issues ?

(if you said something about that and I missed it I apologize in advance)

Thank you !
[FYT Android Head Units] yuvalmesika:
Hi,

I'm having a weird problem,

I running on GTX v6 for 3 weeks and everything was great.

On Friday I installed the SofiaTweeker for preventing the Bluetooth app to be always on top, I also updated the GpsSpeedFix to 1.11 after reboot my GPS show no reception at all, checked from the car settings and it shows nothing, not even one 1 bar in the screen.

I tried to to uninstall GpsSpeedFix, disable exposed, change the GPS mix mode, played with location settings, but nothing helped.

I thought maybe the GPS anttena disconnected from the SOM, but before disassemble the head unit, I decided to reinstall the ROM.

After the new installation the GPS reception came back to life,

Tried to reinstall the GpsSpeedFix and again no reception at all after installation.

Does anyone facing the same issue? [MENTION=520205]gtxaspec[/MENTION] [MENTION=2550900]surfer63[/MENTION] do you think it related to the GpsSpeedFix module?

What can cause the GPS to stop getting any signal?
[FYT Android Head Units] surfer63:
I assume it indeed has to do with the GPSSpeedFix, but I have no clue what.

You mention that you uninstalled Xposed. How did you do that?Or did you disable it?

Same for the GPSSpeedFix. Try enabling and disabling it from the Xposed Installer and do a FULL reboot, not a soft/gui/system reboot (as mentioned as second option by the Xposed Installer). Most Xposed modules work on apks and therefore only a gui reboot is necessary. The GPSSpeedFix works works on the GPS HAL in the kernel and needs a full reboot.

---------- Post added at 04:49 PM ---------- Previous post was at 04:36 PM ----------

@gtxaspec:

I do not understand certain parts from your install-recovery.sh like

clock_max() {

if [ $maxfreq == 1200000 ];
then
log -t GTX_FB "Set CPU Scaling Max Frequency to 1200000";
echo 416000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo 1200000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
else
log -t GTX_FB "Set CPU Scaling Max Frequency to 1040000";
echo 416000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo 1040000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;

if [ `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq` == "1040000" ] || [ `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq` == "1200000" ]; then
boot_detect
else
sleep 0.2
clock_max
fi
fi
}

If you do it like that and the scaling frequency is "1200000 " (the 'then' part for the 6021), it will never(!) get into the 'else' part which is the only location where the

if [ `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq` == "1040000" ] || [ `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq` == "1200000" ]

is executed.

So the code works on a 5009 running at 1.04GHz, but it doesn't work on a 6021 runing at 1.2GHz. So on the 6021 the 'boot_detect' will never be executed and therefore, the mcud will never be stopped (and the clock_max will not be run either which is less essential, but not good either).

Should the code not be:

clock_max() {

if [ $maxfreq == 1200000 ];
then
log -t GTX_FB "Set CPU Scaling Max Frequency to 1200000";
echo 416000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo 1200000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
else
log -t GTX_FB "Set CPU Scaling Max Frequency to 1040000";
echo 416000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo 1040000 | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
fi

if [ `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq` == "1040000" ] || [ `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq` == "1200000" ];
then
boot_detect
else
sleep 0.2
clock_max
fi
}

I guess this is also the reason why users (on a 6021?) complain about the sluggishness of keys and where it stops working at a certain time as both the mcud and SofiaServer "fight" about the hardware and Steering Wheel keys.
[FYT Android Head Units] gtxaspec:
Yes, I re worked and fixed in v9. Thanks for the heads up!!!
[FYT Android Head Units] yuvalmesika:
I tried to uninstall GPSSpeedFix which did not worked, so I deleted the GPSSpeedFix App manually and did a full reboot.

I didn't uninstall Xposed, I just tried to disable it.

I did full reboot each time, even pulled out the head unit fuses (also tried to replace them) in order to get a real shutdown, nothing helped, only reinstall of the ROM did the trick.

[MENTION=520205]gtxaspec[/MENTION] I noticed on your gtxlab a GPSSpeedFix V1.2 is it a new build for GPSSpeedFix?

http://mirrors.gtxlabs.com/joying/1_Firmware/joying_gtx/
[FYT Android Head Units] yuvalmesika:
deleted
[FYT Android Head Units] surfer63:
Looking at the date it is an older version.
[FYT Android Head Units] gtxaspec:
So with lots of testing, the GTX JY ROM will be moving to a v10 STABLE release very soon. v9 should be released within the next few days, with some V9 point releases in between for bug fixes. Thanks to everyone who has used, tested, broken, and is enjoying their head units! Please send lots of feedback to help move to V10 stable for more to enjoy.
[FYT Android Head Units] gtxaspec:
i need a boot partition dump from one of the releases where viper worked (6.0 based)

dd if=/dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID071 of=/sdcard/p9.img

i need this to test further, but I don't have the old release to test. if you can get this, OR the full installation zip, i can do more testing!
[FYT Android Head Units] gtxaspec:
for the folks ( like me ) who are tired of sounds, notifications, TTS prompts, etc being cut off at the begining:

the sound HAL cuts the audio when nothing is playing ( uncertain why )

my solution is to use a command line audio player (andplay) to play an empty sound file when ACC is kicked ON, and kill the program when the ACC is OFF. (if you don't kill it, then unit will NEVER sleep, it will shutdown)

v9 of the rom will include this file, audio_stream_bypass.sh <start|stop>

so, as an example, using XSofiaTweaker, you can define ACC_ON by system call, and assign it the string: audio_stream_bypass.sh start, and the same for ACC_OFF, with the string being audio_stream_bypass.sh stop

and viola, all notifications, as well as TTS prompts are always heard, because the audio HAL is keeping the audio stream open instead of closing it and opening it each time a sound is played. (note that this does cost some cpu cycles, the real solution is most likely to create an app that opens an audio stream, only, not playing or decoding any files, costing the cpu no cycles to decode the audio)
[FYT Android Head Units] ptolomeo:
Can you please include the navi_apps.txt mod so that Sygic can be heard even if it's in background? Or are there any instructions on howto decompile-recompile the sofiaserver? I could try to do it on my own...

It's the only thing I'm missing from this wonderful ROM.
[FYT Android Head Units] surfer63:
As a workaround you can install the "default" SofiaServer from my JET apk. It is there for those users still wanting to use the direct SofiaServer mods and be able to go back to the default Sofiaserver.

It IS the default sofiaServer but enhanced with the extended navi_app.txt and player_app.txt.

and for [MENTION=520205]gtxaspec[/MENTION]: If you want to include it in the ROM, the January version is here.

I'm still looking for a way to make it "user expandable/modifiable" in the XSofiaTweaker as a setting, but was unsuccessful so far (but didn't look/try for the past week btw).
[FYT Android Head Units] gabrielnic:
Have you checked the 3368 settings menu? There is a setting in there for front/back or maybe internal/external mic. Leave that on front or internal mic even if you plugged in/use the external. I thought my external microphone was broken until I figured out that the mics are in parallel (they are both always on) and that that setting just breaks/turns off both of them. It doesn't actually select between them.
[FYT Android Head Units] texastwurkteam:
I could be wrong but I was under the impression that there was no working version of Viper on 6.0. From what I've read it worked in 5.0 and then ceased working after the first 6.0 patch around May? These are all off the top of my head so I could be off on stuff
[FYT Android Head Units] gtxaspec:
I personally never used viper before, so I'm going on what some other folks have said, and they say that early 6.0 releases work.
[FYT Android Head Units] ptolomeo:
OMG!! I had an external MIC installed and people started complaining that they heard me with echo, so I was looking how to deactivate the internal MIC. So, maybe the only way to disable the internal mic is actually opening the head unit and desoldering it? I can't believe it!!
[FYT Android Head Units] ste2002:
ptolomeo, as first step try to plug ext.mic connector all the way in - it has rather hard last click. If not connected properly, it can disable both mics, as gurus say. And as your experience shows, it also can make both work with echo.

If ext.mic plugged properly, internal mic is automatically switched off.
[FYT Android Head Units] gabrielnic:
Unfortunately plugging in the external does not deactivate the internal. They both get used, at least that's what happens on mine, an 8 inch screen doubble din with touch buttons. You can try for yourself by gently tapping on each mic and you'll see that they will both pick up the tapping.

---------- Post added at 10:19 AM ---------- Previous post was at 10:14 AM ----------

That is what i ended up trying. I oppened it up and cut the negative trace going to the internal mic. Then i soldered in a switch so i can turn it back on if needed. It did help slightly but at highway speeds it's still horrible. I am currently looking into what i can do to get some sort of external noise filtering happening as i dont think it can be done by an app of sort, can it?
[FYT Android Head Units] wanb1i:
Will it include Live Wallpapers?

---------- Post added at 01:16 PM ---------- Previous post was at 01:09 PM ----------

That was alot of work. If you go into Car Settings enter 3368 and scroll to the very bottom, there's a switch there to activate /deactivate the appropriate mic.

---------- Post added at 01:19 PM ---------- Previous post was at 01:16 PM ----------

Interesting, it turned on my external mic and turned off the internal one.
[FYT Android Head Units] gtxaspec:
What model unit do you have? Is it 5009 or 6021 SoM?

Live wall papers apk are included in the oem directory, use the file manager to install the app.
[FYT Android Head Units] gabrielnic:
It looks like that front/back setting may work on some head units and not on others. On mine it turns off both mics as they are hooked up in parallel.
[FYT Android Head Units] buurman42:
I break my head ... I have the V8_test version installed and I still get the 'i can't make calls yet' :(

Where do I change the DPI setting? on the google app, or with the "Joying extra tools" app, Alter DPI setting?

Can someone explain step by step?
[FYT Android Head Units] wanb1i:
I'm not sure which SoM, it's the one with the internal amp, if that answers your question? I think it's the 6021.

Cool, I'll check out the OEM directory! Thanks!
[FYT Android Head Units] ptolomeo:
Yes, yesterday I tried this and both mics are in parallel. If I turn off one, both stop functioning...

Crap!
[FYT Android Head Units] silver1977:
I have checked the settings in the 3368 menu, it is set to back. I use an external micro, so that should be correct?

I have never changed anything in the settings for the micro.

That's why I'm surprised why it suddenly stops working.

I also plugged the plug in and out again. That does not help.

I also tried recording with a recording app. This only picks up noise.
[FYT Android Head Units] amon101x:
dont change it to back it should be set to front always or you dont have sound
[FYT Android Head Units] silver1977:
have changed it to the front. when i record now with the app, i hear my voice. but calling still does not work. conversational partner does not hear me.
[FYT Android Head Units] Huge Torque:
Tried the V8 but couldnt get the hardware keys to work on the JY-UM135N2 (7" double din 2gb/32gb with the volume knob). I think i just want to go back to stock. Inserting the usb thumbdrive with the latest joying firmware doesnt do the trick. Can anyone help me get on the right path, either way. At wits end. TIA
[FYT Android Head Units] gtxaspec:
use custom to make sure stock recovery is flashed and then use a flash drive with stock joying. Known issue with v8...v9 fixes all issues with your unit out soon.
[FYT Android Head Units] farmerjohn:
Post deleted, too late.
[FYT Android Head Units] gtxaspec:
Need a volunteer with 6021 unit to test a build of v9 for me... Anyone?
[FYT Android Head Units] PuntoGT16VT:
Hi,

i have a 6021 Unit. I can test v9 tonight if you want.
[FYT Android Head Units] gtxaspec:
awesome, uploading now.
[FYT Android Head Units] Huge Torque:
ok, so I use the custom.apk and hit restore stock and get this (see pic)

does that mean i made sure stock recovery is flashed?

nothing further seems to happen, so i remove the flash drive (which has worked in the past) and reinsert it into the usb port on the right.. nothing happens so i reboot and every time it loads up the gtx rom as if i did nothing
[FYT Android Head Units] gtxaspec:
once you have flashed stock recovery, insert USB flash drive, and press the RESET button on the unit, do this about 3 times, and the unit will boot to install stock joying.
[FYT Android Head Units] Huge Torque:
thank you it worked. love
[FYT Android Head Units] btrax:
Hey :)

I have for the moment the v7 version of GTX ROM and I experiencing some problem with spotify, youtube and some app for TV Stream. The apps are lagging and so the sound is very poor (like the speed of the song are at x0.5 on spotify ^^) and video have a lot of freezes, even if i kill all the apps before.

and second thing I don't know how to use the GVC Call handler. On the app I have two option to check/uncheck and when I try to call someone via google app, it says it's not possible for the moment.

Glad to see the v9 version up! i will try that this weekend.
[FYT Android Head Units] farmerjohn:
Do you have Viper enabled. If so see/hear what happens if you disable it. Could also be a problem of cpu overheating/throttling. Do you have any cooling/heatsink? Watch cpu temperatures and frequency with JET app.

For Google Voice you must change dpi settings to 161 or greater. You can do this with the JET app (Joying Extra Tools). Also you must set GVC as your main calling app.
[FYT Android Head Units] DBestman:
When I change the DPI settings with JET or with the App Settings xposed module, I don't see any change. What am I missing?
[FYT Android Head Units] farmerjohn:
Did you reboot?
[FYT Android Head Units] DBestman:
Yup
[FYT Android Head Units] wanb1i:
How do you know which SoM you have? :confused:

I'm willing to test v9 if I have the right SoM. I have JY-UMS01N2D running V6. :)
[FYT Android Head Units] wanb1i:
I've checked all settings in the system and the Joying Auto website & the box the unit shipped in and cannot find what SoM is in it. I have a JY-UMS01N2D
[FYT Android Head Units] wanb1i:
The SoM I have looked like this picture before I installed the heatsinks.
[FYT Android Head Units] wanb1i:
In the Custom app, I wanted to do a nandroid backup, but the TWRP doesn't see my external sdcard & won't mount it either. I really hate to use internal storage for nandroids as the eat up too much space. Is there a plan to get the TWRP to see external SD in the future?
[FYT Android Head Units] SkyBehind:
I don't see v9 uploaded, or am I an idiot?
[FYT Android Head Units] amon101x:
he uploaded it for the guy to test it on 6021 SoM no release for public yet
[FYT Android Head Units] wanb1i:
I found the oem folder and installed the Live Wallpapers app, rebooted and I still get the same error "app isn't installed". Any help would be appreciated...
[FYT Android Head Units] gtxaspec:
Try putting them in system/priv-app
[FYT Android Head Units] surfer63:
It clearly states on the SOM FYT6021.

So now you know for sure :)
[FYT Android Head Units] wanb1i:
Thanks, but it still doesn't work. Same error message "app isn't installed" :eek:

---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------

Thanks, I completely missed that! :D
[FYT Android Head Units] gtxaspec:
Set permissions to 0644
[FYT Android Head Units] gtxaspec:
For the brave

https://drive.google.com/file/d/1T8-lXex6Ve-8OdOMZttu3MerC-aTkr3W/view?usp=drive_web

V9 alpha 1

Dirty flash from v8 ok. See first post for change log
[FYT Android Head Units] Stail:
Thanks!

Clean flash and looks promising :) no overlay issue anymore.
[FYT Android Head Units] wanb1i:
How about dirty flash from v6?

How far away are we from a stable version?
[FYT Android Head Units] gtxaspec:
V9 will be the base for final, I would recommend clean flash. Anything after v8 should be ok to dirty flash...
[FYT Android Head Units] farmerjohn:
First impression of me and another user from german forum china-rns (by now only tested at the workbench, not in the car): Very good !

Clean install from January Joying ROM went fast and flawless. No overlay problem, JET updated without problems, EQ-App seems to react normal, Amp Switch in car settings has effect.

The only thing I notice is that the setting for start volume seems to be saved, but unit starts with "18" (EDIT: After second reboot, start volume was set correctly). I noticed that my unit was running at 900mhz max speed, but corrected that with Kernel Adiutor.

Thanks gtx! Great work.
[FYT Android Head Units] gtxaspec:
Custom 4.9 will have a performance mode enabler which locks the clocks to max, disables itux(Intel throttling software) and changes the governor to performance. Will update custom to make it user friendly. Only for those with active cooling.
[FYT Android Head Units] PuntoGT16VT:
Same here works very smooth better then v7. It feels faster!

I make dirty flash from v7.

Good work! :good:
[FYT Android Head Units] totaltmega:
This is not for the FYT6021 SOM right?

Can you upload it for me to test?

Thanks
[FYT Android Head Units] gtxaspec:
Works on 5009 or 6021.
[FYT Android Head Units] totaltmega:
Perfect!

Will try as soon as I find a firmware for my unit (JY-BM124N2) thats later than 2017_12_15, as per the first post. Now I have 6.0.1 MMB29M 20170831

Does anyone know of a firmware later that this for the 6021 units? Joying removed the blog post 59 with all the firmwares. Maybe there is a mirror somewhere?

Thanks

Totaltmega
[FYT Android Head Units] amon101x:
thx for your work.

is audio_stream_bypass.sh integrated in this alpha?
[FYT Android Head Units] kamiljur:
Hello, I have installed V4_8 and there are two problems:

- Climate control pop ups from bottom only on startup for a few seconds and then appears maybe for 1 of 30 times when I'm trying to adjust it.

- When music plays something is immediately muting it for no reason. It happens once per ~30 minutes and sometimes system starts muted. I must click Vol+/Vol- to resume music. I think that music source and app does not matter, I have tried built in music app, Music over BT and AIMP.

I have tried at least 2-3 launchers and it didn't change anything.

Please help me.
[FYT Android Head Units] gtxaspec:
Try v9 alpha 1