yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] budwha:
If I understand you correctly, you want your phone to turn on the hotspot automatically when your phone connects to joying thru bluetooth.

This can easily be done by installing Tasker app on phone. (Automate might work too but have never used it). You can set up a profile and task in the app to make this work. If you don't know how to use it, there are several youtube videos explaining.
[FYT Android Head Units] kampfschachtel:
perfect, thanks. That's what I was looking for.

My R8 is used as all day car but sometimes it stands still for 3 weeks due to I am regularly on business trips and then I use it daily 2 weeks straight and put 3000km on it. So I didn't wanna risk discharging the battery and stand at 2 at night in the airport parking with a drained battery as exactly then it will happen as Murphy is my best friend:eek:. So I shut it automatically fully down everytime when I turn off the car.

The first 20sek the cold start of the V8 engine of my R8 is so loud:cool:, I wouldn't hear the joying playing anhow:D

so it can fully boot from scratch or just awake in this 20sek (both is done in 20sek), I won't notice/hear the difference till the engine is finished with the cold start procedure.
[FYT Android Head Units] budwha:
Ok. .....I've installed your "NoKill server apk" and the alarm volume stays where I set. Now I'll just need some more time to test out some apps and Tasker tasks. Thank you.
[FYT Android Head Units] rhacy:
Many thanks for adding the ok google talk back to the No Kill Sofia-1-C9-Server-V1.0.apk. It's working from the home screens on the 2-22-17 firmware without changing the JY settings apk to the standard 5.1 settings apk . To clarify, I'm able to set the alarm volume in the clock app - alarm volume setting and it stays set at the volume selected. Yay!

On a related note, does anyone know if it's possible to have ok google work from any screen, not just the home screens? If yes, could someone point out how? I looked in the language and input as well as the google app settings, but did not find a way to activate it.

Cheers,

R
[FYT Android Head Units] edit:
Is is possible to do that?! As long as the unit is permanently powered I think it still drains some small amount of power either you turn it off from the headunit menu.

Has anyone been curious enough to test if powering off from the menu does it make a difference in idle power consumption?

If it's really does make a difference that would be a great feature (to be able to power it off completely via software)
[FYT Android Head Units] WILD9:
Yes it still has the same crappy software, I'm trying to modify it at the moment but it is a slow process.
[FYT Android Head Units] edit:
It would be great if you can put it in the background somehow so you can still use the navigation or other apps while talking on the phone... if not it's a big pain in the A.

Another problem is that if the phone app blocks you screen and your unit from operating it it's a big problem at times... I find myself talking to the phone often and also need to see the Waze app for directions because I can't hear the voice directions anyway (my unit mutes the Waze voice while talking to the phone).... so with no voice direction and the screen blocked... big NO, NO.
[FYT Android Head Units] WILD9:
My goal is initially to make the overlay much smaller which seems like it can be done with an XML edit and then if I can figure it out add the ability to close it. Not sure about allowing directions to play over voice calls this is likely solved elsewhere and not in the BT APK.
[FYT Android Head Units] edit:
If you can make it smaller and better yet if you can close the interface somehow but by closing I mean not hannging up on the caller it it's fine by me.... I don't mind if I can't hear the navigation direction as long as I can see the screen... the whole screen... or as much as possible so I would not miss the direction shown on the screen.

Thank you !
[FYT Android Head Units] WILD9:
It looks like the overlay only occurs if the defined navi app is currently on screen, otherwise it just switches to the BT interface, can anyone confirm this behaviour? It might be easier to just remove this check and have it always change to the BT app, at least you can then switch back to whatever you were doing before.
[FYT Android Head Units] bogdi1988:
That is correct. However if either the BT app or the overlay are on, you can't get out of them - at least not for me.
[FYT Android Head Units] zorantoma:
For wifi tethering try Hot spot starter from playstore. I have the payed version and it works superb.
[FYT Android Head Units] kampfschachtel:
Good point.

I didn't measure it if shut down instead of dormancy mode is a big difference, I assume it is but I will measure. So with shutdown it will still take some juice from the battery.

I simply connected the red wire with the yellow ACC wire, so joying is on when ignition is on, off it's completely off.

But I will reconsider this if I measured the two different modes and know how much.
[FYT Android Head Units] edit:
If you can do some measurements and post some numbers that would be great ! It will help a lot of people, me included :)

Thank you !

---------- Post added at 11:24 AM ---------- Previous post was at 11:22 AM ----------

So as long as you are talking on the phone the unit is unusable, you are stuck with an overlay or the BT app on display? Unable to use any other app?
[FYT Android Head Units] budwha:
[MENTION=2798350]depre[/MENTION]dster........I installed the Sofia server apk you linked me to in this post https://xdaforums.com/showpost.php?p=71734364&postcount=403

Does it include your google voice mods?

I cannot get a response to "ok google" at all. What am I missing? I have checked all settings that I am aware of.
[FYT Android Head Units] KamaL:
Exactly. One of the worst things in these joying units.

Any solution for this?
[FYT Android Head Units] surfer63:
I saw no replies and I don't have the answer either, but in aliexpress you have on the left side the "contact now" link where you can contact the supplier directly.

Did you ask them?
[FYT Android Head Units] dpredster:
You should be able to activate it from google settings app. In the app go to Search > Voice > "Ok Google" detection and you would find the option to work from any screen.

---------- Post added at 07:15 PM ---------- Previous post was at 07:09 PM ----------

No it doesn't. The Sofia server apk mod is used to prevent the alarm volume which "ok google" uses from going back to 0 (see https://xdaforums.com/showpost.php?p=71565661&postcount=274 for more information). The mod to enable full google voice is here https://xdaforums.com/showpost.php?p=71658217&postcount=313. Also don't forget to increase you alarm volume if you want to hear a response.
[FYT Android Head Units] budwha:
Thanks........but I was under the impression there was a NoKill Version 3.0 or 3.1 that did not modify steering wheel keys.

Is there an apk available that has all the bells and whistles that surfer63, assassinslament, gustden, and depredster have put together. I do not want to modify my steering wheel buttons, but still want NoKill, ok google from any screen with talk back responses.

I am sorry if this is obvious, but as I said before, I lost track of all the different versions being mentioned in this thread.
[FYT Android Head Units] dpredster:
Let me try to clarify the process. In order to get "ok google" working you need to install the missing google apps and files. The problem is in Joying's setup the voice response for google voice is played via the alarm volume (credit goes to [MENTION=503463]AssassinsLament[/MENTION] for finding that and creating a fix). This is where you need a modified Sofia-1-C9-Server-V1.0.apk. As you stated you would like the NoKill version that does not change the steering wheel buttons. The No_Kill_Sofia-1-C9-Server-V3.0-GVS.zip that I posted in post #274 has that file. As stated it does NOT change the steering wheel keys. The final piece to the puzzle is being able to adjust the alarm volume. You can do this through the clock app (thanks [MENTION=286067]rhacy[/MENTION] for pointing that out) or you can replace the Joying Settings.apk with the ASOP Settings.apk that I uploaded in post #352.

If you are comfortable using wireless adb I can create an install script that would change all the necessary files for you. Let me know.
[FYT Android Head Units] kampfschachtel:
Source button: Are there some modifications possible, if yes where and how can I do this.

Can I change the order of the sources when switching through with the source button (via steering wheel control button sources), can I erase some sources I don't want and add apps as source e.g. Spotify?
[FYT Android Head Units] dpredster:
See https://xdaforums.com/android-auto/android-head-units/joying-2gb-steering-wheel-key-t3543390
[FYT Android Head Units] android_enthused:
Hello,

I've followed the aforementioned steps, and I cannot get an Amazon Fire Stick Remote to pair (this device does not require a pin). I tried both the Joying bluetooth app and the normal bluetooth option from settings. I also tried using the Bluetooth Auto-Pair (and other bluetooth apps), but it does not seem to do anything.

Any suggestions would be greatly appreciated.

Thank you.
[FYT Android Head Units] budwha:
I have installed the GVS.zip from your post #403........is this the correct one?....I do not see the file you refer to in post 274

I have installed new settings apk from post #352........and have adjusted the alarm volume

Ok google is not working

If I understand you correctly, that is all that is needed. Is there something else I need to do?

I am not very comfortable with adb, but did use it to install SuperSU.
[FYT Android Head Units] rhacy:
Thanks for the help dpredster. D'oh... before my last post, I did look in the JY Intel google settings under the Search > Voice > "Ok Google" detection, but the "From any screen" option was missing along with the Personal results option. Moreover, I just checked my older JY rk3166 unit and it has both options. In turn, I'm guessing that I must have turned off some of the google accounts and privacy - google activity controls that are needed for the option to be visible. Anyway, I'll turn on all the google activity controls and force stop the google app or apps or reboot, and then hopefully the additional any screen option will show up. Thanks again for the reply and again adding the ok google talk back fix to the no kill server.

Also, many thanks to gustden, surfer63, AssassinsLament for all your contributions and help.

Cheers,

R
[FYT Android Head Units] dpredster:
You seem to have everything you need. The Joying_GVS from https://xdaforums.com/showpost.php?p=71658217&postcount=313

The No_Kill_Sofia-1-C9-Server-V3.0-GVS.zip from https://xdaforums.com/showpost.php?p=71734364&postcount=403

and the Settings.zip from https://xdaforums.com/showpost.php?p=71701071&postcount=352

Now all you need to do is enable google voice. This is done by opening the google settings app. In the app go to Search > Voice > "Ok Google" detection and you would find the two options that you need to enable. They are "From the Google app" and "From Any screen". The "From Any screen" option requires you to train ok google. Just follow the prompts.

Please not that it currently does NOT support offline speech recognition and the only supported language is English.
[FYT Android Head Units] budwha:
Ok........now I see what I must be missing. I have not installed anything from this post https://xdaforums.com/showpost.php?p=71658217&postcount=313 because it says it is for a version that mods the steering wheel keys. Am I supposed to ignore the reference to "V4.1-Custom-Keys-Mods" and install those files anyway, using adb?

Sorry for being a pita, but please let me know if this is correct.
[FYT Android Head Units] dpredster:
Don't worry we are here to help each other.

Yes ignore the reference to V4.1-Custom-Keys-Mods. I was indicating that the mod was working with V4.1-Custom-Keys-Mods (which is what I am using).

You can safely install it. All it does is install the google files. I should mention that the scripts uses wireless adb. It is similar to rooting where you run install <ip address> in the command prompt of a Windows computer connected to the same wifi.

Good luck and let me know if it works.
[FYT Android Head Units] budwha:
I will try this tomorrow........but with a laptop hardwire connected to usb on HU, thats how I installed SuperSU. It should still work though, right?
[FYT Android Head Units] dpredster:
I'm not sure. I have never tried connecting a laptop hardwire to the head unit.
[FYT Android Head Units] kampfschachtel:
is there an alternative app/setup to easy connect (on joying) and Yijia App (on your android phone) to remotely control your android phone with the joying? That setup is crap and UI is pita.
[FYT Android Head Units] zorantoma:
Hello to all

I must say that this thread is superb and thanks to everyone for the mods.

I allready rooted,change the radio app to red and used the no kill mod on my vw 8inch radio with 28.3 fw.

I just need some help with one thing. I froze the stock music app,becouse i use Power amp. Is there any way i can change the media hw key on the unit to select Power amp instead of music app. Now i dont have any function on the media key,becouse of the frozen music app.

This is the only thing i cant find a selution for.

Any hint and if yes a tutorial would be superb.

Thank you
[FYT Android Head Units] mad212:
Could u please create a script for all this? I'm pretty comfortable with wireless adb and am having an issue with getting this all setup for some reason.
[FYT Android Head Units] budwha:
I just tried installing the google file from https://github.com/dpredster/Joying_GVS, and I must be doing something wrong.

-I open command prompt as administrator

-change directory to where I put the files downloaded

-type "adb connect 192.168.1.16"

-it says " connected to 192.168.1.16"

-type "install.bat 192.168.1.16"

it runs a bunch of lines quickly and says "error: device '(null)' not found under each line

btw I did it wirelessly..........USB debugging is enabled

what am I doing wrong?
[FYT Android Head Units] dpredster:
Type adb kill-server.

Then type install 192.168.1.16.

That's it. The install.bat would do the rest. This is assuming the head unit's ip is 192.168.1.16.

---------- Post added at 03:56 PM ---------- Previous post was at 03:56 PM ----------

When I get to my laptop later I'll upload it for you.
[FYT Android Head Units] budwha:
I tried kill-server and same thing happened......but when I removed the .bat after install it began running the commands.......NOW it appears to be hanging on one command for a while....like ten minutes so far..........do I just be patient?...........how long should it take?
[FYT Android Head Units] dpredster:
Two of the command writes some files to the head unit and that takes a little while. Just be patient and it should finish running soon.
[FYT Android Head Units] budwha:
Thank you again for the fast response.........it has finished now...took about 20 minutes total.

Now on to next problem..........the HU is is stuck on the "Android" logo for about 25 minutes now and I have to leave for work soon. Is there risk of damage if I interupt..........it shouldn't take this long?
[FYT Android Head Units] joshnat:
I had the same issue with the Google voice script. It ended up rebooting after a while but all my app settings were wiped. I've since upgraded to the 3/28 ROM but have been wary of trying the script again.
[FYT Android Head Units] PsychoMcSatan:
It seems clear that there's something unstable with ADB over wifi and these units. I've gone through the same issues with installing some of the tools/fixes available in these forums and even with my router stretched out into my garage, I still see random "dropouts" while running the scripts.

One workaround seems to be to run the contents of the install.bat files manually, one line at a time by copying and pasting onto the CMD window. That way you can see if and when a particular command fails, and in most cases you can just try that one command over again till it works.

That being said, any idea why so many of us seem to be having these issues? I see there are a few "ADB WiFi" apps in the Play Store to enable/disable ADB functionality so I'm wondering if any of these might improve stability. I'll give a few a try tonight and report back if it improves things for me.
[FYT Android Head Units] surfer63:
After sleep mode the WiFi gets often unstable, at least on my unit. I posted about it on the forum.carjoying.com but didn't get a single reply. So I assumed I was the only one having either some quirks in my network or a bad WiFi receiver in the car.

What I do before every copy/install connection is reboot the unit. After the reboot the connection is for me "rock solid".
[FYT Android Head Units] KamaL:
I faced the same issues with wifi. I also reboot the unit when that happens.
[FYT Android Head Units] treel:
the original BT app from joying does not work.

You need it to replace it with the one i have modified.

If your device does not require pin the modified app need it to know you just enter the pin 3368 and it should work.

I'm not able to test it on amazon fire stick remote.
[FYT Android Head Units] budwha:
The unit finally boot up after about 45 minutes........I thought for sure it was stuck for good.

Now to adjust all the settings
[FYT Android Head Units] android_enthused:
I've already replaced it with the one you provided and follow all steps (set permissions, etc)

When I attempt to connect the remote it states I have the wrong pin. I have tried 3368, 0000, 1111, 1234, etc.

Has anyone else connected any remotes via bluetooth?

Thanks.
[FYT Android Head Units] rnabi99:
Awesome work, I love how you increased the size of the RDS data.

Would you mind creating a Green version for Fords?
[FYT Android Head Units] slav.z:
you need to set your bluetooth password to 1234. The stock app doesn't pair with your odb II because the HU pin is not 1234 (or whatever you odb II dongle uses ).
[FYT Android Head Units] treel:
When you use the modified app you scan for devices and you see the remote ?

then you click on on the device in the list and the unit ask for PIN ?

you enter the 3368 and the app tell you that it is a wrong PIN ?

if everything is answered yes then your remote require PIN or it use some different security.
[FYT Android Head Units] surfer63:
Green?

I drive a lot of rental Ford Focuses and most of them are Red or Orange or Blue. (edit: The radio that is :D )

Do you have a photo or link to a photo?
[FYT Android Head Units] rnabi99:
http://www.shareamemory.com/radio/Navigator_CD_radio.jpg
[FYT Android Head Units] android_enthused:
Yes to all. I know the amazon fire stick remote does not require a PIN because I was able to pair it to an Android phone (Nexus 4) without a problem (and it did not ask me for a key).

Thank you for the suggestions thought. :good:
[FYT Android Head Units] treel:
do you see some messages like

Start Auto Pairing. PIN = ..... or set pin .... setconfirm

try to change the setting of auto answer.

Or it is possible to make a short video of the pairing process ?
[FYT Android Head Units] Tubra:
This is going to be an interesting question, how much is the head unit supposed to use when the vehicle is off? I measured mine at 93-125mAh while off. The 93mAh is when the unit is set to shut off and the 125mAh is when "dormancy" is activated in the settings. My Metra canbus unit uses 27mAh. 152mAh isn't much and will reduce my battery to an estimated 50% in a few weeks. So, is 125mAh too much for the head unit to be using?

My method for determining mAh draw was to set a multimeter to 200m DC voltage and use the probes to get a reading on the radio and hvac fuses(they have exposed leads for probes on top). I used my car manual's fuse box diagram to find the fuse location. I then used link below to a conversion chart page and selected the "mini fuses" link(different chart for different fuse type) to convert the reading to mAh. http://info.powerprobe.com/fusechartsdownload

https://youtu.be/lRcj1fQcWwU -full method explanation

This was a ridiculously easy way to get the mAh draw for the joying unit, but I'm wondering if 125mAh is too much?
[FYT Android Head Units] edit:
From what i have read so far even 96mAh draw at idle is very much. 152mAh draw is huge... If you have a car alarm that's at least 20-30mAh more... If you drive daily at least 7-10 km might not be a problem... But if you park the car for 2 weeks you have a good chance that your car will not start. It also depends on how old is the battery, how good is the charger...

I'm not an expert so guys if i'm wrong please teach us.
[FYT Android Head Units] tuuza:
Its simple maths, if you dont count the differencials like temperature and how easy engine starts.

Average modern car battery 75Ah( ~700A ), condition 80% 560A left

96mAh * 24hours = 2304mA daily draw.

Over a week its 16128mA, 16.128A

So after a week there is 544A left, and a car should start using under 200 amps.

If you have a good battery there should be no worries.

If you are using old battery or bad car then all you should blame is urself.
[FYT Android Head Units] miatawnt2b:
Hey all.

I am looking to install something into my Suburban. The car has rear screens for the 2nd and 3rd row. The stock NAV unit will allow you to output video to the rear screens with audio going to separate 3.5mm jacks in the rear while at the same time allow you to use the head unit screen for NAV and/or Radio through the car speakers. Will these units do the same?
[FYT Android Head Units] AssassinsLament:
Sadly no. No video out.
[FYT Android Head Units] edit:
I am planning on leaving on a 2 week vacantion and my car is a diesel that usually needs more power to start... Will my car start?

The battery is new, 74Ah.
[FYT Android Head Units] KamaL:
Why not shutdown the Headunit off when you're on vacation? You'll be safer this way.
[FYT Android Head Units] edit:
Of course I will but 96mah draws the HU (shutdown triggered in software) plus my car alarm that draws around 40mah... For 2 weeks... It will be close
[FYT Android Head Units] bogdi1988:
Most likely not. I'd recommend to change dormancy setting to OFF instead of standby.
[FYT Android Head Units] KamaL:
I mean complete shut down.
[FYT Android Head Units] edit:
I don't know of such a way... unless i take it out of the dashboard and pull out the power plug but that's quite a lot of work and not suitable for me... I rather install a microswitch to cut the yellow wire (permanent +12v power feed)... I can't think of a better solution for the time being.

Feed me some ideas if you have, thank you !

---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------

From my understanding doing that still draws 96 mAh from the battery... opposed to 125mAh for standby mode. Did I get it wrong?
[FYT Android Head Units] bogdi1988:
Pull the battery cable of the battery itself and lock the car? When you're back, reconnect cable.
[FYT Android Head Units] KamaL:
In the Taskbar there's an option to shut it down completely, will it still draw power when shut down?
[FYT Android Head Units] bogdi1988:
Apparently so, haha
[FYT Android Head Units] edit:
Aparently quite a lot of power 96mAh
[FYT Android Head Units] edit:
That method in theory would work but with these new cars, full of electronics that method is not recommended. On my char there is a lengthy process for connecting and disconnecting the battery because skipping that for some reason increases the chance to damage certain on board computers... beats me why.... Ford knows better

That method will also disable completely my car alarm... and my car lives on the street... I don't own a garage...

So for me it's not an option... thanks for the thought