yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] luciusfox:
Lag isn't nearly as bad as being *wrong* ;)

But of course, minimizing the lag while not massively throwing off the accuracy is a very good thing.

My biggest concern when it comes to reducing the window would be at low speeds with poor signal quality. At highway speeds, the distance travelled will be large between samples, so inaccuracy in the location would have very minimal impact. Highway also tends to yield better signal, since you are more likely to be out in the open.

On the other hand, driving in traffic in the concrete jungle...

If you wanted to, you could get fancy with this. Perhaps with a higher error and/or lower speed, increase the window length?
[FYT Android Head Units] tOz666:
When you're talking about lag are you referring to lag on the KM/h update, or lag on location update response? i've put newest GPS Speed fix from JET and didn't notice any to no lag using TomTom Go... of course my eyes were on the road and I may need to re-check.
[FYT Android Head Units] surfer63:
The speed is updated once per second to the screen, but it is based on 5 samples, and now 3 samples (your download), which means that the "real" speed is running 5 or 3 seconds behind.

When you drive at constant speed on the motorway, preferably on cruise control, you will have no problem at all.

When you drive in the city in rush hour, constantly accelarating and decelarating, you see that the "real speed" is lagging behind.

And you are completely right: you should have your eyes on the road, not on the unit.
[FYT Android Head Units] ste2002:
> When you drive at constant speed on the motorway, preferably on cruise control, you will have no problem at all.

> When you drive in the city in rush hour, constantly accelarating and decelarating, you see that the "real speed" is lagging behind.

This is absolutely perfect for me: on cruise I need correct reading not to break speed limit, and in jammed traffic in start-stop mode I just do not need any speed readings much (or at all).
[FYT Android Head Units] surfer63:
As mentioned: I'm testing with 1-sample insted of 3 samples, but actually I'm perfectly happy with the 3-sample version. I have not seen any weird speeds (between buildings in th city for example).

I'm just testing the 1-sample version to see how stable the signal is. If it is stable, then we do not need to average multiple samples.

After all: we already got an unsampled speed from the unit before the GPSSpeedFix (be it an "unprecise" one).
[FYT Android Head Units] luciusfox:
You're making unfounded assumptions about the implementation of speed determination within the GPS unit itself. What they're doing is more complex than just calculating the distance/time from one sample to the next. They have a lot of different filters running in there to spread out the samples while still giving a reasonably instantaneous result.
[FYT Android Head Units] gtxaspec:
Curious, How should the proper implementation function vs what FYT did?
[FYT Android Head Units] luciusfox:
Here is the thing; the hardware in it is actually calculating the speed correctly (in KNOTS). The problem is that ANDROID likes the speed in m/s, and accepts a FLOAT, but FYT is too stupid to handle the conversion and casts a m/s INTEGER to a float and feeds that to Android. That's why the speed steps are in 1.0 m/s (1.0 m/s = 3.6 kph).

Also note that FYT does NOT write the GPS firmware.
[FYT Android Head Units] gtxaspec:
Hmmm...I wonder if that is present in the Intel sdk?
[FYT Android Head Units] liquidini:
First of all thanks for this great custom room.

I was at 5 1.1 stock and now have lost the radio widget.

I used nova launcher in previous version and the widget was there.

Is it deprecated in Android 6?
[FYT Android Head Units] surfer63:
I really can't remember what it was in 5.1.1, but in 6.0.1 the radio widget is part of the joying launchers.

So if you use Nova you indeed will not have a radio widget.

The creator of the FCC launcher is currently working on a radio widget for his launcher.
[FYT Android Head Units] liquidini:
In 5.1.1 the widget was there to use with nova launcher.

I will try to install that radio.apk and see what happens. Maybe it's specific to Android 6 restrictions
[FYT Android Head Units] yebokmj:
My Waze is constantly loosing signal dispite the unit having good signal, this was on the December ROM this ROM and then this ROM with latest gps fix from JET. Any ideas?
[FYT Android Head Units] edit:
I would first try step 7 but feel free to check then all if you still have problems :

1. check the GPS cable if it's securely tightened to the headunit

2. check the GPS antenna positioning and the signal strenght

- if the positioning is bad and the signal is weak when you are on the road, open skys, then it will be worse in the city and you might even loose it if you have tall buildings around

3. some windshields have a special coating to reduce cabin heat (have a greenish/violet tint when you look from outside) that blocks GPS signals up to 60%, in that case you need to find a solution to mount the GPS antenna on the outside of the car OR in same cases there are special zones of the windshield (usually near the mirror) where are safe to mount the antenna - if that's the case check the car manual for more details

4. some windshields have heating, very tiny wiring that heat up the windshields.... those block the GPS signal up to 40% but there are areas where you can mount the GPS antenna on the windshield without issues

5. antenna cable might get broken inside if the cable is bent, tensioned or from vibrations- if that's the case buy another from a store that accept returns, it costs 9-12$, install it, if it runs then keep it... if not return it and go at step 6

6. open up the HU case and check GPS antenna cable soldering on the SoM, check if the soldering points are ok

7. if you use GPSSpeedFix module, disable the GPS module from Xposed and restart the HU
[FYT Android Head Units] surfer63:
What do you consider as the latest gpsspeedfix? The one of last Thursday 16 Feb? Because that is the last one.

Please be more specific. You now let us guess which version you have.

Based on your description you still have the one with the "lastbearing" issue, which is NOT the latest version.

Please reinstall the gpsspeedfix.
[FYT Android Head Units] edit:
If I think about it, since I started to use the Xposed GPSSpeedFix v1.0 or the v1.1 the Waze makes some strange attempts to redirect but it cancels them or something... I did not pay attention exactly what happens because I always look at the road but I hear

Waze beeping for no reason and when I look at it it still has a small blue window on the bottom of the screen telling me something (forgot exactly what).
[FYT Android Head Units] yebokmj:
The unit has good signal as I mentioned, if you toggle back and forth between waze and settings gps you will see both glonass and gps have strong signal with 6-8 satilite each when Waze says there is no gps signal. This continues to be an issue even after the "latest" Thursday's JET update to gpsspeedfix. I'll try number 7
[FYT Android Head Units] dyabolikarl:
If it's constantly re-calculating. Then get the newest gpsspeedfix. It fixed my issue.
[FYT Android Head Units] mefisto1972:
Здраствуйте.Спасибо за отличный РОМ.Когда выйдет 6 версия??Благодарю
[FYT Android Head Units] derschnelle:
English would be cool ;)
[FYT Android Head Units] CODEONETEAM:
He wanted to say:

"Hello. Thank you for the excellent ROM. When will version 6 come out? Thank you."

:laugh:
[FYT Android Head Units] gtxaspec:
[MENTION=2550900]surfer63[/MENTION], do you mind if I include JET on the v6 release? I've had various people ask to have it built in.
[FYT Android Head Units] gtxaspec:
If anyone wants to tackle the LED's turning off when the system goes into ACC_OFF...maybe we could do it using XPosed...need to look in which method sofiaserver does this. It should call /sys/fytver/colorled somewhere, or the jni i2c lib...
[FYT Android Head Units] bigsteve01:
Hi gtxaspec I have kept my unit booted is there any chance you will share your ideas to fix my boot issues

Thanks
[FYT Android Head Units] surfer63:
No problem at all. I don' t know though what the automatic update mechanism will do if it is installed as a system app. But if that no longer works I use the same trick as for the replacement of all other system apps.

I can do a quick test by pushing an older version as a system app in the current ROM and see what it does if it checks for a new version.

---------- Post added at 08:09 AM ---------- Previous post was at 08:05 AM ----------

It could be done quite simply by adding the command

echo "0" > /sys/fytver/colorled

and on ACC_ON the value for the selected color.

I am already looking if I can add some "badly saved" Joying settings to a settings profile in the XSofiaTweaker, especially selected radio frequencies, colorled settings, and a few other things I think are important (maybe other settings for other people)
[FYT Android Head Units] gtxaspec:
sure, please remind me

Are you able to boot into the android desktop

were you running the STOCK or the CUSTOM recovery?

are you familiar with ADB or terminal commands?

How did you install? USB or MICROSD.
[FYT Android Head Units] gtxaspec:
color led takes letters, i think a through g, also has to be

echo -n "a" > /blah blah

good idea, easier than hooking the method...still it would be nice to find it and add some sort of mod to the "time only" function.
[FYT Android Head Units] surfer63:
You are right about the letters. You were the one that shared that with us.

blue echo -n "a" > /sys/fytver/colorled
green echo -n "b" > /sys/fytver/colorled
teal echo -n "c" > /sys/fytver/colorled
red echo -n "d" > /sys/fytver/colorled
pink echo -n "e" > /sys/fytver/colorled
yellow echo -n "f" > /sys/fytver/colorled
white echo -n "g" > /sys/fytver/colorled
off echo -n "h" > /sys/fytver/colorled

What do you mean with time only?

Edit: I know what you mean. I'm already looking at an Xposed module for the MTC that does this based on time and geographical position. The user can then say: + xy minutes or -yx minutes, and the leds are switched on/of.
[FYT Android Head Units] bigsteve01:
My unit is booted to the desktop at the moment

I am running the stock recovery

I have used adb for rooting my unit although I am no expert

I usually install by usb

Thanks
[FYT Android Head Units] rambo21es:
Thanks for your work. I like this mod rom, but COPILOT app crashes after some minutes running.

Could you check it?

Thanks
[FYT Android Head Units] dixet:
Since I'm an impatient man I did not want to wait for Joying to be back from their new years celebrations and repair their site, so I used this file to try and update my unit to the januari update. With the intention to install the custom rom afterwards.

But with some poor results... the update started fine, but after a few seconds gave the message "Canot [sic] unzip update file! Error wait here ...."

After that the unit would not boot anymore. Result is the same when updating from either sd-card or usb.

Any ideas?
[FYT Android Head Units] myxcon:
Are you certain the download was ok and not corrupted?

MD5 :358E80E0927470D6265E0329C397FD35

SHA1: DEFFC1A78F0D440AE6473C9FAA5C8DEDA2EA280D
[FYT Android Head Units] gtxaspec:
I will send you a custom version of the apk that should help you recovery the unit. I'll send you a PM soon.
[FYT Android Head Units] gtxaspec:
heck of a time figuring out this upgrading /system without wiping data, due to limitations of the intel sofia SDK, and the version of TWRP that runs on our units. Looks like I just figured it out. I will need to make some changes to the custom apk to make this work easily for users. Almost ready for a new release...
[FYT Android Head Units] bigsteve01:
Thanks for your assistance

It's much appreciated
[FYT Android Head Units] surfer63:
Great work!

=============================

I have a final request to enable possible use of usb dacs. In /system/etc/audio_policy.conf

usb {
outputs {
usb_accessory {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_USB_ACCESSORY
}
usb_device {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_USB_DEVICE
}
}
}

Can you add an input section for usb dacs?

usb {
outputs {
usb_accessory {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_USB_ACCESSORY
}
usb_device {
sampling_rates 44100
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_USB_DEVICE
}
}
[COLOR="Red"] inputs {
usb_device {
sampling_rates dynamic
channel_masks dynamic
formats dynamic
devices AUDIO_DEVICE_IN_USB_DEVICE
}
}
[/COLOR] }

For usb dacs to work at all, this section is needed.

I could also add it to my JET apk, but Joying should already have added it (like on any phone). Whether or not you have a usb dac, it "doesn't hurt".

(No, I don't have a usbdac. Yes, I try to enable the usbdac functionality in my XSofiaTweaker xposed module.

I have added it to a branch of my XSofiaTweaker -> USBDAC)

The XSofiaTweaker usb dac apk can be downloaded from here.

It is completely untested as I do not have a usb dac. You also need the section in the /system/etc/audio_policy.conf as mentioned above.

You need to enable the "Block Joying volume control and enable volume control over USB DAC." from the "Miscellaneous Settings".

This is all based on the initial work from [MENTION=503463]AssassinsLament[/MENTION] (Rolf): https://xdaforums.com/showpost.php?p=72107360&postcount=127
[FYT Android Head Units] gtxaspec:
i don't remember if I have a USB DAC, but I can buy one easily...I merged viperaudio in and am using their audio policy, not near my computer, are those changes in the viper files?
[FYT Android Head Units] surfer63:
No, Viper needs other settings also in the /system/etc/audio_policy.conf.

I assume though that once usb input (from the usb dac) is enabled, viper might be able to work on that as well. After all it is just another digital input. Viper only works on digital inputs and will do nothing for the radio.

Of course I could buy a usb dac, but I don't need one.

Besides: I have no more usb connections left which means that I a should also buy a hub.
[FYT Android Head Units] gtxaspec:
lol, yes I also bought a hub. for cable management, I removed one of the super long usb cables, and neatly pulled and rolled the other one to fit in the unit so all the cables are the same length. A usb hub is working fine with my USB ethernet as well as other junk. I'll add those changes into the audio policy file.
[FYT Android Head Units] surfer63:
I still have to look at that ethernet in my JET.

Thanks for adding the changes.
[FYT Android Head Units] tOz666:
Will that fix up with bluetooth music? mine is not working
[FYT Android Head Units] gtxaspec:
I haven't tried Bluetooth music in a while, but last I did it was working. Could you please remind is what isn't working the way it should??
[FYT Android Head Units] tOz666:
Of course, using Bluetooth Music app, with your custom ROM, with the phone paired and all, you fire up the app on the HU and put some music on the phone. No music is heard, but the controls (skip track, pause, etc) are working as you can see the app you use on the phone (Spotify e.g.) obey to controls.

When using BT music app in the untouched Joying ROM the sound works flawlessly though.
[FYT Android Head Units] gtxaspec:
I'll try as soon as I'm done eating lunch on my drive back!
[FYT Android Head Units] gtxaspec:
Using Google play music, i can confirm Bluetooth music streaming does work. I had to enable media audio on my phone under the jy Android device options in Bluetooth. Controls work, and it does display the track title also.
[FYT Android Head Units] edit:
Since this is one of the more active threads latest I will post here :

Can you guys find a way to make the headunit BT phone app minimize in the background when I am talking on the phone please?.... or can you point me to an Xposed module maybe?

When I am using Waze or Google Maps and receive a phone call it's a big problem for me, I can't hear the indications or visualize the map and that's a deal breaker for me.

Thank you !
[FYT Android Head Units] tOz666:
Guess I'lll try when you release next version. I personally think that a custom ROM following Joyings updates of the good stuff and leaving out the crapware is the way to go. Thanks for your work.
[FYT Android Head Units] gtxaspec:
in the pipeline, I just wonder if it's sofia-server that forces it to the front, or the phone apk. leaving towards sofia-server. the fix will be an xposed module.
[FYT Android Head Units] farmerjohn:
Haven't tried it myself, but maybe Bluetooth Mod by Baloo1986 is helpful:

https://hvdwolf.github.io/Joying-RootAssistant/OtherMods-examples.html
[FYT Android Head Units] PuntoGT16VT:
I install this mod yesterday with the latest JET, but I have the same fullscreen as without mod if I make a call. I don’t know what I’m doing wrong. I have the custom rom installed.
[FYT Android Head Units] surfer63:
Did you reboot?

I have been using the Baloo1986 mod as well but not on the GTX ROM. On the Joying ROM it worked fine after reboot.

I made a patch file as the changes are layout related, not smali related.

I just did a patch on the January BT apk

apktool -d JY-1-C9-BT-V1.0.apk
cd JY-1-C9-BT-V1.0
patch -p0 < ../org-vs-baloo-l1.txt
patching file 'res/raw/bt_contact.xml'
patching file 'res/raw/bt_contactitem.xml'
patching file 'res/raw/bt_dial.xml'
patching file 'res/raw/bt_history.xml'
patching file 'res/raw/bt_pair.xml'
patching file 'res/raw/bt_set.xml'
patching file 'res/raw/conf_platform.xml'

cd ..
apktool -c b JY-1-C9-BT-V1.0

If anyone wants to test this January BT mod on the V5 January based GTX ROM, please find attached.

(I don't have time coming 1½ day)
[FYT Android Head Units] PuntoGT16VT:
Yes I make a reboot but it’s the same as stock.

Maybe I can test it tomorrow.

Thx.
[FYT Android Head Units] luciusfox:
sofia sub server
[FYT Android Head Units] DBestman:
I had the same problem. Go to the volume settings and crank up the "alarm" volume. That should fix the bluetooth audio.
[FYT Android Head Units] tOz666:
I suppose you mean crank up the alarm volume

on the HU

. So, what I did when I had GTX rom installed, was to immediately switch to standard joying settings using JET, which that, IIRC, don't have the control for setting up Alarm volume... so I didn't raise it up.

Going to try V5 then, and also try the LED commands that were posted earlier in this thread, because they're always on even when you shut off the car.
[FYT Android Head Units] DBestman:
Yes, the "alarm" volume in the settings that come with this ROM. You're right, the Joying settings do not offer a separate alarm volume.
[FYT Android Head Units] rambo21es:
COPILOT app crashes after some minutes with this mod rom.

Anyone else?

Solution?

Thanks
[FYT Android Head Units] gtxaspec:
Note that my alarm volume is set to the minimum level and I can still hear Bluetooth audio just fine. It must be changing when I have the bluetooth app open.
[FYT Android Head Units] tOz666:
I use TomTom Go, it works flawlessly, it does have everything I need, and Valencia street coverage is excellent! give it a try.

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

I'm reinstalling your V5 ROM again, give me a few hours to set it back up again and i'll tell if I succeed with BT audio. If it works i'm good, and if not i'm available to test whatever fix.
[FYT Android Head Units] rambo21es:
Me too, I prefer TomTom Go, but it seems to me that Copilot it's faster getting position.

Anyway, I have the premium Copilot app and I would like to be able to use it, like it does with stock rom.

Gràcies!
[FYT Android Head Units] merdok:
I have been lurking in this thread, anxiously waiting to update my UL135N2. I have read several posts of amp switch. Is this for remote amp turn on, or internal amp on different version than I own?

I have an external 5ch amp
[FYT Android Head Units] PuntoGT16VT:
It’s only for the internal amp in the unit from joying.
[FYT Android Head Units] PoppaRoxie1986:
I have a UM135N2 (it's the same only it came with Android 6.0 preinstalled). The amp option in Car Settings (on the same tab as the key tone option) is to turn on and off 12V to the orange harness wire and it's used for remote amp turn on. I have a cooling fan hooked to this wire to make it possible to turn the fan on/off as my Pioneer external amp (GM-A4704) does not require the remote turn on.

There is an amp selection option on the menu that requires the 3368 password to select internal/external amp.
[FYT Android Head Units] myxcon:
It's currently missing in latest v5, hopefully it will make it's way back in v6, for us users that require internal amp enabled.
[FYT Android Head Units] PoppaRoxie1986:
I can confirm that it is in v6 and present in gtx's ROM. That's why I indicated that I have the UM135N2 as my unit came with 6.0 preinstalled. It seems that the internal/external selection doesn't do anything if your speakers/amp are not connected to the RCA connections (i.e. hooked to the wiring harness).
[FYT Android Head Units] surfer63:
V6 is not out yet. Which one do you mean?
[FYT Android Head Units] PoppaRoxie1986:
My bad, apologies for the confusion. My mind was thinking Android 6.0 not v6 of gtx's ROM.:p :D
[FYT Android Head Units] texastwurkteam:
Any ETA on V6? Seen it been talked about in this thread since Feb 1st and just curious. Seems this ROM may answer all/most my problems
[FYT Android Head Units] gtxaspec:
Finishing up custom and some scripts in the ROM...been super busy IRL last few weeks, everything has slowed down now. Aside from switching all my development stuff to a new machine (and set it up the way I like) the next few days should see completion and release. (Yes 20 days is a long time on xda...lol)
[FYT Android Head Units] texastwurkteam:
Ahh all good man; take your time. Hopefully this is my savior from the Joying headaches, stable builds are always better lol
[FYT Android Head Units] tOz666:
Well I reinstalled GTX V5 and my bluetooth audio problems are gone, without doing nothing... strange.

I tried this command setting this commands on ACC_ON and ACC_OFF as system call on XSofiaTweaker... they doesn't seem to work, and I checked the command syntax, the commands work using Terminal app...

The module is working as it unmutes Alarm volume correctly.

I want to turn off (echo -n "h" > /sys/fytver/colorled) when ACC_OFF and same but with "b" to turn on green on ACC_ON

Is this feature working yet or am I missing something?
[FYT Android Head Units] gtxaspec:
Try it in a terminal or via adb. Works on those for me, I haven't tried via xsofia yet.
[FYT Android Head Units] tOz666:
I think I reproduced that issue, with the standard SofiaServer and standard bluetooth app that comes with this ROM doesn't use mini-transparent caller app, instead, it goes fullscreen.

However, then using [MENTION=2550900]surfer63[/MENTION] 's JET, I installed december nokill only mod (hvdw) that includes NoKill and enhanced navi_app.txt

With this it started working, but only when using certain apps, like TomTom Go, so it didn't block my navi view, it used the mini-transparent caller with buttons on the bottom.

So my guess is that SofiaServer or BT app takes navi apps from that txt and uses the small caller accordingly, and if you don't have this well set up (I don't know what the settings of the default sofiaserver that comes with this ROM are, apart that I think it uses no-kill and some other settings too)

But I may be completely wrong and I only had luck, and without errors because of a fresh install, but you can try my advice...

---------- Post added at 08:21 PM ---------- Previous post was at 08:19 PM ----------

Yes the commands work good on terminal and/or adb, I want to try Xsofia to automate the process when I leave the car... I want to avoid a "christmas tree" effect that points my car to thieves in not-so-safe places.