yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] avnb39:
Darn decoys.. But that did work, thanks!

I'm also having a weird issue with Ok google everywhere. I installed the Google app from the play store, and my unit's language is in english, but the everywhere option is greyed out. I know some people were having luck with velvet.apk, but if that breaks sleep mode, that's not really an option. Is there any good solution right now? Any advice would be appreciated.
[Android Head-Units] surfer63:
I downloaded and unpacked two other x86 non-joying ROMs, one Sofia3GR-MTCD head-unit (other MCU) and one for the Asus Zen phone

All use the same libbluetooth_jni.so. The other two had the same config which is slightly different than the joying config. That could be becauce the MCU is completely different but I don't think so for bluetooth.

If I do a "ls -lR" (dir /s) inside /system/app/Bluetooth I get for the Joying:

.:
totaal 768
-rw-rw-r-- 1 root root 778659 dec 23 2014 Bluetooth.apk
drwxrwxr-x 3 root root 4096 jul 13 18:43 oat

./oat:
totaal 4
drwxrwxr-x 2 root root 4096 jul 13 18:43 x86

./oat/x86:
totaal 6452
-rw-rw-r-- 1 root root 6603244 dec 23 2014 Bluetooth.odex

and for the other two:

ls -lR
.:
totaal 3204
-rw-r--r--. 1 root root 3276771 jan 1 2009 Bluetooth.apk
drwxr-xr-x. 3 root root 4096 jan 1 2009 lib

./lib:
totaal 4
drwxr-xr-x. 2 root root 4096 jan 1 2009 x86

./lib/x86:
totaal 0
lrw-r--r--. 1 root root 31 jan 1 2009 libbluetooth_jni.so -> /system/lib/libbluetooth_jni.so

The other two miss the oat folder with the precompiled odex. That is not an issue because the odex will be created in the /data/app area in an "optimizing apps" step if it isn't in the app or priv-app section.

The point is that the other two have a lib/x86 folder containing a symlink pointing to the "/system/lib/libbluetooth_jni.so" library. In the joying ROM the library is of course at the same location, but the app folder does not contain the symlink. I have no idea whether that should be there. My gut feeling is that it shouldn't be necessary, but why do the other two have it? Does it really make a difference?

Edit: This is of course the system bluetooth.apk, not the Joying JY-1-C9-BT-V1.0.apk.

That could contain additional bugs.
[Android Head-Units] shanetrainST:
I also found it odd that the Bluetooth folder contained a symlink to a .so where as most others didn't?

I am very noob with Android, but I spend quite sometime playing around with getting the BT working better and didn't have much luck.

My last attempt was to replace the Bluetooth folder with one from another X86 but I don't think it liked the original Libbluetooth_jni.so

There is little of no information on the net for BT but what I did find was this

The files for all the BT system are

Bluetooth.apk

Bluetooth.odex

Libbluetooth_jni.so

Libbt-utils.so

Libbt-vendor.so

Libbt-hci.so

And if the system was running bluestack

Bluetooth.default.so

If only we can replace out the crap Joying placed in that crippled it, that would be awesome

Edit. Possibly replacing those file from the android 5.1 system might help correct it, but I would rather see it replaced out with something way more standard than the Joying junk
[Android Head-Units] surfer63:
Are you sure? Are you now looking at X86 Android iso images that can run inside VirtualBox, Bluestacks and the like? Or in real android phone/tablet/head-unit ROMs?

As far as I know these are the relevant bluetooth files on our units

./system/etc/bluetooth/auto_pair_devlist.conf
./system/etc/bluetooth/bt_did.conf
./system/etc/bluetooth/bt_stack.conf
./system/vendor/etc/bluetooth/bt_vendor.conf
./system/vendor/etc/firmware/bt/a11.pbn
./system/vendor/lib/libbt-vendor.so
./system/vendor/bin/bt_nvm_init.sh
./system/lib/libbtuscplugin.so
./system/lib/libbt-hcivsservice.so
./system/bin/bt_vendor_test
./system/bin/phonetool_btapp
./system/etc/permissions/android.hardware.bluetooth_le.xml
./system/etc/permissions/android.hardware.bluetooth.xml
./system/lib/hw/bluetooth.default.so
./system/lib/libbluetooth_jni.so
./system/app/BluetoothMidiService/oat/x86/BluetoothMidiService.odex
./system/app/BluetoothMidiService/BluetoothMidiService.apk
./system/app/Bluetooth/Bluetooth.apk
./system/app/Bluetooth/oat/x86/Bluetooth.odex

And of course the JY-1-C9-BT-V1.0.apk

The interaction between the SofiaServer apk and the BT apk with the MCU-board are a black-box to me.

This bluetooth issues should be a different thread. This thread is about the 6.0 update. It is now deviating too much.
[Android Head-Units] shanetrainST:
I have been looking at the X86 ISO android rom that can run in virtualbox.

Probably be better to use a rom from a tablet, but I have been unable to find a Sofia rom in 6.0.

That list is more comprehensive than mine, are u going to try swap those files and use another Roms files?

Agree this needs a new thread
[Android Head-Units] edit:
I emailed Joying many times asking for BT tethering... They answered politely that they will ask at the factory and that was it... I will keep emailing and insist on it...

Please email them too guys... Who knows... Maybe... Someday....
[Android Head-Units] shanetrainST:
74 emails and counting about BT related issues I have personally sent them.

Once u email them, they will ask the factory, then two days pass and u will get an email saying there is nothing they can do... that has been my experience with them.

I really hope everyone that's having Bluetooth issues emails them so they might do something.

If anyone is going to fix it, it's FYT and not Joying and so far they won't give me their email so I can ask the question.
[Android Head-Units] rknuette:
I did the update yesterday. Installed applications are still there after update, but all application data is gone (accounts, settings, map data of navigation software etc.). The device also got a new device ID again, which is annoying since traffice information in Mapfactor Navigator is based on the device ID and Mapfactor does not believe that an update can change the device ID.

I haven't tested other stuff so far.
[Android Head-Units] surfer63:
On every update it gets a new device ID and a new MAC address. It is really annoying.
[Android Head-Units] rknuette:
Does anyone also have a worse GPS signal after the update? Only tested in front of my house I've had a fix with 7 to 8 satelites before update, now only 3 to 4 (and the radio has been switched on the whole night due to GPS map download).
[Android Head-Units] TransAmMan:
I did the newest July 7 update. It's worse than the May 25th from what I've seen. I factory reset my radio, did the install, then factory reset it again. Bluetooth barely ever connects and if it does it's only for 30 seconds. Also the google maps fix they added made matters worse as well. It'll always work the first time after a radio reboot but if I turn my car off, then back on and use google maps again after entering the address and pressing "directions", the circle just spins forever. I never get the next screen to press "start". I have to reboot the radio then it works again. I'm going back to the May 25th update. It has issues as well but not this bad.
[Android Head-Units] Dvalin21:
I have emailed them like crazy, and still they don't do anything it. The Bluetooth.apk is absolutely flawed. It changes setting back to its original state without notice, still causes a bunch of air noise when there isn't any, and of you use google via voice command, it will not send the command to call someone to the phone......but the command can be sent to the phone. But if you email and ask them, they will just its not suppose to do that. Grrrr. Wishing someone would mode the thing and fix what apparently they can not.
[Android Head-Units] shanetrainST:
I would say keep sending them emails

I am sure they can fix it if enough people complain about the BT
[Android Head-Units] usa911g:
can we downgrade the F/W from 6.0.1 to 5.1.1???

I think the 5.1.1 is more stable than 6.0.1

and I think joying are unable to solve the bug, just sold out the product but no capability to solve.
[Android Head-Units] TransAmMan:
​

I agree. I too think 5.1.1 is more stable. I had zero problem with it. You can't go back, Joying even warned that. I've considered buying a 5.1.1 and just selling the one I have updated to 6.0.1.

---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------

The newest July 7 update has the worst bluetooth performance to date. My phone disconnects after about 20-30 seconds and never reconnects. Part of the problem is it seem to lose bluetooth settings if you change them. You have to change the password to 1234 for OBD2 adapter to work and after rebooting or just coming back to the car it defaults back to 0000. It wasn't that bad with the May25 update. Sometimes I had no problems, sometimes I did. I've been using it with an LG G6 and just went back to the G5 for other problems so I'll see if it has the same problems. I never had problems with bluetooth on my Joying 4.4.4 or 5.1.1 with my G5.
[Android Head-Units] edit:
Guys... some things might be possible but we don't have skilled people to help us... that is one MAJOR problem for us who bought the Intel Sofia platform

And I am sorry but I don't trust J saying that we can't go back to 5.1.1.

I am under the impression that they don't want us to go back...
[Android Head-Units] kampfschachtel:
Fully agree, the Android 6 is unacceptable so far. If emailing doesn't help maybe this helps:

How about everybody here opens up a PayPal dispute and request money back at unit is not useable with Android 6. Will do this now.

Paid in total 150CHF to replace my broken 5.1.1 unit and got a 6.0.1 unit, I will request a 5.1.1 instead for free now.

I tried downgrading using the 28th March 5.1.1 as you suggested with replacing it with 5009.60 but didn't work. mcu upgrade runs through, then it stops update with the Oda package error message. You can just reflash with 6.01 from may 28th, no brick.
[Android Head-Units] surfer63:
Why 5009_60? All 5.1.1 builds used the 5009_20 zip format.

Did you also try with the "standard" 5009_20.zip?

The 5009_20.zip and 5009_60.zip are the update packages as meant by the "OTA package" error you see. (OTA, not ODA by the way)

Those zips contain a folder META-INF which contains the sub-folder "com/google/android/" which again contains the update-binary. That binary is checked and then started with a number of parameters among which the "update package .zip", being 5009_20.zip or 5009_60.zip.

This is done by the recovery partition.

I don't know the details either.

I still didn't try to go back as the 25 May version is working fine for me after having issues with, and being frustrated about, the 12 May version.
[Android Head-Units] kampfschachtel:
I used the 5.1.1 release with the 5009_20.zip and renamed it to 5009_60.zip as you suggested to try to trick the 6.0.1 update procedure. Result as described. reflash possible...

Also tried orignal 5009_20 5.1.1 upgrade , that didn't even start updating on mine.
[Android Head-Units] surfer63:
Yes, now I remember :) I'm getting old, I assume.

It should be possible though as Google did it some time ago, going back from 7.1.1 to 7.0 on their Nexuses, for whatever problem/reason. I will do some googling on that.
[Android Head-Units] edit:
Did a lot of digging since this morning and a lot of flashing and modified the original post

I flashed the 25May firmware the FYT5009 version on a 5009 unit and discovered that It does not have the brightness menu in the Carsettings app so I flashed the 25May FYT6021 version on the 5009 unit, flashed ok and the brightness menu showed up.

Then decided to compare the files (binary) between the firmwares to see what files are different and except the customercfg.txt and rksofiacfg.cfg all the other files are identical between the 2 firmwares.

The rksofiacfg.cfg file has the same size on both firmwares but the content is different.

It ALL comes down to this file when it comes to "Backlight current adjustment" menu being prezent or not : rksofiacfg.cfg

This is not an editable text file so can't say much about it but all I can say is the only one that makes the difference.... maybe someone with debugging skills can read it... and maybe figure out what's in there and more important where is that file in the system and what does it do.

If you want for some reason to flash the MCU only extract these files from an firmware and put in the in the root of a flashcard or usb stick :

AllInOne.bat

SQLSOFIA

STM8_PROJECT cov.s19

STM8UD.BIN

If you want for some reason to flash/reflash an firmware without the MCU (because you want to keep the MCU you have) unpack the firmware archive in a folder and delete these 3 files (just the 3, SQLSOFIA is needed for the unit to detect and flash the firmware, it's the flash trigger file)

AllInOne.bat

STM8_PROJECT cov.s19

STM8UD.BIN
[Android Head-Units] hammer_gaidin:
Hello,

Thanks for the reply. I am using the Android 6.0.1 build. I have rooted, and have your app installed as well. However, no matter what I try, I cannot get usb to work at all. I have been able to connect via wifi adb, but that is all. Disabling wifi adb, i still do not get a device when plugging into a pc. I suspect it has something to do with host mode vs device mode. However, when i try to change the HU to device mode, it doesnt change.

Thanks
[Android Head-Units] CadillacMike:
i did the July 7th update, it is working good for me so far. It fixed UI3 so the Google app doesn't make it go crazy. Ok Google seems to work, although I dont use it, I just did so I could test it:

https://youtu.be/AWf8SX16q_k

I primarily use Google Maps, and the GPS has been fixed too. I used to have the issue where it would just do the searching for directions thing, but now it seems to work pretty great.

Bluetooth did disconnect and reconnect a bunch, but I dont use it very much, so I can't confirm if it is worse than before or not.
[Android Head-Units] edit:
Have you tested the [MENTION=3076686]gustden[/MENTION] mods (from 25 May firmware), still work ok? I am interested in custom keys...

---------- Post added at 03:52 PM ---------- Previous post was at 03:24 PM ----------

The new firmware has an new button next to the Reboot, Standby,Shutdown called "Off-Screen" misspelled as always... it meant Screen Off... turns off the screen
[Android Head-Units] TransAmMan:
A lot of people including myself have complained about Bluetooth issues. I'm now thinking it's problems with certain phones. I had the LG G6 and had the same problems as others with Bluetooth disconnecting after a couple minutes. It seemed much worse after the July 7 update. I went back to my old LG G5 and my Bluetooth is rock solid. Connects right away and never disconnected yet. I tried my new G6 again and had Bluetooth disconnect problems. Certain phones might not work well with Joying. After testing I went back to the Joying May 25 update since the new update was having Google maps problems for me. My LG G5 is working perfectly in all areas so far with the may 25 update. I may not update anymore or at least for a while.
[Android Head-Units] gtxaspec:
Steering wheel key mod works...
[Android Head-Units] edit:
Can you tell me please your impressions? pro/cons ?

Btw, do you have any ideea why the GPS on the Joying updates the speed in 3.6 km/h increments? It drives me nuts...

There are times when I drive with 50km/h and my waze shows me 50 km/m.... I drive with 52... Waze still showing 50... I step up... my car 53... Waze still showing 50... i step up even more... my car 56... Waze 53,6

---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------

What kind of problems? Can you please explain a little more?
[Android Head-Units] gtxaspec:
GPS bug is still there, must be something in the HAL or some configuration file, haven't looked into it yet.

Regarding those people wanting to downgrade, it's impossible due to the fact that the recovery will not allow you to downgrade OS, it knows what versions and dates you are flashing. We still haven't found a way to modify or remove res/keys or even modify the recovery binary itself. Anyone who has deeper knowledge of this please help out if you can.

So far, this is the best performing ROM i have used on my 5009. Steering wheel key mod works fine, no issues.
[Android Head-Units] edit:
Can you please have a look, it drives me insane, I got used to look at Waze GPS speedometer and also rely on Waze warning me when I tend to speed up.... my car speedometer tells the speed with a big error... around 7-10km/h

Like I said many times, I am so sorry that we don't have guys with real skills to help us out.

So, If I understood correctly, it's not like it can't be downgraded, they made sure that it can't be done because they don't want us to downgrade.

What exactly makes you say that?
[Android Head-Units] TransAmMan:
[/COLOR]

What kind of problems? Can you please explain a little more?[/QUOTE]

For the GPS problem with the July 7 update, after a fresh radio reboot, Google Maps works great. There are no problems. As long as I don't shut my car off it works. If I go into a store (radio goes into hibernation mode) then come back out. I launch google maps and enter my address. The screen comes up to hit the button "directions". I hit "directions". The next screen should show the routes and say "start". It never does. The little circle just keeps spinning forever. Now this happened sometimes with the May 25th update but I only had to close google maps, relaunch it and it would always work on the 2nd try. With the July 7 update, you can close google maps and reopen it 100 times and it will not work. I have to do a radio reboot from the top toolbar and then it works again with July 7 update. It was a minor annoyance with the May 25 software so I went back to that one and will wait to see if they launch something new that's a little better.

For my install I performed a factory reset, installed the software, reset the radio again, then installed my apps.
[Android Head-Units] edit:
I have another problem that is also annoying and I am sitting on it for quite a while now :

If I set in Viper :

Viper Bass to +8db

Viper Clarity to +3.5db

Dinamic System to 10%

and if I want to modify the EQ on top of that the sound goes nuts, shuttering, clipping, music stats to play at a slower speed.

In Android 5 everything was fine with the same settings.

Any idea what's the problem in 6?
[Android Head-Units] Dvalin21:
Looking for this July 7th update that has been mentioned. Not seeing it on the site

NVM

Found it through the forum
[Android Head-Units] 81greg:
Has anyone got OnStar to work on a chevrolet
[Android Head-Units] hammer_gaidin:
What would you be looking to get working? I work with the OnStar system for other reasons.
[Android Head-Units] piotrek_r:
The same problem for me. I was trying to inststall other viper4android version / reinstall android / wipe/etc. Still the same. Firmware version: 7 july.
[Android Head-Units] edit:
It behaved the same on 25 july and I am under the impression that they did it on purpose somehow to be able to promote their new shiny units that have the new EQ and amp.
[Android Head-Units] kampfschachtel:
If you have an external USB DAC it's even worse....just turn viper on and you get cripples and other stuff.

But they must have improved the preamps and internal DAC with the 6021 unit and/or may 25th update.

Unplugged the DAC to test via analog preout and sound is fantastic over my Audi B&O system. Never heard that before. Actually it is better as with the external USB DAC before, so I disconnected it permanently.

Can only compare it to 5009 unit and 25th March 5.1.1 and that's night&day what the preouts deliver now with 6021 and 6.0.1 25th may.

What I realized on my unit if you just turn viper via the master on in headphones, the sound really opens up. If I then just switch on the EQ it gets a bit quieter and stage+brightness reduces. The more you add the worse it gets.

I think joying improved the performance of the DAC and viper itself helps great to increase performance more but only the basic config. If you start to use a the possibilities in viper it gets worse.

If these are incompatiblities with viper or the viper tweaks need a lot processor power which is not available (my guess) anymore as internal DSP needs it or on purpose created I don't know.

They needed to make the DSP and preouts better/improve as their promoted new combo would even sound worse as the additional amp just amp the crap loud that it got: garbage in=garbage out.

That's what I experienced with 5009 unit and 25th March release, every additional viper tweak improved performance but it was not even close to what comes now out of the preouts with just viper switched on but no tweaks used.

If it's just the 6021 or 25th may update or both I cannot say.
[Android Head-Units] edit:
They definitely modified something for the better and I suspect if from the MCU update that happened along with the 25May firmware.

What I was struggling to achieve with my speakers is to have a bass that hits a bit lower, a bit more in the Sub area of frequencies. I don't have a sub in my car but the speakers are pretty good and I know from previous units that I owned that the bass can go pretty low and hit pretty hard. With android 5 I could not achieve that no matter what combinations I was using in Viper or the Joying default EQ... is like somehow the DAC+AMP were limiting my frequency output range. With the help of the 25May firmware+MCU I managed to find a balance that brought me quite a few steps to the sound that I once had... but I am not there yet.

I am glad that I am not the only one that noticed the sound improvement difference.
[Android Head-Units] kampfschachtel:
The joying is not limiting the frequency, it does exactly 20hz till 22khz which is very good for a 24bit DAC that is running on 16bit/48hz.

I had punch, even too much if my USB DaC was connected as my Audison DSP then fully decoding this and preamp is delivering this to the B&O amps.

The punch in the low bass is missing due to too less ampere power of the preamps so I cannot be that dynamic low down. My audison DSP afterwards via analog pre in is able to deliver these ampere's so DSP can add this to some extend.

You can help the joying with this if you improve the power supply to it means bigger red cable and a car HiFi cap with 300000piko Farad as close as possible to radio, that delivers the peak ampere power the joying need. The caps in the internal power supply are quite small.
[Android Head-Units] tostbig:
How do I activate this feature?

Oh ~ good info thank you. How do I activate this feature?
[Android Head-Units] gustden:
Here is an updated "no-kill" Sofia-1-C9-Server-V1.0.apk for the April 27 release ( android 6). It just has the task killer commented out and updates to the navi_app.txt file.

--Edit--

There was an additional spot that was still killing applications. Fixed and attached updated file.
[Android Head-Units] TransAmMan:
I updated my 8" 2gb Ram Joying radio to 6.0 today. My first attempt I had some problems, possibly an app conflict. None of my music apps could get an internet connection (pandora, spotify, Amazon music). Google playstore worked okay. I'm thinking maybe it was Nova launcher since they can be finicky with some aftermarket launchers. I factory reset the radio and tried again. Now all music players work fine. I'll play around more with it this week and see how it goes.

There is still a music app conflict that started 5.1.1 that didn't exist in 4.4.4. I was hoping the 6.0 would've fixed it. It really likes to default to Poweramp. So if I'm using Pandora and use steering wheel controls for "next track", it switches back to power amp and goes to the next track. "Play/pause" has the same issue with steering wheel controls. It basically toggles back and forth from poweramp to whatever app I'm using. It was never like this in 4.4.4. Oh well, I use an app called Task Killer to shut down poweramp an the problem goes away until the next time I use it.
[Android Head-Units] psxsnake:
I'm having problem to root my unit