Well i've been doing a bunch of stuff to my phone to get things humming along, but the one thing that hasn't worked at all is Bluetooth Voice Command Dialer.
I've tried the native bluetooth voice command dialer, and the following apps below:
Vlingo Virtual Assistant
Choice Dialer
Bow Tie
The bluetooth handsfree that i am using is the Samsung WEP200 and I own 3 of them and all 3 of them don't work.
When i mean don't work, i hit the command button and it would prompt with the "Bluetooth Voice Dialler" prompt and I try to speak but nothing is happening. The audio routes to the bluetooth, but i suspect the mic isn't.
Bluetooth calls and call last caller works, but that is it as it is basic bluetooth capabilities.
So at the moment I am stumped and wondering if anyone out there got it to work and what your handsfree is.
I have noticed the same problem. Is your phone a Rogers Captivate using Kies to update or it's an ATT Captivate using Odin to flash rom?
I have i897 AT&T and Odin flash and I notice this issue. When I was on the Rogers ROM 2.1, my bluetooth wouldn't pair. Now on 2.2, I can pair and call using BT, but voice dialler doesn't seem to have the mic on...
I tried bluetooth mic tester app and it didn't record anything via bluetooth.
I'm using the Rogers Froyo over Kies. It took me forever to install it since i had to repair my nv_data.bin.
This problem plagued me from Cognition 2.3b8 as well. To date I haven't had a Froyo install that worked with Bluetooth Voice Command Dialer.
If anyone out there that had the bluetooth voice command dialer to work on their captivate I'm all ears. I am thinking maybe it is because my Samsung WEP-200 is too old?
BTW, I'm using Jawbone Prime.
I also tried other apps vlingo and all those none seem to be able to capture mic from BT when voice dialing. I can have voice conversations using my BT, but no voice dial.
Well I think it might be a general issue with Froyo and Samsung Captivate in general, regardless of Froyo custom builds. If someone else has it working on a specific ROM i am all ears.
Later tomorrow I will contact Samsung Support and ask them about this, because this is really stupid.
Just wonderful. Well, I hope that's not your true official Froyo. If so, Samsung is just killing me. I've been running I9000 Froyo ROMs because the first nor second Cappy Froyo leaks don't have this functionality. This is the one function I want Froyo for more than anything else. I hate to say this, but my iPhone 3GS worked perfectly (you know what that means: I could voice dial over Bluetooth, but the call wouldn't stay connected!!). I just hope this is not an indication that Froyo for Cappy - if it ever is released - will not have this functionality. It just keeps getting better with these guys.
Any updates from Samsung?
well i called samsung social hub support. Their official answer it isn't even a feature of the phone. Also they are aware that the bluetooth voice command dialer is broken on the phone and isn't supported.
I've requested they have it as a potential feature in the future as it is bylaw in some provinces and states that people use bluetooth voice command dialer.
Well this only puts one more nail in for samsung...
Also this could be related because of their stupid bluetooth stack, but there isn't much more I can find on this.
I hope this information is helpful to those looking around.
I've had it successful on two or three different ROMS. But I can't remember which for sure.
I think it worked on one of the Perception ROMS; It doesn't come on Assonance ROMS.
Something that I have done on ROMS that don't come with the Voice Dialer, I use Blue Tooth LAunche. I'm using it now on Assonance 5.2 You can configure it for what you want it to connect to.
It may take a bit of experimentation on how to configure it. When you go into the list of apps to configure, it lists all the various activities of the apps, and you need to select the right one. For example, to bring up Google Voice Search, I have it using com.google.androd.voicesearch.recognitionactivity.
Google Voice Dial
I had the same issues on Assonance 5.2. What I did was take the voicedialer.apk from Perception 9.5 and installed - that worked for me.
I have attached the apk for you, I can't for the life of me remember how I had to install it though.
I had a lot of dropped calls on Assonance and didn't realize at the time that I could just update the modem - live and learn I guess.
I just downloaded the voice dialer.
I actually have it at home, but not sure if same version. I tried to install it on one of the ROMS (I think Assonance) and was unsuccessful. I probably tried using Root Explorer. I don't think I tried just dropping it in the Apps folder. But not sure.
I'm installing Cognition 3 as I write this. We'll see how things go on that.
baxster said:
I had the same issues on Assonance 5.2. What I did was take the voicedialer.apk from Perception 9.5 and installed - that worked for me.
I have attached the apk for you, I can't for the life of me remember how I had to install it though.
I had a lot of dropped calls on Assonance and didn't realize at the time that I could just update the modem - live and learn I guess.
Click to expand...
Click to collapse
I'd try this but it wont let me install over system apps lol. Anyone know how to do it? BT dialing doesn't work on my rogers 2.2 either.
Well the bluetooth launch + vlingo voice works (the one from samsungs apps)
I've tried updating the voice dialer.apk from this thread, and this one:
http://forum.xda-developers.com/showthread.php?t=780687
http://forum.xda-developers.com/showthread.php?t=908492
No luck.
I think if we wanted to use the native bluetooth voice dialer we need to update some system libraries and also the apk file. Thoughts?
kintaro said:
Well the bluetooth launch + vlingo voice works (the one from samsungs apps)
I've tried updating the voice dialer.apk from this thread, and this one:
http://forum.xda-developers.com/showthread.php?t=780687
http://forum.xda-developers.com/showthread.php?t=908492
No luck.
I think if we wanted to use the native bluetooth voice dialer we need to update some system libraries and also the apk file. Thoughts?
Click to expand...
Click to collapse
I am hopping that when the AT&T update happens we may be able to get the files we need to get the Rogers version working...
I also tried with the VoiceDialer.apk provided in this thread and no luck. Also tried the 09SEP-VoiceDialer.apk and no luck.
I do agree that there is some system libraries that need to be updated, since there are claims that 09SEP-VoiceDialer.apk worked with others.
Since we can have conversations with our bluetooth, it's not an hardware issue. It's something with software.
Same issue here with rogers captivate.. I deleted the dialer to see what happens, and the button on my headset now did nothing, but if i held it in, it would call the last number dialed. I flashed it back to factory and got my app back, and the button brought up the bluetooth dialer again, but it doesnt work. And now pressing and holding calls voice mail again.
I wish they had a settings section to assign the button presses to applications without 3rd party apps.
I hate how rogers and samsung are washing their hands of the issue. they wont take the phone back. Its illegal here to use my phone while driving. I got the phone on the 11th. I am still waiting for the accessories I bought to arrive, everything from a desk dock to car dock, spare battery.. all OEM.
If they don't get this right, I wont be buying more products from them.
I have more faith in you guys finding a solution than them.
Same problem and I think NONE of the Bluetooth mic works on Voice Command on Froyo roms for my Captive. I've tried the AT&T leaked Rom and also the Cognition 3.04, NONE of them support Bluetooth voice dialing but no problem for normal phone conversation. Now that is EXTREMELY ANNOYING!
iPhone 5 for sure! No more Android suckers!
Just wanted to pipe in that I'm in the same boat and pretty mad at sumsung/rogers for not including bluetooth voice dialing! Is this 2011 or what?
I just bought some very expensive bluetooth headsets for my motorcycle and now find out that my brand new "state of the art" phone can't voice dial with them?
Hopefully someone figures this out. I'm counting on someone being way smarter than I am with this stuff
Man, after having this phone for 6 weeks now I'm starting to wonder why I switched from my WinMo phone. For all the hype of Android and the criticism of WinMo, there are a number of things, like voice dialing over BT, that just plain worked on my HTC Tilt 2. And I'm finding that WinMo was a lot more customizable (and a lot easier to work with) than what Android allows me to do. If it weren't for the gorgeous screen and capacitive touchscreen I would go back to my Tilt 2 and sell this POS Samsung device.
Miami_Son said:
Man, after having this phone for 6 weeks now I'm starting to wonder why I switched from my WinMo phone. For all the hype of Android and the criticism of WinMo, there are a number of things, like voice dialing over BT, that just plain worked on my HTC Tilt 2. And I'm finding that WinMo was a lot more customizable (and a lot easier to work with) than what Android allows me to do. If it weren't for the gorgeous screen and capacitive touchscreen I would go back to my Tilt 2 and sell this POS Samsung device.
Click to expand...
Click to collapse
In all fairness, this is a samsung issue. Not Android.
Related
I have an ATT Tilt with a personalized cooked ROM. I make a call which the dialer says it is dialing but I hear no ring. It then says it is connected but I cannot hear the person I'm calling nor can they hear me. I've confirmed that it does ring through to them and they answer, but we cannot hear each other.
The only way to fix it is to soft reset. Pain when I really need to make a call.
Has anyone had this problem? Better yet, anyone know of a permanent/non-reset remedy?
Thanks!
Alan
Yes indeed, sounds very familiar! My wife's tilt (stock rom) did it for a period, soft reset let it work for a little while. We called ATT support, tried everything to no avail. Received a replacement phone, all is well now.
My phone (stock rom) has done it a couple of times. Seemed to be related to lower signal strength environments like a costco warehouse. May be related to applications I have downloaded. I have a feeling Voice Command could be problematic.
I do have voice command installed as well. It would not surprise me at all if it is the culprit.
Same here on occasion (German TyTNII ROM). No voice command installed, for me not signal strenght dependent.....
same here from time to time. from what i can recall, it only happens when i am using my bt headset.
HTC have a bluetooth fix to download if you're getting problems with calls while using bluetooth.
Same problem here from time to time (no bluetooth active & no voice command though)
Funny, I have had this happen to me a few times, too. It just started about a week ago and has happend on about 2-3% of my calls. Another thing I noticed what during an inbound call, when you answer call waiting, the original party's call is not terminated (if you know what I mean).
Is anyone using Live Search when this happens? The loss of audio has happened whenever I have Live Search open, possibly with gps on, and when a call comes in, theres no audio. Im not sure if this is just a Live Search bug or a general GPS related bug, but its pretty consistent.
TILT Audio problems
I have had similar issues on my stock ROM ATT TILT (Mobile 6.1). Sometimes audio goes away (call connects without audio). I have also noticed 402 errors in browser at times (while using Edge connection). In both cases, hard power off-on fixes the problem. Very annoying issue.
I have Live Search installed, but the problem started prior to that - possibly about the same time as I installed the 6.1 update.
I'm not sure what triggers / influences the problem. I may have noticed Bluetooth device disconnecting (like when I walk away from my car's handsfree) having some influence. As an additinal input, I don't recall this problem occuring if the Bluetooth radio is disabled.
Any thoughts?
having this problem with the TOUCH PRO 2
Having problem with TP2
Looks like a minor upgrade. There is a PPC version and a Smart phone version, not sure of the differences or which is best for the Touch Pro.
Hi,
It is a major upgrade since a new voice engine is included.
The on the touch pro you need to install the pocket pc version.
http://www.skype.com/download/skype/windowsmobile/
Regards,
madraven said:
Hi,
It is a major upgrade since a new voice engine is included.
The on the touch pro you need to install the pocket pc version.
http://www.skype.com/download/skype/windowsmobile/
Regards,
Click to expand...
Click to collapse
it does not matter how major an upgrade they come out with its all crap until they come video chat for windows mobile.... i think its time for a poll
skype
does any one have cab file for this software?
Thanks
dadavotinh said:
does any one have cab file for this software?
Thanks
Click to expand...
Click to collapse
Click on the skype link above....click download to ppc....
http://www.skype.com/go/getskype-pocketpc-cab
Does it fix the issue with the sound playing out of the back speaker instead of the front one?
My company just made skype standard platform for internet call. Just wonder if this PDA version ad free? I installed desktop version but hate the pop-ups and silly ad on top. Well, I knew I should not complain as I use it for free.
ok i have a question. if i install this skype on my phone and my friend in india installs skype on his phone as well are those calls free if we can call each other through skype? I am always around wifi in the US and my friend has internet on his phone all the time since its dirt cheap (30 cents a day for unlimited in case your wondering)
Hallo ptyindian,
skype2skype-Calls are free!
KUR0I said:
Hallo ptyindian,
skype2skype-Calls are free!
Click to expand...
Click to collapse
hey thanks just wanted to make sure. I thought they were free but my friend in India was saying they are not. K cool thanks for the clarification.
speaker?
did they fix the speaker/earpiece problem?
do u guys know if this skype can be used with bluetooth headset?
"00" = "+" to make calls
Maybe this is common knowledge, but it took me an hour to find answer, which I eventually found on skype forums. I've used skype on PC for couple years, but just installed it on Fuze.
Problem is, you have to dial numbers in international format. For USA, that means you dial a "+1" before the area code and number. Skype 2.5 softphone has no way to type a "+" symbol and you cannot set it up to do so automatically like Skype on PC. Also, it does not accept input from our phones keyboard.
So, I found on Skype forums if you type "00" it equals the "+" symbol. Maybe its common knoweldge, but it gave me a hell of a time. Hope it helps.
...anyone know how to import Outlook Mobile Contacts into Skype mobile contacts?
Current Pocket PC version: 2.5.0.170. Release date: February 16, 2009 solved problem with Skype shuting down upon initiating skype call on my Touch Pro with Proven 1.14a ROM.
Finally I can make calls with skype on TP
Hey guys, I tested this over an EVDO data connection and wifi with and without a headset (wired). The quality of voice call was acceptable in every circumstance on both ends. However, not sure if this is an issue with my wireless ISP, using the EVDO data (and this has never happened) my data connection was disconnected within a minute or 2 in 3 consecutive calls. I have never had a disconnect issue before, and I did not receive a standard call to my phone in that period of time. Again, I am not sure if this is Skype causing the issue, or an issue with my stock Bell Mobility ROM/ISP. My guess would be Bell.
has anyone tried to use this with bluetooth headset?
Skype over Normal (front) phone speaker/ BT Problem
daveyS said:
Does it fix the issue with the sound playing out of the back speaker instead of the front one?
Click to expand...
Click to collapse
Keep this issue alive...
My guess is there is a registry setting or three to adjust related to the default audio gateway instructions for Skype output, but I had trouble locating them before flying overseas (and therefore, using a WIRED headset for every skype call). I will look again, but anyone who has this fix, or an idea about solving the problem, please weigh in.
If this can be taken care of, then the "Call using Skype" option in Contacts may actually make Skype on a mobile work like a true IP phone client and change my mind about leaving Skype running on my mobile al the time instead of forwarding incoming Skypes to my mobile number (and paying for the forwarding) in an effort to avoid every answered Skype call being on speakerphone by default.
mlbal said:
Keep this issue alive...
My guess is there is a registry setting or three to adjust related to the default audio gateway instructions for Skype output, but I had trouble locating them before flying overseas (and therefore, using a WIRED headset for every skype call). I will look again, but anyone who has this fix, or an idea about solving the problem, please weigh in.
Click to expand...
Click to collapse
There is no registry setting or such thing (also see the Skype forums for this issue) to achieve this. According to the developer(s) they have no possibility to use the earpiece speaker from their code as the phone OS will not allow this...
CU,
Cactus World
P.S. If anyone finds a way, please share as this issue is very annoying indeed!
test results
OK, so the speaker issue is not resolved.
As mentioned before, physical keyboard is not working: on-screen keyboard fine.
I only use skype on wifi, but for me the call quality is improved.
So, other than the keyboard issue, it's a good update.
to use skype through the earpice instead of the speaker just install troca2.cab works perfect
orry paul : /
ive been getting more and more failed texts lately, the phone just cant send them, sometimes i reset the phone and they work, sometimes not. All of my friends with iphones and blackberrys say its happened to them maybe once or twice a year. So is it TMobile or is this just another in the seemingly endless list of android's failures? Android is my first smart phone, my g1, mytouch and nexus have all had similar problems im just wondering if other popular smart phones have the level of problems android does....i realize all phones have issues and android is still young (although that excuse is getting pretty tired) but its just all the damn time with these phones. I love android but at some point the phone's got to either work or im out...thanks
what messaging app are you using? Handcent seems to work for me rather well. I'm not too sure about the native messaging as I don't use it.
Same crap happens to me and I'm using stock sms.
McFroger3 said:
Same crap happens to me and I'm using stock sms.
Click to expand...
Click to collapse
Try out handcent. If you have problems, the developer is very easy to get in touch with and actually works with you to find the problem
djn541 said:
Try out handcent. If you have problems, the developer is very easy to get in touch with and actually works with you to find the problem
Click to expand...
Click to collapse
Used it before, same issues. I don't think it matters what you use, I think its a bug in the Android OS itself.
from time to time, i've experienced SMS send failures on all of my smartphones, WinMo & Android. a soft reset/reboot seems to correct the problem. to the OP, what ROM are you using? have you asked T-Mo if they've been having issues with SMS messages? hope you get it resolved soon!
first of all, sorry that my post sounds so grouchy. My phone isnt rooted, but i do recall similar problems on my g1 and it was rooted, mytouch was not rooted but had same problems. Its not so much THAT it happens, because im sure it happens across the board to all phones, its just that it happens about every other day which seems a bit much for competitive smartphone software (of course, i am not smart so ive no idea that its the software and not the hardware or carrier, im just poorly connecting what dots i do have...) I had the problem with stock app and i tried chomp, same issues so i went back to stock, again same issue so i currently have handcent (which is an awesome app but i just hate having two icons/apps for the same purpose when im only using one of them).
the issue happens with handcent, and every time before restarting the phone i try the stock app and it doesnt work so im guessing its not the particular app, TMobile definitely has poor signal quality compared to the other major carriers, but i have 3g and full bars here in san antonio for the most part. If its not a particular app, i assume there is something in the android system that text messaging uses regardless of what app is being used; since i have 3g and full bars im led to believe its something in the android system? But again, android smartphones are the only smartphones ive had so i dont know if its just the nature of texting although like i mentioned the other two phones i have several friends who own report very very rare if any text messaging issues...
android is such an impressive software, so sophisticaed that i can understand that some part could mess up another part and cant be resolved without messing up yet another part. I cant even begin to imagine how to resolve all of the software issues android has, but if apple can do it, im confident google can too. i just hope the forthcoming litigation doesnt affect the efforts, i already feel like ive been waiting for some fixes for a long time, but thats probably due at least in part to my extreme, childish, and uncontrollable impatience...
Everytime I have issues with SMS messages, I am always using a HTC ROM. That is why I stopped running Hero ROM's on my G1. It would just not recieve the messages at all sometimes. I tried the Desire ROM on my N1 and it worked great for a while, then I started having issues with the messaging app (stock one). It would list the threads incorrectly by contact, but when you clicked on them, it would be the right contact. For example, I had a conversation with Jim, it would show what Jim said in his last message to me, but the name next to it would show Carl. I clicked on it to see the whole thread, and it would show Jim's name next to all of his messages. This was okay, until it started sending messages to Carl, when it was supposed to send messages to Jim.
I am not saying the HTC ROM is to blame, It might have been the back up and restore software I was using and how it is affected by crossing from a CM ROM to the Desire ROM.
I've seen this question asked about a dozen times since the JI6 ROM leaked, but haven't seen it answered yet. Does anyone have Bluetooth Voice commands working in JI6? If not, how difficult would it be to pull that functionality from one of the i9000 roms that has it?
I have seen this question answered a couple times where it is not working for people. Give it time, things will get sorted out. But please next, time put the thread in the Q and A section. It is tough enough to keep this dev section cleaned up.
There is no VoiceDialer.apk in /system/app I tried the one from CM6 and it seemed to run when I hit the voice dialer on my BT. Unfortunately there is some disconnect because it couldn't "hear" (or "understand") a thing I was saying, I could hear the familiar hiss that the bluetooth had switched on though. I also tried Choice Dialer and it seemed to have the same problem. My suspicion is that the speech recognition toolkit is not working correctly in this beta.
Hey,
I finally rooted my XT1092 and installed the latest version of cm in it with the Slim Gapps and I can't find the option to enable OK google everywhere in the google app. Is there no way to get this? I always thought if I get rid of Moto Voice I'd have the option but it isn't so. Has anyone had any luck with it? Any help would be appreciated. Thanks!
If voice commands are so important for you then you should had stick to stock ROM. Moto Voice is best voice feature so far in the smartphone world which works in offline mode and you can also allot your own customized phrase to launch it.
Jack Sparrow xda said:
If voice commands are so important for you then you should had stick to stock ROM. Moto Voice is best voice feature so far in the smartphone world which works in offline mode and you can also allot your own customized phrase to launch it.
Click to expand...
Click to collapse
Moto voice is way too slow and it doesn't work with wired headsets whereas Google Now does.
karanrajpal14 said:
Moto voice is way too slow and it doesn't work with wired headsets whereas Google Now does.
Click to expand...
Click to collapse
To me it works moto voice with wired headsets
Yeah, the options disappeared also on other devices.
Sent from my XT1092 using Tapatalk
Through experimentation, I found out that the "ok google" command everywhere only works on AOSP roms, like Slim6 and Turbo. (if you're going to try Slim6, go with the 0.6 version, as all of the other ones after have a infuriating delay when pressing the buttons on the nav bar)
Slightly off topic question...
Given that with moto voice we have touchless control working like a charm (for example, "call -contact name- mobile" and a call gets initiated with loudspeaker already on), has anyone succeeded in these actions without the aid of moto voice?
Last month I switched to cm, I didn't have the OK Google everywhere option but everything was working well (thanks to OpenMic for screen-off activation), until I discovered I couldn't start a call by voice. The command was registered but I still had to touch the screen to initiate the call. Switched back to stock 6.0 right away.
Is anyone else having this problem on custom ROMs?
I don't think it's minor, cause in a few months we're gonna get cm14 and it would be nice to replicate stock ROM functionality on Nougat
Flipz77 said:
Switched back to stock 6.0 right away.
Click to expand...
Click to collapse
Intelligent move.
Is anyone else having this problem on custom ROMs?
Click to expand...
Click to collapse
If you bought Moto X for its features and got used to of them then you will find that none of the custom ROM can fit it. Even if you make up your mind to convert the MotoX into a bare bone nexus kind of thing then also you won't be able to find any bug free ROM, they all suck and all have one or other bugs all the time.
That's true, unfortunately. I never liked cm but I didn't hate it for the two weeks it was run on my phone. Everything worked smoothly, apart from this pretty ugly bug. If only we had a dual boot kernel