Hi, does anyone know if voice dialling via a bluetooth headset is possible on the Note 2?
On the original Note I've used Voice Speed Dial from Cyberon very successfully for this and apparently it also works on the S3. As soon as I get my Note II next week I'll be installing it, hoping it will work.
dosher said:
On the original Note I've used Voice Speed Dial from Cyberon very successfully for this and apparently it also works on the S3. As soon as I get my Note II next week I'll be installing it, hoping it will work.
Click to expand...
Click to collapse
Can you let me know how you get on please?
Related
is there a download or fix for the bluetooth voice command....my bluetooth works but when i push the button on the bluetooth it says give command and then there is an error followed by, it disconnects. any advice on what to do or where togo to get the fix for this problem?
I've not been following the latest news on Epic, but if Sprint has released 2.2 I think you need to manually update your phone. Though from what I've read in the previous days was that Sprint did send out an update to some Epic users but the update was buggy. Therefore not everyone had their phone updated. Though assuming you're new to this forum ? And perhaps your Epic ? If your phone has 2.1 then there's no way you're going to be able to use your headset as 2.1 isn't capable of dialing out only accepting calls and manually making calls. I'm using midNIGHT custom rom and by using midNIGHT my headset does dial out. So join in on the forums and read up. I know there was a recent post http://forum.xda-developers.com/showthread.php?t=967014 That should be of great assistance to making your phone a lot better. Though most importantly I'm new here too and perhaps someone can give you better advice. But I do know that your phone out of the box won't allow you to voice dial using a headset until you're updated to Froyo and that I recommend midNIGHT rom but there are many roms to choose from as well as a lot of reading and learning which can be fun.
I have tried out a couple of ROMs on my AT&T S3, and I have consistently had one issue on every custom mod that I didn't have on the stock firmware. I have a Bluetooth setup in my car and the phone connects fine, and I can receive incoming calls just fine by pushing the accept button, and Bluetooth will work fine for dialing out if I type in the number on the phone (not the best for driving), however I can't seem to get the voice activated dictation working when using any custom ROM, and my guess is because they all remove S-Voice.
If anyone has any luck using Bluetooth with voice commands in the car or with a headset by pushing the button and then saying something like "Call so and so", please let me know!
Thanks
Hi,
Just bought the T-mobile Galaxy S3. Upgraded it to the latest version using Samsung Kies (e.g. no custom ROM).
When using Viber, I cannot hear the other person. Other person hears me fine.
Have tried to deactivate Viber account, delete application data, uninstall, reboot, reinstall Viber. Tried with and without handset. On wifi and on 4G.
Normal calls and Skype works fine.
Any suggestions? Preferrabely without changing to a custom ROM, as I have no Android experience. I am an exchange student residing in the US this fall, so really need the Viber to work.
Thanks.
Same problem on Galaxy Note N7000
I have the same problem on my Galaxy Note N7000, yet would be happy to hear the reply to S III, could be the same problem or at least the direction to where should I look to find the solution.
Anyone?
Hi, I have a Chevy Volt and a Galaxy Note 2. When I was on a 4.1.2 based ROM, the integration with the car worked automagically (once BT paired). I recently updated to a 4.4 ROM (OmniRom), and now the link is broken. I can play audio through the BT as before, but the push to dial commanding will no longer dial the phone. The car just says "dialing failed", but the phone never even tries to dial! I think this may be a 4.4 issue because I had the same problem with another 4.4 CM based ROM.
Anybody have similar experiences, know of a workaround or way to get it to work?
Thanks!
lrsmr2 said:
Hi, I have a Chevy Volt and a Galaxy Note 2. When I was on a 4.1.2 based ROM, the integration with the car worked automagically (once BT paired). I recently updated to a 4.4 ROM (OmniRom), and now the link is broken. I can play audio through the BT as before, but the push to dial commanding will no longer dial the phone. The car just says "dialing failed", but the phone never even tries to dial! I think this may be a 4.4 issue because I had the same problem with another 4.4 CM based ROM.
Anybody have similar experiences, know of a workaround or way to get it to work?
Thanks!
Click to expand...
Click to collapse
Probably just go back to a Touchwizz based rom (Lots of 4.3 available) and you should be fine. But there may be other options but thats a suggestion
Yes as a test, works on 4.3, but
As a test, I loaded a 4.3 ROM and after I set the BT options for both media and phone it worked fine. I'm going to reload a 4.4 rom and see if it was simply that I did not have the BT set for audio and phone. duh.
Remember to update once you've tried it out. Could help out others in your situation.
no 4.4 yet, plan to though
Still running 4.3. SkyNote works pretty well, so I'm reluctant to move now.
Lots of threads about 4.4 BT problems. Sorry.
Hi,
I have recently upgraded my Captivate Glide (SGH-i927) to bubor's CM11 Android 4.4.4. Everything works great, except VOIP calls. Calls over SIP are coming in very slow (slow motion, incoming jitter of 268244ms). I tried using the built in Android function, Zoiper and CSipSimple, all had the same problem. Calling on Skype didn't work either - the screen went white when I answered a call and then nothing happened.
I am travelling today and was hoping to use VOIP to call home while I am away. I did some searching on the forum and it looks like others have this (unresolved?) issue.
Is there any solution or workaround or app to to resolve this? I apologize if a solution/update was already posted somewhere - I wasn't able to find it and I am out of runway today.
Many thanks in advance, any help would be greatly appreciated!
Andrew
azwindsor said:
Hi,
I have recently upgraded my Captivate Glide (SGH-i927) to bubor's CM11 Android 4.4.4. Everything works great, except VOIP calls. Calls over SIP are coming in very slow (slow motion, incoming jitter of 268244ms). I tried using the built in Android function, Zoiper and CSipSimple, all had the same problem. Calling on Skype didn't work either - the screen went white when I answered a call and then nothing happened.
I am travelling today and was hoping to use VOIP to call home while I am away. I did some searching on the forum and it looks like others have this (unresolved?) issue.
Is there any solution or workaround or app to to resolve this? I apologize if a solution/update was already posted somewhere - I wasn't able to find it and I am out of runway today.
Many thanks in advance, any help would be greatly appreciated!
Andrew
Click to expand...
Click to collapse
I think that is the alsa fix you talking about.
As mentioned in bubors OP for cm11 :
http://forum.xda-developers.com/cap...lication-to-fix-audio-4-4-roms-t2836257/page1
Is it this what you need?
.
Hi,
Sorry for the belated reply.
Many thanks for your reply and direction to the audio fix! It really helped me since the phone I took travelling with me was updated to CM11 and my main way of calling home wasn't working.
One thing that I figured out once I got back is why my GSM calls weren't working, while my VOIP ones were working fine. It seems to me is that I have to manually switch the stacks through terminal emulator (su *press enter* alsas) to get either GSM or VOIP calls, which makes receiving both type of calls difficult. Do you know how to make both GSM and VOIP calls work at the same time? I posted this comment in the audio fix thread as well.
Many thanks again for your help, that was much appreciated!
steadfasterX said:
I think that is the alsa fix you talking about.
As mentioned in bubors OP for cm11 :
http://forum.xda-developers.com/cap...lication-to-fix-audio-4-4-roms-t2836257/page1
Is it this what you need?
.
Click to expand...
Click to collapse
azwindsor said:
Hi,
Sorry for the belated reply.
Many thanks for your reply and direction to the audio fix! It really helped me since the phone I took travelling with me was updated to CM11 and my main way of calling home wasn't working.
One thing that I figured out once I got back is why my GSM calls weren't working, while my VOIP ones were working fine. It seems to me is that I have to manually switch the stacks through terminal emulator (su *press enter* alsas) to get either GSM or VOIP calls, which makes receiving both type of calls difficult. Do you know how to make both GSM and VOIP calls work at the same time? I posted this comment in the audio fix thread as well.
Many thanks again for your help, that was much appreciated!
Click to expand...
Click to collapse
no problem and for the other problem you describe i have no idea maybe @bubor has one.
Good luck
.
azwindsor said:
Hi,
Sorry for the belated reply.
Many thanks for your reply and direction to the audio fix! It really helped me since the phone I took travelling with me was updated to CM11 and my main way of calling home wasn't working.
One thing that I figured out once I got back is why my GSM calls weren't working, while my VOIP ones were working fine. It seems to me is that I have to manually switch the stacks through terminal emulator (su *press enter* alsas) to get either GSM or VOIP calls, which makes receiving both type of calls difficult. Do you know how to make both GSM and VOIP calls work at the same time? I posted this comment in the audio fix thread as well.
Many thanks again for your help, that was much appreciated!
Click to expand...
Click to collapse
We have 2 audio driver, one works with gsm and other works with voip, you have to switch with "alsas" command. You can find solution to switch automatical. I've never used that, you should ask them. Try to use logcat.
Many thanks, bubor! I didn't realize that fusor's app was an automatic fix and there was always an option to switch the stacks manually. I was able to get it to switch automatically by using the Tasker app.
http://forum.xda-developers.com/showthread.php?t=2541182&page=18