FWIW, on my old i700 I would ALWAYS shutoff the phone portion (you call it flight mode) when installing and uninstalling software. It was a pretty common issue.
Originally posted by mswlogo 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.
I tried the 3100 patch on my XV6600, it pretty much gave me the same problems as the factory build.
Well my big issue right now is the phone and bluetooth headset loosing a connection when the phone turns off. The 3100 patch didnt seem to fix that. The 3500 did i think but it kept on giving me this weird noise when i tried to answer a call from my bluetooth headset with the phone coming out of sleep mode.
Originally posted by xxplosive Well my big issue right now is the phone and bluetooth headset loosing a connection when the phone turns off. The 3100 patch didnt seem to fix that. The 3500 did i think but it kept on giving me this weird noise when i tried to answer a call from my bluetooth headset with the phone coming out of sleep mode.
ahh, conflicting reports
I've seen more than a few people claim the latest 3500/3100 hybrid patch fixes most all of their bluetooth problems. Once bluetooth gets ironed out I'll bite the bullet and purchase this phone.
Originally posted by xxplosive aarong, most of the successful reports have been with the sprint ppc-6601. I'm trying to do this on the Verizon XV6600...big difference.
unless I misread the posts on howardforum (good chance I did) people are reporting success with the XV as well...
Guys, I'm having the exact same issue xxplosive is reporting with my XV running 3100.
I don't have any issue keeping the HS820 paired to the XV. However, how / when it connects is a bit of a mystery. There is definitely a sleep mode the phone goes into (after 10 mins?). When this happens, the BT turns off, and the headset also appears to turn off (indicated by the lack of blue flasher, and a lack of beep when the volume buttons are pressed to either extreme). I've seen two different things happen at this point when a call comes in: 1) When the phone rings, the BT re-enables, however a connection to the headset doesn't happen in time to prevent the call from going to voice mail. 2) When the phone rings, the BT re-enables and does connect after about 25 seconds of ringer. If I then "answer" the call via the headset, the calling party is greeted by static. When (2) happens, the only way I've found to clear the problem is manually disable and then re-enable the BT on the phone. Just powering down the HS820 does not fix the problem.
Hope that helps. And I am very willing to help test anything you want to throw at me. I'm avoiding 3500 since it seems clear there are known, fairly repeatable issues with it as well.
Originally posted by JasonWilliam Guys, I'm having the exact same issue xxplosive is reporting with my XV running 3100.
I don't have any issue keeping the HS820 paired to the XV. However, how / when it connects is a bit of a mystery. There is definitely a sleep mode the phone goes into (after 10 mins?). When this happens, the BT turns off, and the headset also appears to turn off (indicated by the lack of blue flasher, and a lack of beep when the volume buttons are pressed to either extreme). I've seen two different things happen at this point when a call comes in: 1) When the phone rings, the BT re-enables, however a connection to the headset doesn't happen in time to prevent the call from going to voice mail. 2) When the phone rings, the BT re-enables and does connect after about 25 seconds of ringer. If I then "answer" the call via the headset, the calling party is greeted by static. When (2) happens, the only way I've found to clear the problem is manually disable and then re-enable the BT on the phone. Just powering down the HS820 does not fix the problem.
Hope that helps. And I am very willing to help test anything you want to throw at me. I'm avoiding 3500 since it seems clear there are known, fairly repeatable issues with it as well.
This is PRECISELY the problem im having. aarong, can you provide a link to the thread on howardforums where XV users are able to get these patches to fix thier problems?
From the HS20 User's Manual, p. 17 Note: When the wireless headset is paired to the phone and there is no activity for 5_minutes, the blue flashing LED turns off. Any button press on the headset, resets the timer, and the flashing resumes. If you press the up and down volume buttons at the same time during a call, the pulsing LED turns off for the duration of that call.
Are you sure this isn't some of the behavior you're seeing?
HS820 here. I'm 99% positive this is NOT an issue with the headset, but rather with the driver on the XV. I've used this headset with other phones as well as my PC with zero issue.
Originally posted by xxplosive This is PRECISELY the problem im having. aarong, can you provide a link to the thread on howardforums where XV users are able to get these patches to fix thier problems?
I went back and read the posts I referred too earlier: they all have to do with the imate PDA2K GSM version
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).
-I'm going to download Build 3500 (rev 124 released 12/23/04 with AudioGW.dll from Build 3100) as posted in Post 1 of this thread
-I'll copy it over to my XV and run the cab
-Soft reset?
-I'll change the parameter as suggested above.
-Soft reset
-Test test test
Do I have this right? Say yes and I'll give it a go now.
Originally posted by JasonWilliam OK, before I jump off the cliff...
-I'm going to download Build 3500 (rev 124 released 12/23/04 with AudioGW.dll from Build 3100) as posted in Post 1 of this thread
-I'll copy it over to my XV and run the cab
-Soft reset?
-I'll change the parameter as suggested above.
-Soft reset
-Test test test
Do I have this right? Say yes and I'll give it a go now.
You want to start with a hard reset and NOT restore from a backup afterwards, from what I've read. I'm 99% sure they (mswlogo, etc) are suggesting a HARD reset before patching.
Login
Panel
