yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] st.trophey:
Is it possible to adjust (or is it hardware option) timer, when back view mode activated after reverse gear is on? At me it switches in current of 5-6 seconds. Sometimes, already it is not necessary. Switching the interface. The camera turns on immediately.
[FYT Android Head Units] Polluti0n:
Wow the development for this unit has come along way since the last time I browsed this forum. Congratulations to all involved.

I was thinking about a few of the requests I saw to include a file manager or a media player packaged with the rom. A good way to include these features while still keeping the rom lite would be to use an aroma installer. This allows the users to select the apps and features they would like preinstalled on top of the base rom. You could even let them select build.prop modifications, Preferred DPI, and which Xposed modules they want enabled.

Just my 2 cents.

Serious props, respect and gratitude for everyone's contributions.

-Polluti0n
[FYT Android Head Units] bigsteve01:
Hi I hope you can help

I updated to the version 1 rom as soon as it was available and upon my first reboot I had problems with the unit not booting

I have since discovered if I leave the unit powered on it will boot and run fine once every approx 24 hours

I believe my trouble is caused by flashing this rom from the may joying rom and not updating to the Dec rom

I am unable to update to a joying rom as my system will not recognise it

Is there any way I can get my unit updated properly

Thanks
[FYT Android Head Units] surfer63:
When you boot your unit, wait till you see the boot logo. Then press the reset hole with a "pointy" thing. Do this another 2 times.

The 4th time the button leds will blink pink. At that moment insert the usb-stick or sd-card with a clean joying firmware rom.

It might immediately start the upgrade, or it might reboot another 2 times flashing pink and then start the firmware install.
[FYT Android Head Units] gtxaspec:
When you are able to boot, re flash the stock joying recovery. Then you will be able to update to Dec ROM.
[FYT Android Head Units] bigsteve01:
When I re boot my unit all I get is pink lights immediately

It might take 15 hours before the logo appears and it is very unlikely to happen while I am in front of my unit

---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------

My unit is booted at the moment

I have used your app to confirm stock recovery us installed but when I insert my usb stick the update fails to start
[FYT Android Head Units] gtxaspec:
Ok do this:

You need to press reset until you get pink lights, with the USB inserted with the stock joying ROM.
[FYT Android Head Units] bigsteve01:
OK I will try this now but every time I re boot it gets stuck at pink lights without even pressing reset then if I leave it like this I will boot after approx 15 hours
[FYT Android Head Units] gtxaspec:
Did you flash stock recovery before and still have this problem?
[FYT Android Head Units] bigsteve01:
No I assumed your rom automatically re flashed stock recovery

I have now re flashed and confirmed stock recovery

I will try now to re boot and see if it will flash joying Dec rom
[FYT Android Head Units] gtxaspec:
Ok. Report back please!
[FYT Android Head Units] bigsteve01:
I have re booted straight to the same pink lights

The led on my usb stick doesn't even flicker

I have tried 2 sticks that I normally flash my unit with and also a micro sd card
[FYT Android Head Units] gtxaspec:
What model is your unit? WhichROM were you on before?
[FYT Android Head Units] bigsteve01:
Jyul135n2 I was on the March rom
[FYT Android Head Units] bigsteve01:
Sorry may not march
[FYT Android Head Units] gtxaspec:
When you get the unit booted again let me know. I've got some ideas to fix your boot problem
[FYT Android Head Units] bigsteve01:
Thanks for your help

Hopefully it will be booted when I get home from work

I will let you know
[FYT Android Head Units] gtxaspec:
Sure. I will test on my unit before I have you test on yours for safety.
[FYT Android Head Units] kawaninja72:
Hi

I'm from Italy and are new of this forum

thanks to developer of nice Rom

i install this rom on my Joying 2din and start to test it.

For now i found that when I reboot the system the master audio volume come back to "18" and not at the value that I set in the car setting.

I continue to test the Rom and post in this thread my results.

Thank a lot

bye
[FYT Android Head Units] bogdi1988:
There is a setting somewhere in car settings app for that. Either in the first tab or in the last tab where you have to enter the pin to unlock it.
[FYT Android Head Units] DBestman:
This. Will. Be. Fantastic!!!
[FYT Android Head Units] bogdi1988:
Can you please add the feature in the car settings to allow backlight at 100% when lights are on? It's limited to 70% right now.
[FYT Android Head Units] gtxaspec:
It is, it's called backlight current, password 5768.
[FYT Android Head Units] bogdi1988:
It's limited at 70% when lights on. If not, how do I adjust time range of I chose "night" mode on time instead of switch?
[FYT Android Head Units] gtxaspec:
Whatever you set the system brightness slider at, when your headlights are off, should be remembered.

The same goes for:

Whatever you set the system brightness slider to when your headlights are on, should also be remembered.

Or, do you mean that the minimum brightness when your headlights are on is limited to 70%?
[FYT Android Head Units] bogdi1988:
Correct. Bump the 70 limit to 100
[FYT Android Head Units] gtxaspec:
You mean lower the MIN brightness to 0? Max should be 100 already.
[FYT Android Head Units] bogdi1988:
See attached image
[FYT Android Head Units] derekbunch:
Is this rom compatible with the Joying JY-tl123n2 as long as it has build number of sofia3gr_car_64-userdebug 6.0.1 MMB29M eng.bsp.20171215.153906 release keys? I only ask because when loading the apk, the buttons are on top of each other and I would like to make sure it is compatible before I continue. My unit is 800x480 so that may be why, just wanted to make sure beforehand
[FYT Android Head Units] Tarsa:
I'm getting Bluetooth disconnects when connected with phone.
[FYT Android Head Units] gtxaspec:
Wait for v6 if you have 800x600, I actually have someone testing on that resolution right now, there are some changes to some scripts that need to be adapted to that resolution (I'll keep you guys posted...that's why v6 is slightly late.)
[FYT Android Head Units] derekbunch:
Thanks for the quick reply, I will wait for v6! Great work btw, I can’t wait to try this out!
[FYT Android Head Units] edit:
It is at 100% when the lights are on... that 70% in your picture that you posted is the MIN value that the brightness can go if you decide to LOWER the brightness using the slider...

If my answer was not clear enough it means I do not understand what your real issue is and you might need to explain it more clearly... or better PM me.
[FYT Android Head Units] bogdi1988:
It's actually backwards. It is supposed to reduce brightness when lights are on - so it's not too bright at night to disturb vision. The issue I have is that during the day I run my DRL and so the unit is wired to that and not main headlights... so as soon as I turn on DRL, brightness is reduced to 70%. I guess it would be nice to have a better manual control over the brightness. I know I can set the brightness to time control instead of light switch, but I can't seem to find the setting where you set the "night" and "day" time. I know it was somewhere in the menus.
[FYT Android Head Units] edit:
Yeah, it's backwards.... I did not write corectly.

OK... here is what I do that might apply to you.

In my case MIN brightness possible value is set to 5 and Max set to 100

The HU remembers the brightness you set via the brightness slider from the top down menu as you know... it remembers the value you set when the headlights are on... and when the headlights are off. So when the headlights are on by default it goes to 5% brightness (the value that you set in the CarSettings) BUT if you slide down the notification bar and you modify the brightness slider position to the right to add more brightness next time you turn on the light it will go to that specific brightness position that you set before ignoring the brightness you you have set in the beginning in the CarSettings app...

The bit annoying part for me is that when I get out of town during the day I have to turn on the lights (it's the law here) and the brightness goes all the way down to 5% because I keep the brightness slider all the way down when I turn the headlights on... so I use the slider to take it all the way to 100%... the downside is that I need to adjust it manually again next time when I turn on the headlights and it's actually night.

In the CarSettings menu you basically define how low or high the brightness can go when you move the brightness slider... the actual brightness for the headlights on and off are set through the brightness slider.

So, bottom line, in my case there is nothing that prevents me from have the brightness at 100% or 30% or 50% no matter if the headlights are on or off no matter if I defined my MIN brightness to 5.

IF I set the MAX brightness to 50% in CarSettings ONLY THEN I cannot have the max brightness to 100% EVEN IF i have the brightness slider all the way to MAX.

If my explanation was not enough, like I said, PM me to discuss it further because I think we are a bit offtopic by now.
[FYT Android Head Units] bogdi1988:
I think I'm following this time
[FYT Android Head Units] myxcon:
Does anybody know where I can buy one of those 40 pin ribbon cables that connects the screen to the motherboard in the single din units? Mine broke...
[FYT Android Head Units] st.trophey:
You can ask part directly https://joyingcardvdplayer.aliexpress.com/store/1463369

(after 10 days)
[FYT Android Head Units] mirzinho:
I am new to the process of installing custom roms to android units.

I have a Bway Auto unit with the following info:

APPVER: K2001_YZG_s211103.20170518

PLATFORMVER: K20-2015/05/18 -7.03

MCUVER: V1.3-FF01-20160503-A020-CAN0000-00-00-DVD0000000-00

SWVER: YZG_t3_p2_sq

I was wondering if I can install this ROM? Or if someone can tell me how I can tell what is compatible?

Help would be much appreciated!

Thank you!
[FYT Android Head Units] derschnelle:
This is what gtxaspec said about other brands:

"So I've been noticing that people are trying to install this custom ROM on non joying Sofia based units resulting in bricks. This ROM is only supported on joying or witson units. Any other Sofia 3gr based units have a different kernel and when this ROM is flashed will result and one good Boot and the following boot will be bad. The unit get stuck in an endless loop trying to verify security.

I'm in the process of updating the custom APK helper to refuse installation on non joying or witson units."

So I would say no, you can't use this ROM with your unit :(
[FYT Android Head Units] PuntoGT16VT:
Hello,

first, very good work. I'm looking forward to next update. :good:

I tested the Custom ROM yesterday and i have some little problems.

My stock joying firmware was from 26. january.

TomTom Go has problems when i install and activate the xposed gpsfix with Joying Extra Tools.

On CarSettings i have good GPS signal, but TomTom makes some weird movements.

Sometimes he stands on the spot and does nothing. :confused::confused:

And the second problem is when tomtom giving direction the music sound will not lowered.

I set tomtom as default navi app in carsettings. With Stock Joying everything works perfect.

I have a unit with internal amp and there is no settings to activate the internal amp in carsettings.

Maybe that is my problem?! I read yesterday the amp settings comes with v6.

It only lowered the sound when i deactivate xposed completely. :confused:

Regards

Ergin
[FYT Android Head Units] bigsteve01:
Hi gtxaspec my unit has finally booted if you have any suggestions for me
[FYT Android Head Units] surfer63:
I thought you did mini because it contains google maps (which I do not use either:)). The smaller ones don't have GMaps . But you can always download GMaps from the play store

nano is excellent as it still contains Google Search and Google TTS. It does not contain the Google Now launcher for those who are interested in that one (again: I'm not :))

nano vs. mini should also make the zip about 400MB smaller (with pre-odexed packages)
[FYT Android Head Units] gtxaspec:
v4 is live! open gapps nano! uploading installation video to youtube!

Edit: updated custom to V4.1 to fix installation from SD cards issue. Download the latest custom to install the rom from micro sd.
[FYT Android Head Units] PoppaRoxie1986:
I downloaded and tried version 4 with custom4_1. I installed using micro sd card. Gotta say it worked really well! Very nice indeed.

One comment regarding your custom app, perhaps the button "flash stock" should say "flash gtx" as flashing stock implies to me that I would be installing a stock joying rom (boooooo :p ). In addition the 120 second delay at the end seems, rather long (too long for the impatient, like me).

Could you perhaps change the sleep timer to like every 5 seconds check to see if the user removed the install media (the script should already know where it installed from). Maybe if you want the lights flashing a little longer go until you've detected the removed media two or three times.
[FYT Android Head Units] m1john:
I can use this RightCamera (front cam app) modified APK in stock rom? I am rooted
[FYT Android Head Units] surfer63:
deleted. Stupid xda did not work this afternoon.
[FYT Android Head Units] surfer63:
I flashed the V4 Yesterday evening. Now that it is reduced in size (nano Gapps vs mini Gapps) it flashes even faster. In less then 8-10 minutes, it completely flashed and restarted.

And maybe off-topic and maybe not: I did have issues though with restoring apps via Titanium. It took extremely long and then it complained about missing apps. The data was available but not the app itself.

Anyone else, or is it just me?

[MENTION=520205]gtxaspec[/MENTION]: How do you make the ROMs? Do you do a a clean ROM install without Allapp.pkg, followed by a custom recovery install, followed by a zip-flash Xposed, and then take a nandroid backup or so? and sign it with test keys?
[FYT Android Head Units] PoppaRoxie1986:
I encountered the really long time to restore apps using Titanium. I only restored missing apps with data in the hopes of it being faster. I am going to use Titanium to create a TWRP flashable update.zip from my backup and see if it's faster.
[FYT Android Head Units] gtxaspec:
New joying update released today. Will rebase rom around that
[FYT Android Head Units] ste2002:
Can not find it both on carjoying and youtube. Could you please share the link?

Edit: found it, sorry: https://www.youtube.com/watch?v=uzI6xCJz78o
[FYT Android Head Units] olivier2591:
Hello Gtxaspec,

thank you for your work

very interested in your project, is it possible to put the link of your installation video of your rom?
[FYT Android Head Units] gtxaspec:
[youtube]NrHVJJ72qQA[/youtube]
[FYT Android Head Units] gtxaspec:
Titanium always takes a while to restore all of my apps. I will time stock vs custom gtx.

I use the "kitchen" method to build the rom:

I take the factory 5009_60 zip, extract it, make changes to it, like merge in Xposed and other apps and make changes and re-zip.

No signing needed since we flash using twrp. Infact we add checks to the update script to ensure it only is able to flash in twrp.

During installation, the update script grants the proper privlidges and contexts to the file system.

The nandroid method never worked for me properly so we don't do it. We make a factory style .zip that installs
[FYT Android Head Units] dyabolikarl:
Did you say there is a NEW JY rom? I want to install this as i have massive issues with my bluetooth and obd adapter so it's hard to update. But if there's a new rom maybe i will wait until you update your rom. Super keen for your rom.

I assume your rom also has the full BT stack so I can use my adapter with rolling pairing pin?>
[FYT Android Head Units] surfer63:
[MENTION=520205]gtxaspec[/MENTION]: You asked about the build.prop settings Yesterday.

It might be good to add:

persist.service.bdroid.ssp=true

to enable the paring popup for BT devices which Joying removed.
[FYT Android Head Units] pwood999:
I've been watching these threads with interest, but not quite ready to dive in yet.

One question: Why is "face detect" in there ?
[FYT Android Head Units] gtxaspec:
It's installed by default on opengapps for face unlock which works with your camera on a tablet or phone. Technically our head unit is considered a tablet device. The build prop disables it anyway, as I didn't touch the opengapps installer script.
[FYT Android Head Units] dyabolikarl:
Nevermind :). I am stupid.
[FYT Android Head Units] gtxaspec:
Any Russian users willing to help translate custom to Russian? Would like to include some of the guys at 4pda to use the ROM
[FYT Android Head Units] ste2002:
Sure there are going to be some, stand by :).
[FYT Android Head Units] m1john:
it can be done?
[FYT Android Head Units] surfer63:
The original gpsspeedfix contains a bug in the "GPS bearing" (the direction you are moving to). The new JET apk (just released) contains the fixed version. The GTX rom has the gpsspeedfix installed as system app which prevents a normal replacement/update. The new JET apk can now overwrite/install that one.
[FYT Android Head Units] PuntoGT16VT:
Perfect :good: :victory:

I will test it tomorrow.
[FYT Android Head Units] DBestman:
Question: Why doesn't [MENTION=2550900]surfer63[/MENTION] 's Joying Extra Tools come preinstalled with this ROM?
[FYT Android Head Units] tOz666:
Sorry to repost, is anyone else experiencing this?

Also, the bluetooth music app doesn't work well, it shows the song titles and can switch between them using the onscreen buttons, but no sound is heard.

I went back to joying stock january 2018 ROM and all of the above is working ... well I still have car settings in English and not in Spanish, but that's OK.
[FYT Android Head Units] luciusfox:
How come you guys didn't submit a pull request with the change?
[FYT Android Head Units] gtxaspec:
I personally was waiting to test, the original modification done was producing some errors on the logcat regarding the math. I don't have my laptop with me as I am at work so as soon as I test it I'll report back and issue a pull
[FYT Android Head Units] olivier2591:
hello,

Excellent rom, fast and serene, I use it with the FCCcar launcher.

This launcher uses a single player widget for all music player and radio.

Intel sofia unit is a little complicated to manage the radio. In the original rom an application is used to have a radio widget.

Today in your rom this widget / application doesn't exists. For testing I will need to re install this application. what is the name of this application and is it possible to install it manually on your rom?

thank you
[FYT Android Head Units] tOz666:
Last time I added the Radio widget, it was grouped into the "Weather" category. So my guess is that you need to reinstall JY-1-C9-TimeWeather-V1.0 from the original ROM.

You should obtain it from the original ROM and maybe install it as system app... don't know if other steps are needed.
[FYT Android Head Units] olivier2591:
ok i will try.

thank you for your answer ... so fast !! ;)
[FYT Android Head Units] x3rb3ru$:
Anybody know the links to the downloads of the official Joying firmwares (blog 59)? Looks like the joying site and forum have been down a couple of days and wanted to test this rom but I'm still on the october firmware so I need to update that first...
[FYT Android Head Units] derschnelle:
Yeah you're right, I usually use this: https://www.carjoying.com/blog/joying-head-unit-after-sale-support/59.html

Link, but it's still down...

Maybe I have the December version somewhere on my hdd, I could check this evening.
[FYT Android Head Units] myxcon:
Here you go, latest january update for MCU 25.05 rez 1024x600

https://goo.gl/H9q5fe

Give it some time to upload, slow mobile connection atm.
[FYT Android Head Units] farmerjohn:
You can find the links on Youtube (see description).

800x480

https://www.youtube.com/watch?v=uzI6xCJz78o&app=desktop

1024x600

https://www.youtube.com/watch?v=Az7EkWPf-4M&app=desktop
[FYT Android Head Units] x3rb3ru$:
Great, thanks!
[FYT Android Head Units] surfer63:
I first thought that the user jvdv would create a pull-request (you specifically asked him)

Then I went on experimenting.

Why do you use 5 samples? You don't seem to use them or average them, only add them to mLocation (or maybe that is still my lack of understanding java)

Also the speed indication has a real lag: the speed change literally is approx. 5 seconds (with 5 samples) and approx. 3 seconds (3 samples) behind. From your Dashcam and my modification of it (I added gpx), I know that the NMEA measurements are taken 4-8 times per second. The gpx measurements 1-2 per second.

Are the gpx measurements already averaged based on the NMEA measurements?

Anyway: I already created a new version without the 5 samples (or 3) at all and when that one works, is faster and is stable, I wanted to create a pull request.

That's also what I mentioned on my fork and why I forked it: I want to experiment and possibly deviate if necessary.

But I like to have a "good change" before creating the pull request.

Edit: Also because I wanted to make a clean pull request. Due to my inexperience I created quite a few modifications (including those with errors), that I want to remove by forking a clean tree, make the "final" changes and create a pull request.
[FYT Android Head Units] luciusfox:
It actually *is* averaging them. Total distance over the 5 samples divided by total time over the 5 samples.

The thing about distance is that if you add up the intermediate distances between subsequent samples, it will more or less average out to the distance from the first sample to the last, that is unless there is a radical change in direction happening some time in the middle of it (which is not going to happen when you're driving on a road).

And as far as using them all, its a sliding window, all of the samples get shifted by one space when a new sample is received, which means that we may use only the first and current now, but next window will use what is currently the second.

It is very possible that 5 samples is too conservative, but the idea was that the longer the sample space, the less impact there will be due to errors in any particular sample.

It was understood by the 5 sample window that it would have a lag.

Now as far as the sampling rate goes, the GPS is operating at a rate of 1 Hz. If you use the adafruit GPS + rpi for dashcam, then that can be configured up to 10 Hz. Now that does not mean that there is only one NMEA sentence being brought in per second, but they will be brought in in a block of several different sentences carrying different data (the common data will all match).

You don't need to re-fork.

What you can do instead, is SQUASH the commits.

https://stackoverflow.com/questions/5189560/squash-my-last-x-commits-together-using-git

That will reduce a heap of ugly commits to a single "overall" with all the mess cancelled out.
[FYT Android Head Units] surfer63:
Just created a pull request.

The version without the averaging is not yet added. I did a quick 10 minutes test this afternoon and it seems to work OK, but it needs some further testing.

There is minimal lag when accelerating. I guess that a sample per second can create some lag when aggressively accelerating (which I normally never do, btw)

There is some lag when decelarating.
[FYT Android Head Units] vitaliy_1508:
Firmware for MCU YG

I have mcu YG. how do I flash this firmware to not have the red label? Native firmware Joining costs December 2017. I changed the manufacturer code in the file FYT.PROP and installed the firmware. and here is how it is implemented?

Thanks in advance.