yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] gustden:
The home screen issue has always been an issue for my unit with the google app. I always install Nova launcher and make sure it is setup before installing the google search app. I believe that the Joying launchers 1 & 2 also work ok with the google app, just not the launcher 3 ( which they default to ).

I did some more investigation of sound issue and it looks like google maps using the 'media' stream which is being muted when playing on radio, as [MENTION=5110928]p33t-r[/MENTION] mentioned.

I have let Joying know the issue with google maps not "speaking" during the radio is still present on the May 12th update, and gave them this information.
[Android Head-Units] dayanandgp:
After changing the settings.apk via script, my unit resets the data every time I do a restart and I lose all app settings.. . Sigh... Frustrated as hell...
[Android Head-Units] edit:
I set up Nova Launcher and I use Titanium backup and freeze launcher 2 and 3.... and only after that I install Google app.... to avoid potential issues.
[Android Head-Units] dpredster:
For anyone having issues with Joyings launcher and google apps there is a workaround. This fix works by editing the config.txt file in the joying update. You need to do this before you update the firmware. It seems that the default launcher is selected based on the name n the config.txt (example ro.fyt.launcher=com.android.launcher4 sets launcher 3 as the default launcher). All you have to do is change this line (example to make Nova your default launcher replace that line with ro.fyt.launcher=com.teslacoilsw.launcher). I have testes this and it works

To set launcher 1 as default use ro.fyt.launcher=com.android.launcher2
[Android Head-Units] BassRareba:
Can anyone update the settings.apk for the latest patch? I confirm that it's not working anymore :)
[Android Head-Units] jodybgoode:
I cant connect my OBDLink LX it always says pin rejected. I even tried to pair without a pin.
[Android Head-Units] wrx216:
I have the MX version with setting the password to 1234 it works fine , just in case make sure your car is on not acc ?
[Android Head-Units] thedru13:
Can anyone help me out... I updated was running the April 6.0 update and yesterday Ran the new update. I got an error and run just the mcu file and then tried to run the update again and I keep getting this error.
[Android Head-Units] peeterc:
My USB ports are no more visible in the file manager nor in the music player. I tried to reflash the firmware and I had the same error. I wrote a message to Joying hoping they fix it. Anybody else had trouble with USB ports after updating to May 12th firmware?
[Android Head-Units] thedru13:
Hmmm I wasn't using the USB port. Was using the card slot. Maybe I will try the USB and see if there is any change. I heard back from Joying but they gave me an odd response. "Please try USB cable or SD Card"
[Android Head-Units] KlaverBoer:
Just insert the microsd card in the other slot.
[Android Head-Units] edit:
Wrote about it here

https://xdaforums.com/showpost.php?p=72192975&postcount=220

Screenshot of the error and everything...
[Android Head-Units] peeterc:
I have only one SD slot in my unit and I can't see the USB ports anymore.
[Android Head-Units] BassRareba:
Solved
[Android Head-Units] gf4tiu:
I've got the same issue. I had the first Android 6 update and wasn't able to update to the 12th May update anymore via USB, so I've used the SD-Card slot and it worked.

But now the CAN adapter doesn't work: no steering wheel control, no clima/door activity on screen. Should I do a MCU update (how?)

Another issue, but I think I've read something about this: There is no bluetooth point in the settings. I'm able to see the device via my iPhone and then the Bluetooth symbol appears in the bar on top - is this a bug or a feature?

Thanks!
[Android Head-Units] shanetrainST:
Try go into the factory setting and set your car CanBus again.

Advance setting password - 8086
[Android Head-Units] peeterc:
There's a file on Joying website to update the mcu only, but it doesn't do the trick. The firmware cannot be reflashed because the error and Usb ports are no longer available, it seems that the OTG function doesn't work anymore. My steering wheel controls still works fortunately.
[Android Head-Units] thedru13:
Only have one slot.
[Android Head-Units] edit:
Then you are out of options I am afraid... talk to Joying but I don't think they can help.... maybe send the unit back for repairs or buy a spare part to replace yourself...
[Android Head-Units] thedru13:
Sigh that really sucks.
[Android Head-Units] mancavetoyz:
what is the difference between the 6.0 to 6.0 update on the 11th versus the one posted on the 12th...the files are much larger on the 12th version. im only wanting try it out since my unit is very laggy since the update to 6.0. bluetooth sucks, apps hang and freeze inbetween screens.
[Android Head-Units] peeterc:
I found a solution that worked for my unit. Format an Usb pen drive with the tool SD formatter from sdcard.org. Then copy the firmware files 6.0 to 6.0 and put the drive inside Usb Port 1 (the 2nd doesn't work) and you will able to reflash the firmware. I don't know why but usb drives formatted with that tool are recognized by the system and old ones not.
[Android Head-Units] thedru13:
Awesome. I will give that ago thank you.
[Android Head-Units] windowsdan4216:
You take the settings .apk out of what ever firmware you have downloaded from Joying ... it's in the zip file under system=>priv-app=>settings

Make sure your folders are set to 755 and the settings.apk is 644

I had this happen too ... if you copy over the settings.apk and set all the correct permissions and then do a factory reset (I know it's drastic) you'll find everything works fine again.

Funny thing is that after a factory reset you still have the full settings.apk ... it doesn't revert to the old one!
[Android Head-Units] thedru13:
So formatted and popped it in the USB slot. It's updated. So thanks for figuring that out. Really appreciate the help. Hopefully the update doesn't brick the unit. :)
[Android Head-Units] dayanandgp:
I got too frustrated and simply updated to, 12th firmware without settings apk update. Apart from split screen is there any other way advantage for doing this update?
[Android Head-Units] thedru13:
Well it sort of worked. It updated but was different from the other updates. Home launcher isn't working right and when I reboot I keep getting this every time I reboot
[Android Head-Units] windowsdan4216:
You have the same problem as:

https://xdaforums.com/showpost.php?p=72290267&postcount=334

Factory reset will sort it once and for all. Stop it from doing that every reboot.
[Android Head-Units] naplesbill:
Perform a factory reset now from settings.
[Android Head-Units] windowsdan4216:
If you require accessibility settings for apps like Tasker or if you use VPNs then all of these settings are not available in the default settings app ... among many other things.
[Android Head-Units] edit:
I've installed my Android 6 unit into the car and replaced the previous unit (another Chinese unit ) and realized that the sound quality is not as good. I started to fiddle with Viper4Android for an hour at least with the engine running (waste of fuel).... no matter WHAT I tried the EQ section from Viper4Android seems to do very little the the overall sound... I had a hard time hearing the difference. I remember that some of the users from the android 5 thread telling me why I bother with Viper4Android because it does not improve sound so much... and they were right... on my old unit the difference was HUGE after I installed Viper.

So I took the old version of Viper that I was using on my old unit meaning "ViPER4Android_FX_A4.x.apk" and replaced it into the install script.

WOW ! The difference is HUGE once again. Guys the EQ works and you can hear the difference from miles away.

So the ViPER4Android_FX_v2505_A4.x-A7.x.apk that was used previously has some major problems and the EQ is pretty much dead, yeah, there are things that work alright like Viper Bass, Viper Clarity and so on but not the EQ and the EQ is a BIG part of the Viper and sound.

Can't stress enough how big the difference the EQ brings. I am glad that I brought the good sound back. I am still testing the Viper4Android but it looks that it is working ok even if it was made a while back and the compatibility might be not so good.
[Android Head-Units] dominicanodcora:
Can you post the link to the old viper4android apk.
[Android Head-Units] edit:
Ok, I Googled it for you :

1. from the official Viper4Android thread : https://xdaforums.com/showthread.php?t=2191223

2. take the following version off the page quote "v2.3.4.0 (Android 2.3~5.0)" mediafire link next to it : http://www.mediafire.com/download/cnqqdme51qy9ft4/ViPER4Android_FX_v2340.zip

3. Inside the zip file there are 2 files but i used this one as I mentioned before : ViPER4Android_FX_A4.x.apk

4. rename it, insert it in the right folder and run the script and tell me if you are happy with the results or not
[Android Head-Units] dominicanodcora:
I know where it is but as expected I downloaded the wrong file. I downloaded 2.4.0.1. I will download the correct version now and follow your instructions. Thanks.

---------- Post added at 05:19 PM ---------- Previous post was at 04:33 PM ----------

how do i start the driver proccessing?
[Android Head-Units] edit:
In the Android 6, 12 May Firmware they REMOVED the ability to set how low the brightness will go at night mode.

Out of the box, the low brightness setting (night mode) was set to 70% and for my eyes it's very bright so the menu allowed me to turn it down to 5%, and in some instances I even that considered not to be low enough and used additional software to lower the brightness even more.

So the brightness slider will now will only go from 70% to 100%... so why remove that beats me... they correct some things and break other things... oh man.

I tried to replace some files with the files from the old firmware but without luck ( I replaced the SYU-2-C9-CMSettings-V1.0.apk)

I've reflashed the unit for nothing, the high brightness at night it's a deal breaker for me... now I have to go back to previous firmware

---------- Post added at 09:24 PM ---------- Previous post was at 09:22 PM ----------

After the reboot you launch the app (you need root) and let it install it;s driver, reboot, enter settings, lock the headphone profile, customize the EQ from the headphone profile enable the profile and tell me if you are happy
[Android Head-Units] dominicanodcora:
i had the latest version working no issues. but i wanted to try out the louder eq. i thought it was the phone speaker i had to customize. i will try to custmize the headphone profile.

---------- Post added at 05:51 PM ---------- Previous post was at 05:42 PM ----------
[Android Head-Units] edit:
I don't know what happened in the latest version with the EQ section of the app but it's broken. But since no one commented anything in this thread I guess very few use the Viper4Android or they used it and they were let down by it and moved away from it. To be honest in the old version the EQ sound boost is HUGE compared to the latest version... Don't understand why.

I have to go back to Android 6, May 8th firmware because you can set lower brightness in the Car Settings app.

The go to app for me it is the : https://play.google.com/store/apps/details?id=com.haxor&hl=en

Simple and effective. There are many in the app store, I am sure that there are better ones but this is enough for me.

It would be nice to find an app that dimms the screen slowly as the sun sets (location check via GPS)... but that's an quest for another time.
[Android Head-Units] bogdi1988:
What settings do you use in the app?
[Android Head-Units] edit:
Disclaimer : All the settings that I will post are tailored to my speakers so most likely it might not work well on yours

1. locked effects mode to headset (has the most settings)

2. EQ graph set like on in the picture

3. Spread Spectrum - ON and set to 0.7

4.. Viper Bass - Natural Bass, set to 80hz and +8db (or +10db when I am in a more bassy mood).

5. Viper Clarity - 3.5db

More info:

The old app is not x86 optimized so it's currently under testing to see how it behaves, so far, in the last 2 days it was ok.

When run the app for the first time and it's installing the driver, have patience, android offered to kill the app a few times, it considered that it was stuck, have patience and click "WAIT", let it finish, it takes a while.

My setup is more bass driven because I like to have a good amount of bass at low ( and very low) sound volume, I rarely crank up the volume above 20.
[Android Head-Units] dominicanodcora:
i live in the city and i park in the street. sometimes far from where y building is. so it's hard for me to play with the radio. i will check when i have time and play with it. i notice when i run the script it fails.
[Android Head-Units] edit:
If you don't tell me the specifically error/s you encounter I am sorry but I can't help you.
[Android Head-Units] dominicanodcora:
once i get back home i will copy and paste or take a screenshot. my laptop battery died last night.
[Android Head-Units] windowsdan4216:
[MENTION=3076686]gustden[/MENTION]

I can't seem to find the Sofia Server NO KILL with Google Voice on src apk for the may 12th update?? Is this available somewhere, if not does the May 8th one work with it?

Thanks
[Android Head-Units] edit:
Here : https://xdaforums.com/android-auto/android-head-units/joying-2gb-steering-wheel-key-t3543390

scroll down to the end of the first post and pick the "V6.1-Sofia-1-C9-Server_NOKILL_GVS.zip"
[Android Head-Units] windowsdan4216:
It's says updated for 8th May base not 12th May?

Does that matter? I'm on 12th May release
[Android Head-Units] gustden:
I have not upgraded to the May 12th release or even looked at it yet. The May 8th release is working well for me, so I was going to wait until the next update before upgrading. I don't have time to install and update if they make a release every few days :(

My guess is it would work, but I have not tested it.
[Android Head-Units] edit:
I would say no but i haven't test it to be 100% sure.

My advice is to rename the original file (add an .old to the apk extension ) and leave it there and copy the moded file and give it the proper permisions... test it... if something does not look right delete the mod and rename back the original file)
[Android Head-Units] dayanandgp:
I can still change brightness to lowest... For me setting is as before

---------- Post added at 07:14 PM ---------- Previous post was at 07:12 PM ----------

It works... I am 12th and script runs fine with launcher. Sh
[Android Head-Units] vinhZ:
Velvet.apk breaks sleep

It looks like velvet.apk is breaking sleep mode in android 6. I deleted it and sleep works again :(
[Android Head-Units] Astur_Torque:
I thing I'll keep 5.1 till the 6.0 be mature enought
[Android Head-Units] dpredster:
Does anyone know what the Dormancy Setting does?
[Android Head-Units] bogdi1988:
Dormancy sets what the unit will do once you turn off the engine and ACC.

Dormancy ON -> unit goes in standby. Resume time -> 1-2 sec

Dormancy OFF -> unit turns off. Resume time -> 30-40 sec, pretty much a full reboot

For all other folks - have you noticed that in 6.0, the dormancy settings have changed? It is like this now:

OFF -> turn off

ON -> standby + turn off. I am assuming that after a pre-determined time, the unit will physically turn off to save power.
[Android Head-Units] dpredster:
I noticed that.
[Android Head-Units] vinhZ:
If anyone removes velvet.apk , it resets your permissions, go to setting,apps, google apps, permissions, enable your permissions. This will bring back okay google from google app screens and google maps.
[Android Head-Units] edit:
Please don't post information this vague because It will not help anyone. Be specific, bring up details.

In fact I since you brought it up I will be more specific for you.

For those of you who bright screens bother you at night this is what you NEED to know about the changes:

- In firmware of 12th May they removed the "Backlight current adjustment" from the Car settings app. (picture attached)

- I discovered that they moved the option to adjust the night screen brightness level to the Settings menu, Display section (picture attached)

- if you are like me and replace the Joying "Settings.apk" with the android one you will not be able to access this menu or modify the brightness for Day mode and Night mode and that's a real problem

- the BIGGEST problem is that EVEN IF you turn down the brightness (to 0) from Settings... it will not go as low as in the firmware from 8 May

- I've done some testing : 8 May firmware build, brightness turned down to 0, measured in Google maps, the screen brightness has 14-18 Lux, 12 May firmware build, brightness turned down to 0, measured in Google Maps, the screen brightness has 85-90 Lux... quite a big difference. What I learned from past versions is that the brightness can go pretty low (not low enough for me but that's another story) and I want it back. I wrote to Joying but I don't have high hopes, these subtle issues are rarely solved.
[Android Head-Units] nyogtha:
I can't document this, but for me, it feels like internet usage (google play, navigation, streaming radio ++) has become much slower with the upgrade from 5.x to 6. I use wifi-tethering through an android phone that's always in my car. Has anyone else experienced this?
[Android Head-Units] edit:
Have you tried an wipe after the update or have you done one before the update?

In my case after the update the unit was unbelievably slow... I had to wipe and reinstall, reconfigure everything.

After that it worked great !
[Android Head-Units] dpredster:
I noticed after the update my Max CPU frequency was 600. In my case that was the reason for it running slow.
[Android Head-Units] nyogtha:
I didn't wipe, as I thought the upgrade did that anyway, but I'll give it a go :) I'll check my CPU freq. as well. Thanks!
[Android Head-Units] edit:
My advice :

1. backup data if you must

2. wipe/clean/format/reset everything - make it clean just like you got it out of the box, no apps or data on the internal storage

3. update or reflash firmware

4. wipe again

5. install / configure everything back

This way the unit should work fine.
[Android Head-Units] BassRareba:
Maybe i've the same issue.

Does the screen turns black suddenly?

Today is happening continuously!

No matter if i reboot or turn off the car the screen remains black.

Sometimes it returns to a normal state but after a while it returns black again.

If this is the case how did you manage to remove velvet.apk?

Where is it located?
[Android Head-Units] windowsdan4216:
All working correctly on 12th May update. No Kill fine and Google search too :laugh:

The settings replacement .apk works too!!

Very happy that all is updated and everything working correctly ?
[Android Head-Units] BassRareba:
Do you have a link to the settings.apk? :)
[Android Head-Units] vinhZ:
This doesn't have anything to do with your issue. You seem to have an hardware issue. Contact your seller for options/ you should be covered for 2 years. The only painful part is sending them the old unit.
[Android Head-Units] BassRareba:
Mmm...i prefer to try anything that's possible :)

It's an issue i have since the May 12 firmware update so MAYBE i should try to roll back to the 8th May.

I really hope that's not an hardware issue...i don't want to stay without a radio :(

---------- Post added at 05:02 PM ---------- Previous post was at 04:54 PM ----------

Mmm strange...i tried to turn on the unit now and everything was fine.

Could it be that the heat from the sun caused the screen to malfunction?

I've a convertible Alfa Spider and today at noon the temperature was 30-35 degrees...
[Android Head-Units] edit:
Can't talk about the Joying units because I installed mine only for a week but my previous Android unit was able to work fine when the car interior was at 60-65C after a full day in the hot summer sun.... also ran fine in the winter at -20C.

Having said that 30-35C is nothing to worry about. Your issue seems to be more hardware related (screen)... Write to Joying, tell them you problem.
[Android Head-Units] windowsdan4216:
It's in the 12th May update you downloaded from Joying.
[Android Head-Units] CadillacMike:
i was feeling like this too. That and my dormancy has basically quit working.

I think I will do a full reset, then install the May 12th 6.0 to 6.0 update
[Android Head-Units] edit:
What firmware are you currently on? The first release or the one from the 8th of May?
[Android Head-Units] dominicanodcora:
anything wrong with using poweramp eq?
[Android Head-Units] edit:
Viper4Android it's better in my opinion but the BEST feature is that it's sound correction abilities applies to virtually every audio/video app that you use in android... even for BT streaming... one exception that comes to mind would be the FM radio :)

Of course there is nothing wrong with using PowerAmp EQ... if you are using only PowerAmp and you are happy with it.

I am using various apps, Deezer, XiiaLive, PlayerPro, Youtube, Pocket Casts, Soundcloud and thanks to Viper4Android I have the same good sound from all of them no matter the EQ capabilities of the apps.
[Android Head-Units] naplesbill:
Do you know if it works on auxiliary audio in?
[Android Head-Units] xdamember2:
Would it help to modify the sofia server apk, and prevent muting of the media stream?

Edit: I added a line of code so nothing is muted, now I can hear Maps while the radio is playing. It still mutes the radio while Maps is speaking so that must be happening somewhere else.
[Android Head-Units] Cegomez1:
I'm trying to update from 5.1.1 to 6.0 and am getting the error "OTA and APK must update same time!" I see the fix for this when re-flashing 6.0 but what about upgrading from 5.0?
[Android Head-Units] bogdi1988:
Anyone experiencing after each standby that the location is turned off on the device and there's a prompt to re-enable it each time?
[Android Head-Units] CadillacMike:
that's what I'm looking for
[Android Head-Units] surfer63:
Just did some checks without flashing by examining the apks itself.

- SofiaServer is indeed missing all most improvements

- busybox is still the older, buggy, less complete version.

- USB audio policies still completely missing

- 6.0 Bluetooth app layout completely identical to 5.1 layout
[Android Head-Units] AssassinsLament:
audio_policy.conf now supports usb dacs without modification. Someone was paying attention to us! Although we still have the volume control issue.
[Android Head-Units] surfer63:
You are right. I checked the wrong one from the previous release (constantly switching folder in two windows).
[Android Head-Units] gustden:
I haven't seen this issue on my unit on either release. Mine are still black text on white bar.
[Android Head-Units] bogdi1988:
I have seen on some notifications on mine. Example: Youtube or Youtube Music.
[Android Head-Units] Astur_Torque:
There isn't any +7.0 compilation for x86 architecture, as far as I know
[Android Head-Units] AssassinsLament:
Google App still bugs out joying launchers but the good thing is that Google now responses are now heard without any modifications!
[Android Head-Units] edit:
I sit and wonder if upgrading from 5 to 6 would bring us any benefits...

Let's set aside the Chinese buggy apps, can you guys please explain why is worth having 6 over 5?

Thank you !
[Android Head-Units] naplesbill:
One was just mentioned. Google voice response without hacking.
[Android Head-Units] edit:
I would not call that benefit... yes, having it out of the box is nice, I don't deny it but It's not like we did not had it before...

I would expect a benefit something we did not had in 5.0.1... an extra... an bonus feature... something.... anything :)