was what I had heard about the patch being bugged accurate?

also, do you know more about what the patch is and is not?

The offical patch will hopefully fix all our bluetooth problems with handsfree headsets and will hopefully take care of the popping noise people say they hear with the hp bluetooth stereo headphones. Im excited to see if thats true. I just ordered the headpones from HP. I know I will be disapointed but I know they will make improvements

-nate

I borrowed my buddy's H6315 phone again and tried Build 3500 again. I found the problem and it seems to be working fine now.

In fact it seems to be working better than on my PPC-6601, because it can do PDA Audio.

This may fix some range and static problems.

I did not test a lot. I will report later on how well my friend thinks it's running if you want to wait.

The links to patches are maintained in the first post of this Thread.

so wait, you're telling me that if I go grab build 3500 and install it on my system, it will actually work? (6315, currently running the 3100 build somewhat successfully)

I would *love* to lose the static.


edit - specifically, what did you mean by "found the problem"?

k installed 3500 and it seems more static-y, but I could be wrong. I'll play a bit on my lunch hour.

Which headset are you using?

Some headsets just don't get along with these phones currently.

It does not work for everyone.

I'm glad it installed smooth anyway.

HS820 has no static. But I don't like this headset because it's not as clear as others.

HBH-300 will still not pair with this phone.

But it's real clear with PPC-6601.

jabra bt250

and i take it back, the static-y thing was before another soft-reset. seems a BIT better now.

I'll let it go a day, but no obvious issues yet.


let's hear it for early adoption!

has anybody tried this patch with the HS810? It's a pretty painless pairing to begin with, compared to some of the other headsets. But I would use this patch if somebody noted a real benefit with the HS810.

__________________
-nickster

I'm pretty good with a bowstaff.

I have the 6315 and HS810 &820

Huge improvement with the HS810 and the 6315 with the new 3500 patch mslogo put out! Its a must try! Ive used it for about 4 hours now. The major problems with the last one (patch 3100) was people not being able to hear me on the other end. There was no audio what so ever.

This new patch fixed that and people say it sounds excellent. I did a hard reset then applied the patch. I also gotbrave and restored a backup from this morning. Everything still works great!!

Thank you again mslogo for the time you put into this new release

-nate

loop,

jabra bt250, that's your problem. May work fine with other phones but not yet on this stack. Other headset work much better.

HS820 works almost perfect and is light. But it's 75% the quality of the HBH-300 for receive and 50% the quality for send. However HBH-300 will not work on this phone yet.

I suggest a Plantronics M3000 (but I don't know if it willwork with this phone with or without patches). I've read consist good reports on these Microsoft based PDA phones with that headset that previously had a Jabra or HS8xx.

thanks mswlogo -

turns out that the 3500 works BETTER for the jabra than the original firmware, it seems. i could be wrong, but my reception is certainly much better.

I am not thrilled with the range though, and yeah, I imagine this is something that may eventually be fixed. I hope. otherwise, this headset's really nice.

I noticed I didn't answer loops question. The "problem" was the keyboard driver made the phone misbehave. 3100 didn't include an updated keyboard driver but 3500 did. So I simply removed it.

mswlogo,

3500 kit worked better for my Logitech Freedom headset....Now when my headset goes out of range with the ipaq, it shows a ? in the headset icon when it is back within range. However it does not connect back automatically.

At least a big improvement.

regards

__________________
PeterQ

I've seen that behavior on various patches with various headsets. I didn't test everything on the H6315. The headset that behave the best in that regard is the HBH-300 on my PPC-6601. But it refused to pair with the H6315. We had similar problems on the PPC-6601 with no patches with most headsets. But now the HBH-300 can walk a block away. Receive a callon handset. Then get back in range and recive the next call on the headset.

The patches make bigger improvements to some headsets than others and I don't think they are done. You can wait or experiment with other headsets.

Can a moderator make this thread sticky. Please

Indeed, this should be a sticky at least until an official patch is released.

neskifstad, you said you did a hard reset followed by a backup restore. Did the patch stay on even after restoring the backup? Ideally I'd like to do this without reinstalling everything, so being able to restore a backup would be ideal.

__________________
-nickster

I'm pretty good with a bowstaff.

ahhhh... that would explain the problems I am having now.

I get locked in suspend....

so how did you remove it? which file (in the cab) did you pull, or was it obvious?

I'll look in the morning.
(Sticky this, seconded/thirded)
Thanks again, mswlogo, you rock.

njbair,

I did a hard reset - applied patch - soft reset - then restored backup. I would recommend testing out the quality after the hard reset to see if it changes at all when you restore a backup file. If it does youll have to go back and after another hard reset and install your programs one by one to see what one causes the fuss!!

-nate

I agree, please sticky this post.

thanks again mslogo

It depends on the backup program and what you had when you backed up. If you had 3100 restore may restore that.

You can check your version of all bluetooth components see FAQ.

You could also try reapplying the patch again.

This why I say Hard Reset Install Patch and then install apps and resync is the most reliable. It's hard to rpedict what you will end up with if you do a restore.

Watch out for the "Event Notification Bug" too in all PPC WM2002/WM2003 PDA's.

just a quick bump to mswlogo in case you didn't see this question. Thank you in advance!