Related
I am looking for users with problems using the MS Voice Command on the T-Mobile Wing/Herald and their fixes or commments.
I have been using WM devices and MS Voice Command for many years. I have had a variety of devices all using voice command; but none have been worse at recognition and speed as my Wing has. How does everyone else with a wing feel about MS Voice Commands performance.
Problems I experience:
Slow response to initialization (1-2 seconds usually)
Slow finding a contact and confirming (2-4 seconds)
Most times with some background noise just gives up and makes that aweful beep.
Always asks to Please try again
Will not understand through bluetooth headset at all.
Commonly mistakes simple names for others i.e. (John Patrick)
Now the voice command can work pretty accuratly in a queit room other than the responsiveness, but I have had it installed on numerous devices and know how it should opperate and the tolerance to noise. I have overclocked my CPU to 273 and doesnt seem to help. I have tried increasing the page pool to 4mb which I have 23mbs for memory and still no luck. Ive even tried the combination of the two but doesnt seem to help. No other progams have been installed for test purposes to see if there is any conflicts and I have about 73 contacts, and sync very little content.
My previous device was a Wizard which respectively is very simular. It did work good with voice command 1.6 both on WM5 & WM6. I have had it installed on a Audiovox PPC4400 (WM2003), Treo 700wx, Blue Angel (WM5), and a Hermes (WM6); all the later devices worked best with no noticable delay or comprehension issues. The Herald will work with the same bluetooth equipment almost flawlessly, the wing will initiate the command but always fail to understand or will pull up something else.
I would like to know if I'm and isolated instance or if everyone has this problem.
Thanks
Jcostanza4
Works fine for me! However, I do speak in a Robotic tone.
Naw, I cant get that thing to do what I tell it.
YES!!!! MS Voice Command on the Wing is almost unusable for me. On my Wizard it was amazing -- fast and accurate. On the Wing frustrating, maddening and worthless.
I have experimented with standard versus overclocking, mic gain settings... everything I can think of. It seems to be a little bit better if I have Bluetooth turned off -- but just a little bit.
I have been reading these forums since the Wing was released and have been surprised that others have not commented on the problems with MS Voice Command on the Wing.
I sure wish there was an answer. Does anyone know what the problem is?
I agree with you, I dont know why more people haven't brought it up.
This is one of the biggest downfalls of the Wing for me. I love everything else even speed when overclocked and the page pool make it quite fast. But I just disable voice command completly because it is so unrelaible. I think it would more likely be along the lines of a hardware compatibility issue that the software would have to overcome or a fix in the OS; but I really dont know.
I wonder if the Herald guys get this problem or if its just an issue with the Wing OS.
Time will tell.
Jcostanza4-
It seems like it's just the crappy microphone on the bottom. It picks up EVERY noise around you and that confuses the voice command. I've noticed that if I use the wired headset that came with my wing it's almost always accurate.
Take a voice note in a semi-noisy environment and you'll see what I'm talking about. It definitely is not a noise canceling microphone.
Well... I can confirm that the audio quality of a voice note is clearly superior on my Wizard than on the Wing... considering that other people do not seem to be up-in-arms about MS Voice Command, I am coming to the conclusion that the microphone on the Wing is at fault.
Has anyone had problems reported with phone calls
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
jcostanza4 said:
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
Click to expand...
Click to collapse
I haven't used a bluetooth headset before on my wing but my wired headset works flawlessly almost every time. It could be that the bluetooth connection wasn't as strong or something (biased towards the wing not working when testing?). I still believe it's the microphone but I could be wrong
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Tweaking th mic gain.
dcmtnbkr said:
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Click to expand...
Click to collapse
Is your device a wing or a herald?
Im still using the stock T-Mobile Rom on the wing and Ive enable and disable the mic gain; shows no improvement that I can tell. Now the Wing comes pre installed with Voice Command and does not have a remove from the Uninstall Program options. I did once try to install 1.6 over it to see if i could get back the remove option and when I clicked reset to finish after installing it hard reset on me.
On your PDAVIET rom, does the vioce command launch instantly, respond quickly, and understand you to some degree or is there some trouble in any of these areas?
Thanks for the info
jcostanza4
me, too - very disappointing indeed
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
mtn_lion said:
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
Click to expand...
Click to collapse
I made all of my contacts store with first name, last name format and the recognition appeared to get a lot better. You shouldn't have to do that but it seemed to help so you could try it. I am temporarily trying the wing overclocked to 273mhz with a boost up to 286mhz and in a quiet environment I haven't had a problem with the voice recognition finding my contacts. I still have trouble with the "play" command and it's VERY difficult for it to understand my "yes" for some reason but contact recognition is good and speedy.
The yes response or correct doesnt pick up well for me either
I did notice this too, but I always forget that thats one of my biggest problems with dailing by name or number. Let's say its a bad mic, even with a headset wired/wireless does it seem to lag in speedy ness or accuracy?
I did mess with page pool on the Wing, I ran 4mb for about 2 months then moved to a 6mb and the device is overall faster than the 4mb or 12mb. The 6mb page pool defenitly responds quick when it can understand you; but 70% of the time it can understand and gives that very long pause before saying "please repeat". It does seam like voice command when enabled eats about 5mb or ram. I have 22.5mb on a soft reset and after using voice comand once it drops to 13mb and then goes to 17mb after about 3 minutes of no use.
I have not read anything from the Hermes users to show that they are having these issues. Could it be an OS problem that translates the mic to the program?
Jcostanza-
kraftey--Thanks for the suggestion, which makes sense, I guess...but I'm not willing to organized my contacts by first name, period. Call me a neo-traditionalist.
As I've posted in the overclocking thread, I can't get my Wing above 228 without the screen flickering.... Ideas?
jcostanza4--Thanks, too. Honestly, in a *perfectly* quiet environment, recognition is not bad, and using either BT headset or not, time from command to response is 5-7 seconds. That doesn't sound like much, but in actual use at work it's an eternity--and made much worse by all of the "Please Repeat"s, additional delays and/or failures.
I've got the pagepool set to 6MB, and I've mucked about with performance-related registry tweaks, but the 5-7 seconds and poor recognition in real-world environments is the best I've been able to get out of VC so far.
Im overclocking the Wing with Battery Status Ver. 1.04.203
I have the device set on dynamic mode so its 201Mhz on minimal load and 273Mhz on Max Load. Battery can last quite a while like this and I havent had screen issues. I hope this helps. I had issues with some other overclocking apps, and eventually tried this one and it worked. No complaints and Ive been using it for about 4 months.
Yes. The darn thing is frustrating. This was supposed to be top of the line. I paid around $250 for the PDA and I paid $100 for a top of the line bluetooth, and the voice mail keeps trying to call my Brother Jeff, regardless of what I say. I paid $140 for a Jawbone, and got the same poor performance. Just how much do I have to pay to get something that works.
Yes, jc, that helps. I had already moved to BS, but now I'll update it with the 1.04 beta. For starters, what OmapClock was calling "228", BS calls "247." With the "released" version of BS, I still get the screen flicker above "247." We'll see if it's any different after I install the beta. Thx.
I solved my Voice Command Problems!
I originally posted all the issues I was having with Voice Command 1.6 on my T-mobile Wing. I now have a working Voice Command to my standards, it works as it has on all my other devices; a little slow at times but not more than a second lag. Recognition is accurate and mic also seems to work better.
Here is the steps I used. (this was completely accidental, as I was trying to get TouchFlo working on the Wing)
I reflashed the T-Mobile Wing RUU found in the Herald wiki section or this thread http://forum.xda-developers.com/showthread.php?t=321717
Then Flashed the Original T-Mobile Rom with Touch Flow found here http://forum.xda-developers.com/showthread.php?t=329456
Then I Ran the Automatic 6mb page pool found here http://forum.xda-developers.com/showthread.php?t=324955
Then I installed Battery Status and overclocked my Wing to 273mhz.
I dont know if the RUU that was released was an update to the original rom, but my mic seems to work great now and recognize with about a 90% accuracy rate.
Please try this at your own risk, This may work for me and may not work for you. By all means I am no programer nor can I assist in a sticky situation.
I suggest reading each of the other threads I have listed before attempting. I will not be responsible if you brick your device. There is alot of information in each thread that is not posted on the first Topic like using ASerg Policies or how the page pool works or common problems.
Thanks-
Jcostanza4
Start > Settings > System > Microphone AGC
I don't use voice dial because I had all the same probs as the original poster. May want to give this a try before all of the steps mentioned in the post before me
for me it is working fine most of the time but not as good as it did with my wizard it is not slow and recognizes commands most of the time, I am using the pdaviet rom build 12 I changed the page pool to 4mb and clocked to 260 with bs , my problem though is that I can't get voice command to work by pressing the bluetooth headset button wich works fine on the wizard.
My Vario III suddenly stops recording sound properly via the built in
microphone. If I make a call when this is happening the other person cannot hear me or sound quality is very poor and if I use htc voice-recorder the sound seems very far away with occasional loud distortion. If I plug in my external headphones and use that mic the sound is absolutely fine.
This problem seems to just appear and then can just go. A soft reset makes no difference. A hard reset or flashing the radio or rom has, so far, always solved the problem - until it happens again which could be in a few hours, days or even weeks.
I can't link the problem to any particular software that runs.
I've tried flashing several different radios. I still get exactly the same problem. My local repairer says it won't be the mic as they either break or they work - not coming and going as I have.
Has anyone any suggestions for what I could try to fix this? Suspect software? Should I just keeping working my way through new radio roms? Do you think it is actually the mic in the phone?
I can't find quite this problem described anywhere else so your help would be very much appreciated. Many thanks.
Currently
Dutty's WM6.1 WWE
Radio 1.70.18.02
Protocol 25.83.40.02W
Originally: (when problem started)
Rom 1.56.110.4 (T-mobile UK?)
Radio 1.27.12.32
birminghamuk said:
My local repairer says it won't be the mic as they either break or they work - not coming and going as I have.
Click to expand...
Click to collapse
Then go see somewhere else, they're not reliable...
A bad contact causing an intermittent failure is one of the most common problems in electronic devices...
I'm having the exact same problem on my Vodafone V1615. Funny thing is, my radio ROM was the same as yours when the problems began. I waited till the Vodafone V1615 WM 6.1 ROM update, and installed it. It worked, for a few weeks, and then the problem returned. Vodafone does not want to fix it for me
Hello tha_bulldog
When your mic stops working have you found a reliable way to get it working again?
Long shot but does this thread help??? The problem was the way the user holds the phone, covering the mic with their hand.
http://forum.xda-developers.com/showthread.php?t=360271
Occasionally I have a problem where when making or receiving calls I pick up and there is no sound. If I Soft Reset I can make the call and it works fine. It's been starting to happen more often recently, and is really bugging me. It happens both when I'm using the phone speaker, and my headset.
what rom are you using? I have noticed the same thing the last couple of days since upgrading to L26 M2D v1
ah, here it is the same thread.
I use WM 6.1 htc version
Is there no bugfix?
Have you tried flashing a new radio?
Ta
Dave
data at info:
ROM: 3.28.407.0 GER
funkempfänger (i guess it's the radio): 1.65.16.25
protocoll: 25.83.40.02H
it was updated with the new htc 6.1 version what i've heard.
or can i downgrade it to a version that is working fine? when yes, where is the file to do so..
Right now I'm using Radio 1.58.16.27, I'll try another one, which do you recommend?
I was using 1.65.29.22, switched to 1.65.24.36 (I was using this with L26 diamond V12 with no issues)
had the same issue today.
hm, looks like a big upcoming problem for everyone...
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
virusv69 said:
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
Click to expand...
Click to collapse
Old thread but still, I've been experiencing this issue on the Hyperdragon series of ROMs from late October. Also had this problem in the past on some of Dutty's roms. The latest Raphael version (15/11/2008) has not exhibited this problem in 4 days. Only difference I can see is a slightly newer version of MSVC (1.6.19965).
Cheers.
gatewayer said:
hm, looks like a big upcoming problem for everyone...
Click to expand...
Click to collapse
I am getting the same problem intermittently, with a soft reset as the solution.
I am running a bone stock AT$T rom,recently upgraded to 6.1. It started happening post upgrade.
An upgrade problem?
same here... im playing around with different radios, it has to be a radio issue imo
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
1stPeregrine said:
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
Click to expand...
Click to collapse
My phone rings and notifies just fine when Texts,emails and calls come in. It answers just fine, but there is no sound. Then when I try to call people back, there is no dial sound and the call appears to not go through, until I do a soft reset, then all is back to normal.....................for a while.......................
I'm having this issue also. The other party can hear me when I answer, but I can't hear anything after the initial incoming-call ringing. A power-cycle restores normal operation but only for a while.
ROM: 3.28.405.0 WWE, 05/02/2008
Radio: 1.71.09.01
Protocol: 25.75.40.02.eMo
I'm in same boat as everyone else here.
Sometimes my phones rings, but when I answer I have no sound and other party can't hear me. Other times, my phone doesn't ring and all audio is muted (despite volume on). Soft reset is the only thing that works for me.
I gotta say this is really pissing me off. I'm missing lots of important calls because my phone doesn't ring when it should, or if I'm lucky it rings but has no audio so I have to soft-reset and wait 5 minutes for my phone to reboot & re-establish signal all whilst my clients are trying repeatedly to call me.
I'm willing to try other radios, but no one seems to have any working suggestions.
Thought maybe it was software, since I don't remember this happening after my initial WM6.1 upgrade. Uninstalling S2U2 didn't work (happened again today). Just uninstalled Voice Command, too, but haven't tested yet. VC's been flaky since upgrading to 6.1, working sometimes, failing to announce calls other times, plus occasional VC crashes at boot claiming "out of memory" which is blatantly untrue.
Just out of curiousity, is everyone with this problem using Voice Command, or just some of us?
Think I might have to go back to WM 6.0 since 6.1 didn't solve my Bluetooth issues plus screwed up Destinator...oh well. Schap's WM6 4.31 was best ROM anyway.
Anyone having any luck with this problem?
Like I said, I was running AT$T WM6 with no issues. The I updated to WM6.1 and started having these call issues.
Last week I flashed to HD III still no joy. SJ says that he is running the same radio as me, 1.65.24.36 with no problems.
Is it " my " phone? Microsuck 6.1 ? The radio ? Has anyone solved this with a new radio flash ?
I run a business on this phone and it is getting really frustrating, I don't want to go back to 6.0 just so I can get my phone calls?
I'm not just whining, looking for sucess stories.
Hi, havent been here in a while but i thought i'd add to the list. I have recently flashed HD3 (one of the early november editions) and it was without problems until friday when i dropped my fone. Ever since then i have had the intermittent sound in call which is only fixed by a soft reset (exactly the same as denco7). I haven't changed the radio since dutty's 1st diamond rom (a while ago) as i haven't had any problems but now im thinking about it.
Current setup (from device info):
ROM version: HD_III_Jade WWE
ROM date: 09/30/08
Radio version: 1.65.24.36
Protocol version: 25.94.40.06H
Not using MSVC
Recently flashed to HD III Blackstone hoping this might work but still having the problem.
I also flashed radios 1.65.24.36 and 1.70.18.02
and now I am running 1.70.19.09....... and it is still happening. It has got to be something in WM 6.1. Cannot be a software conflict, because it was happening when I was running bone stock AT$T 6.1 upgrade with no software add ons.
Again, I would hate to think that I have to downgrade to 6.0 just to get my phone calls.
Damn WM6.1 sound!
Well, I thought I'd let everyone know that I've uninstalled all my favorite apps from my Kaiser. No MSVC, no S2U2, occasional hands-free Bluetooth, and no A2DP. In that time, I've had only 2 incidents of no sound for the last 3 weeks--much better than no sound every few days or even several times a day. Don't know that the apps have anything to do with it since denco7 had same problem on an unadulterated AT&T ROM.
The big question is why do we all have the same sound problem but most WM6.1 Kaiser users do not (if everyone did I'm sure there would be a lot more *****ing). If we could reproduce it at will, we'd at least have something to focus on. Not knowing that, I'll have to guess and say that I suspect one or more of the following:
WM6.1 and/or the 1.65+ radios required for WM6.1 introduced some sound bug (deadlock, dereferenced pointer, etc.). The more apps that interact with sound and/or the radio, the more likely the bug will be triggered. But even if this is true, why does it happen to us but not to others?
The bug exists only in a particular base ROM source used by the ROM cookers. Still, should be affecting more people.
Maybe people who customize their phones are more likely to reset and clear any conditions that lead to no sound? Doesn't seem likely, but hey...
The problem exists only in specific Kaiser versions, perhaps even in conjunction with only specific WM6.1 builds and/or radios. I think there's been 5+ different hardware versions of the Kaiser line, but I can't find where I read this or how to tell what version your Kaiser is.
Bluetooth affecting sound? Got absolutely nothing to back this up other than WM6.1 supposedly fixed a lot of Bluetooth problems and during the time of my frequent lockups, I was using A2DP to stream an audiobook to my car's Parrot MK6000. Finished the audiobook & quit traveling so much, so I rarely used Bluetooth during the last few weeks when I've had only 2 no sound incidents. BTW, I upgraded to WM6.1 specifically because of the Bluetooth fixes, hoping they fixed the 100% CPU usage after finishing a hands-free call and fixed the A2DP dropping after calls. WM6.1 didn't fix either, so what did they do? Maybe their "fixes" just introduced new problems?
Possible dead zone f'ing up the radio and consequently sound? I offer this only because when I was working in a particular dead zone I had frequent sound problems. For some reason, my phone has problems reconnecting after leaving this dead zone and I have to reboot. Occasionally it would reconnect without rebooting, but I never correlated this to no sound. However, I haven't been there in weeks, and my problems with sound decreased (although I also uninstalled apps & quit using Bluetooth as much). Went there last Friday, and while I was there I found I had no Windows sounds. Could dead zones or even just temporary signal loss be f'ing up the radio and consequently the sound?
These are all just guesses--I'm just throwing out some possibilities so we can find something in common between us. However, I gotta say that if I don't find a solution soon, I'm going to switch back to WM6. Threaded messages are nice, but they're not worth this no sound headache.
BTW, I'm using:
AT&T Tilt (purchased within a month of initial release)
ROMeOS v4.21.1 (OS v5.2.20273, AKU 1.3.3)
Radio 1.71.09.01
Newbie here...
Last week I upgraded to 6.1 Rom on my ATT Tilt (downloaded the tilt version from HTC site) and installed some common apps (google, msn livesearch, Java, Opera Mini, etc.) and just today I noticed that when I make calls the other party cannot hear me at all (I can hear them perfectly fine). I have not applied any hacks or anything. The phone was working fine until yesterday.
Are there any settings that I should look at...is this a known issue with the phone related to 6.1 upgrade?
Any help will be appreciated.
Thanks
Update:
The mic is not working but when I tap anywhere on the phone, the other party can hear the vibrations caused from the tapping. So, clearly somewhere the mic is picking up these vibrations, but it's not picking up the sound from my voice.
Seems that this is not a software or settings related issue but a mic placement or hardware issue.
Anyone with any ideas...any help will be appreciated.
Thanks
My X1 has had problems with it's Bluetooth cutting out during calls ever since I got it. Even after a replacement phone and the new R3A firmware the problem persists. So now I am going the custom route...
Can anyone recommend to me a custom ROM for the X1 that has had improvements to the Bluetooth implementation?
jhbodle said:
My X1 has had problems with it's Bluetooth cutting out during calls ever since I got it. Even after a replacement phone and the new R3A firmware the problem persists. So now I am going the custom route...
Can anyone recommend to me a custom ROM for the X1 that has had improvements to the Bluetooth implementation?
Click to expand...
Click to collapse
Never heard any cook do BT differently exept base on differenr WM built. I do patch the driver w/ HD one such that Cyberon VC over BT works. I never had bt cutting out during call but sometime AFTER the call (and it's a well known issue to all HTC device)
Perhaps it is worth to try other radio (you don't have to change rom, just update radio). I'm really not sure, but radio probably contains Bluetooth drivers too. Is that right?
netbat said:
Perhaps it is worth to try other radio (you don't have to change rom, just update radio). I'm really not sure, but radio probably contains Bluetooth drivers too. Is that right?
Click to expand...
Click to collapse
When flashing generic ROM you flash a corresponding radio (R3A with 1.14, R2A with 1.11 or 1.10). So this is probably no solution, but always worth a shot.
Diferent RADIOs are NOT the solution (I tried more than five radios).
I have tried more than 30 diferent ROMs in spanish and english, with WM6.1 and WM6.5, and no one go right with the Bluetooth.
I call Sony Ericson and they said that is normal because to save energy. It´s my first phones that disconect the bluetooth.
I've had all kinds of BT problems.
It usually turns of by itself, even in the middle of a call. (not so fun in the car, driving)
An I've also tried different ROM's and radios, no better.
BT is not very good on X1 I'm afraid... : (
mattiL said:
I've had all kinds of BT problems.
It usually turns of by itself, even in the middle of a call. (not so fun in the car, driving)
An I've also tried different ROM's and radios, no better.
BT is not very good on X1 I'm afraid... : (
Click to expand...
Click to collapse
Would you say that this problem affects all Windows Mobile devices? For example, if I get an HTC Touch Pro 2 am I going to have the same issues?
I have no idea really, I only have the Xperia.
Any htc owners here ?
jhbodle said:
Would you say that this problem affects all Windows Mobile devices? For example, if I get an HTC Touch Pro 2 am I going to have the same issues?
Click to expand...
Click to collapse
jhbodle said:
My X1 has had problems with it's Bluetooth cutting out during calls ever since I got it. Even after a replacement phone and the new R3A firmware the problem persists. So now I am going the custom route...
Click to expand...
Click to collapse
A friend and me, we both have the same problem as described by jhbodle since approx 6 months back.
During almost every call the sound is transferred back to the phone (as if I would have shut down the headset).
The weird thing is that bluetooth is still on and the headset is still treated as if it would be connected, meaning that I can still end the call by pressing the call button on the headset.
I can get the sound back to the headset (during the conversation) in two ways:
By choosing "Turn hands-free off" and then "Turn hands-free on" from the phone, or by shutting down the headset and then starting it again.
We have narrowed it down to that this happens whenever the phone disconnects from dataconnection (which seems to happen from time to time when using Activesync with Push - it disconnects and then directly reconnects). It does not matter if the phone is in 3G or GSM mode.
Have any of you noticed any similar problems during calls?
We are using the Swedish Telenor network. It might be possible that they have changed something that triggers the dataconnection to reset, and you on other networks are not beeing disconnected and therefore have not noticed this issue?
Maybe most of you are not using your dataconnections that heavely?
Those who are - could you test to disconnect the dataconnection while in call with TB headset..?
My friend have kept his phone with stock ROMs - he have had this problem with 3 or more different headsets.
I am flashoholic and have tried every ROM release from the top five cookers since the Hard SPL release for the Xperia. I have had the phone replaced once for a month ago - I have had this problem with both phones.
Hope you can help me to narrow this problem down even more, and most of all, I would like to know if we are alone with this problem..?
I have searched the forum for similar problems, but only found this one, so I did not want to create a new thread even if I it should be in the "General" category...
Oops... apparently I did not search enough - i have now found some other threads discussing this issue, but without any solutions.
I know that the most common BT issue for everybody is the BT deactivating itself after a call (I have had this from time to time aswell -especially after I have installed the MSVC software).
I don't want to start cross linking and dubbel posting, so I will wait and see if anybody has something to add to my previous post over here...
Would be nice to know if others, having this issue, can also link this to the dataconnection disconnecting.
How long are you talking on the phone for? I don't talk on mine for more than a few minutes, but occasionally I do get the 30+ minute calls that I have to deal with and I've never had blue tooth just shut off for no apparent reason.
For both me and a friend of mine, this happens during most calls regardless of the call duration (my calls usually take between 30sec and 10 minutes).
Sometimes, when I know that the conversation will take time, I reroute the sound back to the headset, but the same thing can happen again during the same call.
As I said, for me this happens whenever dataconnection disconnects on the phone.
Are you using dataconnection alot? Could you please try to disconnect the dataconnection during a call?
thanks