New User requiring help..

[madcowz]

Hi,

I have a couple of questions:

1) I have a default corporate install 02 Exec and a Motorola BT H3 headset.

When the devices are all paired up, I can receive incoming calls no problem. But when I try and initiate a call from the headset by tapping it, I sometimes get a responding beep from the voice dialling software, other times not. When I don't get an audio response, the device just doesn't seem to even notice and nothing changs on the screen.

I have tried all the usual, re-pairing, reboots etc, but no luck.

I also can't pin down exactly when it does it. Sometimes I can start a call when the device is in 'standby' ie if I haven't used it for a while, other times not.

My next step is to find someones phone and test it with that and see if it is the headset or the exec.

2) My backlight does not come on when I tap the screen or a key despite having ticked the correct setting to enable this. Each time I have to press the power button.

Has anyone else had similar problems?

thanks,


/Mad

[madcowz]

Ok,


have now done a complete hard reset and a new corporate install and the BT headset is stll not working 100% of the time.

I have tested it on another phone and it works a treat there, so it is not the headset.

thanks,


/Mad

[madcowz]

Scrap the below info. This only works if the Exec has been off for a short time. Anything longer than a couple of minutes and it doesn't switch on with a tap.


I have O2 swapping it out over the next couple of days. Let's see if these issues are widespread. but judging by the responses to my pst, I take it I am the only one having trouble?

/Mad



Ok,

With problem 2) I have found that if I do a hard reset and install as O2 rather than corporate, when I open up the device in clamshell mode the backlight comes on and if it is already open, a tap on the screen or key does switch on the backlight.

So, this particular 'issue' appears to be related to the type of install. That is it works in O2 but not in corporate mode.

Still no joy with the intermittant BT headset voice dialling.

Either way, I have O2 swapping it out over the next couple of days. Let's see if these issues are widespread

/Mad

[madcowz]

Last night I updated to the most recent O2 ROM (as per their website) and now...

it appears that the first time I press the BT headset button, nothing happens, but then on the second press it brings up the voice dial software.

I have had a damn good trawl through all the other posts about voice dialling and it seems that the first press connects the headset to the exec and the next button starts the app.

Is this correct? Anyone else had similar problems?

thanks for your time.

/Mad

[SiliconS]

I had similar behaviour when I used my SonyEricsson HBH65 headset with my Exec. When I bought a Jabra BT800 suddenly my Bluetooth experience was transformed, and the combination works perfectly.

I think the latest models of headset work much better with the Exec than those a year or two old.

Maybe this helps. Hope so.

[madcowz]

Thanks for your reply.

I took my BT headset back to the shop today and got them to try a jabra (don't know which version) it still wasn't bringing up the voice dial software every press.

Spoke to O2 support today and they admitted that BT is flakey on the Exec and that it is a known fault with HTC.

Oh well, at least it isn't just me!

/Mad