I got the memory bug too. I seem to be able to consistantly work around this bug by going to Bluetooth/Settings then click "Bluetooth On". The Out of Memory msg always popsups up. I do not close the "out of memory" msg. I soft reset with the message still on the screen. I always restarts with bluetooth working. I will not see it again until I turn bluetooth off.
With build 3900, my HBH 300 works and seems to wake up fine, activesync works, file transfers works. VC1.5 seems to still not work.
When you say VC 1.5 does not work, you mean it degrades the headset or does not work at all. VC 1.5 works for me fine. It's just that I notice glitches on the headset when it's installed.
Yes, MS Voice Command 1.5 works well I just can not seem to control any part of it with my bluetooth headset. I use VC 1.5 to initate the call and build 3900 transfers the call the headset without any issues. The sound quality through my HBH-300 is very good.
To intiate the call I must use a button on the 6601 to activate VC 1.5 and then speak into the mic on the handpiece.
I wish I was able to wake up MS Voice Command with the button on the SE HBH-300, be able to speak into the headset and have it work the same as if it was connected to a wired headset or the mic on the handpiece.
By the way, thank you for all your work with these patches. They are such a big improvement over what we were sold.
Do you have more control over MS VC1.5 with your BT headset?
Ok, I was not referring to Voice Command through Headset.
With VC 1.5 installed the headset is a bit sporadic. Sometimes it willwork fine, other times it will not. I think it's a resource issue. I have uninstalled it and installe VC 1.01 and the problems went away. Now I put VC 1.5 back (with 3500 C) and th eproblems returned.
I don't know yet if 3900 helps with this issue or not yet.
Snow day today so I won't be using the headset (or PDA) for real much today.
I have the xv6600 and I installed build 3900 - now my phone doesn't work. It constantly says No Service if the bluetooth radio is on. Hmmmm....will I ever get a break with this thing?!
I was running the 3500 C, witht eh same results as everyone else: HBH-300 only really good headset; Memory error on reset;
VC 1.5 works OK, but of course not through the BT headset.
I just downloaded and installed the BT3900 version now out there:
Results:
VC 1.5 seems the same
The memory error has reappeared. With the new ROM upgrade to BT 3500, the memory error did not happen, (always did on the "patch" version.
It fixes just the same way. Turn on flight mode; soft reset; turn on BT; turn off Flight Mode.
Can't see any difference in performance as yet, but when I return home I will start on my drawer full of BT devices, that to date have been unhappy with our XV6600's
I would like to suggest that everyone follow mswlogo's example and post their devices. I am going to try the Audiovox patch and I have a VX6600. I am getting confused by everyone who has a PPC6600/1 and is having issues with the VX6600 patch. If the VX6600 causes problems on a VX6600 I want to know that. From what I read it seems that the patching a VX6600 with the official VX6600 patch is an improvement.
Sorry about the redundancy but I want to be clear.
I have an xv6600 and used the audiovox update...it was disappointing. It did not improve my performance with the Jabra BT250. Static was still horrendous and I was frequently unable to answer calls from the headset. I'm now using build 3900 and besides the memory issue it works much better - less static and more consistent pairing.
I've had just the opposite experience with the 6000 and the audiovox patch. my Jabra 250 is working great now. I don't have to cycle the booth tooth manager anymore when the device is inactive or I walk out of range with the phone.
I want to thank mswlogo and everyone who has contributed to this forum. It is the best on the web covering this topic.
I have gone through all the patches with more or less the same results as everyone else.
I now have installed the audiovox update and then the 3900 patch and for the first time it seems to be useable as a phone.
When I get an incoming call I see the phone wake up then the headset rings before the phone does and I can answer from the headset. When I leave the room and return the phone wakes up and reconnects to the headset. I am able to wake the phone up by using call button on the headset and use the redial. The only problem I still have is there is still some static on the headset, but I see light at the end of the tunnel! The next test will be to see if it works as well with vc installed.
Originally posted by kvm I want to thank mswlogo and everyone who has contributed to this forum. It is the best on the web covering this topic.
I have gone through all the patches with more or less the same results as everyone else.
I agree! Thank you everyone! I've installed the 3900 build and much like what you just mentioned I've not had any troubles with the exception of the memory error.
A little more info on 3900. If you hard reset a PPC-6601 (Build 2300) you must install BT 3500 "C" first as BT 3900 does not include all the fixes for the original PPC-6601. I assume the same goes for the XV6600 (Build 2400).
Now if you have a new PPC-6600, or a ROM updated XV6600 or PPC-6601 you can just install BT3900 on top of one of these after a hard reset.
So far I don't see much difference. But those with borderline headsets and cars might see some improvement.
I think VC 1.5 is still causing issues. Might work fine all day and suddendly wham, It flakes out.
So I'm sorry if I missed it, but what do we feel that the 3900 patch is doing for us above and beyond the 3500 "C" build? I'm pretty happy with my phone right now, despite it taking a few seconds for the phone to wake the headset as is.
Plan on waiting for more feedback on the new patch before I blindly install and need to spend an hour reinstalling things.
__________________
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
Originally posted by merkman So I'm sorry if I missed it, but what do we feel that the 3900 patch is doing for us above and beyond the 3500 "C" build? I'm pretty happy with my phone right now, despite it taking a few seconds for the phone to wake the headset as is.
Plan on waiting for more feedback on the new patch before I blindly install and need to spend an hour reinstalling things.
I loaded 3900 on top of 3500c on my sprint 6601 and it still works fine with activesync at home, and with my jeep bluetooth.
Question: Has anyone had the following problem with 3500C using the PPC 6601:
Headset: HBH-300
When the phone goes into deep sleep mode (turns off) the Bluetooth radio shuts down requiring a re-start upon power up. Periodically, I also get the memory error in conjuction with this problem. Seems to be hit or miss on the radio shutting down.