TCL 55P735 no hands free? - Philips, Sony, TCL Android TV

Hello,
does anybody have hands free on a TCL 55P735 TV succesfully activated? I recently bought it and everything works, except that.
Voice recognition and google assistant work if I press the dedicated button on the 2nd remote. But it's not working hands free as advertised on the box and online.
I have switched on the on TV mic (the hardware button at the bottom center), the TV reports the mic's state correctly (TV microphone is on) and the 4 leds go white, then turn off.
Settings: google account ok, google assistant voice control on, quick start activated, screenless servive activated.
But, hands free voice recognition...
Anyone else has this problem?
Thanks

Related

[Q] Can't use bluetooth headset's button to voice dial

I have a Plantronics BT headset that I've been using for years.
It has a "main button" that, when long-pressed, starts a voice dialing dialog with the phone, even when the phone is locked.
Or it did, from the original Captivate running Froyo all the way to my Kit-Kat GS3.
This no longer works on the G4. I get the beep indicating that the long press was registered by the headset, but nothing happens on the phone.
I know I can use "OK Google" to call Google's Voice Search and then tell it to dial, but that only works when the phone is unlocked and the screen is on, which defeats the whole point of hands-free operation.
LG's Voice Mate simply sucks, at least through my Plantronics. It doesn't capture voice input, it interrupts it half a second after it starts listening... It is unusable.
Does anyone have an idea how to enable the good old voice dialing through a BT headset? OK, it was ugly and idiotic with its stupid "Select 1 for mobile..." prompts, but it worked.
It doesn't have to be that. As long as I can voice-initiate a call without fiddling with the phone, I'll be happy.
The G4 turned out to be a great phone, but this particular issue is irritating to me.
I have the same problem with my company-issued Rugby Pro running Jelly Bean. Samsung's S Voice is hit-and mainly miss. My old Rugby II flip was always ready to dial or answer if Bluetooth was on. I use it on a motorcycle, so no button pressing on the phone is possible. I have been trying utter! (still in Beta) the last few days, and it is the most promising that I've found, although it has way too many other things it tries to do. Otherwise, I'll have to try and swap this phone with someone for a i(don't even want to start using these)phone, or go back to the flip and just carry the Pro for use via wifi to get company email.
Voicemate is garbage.
Go into apps under settings and disable as many Voicemate related items as possible.
This will cripple Voicemate and Google voice search will launch on Bluetooth press. It works beautifully.
All the commands I've tried work. One of my favorites is "play <song name>" if you have Google music all access.
http://www.greenbot.com/article/2359684/a-list-of-all-the-ok-google-voice-commands.html
Sent from my LG-H810 using XDA Free mobile app

Google Assistant with Bluetooth Headset?

Is there an app or a way to launch Google assistant with Bluetooth headset button? I've Googled and Googled but haven't found any actual app to do this yet, Bluetooth settings in my Google app are all turned on
Yasharkhan said:
Is there an app or a way to launch Google assistant with Bluetooth headset button? I've Googled and Googled but haven't found any actual app to do this yet, Bluetooth settings in my Google app are all turned on
Click to expand...
Click to collapse
No setting. It just works for me. Try turning off contact sharing for that device, I think that may have helped someone with a similar issue
Sent from my Pixel 2 XL using Tapatalk
I can not trigger it with my Jaybird X3 on my P2XL either. Lots of searching and Google Assist searches on web, G+ and Google Product forums, and Google help. Nada.
I think this was fixed in 8.1, but this supposedly worked for earlier versions: In Settings, Google, Voice, toggle off Bluetooth headset (Records audio through Bluetooth headset if available).
I'm on the 8.1 January security update with a Plantronics Voyager 5200 and it works for me with the toggle on.
Didn't work with 8.0 for me (LG headset) no matter what, but works without any effort on my part with 8.1 update. But the prox sensor is borked with 8.1 while BT connected, as the screen doesn't light up on incoming calls
JimSmith94 said:
I think this was fixed in 8.1, but this supposedly worked for earlier versions: In Settings, Google, Voice, toggle off Bluetooth headset (Records audio through Bluetooth headset if available).
I'm on the 8.1 January security update with a Plantronics Voyager 5200 and it works for me with the toggle on.
Click to expand...
Click to collapse
Well, thank you Jim. That was counter intuitive, but it worked. I toggled it off, then with the screen on and hold the BT HS button, GA came up, I turned the screen off, hold BT HS button and the voice prompted me to turn the screen on and accept the notification to use my BT headset with the device locked. Now it works. :cyclops:
Pkt_Lnt said:
Well, thank you Jim. That was counter intuitive, but it worked. I toggled it off, then with the screen on and hold the BT HS button, GA came up, I turned the screen off, hold BT HS button and the voice prompted me to turn the screen on and accept the notification to use my BT headset with the device locked. Now it works. :cyclops:
Click to expand...
Click to collapse
My pleasure sir! After all of the help you've given me, I am more than happy to give one back to you!

“Hey Google” doesn’t activate car Bluetooth

Something I really liked about my iPhone is that I could hold down the voice assistant button on my steering wheel (2019 Ford) and it would activate Siri.
Or, I could say “Hey Siri” and no matter what input was selected, the car Bluetooth would activate to listen/respond to commands.
I got my Note 10+ and of course holding the car voice assistant button does not activate Google Assistant (I knew this going in). But I kind of expected to bey able to say “Hey Google” and have it mimic the “Hey Siri” functionality by activating the car Bluetooth to listen/respond.
Is there a way to get the Google Assistant to activate the car Bluetooth to listen/respond when saying “Hey Google” ?
Edit: I realize this works when you plug the phone into the car's USB port and use Android Auto from the car; however, it would be nice to have to not plug in the phone to get this to work. I know -- first world problems.
Thanks!
Try with ok google
I need to dial an invalid number to wake up my phone then use "ok Google".
The annoying issue is that the sound still does not come through the bluetooth in my car, only on the Phone. Like you I find this inferior to my previous Windows phone that worked well in the car through Cortana.
Wintrmte said:
Something I really liked about my iPhone is that I could hold down the voice assistant button on my steering wheel (2019 Ford) and it would activate Siri.
Or, I could say “Hey Siri” and no matter what input was selected, the car Bluetooth would activate to listen/respond to commands.
I got my Note 10+ and of course holding the car voice assistant button does not activate Google Assistant (I knew this going in). But I kind of expected to bey able to say “Hey Google” and have it mimic the “Hey Siri” functionality by activating the car Bluetooth to listen/respond.
Is there a way to get the Google Assistant to activate the car Bluetooth to listen/respond when saying “Hey Google” ?
Edit: I realize this works when you plug the phone into the car's USB port and use Android Auto from the car; however, it would be nice to have to not plug in the phone to get this to work. I know -- first world problems.
Thanks!
Click to expand...
Click to collapse
Mine works both ways in my 2018 civic, wife's 2016 CRV, and my 2003 S10. Double check your hands free settings
Thanks for the responses but I'll take a video to show what I am talking about. It seems so simple yet I don't get why it won't work with Android.
Tidbits said:
Mine works both ways in my 2018 civic, wife's 2016 CRV, and my 2003 S10. Double check your hands free settings
Click to expand...
Click to collapse
Thanks for sharing your settings. My Google Assistant is configured identically and it still doesn't do what I am referring to.
When you are listening to say the Radio, and you say "Ok Google", does your radio immediately switch to Bluetooth mode and then listen/respond to you?
Wintrmte said:
Something I really liked about my iPhone is that I could hold down the voice assistant button on my steering wheel (2019 Ford) and it would activate Siri.
Or, I could say “Hey Siri” and no matter what input was selected, the car Bluetooth would activate to listen/respond to commands.
I got my Note 10+ and of course holding the car voice assistant button does not activate Google Assistant (I knew this going in). But I kind of expected to bey able to say “Hey Google” and have it mimic the “Hey Siri” functionality by activating the car Bluetooth to listen/respond.
Is there a way to get the Google Assistant to activate the car Bluetooth to listen/respond when saying “Hey Google” ?
Edit: I realize this works when you plug the phone into the car's USB port and use Android Auto from the car; however, it would be nice to have to not plug in the phone to get this to work. I know -- first world problems.
Thanks!
Click to expand...
Click to collapse
From my past experiences , O K google should work with Bluetooth connected .?
I have a old Pioneer radio DEX_X3950BT model( in my car) and OK Google works , 95% of the time .!
I have to press and hold, the call button icon ,on radio face plate, which simulates a long press on my phone . I have Nova Prime as my launcher ( device) and it is configured in Nova settings /Gestures, to launch Google Assistant, on launcher homepage .
Also data connection must be enabled on device .
I also have OK Google, always listening ,enabled .
I have used this method (on and off) plenty of times to launch OK Google eg.... to send sms /weather or make phone call ,.
I have used this method with my old Note devices eg Note 8/9 .
Bottom line ,
Haven't really tried it with my Note 10+ ,
as i hardly use my car . (these days ) also thus also had no need to .
If it was working with my old devices ,it should work with Note 10 .??
Thus ,from my past experiences ,You can launch OK Google via Bluetooth..!
I really never had any issues launching OK Google via Bluetooth from my car radio .
I also believe it obviously depends, on car radio capabilities/specs , device settings etc .)
Good luck .
Wintrmte said:
Thanks for sharing your settings. My Google Assistant is configured identically and it still doesn't do what I am referring to.
When you are listening to say the Radio, and you say "Ok Google", does your radio immediately switch to Bluetooth mode and then listen/respond to you?
Click to expand...
Click to collapse
It is always connected even when listening to the radio.

Voice assistant via bluetooth - no Alexa if screen is off

Hi All
Had android phones for decades, and used in combination with Alexa for several years. All of a sudden though on my S20 plus I am unable to get alexa activation via bluetooth to work consistently.
Previously long pressing the voice assist button in my BMW would call up the voice assistant on my phone via bluetooth. I'd here a beep, and be able to utilise Alexa to ask for music on spotify or whatever. Obviously the S20 came set with Bixby, and this same functionality worked with Bixby - but I prefer Alexa so changed away to that. What I am finding now though is that it will only activate alexa if the screen is on. If not I press and nothing happens. The next time I switch the screen on Alexa pops up. Also I dont seem to get the beep if I activate with the screen on. Does anyone have any ideas?
Thanks
Dave

Question No Google voice commands when smartwatch is connected

Hey guys, pretty sure a lot of people out there are using a smartwatch along with their Pixel so maybe someone can help me with this: when my Galaxy Active 2 smartwatch is connected most of the time I can not use voice input with Google Assistant / search. When I wake up the Assistant by long-pressing power the device starts listening but apparently can't hear me. When I disable Bluetooth or power off the watch everything's working just fine.
The weird part is this though: most of the time the watch is connected, a Bluetooth icon with two dots on the left and right can be seen in the status bar, but not always! And only when the icon is NOT there, while the watch is STILL connected and fully usable, voice commands DO work! What on earth is going on there?
Same thing with the camera app: when the watch is connected and the icon is there, the cam app tells me a Bluetooth microphone is connected. When the watch is connected and the icon is NOT there, the app doesn't tell me. With the cam it is not a problem either way though because here I can choose what audio source I wanna use, while in the Google app I can't.
Any ideas?
It seems that your Galaxy Active 2 gets recognized by the P6 as a Bluetooth microphone capable device, ergo it won't use the in-build phone microphones.
Does it have microphones, by the way?
You can always change the system "primary" source of a microphone/sound source by going into the Sound menu (press volume rocker, press on three dots, change there or go into See more).
Morgrain said:
You can always change the system "primary" source of a microphone/sound source by going into the Sound menu (press volume rocker, press on three dots, change there or go into See more).
Click to expand...
Click to collapse
Yeah I'm looking for a way to do that, change primary audio source, but I don't see any options for that in the sound or any other menu...
I'll add another bug to the list.
When a watch capable of making and receiving calls (Huawei Watch GT2 Pro) is connected, initiating a phone call from a BT headset/earbuds starts a phone call through the headset, but as soon as the phone call connects, the audio switches from BT headset to phone internal speaker.
You have to disable the "phone" function of the BT settings for the smartwatch to get this to work properly.
This didn't use to be the case, so it's clearly a new bug either in P6P or Android 12.

Categories

Resources