|
||||
Where did you expect sound to be routed?
__________________
Grammar: The difference between knowing your shit and knowing you're shit.
|
|
||||
Wow. WM users put up with a lotta crap to get their phones to behave like real phones. One shouldn't have to tell the phone "Hey I'd prefer THIS call to be private and not interrupt people nearby".
I just verified that MSVC was the culprit. I disabled it, and incoming calls go to the regular earpiece as it did for me under all conditions with WM5 + MSVC. It's not laziness, its purely annoying to have to switch off the external speaker for every incoming call... I love microsoft. Seriously! But I hate microsoft. Seriously. I hate that smooth-running iphones will become ubiquitous, and I'll be defending my buggy, awkward windows PDA. But defend it I will... |
|
||||
Thanks for the good advice, bivowalk! I was leaning in that direction, but glad to hear that someone else had and fixed the problem that way. Cheers
|
|
||||
If reflashing alone doesn't work, then check to see if you have Advanced Configurations 1.1 installed. I had the same speakerphone as default problem with that version of the program. Rebuilt my rom with 1.0 and no problem.
|
|
||||
I had the same prob w/ VC. Fixed it by going to VC under Settings, clicked VC, then notifications, and set it to "announce through bluetooth hands free only".
I can live with that. Love VC, other than this particular part of the program, I use it all the time. Use so much it's seems archaic to have to actually manually look up a contact and push the send button. |
|
||||
You know, I thought it was VC, but turns out I was wrong. It was just intermittent. I played with every VC setting, and turned it on and off... I think you're right about advanced customization. I'm going to avoid loading that prog...
BTW, fixed the prob with a simple hard reset, no reflash. |
![]() |
|
|
|