On a day to day basis (without VC 1.5) no. When I've been mucking around a lot (experimenting with stacks etc.), I have maybe seen it once or twice. VC 1.5 aggravates bluetooth enough that just about anything that can go wrong with bluetooth will but it is random. When VC 1.5 is on there it seems slower and more vulnerable to reactivate everything from sleep.

So do you think VC 1.5 could be causing all my problems with BT on the XV6600...Others have had success stories with the Audiovox update but mine remains impaired...I installed build 3900 and the static is less but it still has problems answering calls.

I just upgraded my XV6600 from BT3500 build to BT3900 build and I can't seem to find any difference. My BT3500 version is from Audiovox ROM update. Anyone know what the changes are?

No, but on the PPC-6601 going from new ROM Bt3500 to BT3900 reintroduces the memory error that was common on the "3500 C" patch. I think the BT3900 patch (like the 3500 "C") patch was designed fora GSM phone. So if you wish to run 3900 you have to live with that annoying quirk. quite a few folks with headsets and cars that misbehave on 3500 ROM's claim 3900 helps. See the the SX66 forum for further reading.

I tried quite a while to find what causes the 3900 to get memory errors but had no luck.

I see no gain with BT3900 on my BT devices.

Well... BT3900 is not designed for GSM phone like HP IPAQ 6315. You cannot update BT Tray (not compatible) on GSM phone. You need to keep the old version on HP IPAQ 6315 or you will get an error when you load BT Tray. GSM phones also have the memory error just like the CDMA phones...

I measured the radius and crackle-spots with a saved voicemail playing, for repeatibility. Then I upgraded from ROM-3500 to 3900.

The range is exactly the same. Same crackle spots, same characteristics using the same voicemail and walking around with exactly the same timing.

HOWEVER, my HS810 is noticeably louder. In fact, I've always had it on the highest volume settings and sometimes need to cup my hand around it. After the 3900 upgrade I am considering lowering the volume as it is almost too loud. Again, keep in mind this is with the same recording, same everything, only change is the stack upgrade.

Ehud

How can I tell which version of the stack I have installed? I just bought my XV6600 on Tuesday from some warehouse supplier, and when I go to BT: About, it says Version 1.0.0 Build 3500. I'm assuming that means it's build 3500 (I know, I'm like Dick Tracy), but I'm not sure if that would indicate 3500-B or -C. I've tried to follow this thread, also, but it goes way back to the beginning, and now I'm just plain confused about what I have, and what I *should* have. Also, does the fact that I have a camera matter at all? I don't think it should, but I figured I'd ask just in case...

__________________
_______
Spu|nik

first, you are fine with the new audiovox 3500 build, its the latest version.

I have run some tests also on the 3900 and can't see a difference, the jabra speakerphone is still quite, and the anycom car kit won't pick up. The HBH-300 works fine

Note that "B" vs "C" were my own versioning of attempts to get BT3500 Patch from the PDA2K to work on the CDMA phones.

If you have a VX6600 or PPC-6601 you should be using the new ROMs available that officially support BT3500 Stack.

BT3900 is a whole other deal and not worth the aggravation for most of us, but worth it for some specific cases (usually cars).

Three times today I received calls... answered on the bt headset, and yet the call audio stayed on the PPC, and the headset symbol had a question mark on it.

Back to rom-3500 for me.

E

sorry for the ignorance, but along ehud's lines, if you answer the call by pressing the talk button on the phone, is the volume supposed to be diverted to the phone rather than the headset? I can answer just fine pressing button on headset, but if using the phone buttons, i get the same question mark with the audio going to the phone. thanks

-nm

I'm a little peeved. Build 3900 stayed on despite a full sprite restore.

I had to do a hard reset and then restore. I looked in the cab and can't find anything except:
[HKEY_LOCAL_MACHINE\SOFTWARE\Widcomm\Version]
"Software"="1.0.0.3900"

But then if I modify that value (1.0.0.3500 in the rom build) to 1.0.0.3501 it still shows up as "3500" in the about settings.

So... how did 3900 survive a Sprite restore???

EHud

nuclearmonkey,

Yes that is how it's supposed to work and how you want it to work. I wish there was a similar easy way to choose on an outgoing call as well.

Ehud,

That's why I frequently say don't use backup restore around patches. I have not used restore in months because it's almost useless. My data is in Active Sync and on the SD card. Also are you running VC 1.5. With 3500 VC 1.5 and HBH-300 so far so good. I had 1/2 hr call with data up over headset while driving and the call was perfect. Beep of death would have normally kicked in. But if anything goes wrong I'll blame Vc 1.5 at the moment.

I'm still using 3500 with my 6600. I just received a new ax bluespoon, my third. With this one, every time I turn the bluespoon on i have to input the authentification code again (0000) before it will work. Every time. This didn't happen with my last two...

Any ideas on how I can fix this?

I haven't put VC1.5 back on. Running 3500ROM with Weatherpanel,SPB PocketPlus, PowerCheck, and things are good and crisp.

The next two things to come back on will be Intellidialer and Calendar+.

I still don't understand how a CAB file that installs normal files and updates a few registry settings can't be undone by a backup which includes the full registry and the prior versions of those files.

Ehud

Has anyone seen this yet?

http://www.blueridge.net/dereck/BT3900_B.CAB

New version of the 3900.
Found it on another thread - the XDA 111

The "prior" versions of those files are ROM files so it probably does not back them up. It has to know to delete something it never backed up !!!

Swap, yes 3900 has been around for a few days. See this thread and a thread in SX66 forum. Most of us do not see much benefit. But it does seem to help some folks with BT cars and stuborn headsets. But on CDMA phone you will likely get the memory error back. I tried it for while and went back.

Empty

I would make a CAB of "3500 ROM BT" except I can't get the cab maker to make a version that my ppc won't complain "is made for an earlier version of your OS".

The version in the cabs that do work has a build number of negative (some large number).... which I can't set with the tool I have.

Is there a better way to do it? That way I can make a "3500 ROM BT" patch, apply it, the files will be in flash, and will backup, restore, and not need to cause I can just repatch...

btw thanks for your info on GSplayer. That thread was closed when I tried to say "THANKS A MILLION!"

E