yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] edit:
This is the only way to overcome the button lights issue? Will the issue be present in the next version of the ROM?
[FYT Android Head Units] gtxaspec:
The button lights is a bug in the Sofia server...we can fix it with Xposed.. [MENTION=2550900]surfer63[/MENTION] might be working on it...the patch is for minimized call window not LED issue.
[FYT Android Head Units] surfer63:
This command requires root. The XSofia does not use a rooted system call. It actually should use it.

The Xposed functions hook into the SofiaServer which operates as a system app, but the system call is probably "just a call of a normal app".

I will change it.
[FYT Android Head Units] tOz666:
Hmmm, I could swear that when testing using Terminal app, I wasn't rooted and it worked well...
[FYT Android Head Units] surfer63:
That would really surprise me as /sys/fytver folder is root owned.

Well, I will do some tests and see where we get.

Edit: I'll guess it is the redirect ">". The Superuser su works like **** with that.

That was also why I fist didn't want to switch from SuperSU to Superuser and one of the reasons I had to completely rewrite my JET apk to work with Superuser. Superuser is just so much more limited than SuperSU.

Try if you can put the command in a shell script. Don't forget to make it executable and to put it in a place where you can set the exec bit.
[FYT Android Head Units] tOz666:
Could be root owned but with write access for everyone else... (chmod 666 or the like)

Thanks for checking into this!
[FYT Android Head Units] surfer63:
see my edit. After/at the same time as your reply.
[FYT Android Head Units] tOz666:
LOL this was like a chat conversation :D

Thanks I'll do that tomorrow and report back. I think files in /data can be set +x
[FYT Android Head Units] gtxaspec:
Or try echo -n "h" | tee /sys/fytverblahblah
[FYT Android Head Units] edit:
Ok, thank you. I hope it will work... but speaking of bugs, would it have been better to stay on the December ROM as a base for the custom rom?

The December ROM seems stable and bug free, at least for me.... it might be the first firmware bug free from them in the last 6-8 months.... In the Jan they added something and of course broke something else.
[FYT Android Head Units] tOz666:
I went to the car before going to sleep and made two scripts:

One with:

#!/system/bin/sh
echo -n "h" > /sys/fytver/colorled

for turning off led

and another similar one with the color I want, "b"

saved as ledoff.sh and ledgreen.sh to /data, put chmod 0777 on both as root

With a rootless terminal they work as intended

Put /data/ledoff.sh XsofiaTweaker to ACC_OFF as system call... no go.
[FYT Android Head Units] gtxaspec:
The Dec and Jan have the same bugs for me.
[FYT Android Head Units] surfer63:
Superuser doesn't support piping either from a system call from java.

We need Superuser for Xposed, but otherwise I would still use SuperSU.
[FYT Android Head Units] surfer63:
Thanks for testing. I will have a look this afternoon.
[FYT Android Head Units] gtxaspec:
i tested, from my custom app, I am able to run the command "echo -n h | tee /sys/fytver/colorled" using Superuser successfully. Are you saying you are not able to make this work with your xposed module?
[FYT Android Head Units] surfer63:
Maybe I did not make myself clear enough. When using a system call, either from java or from my JET apk, I can't use the | pipe option or the redirect option in one call.

What I didn't try so far is for example as system cal is breaking up the command like

String[] mycmd = {
"/system/bin/sh",
"-c",
"echo -n 'h' > /sys/fytver/colorled"
};

Process p = Runtime.getRuntime().exec(mycmd);

and then do this as root (su -c) or not (sh -c).
[FYT Android Head Units] sanangel:
[MENTION=520205]gtxaspec[/MENTION] version v6 can be installed in dirty on top of the V5 or will it need new installation?
[FYT Android Head Units] gtxaspec:
Yes, I am testing dirty flash now. Had some issues with the integration with custom, due to the limitations of twrp...I hope to have it fixed already just need to test.
[FYT Android Head Units] gtxaspec:
with subserver disabled, the phone app still is being forced on top... just FYI.
[FYT Android Head Units] derekbunch:
[ROM] [CUSTOM] [INTEL JOYING] GTX joying STOCK rom v5 2018-02-01

Is there a way to use a different phone app or make it to where the phone doesn’t take the whole screen? That’s the thing I hate the most
[FYT Android Head Units] luciusfox:
Hmm... they may have changed something with it then.
[FYT Android Head Units] barnesk9:
My joying unit is still on Lollipop, If I upgrade to 6.0 there is no way to downgrade or has that changed since now we can use TWRP?
[FYT Android Head Units] gtxaspec:
there is no tested way to downgrade. I have a theory, but it is un tested.
[FYT Android Head Units] amon101x:
No chance to go back
[FYT Android Head Units] surfer63:
2 evenings ago I went through the sub server. It does arrange "things" for the BT app, but it doesn't do anything at all for the "on top" issue. I can't find it in the Sofiaserver either and neither in the BT app itself, apart from the layout.

Maybe it is in the SystemUI.
[FYT Android Head Units] tOz666:
I'll check again this afternoon, but as I stated on a previous post, I had fullscreen dialer when on a launcher screen and small dialer when navigating with TomTom. could it be detecting the foreground app?
[FYT Android Head Units] surfer63:
It could be that TomTom takes over.

I use Magic Earth. Magic Earth also has its own dialer (for which you do need to give access as well on install). When I get a call, I get a popup (accept/reject) and then a bar in the bottom of Magic Earth. It completely overrules the Joying BT app.

Really perfect.
[FYT Android Head Units] tOz666:
I was right, I get the small dialer when TomTom and also Google maps is on foreground, and on the launcher and my music player, the fullscreen one.
[FYT Android Head Units] luciusfox:
FYI: while working on a completely different project, something I've found is that it turns out that gmaps works brilliantly under uG nogapps. This could yield huge performance improvement on these radios.

One enormous benefit that I've discovered, is that doesn't even require a google account. I know that a lot of people worry about putting their main google account on the chinese radio, so... win win.
[FYT Android Head Units] SynMaki:
Hey all:)

Seems like V6 is getting ready.. Do we have Viper in it?:)
[FYT Android Head Units] surfer63:
Read the changelog on first page. you see it is in.
[FYT Android Head Units] SynMaki:
I did, there is nothing. But there is a post somewhere in this thread which says that Viper will be included in V6
[FYT Android Head Units] gtxaspec:
v6 delayed...dirty flash failed on my LAST test...after about a dozen...ugh. stay tuned tomorrow...
[FYT Android Head Units] surfer63:
Then you did not read carefully enough.

====Includes====
xposed v87 x86
open gapps x86 Nano Jan 2018
ViPER4ANDROID FX
precompiled dalvik cache (first boot 2 minutes)
enabled eth0 at boot at 192.168.65.100 for debugging
............................
...........................

---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------

Just take your time and even more important: get your necessary rest.

The V4 and V5 also function very well.

We'll survive :)
[FYT Android Head Units] SynMaki:
maybe i was blind or it was added later :D

However, many thanks.

[MENTION=520205]gtxaspec[/MENTION] yep, just take your time, thanks for your hard work:)
[FYT Android Head Units] texastwurkteam:
Will there be a way to alter resolution included in this? Searched the thread/forum and didn't find any matches for Joying devices. I'm having an issue with a cracked Spotify app that places the login option below the screen with no way to access it as it won't scroll down. 800x480 is what it is currently, I believe. There's an option to change it on the far right of the Car Settings but it doesn't actually do anything for me. Unless I'm just retarded, which is also possible
[FYT Android Head Units] Tarsa:
Hey, quick question... Can I dirty flash, or should I just play it safe and clean flash V6 over V5?
[FYT Android Head Units] wanb1i:
I can't locate the ROM downnload link. I have the Custom.apk, but can't find the FW. :fingers-crossed:

---------- Post added at 02:56 PM ---------- Previous post was at 02:49 PM ----------

[/COLOR]

Just take your time and even more important: get your necessary rest.

The V4 and V5 also function very well.

We'll survive :)[/QUOTE]

Hey Surfer, any chance you can share the link to the ROM, I'm flashing the newest stock and it won't connect to my hotspot either. This ROM looks AWESOME!!:cool:

Nevermind, I found it! Well, I guess I didn't find it, that link is broken...
[FYT Android Head Units] thelunchboxosu:
Hey there! Has anyone using this ROM or headunit tried the x86 nougat port on this head unit?

I did use the search function to see if anyone in this thread had mentioned that Nougat has been ported to run on x86 and didn't see anything.

Is this any use to the awesome devs that are working on this head unit?

http://www.android-x86.org/releases/releasenote-cm-x86-14-1-r1

There are a few articles about it out there, I just don't know enough about the difference between these head units being x86 and if that would apply here to this rom being more awesome than it already is! Additionally, would collaborating with the devs that ported nougat to x86 for other machines be someone that could lend ideas here free the headunit from the drawbacks Joying may have implemented in their design? Just trying to add ideas!
[FYT Android Head Units] gtxaspec:
the boot.img is cryptographically signed by intel, to which the signing keys we do not have. We are stuck on whatever kernel the official releases use...
[FYT Android Head Units] gtxaspec:
change the DPI of the app, or of the whole unit. per app DPI changes are available on the ROM using Xposed
[FYT Android Head Units] gtxaspec:
Hey Surfer, any chance you can share the link to the ROM, I'm flashing the newest stock and it won't connect to my hotspot either. This ROM looks AWESOME!!:cool:

Nevermind, I found it! Well, I guess I didn't find it, that link is broken...[/QUOTE]

there was a last minute bug in the rom, I removed the link. I will re-upload tonight.
[FYT Android Head Units] wanb1i:
GTXASPEC, any chance you could share the download link for this, I would love to test it out!:D
[FYT Android Head Units] derekbunch:
Is v6 confirmed to be working on 800x480 head units?
[FYT Android Head Units] gtxaspec:
Yes.
[FYT Android Head Units] wanb1i:
I'd love a link to V5 so I can unbrick my HU after installing xposed. ;)
[FYT Android Head Units] luciusfox:
There are ways to work around that problem... for instance, we know that it will boot a recovery that isn't properly signed (after a brief pink lights blinking protest). So you could actually rig up a zygote (app_process) that checks what kernel was booted and issue a reboot-recovery if it boots the "official" one.
[FYT Android Head Units] gtxaspec:
To use the recovery partition as an alternate boot image?
[FYT Android Head Units] gtxaspec:
gtx ROM v6 is LIVE! post feedback PLEASE!
[FYT Android Head Units] Tarsa:
Is it okay to dirty flash from V5?
[FYT Android Head Units] gtxaspec:
Yes
[FYT Android Head Units] wolkenschaufler:
Thanks a lot for the great work!

Could anyone tell me, how can i update the helper apk? If i download the current version and trying to install it, i'm getting an error.

BW
[FYT Android Head Units] surfer63:
I assume you mean the custom apk. It has just been replaced with a version 4.6. Your "current" version might be the 4.5, which contained some errors I believe.

---------- Post added at 12:39 PM ---------- Previous post was at 12:36 PM ----------

Is it OK to dirty flash from any ROM? Including those on V3 or V4, but also from the stock Joying ROMs?

Otherwise a warning might need to be placed.
[FYT Android Head Units] ziofester70:
someone can help me? when i try to install the custom recovery, the custom remain in recovery files checksum verification and nothing happen.

Solved: maybe wrong su version.
[FYT Android Head Units] yuvalmesika:
I also got an error when trying to install the custom.apk by just double click on it.

To replace the custom apk I just copied the file to system/app/custom folder and reboot.
[FYT Android Head Units] farmerjohn:
Dirty flashed the update succesful, thanks gtx, great work. First test it looks like Viper has no effect though, I use Poweramp. Driver Status says Neon enabled: NO, Enabled: YES

Also, the Xposed Module "App settings" doesn't work for me, but that was the case in V5 also.
[FYT Android Head Units] PuntoGT16VT:
Same here dirty flash works perfect :good: Thanks a lot for the great work!

With Viper i have heavily music stuttering. But i have the problem also with stock Joying ROM.

I have a unit with internal amp, i think thats the problem.

I have one more question. I miss the "AMP Enable" settings in CarSetting.

Is this included in v6? Maybe i need a clean install to get the "AMP Enable" settings back :confused:
[FYT Android Head Units] luciusfox:
Yes. There is nothing fundamentally different about the partitions as far as what it can boot goes, its just a question of the bootloader's selection of which one it boots.

---------- Post added at 04:28 PM ---------- Previous post was at 04:17 PM ----------

You have a cooling fan on yours? Viper is an audio processing library that does its work on the main CPU, so if your CPU is throttled way down and you're running other software that is hard on the CPU, you will most definitely get audio pausing.
[FYT Android Head Units] myxcon:
Dirty flashing from stock doesnt work very well. I get some FC and also no launcher works, so be heads up if anybody feels like upgradeing from stock without clean isntall.

Also, I cannot select any car model (in settings) for the can decoder,all options are asking for some mcu files which are not available.
[FYT Android Head Units] wanb1i:
COOL!! :cool::D:good: THANKS!
[FYT Android Head Units] PsYkOpAtE:
Hi All,

I follow this thread and i say : OK let go.

First time upgrade from Joying with last firmware : OK

Test if sound working with radio app : OK

Install root : OK

Install V6 : OK

Test sound : nothing ... :(

What i missed ?

Thank You
[FYT Android Head Units] myxcon:
If you have a can decoder for steering wheel buttons, I suggest having the correct option selected when upgrading to gtx rom. The option remains active through the flash and you are unable to select other option as the mcu files are not present in /system/mcu (I guess they can be copied over from stock joying rom).

The amp enable option in settings is still not present, BUT, it sounds as if the internal amp is enabled.

Gonna test more tomorrow.
[FYT Android Head Units] PsYkOpAtE:
Exactly, i have in my car a digital amplifier (Dynaudio).

With Joying rom both setting working, but i fix setting with external amp.

And i didn't do that before GTX upgrade ...

Need to go back to Joying rom ?
[FYT Android Head Units] PuntoGT16VT:
I think internal amp is disabled. Because the music is louder with internal amp is enabled. :confused:

And i dont have the option in EQ to gain the subwoofer level.
[FYT Android Head Units] myxcon:
What I did was, flash joying stock, setup can decoder correctly, enable internal amp and then flash gtx. Seems right so far, gonna have to test further tomorrow, not spending more time in the car tonight.
[FYT Android Head Units] gtxaspec:
good feedback, looks like there was a typo in the buildscript, the McuUpdateAll.bin file was being copied to the /sdcard so it only works on a clean install. I am fixing this for the next release to /system/mcu...as far as the digital amp...i don't have a model with the amp built in. Where was this option? under the 3368 settings? I added ro.fyt.amp_switch=1 and ro.fyt.amp_type=2 to the build prop, which should have enabled the menu...

i'll do a reinstall on the joying stock rom and do some digging.

and don't dirty flash from the stock joying rom...won't ever work.
[FYT Android Head Units] Survivalism:
I Installed v5 and have been having issues with the unit shutting down instead of going to sleep, likely because I missed the factory reset after updating to Jan joying. Do I need to do a clean flash of Jan joying before I upgrade to v6 or do you think a dirty flash from v5 to v6 may resolve it?
[FYT Android Head Units] farmerjohn:
Yes, it is part of the 3368 settings.

https://youtu.be/ocZv2dx_i50

Start at 16:40.
[FYT Android Head Units] derekbunch:
[ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V6 2018-02-22

Can anyone link me to the jan joying update for Rez 800x480? Carjoying.com still won’t load for me and hasn’t for the past few weeks
[FYT Android Head Units] derekbunch:
I’m on the stock 2017_12_15 Android 6.0 Rom and when I click verify recovery, it says “SIGNATURE DOES NOT MATCH STOCK OR CUSTOM.” Is this expected as all I have done to the unit is root it using [MENTION=2550900]surfer63[/MENTION]’s JET app or does this mean my unit is not compatibile?
[FYT Android Head Units] gtxaspec:
What model is that?
[FYT Android Head Units] derekbunch:
[ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V6 2018-02-22

Joying JY-TL123N2
[FYT Android Head Units] texastwurkteam:
Seems to be up and functioning so far. Was getting a few Xposed has stopped working errors but they cleared as I rebooted it a few times for different installations. I am missing the amp options as others are, and Viper is doing the slow down popping thing for me too on the Phone Speaker option which is the only one that seems to do anything. Wasn't JET supposed to be preinstalled with this? Not biggie that it's not, just that I don't see it in here. Model: JY-TM123N2. Also getting a weird issue when paring via BT where the pin screen pops up and then immediately disappears, not letting me input anything. Can be circumvented using the stock Joying BT program
[FYT Android Head Units] swanie2000:
Can anyone point me to where I can download the original Joying Video Player APK?

I understand the need to remove the bloat from Joying, so no worries.

I am probably the only one actually using the Video Player.

Just liked it, no ads, and free. It worked well enough for me.
[FYT Android Head Units] gtxaspec:
I'll post them soon. On v7 I'll also include them in the /oem dir for anyone that's wants to add them back.
[FYT Android Head Units] swanie2000:
After you spend the better part of the afternoon getting everything set up just the way you like...

Is it safe to restart the "CUSTOM" apk,

install the custom recovery again since it was removed during the install of the custom ROM,

Then boot into TWRP?

I didn't look in there, but I was hoping there might be a way to create a complete backup of my system (NAND backup?)

Afterwards, is it safe to leave the TWRP recovery installed, and not switch back to Joying?

************************************************

I had my unit all dialed in, pretty much, and then I made the mistake of upgrading the exposed module from 87 to 89.

It requested I activate the module, and reboot. So I did.

That was the end of that, as the radio never came back up, it just got stuck in the boot screen with the animated 4 dots.

It stayed there forever. I was forced to reset three times, and reinstall Joying firmware. What a drag, but at least I was able to recover my radio.

I would like a way to recover, without having to reload Joying firmware.

This is why I ask if it is OK to leave TWRP installed?

How would you get back into TWRP after a major crash like explained above?
[FYT Android Head Units] texastwurkteam:
Anybody have any idea what could be causing this? I have the no-kill and it keeps shutting down the whole unit instead of sleep, then I get this screen, it reboots, then comes back online

https://imgur.com/a/f7pPb
[FYT Android Head Units] surfer63:
I did have that as well a few times, but I do not think it is the nokill.

You have "texas" in your name , so I do not know whether this applies to you.

In my country it is freezing. I drive very little and experimented a little too much. When I started my car (which barely started), I had the same screen, but I think it might have to do with a too empty battery causing voltage dips when starting, causing the MCU to "think" the unit was not started correctly. Maybe it did get 3 not strong enough "sparks" from the battery.

I had this 3 times on a row and really suspected the software. I had not changed anything, but after one 30-40 minute drive and the next start, it was OK and it did not do it again.

One weekend later while doing tests and have to start the car the next day when it was freezing, it did this again.
[FYT Android Head Units] farmerjohn:
But the unit shutting down instead of going to sleep is a known issue of no-kill mod, isn't it?

I keep getting the same message now and then and didn't notice it on the original joying ROM. My car is in a garage with approx. 7-10 degree Celsius, so I don't think temperature is a problem. Cars battery is only a few weeks old and powerful.
[FYT Android Head Units] surfer63:
There is a difference.

The nokill indeed does not kill apps, like the original SofiaServer. It means that "bad behaving" apps, keeping the CPU at too high frequencies, will cause the MCU to completely shut down the unit, resulting in a cold boot on next start. But that's a clean, fresh cold boot.

These bad behaving apps do not make the unit crash 3X on a row, when booting.

This message "has not fully launched 3 times", ONLY occurs on the first normal boot after having booted to the recovery (when you need to reset your unit 3 times before it boots into recovery).

Or you see this message when the unit starts to boot but can't continue and needs to restart, for example on a too weak power supply, or something bad in the boot sequence. But then it might reboot forever (soft brick).

In your case of an environment of 7-10 C it could still be a case of "playing" too long with the unit, thereby draining the battery.

When discussing this, also old memories come back. I did have my unit on the bench some 8-9 months back on a 12V-1A transformator. That one was just too weak also causing these boot errors.

When replacing that transformator with a 12V-2.5A power supply it did not occur again.

Of course you can only be sure when measuring with a multi-meter.

But I'm almost 100% sure that the "has not fully launched 3 times" is not coming from the nokill (but I can be very wrong as well)
[FYT Android Head Units] farmerjohn:
I agree that "no kill mod" does not cause the error message, because it occured before I ever used the no kill mod. I only used the nokill for a few days, but as I cannot find the "misbehaving" app, it annoys me to have to boot fully everytime I start the car. Thats why I deactivated nokill again.
[FYT Android Head Units] SynMaki:
Works great so for.

There seems only one Problem atm. I cannot control my subwoofer anymore in the original EQ settings.

Anyone got the same?
[FYT Android Head Units] derekbunch:
JY-TL123N2, any idea why I’m seeing this message? I’d love to use this room and I’m super excited to try out V6, I just wanna make sure the “stock” rom will still work with my unit and allow me to recover if anything bad happens
[FYT Android Head Units] Survivalism:
This is the same issue I have been having, I am not convinced it is temperature or voltage related as it has happened to me after driving for ~30 minutes and restarting after the car sits for ~5 minutes.
[FYT Android Head Units] merdok:
What is the proper SU version? I have first tried 2.8.2 SR1 SuperSU, and after seeing this post tried 2..82 SR5 with the same results.

I have waited ~5 minutes without a change and the app reacts if select the exit button or get user ID options. it does prompt from SU app and says it is root.

I was on Joying build from last year, updated to the Jan build rooted over adb and am stuck at this point. device is the UL135N2
[FYT Android Head Units] surfer63:
You mean the rooting of your Joying before you can do the custom install?

We no longer use SuperSU, we use (se)Superuser. See my signature for the script.