I spent several time to determine why my treo can't reconnect.
I must soft reset the treo to reconnect to internet. Only the first connection work. Then, it's necessary a reset to reconnect.
I found this issue.
If I flag the auto-record call the treo wan't reconnect.
I tryied Vito AudioNotes and Resco Audio Recorder.
same problem.
If I set to auto-rec, I can't reconnect my treo.
I hope this features have some conflict with the connection.
(if I try to recconect by pressing the connect button in PhoneAlarm, Resco Audio Record start recording.....!!!!??? )
So it's diffucult for me keep this option active in my treo.
I don't know if this bug had a solution, I posted just FYI
Related
I have recently got a new O2 Graphite (WM6) via an upgrade, which came with an O2 "Blue" Bluetooth headset.
I paired the phone and the headset, and they worked fine for one call. After a single use I press the headset "talk" button, but the phone completely ignores it... I press the talk button and I do not get the "Say Command" prompt. I tried with another (non-O2) headset, and I get the same problem. The only way I can get them to work is... delete the pairing, reboot, create pairing, make a call, delete the pairing, reboot....
The pairing seems to time-out or something.
I have Bluetooth visibility on the phone turned on, and "show-visible" time-out set to never.
Is this a typical problem with these phones? Shall I send off for a replacement?
Maybe I should forget about the hands-free law, use my phone as normal, and if I get stopped, get O2 to attend court, take the points, and the fine!
Thanks, Demon
Hey there, I'm running Treo750 Unofficial WM6.1 OS5.2.19199 build 19199.1.0.0 - Standard OEM Version, which doesn't have Voice command included.
I was wondering where I might be able to find a cab file that installs Voice command 1.6 for WM6.1 on my 750. Would anybody be able to point me in the right direction?
just search the whole forum not the cab. The cab is for all Windows Mobile phones not just one particular for the Treo 750
found it, thanks, works like a charm.
are you able to voice dial with a bluetooth headset using VC and 6.1 ??
jcrompton said:
are you able to voice dial with a bluetooth headset using VC and 6.1 ??
Click to expand...
Click to collapse
If you have the 19209 build, that shouldn't be a problem.
kareem9nba said:
If you have the 19209 build, that shouldn't be a problem.
Click to expand...
Click to collapse
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
peeps said:
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
Click to expand...
Click to collapse
bump....anyone???
peeps said:
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
Click to expand...
Click to collapse
double bump...
Search for 'jabra bt registry' on this forum. I found a registry hack, that says this:
When VC 1.6 gets itself installed, it modifies the following registry key from:
FROM: (Original Registry without VC1.6)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Au dioGateway:BTAGExtModule = BTAGExt.dll
TO: (with VC1.6 installed)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Au dioGateway:BTAGExtModule
=\Program Files\Voice Command\vcbthag.dll
When I have set this registry back to BTAGExt.dll ( I have used CEregedit to make the replacement) my Jabra BT Headset was able to listen and deliver Voice Commands to the device and viceversa the device was able to deliver messages and notifications to the BT headset.
Simply make the registry change and soft-reset the phone, and you are back in business.
I have an Xda Orbit 2 (aka Polaris aka Touch Cruise) with MS voice Command 1.6 patched as per the instructions given at the link below in order to make incoming call announcements work.
http://forum.xda-developers.com/showpost.php?p=1548114&postcount=5
The above fix worked fine on my original Orbit (Mark 1) apart from the fact that incomimg hotmail emails are not announced. When I upgraded to the Orbit 2, I again installed the same patch and it worked again (minus hotmail announcements again) BUT with one additional issue: The blue Bluetooth LED never comes on. I can soft reset, power off and on again, turn Bluetooth off and on but nothing makes any difference. The lamp stays off. However Bluetooth works fine - I can transfer files to and from my PC and my Bluetooth headset works.
The practical issue is if for some reason for example a transfer fails or the headset has problems, I can't tell if Bluetooth has turned itself off or is still on without going into Comm Manager. If I'm driving and trying to use the headset I have to stop the car just to do this!
Today I did a hard reset. The Bluetooth light worked fine until I reinstalled Voice Command.
Does anyone know of a fix for this? A registry entry to change maybe?
Thanks in anticipation.
Hi,
I am using my HTC Touch Pro with an Opel Vectra built-in bluetooth carkit.
All functions, like browsing the address book and call registers, are working fine. However, at random times, my carkit reports no phone. When I then check my Touch Pro's bluetooth status, I see that it is has been disabled.
After manually re-enabling it, I can pair with my carkit for as long as it takes for bluetooth to turn itselves off again.
I've already tested with JETware, but that does not change anything. Also tried the universal broadcom bluetooth stack, but doesn't seem to work on the Touch Pro. HTC only comes with a standard answer that they don't support all carkits and headsets... Since the BT stack on the phone seems to crash, I don't think it's a carkit issue.
Anyone here with the same issue? And maybe a solution?
Thanks and regards!!
Start -> Settings -> Connections -> Bluetooth -> Timeout (tab). Turn off Visible mode set to "Never".
I think this must be your problem.
Hi Freco,
Thanks for your reply! This option is set. However it's not really the visibility that turns to invisible, but the whole bluetooth stack is being turned off completely. Need to fully re-enable it via Comm Manager.
Any other options? Does anyone know if there is a working broadcomm stack for the Touch Pro?
Regards!
Hi,
I have exactly the same problem with a Vauxhall kit, I have tried all sorts of things, but nothing seems to work
try:
start -> settings -> connections -> bluetooth
timeout tab
select 'never' from drop down box
Hi Brendo,
Unfortunately this doesn't solve the issue. Once paired, the connection even works without being visible. It's also not a fixed period of time before the disconnect takes place (can be within a minute, sometimes after half an hour). However, the whole bluetooth icons disappears from the top icon bar and comm manager shows it's turned off completely.
Hope somebody has any other ideas, because the only thing HTC can do is point to the carkit vendor :-(. Since all functionality is there when connected and the phone is turning off BT in some way, I really don't think this is caused by the carkit vendor. I should at least expect BT to stay enabled on the phone.
Thanks!
Yes, same here, BTW I have tried this in my Friends Saab, and the same problem.
same problem here with a Opel DVD90 buildin bluetooth carkit.
With other htc phones it always worked like a charm, but my mda vario IV continuously disconnects after a random time period and shuts down the complete stack.
Try this!
I have the same problem with my opel with original bluetooth-kit (2007). On the touch pro I changed the band and network from auto to GSM, as G3 reseption in this area is quit poor, especialy while driving. It helped for me, at least the last few days. I agree this has been an annoying problem.
I have tried to switch to "GSM only mode" in the past, but as far as I remember it does not completely solve the issue. However, I will give it another shot! Actually I can't figure out at what point it occurs... It can happen within a minute or after half an hour without using any funtion.
Does one of you know if there is a way to do some debugging on the Bluetooth stack?
And has anyone experience with other Windows Mobile 6.1 based phones in this combination (just curious if it's a WM issue or HTC only)?
Furthermore I did some tests with JetWare. You should be able to limit the number of synchronised items then (might be related to this issue). However, it looks like this configured limit is being totally ignored: when I limit my recent call list to 5 with JetWare, it still syncs about 25 items. Anyone tested with Jetware?
I have tried the GSM only mode, this didn't help either
I have now given up and got myself a Nokia E66, which works perfectly.
All contacts are pushed to car, no disconnects and AD2P works so my mp3 ringtones play through the car speakers! Sweet
Word of note, I had issues with N-Series phones, would connect ok, but contacts would not push.
I have the samen problem with my HTC Touch Pro and Saab.
bluetooth pairs just fine with my pioneer bluetooth enabled deck, but the problem iwth mine is once i receive a call sometimes no sound comes from the car, instead the earpiece is still on. but if i initiate the call first sound works just fine and earpiece on the phone is disabled, BUT once the call is ended bluetooth disconnects randomly and the phone takes a good 1-2min to reconnect. i absolutely hate the bluetooth on this phone!
ExTREmE99 said:
bluetooth pairs just fine with my pioneer bluetooth enabled deck, but the problem iwth mine is once i receive a call sometimes no sound comes from the car, instead the earpiece is still on. but if i initiate the call first sound works just fine and earpiece on the phone is disabled, BUT once the call is ended bluetooth disconnects randomly and the phone takes a good 1-2min to reconnect. i absolutely hate the bluetooth on this phone!
Click to expand...
Click to collapse
I am having the same problems you describe. Anyone got an suggestions???
I encountered the same problem; first with an opel udp carkit and next with the bluetooth interface software from homeseer.
It has something to do with phone signal loss.
With the opel carkit I noticed bluetooth automatically turns off when the phonesignal switched from 3g to gsm.
I also noticed that in my home, BT turns off whenever I have been in a room with no phone-signal reception.
try this thread, both registry change and attached cab file, reset. DOn't worry if the make visible to all option is unchecked.
http://forum.xda-developers.com/archive/index.php/t-314996.html
I'm looking for a way to detect wire headset (maybe there is a general headset event?) connecting to a WM device (Omnia in my case).
I want to make script, which launch media player in fullscreen mode when headset are connected do the phone.
I can't find the answer on xdadev nor in google. Mortscript too haven't functions for this event.
The only solution I was found is to continuously checking in Mortscript script HKLM/System/State/Hardware/Headset value if it is changing. (http://forum.xda-developers.com/showthread.php?t=284446)
But I'm afraid about device performance impact of this continuously executed registry check.
Any clues?
G-Profile?
Have you looked into G-Profile yet?
Can't post a link to it from work, but go to Google to find it.
I'll try this, thanks