Related
There seems to be a very annoying bug on my new XDAII that is running the 1.6O O2 ROM.
If I am on the phone and i receive a call that alerts me that there is a call is waiting, and I decline to answer it, the sound is cut off and I can't hear the caller anymore. Cancelling the current call and re-dialling is the only way of getting 'sound back'.
Furthtermore, another irritating bug is that if the phone rings and I answer after only 1-2 rings, I can't hear anything for a few seconds and have to wait those couple of seconds before i can speak to the other person. This doesn't seem to happen if the call is answered after 3-4 rings.
Any help would be appreciated.
Me too - only answer I found was to turn off call waiting.
Poor solution.
Same for me, i too had to turn off call waiting, however i found that if you are using a bluetooth headset when the second call comes in and you decline to answer it, it just transfers the current call the the phone and you can continue it there
Same problem here.
I find that if you put the call on hold and then resume - the voice will come back.
VERY irritating.
Same for me too, I have T-Mobile 1.60 and using BTHTools 1.1.0.0...
Do you use BTHTools?
yes l am using BT tools.
regards,
hasnain
I performed a hard reset...
Did NOT install BT Tools - and had the same problem.
Mine did this long before using BT tools also.
I also have the same problem....
Is it an incompatibility between the phone and Bt Tools?
Is there any solution other than turning off call waiting?
Does anyone face the 2nd problem that I mentioned:
Sometimes when I pick up the phone after it rings, it takes a couple of seconds before i can hear the caller. This happens more often when picking the phone up within 1 or 2 rings.
This problem was aroung in the I-mate ROM 1.66.
They fixed both with the 1.72 ROM.
ketinson said:
This problem was aroung in the I-mate ROM 1.66.
They fixed both with the 1.72 ROM.
Click to expand...
Click to collapse
i DON'T THINK THIS IS FIXED IN 1.72. i STILL HAVE THESE SAME PROBLEMS TOO, RUNNING t-MOBILE 1.72.
While running 1.60 I replaced the Radio Stack only with the O2 original release version - sorry don't remember version number - and it worked without these two very annoying bugs in the phone. i think it is a problem with the readio stack version only.
After losing the voice with an incoming call I can get the voice back without redialing by placing the call on hold and then resuming.
I have the same problems with or without bluetooth tools and with or without a BT headset.
Now, I have T-Mobile's 1.72 installed and am afraid to reload the working radio stack becasue of the "downgrade disaster" with 1.72. I am anxiously waiting for either a stable 1.72 or XDA Developers to help us out of this mess with this ****ty ROM.
This forum is fantastic. Thanks to everyone.
Steve
I had the problem in the 1.66 ROM, and no longer have it with 1.72!
I've just installed the new O2 1.72 ROM and am still having the same problem.
I am also suffering from a problem I was having on the old ROM. Many times when I receive a call and press the green answer button, it takes between 2-5 seconds for me to hear the person calling. The person calling also hears a similar period of slience before he/she can hear me.
The same thing also happens sometimes when I call out, where only once 2-3 rings into the call or if the other party has already picked up thephone can I hear or say something.
I'm not sure if caller ID or Photo ID has anything to do with it as I have around 1380 contacts on my xda.
This problem is extremely annoying and was wondering if there is anyone out there who has faced the problem and may have an answer for it.
Us too
We have two xda2 with 1.72, and same thing, there is a 5 second delay upon recieving any call, and sometimes there is a hangup duriong call waiting???
I never had that problem until I installed Bluetooth Tools...now it always happens. Though as someone's suggested, holding and resuming seems to do the trick.
Hi everyone!
New to this forum but got my Qtek S100 a couple of weeks ago and found an irritating bug in it..
When I use my SonyEricsson HBH-300 Bluetooth headset everything is fine until I've talked for ~7 minutes.. after that the other party doesn't hear me while I still can hear the other party.. Sometimes my mic never comes back during that call but sometimes it's back after about half a minute or so.. the funny thing is that if it comes back it goes away againg in about 14 minutes.. and perhaps 21, 28 and so on.. haven't really made that long calls with that headset because of the bug..
The headset works fine with other phones, at least SE Z1010, SE P900, Nokia 6630 etc..
And the S100 works fine with my Bluetooth GPS..
Has anyone experienced anything similar?
Have you got other bluetooth headsets, do they work for long ( +7 minutes) calls?
Cheers
/Rikard, Sweden
di7riks said:
Hi everyone!
New to this forum but got my Qtek S100 a couple of weeks ago and found an irritating bug in it..
When I use my SonyEricsson HBH-300 Bluetooth headset everything is fine until I've talked for ~7 minutes.. after that the other party doesn't hear me while I still can hear the other party.. Sometimes my mic never comes back during that call but sometimes it's back after about half a minute or so.. the funny thing is that if it comes back it goes away againg in about 14 minutes.. and perhaps 21, 28 and so on.. haven't really made that long calls with that headset because of the bug..
The headset works fine with other phones, at least SE Z1010, SE P900, Nokia 6630 etc..
And the S100 works fine with my Bluetooth GPS..
Has anyone experienced anything similar?
Have you got other bluetooth headsets, do they work for long ( +7 minutes) calls?
Cheers
/Rikard, Sweden
Click to expand...
Click to collapse
That also happened to me in the beggining after erasing the handsfree from my devices and paired it once more its running fine since then!
HI!
di7 riks.....I am using a Motorola HS810 Bluetooth handsfree with my O2 XDA II Mini and the same 7 minute problem is happening to me also. Initially it was 12 minutes but now it is down to 7. I can hear the other party but they can't and then I have to disconnect and dial again.
think I will do as katsj did...try pairing teh device again.
U
This is a known issue. Apparently, what is happening is that the device is going to sleep, and bringing down part of the bluetooth with it. The quick'n'dirty solution is to set your device to never power off, and just turn it off manually. Hopefully this will be fixed in the next round of ROM updates :?
I have an "almost" similar problem: I answer the call with the HBH-300 and talk for about 10 seconds after which I can hear nothing (the other part hears nothing also). If I close the handsfree from the MDA Compact then I can continue talking from the MDA (the call is not ended).
If I close the call and make a new call I get the same problem. But if I switch off the HBH-300 headset and switch it on again then the problem stops and in the following calls I can talk using the HBH-300.
This problem appeared only twice in the 15 days that I am using the MDA.
Obviously the phone did not power off in 10 secs (it was on when I had the problems) so the "sleep issue" mentioned previously could not have created the problem. Only the backlight goes off in 10 seconds. Do you think that the backlight might cause problems to the bluetooth?! :shock:
atsois said:
I have an "almost" similar problem: I answer the call with the HBH-300 and talk for about 10 seconds after which I can hear nothing (the other part hears nothing also). If I close the handsfree from the MDA Compact then I can continue talking from the MDA (the call is not ended).
If I close the call and make a new call I get the same problem. But if I switch off the HBH-300 headset and switch it on again then the problem stops and in the following calls I can talk using the HBH-300.
This problem appeared only twice in the 15 days that I am using the MDA.
Obviously the phone did not power off in 10 secs (it was on when I had the problems) so the "sleep issue" mentioned previously could not have created the problem. Only the backlight goes off in 10 seconds. Do you think that the backlight might cause problems to the bluetooth?! :shock:
Click to expand...
Click to collapse
I am facing both problems described here. Does anyone know of a solution?
This is a known issue, but unfortunately it is not stated on Club IMate as a known issue.
This is concerning, because I assume i-Mate Techs are not working on this issue.
Over at Howards Forums Bengalboy states if you press the devices call button twice the headset incoming audio gets reactivated. I have yet to test it, because my caller hangs up before I get the device out of the case to press the call button twice.
One of these days I will beat the clock.
1.5 years ok, way back in Oct-03 I remeber many of us scrambling about all the MS Stack issues on the MDA II/XDA II, etc, and eventually tools were developed to help the issues.
I get rid of the PDA2K, because of all it's issues. Now the PDA2K has a better ROM and a new fix for the Broadcom stack.
Oh the misery.
I pressed the power switch on and also pressed the call button twice...I dont know which worked but my call did not get disconnected after the 7th minute...
Ujj
BT headset cutting out
I have the same problem - BT headset cutting out after a limited period of time, ~10 seconds.
Same problem here, when using bluetooth headset people can't hear me after 8 minutes, pressing the green talk button twice restores the connection.
Second problem: phone does not answer call automagic with bluetooth headset. (jabra BT 200)
Third problem: no voice dialing and no possibility to hear who is calling.
Are these MS Bugs or HTC Bugs?
_________________
T-mobile compact
ROM version 1.01.00 WWE
ROM date 10/21/04
Radio version 1.00.10
Protocol version 1337.36
ExtROM version 1.01.124 WWE
For the swedish Qtek S100 this issue was solved in the latest software update (1.06).
bamse said:
For the swedish Qtek S100 this issue was solved in the latest software update (1.06).
Click to expand...
Click to collapse
This is interesting - I'm running rom 1.06.00 WWE and extRom 1.06.115. I noticed that they have a extRoom 1.06.116 there, is that the one you are running?
espenleknes said:
bamse said:
For the swedish Qtek S100 this issue was solved in the latest software update (1.06).
Click to expand...
Click to collapse
This is interesting - I'm running rom 1.06.00 WWE and extRom 1.06.115. I noticed that they have a extRoom 1.06.116 there, is that the one you are running?
Click to expand...
Click to collapse
Yes, 1.06.116 it is.
It adds another issue though, making GPRS unable to reconnect after a phone call or USB Active Sync.
Hit the power button to reactivate - not the Green call button.
I also have this problem, when the device goes back to sleep my bluetooth headset microphone no longer works. I can still hear the other caller, however i need to hit the power button (Red one on the side) to get working again.
No need to disconnect the caller.
Been having a problem on my XDA II in that when I receive a call and answer it, it takes a few seconds before I can hear the other person. Sometime it woks fine and others the person can hear me but I can't hear them ?
It has been back for repair 3 times and it still does the same thing. The speaker is fine as it works loud and clear, it's only on incoming calls not on outgoing.
The place where I have bought it will now swap it out for a XDA IIi as you cant get the II anymore around here. That's great but I would still like to know why it went wrong ? Anyone got any clues ?
plz explain what is delayed.
Could it be just too much s/w running?
I found that when I am running activesync, calendar & contacts sometimes there is an awful delay in the response of the MDAII. Especially the BT headset has delays then of more then 20seconds (so I answer call on MDAII and then transfer it to headset when this occurs).
delay on phone
:shock: Me too!
Not sure if I should answer on screen,accept or reject,or green button.Both seem to delay,often with caller ringing again.
When the phone rings and you answer it. You hear nothing. It's a case of hello ? hello ? etc. They can hear you but I can't hear them then all of a sudden their sound will just kick in.
Actually sometimes when I dial out, I never hear a ringing tone and all of a sudden the person cuts in.
There is a delay. I have no software running at all. It does this from a hard reset as well.
What bugs me is that it has gone back 3 times and they claim it has been tested and fixed. It clearly hasn't.
Hope the XDA IIi is better, cos this was very annoying.
Hi Ekko,
Would you happen to be running Pocket Bluetooth Tools?
Cheers,
Pete
Hi, the phone was fine until about 6 mths old when it started doing this. I had Pocket Bluetooth on it and it used to be totally fine. This never affected it at all.
Obviously once this problem arose, I have hard reset the machine on a number of occasions and have used it as a clean machine. Same problem ? So not down to Bluetooth Tools.
Hands Free mode
In order to use an Himalaya with a BT headset you need to run 2.20 translated. The Hands Free profile works better and it will even support caller ID and there is no delay when answering calls.
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
Hi everybody,
I have this one problem. After 2 days of usage, my Hermes suddenly went mute. No vibration or screen click can be heard even If I changed it to the loudest. I missed a lot of calls and sms due to this problem. The only way to solve this problem that I employ is by soft-reset my device.
I really hope somebody can help me tracking to root-cause of this problem and in the same time providing or proposing a solution to it.
Kindly help. Regards
morisa
Device: DoPoD 838Pro
did you unmute it from the speaker icon ?
if you have a backup restore it if not do a hard reset just make sure you backup your contacts/ stuff first
Phone goes mute
I think I'm having that problem too. Just out of the blue it happened. Didn't install anything extra the whole week. But when someone calls it rings, and if it's missed, it doens't play the miss call tone... or any other sound in that case.
darky said:
did you unmute it from the speaker icon ?
if you have a backup restore it if not do a hard reset just make sure you backup your contacts/ stuff first
Click to expand...
Click to collapse
Hi,
I noticed that the problem started to happen when I long-press the "Green" Button to activate the speakerphone during a call instead of pressing the "Speaker On" menu on the screen.
I've no idea why but maybe that could be the problem. Presently, I have to press that "Speaker On" on-screen menu to activate the speakerphone to avoid this problem.
Maybe other users can confirm this problem.
Regards,
morisa
mmorisa said:
Hi,
I noticed that the problem started to happen when I long-press the "Green" Button to activate the speakerphone during a call instead of pressing the "Speaker On" menu on the screen.
I've no idea why but maybe that could be the problem. Presently, I have to press that "Speaker On" on-screen menu to activate the speakerphone to avoid this problem.
Maybe other users can confirm this problem.
Regards,
morisa
Click to expand...
Click to collapse
Got the same issue here and I don't use speakerphone
my pda´s auto mute so
No sound although speaker icon no in mute
I have the same problem. Out of the blue no sound is heard at all. I tried changing volume but it did not do any thing. Had to shut down (not soft reset) and restart device and it works fine. This happen several times and I can figure out why it does this.
If anyone can help...
Tal
Same here, I'm using a X01HT Softbank variant TYTN flashed with the latest HTC WWE rom and after about like 12 hours of use the device goes mute for some reason, making calls it works perfectly but playing sounds or ringers the speaker does not work. Anyone have any ideas? I'm thinking of maybe re flashing the device since most of my information is on my storage card. I'll see if that fixes the problem :-\.
same problem here....
Same here. Only a reboot fixes it.
I have the same problem but it only happens when using the speaker phone. After the call ends, then there are no more system sounds etc. I then have to soft reset, which pisses me off as I use the speaker phone plenty in the car.
If i dont use the speakerphone, then there is no problem. Kind of strange....
Has anyone got any ideas on how to solve this?
I have same problem. I thought it was software related, but seems that it is caused by the speaker phone. I had the exact same problem with my old IPAQ 6515. It must be a software issue with WM although the 6515 had WM2003SE and the TYTN has WM5 so I do not know. Really annoying though as I use this phone for an alarm and it never goes off because the sound turns off sometime while I am sleeping - Uhggggg!
I also have the problem. Only a Softreset brings the speaker back to live.
my new problem...misery loves company
same here; curiously 2 pages into this thread and there are no real solutions.
I have solved the problem on my TyTN.
The Midlet Manager is the root cause for the Phone Mute issue on my device.
lol I just started getting this issue out of the blue after a couple of months and I didn't install anything :|
yeah nothing but a soft reset brings the sound back
Happens to me too. Strange coincidence - I've just checked my m3100 and it's giving me the silent treatment now. Time for another soft reset
I never use Midlets, so that rules the above theory out for me. However my battery was almost dead. I was using WiFi at the time, which turned itself off when the warning notifications popped up. Maybe when the battery drops below an acceptable level it turns the sound off to save power, but doesn't restore it after charging?
nope it happens to me even if my battery is fully charged
this used to happen on my i-mate PDA2k, and my JasJar (Universal) running both WM5, AKU3.2, 3.3, 3.5 and unfortunately even WM6 :S
Hi All,
After checking and testing the phone. I found out that the only way for me to solve the muting problem is by silencing the notification sound when a new email arrives. Since I have an unlimited EDGE/GPRS, my push mail is working around the clock. Thus, by not having the new email sound notify, the muting problem gone. This is caused by the notification event locking up the sound and not releasing it even after I read the mail. Previously the only way to resolve is by soft-reset but now, no more.
I have no idea whether this work or not for others but you might try and post your solution here.
Regards,
morisa