Quote:
Originally posted by mswlogo
Eduh,
|
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.
Quote:
Great details and good news.
Sorry, but I'm just still a little confused on what made it work the second time.
|
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.
Quote:
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.
|
I have not yet tested it... but I will do so shortly.
Quote:
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). [/b]
|
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