Status Update
Comments
hb...@gmail.com <hb...@gmail.com> #2
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Thanks & Regards,
Manish Bavireddy.
Google Cloud Support
wo...@gmail.com <wo...@gmail.com> #3
I now bought Cyberon Voice Commander. When pressing the dial button on the headset I now get the choose of Google Voice Search and Cyber on. When choosing Google nothing else happens than the grey screen for less than a second and the shortly after this the message "please wait" on the headset. When choosing Cyberon it works like it is suspected.
In another German forum I was told that owners of the Galaxy Nexus do not have such problems with 4.2.1 ???
I really would love to use the Google Voice Search, as it hopefully would work better than Cyber on - but this may also be the problem of a general bad Bluetooth connection with the Nexus 4 (several other issues are open to this topic)...
de...@googlemail.com <de...@googlemail.com> #4
Is there any other workaround known yet?
sy...@gmail.com <sy...@gmail.com> #5
When using "bluetooth launch" app, I also get prompted to choose program to use. Unfortunately, this workaround does not work consistently.
Please correct in next version !
wo...@gmail.com <wo...@gmail.com> #6
wo...@gmail.com <wo...@gmail.com> #7
my...@gmail.com <my...@gmail.com> #8
pa...@gmail.com <pa...@gmail.com> #9
Initialisation.... never ends
This feature worked very well with my old iphone...and I really need it when I'm driving. This is not a low problem, because it can cause a car crash,as to bypass this problem I'm obliged to have my phone on my knees
Please fix it
Thanks
ri...@gmail.com <ri...@gmail.com> #10
Only in 4.2.2, it worked with 4.2.1!
mi...@gmail.com <mi...@gmail.com> #11
This totally doesn't look like a duplicate of #38566
gi...@gmail.com <gi...@gmail.com> #12
The phone connects fine to the Bluetooth, but when a call comes in, the voice commands to answer doesn't work.
The Bluetooth unit is fine (tested with another phone on Gingerbread), so it's to do with the voice command over Bluetooth not working.
Same issue, another variant of the OP.
be...@gmail.com <be...@gmail.com> #13
Long press on BT headset button. Nexus 4 (4.2.2) stuck on "Initialisieren".
se...@gmail.com <se...@gmail.com> #14
Nexus4 (4.2.2) "Initialisation..." + sound "Veuillez patienter"(Please wait) in the BT device, then nothing ... I had wait 20min.
Motorola h560
Scala rider G4
both were working with my old iphone4.
sy...@gmail.com <sy...@gmail.com> #15
The issue of OP (grey flashing screen) seem solved with 4.2.2
I would suggest to close this issue.
ri...@gmail.com <ri...@gmail.com> #16
The 35737 is quite old and i don't think that a fix for the sgs3 will help us here.
Cheers
crusi
wo...@gmail.com <wo...@gmail.com> #17
it still hangs with gray screen and saying "Initialisierung". Before with 4.2.1 it was just flashing the gray screen shortly and went back to home screen.
Yes it's true it seems that
Blame Google
wo...@gmail.com <wo...@gmail.com> #18
sy...@gmail.com <sy...@gmail.com> #19
The fact that we are then struck with another issue, as described in #35737, seems independent, and largely analyzed in there.
This topic remaining open is misdirecting for both users and developers and does not serve anyone.
Everyone with something related with "new" issue should post to #35737 for clarity.
wo...@gmail.com <wo...@gmail.com> #20
In case that you really have the insight you might be right. For a simple user it seem to be still the same issue but sticking one step further. And the the problem of the headline still remains. As other users may find this issue via search before #35737 we should not close it as solved. But rather let it as it is with the hint to
na...@gmail.com <na...@gmail.com> #21
sc...@gmail.com <sc...@gmail.com> #22
ph...@gmail.com <ph...@gmail.com> #23
mi...@promomasters.at <mi...@promomasters.at> #24
mi...@promomasters.at <mi...@promomasters.at> #25
vi...@gmail.com <vi...@gmail.com> #26
ma...@gmail.com <ma...@gmail.com> #27
il...@gmail.com <il...@gmail.com> #28
nexus4 and bone bluetooth headset....
be...@gmail.com <be...@gmail.com> #29
be...@gmail.com <be...@gmail.com> #30
co...@gmail.com <co...@gmail.com> #31
Stuck with the "Initializing"-Screen after pressing the button on the headset.
al...@gmail.com <al...@gmail.com> #32
mi...@promomasters.at <mi...@promomasters.at> #33
mo...@carefactorzero.net <mo...@carefactorzero.net> #34
Settings -> Accessibility -> Text-to-speech output
Settings on "Google Text-to-speech Engine"
Language:
Was set to English (United States)
I've set it to English (United Kingdom).
Nothing else was changed, and now when I push the call button on my bluetooth mic I can tell it to "Call Joe Smith" and it actually will!
Could be a coincidence, but nothing else has been changed (nor software installed or removed).
n....@googlemail.com <n....@googlemail.com> #35
Your workaround does not work for me... I tryed US-, GB-English and German...
gr...@gmail.com <gr...@gmail.com> #36
D Grimon
it...@gmail.com <it...@gmail.com> #37
it...@gmail.com <it...@gmail.com> #38
fl...@gmail.com <fl...@gmail.com> #39
mi...@promomasters.at <mi...@promomasters.at> #40
sc...@gmail.com <sc...@gmail.com> #41
gr...@gmail.com <gr...@gmail.com> #42
gr...@gmail.com <gr...@gmail.com> #43
2) unpredictable search result of contact: the contact is sometimes found, sometimes not found, even though the voice recognition seems correct; but the soft #37 is not guilty : Google search seems to be guilty.
3) Finally, unreliable system: Call a contact by voice recognition via a Bluetooth device such as the Jabra Freeway is too uncertain to be useful.
.
1) incapable de lancer la recherche si le téléphone est en veille
2) résultat imprévisible de la recherche de contact : le contact est parfois trouvé, parfois introuvable, alors même que la reconnaissance vocale semble correcte. Le soft de #37 n'est pas responsable, mais Google search est probablement en cause.
3) en final, système non fiable : L'appel d'un contact par reconnaissance vocale via un dispositif bluetooth tel que le freeway de jabra est trop aléatoire pour être utile.
be...@gmail.com <be...@gmail.com> #44
Just install his little program.
Thank you so much Itdevrowd!
ma...@gmail.com <ma...@gmail.com> #45
Temporary using "voice command" (big thanks to the author)
(sorry if bad english, I'm french)
jb...@android.com <jb...@android.com>
ku...@gmail.com <ku...@gmail.com> #46
ms...@gmail.com <ms...@gmail.com> #47
ri...@gmail.com <ri...@gmail.com> #48
vm...@gmail.com <vm...@gmail.com> #49
Google should remember that Android is mostly used on smartphones and bluetooth headset is a basic companion of it !!
This functionnality is implemented by every single basic cell phone. That means that Android is below this base line... Too sad for the first mobile device OS.
fa...@gmail.com <fa...@gmail.com> #50
pa...@gmail.com <pa...@gmail.com> #51
ro...@googlemail.com <ro...@googlemail.com> #52
ma...@android.com <ma...@android.com>
lu...@gmail.com <lu...@gmail.com> #53
sp...@gmail.com <sp...@gmail.com> #54
ja...@gmail.com <ja...@gmail.com> #55
I formerly had an iphone and it worked fine. Pretty disappointing...
gi...@gmail.com <gi...@gmail.com> #56
pa...@gmail.com <pa...@gmail.com> #57
af...@gmail.com <af...@gmail.com> #58
ja...@gmail.com <ja...@gmail.com> #60
ha...@gmail.com <ha...@gmail.com> #61
mi...@promomasters.at <mi...@promomasters.at> #62
yo...@gmail.com <yo...@gmail.com> #63
de...@gmail.com <de...@gmail.com> #64
my...@gmail.com <my...@gmail.com> #65
They travel by public transit.
th...@barcat.fr <th...@barcat.fr> #66
hi...@gmail.com <hi...@gmail.com> #67
- set system language to English
- reboot the phone
- try the voice dial with your bt-headset (keep the English commands in mind, you will need them later on)
- set system language back to your favourite language (in my case German)
Now the voice talks to you in your language but the commands are only accepted in English: call <name>, select <one, two, three>, cancel, OK...
I couldn't find a switch to change that. So there still seems to be an issue.
ba...@gmail.com <ba...@gmail.com> #68
Same issue with my Nexus 4 android 4.2, then 4.3.
I was looking for an answer since a long time but with the bad keywords.
Comment 60 link "solved" the issue for me.
But I don't understand why google don't fix this on its Nexus. Bluetooth is the better companion for voice search.
br...@gmail.com <br...@gmail.com> #69
ra...@gmail.com <ra...@gmail.com> #70
ra...@gmail.com <ra...@gmail.com> #71
th...@barcat.fr <th...@barcat.fr> #72
be...@gmail.com <be...@gmail.com> #73
stock HTC One mini (GERMAN!), stock Beats-WIRE-Headset.
Long press on headset button: "Initialisiere" and speech output "Bitte warten".
Nothing ever happens...
Google... try sniffing less, and working more.
ju...@gmail.com <ju...@gmail.com> #74
er...@gmail.com <er...@gmail.com> #75
fa...@gmail.com <fa...@gmail.com> #76
It has legal implications in Germany since we are not allowed to lay hands on our phone while we are driving. So the missing voice dial is really a blocker in this case!
(Nexus 4 (German) + Plantronics M55)
pa...@gmail.com <pa...@gmail.com> #77
This is a blocker.
Is there someone who know how to rise this bug?
fa...@gmail.com <fa...@gmail.com> #78
da...@gmail.com <da...@gmail.com> #79
with screen locked pushing microphone button will result in a "initialization" grey screen.
If I do it with screen unlocked everything works fine.
Nexus 5 stock rom.
ca...@gmail.com <ca...@gmail.com> #80
ca...@gmail.com <ca...@gmail.com> #81
ca...@gmail.com <ca...@gmail.com> #82
se...@googlemail.com <se...@googlemail.com> #83
sn...@gmail.com <sn...@gmail.com> #84
ja...@gmail.com <ja...@gmail.com> #85
pa...@gmail.com <pa...@gmail.com> #86
I'm really sad... No workaround...
It's a pity
ni...@gmail.com <ni...@gmail.com> #87
ni...@gmail.com <ni...@gmail.com> #88
mi...@promomasters.at <mi...@promomasters.at> #89
pa...@gmail.com <pa...@gmail.com> #90
an...@gmail.com <an...@gmail.com> #91
a....@gmail.com <a....@gmail.com> #92
dm...@gmail.com <dm...@gmail.com> #93
da...@gmail.com <da...@gmail.com> #94
a....@gmail.com <a....@gmail.com> #95
li...@gmail.com <li...@gmail.com> #96
ma...@gmail.com <ma...@gmail.com> #97
moto g + jabra cruiser 2
se...@googlemail.com <se...@googlemail.com> #98
se...@gmail.com <se...@gmail.com> #99
I choose a non free solution with KLets
Now my nexus4 do the job very well (in Français) and it looks like having a
support in many languages
regards Séb
vi...@gmail.com <vi...@gmail.com> #100
I have this issue with a Nexus 4, 4.4.4 KTU84P and Plantronics PLT-M155, Plantonics C720, Plantronics PLT_M25-M29, HCB-405. Phone set in French, plantronics devices also set in French...
pa...@gmail.com <pa...@gmail.com> #101
I discovered klets from your comment and it works perfectly on my nexus4
I'm really satisfied now
thanks again
ni...@gmail.com <ni...@gmail.com> #102
bg...@gmail.com <bg...@gmail.com> #104
kn...@googlemail.com <kn...@googlemail.com> #105
1r...@gmail.com <1r...@gmail.com> #106
sp...@gmail.com <sp...@gmail.com> #107
th...@barcat.fr <th...@barcat.fr> #108
ad...@gmail.com <ad...@gmail.com> #109
ma...@gmail.com <ma...@gmail.com> #110
On my Nexus 6 it simply doesn't want to take french language, stick to en-us, but that's another story.
Thing is Google should fix that Bluetooth/external divice voice command issue! That's a f#*king shame to see this 2 years old thread still open!
go...@gmail.com <go...@gmail.com> #111
go...@gmail.com <go...@gmail.com> #112
sc...@gmail.com <sc...@gmail.com> #113
Sony Z3 Compact, 4.4.4 Kit Kat with Plantronics Voyager 520 BT headset.
Just the "Bitte warten" (please wait) und "Initialisieren" (initialising). :(
Changed language to english, which works fine, but turning it back to german and the problem is there again.
wi...@gmail.com <wi...@gmail.com> #114
se...@gmail.com <se...@gmail.com> #115
french language, ...
yv...@gmail.com <yv...@gmail.com> #116
It solves this issue with bluetooth headsets.
You just have to set the default action to it when asked.
sc...@gmail.com <sc...@gmail.com> #117
sc...@gmail.com <sc...@gmail.com> #118
sc...@gmail.com <sc...@gmail.com> #119
If I hold the button on my headset and the phone is on, than it starts the google search, but for a voice command I have to click on the microphone button on the display.
While the phone is locked or in standby and I hold the headset button, I need to unlock the phone, the search is already loaded, but still need to push the microphone button.
Is there a way to change this?
This way it is kind of useless, since I want to start calls with voice command while driving, without the need of unlocking the phone or activating voice regocnition over the touchscreen, especially while I have the phone in my pocket.
vi...@gmail.com <vi...@gmail.com> #120
When I long press the button of any of my BT headsets, I get the OK Google environment.
I activated OK Google and made changes in Google's settings for voice recognition.
I even used Nova Launcher which makes it possible to activate OK Google on all the home screens with any language but now, OK Google works from any screen (not only home screens) without the Nova Launcher add-on for it (I have French as my default language).
And it takes input from my BT headset.
You have to configure everything accordingly in Google Settings (Search and Now/Voice)
sc...@gmail.com <sc...@gmail.com> #121
So I still need to get a least to the lock screen to start voice recognition with "OK Google".
With my iPhone I just needed to press the headset button long and the voice recognition started unlocked, locked and in standby.
vi...@gmail.com <vi...@gmail.com> #122
On my side, when I long press the button of my headset while my OnePlus One is in standby, I usually get the OK Google environment directly...
sc...@gmail.com <sc...@gmail.com> #123
Sony Z3 Compact.
Also tried turning off stamina battery mode and disabled lockscreen. Doesn't work either.
sc...@gmail.com <sc...@gmail.com> #124
Till now I just tested with my headset at home. In the car I usually listen to music with a A2DP bluetooth receiver with handsfree function (Belkin AirCast).
So I connected my BT headset and palyed music. While music is playing I can start the voice recognition by long pressing my headset button. (sometimes microphone active directly, sometimes "OK Google" necessary)
Does somebody know if there is an option to stop/abort a call before dialing in case the phone detects/chooses a wrong contact? I know that it is possible on the screen, but can this be done by voice command or headset button? Or maybe confirm the contact before dialing? With the headset button I could only end a call after the phone is already ringing.
ki...@gmail.com <ki...@gmail.com> #125
hs...@gmail.com <hs...@gmail.com> #126
Devices:
- Jabra Freeway
- Wiko Ozzy - Android 4.2.2
So much time since this issue was raised...Unbelievable!!!
ad...@gmail.com <ad...@gmail.com> #127
All worked fine and since few days grey screen with my Bluetooth car kit and my headset when i want call.
Samsung S3 LTE , KIT PARROT MKI9000 or 9200 , headset Plantronic beats.
ch...@gmail.com <ch...@gmail.com> #128
I have a Plantronics M55 and was hoping to use it with Google Now. Running everything on an Oneplus One with Android 4.4.4 and CyanogenOS 11.0-XNPH05Q.
When long pressing the headset button I hear "Please wait ..." ("Bitte warten ..."), the screen goes dark and the word "Initialize" (Initialisieren) appears on the screen. Then nothing happens until I do something against it.
Is there no solution to this what so ever?
ja...@gmail.com <ja...@gmail.com> #129
se...@gmail.com <se...@gmail.com> #130
ko...@gmail.com <ko...@gmail.com> #131
bu...@gmail.com <bu...@gmail.com> #132
Samsung S6 (5.02) with a Sony Ericsson MW600 results in a endless 'initialiseren' (dutch).
ro...@gmail.com <ro...@gmail.com> #133
lu...@gmail.com <lu...@gmail.com> #134
la...@gmail.com <la...@gmail.com> #135
fr...@gmail.com <fr...@gmail.com> #137
Cannot believe that this thread exist since 2013 without solution!!
se...@gmail.com <se...@gmail.com> #138
difficult to believe but true...
here some alternatives:
-the "lg watch R" is able to send some SMS or email, after "Ok google +
command"
-"trigger" (app) initialy for RFID command, but it could program some
icon(ex: Wave + Music)
-in one of my previous post I mentionned an no free app could help, not
perfect, but do the job (In french in my experience)
My 2 cts
ni...@nclm.de <ni...@nclm.de> #139
h....@gmail.com <h....@gmail.com> #140
ha...@gmail.com <ha...@gmail.com> #141
la...@gmail.com <la...@gmail.com> #142
It is impossible to trigger voice commands from a bluetooth device (tried from my pionneer car audio and my Plantronics headset)
I just get that initializing screen and a please wait women voice ...
la...@gmail.com <la...@gmail.com> #143
a....@gmail.com <a....@gmail.com> #144
a....@gmail.com <a....@gmail.com> #145
jo...@googlemail.com <jo...@googlemail.com> #146
fv...@gmail.com <fv...@gmail.com> #147
ti...@gmail.com <ti...@gmail.com> #148
Language is German.
mi Xiaomi Piston 3 wired headset.
fa...@gmail.com <fa...@gmail.com> #149
It's ridicolous that Google develops voice command for "Google NOW" and people can't use it without touching the screen.
SOLVE THIS the ticket is ASSIGNED from 2013 :O
ma...@gmail.com <ma...@gmail.com> #150
3.rd party solutions like voice command does not work.
Fix it please.
ve...@gmail.com <ve...@gmail.com> #151
pe...@gmail.com <pe...@gmail.com> #152
ma...@gmail.com <ma...@gmail.com> #153
I'm using a stereo Bluetooth headset, LGHBS 730.
st...@gmail.com <st...@gmail.com> #154
Setting language to German: it does NOT work!
can't be that hard to fix!
st...@gmail.com <st...@gmail.com> #155
le...@gmail.com <le...@gmail.com> #156
[Deleted User] <[Deleted User]> #157
ro...@gmail.com <ro...@gmail.com> #158
al...@gmail.com <al...@gmail.com> #159
gi...@gmail.com <gi...@gmail.com> #160
Turning phone in english it works; basically there's another menu in Google now settings: "headset". Such entry disappear when you turn in other language. I've used a logger and noticed that Google invokes a different service using italian and english so the problem is the Google app I guess.
I've sent a feedback using the app. Please all of you do the same so maybe Big G will care about not-US people sooner or later.
Anyway my workaround:
- this app helps to reassing Google now voice search to the bluetooth media button
- this app keeps the display off (English version of google now do it automatically) if the phone is in the pocket (really important if your phone is in your pocket while riding a bike or scooter as me)
- Since the app above is annoying when I'm not on my bike, I use "Automate" to turn the sensor off when Bluetooth is not working.
Known Issue: after a couple of voice command, the workaround doesn't work no more because somehow BT GNOW launches more Google apps and the microphone get stuck somehow. After some command you have to close all instances of Google App.
Description
seems to be quite close to my problem.
I have the NEXUS 4 with the actual stock ROM. No routing. I have two different kind of headsets "Sony Ericsson MW600" and "Jabra EXTREME2"
With the MW600 I was able to start the voice commands with my old Motorola Defy/Defy+ when pressing the call button. On my NEXUS 4 I get from both headsets the notification "please wait" (in German "bitte warten") as like with the Defy. Before this message the screen of the NEXUS 4 goes very short totally gray.