yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] christian51:
Feedback how is the experience on the ROM V7

Thank you for the good ROM V7.

I have it installed on a Joying UMS03N. Before, I installed the stock ROM from Jan 18, 2018 and executed the rooting via WIFI-ADB. The installation of the custom ROM V7 went smoothly and much faster than the installation of the stock ROM. The head unit (a 1-DIN unit with 7 inch screen) I have equipped with an additional 50 mm cooling fan in the lid, which blows outside air through additional holes in the lid directly onto the heat sink. So I was able to reduce the CPU temperature from 70-80 ° C to 45-55 ° C at 100% CPU load. All software installations ran smoothly. The file browser Amaze I use no more, because of errors in network access to CIF / SMB shares. For this I use the TotalCMD app. As a navigation software I use iGO version 9.6.29.625822 on a micro SD. Thanks to treel https://xdaforums.com/showpost.php?p=71280945&postcount=88 I succeeded in the Bluetooth coupling with OBDLinkMX. The coupling succeeds only over the Joying BT surface with PIN 3368.

About the Android setting for BT does not work, it always appears for a few seconds, the request to confirm a random 6-digit random PIN with subsequent error message the PIN is wrong, no matter if prompt is confirmed or not entered.

In the GTX-ROM V7, only the original Android setting is possible, not the joying settings. The Android settings on the GTX-ROM contain unnecessary settings for a CAR HEADUNIT, but important custom settings, such as daytime and nighttime display settings, are missing.

I have re-established the Joying-Setting with the help of the JoyingExtraTools version 39. Unfortunately, in the newer version JET 43 this has not been possible anymore, the menu item for it is grayed out.

Sleep mode (Dormance) works well so far.

Thanks to the successful coupling of the OBDLinkMX adapter, the monitoring of vehicle OBD data works in parallel with the navigation with iGO.

Whether the navigation in the background mode works seamlessly, I still have to test.

About the radio reception, I can not say anything, because I use a separate tuner.

An improvement suggestion would be for me to be able to control the LED for the menu buttons separately, regardless of the display brightness (not dependent on car light or time). I would keep the LED on all the time and only control the display brightness of the car light or time of day.
[FYT Android Head Units] markmorto:
Issues with installing/verifying custom recovery

I finally took the dive today to install GTX, but couldn't get past the first step to install the custom recovery.

I'm using version 4.6 of the custom.apk, on the early January stock, rooted Joying firmware, to install GTX version 7.

When I select "INSTALL CUSTOM", the operation never completes. The screen displays the custom number version, with the next line that reads "Verifying Recovery ....", and just hangs there. I waited 25 minutes before closing the app, and then tried again, only to have the same thing happen.

I didn't want to try an install until I know what state my recovery is in. What do I do next?
[FYT Android Head Units] gtxaspec:
Looks like multiple users have this issue, I will look into it today.

We're you able to verify recovery successfully...or according to what you are saying, it just says verifying recovery forever?
[FYT Android Head Units] neozebulon:
I have the same problem jy-um135n2 with january update "CI V4.6" ,after i try with "custom install v 4.4 ", it work but after install i block at android logo.
[FYT Android Head Units] farmerjohn:
A user from the german forum reported that he is stuck at "Recovery Files Checksum Verification" using Custom4.6.
[FYT Android Head Units] Lowen SoDium:
I had this same issue.

The fix is to:

1: flash back to stock.

2: Root using the newest version of the root script here: https://github.com/hvdwolf/Joying-RootAssistant/releases/tag/20180107

3: Use the Custom.apk to install the rom.
[FYT Android Head Units] markmorto:
The "VERIFY RECOVERY" option hangs too - same as during the install.
[FYT Android Head Units] markmorto:
I was on stock, rooted with the same version. I just did the update/install the second week of January.
[FYT Android Head Units] ziofester70:
Thanks a lot for this rom!

I’ve trouble with tomtom app, if gpsfix is enabled tomtom go crazy, if i disable gpsfix tomtom works well.
[FYT Android Head Units] PuntoGT16VT:
Do you have the newest gpsfix installed?

I’m using TomTom GO every day with gpsfix and it works perfect.
[FYT Android Head Units] warata:
Thank you gtxaspec.

I made a video that compares the startup time with GTX custom ROM and JOYING stock ROM.

https://youtu.be/kQ0uziwsweM
[FYT Android Head Units] gtxaspec:
Yes slight lag on normal boot due to Xposed...that popup that says android is starting is Xposed initializing.

You should video the install and compare times =)
[FYT Android Head Units] warata:
What else should I install? Xposed has already been activated.
[FYT Android Head Units] gtxaspec:
No, I mean do a fresh clean install of both roms =)
[FYT Android Head Units] warata:
Ok, I got it.;)But both of them are just after clean installation.

And I confirmed that no pop-up will occur if restarting with the state that +B (+12V) is connected to the unit.

In order to do a test that is close to actual, I have to count from the moment I tap the restart button on the screen instead of the power supply...
[FYT Android Head Units] gtxaspec:
here is a test version of custom, v4_7. It should resolve the issues people were having using it. If someone could please test and report back!

https://drive.google.com/open?id=1QQelmNhPGxm5rCTM7FlwzgUl1WqA56i1
[FYT Android Head Units] ste2002:
Making such comparison, one should be absolutely sure that CPU temperature in both cases is the same and CPU is not throttled down, or it is equally for both cases..
[FYT Android Head Units] surfer63:
deleted. out of date.
[FYT Android Head Units] ziofester70:
Thanks for reply.

I've installed gpsfix 1.1 and tomtom do not work, maybe i do something wrong.
[FYT Android Head Units] surfer63:
You do not write what you already tried.

So, check in your Xposed Installer whether you indeed have 1.1.

If installed, deactivate it, reboot and see if TomTom does work.

If so, reactivate, reboot, and test again.
[FYT Android Head Units] PuntoGT16VT:
I tried TomTom GO again today and it works with gpsfix. Over 1,5 hours and no problem.

I have v7 and make a dirty flash from v6.

But I noticed today that the music volume is not reduced when instructions come from the navi. :confused:

I set TomTom as default navigation. I treid with disable the internal amp. But no change.

Everything was fine with v6 i think. I'm not sure. :confused::confused:

Can you even try if it works for you with the volume reduction?

EDIT:

I found out that it only happens when bluetooth music is playing. YouTube, Radio, Apple Music App

is working. Volume is reduced when instructions come.
[FYT Android Head Units] gtxaspec:
Yes, we need to disable Sofia server from intercepting audio stream 3. I have an Xposed module that does this, and will suggest to [MENTION=2550900]surfer63[/MENTION] to implement this in his Xposed tool once I have tested with the radio.
[FYT Android Head Units] PuntoGT16VT:
ok, that sounds great :good:.

If I can help in any way, please let me know. :D

I found out a few keycodes through logcat.

Volume Up
KEYCODE_SQL_BUTTON_SOUND_UP==down - keyCode = 227 action = 0
KEYCODE_SQL_BUTTON_SOUND_UP==up - keyCode = 227 action = 1

Volume Down
KEYCODE_SQL_BUTTON_SOUND_DOWN==up - keyCode = 228 action = 1
KEYCODE_SQL_BUTTON_SOUND_DOWN==down - keyCode = 228 action = 0

Mute
KEYCODE_SQL_BUTTON_KEY_FOUR==down - keyCode = 232 action = 0
KEYCODE_SQL_BUTTON_KEY_FOUR==up - keyCode = 232 action = 1

Play/Pause
KEYCODE_SQL_BUTTON_KEY_EIGHT

Next Track
KEYCODE_SQL_BUTTON_FAST_REVERSE==up - keyCode = 224 action = 1
KEYCODE_SQL_BUTTON_FAST_REVERSE==down - keyCode = 224 action = 0

Prev Track
KEYCODE_SQL_BUTTON_FAST_FORWORD==up - keyCode = 223 action = 1
KEYCODE_SQL_BUTTON_FAST_FORWORD==down - keyCode = 223 action = 0

I can, for example volume up with

input keyevent KEYCODE_SQL_BUTTON_SOUND_UP

via adb shell.

Maybe thats Interesting for people like me without HW-Buttons.

Its possible over Tasker to execute the code and bind up to keyboard keys.

Is there any way to bind up the keyboard keys to the code without Tasker?

The problem with Tasker is that he needs su to execute the code. And that takes 1-2 seconds.

For Prev or Next Track is this ok but not for Volume Up or Down. :(

Thanks for everyone to get this ROM better and better.
[FYT Android Head Units] gtxaspec:
How did you find these? Can you paste logcat?
[FYT Android Head Units] markmorto:
Tried the new version. Custom recovery install worked very quickly. GTX room install not so much. It now just boots into the Team Win Custom Recovery. Room installation never happened and the recovery doesn't recognize the USB drive with the zip file. What next?
[FYT Android Head Units] gtxaspec:
Do you have another USB drive to try? You can also try a Micro SD card
[FYT Android Head Units] markmorto:
I do, but something seems broken and I want to make sure I get this right. The drive I'm using has installed every image on the device so far successfully. I was under the impression that it would do this all automatically, but when it first booted (after two loud pops from the audio), it went straight into the recovery and hung there. i had to swipe to the right for the recovery to load.

I tried to just restart the device through the reboot menu, but it just went back into recovery again. That's when I searched for the zip files but couldn't find them. The recovery does see the internal drive and SD card, so I will try to copy them there.

If I do copy the zip files, including 5009_60.zip, 500_60_gtx.zip, data.zip and open_gapps.zip to another drive, do I just flash them all using the recovery tool and reboot, or is there something else I need to do with the openrecoveryscript?

Update:

After I restarted about an hour later, it booted with purple lights for three tries and eventually loaded the original (stock rooted) image. The custom.apk says that the custom recovery is still loaded.

So I'm back up and running, but not on GTX, and wondering what went wrong overall?
[FYT Android Head Units] gtxaspec:
hi mark,

i looked at your feedback and changed the way the installer works, I am releasing a new version of custom and the v8 rom tonight. should fix some issues during installation. testing now!
[FYT Android Head Units] PuntoGT16VT:
I’m binding my touchpanel keys with joying carsettings to volume up or down and then log it with logcat.

Every time when i click the keys i get this message.

I’m on work. I can paste the logcat when I'm at home.
[FYT Android Head Units] gtxaspec:
No need, makes sense. Thanks fir the find!
[FYT Android Head Units] PuntoGT16VT:
I am happy if I can help. :)
[FYT Android Head Units] gtxaspec:
cool, you can control volume from the command line and it controls the SoFIA Server! thanks again!

input keyevent KEYCODE_SQL_BUTTON_SOUND_UP

input keyevent KEYCODE_SQL_BUTTON_SOUND_DOWN

could you post logcat? would be awesome to have a complete list of all the KEYCODE_SQL buttons.
[FYT Android Head Units] ptolomeo:
Quick question here: everytime I turn off the car, it kills Sygic, so when I get back to the car, I have to open Sygic and set the 'navigation mode'.

I think with Gusden nokill patch, Sygic wouldn't die when turning off the car.

Also, if the Sygic is not active (i.e. in background) I cannot hear the alerts.

Any sugestions?Maybe I'm missing something?
[FYT Android Head Units] surfer63:
Do you have any nokill option installed/enabled? And if it is an Xposed module, did you activate it?
[FYT Android Head Units] ptolomeo:
Good question. I'll check it (I took it for granted that it was activated by default)
[FYT Android Head Units] gtxaspec:
Looks like Google broke voice calling in the new open G apps so I will roll back the G apps to the previous version. Really frustrating.
[FYT Android Head Units] yuvalmesika:
Hi,

Tried custom v4.3 app and it refuse to install custom recovery or verify (checked and the build number and its 15-12), coming from your custom ROM v3.

Trying to install v5 with previous custom app.
[FYT Android Head Units] gtxaspec:
you found a bug! thanks, I am uploading an updated version of custom now...
[FYT Android Head Units] gtxaspec:
viper still has audio issues, minor popping and clicking. Although 1000% better than the stock which sounds like a slow motion broken audio stream.

i found my perfect viper equalizer setting! i'll keep digging into getting a 100% solid audio stream. I think we are 95-98% now audio quality ( minor popping )

After more testing, all audio defects seem to disappear after 5 minutes or so. They come back if you pause audio, then go away after some time.
[FYT Android Head Units] derschnelle:
Short question: How do we flash incoming updates? Is dirty flashing possible or do we have to clean flash when updates comes in?
[FYT Android Head Units] ste2002:
gorlexx of 4pda has started already to make translation into Russian. How do you see the process should be arranged?
[FYT Android Head Units] dyabolikarl:
Would also like ot know how to apply updates if you can dirty flash. Also what happens if you factory rest the from from the settings? Will it kill all the install like the apps you replaced etc?
[FYT Android Head Units] PoppaRoxie1986:
Would it be possible to add support for custom logo.bmp and custom bootanimation.zip? With the stock joying roms you can replace the two files before flashing and it will use the custom files instead.

Nice work on v5.
[FYT Android Head Units] gtxaspec:
Viper audio quality video

[youtube]ip9tGH4cwfA[/youtube]
[FYT Android Head Units] danstah:
Any issues with bluetooth with ok google anywhere? With the normal Joying ROM if you call someone or get a call the person your talking to hears fax like sounds.
[FYT Android Head Units] gtxaspec:
Most Bluetooth issues were fixed on the December rom
[FYT Android Head Units] danstah:
Ok cool. I'll give this a shot when I get a chance. This has been a pretty longstanding issue with the Joying ROM's. If it's fixed that's great!
[FYT Android Head Units] BassRareba:
Is the rom ready for daily use?

I'm on the september rom and i'm eager to install this :)
[FYT Android Head Units] Tarsa:
I also wanna try this out. I believe I am on the December update.

Is that sufficient? should it install without a hitch?
[FYT Android Head Units] dyabolikarl:
Installed this morning. Remember you need to be on the DEC rom to begin with to install this.

It seems stable for me at the moment. I only had it on a couple hours. So much quicker than stock too.
[FYT Android Head Units] Tarsa:
Incredibly tempted right now... I need to root it in the first place though. So I will start there.
[FYT Android Head Units] dyabolikarl:
It's easy as get the JET tool, then get the rooting ZIP

https://hvdwolf.github.io/Joying-RootAssistant/rooting.html
[FYT Android Head Units] Tarsa:
Working on it! Thanks for the help :)

---------- Post added at 01:23 AM ---------- Previous post was at 12:53 AM ----------

The download for the rom is incredibly slow. jumping between 1 and 2 hrs estimated.
[FYT Android Head Units] gtxaspec:
I'll get a Google drive mirror setup soon.
[FYT Android Head Units] Tarsa:
Thank you.
[FYT Android Head Units] karazz:
Hi all, first of all, thanks for all your great work! These small projects really show the power of the xda community.

Haven't had time to install the rom myself yet, but hoping to find some time rather sooner than later...

Quick question: Does this custom rom have any effect on the radio draining the car battery when in idle? Or is that a hardware issue?
[FYT Android Head Units] ste2002:
I am still on stock Dec FW, and my default Navi program auto starts with ACC ON since there is an option to do so in Car settings (black&white).
[FYT Android Head Units] gtxaspec:
v8 is live. updated first post.
[FYT Android Head Units] surfer63:
That is a hardware issue, not a ROM issue.

There are 2 options:

- The 12V constant wire and 12V switching wire are not correctly connected.

- You have a VAG car which sometimes have different wiring and CANbus mechanisms in place which are not full covered by Joyings CAN bus implementation. In that case you are either lucky or unlucky (like me and a bunch of others). If you happen to belong to this second group, take a look at my workaround which I posted once on a no-longer existing Joying forum.
[FYT Android Head Units] PuntoGT16VT:
https://drive.google.com/file/d/16K9bpSN8lIsd1mEgSXNut-84xj4FqzVs/view?usp=sharing

I did not filter the keycodes. I hope that's ok. :o
[FYT Android Head Units] pyrlix:
Hello!

Using the current V7 FW - sofar its a great piece of ROM. Fast, snappy and overall quite good. However Viper4Android shows "Processing NO" when using POWERAMP, Radio or Bluetooth. Any idea why that could be?
[FYT Android Head Units] markmorto:
Thanks for the quick turnaround. I'm going to try again later today.

I noticed there's a new version of custom.apk. Since I used v4.7 to install the TWRP recovery, do I need to re-install recovery using the new 4.8 version before I install the new ROM?
[FYT Android Head Units] gtxaspec:
Remove the old custom, install the new one. No need to reinstall custom recovery if you already did. Just verify to make sure installation is good.
[FYT Android Head Units] tilaksidduram:
Firstly i want to thank [MENTION=520205]gtxaspec[/MENTION] for this custom rom for the Intel Sofia HU's. This ROM really makes the 1GB HU respond much better than the Stock Joying ROM. After i installed this ROM, i am facing issues with my touch screen as it does not detect my touch inputs in two different locations on my 7" touch screen. Navigation buttons(Back, Recents, Volume, Home) on my Status bar/notification bar don't function any more. When i press them nothing happens. I am also not able to pull down my status bar from the top of the screen. All touches just below the status bar works fine and i am able to click on the Icons and have them open fine. The 2nd location that does not detect my touch inputs is the 2nd row of the Radio app(using radio app to show the location as an example). Due to this issue i am not able to set the radio channels for 2nd row in the radio App. Since the touch is not working in this location any popup that shows up on the screen im not able to click the OK button. Same goes with the Superuser allow option. i am not able to click on Allow to allow root access for some of the apps that i wanted to grant root access. If i use a USB mouse then i am able to access the HU with out any issues. I am writing here to get some help. I also tried to load the stock Joying ROM to see the touch issue i am facing is with this custom rom or not. I unzipped and copied the Joying Stock rom to the root of the USB drive and then connected to the HU USB port, i did not see a popup asking if i wanted to updated the ROM. so i opened up the custom.apk file and made sure that i have the Stock recovery installed and even with the stock recovery installed i dont see the HU giving me an option to install the stock ROM. I even tried the option to boot into TWRP and see if that can read my USB drive and install the Stock ROM. after reboot i see the white android logo and then the Green Android servicing logo , the blue bar starts to move forward and then i see the Joying ROM installation screen and here it says the signature verification failed and the installation gets aborted. The ROM i'm installing is the 1024 * 600 version with MCU 5.25 and older. Can some one provide me the steps to flash the stock joying rom back so that i can verify if the touch issue i am facing is a hardware issue or a software issue.

I am currently running the V7 version of this ROM, prior to installing the GTX custom ROM i was running the Stock Joying Rom released on Jan 2018.

Thanks in advance for the help.
[FYT Android Head Units] gtxaspec:
Flash stock recovery, and then hold the reset button down for 30 seconds, could take up to three attempts. Make sure you have the USB drive plugged in. Unit will reboot with purple lights and then boot off the flash drive to restore stock. Boot into stock joying, verify everything works fine, then try flashing v8.
[FYT Android Head Units] tilaksidduram:
Thanks for the quick response [MENTION=520205]gtxaspec[/MENTION]. I will try the steps you mentioned above and will revert back.
[FYT Android Head Units] rilerale:
Hello, [MENTION=520205]gtxaspec[/MENTION] [MENTION=2550900]surfer63[/MENTION]

JY-FM122N2 with GTX V8 and XSofia Tweaker 1.11 dirty flash from v7 without clear

i have hardwheel for on/of and volume, hardwheel for radiosearch ond home function

start volume is 0

volume changes are not saved

eq changes are not saved

volume wheel reacts very badly

home wheel button reacts very badly

custom settings for hardbutton in xsofiatweaker are often not executed

I deactivated the module, problems remain

So it's up to the gtx v8

after the 10 reboot xsofia is apparently completely without function

gtx v8 is useless for me

a great pity

There are obviously many different varieties of joying

back to gtx v7

everything works
[FYT Android Head Units] gtxaspec:
Have you tried rebooting a few times?
[FYT Android Head Units] RoNeReR:
same issue here, also revert to v7.
[FYT Android Head Units] gtxaspec:
Ouch. I'll test flashing again today
[FYT Android Head Units] gtxaspec:
A logcat | grep GTX would be helpful if anyone can post
[FYT Android Head Units] gtxaspec:
ok...so i did a dirty flash to test and it failed on me, but, the good news is I found a way to fix it without starting over, will be releasing v9 to fix some issues...good news for dirty flashers....
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION], do you have a link to gpsfix 1.1?
[FYT Android Head Units] surfer63:
Not version 1.1 anymore. Version 1.11 is uploaded to my repo.

Only difference is the removal of the appcompat layer (as mentioned earlier), thereby reducing the size from 1.3M to 98Kb.

I did not do the pull request yet to lbdroids repo.
[FYT Android Head Units] gtxaspec:
does anyone have a link to the last version of android 6.0 that has working viper? i lost my copy. april or may 6.0 right? [MENTION=309187]edit[/MENTION]
[FYT Android Head Units] gtxaspec:
what is the preferred version of Xposed's appsettings module for our units? I include 1.10, but there are versions up to 1.17 unofficially. Any feedback?
[FYT Android Head Units] surfer63:
The stable version is 1.10.

I would strive for the stable version to make everything less complicated and to provide a stable build. If users find "something" in a higher beta or unstable version, they can apply that at own risk. But the normal user base should get the stable version.

(my point of view).