Database Users

Google Voice now available on Market

Google Voice showed up on the Market and also Amazon. It's functional but does not include call-out capabilit as I had hoped. It will do voicemail and text message but you still need GrooveIP if you want to be able to do Voice over Google Voice
You have to have a GV account set up and a GV number, but it's goovy. I don't have GrooveIP yet but am seriously considering it at $5. I've got a cool pair of noise reducing BT headphones that have a mic, so I might as well.

Ive been using grooveIP on my no service DX via google voice and it works great. I can only imagine it'll work fine on the tab.
Its certainly worth the 5 bucks.

It had been available for week at least, but since I didn't find the call button, I am not too much a fan. I complaint on google's forum about the GV for Tablet. Does the GV for phone has a call button? I think it does. I don't have an android phone.

GrooveIP was on sale on amazon last week for $2....i just missed it too

When adding the widget look at the messages it shows funny stuff
Sent from my A500 using xda premium

mknewman said:
I've got a cool pair of noise reducing BT headphones that have a mic, so I might as well.
Click to expand...
Click to collapse
I don't think Bluetooth microphones work (yet), just the stereo A2DP. I've tried really hard to pair a Plantronics Savor M1100 which does both regular hands-free microphone and A2DP audio... but Honeycomb 3.1 only shows the A2DP profile.
However, I'd love to be proven wrong! I use Google Talk / Video Chat a lot so it would be a very welcome addition.

On my Android phone it allows you to choose if you always want to use GV for calls, ask every time, never, or only for International calls. It uses the stock dialer, which is where GrooveIP comes in. My reluctance in buying GrooveIP is it would seem a natural fit for Google to include outbound calling for tablets, so there would be no need for it. My guess is eventually Google will buy GrooveIP (they buy everyone!) and it'll become closely integrated.
ctiger said:
It had been available for week at least, but since I didn't find the call button, I am not too much a fan. I complaint on google's forum about the GV for Tablet. Does the GV for phone has a call button? I think it does. I don't have an android phone.
Click to expand...
Click to collapse

Nexus 4 hands free problems

First post here, so apologies and let the flaming begin but I am trying to determine if my Nexus 4 "issues" are unique to me or normal for this phone.
1. Issue #1 - Bluetooth functions only for numeric dialing, no voice (say name phonetically) dialing or other voice actions seem to work. You can speak the numbers you wish dialed and that's about it. Maybe others can confirm whether this is unique to me. Android ver 4.2.1. Using with a Sena SMH10 bluetooth motorcycle headset
2. Minor issue, but also related - I can not use a stereo headset with my phone and expect the handset mic to work. Something that simply works in every other smart phone I've owned. You plug in a stereo headset (3 conductor earbuds only, not 4 conductor with mic for example) and the phone ideally recognizes the lack of 4th conductor and sends output audio to headphone while using handset mic. So, if you wish to make a call, you can do so. And if you wish to communicate with your phone using verbal commands you may do so as well. You may get "some" functionality using a 3 conductor headphone, however try making a call to someone and it simply doesn't work.
I don't think my phone issues are unique, but perhaps I got a lemon? Nexus support can't seem to confirm whether or not its a known issue.
Anyone else have these "features"?
Thanks in Advance.

Issue #1. Confirmed hands free dialing works over Bluetooth using blue ant s4. In fact I was excited they actually reworked the voice dialer to be accurate!
Sent from my Nexus 7 using Tapatalk

Well that's certainly weird. The headset I am using lists the following profiles:
Key Specifications:
• Bluetooth v2.1+EDR, Class1
• Supporting profiles: Headset Profile, Hand-Free Profile (HFP), Advanced Audio
Distribution Profile (A2DP), Audio Video Remote Control Profile (AVRCP)
The Settings tab of this headset in my Nexus say it is paired for:
-Phone Audio
-Media Audio
I have paired/unpaired and reset bluetooth device to factory.
This headset worked flawlessly with my previous phone, an HTC MyTouch 4G running Android 2.3
When i attempt a call, I get a prompt from the phone "Voice Dialer" that says:
"Say Call, followed by a name or a number"
If i speak the numbers to dial, it works perfectly. If I say the name of any person in my google contacts list, it balks and exits right away, sometimes saying "Sorry, I didn't catch that"

HF Dialing has been horribly broken in Android for some time. You might try disconnecting it from A2DP to see if that helps. For me, since I use a moto headset, I went with Motospeak and it works pretty well.

chas4android said:
2. Minor issue, but also related - I can not use a stereo headset with my phone and expect the handset mic to work. Something that simply works in every other smart phone I've owned. You plug in a stereo headset (3 conductor earbuds only, not 4 conductor with mic for example) and the phone ideally recognizes the lack of 4th conductor and sends output audio to headphone while using handset mic. So, if you wish to make a call, you can do so. And if you wish to communicate with your phone using verbal commands you may do so as well. You may get "some" functionality using a 3 conductor headphone, however try making a call to someone and it simply doesn't work.
Click to expand...
Click to collapse
This works fine for me. I've used it a number of times in the car, where I have a stereo cable to an FM transmitter, and I just tested it with a no-microphone set of headphones: my voice went through the phone microphone with no problems.

chas4android said:
Well that's certainly weird. The headset I am using lists the following profiles:
Key Specifications:
• Bluetooth v2.1+EDR, Class1
• Supporting profiles: Headset Profile, Hand-Free Profile (HFP), Advanced Audio
Distribution Profile (A2DP), Audio Video Remote Control Profile (AVRCP)
The Settings tab of this headset in my Nexus say it is paired for:
-Phone Audio
-Media Audio
I have paired/unpaired and reset bluetooth device to factory.
This headset worked flawlessly with my previous phone, an HTC MyTouch 4G running Android 2.3
When i attempt a call, I get a prompt from the phone "Voice Dialer" that says:
"Say Call, followed by a name or a number"
If i speak the numbers to dial, it works perfectly. If I say the name of any person in my google contacts list, it balks and exits right away, sometimes saying "Sorry, I didn't catch that"
Click to expand...
Click to collapse
I understand your frustration. Hands free dialing is a feature I don't like to do without. After jumping to jellybean from ICS on my fascinate handsfree was horrible.
When I set up my blue ant with any phone it goes through a "transferring contacts" part of the setup. Perhaps this is why it can recognize the peoples names and not just the numbers.
Does your headset "transfer contacts" like the S4?
Sent from my Nexus 7 using Tapatalk

No, the headset is strictly a phone headset as far as that goes. Not a sync device like some cars, etc. In that case, it might work since dialing could be handled by the Bluetooth device?
I'm no expert, but relying on the nexus dialer seems to be the issue. What baffles me is that when not using Bluetooth and using the Google voice search, it actually works. If pressing the "pickup/hangup" button actually launched Google voice actions... It would solve the problem as well as give me further hands free operations such as nav and music control.
Anyone know how to make that action occur with Bluetooth button?
As for #2, I actually called nexus device support, and while speaking to the rep plugged in my skull candy ear buds. He confirmed that mic sounded extremely garbled and not understandable. These same ear buds world fine on my old my touch and my girlfriends iPhone. Both of those phones recognize them as basic stereo headphones and keep the handset mic intact.
I'm going to call them back and just get a replacement today. Screen has done the flicker/vertical lines thing now at least once too.

I'm having bt issues with my car stereo. It's after market that worked fine with my GNex. I can pair it with the N4 and it shows Phone Audio, but then after a few seconds disconnects. Could bt be bad on my N4? I normally have the headphone jack plugged in through aux and can take calls that way, but I'd like to get bt working again.
Update: after powering off the stereo and powering it back on it seems to be connecting ok

Lttlwing16 said:
Issue #1. Confirmed hands free dialing works over Bluetooth using blue ant s4. In fact I was excited they actually reworked the voice dialer to be accurate!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Just checked... Blue ant uses its own voice recognition to pair contacts with numbers and thereby bypasses phone voice dialer. That's why it works for you.

I just got a SMH10 as well. I am able to voice dial okay as well as use google music, what I don't like is no access to Google Now without handling the phone (which would require me to stop and get my phone out of my pocket). Not sure if this is an issue with the SMH10, or with android 4.2.x.
I know it's been over a month since you posted in here, curious about your usage and if you have found any tricks to get google now to work in place of the voice dialer only. Since google now should handle voice dialing I am hoping to get that to work so I can also use the navigation when needed.
Sending a note to Sena as well to see if they have a solution as well.

Hands free out-calling issue
As of last week the bluetooth hands free calling feature was working fine on my Nexus 4. A couple days ago I went to call out using the hands free, and the display on my car stereo went blank for a few seconds and came up saying 'Not Supported'. I can receive calls fine, but for whatever reason the hands free voice recognition doesn't want to open when I ask it to now. Anyone have a similar problem?

ssj4kevin said:
As of last week the bluetooth hands free calling feature was working fine on my Nexus 4. A couple days ago I went to call out using the hands free, and the display on my car stereo went blank for a few seconds and came up saying 'Not Supported'. I can receive calls fine, but for whatever reason the hands free voice recognition doesn't want to open when I ask it to now. Anyone have a similar problem?
Click to expand...
Click to collapse
I've had exactly the same thing happen. Weeks and weeks of working voice dialing through my Blueant S4. Now, it doesn't work at all. Incoming calls can be answered, but I can't dial out by voice.

Nexus 4 4.2.2 and RNS 315 car system issues/tweaks

Hi,
I am a happy switchover to Nexus 4 from my iPhone, only thing I am starting to miss are some integration bits with my car audio system.
I am currently connecting the phone via bluetooth and it is working well, I can stream music and use built-in car dialler, however, I do not see what is currently playing on the car dash.
When I had the same setup using iPhone, I could see the currently playing song information. I can still skip to the next song using car's steering wheel buttons but I only see "Bluetooth audio" on the display.
I am using the default Google Play app to play music - have also tried with dogcatcher but no avail. On the iPhone various app worked - Music, Podcasts..
Second issue I have - is it possible to "force" phone calls to background when connected to bluetooth headset? I would quite prefer the satnav to stay on instead of seeing the current caller's information - as I already see that on my dash.
Thanks!

zard_cz said:
Hi,
I am a happy switchover to Nexus 4 from my iPhone, only thing I am starting to miss are some integration bits with my car audio system.
I am currently connecting the phone via bluetooth and it is working well, I can stream music and use built-in car dialler, however, I do not see what is currently playing on the car dash.
When I had the same setup using iPhone, I could see the currently playing song information. I can still skip to the next song using car's steering wheel buttons but I only see "Bluetooth audio" on the display.
I am using the default Google Play app to play music - have also tried with dogcatcher but no avail. On the iPhone various app worked - Music, Podcasts..
Second issue I have - is it possible to "force" phone calls to background when connected to bluetooth headset? I would quite prefer the satnav to stay on instead of seeing the current caller's information - as I already see that on my dash.
Thanks!
Click to expand...
Click to collapse
The first problem is caused by you and other people buying iPhone. You have contributed to pushing 3rd party manufacturers into supporting proprietary apple formats and communication protocols.
There is a perfectly fine Bluetooth protocol for track display, but your car stereo doesn't suport that, only the proprietary Apple one.
Hopefully you are now aware of the evil lock-in tactics that Apple have been engaging in, and next time you will check the product specifications to see see if your purchase is going to lock you in in any way.

Volkswagen and their bluetooth devices work fine with Android. It's Android that lacks a proper protocol to push that info to the radio. I know this because I worked with VW for months on troubleshooting the issue. Eventually, I obtained a stock galaxy S3 and it displays info just fine. With a custom 4.2.1/4.2.2 rom, it does not, just displays "BT-Audio".
CM is adding in bt tag support, but it currently doesn't work with play music, but is noted to work with pandora.
OP - your second issue is not possible. The radio automatically flips to the most recent info it has to display to you. You can manually toggle it back IIRC, as I can on mine.

I have the same issue:
See thread which explains a lot and could solve your issue:
https://productforums.google.com/forum/?fromgroups#!topic/mobile/5lTaNBEBJMU
http://rootzwiki.com/topic/20091-request-avrcp-13-for-cars-w-bluetooth-built-in-etc/page__st__20
http://forum.frandroid.com/topic/11...ense-ota-cm101-nighlty-20130304/page__st__460
We need to get AVRPC in our devices then it would work.
I drive an A5 SB with no go : ( to bad

yea the bluetooth works on my ford focus, but doesnt show the info of what track is playing.

Bluetooth calling / contacts in-car

So I took delivery of my shiny new Nexus 4 yesterday at work and as soon as I got in the car I paired up the bluetooth. Then somebody called me and the steering wheel controls wouldn't answer the phone. I've tested this several times now and that seems to always be the case. If I initiate a call from the phone though, it does relay the call over the bluetooth.
Secondly, the car cannot see the contacts in the phone. It just either tells me that 'no phonebook is available' or 'the phonebook is empty'. The car has never asked me for permission to read the phone book, even though I have unpaired, factory defaulted (the car B/T) and re-paired several times.
I had similar issues with my HTC Sensation when running 4.2 but the Sensation and car worked flawlessly together when using a Sense-based ROM.
Does anybody have any fixes for these issues? Not being able to use the car controls is a bit of killer to be honest. Not displaying the phone book is not great but at least if the car can control the phone I can use it to answer calls. I tried installing Bluetooth Phonebook but it didn't seem to make any difference.

Radio out car if using stock radio would really help here. I have JVC in the double din in the Saab and an eclipse in the wrx. JVC works as designed most of the time after the new update. Eclipse does not support PBA protocol. But controls work (minus pause on Google play app)
Sent from my Nexus 4 using xda app-developers app

This one is still frustrating me. I have discovered that if I initiate or answer a call on the phone itself, it plays through the car speakers perfectly but it isn't possible to control the phone from the car controls.
I believe the problem is at least in part that I haven't had the pop-up on the phone with the car asking for permission - I did see it once after leaving the car but when I sent to activate it, the prompt disappeared.
So my question is still: Is there a way to force that permission setting, and if not does anybody have a workaround?
Sent from my Nexus 7 using Tapatalk 2

I'm in the same position
I've had my Nexus 4 for about a month. It worked fine 100% with my car till (coincidentally??) I went from the stock kernel to faux123's.
I have a 2008 Audi A6, which only allows voice - no option for streaming music across unfortunately. The phone paired, I Ok'ed the request to share call history, checked the "don't ask again", and I could make and receive calls from the car's controls. So far so good, just like my previous Gingerbread phone.
I don't think the new kernel was to blame - could it have been a google apps update? - but since then I can delete and re-pair the phone, I OK the share call history and "don't ask again" option, BUT the car's controls don't initiate or answer calls.
I went back to the stock kernel, tried Franco's, just moved to ParanoidAndroid's latest ROM+kernel - with all the necessary wipes - still no luck with getting the car's controls to work. I can start a call from the phone, or answer an incoming call on the phone, and it will play through the speakers, but it's a royal PITA, as well as illegal and dangerous.
So, I guess it ain't the kernel, but I just can't work out what changed. I have frozen Google+, Google Search, plenty of reboots and wiping the pairing off both devices.
I've done a good few searches, and it seems Google have never had a really clean bluetooth stack, and Volkswagens/Audis seem to suffer more than others.
But my Desire HD worked like a dream

paul c said:
I'm in the same position
I've had my Nexus 4 for about a month. It worked fine 100% with my car till (coincidentally??) I went from the stock kernel to faux123's.
I have a 2008 Audi A6, which only allows voice - no option for streaming music across unfortunately. The phone paired, I Ok'ed the request to share call history, checked the "don't ask again", and I could make and receive calls from the car's controls. So far so good, just like my previous Gingerbread phone.
I don't think the new kernel was to blame - could it have been a google apps update? - but since then I can delete and re-pair the phone, I OK the share call history and "don't ask again" option, BUT the car's controls don't initiate or answer calls.
I went back to the stock kernel, tried Franco's, just moved to ParanoidAndroid's latest ROM+kernel - with all the necessary wipes - still no luck with getting the car's controls to work. I can start a call from the phone, or answer an incoming call on the phone, and it will play through the speakers, but it's a royal PITA, as well as illegal and dangerous.
So, I guess it ain't the kernel, but I just can't work out what changed. I have frozen Google+, Google Search, plenty of reboots and wiping the pairing off both devices.
I've done a good few searches, and it seems Google have never had a really clean bluetooth stack, and Volkswagens/Audis seem to suffer more than others.
But my Desire HD worked like a dream
Click to expand...
Click to collapse
I have no problems with bluetooth, calling or music streaming, in my 2013 Ford Focus using Ford SYNC. I'm stock 4.2.2.

Check tune2air BT adapter from viseeousa.com. My mom let me use her car and I want to stream music in it but I can't seem to do it in her car. So I found a solution, bought the WMA3000A with built-in AMI cable and i have BT steaming, and able to control, read, ,display music using original steering wheel and head unit controls. You can also check and try the 30pin WMA1000 model which plugs into any 30pin iPod integration cable.

Is this a Beta P issue or problem in general?

I noticed that my phone no longer responds to voice commands through BT. I have a Sena 20S system in my motorcycle helmet. I used to be able to hit the button on my helmet, and I would hear the Google Now/Assistant tone, and I could say "Call XYZ" or "Play Music" or whatever...
Now, it does nothing. I checked all the settings and "enable voice commands from BT" and that stuff is enabled.
When I am on a call, the mic works and everything works as it should. I just can't issue any voice commands to the phone unless I use the phone's mic.
This may be a difference issue, but I also see that Google Assistant no longer allows me to search or play my music. I can have 500 songs downloaded to the phone, but I can only select them or even play any of them manually. Voice commands no longer work for downloaded music. Apparently I have to pay $10 a month for Google's Play Music service for voice command functions on music that I already own? Seems that Google is trying to out apple, Apple... LOL
Anyone know what's up with the first issue? No voice commands at all through BT?