Jcrompton,

A hard reset? You must mean a soft reset since the 3500 and 3100 builds won't survive a hard reset.

To get the 3100 build to work (i.e. no memory error) I turn off the phone ("turn on flight mode") and do a soft reset. Then I turn on the Bluetooth before I turn off flight mode (i.e. turn phone back on). This will allow you to turn BT on and off at will until your next soft reset.

Good news !!!

I located the new PDA2K ROM and noticed i-mate applies a mini bluetooth patch on top of Build 3500. I incorporated this mini patch into a 3500 CAB. It fixes the AudioGW.DLL that caused DUN/Active Sync to shutdown when PDA wants to sleep. I had worked around this previously by using AudioGW.DLL from Build 3100. AudioGW.DLL is a critical component in the whole scheme of things, running the latest may get you over new hurdles. It also seems to have the speedy wakeup of the headset when PDA asleep that Build 3100 has. Still testing but looks good.

But, it still has that nasty issue of randomly giving a memory error. If you've learned to deal with that error on your phone then you'll probably want to try this out. Once you do get BT to start by what ever tricks you see above. Leave it on. If BT is on, on boot I never see the memory error. However, I have seen some actions shut bluetooth off for a moment and back on. That might be when some people run into the memory error.

I also uploaded Build 3100 again with Serial_BTUR.DLL removed. This restores the side buttons when PDA is asleep. I uploaded this because build 3100 has proven itself again and again with my HBH-300 on a PPC-6601. But I will be trying Build 3500 again with these new tweaks. I've never had a memory error on 3100 which is also why I like it.

All links are in the first post as usual. Newest at the bottom.

These are UNOFFICIAL. BACKUP. SYNCUP. And get your stylus ready for possible hard resets.

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

OK, I played all day with the 3500 build installed on my SX66. Good and bad news. The good news is that it paired with both my HBH-660 and my Acura's HandsFreeLink (HFL).

At first HFL would dial and answer, but the car's stereo wouldn't act as the headphones. For some odd reason it suddenly started working. It isn't 100% consistent. It always is capable of answering and making calls, but sometimes it will not act as the headphone. Very odd, I would expect the opposite. If it isn't being the headset I can say "transfer" which switches the audio between the phone and the car and that usually works. Once in a while when the car is doing the audio I can't hear the other end of the conversation. All odd.

My HBH-660 is not acting as good as it did on build 2400. I had the usual problems with connectivity before, but not this bad. Now the phone and headset seem to waver between seeing each other and not constantly, even during phone calls. I can't tell if standby mode is affecting it because it happens so often regardless of the phone being in standby. It even happens during calls, which is pretty frustrating. One thing new is the question mark within the headset icon. I hadn't seen that before. I get that constantly. Sometimes the headset icon dissappears entirely and sometimes it has a question mark in it. Either way this disables the ability to use the headset.

I did completely remove pairing and re-pair both devices to get this far. I will live with this until the next build. I would like the headset to work like it did before, but it is so cool to have HFL working in the car (albeit only about half the time) that I can't go back. People told me today I sounded like I was on a landline to them and they sounded better than ever to me via my Bose stereo. Incredible.

One question, why are the Bluetooth builds you are working on specific to CDMA? I would think GSM and CDMA would have little to do with Bluetooth. Anyway, if there is a difference I hope someone does all the great work you guys have been doing to a GSM phone to fix these issues for me. If you have any thoughts or suggestions, or hear of a new build, please let me know!

__________________
Jamison West
Seimens SX66 - Cingular

mswlogo.... Can you possibly post that extra Bluetooth ROM from imate as is? Perhaps it will fix more of my issues. I'd love to give it a shot...

__________________
Jamison West
Seimens SX66 - Cingular

mswlogo

Between the very first 3500 patch and the current one BT3500_CDMA_C_OEM_WWE_124_008.sa.CAB with the OEM_Patche_12100401.sa.CAB (http://forum.xda-developers.com/viewtopic.php?t=14329) on my PPC-6601, I have lost my Bluetooth modem support. With the very first 3500 patch, I could query the bluetooth modem and get a response, now I get "modem failed to respond, make sure it is properly turned on and ...". Do you think this is just my issue or a BT stack issue? By the way, I purchased an HBH-300 based on your comments, it does indeed have excellent sound quality. People tell me it sound just like a boom wired headset.

Thank you

mswlogo - Sounds like you've really figured this stuff out. My hat is off to you.

So you suggested just installing the 3500 ver B over my stock bluetooth files, while others recommended upgrading to the 3100 stuff, THEN going to 3500. What's your recommendation with C? Should I just try installing it, and if it fails hard reset and try it again?

I've got my backup if whatever I try fails. And with any luck, my bluetooth headset will be here shortly.

Merkman, "C" should replace everything 3100 put on. If you have trouble hard reset and try again on a clean device. I disagree with the need for 3100 first. But they were correct on the shutting off the radio to get around memory error. 3500 replaces everything. The confusion was the unpredicability of memory errors which I think I narrowed down. Behavior however may be different on VZ6600.

Understood. Kinda figured that was the way to go, but we all know what happens when we assume... or maybe that's just when *I* do.

In any event, once again I thank you for your kind attitude and great work sir. Have a great night!!!

P.S. My Logitech Mobile Freedom Headset has not yet shipped from Amazon, and may be out of stock. I see on their web site that they only have it available from Office Depot right now for $47.95, which is more than I paid for the unit including tax.

TimAA,

Couple things.

BT3500_CDMA_C_OEM_WWE_124_008.sa.CAB already has OEM_Patche_12100401.sa.CAB updates within it. I only put that file up for non-imate GSM phones like SX66 (since they had no other way to get that update and they can use the othe i-mate patches un modified.

I'm posting this over DUN with bluetooth using BT3500_CDMA_C_OEM_WWE_124_008.sa.CAB to double check. XP is almost as flakey with bluetooth as with the phone. I'd try stripping down the PC side. Remove BlueTooth Pairing. Remove Bluetooth modem etc. And let it rediscover it. Sometimes just a reboot on the PC is all that's needed. I've run into that.

jamisonwest,

I did post it, just for folks like you. I put it the proper forum.
You are really confusing things.
Be more specific which patches you used. You should NOT use the patches that say CDMA in them. You have a GSM phone.

I'm not posting instructions here because that will confuse folks with CDMA phones. Which is what this Forum is for.

Ask in the SX66 Forum.

I know, I know we have more fun over here. You should have got a CDMA phone

mswlogo

I am posting via BT DUN through my PPC-6601 and it is working well. Thank you. I do have another two questions.

Does the BT DUN connection use the BT Modem to connect? I am quite sure it does. (My HP tablet, Windows XP SP2, uses an HP BT patch which changes the MS BT stack back to the Widcomm BT stack, ). At one point around the first 3500 build I could query the BT modem from the Control Panel/Phones and Modems/Modems/"Bluetooth Modem"/Properties/Diagonostics/Query and get a response. Now I can not get a response but DUN works. Any ideas?

Do you think AT commands sent via the BT serial port are able to access and control dialing the phone?

Thank you

Well that was the missing piece for me. 3500 was still working perfectly, except for the range issue with the Jabra FS2500. I applied the above directly over the top of 3500_B and I still have all the same functionality (BT DUN/ActiveSync, good sleep/wakeup response) but now I can get over 15 feet away before I start hearing interference.

Thanks again mswlogo. You have singlehandedly taken my XV6600 experience and turned it from one of extreme frustration into one of wonderful success.

jamisonwest, I've got to ask... do the GSM versions have some kind of audio gateway profile? How are you able to ever connect the audio (not headset) from your device to your car? I was under the impression no audio gateway was available, much less sort of working...

Sorry if this is an ignorant question since I just came upon this thread:

Can I install the latest bluetooth patch on to my xv6600 without a hard reset? I would rather not back up and restore. I have the original bluetooth build on my phone.

It's never a good idea to tinker with software such as drivers for your hardware without a backup. Just in case. Better safe than sorry.

__________________
John

PDAPhoneHome Forum Moderator

jamisonwest,

I'm not sure about the query capability. There are so many variables here. Did you have Active Sync up. Did you do it perhaps after a call. Who knows. The only way to tell for sure would be to test with the stack you had working.

sdcot,

Like jpmihalk said always do the back up. It's easy. But just as importantly (for me anyway) is do an active sync too [that's my critical data].

As far as trying with out hard reset, it does not hurt to try (for this patch because this patch is a superset of all patches) (after a backup & activesync). If it doesn't work and you really want the new features and others seem to have had luck on your phone then it's time to hard reset. A Hard Reset device puts all phone in the same state (for a comparison reference). So much software out there that could be causing complications. Now that we better understand the memory error conflict with the CDMA radio I'm a little less concerned about the required need for hard resets. Some patches I have have files removed and you have to manually know how to remove them or hard reset. Also if you have previously patched it doing a restore may restore an old patch. So be aware of that too.

this is off topic, but what do you all use primarily to back up your PPC?

mswlogo -

I have been following this thread for a while. Thank you for your work on this patch. My Cardo Scala is functional now except for a couple of concerns (static & fit). Thanks again.

I use Sprite Backup Premium by Sprite Software. It's very flexible and even backs up the speed dial database and call logs and lets you selectively restore. It also lets you create self-executable restore files (.exe) on your SD cards... very handy!

__________________
John

PDAPhoneHome Forum Moderator

Ok. I have a 1 week old (almost) PPC6601 that I love. Not perfect, but doing what I expected. Next big thing is to install the BT patches. BUT, there are 11 pages here. I don't want to be up until the wee hours of the morning.

Could someone summarize what I need to do (or point me to the posts in the thread that will let me know)?

I don't have a BT headset yet, so recommendations on that would help as well. I have used a Jabra 200/250 in the past and thought it was ok. It was comfortable over my ear and fairly easy to use.

Thanks!!! (This way I might actually be able to get up for my way too early meeting in the morning............ )