yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] ste2002:
sweetnothings, now I have another issue with latest update: the 1st dialed number dials OK. Every subsequent number I ask to dial (2nd, 3rd, etc.) is processed correctly (as I can see in phone number field), but Joying BT app dials number which was dialed 1st - always the same 1st number.

I've rebooted my phone, which did not help. And another voice assistant (Dosi - I already mentioned it) makes BT app dial correctly each number I ask. Very strange.

My setup: I use Car Launcher AG and CPU Temp app - nothing special besides that. Inbetween I played with ELM327 dongle and Torque app (changing default BT password from 0000 to 1234) and could blame that for misbehavior - if not for Dosi, which still dials correctly.

----------------------------------

BTW, while testing previous app versions, I mostly used the only one phone number to dial, no variations - above problem could not be seen with only one number dialed one by one.
[FYT Android Head Units] sweetnothings:
tnx for your update. please check out the next version if it is still the same
[FYT Android Head Units] ste2002:
Today "OK Google" made another surprise saying something like "You can not make calls yet". Your app does not seem to relate to this since it happened both with pre-last and updated versions of it. I have to sort it out then proceed with testing. Just for the record: Dosi assistant again has no problems to dial.
[FYT Android Head Units] tOz666:
Same here. I've just installed today my new Joying and updated it, and thought I've done something wrong when setting it up.

Did you found any solution to this? OK google still keeps saying I can't make calls.
[FYT Android Head Units] ste2002:
The same today. I did not do anything yet: removal/installation etc. Still trying to find any clue by searching Inet.
[FYT Android Head Units] tOz666:
Today I started my car in the morning and it now works for me, and I didn't do anything on purpose to fix it (but i've been fiddling with other stuff that maybe fixed the issue without me noticing ...)

Maybe it updated silently, try to connect the unit to Internet and try to update Play Store apps...
[FYT Android Head Units] ste2002:
Thanks for input. My HU is always connected, and I've checked Play Market for updates before dialing. Since there is an alternative voice dialer I am not going to push things by massive reinstalling Google apps, only keep trying.
[FYT Android Head Units] tOz666:
I ended up using another voice dialer app, one I know since the PocketPC days, Cyberon Voice Commander.

It's not supper pretty but it does its job.

From now on I'll use Google Voice only to tell it places to go with Maps while driving... other uses can be covered fairly well by Cyberon.
[FYT Android Head Units] ste2002:
My alternative is cheaper and it's multi-functional assistant supporting 3rd party extensions and macros. Apart from dialing it is able to pass a destination to a navi program, give weather forecast locally or in given place today and any date, tell news, anecdotes, open/close apps etc. AFAIK it works only in my language (Dosi assistant).
[FYT Android Head Units] sweetnothings:
i was not able to reproduce that on my end.

i am on July 6.0 Rom, using SuperSu, model JY-UMS03N2
[FYT Android Head Units] tOz666:
Well i'll try to shed some light to the topic, yesterday I made the mistake of installing xposed which led me to a bootloop, which led me to reflash the firmware, full wipe and reinstall everything.

I have the unit up and running again, and again google voice calling works for me as expected.

I didn't try to test calling before doing the following mods, but I thought they can be related:

I installed the Velvet.apk for enabling OK Google on any screen, following the Velvet.apk for android 6 part of this instructions.

(PS I ended up disabling it because it interferes with the phone calls, people doesn't hear me).

I've also installed Offline Voice Recognition for my language (Castilian Spanish) following this

Maybe this has something to do with the issue, maybe not, but sure they affect on how Google app works... give them a try.
[FYT Android Head Units] tOz666:
Also [MENTION=715356]sweetnothings[/MENTION] could it be possible to add an option to configure a timeout, so one does not need to touch the make call button to place the call? It would be a great add to make the whole process hands free.

Thanks for this great app, really useful.
[FYT Android Head Units] sweetnothings:
this should work instantly without waiting for pushing the button.

there are two reasons for nate calling automatically:

- i didnt consider the number as surely valid

- a bug in Joying BT App failing the Joying activity to launch for calling on first time usage after standby or boot.

i have a beta release that may work for the socond bug, i will go for productive release quickly because i don't had enough testers and hope it has not down sides of the fix.

to ensure that its not the first one, please report here the phone number you like to dial and what it does display in the phonenumber field for it. tnx
[FYT Android Head Units] sweetnothings:
i would suggest you to check if the Google app has actually authenticated your Google user account to access your contacts (just one reason i can think of causing this.
[FYT Android Head Units] tOz666:
Spanish landline and cell phone numbers all have 9 digits.

Here's the screenshot I made when trying to dial a cell phone number 654660X8X

X's are digits.
[FYT Android Head Units] sweetnothings:
its because you are not using international formated numbers

but i am considering to skip the number check as it causes to mucj problems.

there are just to much variations out there

check out the update on play store tomorrow
[FYT Android Head Units] tOz666:
Yes this is correct, in mainland Spain there's no need to dial international formatted numbers to place calls to spanish phones.

That's why all my phone numbers are stored as 9 digits, with no symbols whatsoever.

Thanks for all your efforts, i'll wait for the update.
[FYT Android Head Units] ste2002:
What I did: made sure that I re-logon Google account, then cleaned caches of Google and Google services, then removed and installed Google and services - no change, still can not dial. Still not ready to reflash HU for there is an alternative voice dialer. sweetnothings, thank you for support.
[FYT Android Head Units] tOz666:
I tested today the new version, and finally dials correctly, but the other side can't hear me... I thought it was a problem with my mic but I checked it and it works... also called manually with the bluetooth dialer and I can be heard. Same with Cyberon Voice Dial, working good.

I think that the problem is that the google app process keeps listening to the mic in the background and screws it up, I've experienced something like that before (refer to my previous post about Velvet.apk OK Google on any screen)

Is someone else experiencing this issue? Maybe it could be fixed by hiding/ending/killing google app after placing call?
[FYT Android Head Units] ste2002:
I've also experienced that couple of times before OK G refused to dial. I wonder if there is a setting for it to work on background thus locking mic...
[FYT Android Head Units] ste2002:
Wow, it works for me again. The reason for OK-G refusing to dial was that I had to reconnect my phone to HU after playing with Torque and also to again download contacts from phone to HU which resulted in doubling each contact on my Gmail account (not on HU).

After I combined (merged) each pair of identical contacts using PC(BB)->Gmail->Contacts, "OK Google" on HU started to pass contact's phone numbers via sweetnothing's app to BT. Still did not have time to test it for any long period, but the reason was that simple.

============

I've tested it today - the app and voice dial work OK right from the very 1st try, thanks a lot.
[FYT Android Head Units] sweetnothings:
On which rom version is your HU?

There was a bug with phone problems while running gmaps and maybe Google App too, but should be fixed in actual rom version.

Killing Google app before dialing will only be possible on device with superuser app
[FYT Android Head Units] tOz666:
I'm running latest September 1 ROM, rooted.
[FYT Android Head Units] ste2002:
Update to my testing: though dialing now goes perfectly for me, I am also not heard on the other end. My previous success report was after incomplete test (without answer on the other end, I just called home/office with no one there).

I'm also running latest September 1 ROM, not rooted.
[FYT Android Head Units] sweetnothings:
Do you guys have any Sofia Server Mod installed? NoKill, CustomKeys ...
[FYT Android Head Units] ste2002:
I do not have any mods. My setup is still as follows: Radio ON, CPU Temp and Car Launcher AG. I will check if mic authorization gone from Google.
[FYT Android Head Units] tOz666:
I had sofia server NOKILL mod, still can't be heard, and now I have CustomKeys with a custom launcher.sh.

I can test easily if my voice is heard on the other end as I use the following trick: I haven't got enabled my carrier's voice mail, but can call to its number to configure it, and so I enter the option to record the welcome message, and then it's played back when you finish. If there's silence then I know something is wrong with the mic.

One of my tests was to try to end the google app in the background, while placing the call, and try to check if i'm heard..

Turns out the Bluetooth app tries to stay in the foreground at all times, but you can trick it if you touch the show tasks button while touching with other finger to swipe the google app from the background at the same time... crazy.

I only tested that once, placed a call with google voice to my voicemail, try to end google app in background, try the welcome message, and voila it worked I could heard myself.

Next thing i'll try is to kill the google app programmatically using Tasker... so far I didn't succeed, somehow the google app stays unkilled or blocking the mic...
[FYT Android Head Units] ste2002:
It also looks to me that some recent update of Google app locks microphone when calling, never letting Joying BT app use it properly.
[FYT Android Head Units] sweetnothings:
thanks for your input guys.

as soon i have the time i will try to have google app killed before calling, but we will need root rights for this
[FYT Android Head Units] ste2002:
Google app on HU have auto updated couple of times during this week, but I could not try it if the error with mic was corrected since my contact list is again not in sync with Google ("Can not dial yet" again). I do not see any option in Gmail->Contacts to force Contact resync. Will report when got any success.
[FYT Android Head Units] Firik:
I'm getting the same message. I started getting it the past couple of days. I believe there was an update that caused it. It was working perfectly earlier in the week.

Also, in regards to the microphone not working. I didn't read post in depth but last time I had that issue, it was a permissions issue with the Google app. I had to turn it off then back on again. Hope that helps.
[FYT Android Head Units] ste2002:
Did you modify your contacts in between? Unsynced contacts was the reason for Google's refusal to dial for me, sorted by merging similar records. Now I have this "no dial" problem again after modifying contacts differen ways on phone set and in Gmail.
[FYT Android Head Units] tOz666:
Well, what I said about killing google app in background seems to be incorrect.

I've tested further and with the app updated as of 11/04, it still mutes the mic when calling, even if you manage to close the google app (with the task list).

However, What I found and tested is that if you press the "transfer audio to phone" button, and press it back (to return audio to the Head unit), the mic starts working. It's the button I point in red in this screenshot:

[IMG="showing transfer audio button in bluetooth app"]https://i.imgur.com/KAtheGF.jpg[/IMG]

Going to test later about reapplying permissions though.
[FYT Android Head Units] w4audi:
Hi guys i trying to download this APP from the play store and its saying that my unit is not compatible with this version. I have a joying Head unit MTCB-JY-V2.73 running android version kit kat4.4.4. is there a older version that will work on my unit?
[FYT Android Head Units] sweetnothings:
i don't know why, but app requests android 4.0+, so that can't be the point.
[FYT Android Head Units] xdamember2:
In my case I solved this issue by changing the DPI from 160 to 161, deleting Google App's data, and re-enabling its permissions. My theory is that Google doesn't want to make phone calls from a tablet.
[FYT Android Head Units] sweetnothings:
New update on Play Store.

Added settings screen with 2 options.

Wondering if killing google app before dial solves mic problems for some of you.
[FYT Android Head Units] w4audi:
I try again today to install your app and I got this message from the play store. (your device isn't compatible with this version). I am not sure what's wrong.

my unit is by Joying

Model number 3812 J0217

MCU version- MTCB_JY-V2.73

Running Android 4.4.4.28032016

any help will be greatly appreciated is there a way to force the insulation.
[FYT Android Head Units] sweetnothings:
you can try to sideload with the attached apk file.

this is latest version 3.5

please report if it works or not
[FYT Android Head Units] w4audi:
Thank for the new file i did get it to install, but it did not work for me. When i try to make a call using ok google i get a pop up.

Unfortunately, GVC CallHandler 4 Joinging has stopped.
[FYT Android Head Units] sweetnothings:
ok i checked your ANR.

Your HU has an other/older bluetooth application.

i need to know the pakage name and actifity name of your Joying BT App, as it is different then the one on the actual units.

or you can upload your apk file of your Joying BT App here so i can look into it.
[FYT Android Head Units] w4audi:
I have attached the bluetooth app that i am using. I use this so that when i am using the GPS i can minimize it out the way.
[FYT Android Head Units] sweetnothings:
Sorry may i was not clear enough what i need, this app you provided is not to make calls over bluetooth. I will need the one you use to make calls.
[FYT Android Head Units] w4audi:
I am not sure what app it is i thought i was using okgoogle to try to make the Call. If you can print me in the right direction then i can try to find it.
[FYT Android Head Units] sweetnothings:
if there is any way for you to make a call with your HU over a bluetooth connected phone:

You will have one joying stock app with a dial pad and phone book. If there isn't such an app on your HU, my app can't do much for you.

In that case you may want to have a lock at the paid app Tablet Talk [MENTION=3076686]gustden[/MENTION] mentioned in this post
[FYT Android Head Units] w4audi:
Yes i do have a Dial pad see Picture attached but i don't know the name of the app. When i go in the system apps folder the only thing i see is a phone icon that say Telephone Provider.apk see attachment.
[FYT Android Head Units] sweetnothings:
I can't say much from only the name of the app, if you attach this apk in your post i will check if it is the one responsible for making calls.
[FYT Android Head Units] w4audi:
I have attached the file hope thats the one.
[FYT Android Head Units] sweetnothings:
no that is not the right one.

you can find it with the app "App Inspector" on play store
[FYT Android Head Units] w4audi:
Thanks for the pinter i think i found it see attached
[FYT Android Head Units] sweetnothings:
This is a dial app, but it is the one from Google Android, suiteable for mobilephones.

There must be another one from Joying, something named more like Bluetooth or something like that.

If you look up one in App Inspector, you must see that it is not from stock android, you will see syu, joying or something
[FYT Android Head Units] w4audi:
Thanks for all the help but at this time i am given it up i can't seem to find that file. I found 2 Bluetooth files but not sure if they are the right one.
[FYT Android Head Units] cehes:
Hi all,

Really great to do such app, this is exactly what I was looking for to have my joying be quite perfect!

The problem is that when I say '' call John Doe on mobile'' I get ''sorry I can not use call yet''.

I read all the 9 pages and some had this problem and say it comes ok again without doing anything.

I also read on page 8 to change DPI and reset Google apps which seems quite weird

What should I do first?

Thanks for this job!

EDIT : it is now working ! The only thing i did is installing "joying extra Tools", root and change DPI. I do not know in all of that what chnaged, but now i can choose your app and all is good ! Many thanks
[FYT Android Head Units] fabien_m2002:
Hello,

i have same issue with 15 dec firmware: '' I get ''sorry I can not use call yet''.

What's the workaround?

Thanks
[FYT Android Head Units] gtxaspec:
Hi! Just wondering if you are planning to release the source to your program? It is really great! I use it every day! Thank You for creating it!!
[FYT Android Head Units] sweetnothings:
There is really not much behind it, i just wrote a few quick and dirty lines of code for my own needs.

Atm, i have no the time to look into issues or to upgrade my HU to a recent FW.

i dont feel like my code is worth to put on Git, but if it is useful for anyone, i have attached my source files, feel free to use it, or better to improve it ;)
[FYT Android Head Units] sweetnothings:
You should check if you are authenticated with your Google account in the Google app, it needs access to your Google contacts.

And maybe post #91 is useful, but i dont know why that will have any impact
[FYT Android Head Units] gtxaspec:
Thank you so much! I had some opportunities as well where voice calling didn't work on my rom, or stock for that matter if the dpi wasn't 161 or above.
[FYT Android Head Units] dyabolikarl:
What is the stock DPI for the 3gr's?
[FYT Android Head Units] gtxaspec:
160
[FYT Android Head Units] Need4Camaro:
I'm having problems.

I installed the app, but when I make a call by saying "Okay Google call xxx-xxx-xxxx" Google replies, "Sorry, I am unable to make phone calls yet." I also do not get the three dots to modify the launcher app. ...What gives?
[FYT Android Head Units] edit:
yes, I can't find those 3 dots... a picture would help so much !

I finally managed to get it working BUT I had to raise the DPI to 161 and that messed everything up with the Icons on my launcher (Nova Launcher).... isn't any other work around the DPI issue?
[FYT Android Head Units] gtxaspec:
Change your dpi to 161 or greater, clear Google app data and reboot
[FYT Android Head Units] ste2002:
I've abandoned using OK Google for not allowing to dial yet - I'm still on non-rooted HU. Instead I started to use this dialer: https://play.google.com/store/search?q=дозвонщик%20и%20контакты&c=apps - quite nice. All I need from it - give me favorites in handy way. Then control goes to GVC, and I can successfully call.

I can also use local voice assistant (non-Google) to dial by voice, but my dial out list is short enough to fit on one page of above dialer.
[FYT Android Head Units] surfer63:
[MENTION=520205]gtxaspec[/MENTION]: Would it not be a good idea to set this immediately in the build.prop of your ROM?

Currently it says

ro.sf.lcd_density=160

Why not change that in the custom ROM to 161?
[FYT Android Head Units] gtxaspec:
good suggestion. I'll add this to the fyt_build.prop!
[FYT Android Head Units] edit:
The downside of this is that all the icons that i"ve set to be big (140) in Nova Launcher suddenly went small and you don't have the possibility to make them back to what they used to be.

This an workaround with downsides that I don't recommend
[FYT Android Head Units] gtxaspec:
ok...so leave dpi at 160 and set the DPI using app settings xposed module on the googlevoicesearchbox apk to 161... does it work then?

OR

make the dpi like 170 to make your icons bigger. i personally run DPI at 250 and then adjust some apps down...individually.
[FYT Android Head Units] edit:
I tried that and unfortunately it does NOT work.

The downside of this that the notifications bar also grows in size considerably eating away precious screen estate doing..... nothing. This is what preventing me in the first place to raise the dpi to 240 like I used to have on the old HU and that I find adequate.

On my old HU the DPI was high but the bar was small and that was best. Good thing with the exposed on this units I can raise the DPI per app so everything is nice and visible from a distance but the HU UI stays small.

This might be the only solution to the problem... at 170 the bar will not raise that much in thickness.... can't say anything about the icons size though
[FYT Android Head Units] gtxaspec:
Not if you set the system ui's dpi to 160... =] Keeps the bar nice and small...

I love Xposed.
[FYT Android Head Units] edit:
If you can do that then by all means, raise it to 170.... It's the only solution that I can see to our problem anyway.

Can't tell if the Icons get back to a decent side though...

I just checked... at 180DPI the icons are still a lot smaller then what they used to be.... so for those the like big icons in Nova this doesn't seem to work
[FYT Android Head Units] surfer63:
Why? You obviously made the change once from 160 to 140 after flashing. In this case you need to set it once from 161 to 140.

Or do I miss something?
[FYT Android Head Units] edit:
I was referring to the icon size that I made in Nova Launcher settings the max being at 150...

I just set the DPI to 190 and the Icons are still small compared to what I used to have....

Later edit :

The only workaround that I see for the moment is to raise the Nova Launcher DPI to 220 and set the font size to 80 with the Xposed App Settings module .... this brings back the look and the big icons (tested right now)

Yes, it can be done... so you can raise the DPI to 161 just warn the users about it so they know what to do.
[FYT Android Head Units] PoppaRoxie1986:
I found that you can use the App Settings Xposed module to prevent the joying Bluetooth app from staying on top while you're in a call.
[FYT Android Head Units] gtxaspec:
Nice! Which option did you use to successfully keep it from staying on top? I was unable to do so and made an Xposed module to prevent it from forcing to the top.
[FYT Android Head Units] snickler:
All,

Please stick to the context of the thread and refrain from arguing with each other. If you have information to give that helps others, please do so completely in order to prevent unneeded back and forth. If you do NOT have information that helps, don't incite anything or keep it going. We're all here because we want to make things work aren't we? Let's help each other instead of taking away from the legitimacy of this thread.

Let's all get along, folks. I'll be glad to PM a few people if it's impossible for everyone to play nice :).

-snickler