yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] edit:
Nope, they can't get it right at all... the issues with BT at least were terrible from the first release... but there were others as well...

Some of my issues :

1. I lost Viper functionality - the Viper functionality got worse and worse and it's unusable on the 1 Sept, the last firmware that I have tested

2. I've lost system stability (sleep issues) - On Android 5 I might have seen the unit shutdown maybe once in a month... I am on 7 July and it shuts down once every 5-7 days without any real reason (using the same apps and settings as on android 5)

3. BT tethering speeds were cut in half - very sad if you use apps like Deezer that loves to cash songs a bit in advance for uninterrupted play

4. phone BT connectivity issues - depending on the phone (model, brand, firmware)

5. Google Maps issues - stops reacquiring satellites position, requires HU restart, very annoying, solved on 1 Sept firmware apparantly

6. Google App issues - audio does not fade out when you need to voice search something in Waze/Gmaps- solved on 7 july

7. Sofia NoKill custom keys 2-3 seconds buttons lag on android 6 that wasn't a problem on android 5 - [MENTION=3076686]gustden[/MENTION] improved the mod for 1 September firmware and removed the lag for media buttons BUT the lag remains for the rest of the buttons, unfortunately he did not revisit the older mods to rectify the problem... and he is not going from what I can see. Using the latest mod (v6.4) on other firmware versions does not always work. I tested it on 7 July and resulted on units failing to sleep during 30 hours and shutting down instead... very annoying.

8. You can't install the Google Asistant so you can "ok google" from any app or screen... worked fine on android 5... on android 6 break the HU sleep

With all the issues, all the testing, all the wasted time, all the flashing, the instability, unit wiping, car dash disassembly/reassembly to take the unit out, bugs... there isn't a day that goes by that I am not feeling sorry that I've "upgraded" - dumbest move on my part.

Went from a very stable and functional android 5 where all my apps worked fine to an android 6 plagues with issues some that will never go away (like Viper functionality)

It's true that If you don't use additional apps like (XiiaLive, Deezer, Viper), you don't want to customize it (like replacing apps or launchers) and you use only the stock apps you might find the HU perfectly fine on Android 6 like it used to be on Android 5.
[Android Head-Units] jaapsander:
So guys,

I recently got my Joying HU. I got it hookup up to a pc PSU so I can play with it and test the functionality of the unit before installing it into my car. I've read the Roll-up thread (mostly) and the "all you need to know with micro-tutorials" thread, but both topic starts are kind of outdated with the recent changes in the ROMs from joying. Is there a quick summary of what to do with a new joying (I got the JY-UM135N2D). Should I install the latest Joying update (I'm on the 5 July version atm). Which mods are working and mandatory for a "good" functioning unit?

So far I've rooted the device installed Surfer63 his extra tools apk, enhanced multi-pairing BT Mod (from Treel), Bluetooth tethering apk (ibdroid), update for busybox and rsync. I can't find viper4adroid (I know it doesn't work on the newest update anymore, but how about the july version?)
[Android Head-Units] Jaihoidundso:
Have anyone tested the acutally firmware from 15th december?
[Android Head-Units] ste2002:
A couple of mates from my local (non-English) forum did December update and reported no issues whatsoever. BT, they say, now OK (streaming music). Still just a couple of days, not much experience.
[Android Head-Units] Jaihoidundso:
ok than I will test it too.
[Android Head-Units] edit:
By any chance did they test Viper on the latest firmware? Does it work?
[Android Head-Units] ste2002:
Asked about Viper on Dec'17 FW couple hours ago - still no news.
[Android Head-Units] surfer63:
And the 4 km/hr speed step bug. Has that been solved? Meaning that speed steps in the GPS go per 0.1 km/hr instead of 3.6 km/hr.
[Android Head-Units] Jaihoidundso:
Hey, Viper doesn't work correctly. But i forgot to test the speedbug.
[Android Head-Units] dyabolikarl:
I might risk losing my odb to update ... it's the only reason on holding on to may... I know i can get my odblink to run on it.

Really need to get a second using for testing haha
[Android Head-Units] :
I tested and the bluetooh cutting bug was fixed, for me is the best firmware version.
[Android Head-Units] Jaihoidundso:
Hey i've tested the speedbug. And no - bug was not fixed
[Android Head-Units] surfer63:
Thanks for testing. I was already afraid of that.
[Android Head-Units] Jaihoidundso:
Hey,

INSTALL:

I've tried the install first time, and installation was corrupt. Now it's not started anymore, so I have to install new and it's failure again. Than I tried it again. Installation was successful. Set my MCU correctly and start to set up everything to my personality and tried known bugs.

SPEED-BUG:

I've tested the speedbug. And no - bug was not fixed. It's almost the same with 3.6 km/h - that's a pity.

BLUETOOTH:

I don't have any problems with bluetooth music, BUT with phone. It's like a stutter. So I've called me on my home telephone and test it on the mailbox. On the mailbox perfect speech.

CAR SETTINGS:

I found the new setting (is it new?) with Bluetooth Microphone Type: Front or Back. First I tried Back, but my mailbox doesn't registered any speech than. So i tried front and than it works. I have the external microphone from Joying.

BOOT LOGO CHANGE:

I don't know if it is new, but now you can set very easy a new boot logo from your storage. Create a new directory named "mycar" (without ") on a root directory from a sd card or usb storage and put in your pictures (1024x600) and set it over the "Car Settings" App.

VIPER4ANDROID:

Because Viper4Android doesn't work (what a wonder -.-), I used my "emergency solution" and installed "Viper4Arise" on my Oneplus 3T with Android 8.0 and paired it with the phone. That's a mileage difference as without Viper. And yes - the sound is very very good despite Bluetooth. Sure - it will be better, that the sound coming directly from the radio, but without bluetooth it's not (yet) possible.

Everything as a whole, it's a very good update and it's really better like the last firmware updates.
[Android Head-Units] kampfschachtel:
[MENTION=7011404]Jaihoidundso[/MENTION]: thanks for testing that.

Bootlogo change was always possible on Intel units, nothing new.

Was away for 4 month sailing and back now. I saw a lot going on and reading different threads with the Android 6 update but I cannot read all of them. Would need your advice please:

I need to setup my joying new. What is the best update on the Android 6 right now, so below must haves work or I have the highest chance they work?

Must haves: viper, bluetooth (to connect to OBD dongle, no streaming and no phone BD, I dont care), the simple nokill mod, realzoulou dab+ app, xiia-pro app Radio, spotify, google maps and surfers63 joying extra tool. Means I need to definitly root my joying.

don't need: google voice, BT for phone (that runs directly via Audi OEM BT into my DSP) and I don't stream via bluetooth

thank you
[Android Head-Units] Jaihoidundso:
Viper: No chance. On Android 6 there is no good working. The last good firmware I think is the may firmware. Correct me, but I think July isn't work anymore. Bluetooth should be work for ODB (but I don't need it, so i can't tested), no kill mod I think doesn't work with newest firmware but you have to ask surfer63, if it's working on november rom. the dab+ app always works, but i don't use it often, because my signal isn't very good from the external antenna. I use Deezer, and this works fine. My launcher is CarWebGuru and works good with Deezer and (people said) Spotify too. But the only thing what is pure sh**, that Viper doesn't work..
[Android Head-Units] kampfschachtel:
thank you for your answers:

my unit is on may release and viper plus most other stuff worked ok till I tried to use Automate....that screwed everything up.

where do I get the other update releases may till ocotber, joying deleted all beside the last 15th dec update?

I use Xiia, Dab+, spotify or music from stick in this exactly this order.

google map as nav

via OBD Dongle: Carly for VAG/Torque Pro

automate has a genius default driving modus of google maps which shows in switzerland the banned/forbidden version with all fixed or semi fixed flashers (speed&redlight), thats why I would like to use it but it screws everything up, especially BT connection and stability of the whole system.

is here somebody that has the know how to patch a viper version for the 15th december update together?
[Android Head-Units] edit:
I am using right now 7 July firmware and although it works with Viper I can't really recommend it because from time to time it breaks the audio a little.... but it's on rare occasions.

My guess is if Viper is a must like it is for me 25 May is the last firmware that we can use... I will get back on 25 May and test it more.

From what I remember the 25 May firmware does not work with Google app... if that's a negative for you... no voice search on Google Maps or Waze.

It's sad that we have no one skilled enough to solve the Joying issue with Viper... and because of that my upgrade path seems closed for me.... unfortunately.... very sad...
[Android Head-Units] gtxaspec:
What's the exact problem you are having with viper and the recent releases?
[Android Head-Units] swanie2000:
I had an issue where I had no input from either microphone. For me, the front built in microphone wires had been cut by the lid being replaced after I mounted a cooling fan on the lid. After repairing the front microphone, I was able to get input from the front only, and nothing from the rear.

Testing the rear microphone, I have read that some users report that the microphone plug on the back has a hard time being fully seated, or staying fully seated. I didn't find that to be the case for me. However, in order to eliminate that possibility, I replaced the rear microphone pig tale with a know working one. Then I ohmed across the connection from within the radio, all the way to the ceiling where the microphone was mounted, just to be sure. After I was sure everything was OK, and still didn't have any rear microphone input, I deleted the front microphone on the inside of the radio, and unplugged the rear microphone, and soldered it to the place where the front microphone was at originally. This gave me a working microphone on the ceiling of the truck, where it works much better than the front of the radio.

I don't know why, but my rear microphone port just went bad, possible after a failed MCU update? I mean, I shorted out the front port with the lid cutting the wires, and the front port still works. I have know idea why that would effect the rear port, but none the less, the rear port no longer works. Setting the microphone to the front port, and rewire the rear port to the front, solved the problem for me.
[Android Head-Units] edit:
With the recent releases they killed it for good but the problems started from the first releases of android 6 because on android 5 it used to work 100%.

As you know the Viper has different modules, the EQ, Bass, Clarity, Spectrum Extension, Dynamic System... in Android 5 all worked fine... from the first release of android 6 the EQ stopped working but others worked... lately the mode modules you enable the worse the sounds gets.

When you enable the Viper EQ no matter the android 6 build the music is playing at 0.75x speed or slower. If you use a lot of modules but not the EQ the sound stutters and the speakers are popping.

The odd thing is when you are touching the screen... scrolling in a direction (random), no matter what's happening on the screen the sound is fine NO MATTER how many modules you enabled in Viper... so as long as you keep scrolling the sound is fine.

The thing got worse and worse with each Android 6 release (build)... so I stopped at 7 July and I can barely use 2 modules, Bass and Clarity (and with those 2 at times I still have some popping but it happens rarely)... if I dare to enable 1 more module like for instance Spectrum Extension the popping starts.... I think I need to get back to 25 May... but as I remember the Google App was not working for 25 May (and I frequently use voice search for Waze and Google Maps and web)... so I need to compromise for the sake of the sound... I hate that.

I desperately asked for help left and right... mostly did not answer and those who did advised me to raise the clocks to max... all the time... I don't know how to do that and I did not do it... All I did was launch Waze that usually raises the clocks at 1200... but it did not solve the problem. Also I was advised that the Viper might not get the priority that needs... but I don't know how to give it the proper priority... Bottom line... I did not get a simple solution (for a noob like me) meant to help me. I need someone with experience to see what Joying did to the firmware that managed to smash Viper functionality so bad.

As far as I know Viper is not so CPU hungry... It was working fine for years on a dual core (3066) that max clock was 1.1Ghz but I rarely seen it above 800 Mhz and I was regularly was using the same apps as I do now, Music player (Poweramp/Xiia/Deezer) + Waze + Viper

If you are so kind to find a FIX... I would gladly donate for it !

I just want a functional and stable Android 6 build but it seems that I can't have that... I got so tired and sick with the Joying Android 6 problems.
[Android Head-Units] gtxaspec:
I tried every module, and played with the settings. Worked fine. The audio problem when you touch the screen is a hardware problem, my first unit had that issue, I had joying exchange my unit, problem was not present in second unit.
[Android Head-Units] edit:
Impossible, I encountered this issues on 3 headunits. 2 mine (1 board busted) and 1 new that I got was warranty replacement and 1 friend that just got his unit and wanted to have Viper and suprise... he can't use it... same issues.

People on other forums (non english) are complaining of the same issues.... I have a hard time believing that on your unit just... works... what firmware do you have?

If that's the case how do you explain that with early firmwares the Viper still worked (limited functionality, it;s true) and in the latest it stopped completely? (on the same hardware)

Please have a longer look at it, enable more modules, enable EQ, test for functionality, let it run for a longer periods of time.... I can't believe that it works for you... unless you are using one of your custom ROMs :) :) :)
[Android Head-Units] gtxaspec:
I am using custom rom. Will continue to test
[Android Head-Units] edit:
LoL.... i suspected that.

All my description applies only to stock Joying Android 6 builds....
[Android Head-Units] surfer63:
deleted. already answered.
[Android Head-Units] gtxaspec:
Custom rom, I was able to reproduce [MENTION=309187]edit[/MENTION]'s problems after 5 minutes of continuous audio playback. Looking into it.
[Android Head-Units] edit:
Thank you very much! If you find something please make the fix/patch available for the stock firmware as well.... I am sure many will thank you !

I will gladly donate if you show me where !
[Android Head-Units] kampfschachtel:
I will donate too.

Where can I get a custom ROM for our Intel Sofia units?
[Android Head-Units] surfer63:
See this post.

It started all here.

Note that you first need to install another recovery partition first.

I'm working on a script for non-rooted units and an apk for rooted units to make it slightly simpler.

I will test the script today.

(I have been without my unit for more than 4 weeks, and after 4 days again for almost a week. I just got it back).
[Android Head-Units] kampfschachtel:
Thank you:good:

There is light at the end of the tunnel:eek:

Is it possible with the custom ROM to install apps from app store like Spotify or xiia radio and the DAB+ app from real zoulou?

After installing custom ROM can I go back to stock 5.1 if I had 6 on before? Via a new recovery partition it should be possible to downgrade????

Installed may release yesterday so I have some sound in the car. Installed all apps that didn't need root but didn't root it till now. Till now I was able to connect BT dongle and run Spotify and Carly. But sound without viper sucks big time....

Went for skiing to Saas-Fee in the Swiss mountains till 3rd January. Will root mine afterwards and see what works and not....then I will decide if going custom ROM route.
[Android Head-Units] surfer63:
Google apps work fine and so is the Play Store. You can install anything you like.

It is still NOT possible to downgrade. It requires signature keys. gtxaspec started working on the 5.1.1 ROM partitions, but I do not exactly know for what reason. He got the partitions from Astur_torque, who is still on 5.1.1

Maybe it is possible from these partitions to fabricate a downgrade route.
[Android Head-Units] btrax:
Hey, I'm wondering if it was possible to do the same with the built in USB, do you have any idea?
[Android Head-Units] derschnelle:
What do you want to do with your built in USB?
[Android Head-Units] KlaverBoer:
You can follow the wires of the usb connector. I think they are connected to the quadlock connector of the radio. I am not sure because i don't have a usb connector installed. You can remove the usb wires from the quadlock or whatever connector and solder a male USB connector to the wires (just google for the wiring diagram). Then connect the new USB A male connector to one of the Joying USB female connectors.

I dont think there is a converter available. But correct me if i'm wrong.
[Android Head-Units] btrax:
Mhhh, playing music with an usb stick :)

I'm talking about this connector (yellow one): It has 4 pins in it

[IMG="Discover back"]http://i.imgur.com/H7p6mkd.png[/IMG]

For GPS there is a Fakra/SMA adapter, so maybe there is this kind of thing for the USB plug (4pin/USB male).

At the end, it will be plugged to the USB IN entry of the HU. So i can use the USB port of my car without passing any cable.
[Android Head-Units] surfer63:
This is about head units. You are talking about a completely different Volkswagen head unit. The answers you get hear do not relate to your VW head unit as everyone expects you have a Joying. I think you can better ask this on a VW forum.
[Android Head-Units] btrax:
The picture was just to show you the connector and the cable if somebody knew this kind of cable and if I can find an adaptation to plug it to the USB of the Joying. I have a Joying HU :)

Sorry but my english is bad so there was a misunderstanding :)
[Android Head-Units] Hilari0:
Googled "vw usb adapter" and a bunch of stuff came up. Here's one on ebay that might work:

https://www.ebay.com/itm/Volkswagen...arness-Cable-AUX-Adapter-for-VW-/161231017982

If not, google the same and look at the other hits.
[Android Head-Units] Slowdeath:
If someone using latest Marshmellow update of the Joying Intel Sofia 3gr HU could extract launcher as apk, I would be grateful.

Thanks in advance. :)
[Android Head-Units] alessondanilo:
It was my turn to install refrigeration on these products.

Unfortunately I'm having problems with welding, my screen goes black, but the touch works.
[Android Head-Units] edit:
I tried to update to 1 nov firmware but I get the mcu error. I have 5-25 MCU version and downloaded the firmware file accordingly.

There were some MCU files updates that you can download on their page but the links are dead now.

You guys only used the firmware file to update the unit or you had to update separately the MCU as well?
[Android Head-Units] markmorto:
Issue with frequent reboots with latest "no-kill" server

Hi:

First off I want to say thanks to Zwolfe for his"Joying Extra Tools" apk. I used it to root my head unit and it worked flawlessly.

I have the JY-Vl130N2 model with hardware buttons, running the December update, with MCU: 2017-10-25 19:20:05 JY_(_R76)__90_C9_7706_5009_CAN(All)_Newlap_AMP.

I was looking for a solution to the Joying Bluetooth controller not working after the system goes into standby. When restarting the app got it running, I figured the Joying server was killing the process and I needed the "no kill" mod.

I installed it (no kill only, no keys or launcher.sh additions) with Joying Extra Tools, and at first it worked great - my controller worked after coming out of standby and reboot, along with a speedometer widget I use that also needed a fresh restart.

The next full day of use, and afterwards, I'm having problems with semi-frequent reboots after over an hour's time (or always overnight) in standby, causing the unit to do a full restart with Android/Joying boot screen and all. A couple times it rebooted after a couple quick restarts (shopping at a few different places in an afternoon, for example). Each time I had a restart, on the following reboot, my saved Bluetooth connection with my phone was destroyed and had to be recreated. Restoring the standard Joying server fixed the random reboots, but I'm back to the original problem.

Is there something I'm missing in my setup that could prevent these reboots, or is it a known issue with the "no kill" mod?

Thanks upfront for any help.
[Android Head-Units] surfer63:
The "latest" NoKill version is actually the one for the September ROM, so it might indeed give issues. Quite some changes have been implemented between September and December.

You could use my apk to set back the original December version.
[Android Head-Units] markmorto:
Thanks. I did do that and am back to (rooted) stock right now. Any idea when the next update for "no kill" will be available?
[Android Head-Units] surfer63:
No.

I'm working on the xposed nokill module, but that one does not work correctly yet as I loaded 4-5 apps, and only the last loaded app was not killed. I'm still missing something.

This evening I did a quick nokill mod on the December SofiaServer itself based on @realzoulou's post.

Going to check that tomorrow.
[Android Head-Units] jcollins311:
The Dec update allows you to pick a microphone. Anyone verify this is working? I bought an aftermarket external mic in hopes i can forgo the hardware mods.
[Android Head-Units] ste2002:
I tried mic option on Dec FW - in one of two vague named settings my external Joying mic works OK.
[Android Head-Units] surfer63:
The nokill sofiaserver xposed module still doesn't work a 100%.

The direct nokill patch on the December SofiaServer works fine.
[Android Head-Units] markmorto:
Thanks. I'll give it a try today. Is that available from your tool, or should I get it from the link in the previous post?
[Android Head-Units] surfer63:
They both work now: the patched sofiaserver and the nokill xposed module. Note that this is without custom key mod.

I did not release my tool yet, so they are currently not available. I'm doing some more testing on other things as well.

Probably this weekend.
[Android Head-Units] edit:
With your xposed module can we selectively kill some apps... Like Waze for instance that likes to break after HU wakes up?
[Android Head-Units] surfer63:
I do not know the exact issues of Waze. I don't use it. Does it break on the nokill mod?

With the custom key mod (incl. nokill) by Gustden you have the pause and resume option. On the pause option, going into deep-sleep, you can give Waze a "am force-stop com.waze".

On the resume function, waking up from deep-sleep, you can do a "am start -n com.waze/.MainActivity". This will stop and start Waze, but not continue a route as you really stop waze.

My goal is to first mimic the behavior of the Gustden mod in the xposed module (if I ever succeed as I just started with java and xposed).

If that is going to work, I want to have some settings screen where you can add the same options as in the launcher.sh. But that is also for me wishful thinking.

Please check the QA thread by edit. As far as I know he said something about Waze as he is a Waze user..