Related
So I feel like this should be something pretty simple. I'm trying to use voice command with the bluetooth in a VW, but when I activiate bluetooth in the car it dosen't automatically allow for voice commands. Can still use the phone, but it would be nice to be able to use voice command without having to log into the phone. I've tried turning on driving mode and that doesnt' seem to work.
Any advice?
i dont think you can activate the 'voice commands' option from the VW bluetooth. I have a VW Golf and I can only make and receive calls from the car's BT system. If I want access to anything else, I need to use the phone itself.
Yeah, that's exactly the issue I'm having. Would think that you could also use voice commands. It worked fine with the iphone, but doesn't seem to like the galaxy for whatever reason.
While you can still use the VW's built in voice commands (to dial numbers, etc.), I don't believe you can use the car's mic/speaker for the phone's voice command functionality. Since it's just an app, it can't integrate into the car's systems. You can however stream music to the car's audio system via bluetooth.
Does your VW stereo have a button that you push to initiate the voice command application? I had this problem on my Subaru as well. It wasn't launching the application that listens for voice commands when pressing the button. I installed an app called Choice Dialer (Which is actually now Hands-Free Voice Dialer) and it started working.
I'd give this a try and report back if it works.
Thanks for the responses. It actually ended up being something pretty stupid. Pretty sure it's still using the built-in BT, but it takes care of what I was trying to solve.
For whatever reason the first time it requested access to my address book ti apparently didn't work. If someone else has the problem what you need to do is make sure your phone and bluetooth are connected. While connected, open your notification screen, it will probably say there are no att notification, hit that, then it will show a request by your VW bluetooth to your address book. Accept it and now you can use the 'call whoever on mobile' functionality.
Glad you got it figured out. Having half-*** handsfree is a big step backwards after being able to throw voice commands out.
I'm hoping someone here has some *real* ideas or answers regarding this issue.
I have a handsfree Bluetooth kit in my car so that I can safely place calls while driving. This worked flawlessly with my previous Windows Mobile phones (Tilt/Tilt II). With the phone tucked in my pocket and the mobile OS “locked” I could press the voice activation button on the dashboard and easily call someone. Not so with my shiny new AT&T Samsung Galaxy S II. Now I have to dig the phone out and unlock the device before I can use my handsfree system… are we back in the smartphone dark ages?? I might as well take up texting and driving while I’m at it and forget the handsfree unit altogether.
Apparently Google in their infinite wisdom has decided already paired Bluetooth devices pose a security risk. As such, when Android is “locked” it disables any control from Bluetooth. I suppose if you work for the government or some place that you need Pentagon like security this makes sense. For the 95% of us that don’t need these draconian measures this is just plain stupid and potentially unsafe.
I've already rooted my phone. I've tried other ROMs like the latest builds of UnNamed, ICS'd Out, and CyanogenMod. None of these allow Bluetooth operation while the phone is locked (and in fact all of them introduced other issues). I've searched the forums but most similar posts go unanswered or contain nonconstructive replies (flames, unrealistic answers, etc).
I can't and won't disable ALL security. I won't give up making phone calls while driving - I'm on the road a decent amount and need to use that time productively. What are my other choices? Go buy an iPhone or a Windows Mobile unit which work "right"?? Seems like a crazy oversight by Google/Samsung/AT&T if those are my only options!
I would suggest using the official samsung Car dock, as the USB port on there has a special impedance that tells the phone to go into driving mode, which once you unlock the phone, it stays unlocked until you either lock it, or take it off the dock. It also charges your phone at the same time. However if you have a case, this will not work for you. You would need to solder up your own usb plug that has a certain impedance over some pins (theres a thread somewhere about that, its like a jig, but with different impedance) and just plug that in when you're driving, but you still have to unlock the phone at least once with it plugged in.
My clarion cz500 car stereo has no issues making or receiving calls via Bluetooth while my phone is locked.
Sent from my GT-I9100 using xda premium
My biggest gripe with Android is that BT calling does not work as well as it did with WinMo's Voice Command (which works really well considering how poorly much of WinMo worked). Initiating calls via BT is my main gripe with Android. I wish Google would get it right already. That said, I have no problems answering calls via BT even when the phone is locked.
My phone is paired with the built-in BT in my car and I have no issue with making/taking calls while the phone is locked. Maybe its a compatibility issue with your particular hands-free device?
I also have no BT problem when locked, using the standard BT in my Toyota Avalon, 2011. Running rooted, UnNamed ROM, Entropy's DD 120811 kernel.
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Miami_Son said:
For those of you who think BT calling works just fine, I have to ask, have you ever used a WinMo phone with Voice Command? If not, then you don't know how well it's supposed to work. With VC, I could touch the call button on my BT headset or BT car stereo at ANY time, get a little chime and then say the name of the person I wanted to call and have it dial automatically. I never had to touch the phone to do this. When I try this on my Cappy or SGSII I get nothing. I have to initiate the call on the phone and using voice recognition on Android is spotty, at best, and requires more steps. At least answering a call is relatively easy. I have no love for MS, but they got this part right on their phones.
Click to expand...
Click to collapse
Sgs2 does this stock with no problems via samsung/vlingo voice command app. Seems hit or miss on some custom roms. As long as device has bt turned on and had been prior paired with a headset, just have to turn headset on then hit the button on the headset. Voice prompts over headset ensue
Sent from my SGH-I777 using XDA App
I'm headed into the AT&T store tomorrow to do some definitive tests but so far I'm skeptical people who say it's working for them truly have their phone locked. The Bluetooth unit in question is a Parrot CK3100 LCD - a bit dated (3 years old) but it works flawlessly with several WinMo phones, several non smartphones (mostly Nokia's), and we just tried a friend's iPhone 3GS and iPhone 4. In all cases phonebook and voice dialing not only worked excellently it worked when the phones were truly locked and the screen off.
On the other hand the 3 Android devices I've tried all have the same problem - they won't dial out either by phone book entry or voice recognition unless you unlock the device first. The 3 devices are: Samsung Galaxy S II (AT&T), Samsung Galaxy S (Verizon), and EVO 3D (T-Mobile).
Unfortunately I don't have any other Bluetooth headsets to try out, hence my planned trip to AT&T. I plan on walking out of their either with a Bluetooth device that works or an iPhone Thanks for the replies.
I hear you. I have a Motorola FINITI bluetooth headset and it will not voice dial with the screen locked on my AT&T Galaxy SII.
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
mohitrocks said:
Is there not an option to keep it from locking? :/
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Some roms give you a quick toggle in your status bar called secure mode, this should do it.
I'm on villain rom with jaykay mod quick toggles and i have that options.
Sent from my GT-I9100 using xda premium
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
GeorgeP said:
My stock phone is paired with the built-in BT in my car. I also have I have no problems with making or receiving calls while the phone is locked.
I can also make calls using voice dial when the phone is locked using my plantronics BT headset.
Click to expand...
Click to collapse
Are you using a pattern/pin lock? Or just the slide to unlock.
Just slide to unlock.
It works very well and very straightforward. I just press and hold the call button on my headset (while the phone is locked), and then after the tone say, "call John Doe on mobile" and it works.
Something for OP to consider in troubleshooting why he is unable get this work:
The BT voice dial works through the older pre-installed Vlingo (version 2.x). Even though I have the newer version (3) of Vlingo installed, the phone still launches the older preinstalled version of Vlingo for BT voice dial. So it seems the BT voice dial function is in some way hardcoded to that version of Vlingo.
Perhaps OP is using a custom ROM in which the older pre-installed Vlingo is removed(?). I know that is the case with some of the custom ROMs for the Int'l SGS2.
If I were to freeze or remove the older version of Vlingo, that might impact BT voice dial. Although I wouldn't expect it to affect the use of my phone through my car's build in BT.
Try it with a pattern lock or some kind, I believe that is what the OP has and its what "locks" the phone from using BT dialing, whether its voice based, or address book based from a headunit.
OK, if OP means that type of lock, then, no you cannot make a call when locked.
Although, it is not clear to me why one would want BT to bypass the lock in this manner. It seems the PIN or pattern lock would be pointless. If the phone is stolen (or lost) the person who stole it (or found it) could have access to your phone's contents through bluetooth. Am I missing something?
Definitely missing something. He wants the phone to be able to make calls while the phone is locked which is why i suggested to keep it unlocked by enabling driving mode through the mount.
My point was that allowing bypassing the lock through BT creates a exposure many would not want. The simplest solution might be keeping it unlocked either using a mount as you suggest, or using one of the profile apps that lets you create a profile to keep the phone unlocked when plugged in. He could then plug it into the car power adapter.
I use a pattern lock, and can make calls through the built-in BT in my car when the phone is locked. I can dial on the car's touch screen (disabled when the car is in motion, except for pre-set speed dials), or tell it to call someone by pressing a button on the steering wheel and saying the name. The car BT compares the spoken name with the list of contacts from my phone that have been BT-loaded into the car's contact list. Nevertheless,the call is made though the phone, since the vehicle BT is not itself a phone. Has anyone noticed that we have not heard again from Rajah, the originator of this thread? Rajah, are you there? Were your issues resolved?
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
HI Wizards
I must inform you for the following
I have installed the latest I9100G nightly - cm-9-20120730-NIGHTLY-i9100g.zip
2 problems are repeat themselves all releases
1. In PC - 'Device Manager' can't recognize device's Bluetooth properly - it says that drives cannot be found (a specific one)
2. In Car - I have a Bluetooth Speaker installed in my car. (Nokia CK-100, if required)
When I make an outgoing call everything works properly both sides are speaking and hearing each other
BUT
When I receive an incoming call device isn't recognize as BT connectivity and I can NOT hear or speak via car's microphone. I must use it as handset.
It is a known issue - I saw much of CM9 for I9100G users that complained this problems
Are there any suggestions to fix it??? Does someone know the source of this problems??????
Police might be caught me speaking without BT speaker and then I will get a report....
Trust'n you... tnx
When receive or dial out, my Nokia BH-102 mono bluetooth v2 works for CM9/CM10, but not Jabra Easycall v3 bluetooth. However music streaming works for Jabra mono headset.
Having problems with the speech feature with my car's bluetooth.
My 920 pairs fine with my car's bluetooth, and I can receive calls fine.
However, the speech feature where it reads incoming text messages is not working. Under Settings > Speech, I've got all the checkboxes checked, and I've tried everything from "Always On" to "Bluetooth and headsets" but nothing works. I receive a text, my phone plays the notification sound, and then nothing.
With my previous WP7.5 device (HTC HD7), this feature worked flawlessly with my car and other bluetooth headsets. Unfortunately I got rid of my headset so I can't test it with my 920.
Interestingly, I once made a call, and while it was still ringing, I got an incoming text message and bam - my phone spoke over the active bluetooth session and prompted me whether I wanted the message read aloud. The call went through and the phone was unable to pickup any commands.
Also, starting a voice command, while my phone is actively paired with my car, the phone can no longer "hear" my voice commands. Like it thinks it initiated the bluetooth session, but in reality it hasn't.
Anyone else having similar problems, or better yet, a solution??
I can only think of something to try out to get a little more information on the scope of the problem.
You could turn it to always on and try sending a text message to the phone while it is not connected via Bluetooth (e.g. at home while having the device on the table) and check wether it works then. If so, then it seems the problem is with the compatibility of the phone and the car's bluetooth.
Hi StevieBallz - gave that a shot and yes, that works. It seems there are some other people with this issue reported on various other sites. Which is a real bummer.
Played around with it some more, and it definitely seems like the phone thinks it has initiated the bluetooth "call" and is reading out commands to nowhere, and unable to hear commands as well.
I would say this is a bug and not mere incompatibility issue. If they had it working fine on WP7.5, there's no reason they couldn't implement it the same way
Given that they are now using the Windows 8 Bluetooth Stack instead of what was there in Windows CE I would say there are several reasons why it's implemented differently but that's not really the point. If there are other people with incompatibility issues that might lead to a fix down the road. The more interesting question though would be if there are Bluetooth pairings where this works with the 920, because if it doesn't work with any Bluetooth devices I guess that would get fixed pretty soon.
I fear I can't give you any more advice than to contact support on your issue so that they get aware of the situation (because I guess Nokia won't be scouting forums for all kinds of possible bugs). I hope they will fix the functionality for you soon.
PS: I can't count the number of times I've seen issues with Bluetooth. No matter what devices I use, Bluetooth still seems very hit and miss Working with the BMW Bluetooth but only partially but working fine in an Audi. Sometimes only with Blackberry, etc. One would believe if there is a standard they would get all this sorted out someday but somehow they don't.
ultrabob said:
I would say this is a bug and not mere incompatibility issue. If they had it working fine on WP7.5, there's no reason they couldn't implement it the same way
Click to expand...
Click to collapse
It works on my car ('10 nissan). It works on some cars/bluetooth stacks, and not others. This, by definition, is a compatibility issue. Now, why this stack fails against other stacks, when the CE stack worked, is a good question.