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.
80 % times when I receive a call, I keep asking who it is for about 15 seconds until I hear the voice or the people hear me... The only extra thing I did is unlocking it. After some hard resets It keeps ocurring. I have to sim cards with the same number but I tried both of them. With my siemens phone it does not happen... Please help me :arrow:
I have the same problem with my IMATE... answering calls .. it takes somewhere between 5-30 seconds for the call to 'drop in' as in the phone stops ringing on my end and the person calling me end... but its jsut silence for anywhere up to 30 seconds, sometimes more!
Any ideas? I'm currently looking through the forums for an answer...
I find a soft reboot helps it a little....
Same problem
I have exactly the same problem...
It takes anything from 2 to 30 seconds to answer the call, by which time the person on the other side usually disconnects anyway.
I have some suspicion it may be related to the Pocket Bluetooth Tools.
Same here
I experience the same problem with both incoming and outgoing calls although not always.
I did not unlock my phone, but do have BT tools installed. I do not hear anything for about 5 - 15 sec. and the person on the other end doesn't hear anything too.
It's not a big problem, but should not be there either!
QTEK 2020
ROM 1.72.00WWE
Radio 1.14.00
ExtRom: 1.72.126
i thought this would of been a bigger more common problem.
the only thing i have running is the pocket bluetooth tools, otherwise its just standard. no hacks etc...
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.
Hi, can anyone advise as to why I lose the all sounds on an Orange Branded M3100 phone, other that Microsoft voice command 1.6 no other software has been installed! The details of the ROM are as follows
Operator Version: 14.123.1.614
ROM Version: 1.23.61.4
ROM Date: 07/13/06
Radio Version: 1.06.00.00
Protocol Version: 32.37.7010.01H
Here what happens no sound on the phone, reset the phone sound is now back, after a while, don’t know how long but the sound disappears, you get no ringing sound, menu click sounds nothing, reset the phone again and all is back, so it would suggest that it’s not a hardware failure but a software failure, how can I stop the orange branding installing itself after a cold reset in case something there is causing the problem, has anyone else came across this problem?
This is a brand new phone only received it Friday, does it need to go back?
Kind Regards
Dogo
I've recently noticed on my 8525 too, after a while it seems to just go on silent but the setting isn't changed it still set to on and no sound comes out of the phone no matter what program is used.
Phew, I thought it was just me..
I have noticed it may be something to do with the Bluetooth ear piece, although it always seems to happen when I have left the phone a while. and never when I try to check for the problem
To isolate whether this is hard or software you could try doing a full backup. Do a hard reset and let the device run for as long as it would normally take to show the problem, without any additional software. But do run wifi and power intensive applications to warm up the device - as this can cause internal connector problems.
If the problem is gone, this will tend towards a software problem although not an absolute guarantee. There are some issues that are related to both soft and hardware!! For example the screen fading to white issue can be caused by running (power intense) software that makes the device warm and that in turn causes pressure to be put on the screen.
A final thought, the speaker connection block is next to the stylus tip. There have been cases of the inserting and removing of the stylus causing the connector to become loose. This can cause intermittent sound or no sound at all. The warranty voiding fix is easy. Remove back and check connection is tight. No further dismantling needed. Ensure camera toggle arm is engaged before putting screws back in. (Rear Speaker)
The front speaker can also have issues. has spring contacts that can become slack - poor contact with m/board. There is a thread on checking this.
Mike
No Sound, not a Stylus issue
8525, ms voice dial 1.6,
HTweakC 2.0,
SBP Mobile Shell 1.0.0 build 2632.
ROM 1.34.502.1
radio 1.16.00.00
This has been happening about a week, nothing new installed. On Saturday I missed 12 calls because it was "auto-muted" nothing was on mute, just no ring sounds or anything else. I thought it might be some setting, I suspected that it didn't come back after I had set on vibrate for a meeting, so I went through everything, looks good. had to soft reset for audio to come back. Happened again Yesterday morning after being on charger, had to soft reset, happened again this morning after being on charger, had to soft reset. I'm suspicious of the charge ciruits, the phone was placed on a night-stand and I checked to make sure sound was working AFTER i plugged the charger in (i am an on-call engineer for hospitals) when I got up this AM the first thing I checked was the sound, no sound. Had to do a soft reset and sound is fine.
THIS IS VERY, VERY, VERY troubling.
i cant say that my sound has been "loose"
thefunkygibbon said:
i cant say that my sound has been "loose"
Click to expand...
Click to collapse
yep, I agree. My keyboard slider might be loose, but never had problems with the sound.
No sound - possible solutions
I too have had the no sound problem, but I also have a solution (well it seems to work for me and a few other people I know)
I have found that if I have more than about 800 sms messages on the phone (combined count across inbox, sent items, deleted etc...) my phone will decide sometimes to stop making any sounds.
Other symptoms include thew screen not going back to the background when problems are "closed" (well press the X button), sometimes not changing from portrait to landscape.
Hitting the reset key temporarily fixes the problem, but it strike again at any time...
I have seen this on both the official UK orange firmwares
As a side note, more than about 1000 sms messages and 5 unread sms messages and the phone will lock up about 10 seconds after the phone boots up. You have to be quick when the phone boots to go in to the sms inbox and delete 1 message before the phone locks up. This can be a bit tricky but i have done it a few times
from readingmany related threads, it looks like there are several causes for this issue. for me, it was definitely microsoft voice command 1.5 and 1.6. I turned off any notifications from voice command and my problem went away. no calendar voice announcements, no callerid, no bluetooth routing announcements, etc. voice command simply doesn't give up control of the audio sometimes, and it appears to occur most when it wakes up and announces something.
All I use voice command for now is voicedial. try that a while and see if you are fixed.
1.5 was worse, but 1.6 does it too.
good luck!
wes
saga continues
It did it again, twice in one day. Picked up the phone, (it had been resting on the table for several hours). No sound, I tested by placing a call and turning speaker on.. this works! So the speaker (rear) is fine as well as the front (ear).
After I heard the speaker on speaker phone I tried hearing the dial tones or other sounds, none. No incoming ring.
Device and phone volume on FULL
Turn volume off, vibrate, on, off on, and from phone screen turn to vibrate then back to sound
Vibrate still works for inbound calls
Turn voice command off and on
Go to phone (in settings and play the ring I've chosen) and suddenly it’s working again?
I'll try the turning all but phone options in voice command to no-notify. But to tell you straight, this is silly, one more day of this and it's probably (unfortuately) crackberry city for me. I simply can't have a phone that doesn't ring. I guess some ittertation of an O2 would do.. but I'm not too keen on plopping down another 5bills....
any ideas?
labrati said:
It did it again, twice in one day. Picked up the phone, (it had been resting on the table for several hours). No sound, I tested by placing a call and turning speaker on.. this works! So the speaker (rear) is fine as well as the front (ear).
After I heard the speaker on speaker phone I tried hearing the dial tones or other sounds, none. No incoming ring.
Device and phone volume on FULL
Turn volume off, vibrate, on, off on, and from phone screen turn to vibrate then back to sound
Vibrate still works for inbound calls
Turn voice command off and on
Go to phone (in settings and play the ring I've chosen) and suddenly it’s working again?
I'll try the turning all but phone options in voice command to no-notify. But to tell you straight, this is silly, one more day of this and it's probably (unfortuately) crackberry city for me. I simply can't have a phone that doesn't ring. I guess some ittertation of an O2 would do.. but I'm not too keen on plopping down another 5bills....
any ideas?
Click to expand...
Click to collapse
I have just read your last two posts. I am wondering whether you are saying you have a sound/ringer problem OR whether you mean the phone sometimes crashes and therefore does not ring (i.e. you then need a soft reset) and sometimes you discover you've missed a call but never heard it ring.
If the above is true then I think you need to look for the solutions for avoiding hangs/freezing. I can guide you to these or a search will show them. It certainly does not appear that you have any physical problem with the speaker/earpieces.
Mike
dogo said:
Phew , I thought it was just me..
I have noticed it may be something to do with the Bluetooth ear piece, although it always seems to happen when I have left the phone a while. and never when I try to check for the problem
Click to expand...
Click to collapse
Hi, I never had a sound issue untill I started usin my HT820's, but have noticed a few times lately that my device sounds arent working, (I dont mean always through to the bluetooth headset) and I just power off/on the device, I dont get that many calls, so I havent missed any, and wasnt sure if it was rom or bluetooth related for sure, but I do usually leave my bluetooth on, just not always the headsets, it also doesnt happen a whole lot.
Loose connector
I'm not sure if this will help anyone, but i was losing sound on my 8525. I had dropped my phone twice and the rear speaker connection had gotten loose so i opened it up following the directions at http://www.howardforums.com/showthread.php?t=1152710&page=1&pp=15
and now i have sound again.
Continued Issues
Mike, thanks, the issue isn't with the phone locking up at all, it's been very stable, I think I've soft-reset probably 3 times in two months.
The phone literally will stop emitting any sounds. I can still hear if I place a call and if I place that call on speaker phone it's fine. However if you call the phone, try to play an audio file, etc there is no sound that emits from the device.
It did it AGAIN today, I tested, was able to place a call and put it on speaker and called it with my other phone, the pop up screen announcing the inbound call came up and everything else on the phone worked as it should (except no ring). I then went to settings phone and hit ok (top right of screen). BAM.. sound was working on the device again, inbound calls ring, able to play audio etc.
I did note one other possible anomaly, I have my PTT mapped to initiate voice command, when trying to use this I was unable to initiate voice command. After going to phone and pressing OK, voice command started working again. W/O voice command I'm sunk, I have 500+ contacts.
I placed a call to AT&T and I'm back on the "chronic retention" list.. ughhh.. I went through 8 treo's last time. I don't want another basket of refurbs to deal with, I like WM so much better than previous interfaces.. any ideas are very, very, very welcome.
-mike
More information
This morning, the sound was gone again, but I went into settings and started playing to see what else might induce it to work again, I tried voice command again, disabled and re-enabled, that didn't work.
I then went into sounds and that didn't work, went into Today, and Buttons neither of those worked, but when I went into input (didn't do anything, just opened it and closed it) sound started working again.
Hopefully, none of you guys have a newer ROM with the loud startup animation and attempted to turn down that volume via the registry as outlined in the wiki. Unfortunately, doing that also lowers the speaker volume so I just disabled the animation instead. Phone and bluetooth sounds fine but mp3 and everything else were also lowered to a whatever level depending on the startupanimation volume you set.
update
It did it to me again yesterday, this time only going to settings phone and pressing OK would make sound come back.
Today, the phone refused to dial or emit any sound. Would not come back after soft reset (would not dial, no sound) had to do a hard-reset (removed battery). After first soft reset a windows came up to advise that mobile voice command couldn't start...
For a darn near $500.00 phone this is pretty sad. Love the phone but gee whiz...
Daily occurance
Well, it does it every single day at least once a day, and I've noticed the phone has slowed a lot, sometimes during SMS or email the cursor goes away or I have to wait 20-30 seconds for words to complete typing after I've finished. I guess I'll get my refurb next week. Perhaps go back to palm.. dunno...
possible fix?
I turned OFF the SMS message sounds and it seems to be working w/o losing sounds again! I'll let it run for a couple of days and see if this is the deal, but I now have no audio announcement for ActiveSync, POP email, SMS, or MMS. I do have audio/vib for missed calls. Anyway, it's been up and running fine all day. Good Grief.
no fix in sight
On hold with ATT right now for another phone. It did it again today at about 10AM. Strange, it may be time sequential, but it didn't do it at all yesterday.. it was great to have the phone ring.
Hey, I've been lurking these forums for a while but I thought I'd come on to ask a question. I tried asking on sprintmogul.net but they didn't really help.
I've had my mogul for a few months but lately it's been developing a really annoying problem. I'm really not sure where it started exactly so I can't blame any apps in particular. When I receive a call the caller ID / ring and vibrate go off perfectly - the problem happens when I try to answer the call. Generally one of three things happens:
1 - The call connects instantly and just works - this happens pretty rarely, I remember the last time it happened the person calling was also on Sprint, if that makes any difference.
2 - The phone will just sort of hang there for about 10 seconds, caller ID popup still there, the ring stops though. Eventually the popup disappears and I get a missed call notification, as if I never clicked the answer button. This is what usually happens.
3 - The phone hangs like in situation 2, but the call eventually connects. This only happens if I press answer almost immediately after the phone starts to ring.
I'm on winMo 6.1 with the latest radio and am not running any major mods or hacks, just a few reg edits. I'll probably try a hard reset soon but ideas on things to try would be appreciated!
I am seeing this also, on both my own xv6800 and my wife's. It's VERY annoying.