To get Build 3500-124-B running in the first place you *might* have to hard reset. Most people have had too. Symptom is bluettooth won't turn on without memory error.
But if you want to try without hard reseting first go for it. IT won't hurt to try.
You might try the registry thing too before hard reset.
Originally posted by mswlogo Will not require any hard resets to experiment.
aarong, I would have agreed with you, except for the above statement. Thats why I'm askin before tryin
Quote:
Originally posted by mswlogo To get Build 3500-124-B running in the first place you *might* have to hard reset. Most people have had too. Symptom is bluettooth won't turn on without memory error.
But if you want to try without hard reseting first go for it. IT won't hurt to try.
You might try the registry thing too before hard reset.
Restoring a backup *may* also break it.
Ok giving it a go now, as per the steps I outlined earlier...
Last edited by JasonWilliam : 12-28-2004 at 05:09 PM.
Well, everything installed just fine, without the need for a hard reset. Here is EXACTLY what I did:
1) Turn off the bluetooth radio (I was running 3100)
2) Copy over the CAB and run it
3) Soft reset
4) change the registry as per the above instructions to "btceif.dll"
5) Soft reset
6) Turn on the bluetooth radio
7) Make a call and listen thru the headset. Perfectly clear and connected right away.
We'll see about the coming out of sleep issue shortly...
Last edited by JasonWilliam : 12-28-2004 at 05:12 PM.
I got the noise when i tried to pick up a call from the headset with the phone coming out of sleep mode. If you dont get the noise then i'll give it one more try.
Its been about 15 minutes and I've noticed something different already. The headset appears to have gone into sleep mode, however the XV seems to be keeping the BT "heartbeat" alive as indicated by the period flash of the blue light (will this kill battery life?). I don't think this was the case with 3100...
Test call worked flawlessly. The call came in, the headset instantly woke up and there was no static on either end of the conversation.
I'm cautiously optimistic. I'm going to let both devices sit now for about a half hour and try again. I'll post the results shortly there after.
Originally posted by mswlogo Ok, this is how I summarize things:
Build 3100 on PPC-6601 with most headsets works pretty good.
Build 3500-124-B on PPC-6601 with most headsets works pretty good but not as stable as build 3100.
Build 3100 on XV6600 not as stable as 2400 but does not fix Sleep issue with headsets.
Build 3500-124-B on XV6600 looks like it might fix the sleep issue but often gets static when reconnected from sleep.
Anyone can try this that is getting static sometimes. Will not require any hard resets to experiment. But be sure to active sync and backup before experimenting just in case.
You need to have a registry editor tool like RESCO File Explorer (which I think is really nice).
Either works on PPC-6601 (but I have not tested long).
I'm just throwing out suggestions. Don't shoot me if it does not work. If it does work, I can CAB it up.
So let us know if you decide to try it.
"Dll"="btceif.dll" does not work at all with 3500 on the PPC 6601 with a Jabra 250 headset. There is no audio at all. Is it possible to pull the wavedev.dll from the verizon phone to try it with the PPC-6601? My audio quallity isn't where it should be with the Jabra 250 on this phone. Maybe verizon's version of the DLL will fix it.
Originally posted by JasonWilliam Its been about 15 minutes and I've noticed something different already. The headset appears to have gone into sleep mode, however the XV seems to be keeping the BT "heartbeat" alive as indicated by the period flash of the blue light (will this kill battery life?). I don't think this was the case with 3100...
Test call worked flawlessly. The call came in, the headset instantly woke up and there was no static on either end of the conversation.
I'm cautiously optimistic. I'm going to let both devices sit now for about a half hour and try again. I'll post the results shortly there after.
So far... great work mswlogo and company!!!
this is the kind of result I've been waiting for. I wonder if this is headset specific though?
Ok 1.5 hours later, same perfect result. The thing is actually working exactly as one might hope. The blue flash on the phone did persist the entire time, so my only concern now is battery life. But at this point, I ain't complaining!
A couple other notes:
- I didn't notice one way or the other before 3500, but the long press to redial from the HS820 is not working. I'm pretty sure this did not work before.
-Transferring to and from headset during a call: If you've answered with the XV first, a short press of the multi button on the HS will transfer the audio/mic to the headset. However, a short press of the multi key to try and transfer back actually ends the call. Again, I'm pretty sure this was also the case for 3100.
-I haven't tried any of the other features of the HS.
Well, as far as I'm concerned this build with the reg tweak is a success on the XV. Battery drain remains to be determined, and time will tell if this truly is a fix or not. I'll keep ya posted.
Now, find me an audio gateway profile to play mono audio thru the 820, as well as a way to shorten the length of time required to press and hold the talk button for the speakphone, and I'm one very very happy guy.
Thanks again!
Last edited by JasonWilliam : 12-28-2004 at 07:28 PM.
Jason, can you go into the bluetooth manager and tell me if the bluetooth connection is alternating from one red bar to 5 green bars or if its just staying at 5 green bars.
Ok:
-with the 820 in sleep mode, I have an alternating red/green pattern
-with the 820 awake, I still have the alternating red/green pattern
-during a call, I have a solid 5 green bars (no red alternating). As I move further away, less green bars show (signal strength seems to be working).
-as soon as the call ends, the red/green pattern returns.
Without thinking about it too much, this is exactly what I might expect. It seems the phone is in fact putting the headset on standby, and indicating as such with the red/green alternating pattern.
Hope that helps. Don't hesitate to ask any other questions!
Cautiously optmistic is the right attitude.
I'll believe you made progress if it runs for 2 days with no glitches.
Sometimes it has to sleep a long long time before issues arise.
The fact that you never got a memory error is a good sign too.
Keep in mind headsets and other software factor in too.
I don't think the blinking blue light will drain battery (much). I think it is polling it.
Installed the 3500-B patch. Tried taking a call with the phone on through the headset initially and it worked perfectly. Next i tried turning the phone off and then taking a call. The phone came out of sleep mode, but could not reconnect to the headset in time and i was unable to take the call through the headset. When the phone came out of sleep mode it showed an icon of a headset with a question mark for about 5 seconds until it recognized the headset. Could this be a problem with my headset or the phone?
Edit: Tried changing the registry value. Now i cant get any audio whatsoever.
Last edited by xxplosive : 12-28-2004 at 09:35 PM.
xxplosive, I wonder if installing 3500 over the top of 3100 made a difference for me? I still haven't had any issue, and believe me I've been trying to break it.
Have you tried deleting the old pairing and trying a new pairing? Granted, I did not have to do this, but perhpas yours has become corrupted?
Basically what i did was i installed the 3100 patch first, THEN i installed the 3500 patch. I am able to answer calls perfectly with the phone on and off. Thanks!
Login
Panel
