See new thread

http://pdaphonehome.com/forums/showt...threadid=43586

This is the old Pre new ROM stuff below

===========================================

Summary of patches

Which patch:

The last patch called BT3500_CDMA_C_OEM_WWE_124_008.sa.CAB is what I recommend for PPC6601 or XV6600. I only test on PPC-6601 and usually on a Hard Reset device.

I keep all patches available for history sake. Newest is at the bottom. I keep BT3100_CDMA_B_OEM_WWE_122_008.sa.CAB as a backup.

Fixes (some fixes are problems from previous patches):

It fixes Dialup Networking over Bluetooth (including Macs).
It fixes some Headset Range Problems
It fixes some Headset Static Problems
It fixes some Headset Pairing Problems
It fixes some Headset PDA wakeup problems
It fixes Dialup Networking / ActiveSync over Bluetooth going to sleep while active.
It fixes Left side buttons not allowing PDA to wake.
It fixes Bluetooth turning on PDA and Screen randomly when idle draining battery.

What patches do not fix:

It does not fix Voice Command over the headset.
It does not enable PDA Audio over the headset (e.g. no MP3).
It is not perfect.

What does it behave like:

You will sooner or later get a memory error when turning Bluetooth on with Build 3500 patch. It was not designed for PPC6601 or XV6600 (CDMA). If you get the memory error don’t panic. Turn on flight mode, turn on Bluetooth, Turn flight mode off. Leave Bluetooth on, it does not drain battery much and is stable when Bluetooth is on at boot time.

If you have a data connection up and you decide to connect over DUN with bluetooth. It has a difficult time shutting down the data connection and bringing up the DUN one. Shutdown the data connection first before using a bluetooth Data Connection.

Hard resets and not restoring backup (why do I have to start from scratch):

As far as trying with out hard reset, it does not hurt to try (for the BT3500_CDMA_C_OEM_WWE_124_008.sa.CAB patch because this patch is a superset of all patches). Backup and ActiveSync first no matter what. 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 phones in the same state (for a comparison reference). There is so much software out there that could be causing complications. I don’t want to be answer questions, “why doesn’t my X button work now” because you have some whiz bang Today Screen that buggy. 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 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.

To Check your Bluetooth stack version:

Go to Bluetooth Icon
Choose Bluetooth Settings
Choose About Tab
Choose Advanced... button

Rock Solid Install:

Backup (to SDIO card or PC).
ActiveSync
Hard Reset
ActiveSync as Guest
Copy patch to PPC, On PC Copy to either:
My Computer: \Mobile Device\Storage Card
My Computer: \Mobile Device\Storage
Turn on Bluetooth (so it will be on when you are done)
On PPC Use File Explorer and Browse to where you put the patch
Now click on the Patch.
Soft Reset (if not done automatically).
Delete the patch from PPC if still there (it often is no longer usable).
Test your headset and Bluetooth devices.
Do real ActiveSync (delete existing partnership while disconnected).
Reinstall Apps.

Rambo Install:

Backup (to SDIO card or PC), Rambo still does backups.
ActiveSync
Copy patch to PPC, On PC Copy to either:
My Computer: \Mobile Device\Storage Card
My Computer: \Mobile Device\Storage
Turn on Bluetooth (so it will be on when you are done)
Soft Reset
On PPC Use File Explorer and Browse to where you put the patch
Now click on the Patch.
Soft Reset (if not done automatically).
Delete the patch from PPC if still there (it often is no longer usable).
Test your headset and Bluetooth devices.

If Problems:

Hard Reset
Restore Backup
Soft Reset
ActiveSync
Clean up

What if an Official patch comes along:

It may not overwrite everything these patches did.
You may have to apply the Rock Solid Install method using the official patch.

Headsets:

Stay away from: Jabra BT250 and HS820.
mswlogo favorite: HBH-300 (but it's not for everyone)
Good reports on: HS810, BlueSpoon AX, HBH-660

Risk:

This is not without risk. However I never had a single hang, crash, reset, or hard reset in the dozens or so of experiments I did. Except for Bluetooth itself not working.

There is another risk. That people stop complaining to carriers about the bugs because these patches fix their problems. Or they become passive and wait for i-mate hacks like this one. Make sure you KEEP COMPLAINING. Do you have a complaint in now?Threaten to cancel and send the phone back. These patches are proof that it can be fixed proper. There are also many issues not fixed with these patches.

Memory Error Causes using Build 3500:

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 with a Memory Error.

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 every time. 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 makes sense.

GSM Phone Users:

DO NOT USE these patches on PDA2K/SX66/XDAIII use originals from Club i-mate (folks have had good luck with them on SX66). Read the PDA2K forum. I’ve made suggestions there too. These patches may run, but your phone might be even more stable with more capabilities if you use the i-mate patches.

Patches (from oldest at top to newest at the bottom):

Build 3100 (rev 122 side buttons will not wake PDA when asleep audio drop outs on HS820)

http://forum.xda-developers.com/download.php?id=2175 (BT3100_MAX_OEM_WWE_122_008[1].sa.CAB)

Build 3500 (rev 124 released 12/23/04 DUN/ActiveSync shuts down on sleep)

http://forum.xda-developers.com/download.php?id=2222 (BT3500_CDMA_OEM_WWE_124_008[1].sa.CAB)

Build 3500 (rev 124 released 12/23/04) with AudioGW.dll from Build 3100 to fix DUN/ActiveSync on PDA sleep)

http://forum.xda-developers.com/download.php?id=2241 (BT3500_CDMA_B_OEM_WWE_124_008[1].sa.CAB)

Build 3100 for H6315 ONLY (removes registry script and BTTrayCE.exe)

http://forum.xda-developers.com/download.php?id=2264 (BT3100_MAX_OEM_WWE_122_008_T2[1].sa.CAB)

Build 3500 for H6315 ONLY (removes registry script, BTTrayCE.exe and KeyBddr.dll)

http://forum.xda-developers.com/download.php?id=2346 (BT3500_H6315_C_OEM_WWE_124_008_T2[1].sa.CAB)

This is Build 3100 with Serial_BTUR.dll removed to restore operation of side buttons when PDA is asleep. (For Hard Reset Device only). If you already installed 3100 remove Serial_BTUR.dll by renaming it and rebootting.

http://forum.xda-developers.com/download.php?id=2302 (BT3100_CDMA_B_OEM_WWE_122_008[1].sa.CAB)

This is Build 3500 + Additional patches from PDA2K ROM that has a fixed AudioGW.DLL that fixes DUN/Active Sync when PDA wants to sleep and HeadSet Wakes up as fast as Build 3100 does.

http://forum.xda-developers.com/download.php?id=2301 (BT3500_CDMA_C_OEM_WWE_124_008[1].sa.CAB)

This is a seperate OPTIONAL patch released directly from BroadComm to add support for Stereo bluetooth headsets and bluetooth keyboards. It can be installed with or without the above patches. But it should be installed last if you decide to use it.

http://forum.xda-developers.com/download.php?id=2574 (PDA2K_BroadcomCorp_BTUpdate.cab)

This is Build 3900. Source is unknown but I did install it on top of 3500C (Rambo style). I have ActiveSync'd and Did a quick test on HBH300 and it connected ok. I have not used for general use yet. I will update this later with my feedback as well as others. Yes, it still has the memory bug. But it may behave better on a newly updated XV6000 or SX66. Thanks to outz in SX66 forum for finding it. It appears to replace all the files in the 3500C patch. So it should install on a hard reset or on top of 3500C. But I don't know all the historical changes in the registry.

http://www.blueridge.net/dereck/BT3900.CAB (BT3900.CAB)

Lots of Downloads and no feed back on patches. Need feedback for others. Sucesses or failures.

The latest 3100 patch on a clean PPC-6601 appears to me to be working fantastic. No crashes, no hangs, stayed paired for days, with sleep and being out of range for extended periods and battery is fine.

I also updated the FAQ on headsets and patches.

When giving feedback, state, phone, patch, headset and is sleep works.

Is this an update for both the XV6600 and PPC6601? I'm not going to try this on my xv6600 until someone has gotten it to work fine on theirs. Neither of those links work BTW...

Somestimes that server is down. Try again later. No feed back on this patch on a clean XV6600 yet. For that matter no feedback on PPC-6601 besides me.

I'll call up verizon tommorrow to see if theres anything they can do about it. Hopefully someone has raised hell with them about this so i wont have to.

I will give it a shot on my VZW unit. But alas, like the previous builds I doubt it will work.

Well, I tried it, and once again here are the results of trying it on a VZW unit.

"The Bluetooth Radio failed to turn ON due to unsufficient driver memory available. You must perform a normal reset before you can turn ON the Bluetooth Radio."


So another hard reset for me, and re-install my programs.

It sure would be nice if someone else would try these things too....

Which patch and did you HARD RESET first?

I digress... Apparently I did something wrong the first time as I do hard reset and setup from scratch but I gave it another shot with patch 3100 (updated one), and was able to get it working this time.

I will set things up and see how this newer patch works. Hopefully it cures my headset issues, and I would hope that it takes care of the screen coming on randomly (although your probably right and the files with the 3500 stack fix that).
Only negative? Setting it all up once again...

That's great to hear. And I hope other folks appreciate the time you spent.

I'm running 3100 too.

I do see the screen come on now and then.

But I've been paired for 3 days now and have not had to restart Bluetooth once. Or re-pair it. And the battery seems fine.

As far as I'm concerned this device is completely working except voice command.

Okay, I got everything set back up, and I don't see the screen come back on like it was before so that is a good sign. I also made sure that my Moto HS820 works, and I have no issues so far....

"crossing fingers"

Oh and the Voice Command thing is an issue with the voice command software itself....From what I heard, Voice Command 1.5 is suppossed to be out any day now, and has a slew of new features, and hopefully full support of bluetooth headphones.

So is it a DO INSTALL ON XV6600 or DO NOT INSTALL ON XV6600?

Mine's due by 1030am

E

Well, its only been a few hours, and so far build 3100 is working okay for me... but again... its only been a few hours, and I don't see any other test dummies with VZW phones trying it out.

Well, I just couldn't go on allowing everyone else to have all of the fun

I have a PPC6601 and tried both patches just now.

I loaded the 3100 patch first and got the memory bug. Reset (hard) the device and loaded from scratch. Everything worked fine. I still was unable to go from the "sleep" mode and still have the BT working, however I just quickly turned the BT on and off and it came right back up. (SUPER!!)

I figured that since I had already performed a hard reset and everything was wiped (but backed up ) I might as well try the other one. So I did.

3500 was no good for me. I got it to pair just fine....maybe a little slower than the 3100 now that I think about it. BUT, when I went to try and dial out, I got nothing but noise.....you know, the noise like you turned the headset on when not in a phone call. (I don't know how else to describe it). I hard reset again and tried it once more.....same thing.

Oh well, 3100 works like a charm for me. At least it lets me quickly turn the BT on and off to repair the headset. Oh and speaking of headset, mine is a Jabra 250.

Hope this helps....if you need more info, I will gladly see what I can do to help out.....unless it entails a hard reset. I will now spend the next hour loading everything from scratch.

What joy

__________________
I have enough trouble overcoming my own limitations without fretting over the fact that God hasn't seen fit to distribute evenly the gift of intelligence.

With 3100 patch: insufficient memory to load bluetooth drivers; reset. (Does not work).

Without 3100 patch, stock XV6600 delivered today... paired up with my Motorola HS810 NO PROBLEMS.

Ehud

Is anyone on an XV6600 with the new BT patches installed still experiencing the headset connectivity problems when the phone comes out of sleep mode?

OK so once I got everything loaded back on the 6601, I got the memory error.

Count me out from now on. I can live with shoddy bluetooth until a better update come out. At least it worked.

__________________
I have enough trouble overcoming my own limitations without fretting over the fact that God hasn't seen fit to distribute evenly the gift of intelligence.

No issues here yet. I have loaded a few programs and not seeing the mem error, however, I have a few programs not loaded yet. I wonder if it isn't related to a certain program that is loaded, hence the "memory" error.... hrmm...

mboliver,

You did not run a restore did you?

If not, which program tripped it up?

I admit I don't have a ton installed. Voice Command, Resco Explorer, AIM 2.0.

The only app I have not reinstalled is the microsoft reader. Since I was not sure I needed it.

xxplosive,

When running the old 3100 patch I had to periodically toggle blue-tooth to get it back exactly like you described and it would immediately re-pair up on its own.

Since running the later 3100 patch with a hard-reset it has stayed paired through sleep. HBH-300 headset PPC-6601 phone. In fact it has caught me off guard a couple times that I forgot I had the headset in my pocket and it connected to it.

Also on recieving calls I have to hit a button on the headset to pickup on headset (even if headset and phone have been idle for a long time or seperated). When making calls it automatically switches to headset.

I have all the sames apps installed that I tried to restore (except reader). Restore would not work with build 3500. I think there are config files, registry and order that have to do with it.