Update on this 3500-124-CDMA patch.

If the phone goes to sleep, DUN or Active Sync disconnects.

Headset still working good.

At this point if your priority is Headset you may want to try it. If your priority is DUN or Active Sync stick with 3100.

XV6600. [full backup]

Installed patch. Turn bluetooth on - insufficient memory, perform normal reset.

Performed normal reset. Turn bluetooth on - insufficient memory, perform normal reset.

Performed hard reset. Reapply patch.
Turn Bluetooth on:
"BTTrayCE: Sorry! Bluetooth can no longer be used because the license is expired."

Perform hard reset.
Restore from backup.

The driver portion did appear to load... it's the app that won't start.

I hope this helps.

Ehud

Ehud,

If you have time to burn try, putting back your original BTTrayCE.exe

I'm backing up as we speak.
How do I put back the original BTTraceCE?

(I mean, are you saying "Find it on your current system, copy safely, do the upgrade, restore on top of it? or something else...)

Ehud

Hmm.

Backup.
Apply patch.
Turn on flight mode
Reset

Phone reboots.
Turn on bluetooth.
NO DRIVER message.
Turn off flight mode.

Sync up headset.

Decide to do a reset with flight mode off to see if that was a factor. (I hate a testing methodology where the tester introduces random behavior

Phone comes up.
Bluetooth headset is instantly synched... much much quicker than before.

Will see how it performs after sleep.

Ehud
p.s. for clarification, last time it would not start the bluetooth after the patch at all. I had to hard reset to apply the patch, and then the driver was ok but the tray wasn't. This time it DID start bluetooth and it IS working.
(The phone was restored from a full backup just prior to the first patching.)

Short: It works

Long: set the phone to sleep after 1 minute on external power.
Waited for it to go to sleep.
Watched it for an additional minute as every 6 seconds or so the bt light would blink.
Called the phone from a landline.
The phone woke up, immediately showed the headset icon,
the headset beeped.
I answered with the headset button.
About 1 second of no audio and then the call was connected on the headset.

Preliminarily I would say this works

Ehud

Eduh,

Great details and good news.

Sorry, but I'm just still a little confused on what made it work the second time.

Keep in mind about the issues I sited about DUN and ActiveSync will stop if phone goes to sleep. Be curious if you see the same. A work around is to shut off going to sleep when using DUN or ActiveSync (which in practice is possible). I'd also be curious if the i-mate has this problem.

By the way I've been up on DUN with laptop for 1hr straight while wife drives from CT to MA. With powersave off.

I also have had a heck of time pairing my HBH-300 on builds 3100, 3500-122, 3500-124. Once I get that shortcut it's good until I delete it or hard reset. But creating it, is a cat and mouse game. One other issue is after soft reset, first call will not always grab headset. But after that it will work everytime (even after long sleeps).

I just installed the new 3100 patch to my ppc6601 with no issues.

-soft reset
-full backup
-soft reset
-copy .cab to windows dir, unpack.
-soft reset

seems to place and recieve calls fine on my HBH-300 headset. I will test it further over the next day to see if it maintains its pairing reliably.

I do not yet have a bluetooth card to use DUN with my thinkpad but I should have one in the next week along with a BT GPS to test out with the new BT patch.

My first name is "Ehud". My username here is "Ehud". I'm not sure if you're dyslexic or have a poor sense of humor... but in any case, in the spirit of the season and adulthood, let's move on.

Me too. Here is *exactly* what I did
1. Start with XV6600 with software installed. Let's call this State0.
2. Backup State0 to 0-backup.
3. Run CAB to install 3500 patch.
4. Attempt to start bluetooth - insufficient driver memory, wants a reset.
5. Reset
6. Attempt to start bluetooth - insufficient driver memory, wants a reset.
7. Hard reset. Let's call this StateH.
8. Run CAB to install 3500 patch.
9. Attempt to start bt - driver seems fine, but tray complains of license issue.
10. Restore from backup (State0) and reset
11. Now at State0 again.
12. Go about daily business.
13. You suggest trying patch with old bttray.
14. Copy bttrayce.exe to storage card.
15. Make NEW backup. Let's call this State1. State1 is the same as State0 except I've received some more email, etc. (It's an antecedant state).
16. Turn phone functions off (flight mode, so as to prevent new sms from making the backup file outdated)
17. Run CAB to install 3500 patch.
18. Attempt to start bt - succeeds. Note that in this case the device is *exactly* the same as before except that I've added a half day of use to it, and a few messages in the inbox, and I've turned the phone function off.
19. Turn phone function on. All still works.
20. Reset device. All still works.

I cannot explain why 1) Did not work on State0. 2)bttray complained on stateH. 3) worked on State1.

I _can_ definitively tell you that I performed these steps as outlined here, because I made sure not to introduce user error into it. The exception to the rule was flight mode. If you like, I can repeat this with and without setting flight mode and see if it makes a difference.

For now it's been about 22 hours of solid performance with the headset. I've even tried having bt off... have a call come in.... take the call.... ask the caller to hang on... turn bt on, and voila it synchs up with the headset and the call is now ON the headset.

I have not yet tested it... but I will do so shortly.

I have not had a similar problem. My HS810 paired, worked, and was flawless throughout. It has behaved since your 124 build as I would have expected a non-problematic device to work - in other words an average user would not have had to think about it.

Ehud

when I moved to the 3100 122_008 BT build my HBH-300 paired quickly and without incident.

OK, I located which file causes DUN and ActiveSync to shutdown when PDA goes to sleep. Strangely enough it's in AudioGW.dll.

I've taken AudioGW.Dll from 3100 Build and it all seems to work.

I think 3500 gives better Headset Audio more consistenty, but I'm not sure by using AudioGW.dll from 3100 build will lose that edge. I don't think so. Only time will tell.

If you want to try I've attached the one file from the 3100 Kit for convience. You may have to rename the existing file on your PPC to something like AudioGW.dll1 and then put the attached file (after unzipping). This file goes in the \Windows directory of phone. It's easiest to use ActiveSync connection then use XP File Explorer.

If it looks good I'll make a CAB.

P.S. wish we could get somemore conversation going with i-mate owners so we could compare notes on behavior.

Attached Files

audiogw_3100.zip (8.2 KB, 50 views)

Backup.
Rename old DLL to ..-OLD.DLL
Moved new DLL to .DLL
Reset

Turn Bluetooth on:
"BTTrayCE: THe Bluetooth Radio failed to turn ON due to insufficient driver memory available. You must perform a normal reset before you can turn ON the Bluetooth Radio."

Flight mode on.
Reset.
Turn bt on - same error.

Hard reset.
Apply 3500 CAB.
Reset.
Install Total Commander (file explorer won't show DLLs)
Rename old .OLD, move new into \windows
Turn bt on - works.

Restore contacts, calendar, email, so I can use the phone in an "interim no applications installed" mode to test bt, without losing contacts/conversations.

Will test bt for headset and DUN and report further.

Ehud

Headset remains solid.

BT DUNS works, even after phone goes to sleep.

Called the phone.

Phone woke up, headset beeped, took the call via the headset.

At that point it said Bt lost connection to the DUNS client.

Wmodem was still running. I could have reestablished from the laptop... but is it supposed to be that way?

Ehud

Hard reset.
Restored from backup.
BT would not start - driver memory error.
This is making me think that either I'm going crazy, or sprite backup isn't doing a good job, or that there's something that these patches are doing that is outside the scope of the backup/restore process.

Hard reset.
3500-124 build.
New dll
can't start -bttray license issue
Copy old bttray (from 3100)
reset
Starts fine.

That should not have happenned. The original restore should have taken me to my 7:17am backup which was the 3100 stack working fine.

The hard reset and then 3500 build should have behaved EXACTLY as the last time I did that...

Any thoughts?

Ehud

I appreciate all the info you folks are creating on this process. My VZW XV6600 out of the box worked fine with BT, so I haven't tried to change the drivers.

I am learning, so thanks.

Ehud,

Thanks for your info. You are not going crazy. I've done what I think is the same thing twice and got different behavior.

If you ever get the memory error. Try waiting a few seconds and try turn on again. After a boot I think some things are still going in the background. Try this a few times. Many times with 3500 I say start BT, it gets error, start again gets error, start again and it says ok. It always starts smooth if already on at boot.

Also when you say "new DLL".I assume you mean audiogw.zip I uploaded.

I have not figured out these backup programs quite yet. That's why I said only sure fire way is hard reset and apply patch and rebuild. But there most certainly are shortcuts if you know what you are doing. Amazingly I avoided a hard reset after about 6hr's of testing different combo's to find audiogw.dll issue.

Build 3100 is definitely the most stable. Still not sure if 3500 really is much better or not and worth putting up with it's quarks. 3500 is much better behaved with audiogw.dll from 3100.

If I see any missbehavior I'll bttrayce like you did from 3100.

Oh and I think it's normal that the DUN will shutdown when call comes in (on PPC-6001 not sure about EVDO). And on PPC-6601 anyway you don't need to run wmodem for bluetooth DUN connection.

Thanks for the info No more wmodem for me.

I am currently running 3500-124 with bttray from 3100. Yes by DLL I meant the AudioGW file you zipped up.

This is a "new" build since I couldn't get any of my backup states to run bt. I did not wait a while -- will try that next time I have the error message.

Thanks for all the help. This thing is incredibly stable... Let me know if there's anything else to test.

Ehud

Since Ehud and I had good luck so far with 3500 and AudioGw.dll from 3100 I attached a new build 3500 CAB with AudioGW.dll from build 3100 in a Build 3500 CAB. See first post in this thread.

Oh and I have successfully installed either the audiogw.zip or this new CAB on top of Build 3500-124 without hard resetting.

Quick Hint: If you're seeing the driver memory error, turn on flight mode, reset, turn on bt, turn off flight mode.


More data:
I turned off bt for a while.

Then when I went to turn it on I got the driver memory error.

Tried again over multi-minute period with no apps running -- NO success.

Reset.
Tried again over multi-minute period
with no apps running -- NO success.

Reset.
Repeat.
NO Success

Turn on flight mode.
NO success
Reset [with flight mode on]
Success
Turn off flight mode.
Still on
Reset
Still on.

E

FINALLY someone has done this on an XV6600! Has this corrected the problem of the bluetooth headset not being able to pair back up with the phone when the phone comes out of sleep mode? My headset seems to stay connected fine when the phone is on, but if my phone turns off and a call comes through, the phone acts stupid and doesnt fully reconnect to the headset.