Wow thanks Ehud for going through all of this! Would it be too much trouble for you to do a new thread detailing the straightforward way to update the XV6600 BT stack for those of us on that phone with the connectivity problems. It would make it easy for alot of us on the verizon phone that are having this problem. Kudos for finding the solution! Also if theres a way to do this without having to do a hard reset that would be even better!
I can't take your thanks... mswlogo did all the work All I did is some Backup;Patch;Restore stuff (and keep notes
The answer is... you download the file at the front of this thread.
Then you copy the file to your pocket pc. (I used infrared send, some people use activesync, whatever you like
Then, using file explorer, I clicked on it on the ppc and it ran, extracted files, etc.
I then reset the computer.
Ehud
ok, I lied. There were some things I did that I don't specify because it's *my* method, but here they are:
1. I copied all files to my storage card, which I then locked (hardware) against changes. That way I can do an install, and the cab file stays there and doesn't get deleted. It also makes it easy to reapply after a hard reset if I need a hard reset. The storage card is also where I put the backup done right before the patch...
2. I used PowerPanel to do the reset, not using the hardware buttons.
3. I used TotalCommander not file explorer for a variety of reasons, not the least of which is I can move DLLs around easily
This is now the second time it's come out of hibernation and said it's unable to start the bt drivers. (memory error).
However, here's a quick fix that doesn't involve flight mode.
1. Turn on bt
2. Before it has a chance to bitch about the driver error, REBOOT. (I use PowerPanel)
3. It will come up with bt working.
I'm guessing there is a driver order conflict. Of course that's the sign of poor resource allocation. But hey, I was only a VMS kernel hacker for ten years. (VMS is the precursor to W/NT, which of course is the precusor to NT/CE).
In each case I've stopped all running applications, but of course not unloaded any drivers. I suspect something in the CDMA stack is the culprit... based on the earlier experiences.
E
... so I'm leaving the TGV party at Gordon Biersch brewery in San Jose for DECUS, and I hail a cab because the music is too loud and I just can't take it anymore.
An older gentleman asks if he can share my cab, and I said sure. On the way there one of my staff calls me (a Unixhead) and I have to walk him through a SET DEFAULT square bracket dot subdirectory square closing bracket etc. sequence.
The gentleman mentions he's from DEC, and I thought of the only name I knew from the comp.os.vms /info-vax board and said "You're not Steve Lionel, are you?" It was Apparently he knew my name also... It was a fun cab ride back to the hotel
My favorite VMS work was live in-memory loaded kernel patches.
I think im just going to bite the bullet, back up anything important, hard reset my phone, and then try to get this patch working. I'd imagine i would have a better chance of success if i experimented on a barebones device, no?
It did work better for me, but clearly on my device I have a conflict.
Try it once without a reset (after a full backup) and see if it works for you. If you get either of the two errors (no driver memory or license expired) we've already covered workarounds. If you get no errors, you've saved yourself a lot of work
Well i tried it without a hard reset and i got the memory error. Did a hard reset, installed the patch, rebooted, and turned on bluetooth without any errors. I tried calling my cell phone with the headset connected from my house phone, but when i answered the call all i could hear from my house phone was a weird modem-like noise. Thinking it might be a problem with the phone itself i tried picking up a call without the headset and i did not get the noise. What now?
Since you've got a fresh phone you're in a good position to try some things.
1. Soft reset
2. See if problem persists.
If not, shrug and stop.
Else:
1. Hard Reset
2. Apply the "3100 patch"
3. Try it then
4. See if problem persists.
If so, it's a headset problem.
If not, shrug, stick with 3100, and move on.
Im using a Moto HS280 headset if that helps at all. I soft resetted and tried to call the phone with the BT headset connected while the phone was on, the call came through fine without the noise. I tried turning the phone off and calling the phone again, the phone did not pair up with the headset until the call had been missed. I tried turning the phone off again and calling, this time the headset did pair up in time and i was able to answer the call with the headset, but this time i got the noise again . All other times after that the phone would not pair with the headset until after the call had been missed. Unless you have any other suggestions i'm going to try the 3100 patch.
Ehud, if you have an MSN/AIM screen name please PM it to me. I'd like to get this resolved tonight if possible, otherwise i'll just load my backup and put up with the BT issues until a fully working fix comes out.
Last edited by xxplosive : 12-26-2004 at 11:35 PM.
just installed the new 3500 on my 6601. I also got that memory error but I put the phone in flight mode and reset the device. Once it booted back up everything seemed to work. I will try it for a few days and post any problems I may or may not have.
After working with Ehud with getting the 3500 build to work on my XV6600 it is evident that it still does not work. Ehud believes it to be my headset thats causing the noise issues, but i'd very much doubt it . His headset is a Moto HS810 while mine is a HS820. Maybe if more people are able to get the patch to work i'll give it another try.
I would not say it is the fault of the headset but the fact that it is different and the patch is just on the edge of working. The patches seem more stable on PPC-6601.
I'm almost tempted to go back to 3100. On 3100 it really stayed locked on to the headset. On 3500-124 sometimes if it's been idle a while it puts up a headset Icon with a "?" in it. I think this Icon means it is Scanning for headset. When it does this it takes a few seconds. With 3100, I never saw this and it instantly always connected. But maybe 3100 drains battery more. I don't know.
If someone wants to experiment one evening via IM I can tell you some stuff to try. But be prepared for lots of hard resets and a long night with possibly nothing fruitful out of it. But you might get lucky too.
Would it be too much trouble for you to do a new thread detailing the straightforward way to update the XV6600 BT stack for those of us on that phone with the connectivity problems. It would make it easy for alot of us on the verizon phone that are having this problem. Kudos for finding the solution! Also if theres a way to do this without having to do a hard reset that would be even better!
All I did is some Backup;Patch;Restore stuff (and keep notes 
. All other times after that the phone would not pair with the headset until after the call had been missed. Unless you have any other suggestions i'm going to try the 3100 patch.
Login
Panel
