Related
I have experienced a strange problem with my JasJar bluetooth radio. The bluetooth radio seems to turn itself off from time to time. I think it is somehow related to WM2005, because I had the same issue with a Himalaya running WM2005 (thanks to Buzz). What is weird is that the blue light continues to blink. If you go to the wireless manager applet, it sometimes shows the bluetooth as on and sometimes as off, but if you go to the bluetooth setting, it shows the radio as off. Turning it on, with the applet, or in the bluetooth settings, is only sometimes successful in actually getting it working again. Ressetting the device works every time. No need to re-pair.
Any suggestions?
TIA
Panabax
INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!
craigiecraigie4 said:
INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!
Click to expand...
Click to collapse
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.
Edit: i've made a mistake in the registry... found by ekapco. THANX.
uploaded new cab below...
buzz
Buzz, you're a legend!
Trying it right now, will report back tomorrow.
Can u not help us on all our other problems (http://forum.xda-developers.com/viewtopic.php?t=28343)? Your posts on Buzzdev.net indicate that you're far more technically savvy than most ppl here.
Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.
ekapco said:
Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.
Click to expand...
Click to collapse
BlueAngel? I think, this is a Universal fix.
BlueAngel? I think, this is a Universal fix
Click to expand...
Click to collapse
So ????
Registry is almost the same on this issue.
ekapco said:
In your headset fix shouldn't reg setting be hds1: instead of hds1 ?
Click to expand...
Click to collapse
of course... i'm so stupid... sorry...
should be hds1:
THANX ekapco...
buzz
ThExSenatoR said:
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.
Click to expand...
Click to collapse
WOW!
That was a helpful post. Thanks.
Buzz; can you explain what your fix actually does? I don't have a cab extractor here to look at the contents.
fix sets hds1: = dword:0 for 'unattended' system power state.
hds1: is headset device identifier.
bkl1: is backlight
wav1: is wave device
dsk1: is block/disk device
etc...
let's have some fun with those power settings...
open your regeditor and change
[HKLM/system/currentcontrolset/control/power/state/on]
"bkl1:"=dword:4
and
[HKLM/system/currentcontrolset/control/power/state/backlightoff]
"bkl1:"=dword:0
after changing the regs, press power button to off and on again. that will flush and apply new settings.
ok. the above settings will REVERT backlight's behaviour. I mean, when device is on, backlight is off. after inactivity timeout, light goes on.
well... funny experiment...
that proves, that devices could be powermanaged from here.
if you've had enough fun, revert those settings to normal. ;o)))
now set in:
[HKLM/system/currentcontrolset/control/power/state/unattended]
"bkl1:"=dword:0
that SHOULD turn the backlight on, when you leave the device untouched for a longer time (when the display goes off) or if you press the power button.
so leave it untouched and watch the display to see what's gonna happen on the 'unattended' state.
after approx. 5 minutes (never measure that), just when the display is about to off itself, BACKLIGHT FLASHES for a second and goes OFF.
why? we just said, bkl1:=0 (ON)?
so our settings are overriden. maybe that 'flags' settings?
lets see later, but exactly the same happens with BT connection even if we say ON, it goes off...
I have to sleep now in 'unattented' state, but meanwhile you can look at msdn, coz I saw those flags description there.
good night
buz
Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?
EyeOfTheStorm said:
Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?
Click to expand...
Click to collapse
Please follow my last post here or you have to tell me your wifi device handle.
I try to find the device ID
In "HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Power/Interfaces" i fount this 4 IDs
{8DD679CE-8AB4-43c8-A14A-EA4963FAA715} Power-manageable block devices
{98C5250D-C29A-4985-AE5F-AFE5367E5006} Power-manageable NDIS miniports
{A32942B7-920C-486b-B0E6-92A702A99B35} Generic power-manageable devices
{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1} Power-manageable display
Does this help? Or am I wrong?
O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?
craigiecraigie4 said:
O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?
Click to expand...
Click to collapse
...stupid question, but:
does it actually have MS BT stack??
buzz
there is another problem, it seems that my mobile doesn't accept any connection from any nokia mobile, it says to them (unable to connect), i don't know why???????????
I too am experiencing Bluetooth problems with my O2 Exec and a Motoroa HS810 headset. I use voice tags quite a bit and for the most part this works well however sometimes the EXEC fails to respond to the button press on the headset.
I first noticed this when I did the reg hack to make MS Voice Command the default Voice dialler and presumed that maybe there was a problem with MS VC so went back to VoiceDialler. However the same thing happens with VoiceDialler. To get it working again i have to turn off bluetooth in the Wireless Settings panel and then turn it on again. After this it starts to work again (but not ideal if your driving).
I think this might be the same problem mentioned above, i.e. bluetooth says it is on, the blue led flashes on the phone, but in reality it has switched itself off. I did some more testing while the headset was not initiating voice dialling and called the Exec. After a short time, the headset icon appeared on the "Incoming Call" message area and my headset burst into life. This would make sense I suppose because doesn't Headset mode start bluetooth up when a call is received (presuming it is off)?
Looked at Buzz's reg hack for Bluetooth but didn't really understand it
Here's what didn't fixed it for me.
After more reading today I realize I was way wrong.
Re: Here's what fixed it for me.
I can confirm that these registry settings work perfectly on the blueangel Great job.
Help again please.
How do I set the ring time, or number of rings before answering on my xda mini s. I have looked in phone settings but can't see anything that relates to how long it should ring for before I answer or it diverts to answering machine.
If its in my pocket, I have trouble getting it out before its diverted to answer machine. Is there a setting that I'm missing somewhere as I would like to double the short ringtime to a more reasonable length.
I also read somewhere about a newer rom than the o2 release rom. Anyone know where this is and what it does.
Thanks in advance.
This can be found under Setting-> Phone-> Services-> Call Forwarding
The maximum you can set it to is 30 seconds, but I'd like it to be longer as I seem to be missing calls!
I've noticed that the phone icon in the task bar comes on for about 5 seconds before it rings, has anyone else noticed this?
O2 reply
I contacted o2 about this as it eluded me for so long. They said:
Go to phone screen, type **61*901*11*, followed by the time in seconds and finish with # and click the green talk key.
I could get to 30 seconds and no more despite o2 saying I could set up to 60 seconds. What a lot of messing about. I agree (as does a friend) that it would be nice to get a longer delay as the preset time is too short and the maximum of 30 could be better. I suppose 30 seconds is something to do with the network.
Ah well. Nothing is perfect even when its close. Maybe in time.
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
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
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
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
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.
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
I've recently been having a play with the Voice Tag function on my Wizard. I can call any of my contacts by voice, and I can perform a plethora of functions on my phone by voice (helped by the added hardware button functions that Pocket+ provides). Now i'm wondering if I can do even MORE by voice, i.e. a spoken password, dialing by saying each number, that kind of thing?
Yeah,
Dump the cheezy Cyberon Voice Dial and get Microsoft Voice Command or Cyberon Voice Commander.
Both allow you to access PDA functions such as launch programs, access calander etc.
Additionally they allow "Dial 444 555-1234"
In my opinion MS Voice Command is better.
I've played with Cyberon Voice Commander because it will read e-mail and text messages but I've found it to be useless. Also Cyberon has too much of a delay from activation to ready for voice input for my tastes.
Oh yeah, neither of these requires "Voice Tags", they work by recgonizing your spoken voice!
Cyberon Voice Commander costs about $20,
MS Voice Command is about $40.
Both can be purchased at Handango.com
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Danny-B- said:
Now ... call me silly, but wouldnt it be a slight security risk shouting your password at your device to unlock it ?
Click to expand...
Click to collapse
Maybe that's why none of these products supports it!!
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
jimmyhauser said:
I have given up on MS Voice Command. It works well, as long as you dont use it with Bluetooth.
It dials once or twice, but then stops responding to the Bluetooth command button. The only way I can get it to work is to press the bluetooth button twice to redial the last call, quickly hit the button again to cancel the call, and then, sometimes, the long press will initiate voice command again.
Jumping through hoops like this make the program pretty worthless to me. To dial numbers in the car is all I need if for, and that is where it doesnt work. I will stick with the voice tags.
Click to expand...
Click to collapse
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Same for me. Sometimes the recgonition isn't the same over bluetooth, but I never have to try more than twice. I use my VC for everything.
jimmyhauser said:
JNGold said:
That's not VC's issue, it's your BT stack issue. On my K-JAM I press once to activate the BT audiogateway, press again to issue the VC. Works every time.
Click to expand...
Click to collapse
Press once activates the phone over bluetooth (sometimes anyway, sometimes nothing happens at all), pressing again does nothing. Believe me, I have tried EVERYTHING. I was messing with it for two hours doing every combination I could think of. The only thing that works is a double press for redial, end the call right away, then I can activate VC again(sometimes). And the cycle repeats.
On the other hand, built-in voicetag dial works everytime, and I dont have to activate the bluetooth first. One long press prompts for voice dial EVERY TIME.
So I beg to differ, it is an issue with voice command.
Click to expand...
Click to collapse
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
VC Usage Vs. VS VC Memory Usage
I've had VC on and off of my 8125 since I bought it in April.
The main problem I have with MSVC is whether its use (or lack there of) validates the amount of memory it uses.
For someone that makes calls primarily off of his recent call list, I find that the usability benefit does not outweigh the memory usage.
Wish there was a way to disable / enable the functionality, as to release that memory for other applications.
JNGold said:
So how do you account for it working consistantly fine for some, and others not?
BTW, my VC is loaded on the device, not on a storage card.
Click to expand...
Click to collapse
Believe me, I am not an expert on this, I am just trying to figure things logically. But I would bet it has to do with the fact that you are probably using a different bluetooth handsfree device than I am. Maybe that was what you were referring to when you said it was a bluetooth issue. Or maybe it is the fact that you have a different model of phone.
What I am saying is that it cant be the bluetooth software on my phone, because the cyberon voice dial works fine over bluetooth, where the MS voice command does not.
And I have voice command on the phone also. All my programs are. I only keep music and videos on the storage card.
And voice command works great when using on the phone itself. I am amazed at how well and how quickly the recognition works. It just doesnt respond well to my Nokia car kit. And maybe that is the problem.
My wife's car has the same bluetooth kit as my car, I am going to try it in her car one of these days to see if I have the same problems there. She has a Nokia 6682, and her bluetooth voice dialling works great.
And also, does VC really use that much memory? If so, I think may take it off the phone. (I use it a little when not in the car) But if it is considerable, then I agree that it is not worth it.
the problem is that without any BT headset i can't get the microsoft voice command to work.
i installed it, dedicate the button. the problem is that when i press it the mic sign appers, i hear the bip and if i say "HELP " it does absolutly nothing.
NOTHING
it just stands there, then another bip comes and the mic sign disappears .
what should i do?
did you turn your mic auto-gain off like the instructions said?
problem solved.
don't know how ...soft reset and bam ! it worked.
the problem is that it hardly recognizes 0 ( zero )
well...i think the old voice dial would do the trick for me...
Keys to success:
1. Load in main memory. (Yes, it's a hog, but to me it's worth it.)
2. Be patient. Sometimes it takes a moment or two to activate.
3. Make sure your volume is not muted. (I admit it, I often walk out of a meeting and get frustrated with why it isn't working... oh, volume is off.)
4. Experiment. Watch the phone while you are playing.
Here are my results with Motorla hs850 .
1. Usually I push once to open the gateway and a second time to activate VC. (Note, I only wear my headset when I need it.)
2. Sometimes the gateway is open for whatever reason and I'll get an immediate bong. So after the first press, I give it a second to see if it will come up.
3. Otherwise, I may get into three presses. One which I think is opening the gateway but is actually opening VC before the bong sounds. A second which I think is activating VC but apparently is closing it. The third press usually then does the trick, but sometimes I'll even have to go to number 4.
So my strategy is:
1. Push button.
2. Wait a slow count for response.
3. Go back to #1 until success is achieved.
If I am using Tomtom and receive an incoming call, TT is interrupted by the phone screen - fine so far.
However, if I accept the call and want TT to resume so that I can drive and talk (I know I know) - instead I am just stuck on the phone screen and have to fiddle around to get TT back up.
Worse still - if I reject the call, or when it is ended, instead of TT resuming I am refreshed to the home screen.
Is any of this behavior configurable / tweakable? It seems absurd to me.
Results are the same with or worth out a BT headset BTW.
I'm, wondering whether something like S2U2 might be interfering with default behavior?
Any advice / experience much appreciated. Thanks - M.
Disabling the "slide to answer" option in S2U2 fixes this on call termination (reverts to TT) but still stuck with the phone screen when I answer a call.
If running TT in landscape (fantastic view) it annoyingly refreshes back in portrait after call though.
Guess I need to work through the jungle of S2U2 options to see if I can make this a bit more friendly as slide to answer is main reason for running S2U2 in the first place.
Mark One said:
If I am using Tomtom and receive an incoming call, TT is interrupted by the phone screen - fine so far.
However, if I accept the call and want TT to resume so that I can drive and talk (I know I know) - instead I am just stuck on the phone screen and have to fiddle around to get TT back up.
Worse still - if I reject the call, or when it is ended, instead of TT resuming I am refreshed to the home screen.
Is any of this behavior configurable / tweakable? It seems absurd to me.
Results are the same with or worth out a BT headset BTW.
I'm, wondering whether something like S2U2 might be interfering with default behavior?
Any advice / experience much appreciated. Thanks - M.
Click to expand...
Click to collapse
I understand your problem. I run TF3d and have mapped a soft key (via Registry) on the home screen to TT. When it goes to Home page it is just one press to get back to TT. Not sure if that helps or not but may or may not inspire?
Thanks for the confirmation - this seems to be a TF3D "feature" then
Sounds like a fine kludge & I'll give it a go, but "one press" on the motorway is about quarter of a mile of with my eyes off the road....
Guess you already know what you should be doing, but here's my setup.
I have a Parrot Mini Bt hands free unit, others may work similar?
If I get a call, TomTom is interrupted and the phone screen displays.
Hit the red button on the Parrot to reject the call, TomTom resumes.
Hit the green button on the Parrot to accept the call and the TomTom navigation screen is visible with muted sound throughout the call.
Hit the red button on the Parrot to end the call and TomTom voice prompts resume.
Make calls with TomTom displayed as described by one touch on the Parrot green button and speak the name. Let built in voice recognition do the rest.
Costs about half the fixed penalty fine, but without the points.
I find this to be quite the annoying problem actually. I've got the same issues on my Blackstone. TT7 is running and I'm driving (I like to let others do the hard work ;-)) and when a call comes in and when I answer it, it stays on the phone screen. I have to press the Tomtom button to get it activated again.
I never had this prblem on my Tytn.
i got stock rom and and when i recieve a phone call when i use TT, it automatically reverts to TomTom. Haven't touched any settings.
i was coming here to ask similar question, i used tomtom yesterday, and 2 x incoming calls were loat as screen wasnt displayed quick enough, then when finally managed to answer i didnt have the navigation screen any more.
the above reply about parrot head set sounds good, but is there a way without bluetooth, so can just have loud speaker for phone calls, and still display tomtom?
Danun, what parot bt you got? as may be easiest option, have you a cooked rom installed also? or stock? cheers
I hope this info is of some use to you. I have TomTom installed but not S2U2. When a call comes through it switches to the call answer screen and if I accept or reject the call it will switch back to TomTom. However, when I end the call it brings up the end call screen and then switches back to TomTom but in portrait mode (I run TomTom in landscape using Gyrator 2). About 30 seconds after the end of the call TomTom will then go back to landscape mode which is ok if I'm on a motorway and don't have to turn off onto another road. If I do have to then I lift the HD out of the car holder, hold it portrait and then landscape and put it back in and it sorts itself out.
I think that S2U2 is causing the issue with it not reverting back to TomTom but I'm guessing it getting stuck in portrait mode for a period of time could be to do with Gyrator 2.
I also use a Parrot hands free kit. If I didn't I wouldn't be able to answer every call as it sometimes takes too long to switch to the incoming call screen.
t3rm3y said:
Danun, what parot bt you got? as may be easiest option, have you a cooked rom installed also? or stock? cheers
Click to expand...
Click to collapse
I have the older MiniKit model which I bought to use with my Artemis about 18 months ago. I just leave it clipped to the sun visor. There is now a more compact MiniKit Slim model which I would probably go for now.
I have the 1.14.405.3 (22273) WWE stock ROM on my non branded HD.