awesome stuff mswlogo. what is holding VoiceCommand back from working? when, if ever, do you think it will work? that's the only feature holding me back from driving to Irvine right now and purchasing the phone
Earlier today I tried making a BUNCH of phone calls with the newest patch for bluetooth (3500 ver "C") installed after a hard reset, then reinstalling all my apps, resetting my unit name, etc. While the phone dialed out normally, I couldn't hear ANYTHING from my speaker. Frustrated that I couldn't contact anyone, I proceeded with getting an emissions test on the car, getting new tabs, getting my new drivers licence, etc.
About 3 minutes from home, it occured to me to soft reset the unit. Upon doing so, I called home and the phone worked fine. Question is... what the hell had happened that had fouled things up? I had the bluetooth turned off, the flight mode off, and was simply travelling around town as usual. And while I have no idea if the bluetooth files are related to the problem... it certainly freaked me out for a bit.
__________________
Cingular 8525 with Black 3.0.1 ROM (WM6)
Paired: Sony MEX-BT2500 (car stereo w/ audio streaming, it's AWESOME!), i.Trek GPS w/ i.Guidence software, a few PC's
I am getting mixed results on my 6600 using a Belkin Headset. It seems to be hit or miss with answering an incoming call. I am also using the latest 3500 patch recommended by the author.
No memory issues except on my first restart, the recommended solution with turning flight mode on, restarting bluetooth, turning flight mode off, fixed it along with a soft reset.
Don't know what happened. Well before the patches, I've seen that sort of behavior. And I call it a Silent Beep Of death. My wife once got the Beep of Death trying to call me. And once in that state only a soft reset clears. I'd recommend running it for while longer and watch. If it misbehaves move back to one of th eprior patches that seemed to work for you.
RCPerkinsJR,
Not all headsets are equal. I think Build 3100 was slightly faster but the latest 3500 "C" is still working great with my HBH-300. If problems persist go back to a build that you think worked best.
GREAT work on the first post. The info is great and there is lots of it. Cudos to you for helping out the others here (especially me!!).
I have read it about 3 or 4 times now and I think I am ready to take the plunge. But I would be curious as to what headsets people are using with what patches. If that is in this novel of a thread, is there a way we could gather that and put it up front? Call me lazy, but 11 pages is hard to sort through. (at least without slumping over the keyboard or craning your neck looking at your PPC....)
Seems like it would be helpful for newbies like me. I'd be willing to help, but if someone already has a list going, that would be great too.
Originally posted by mswlogo All I can say it's not a bug.
Not sure if a HeadSet Profile was available it might work.
Try using the button on the headset first and then when an open audio channel is started (the headset icon will have changed to a headset active icon) use the VoiceCommand-mapped button on the device to start VC listening on the device. This works on my PDA2k (with only a hands-free profile and not a headset profile.) I can't say it's optimal, but it works.
Originally posted by jpmihalk Try using the button on the headset first and then when an open audio channel is started (the headset icon will have changed to a headset active icon) use the VoiceCommand-mapped button on the device to start VC listening on the device. This works on my PDA2k (with only a hands-free profile and not a headset profile.) I can't say it's optimal, but it works.
Great tip on build 3100 - that did the trick for me (except were noted below) . I also noticed, just for your info, that build 3500 seemed to degrade the performance of my 6600 over time, soft reset fixed it and within half hour, I was soft resetting again. I am not 100% sure it was due to that build, but, it started after I put it on my machine, and it was the last item installed on it.
This BT build (BT3100_CDMA_B_OEM_WWE_122_008.sa.CAB) and the Belkin headset works great! Good response on waking the phone up and being able to answer on the headset.
Here are the tests I have performed:
Turned the 6600 off using top button - called phone, phone woke up, answered using headset button.
Allowed 6600 to go off by itself (timeout) - called phone, phone woke up - could not answer with headset button.
reran above test - same result - answered it on the phone, and was not hearing anything on BT headset, had to use phone to talk.
Any ideas or suggestions? Why does it make a difference how the 6600 goes off (sleep)?
Originally posted by aarong awesome stuff mswlogo. what is holding VoiceCommand back from working? when, if ever, do you think it will work? that's the only feature holding me back from driving to Irvine right now and purchasing the phone
Uhm, this has never worked over HTC PPC phones to date....its the feature everyone wants.....1st gen HTC PPC phones, 2nd gen HTC PPC phones, and now 3rd gen HTC PPC phones and it still doesn't work.......people that have had all these devices have been hoping for over a year+ to get this feature to no avail......
Just "ramboed" the 3500 patch into a PPC6601, seems improved so far but will know better tonight when I use my headset a lot. One thing that was bad before was the line of sight issue. If my PPC was in my pocket I got major static, once I pulled it out though it sounded great. This is with a bluespoon AX and a Sony HBH-660.
So far have been able to put my PPC in a desk drawer and no static on the headset. Will test it tonight in my coat.
Originally posted by t_sqaured Uhm, this has never worked over HTC PPC phones to date....its the feature everyone wants.....1st gen HTC PPC phones, 2nd gen HTC PPC phones, and now 3rd gen HTC PPC phones and it still doesn't work.......people that have had all these devices have been hoping for over a year+ to get this feature to no avail......
we all gotta wait....
from what I had read I understood it was just a matter of a bluetooth profile missing, but now I understand this feature doesn't work on damn near any PPC phone. both saddening and confusing...
OK, I applied the build 3100 patch from the front page.
After reset the phone my today screen would hold the image that popped up from any application. Meaning if I pulled down the start menu it stayed along with anything else on that screen. Everything was functional just messed up today screen. So, I went into the Setting/Today and reset the screen i had selected and it cleared everything. Wanted to post that if anyone else ran into something like that.
This seems to be working much better now. My question is can do a backup now that i have this build saved? I don't have sprite backup, but if I do a backup now if something goes wrong will I have major issues trying to restore?
Is it safe to do a full backup now that I am not experiencing any problems?
Originally posted by DWIM I found my AX worked better w/the 3500 install.
So, question: I've been wondering about a comparision betw the AX & the HBH-660. I'd be quite interested in your observations.
Hmm, kind of a hard one. Overall I would say the bluespoon kicks ass, but the 660 is absolutely no slouch. Here are my comparisions:
speaker: 660 wins hands down. The speaker is louder and more clear than the AX, although the AX speaker is very decent, the 660 speaker is excellent.
microphone: you would think the tiny length/size of the AX would cause a worse mic, but the AX is hands down the best mic I have ever used on a BT headset. It is the absolute first headset where people would not know I was on a headset. The 660 headset was great, but still not "oh you are on a headset?" material.
size: Jeez no comparision. I looked like an alien invader with the 660, now with the AX at least I just look like a young senior citizen with a hearing problem. Comfort on both is awesome, with the comfort factor being won by a hair by the 660 because the AX "plugs" into your ear and kind of muffles outside sounds on that ear, not a biggie, but something you have to accept.
battery: pretty comparable, I think the 660 edges out the AX, but the AX has surprising battery life and the battery is user replaceable.
Now keep in mind the problems I have had with the AX, like static, line of sight issues and frequent disconnects were most likely due to the old bluetooth drivers on my PPC6601, so I will most likely upgrade my review of the AX to a more posiitve note after using the 3500 drivers for a bit. Overall I would HIGHLY recommend this purchase, it is a phenomenally small very cool and highly functional headset.
If you like the Audio on the 660, You can get the same Mic quality as the AX and Audio of the 660 by getting a HBH-300. The Mic on 300 is not detectable by the callee (they cannot tell your on a headset, no echo, no wind, no static). Even driving on the highway with windows open. I have not used an AX, but that is the purpose of the boom on HBH-300. HBH-300 has a super mic over HBH-660. To get good quality mic it needs to face you and be near your mouth, so it can turn down the gain.
P.S. It's nice to have these kinds of nit pick discussions rather than whine how nothing works.