I have Skype ppc on my mini, should I be able to call other skype users through the mini?....meaning talking through skype with the phones earpiece and mic.
I have tried to call someone but the sound (thier voice) comes through the speaker on the back of the phone and it seems they can't hear me
Is there a setting somewhere that perhaps I've missed :roll:
Thanks for any thoughts
marto
Are there other programs people have successfully used the mini's mic and earpiece to talk with?
marto
Hi,
I have the TyTn and when I connect it via Bluetooth to my Nokia CK7W carkit callers complain that my voice breaks up and they only hear every 2nd word or so. I also get the same complaints when using the handsfree inbuilt speakerphone, and that my voice fades in and out.
Yet when I talk normally with the phone to my ear the problem isn't there.
I've tried raising my voice and speaking closer to the mic in both cases but this doesn't work.
Any suggestions?
Tnx
Ari
Might be similair to the issues other users and I are having.
See the following for more info:
http://forum.xda-developers.com/viewtopic.php?t=61594
http://forum.xda-developers.com/viewtopic.php?t=60225
Thanks for the reply. Unfortunately it's not related to the other forums. My phone keeps the bluetooth connection and both incoming and outgoing voices can be heard.
I've heard it for myself and it sounds like i'm in a bad reception area. What's really puzzling is that it also happens when I speak on the phone with the speakerphone activated, yet when I place the phone right to my mouth then the problem goes away, so i'm thinking it's something to do with the mic switching off to cancel any echo?
See this post
http://forum.xda-developers.com/showthread.php?p=1834544#post1834544
I know this has been covered a bit but I have a quick question. MS is saying you need to have AKU 3.2 to get VC to announce caller's over your BT Headset. Has anyone found a simple way to make this work on an earlier ROM. Lately I've been running mostly Molski's ROM, but I dabbled in Faria's 3.2. I swore I had BT working totally with a 2.26 ROM, but am I on crack?
I liked Faria's 3.2 but I was missing too many calls. Is there any way to upgrade just teh BT in an older ROM to make this work. (I'm sure my inexperience shows in this question. If its impossible to do, just say the word and I'll patiently wait for a new 3.2 or 3.5 ROM or just forget about this)
I have two answers to your question.
The first is use the A2DP hack found in this forum and get a stereo bluetooth headset. The iTech Clip R35 or S35 both come with the two headphones; one with only one earbud, so you aren't covering both your ears. When you have a stereo bluetooth headset, all sound, including the calls from MS Voice Command are redirected to your headset.
The second is use the program found here:
http://www.pdaphonehome.com/forums/...luetooth-headset.html?perpage=20&pagenumber=1
It basically redirects all sound to bluetooth (probably a cheaper and easier fix); I haven't tried it yet, but it seems like it might be the solution you are looking for.
I also liked having the feature of calls announced through bluetooth, but it never did seem to work. I have been meaning to download the program from the site, but just haven't gotten chance. If you try it, let me know if it works.
Thanks.
I wonder how hard it would be to get that little program to run automatically when connected to a head set
yeah theres nothign cooler than wearing a stereo headset while driving. Thanks but no thanks.
I've used BT audio with v1.5, and it wasnt for me. i still use it to listen to podcasts via my headset on occasion though.
The nice thing about 1.6 when it was working (mist have been with Faria's ROM) was that I didn't hear my normal phone ringtone through the headset. It rang like normal through my headset, but it would announce the callers name. Its a cool feature.
edit: I must have been wrong. It does divert the ringtone through your headset as well. This gives me hope that I can work somethign out using BTAudio.
Yeah it is a cool feature. You can go to the notification settings in voice command (Settings -> Personal -> Voice Command) and change it so that notifications are done when bluetooth is available (the second radio button). If the notifications cannot sound through your headset, they will come from the phone speaker so you will still be able to hear who is calling without looking at your phone. Doesn't really help if your phone is in your pocket or if you can't hear it, but I guess its the next best alternative.
I have a cooked T-mobile 2.26 ROM and use MS VC 1.6 over my BT205 no problems. I was previously using the original O2 rom and has it working on that too so both an AKU2.0 and an AKU2.3 work fine. To install try this:
remove VC if installed
remove headset pairing
soft reset
create headset pair and leave it switched on
install vc1.6
soft reset
add path string to HKLM\SOFTWARE\OEM\VoiceCommand\
i.e. \Program Files\Voice Command\VoiceCMD.exe
soft reset
then try the button on the headset a few times
Riptos
I'm not having trouble using BT with VC. I want the Incoming call announcements to come over BT.
I installed Farias 3.2 and it worked, but I decided its not a huge deal. I'll try playing around looking at some of teh links here and see if I can't work somethign out. Thanks everyone.
I would also love for voice command 1.6 to announce incoming calls to my bluetooth headset. Interestingly, low battery announcements come through the bluetooth headset, but not incoming calls. Hmmm. Any suggestions/luck getting this to work?
Best,
MJB
VC Caller ID over Bluetooth
I think you all will enjoy this hack
where did u find this hack from? is it reliable?
jacob-mda said:
where did u find this hack from? is it reliable?
Click to expand...
Click to collapse
What? You don't trust someone who's first post is somethign to put on your phone
hell no considering this a brand new mda tmobile just sent me lol..
jacob-mda said:
hell no considering this a brand new mda tmobile just sent me lol..
Click to expand...
Click to collapse
Just wanted to let everyone know I tried it out today and it works as expected. Phone audio gets redirected to BT headset on incoming calls.
but does the ringer get re-directed also? cuz if so thats DAMN ANNOYING!
Well I dont mean to sound condescending to a "senior member" cuz im just a junior but did it cross your mind to select "none" as your ringer? Oh, Btw everyone, your welcome for my fantastic little file
What exactly does the file do???
I had troubles with VC 1.6 at first, but now it seems to work OK. Maybe I accidentally followed Riptos's instructions. Don't know.
Also BTAudio is working to redirect audio when I want that to happen, since VC now closes the audio after it finishes.
The only remaining minor glitch is that after giving a dial command, the little simulated dialing noise comes over the phone speaker not the headphone. So if the phone isn't right by, I don't always know whether it has dialed or not.
Any suggestions?
I tried the CallerID program. It works just as described. The only thing is that is takes up ~443.48 KB at startup. I just installed it so I don't know if it increases after a while.
I have a question. If I understand everything correctly, with a AKU 3.2 ROM this CallerID program isn't necessary if I want to get Incoming Call Announcements over Bluetooth. Right??
Has anyone gotten VC 1.6 to announce incoming calls over a STEREO Bluetooth headset? Seems like the discussions have only been for a hands free device. Anyone?
I don't have a 3.XX ROM and Voice Command notifications work on my stereo bluetooth headset without the program because I think wtih stereo bluetooth, all sound is redirected to the headset. I didn't do anything or change any settings, it just worked. I obviously have the A2DP hack installed, but that's it.
from one week during calls phone speaker doesn't work, but using earphones or enabling handfree works fine.
I checked that speaker works because audio tone realtive at call disconnection or no permitted calls is audible. It seams that when phone switch to the carrier network audio go to mute
Someone know this problem?
ROM refresh can be solve my problem?
thx
marco
I have the same problem and I dont know how to fix. I made a Room Upgrade but the problem remain. did you fix it yet? thank you
There are programs for windows mobile but I can't find any for windows smartphone 6.5 . I'm also looking for stock quotes software... one that can use stocks from non US markets.
I managed to get incoming VoIP/SIP working with a native app but it was a bit messed up. Basically I installed this package: http://forum.xda-developers.com/showthread.php?t=596682
and followed this guide: http://forum.xda-developers.com/showthread.php?t=299950
I can't get outgoing to work, but incoming works.
Wow you got it working? Which device do you have? I tried with the HTC Maple (called Mobilicity Snap here) and could never get the audio to come through the earpiece.
Anyway, the two programs I've tried that DO work are AGEphone and fring.
On the Mobilicity HTC Snap I got it working, yes. The question was not about using the earpiece, it was about using the native VoIP client. In fact, I did manage to get the VoIP calls through the earpiece but it has a very bad negative effect: the ringer also goes through the earpiece after a few seconds, thus making the ring on incoming calls very quiet. In my opinion, it is much better to use the headset for VoIP calls as it provides excellent quality, no echo and no problems with the ringer.
The problem with outgoing calls is in the way WinMo's VoIP places the calls. They work with Voxalot but not PBXes. I am assuming everybody can just use Voxalot as a middleman between the HTC Snap and the voip provider if there are any problems with outgoing calls.
That's funny, as I could never get it working with the headset. Outgoing calls worked, but only over the speakerphone, while incoming calls had no audio at all. The mic didn't even work; I could press the keypad and get a DTMF tone, but that was it.
Could you tell me exactly which steps you took to get the audio to come out of the earpiece? I kind of gave up and am using fring, but it would be interesting to see how you did it.
xenyz said:
That's funny, as I could never get it working with the headset. Outgoing calls worked, but only over the speakerphone, while incoming calls had no audio at all. The mic didn't even work; I could press the keypad and get a DTMF tone, but that was it.
Could you tell me exactly which steps you took to get the audio to come out of the earpiece? I kind of gave up and am using fring, but it would be interesting to see how you did it.
Click to expand...
Click to collapse
Sorry, apparently I was wrong, even with the earpiece hack (I tried both of them) the most you can achieve is to get the ringer to go through the earpiece but once the call connects it goes back to the speaker.
The only solution is to use the headset. I tried for outgoing only and I am able to dial, send DTMF and speak, so the mic works well.
With the native client on the HTC Snap VoIP works only with headset. Overall, I have been using WinMo for about a week and I can say that I hate it more than any other OS I have used. I wish we could get Android to boot but seems like the CPU on the Snap is messing up the effort.
Fring is also garbage on WinMo. It often fails to connect and when it does connect the call quality (over WiFi) is much worse compared to Fring on S60 or iOS. It eats the battery like a monster, something that doesn't happen on S60. There is no way to change/silence the ringtone with Fring on WinMo and if a call comes over the GSM line while you are on a call with Fring your Fring call goes through the speaker, very embarrassing.
I got my Snap for 100$ from Mobilicity and I think the hardware is worth it, but Microsoft should be paying me for being stuck with their useless OS.