I think I put 2 + 2 together today around the memory error.

When you first reboot the phone it goes out and scans for towers this can take a bit of time.

If you try to start bluetooth while it is scanning it collides.

This is why I noticed early on if I kept retrying to start bluetooth eventually bluetooth would start. If I shutoff bluetooth and reboot and immediately start bluetooth it will fail everytime. If I wait a while it will start fine with no error.

This is also why, as some clever folks noticed, that if you shut off the CDMA radio (turn on flight mode). Then start bluetooth you can get Bluetooth started and then turn the CDMA radio back on.

This also makes sense that if bluetooth is on, on reboot it works. I think bluetooth starts before the CDMA radio starts scanning on reboot if bluetooth was on when you rebooted.

Sometimes the CDMA radio can scan for a long time if it's on the fringe area or lots of towers to sort out and optimize signal (I love CDMA).

This also makes sense that it's a problem on our CDMA based phones because the patch was never designed/tested on a CDMA phone.

It's all making sense.

By the way BT3500_CDMA_C...CAB is running really good on PPC-6601 with HBH-300.

I have both home and work running on ActiveSync Blue tooth (could not get work running before [USB Doggle type]). I also had ActiveSync and HeadSet running at the same time. I even transfered data over activesync bluetooth while in a bluetooth headset call to see if it would effect it. Stayed solid. Range seems good to. My Kitchen/Dinning area is about 25 ft long. I had the phone in the dinning area while I got breakfast together in the kitchen talking to my wife and it stayed clear.

I think it's time for the bluetooth GPS