I know this topic has be address many many times and there are still no soluation to the problem.
So.. I want to make a poll to see how many user is experiencing this problem.
I hope to grather enough data to see if it is a hardware problem or Firmware problem so that i can address to O2 regarding this issue.
I love my PDA/phone.. but... this issuse really bugs me cos i used the phone for business and it always happens when a important call arrived... :evil:
Pls, Lets Vote with your honest answer...
Derek
No problems here....
What i've experienced is that sometimes the ringing sound is very quite even though the volume is at maximum. I make a soft reset and everything's back to normal.
NO SOUND
I have also experienced the same. I normally have to do a soft reset to fix the problem. Seems its a firmware issue to me.
One more issue is that we need to disable the power off system setting after 3minutes.
If not, a phone call will be automatically ended after 3 minutes talking.
i have also experienced this problem. i had a important caller call me twice and i didnt hear my phone ring. it was also next to me. luckily, i had my backup phone with me when he tried that line.
agreed that we shouldnt have to soft reset to get back the ring tone functionality. i personally think its a caller id version problem, but thats my opinion cause its easier to fix. i just hope it isnt a firmware problem since i wont hold my breathe on O2 releasing a rom upgrade in my phone version.
im going to try some reg tweaks to see if it will help, once my main pc is up and running (currently moving). i just dont want to go back to an older rom because of a ringing problem. but it IS a big problem for most of us.
ps. sorry about the spelling mistakes and punctuations. im on my pda at a coffee shop.
Yup I have see the no sould on outgoing, no sound on incoming, reset does the trick for me. Also feel that the sound is low in general (even if set to max)
Ha.. i call XDA today in their headoffice in Singapore. The CS guy told me.. they know this issue and say there will be a new (Rom) or patch release very soon.
After seeing the vote result. I believe that the issue is do to software, not hardware.
I have a firend that design such product. he told me that it could be that DSP script is not written well. He said, the Echo Cancelling must be overflow causing the unit to manufunction. and after reset, the overflow will be clear out, so the unit function again.
I hope O2 is really releasing a new patch to fix this issue. If not, i think i am force to go back to my Sony Ericsson P910i or one PDA and one phone option.
i'm glad that O2 recognises the problem and not passing it on to other people. thanks for the information rcbear. glad you took the extra steps get them looking this way.
i hope "soon" means in a waek or two.
same problem
My ringer always works but sometimes, at least every other day. When someone calls me i can not hear them, they can sort of hear me, but the earpiece is dead. A soft reset fix's this problem. Is my issue related to the current issue dicussed in this thread? Thanks
Jeff
I have the problem
But I get it seldom and sporadically.
pda2k (out of the box)
ROM: 1.22.00 WWE
Radio: 1.06.00
Protocol: 1337.38
ExtROM: 1.22.162 WWE
AT&T/Cingular
Re: same problem
jeffro01 said:
My ringer always works but sometimes, at least every other day. When someone calls me i can not hear them, they can sort of hear me, but the earpiece is dead. A soft reset fix's this problem. Is my issue related to the current issue dicussed in this thread? Thanks
Jeff
Click to expand...
Click to collapse
Hi Jeffro01..
Welcome to the club.. :lol:
Derek
I don't seem to have the ring volume problem, but my phone will get into a state where it rings, I answer the phone, but there is no audio. In the six or so times it's happened, I haven't really determined if the caller can hear me. A reboot fixes it.
I can't pin down any one thing I do to cause it to get into this state, but it seems like a software/firmware issue.
I have this problem too.
I had to send my BT headset for repair for two weeks and noticed it did not happen during that time while it started again since I got my BT back.
When it happens (once to twice a week) I soft reset my SPVM2000 and it then is ok.
Also the BT Orange Switzerland patch makes the problem appear less often.
Phone ring problem got me twice today...
Both times, never heard three calls, but the phone still reports them as being missed.
Gotta be a solution for this or I'll be soft resetting every time I finish a call/use.
I had to send my BT headset for repair for two weeks and noticed it did not happen during that time while it started again since I got my BT back.
Click to expand...
Click to collapse
If so I have 2 questions for everyone who has this issue:
1, Do you use a bluetooth headset or any other bluetooth device (gps...)?
2, What is your current bluetooth version and build?
I have Bluetooth build 3900, and I'm using 1.33.
No probleme here
not using BT or WiFi.
Where can I find my BT version?
I don't also have the 3 minutes switch off pb, the PDA function switch off after 3 minutes but the phone remains operational. I often switch the PDA off myself whilst on the phone to save on batteries.
...Hi everyone! (1st post!)...
I get the dead-speaker in calls too...
I took delivery of my first SPV M2000 a couple of weeks ago; it had a few problems, one of which was that the speaker would be dead occassionally when making or answering calls requiring a soft-reset to resolve. I initially thought this might be caused by the device not correctly recognising external hardware had become disconnected - handsfree/BT/car-cradle etc. - but it did seem to be at random.
Orange replaced the device last week; and by day 3 without using any handsfree/cradles etc. and BT and WiFi not even enabled (much less paired/connected); the dead-speaker problem reappeared.
I'm not going to bother chasing Orange about this issue on its own (this device doesn't exhibit any of the other problems I had with my first); as it seems to be a pretty common problem that's going to require a software update to fix. Needless to say when I read that HTC have written a fix I will be on Orange's back to make a fix for their ROMs public. (dreaming?).
Just FYI, both the initial device I was supplied and the replacement have the same software versions (in my sig).
Regards,
Rob.
I circumvented (temporally fixed) the ringtone problem by setting the default ringtone to "None", and also set the phone to vibrate. Then Re-enabled MS Voice Command to announce all incoming calls. The only problem is, the voice isn't loud enough in noisy places, but it does the job in the office or semi noisy environment. I guess this will have to do until a verified fix comes along our way.
Related
I have a SPV m2000 with the latest rom from orange, the first problem i had was when you go to reply to a text you sometimes could only send 70 char. before you had a 2nd text, but that was sorted by this site by turning the use assci code off, the onlt other problem is this -
Sometimes when i go to make a phone call, i dont hear a dialing tone, but after a few seconds it starts counting up like in connected to the call. The person im ringing says that they got the call and they could hear me but i didn't reply. This has happened many times now, it seems to be after its been a long time since i restarted the phone, e.g in the morning etc
I was just wondering if anyone else had ths problem?
Silent Calls
I had this problem from day 1 with my M2000, and I had to soft reset to clear it. Recently updated Radio to 1.13 and Bluetooth to 3900 and problem hasn't re-occured. Of course this may be a coincidence... :roll:
Turn on BT and leave it on, even if you don't use it. This worked for me.
Sometimes when i go to make a phone call, i dont hear a dialing tone, but after a few seconds it starts counting up like in connected to the call. The person im ringing says that they got the call and they could hear me but i didn't reply.
Click to expand...
Click to collapse
There is a huge thread on this somewhere with a poll (survey) in it. Last time I checked around 76% of owners of this handset have the 'no sound in call problem' to some degree.
My old BA did it 2-3 times a day. My new one with 1.13 radio ROM does it less often, but the problem still remains.
If you are really unhappy, and need a reliable phone you obviously wont want the BlueAngel again! Take it back to where you bought it. They will try to deny it is a known problem and at best give you a new Blue Angel. My advice is to find the thread on here, print all 10 pages of it and take it to where you bought the phone. They won't be able to deny it with the evidence right in front of them. Make sure you show it where the public can see/hear so they have to try and talk their way out of it in fornt of an audience
I did this to prove that the whistling screen was a known common problem, not something caused through my neglect and so I was entitled to a new handset under my warranty, not just a new screen (Everyone said the problem came back despite a new screen as the problem is with the circuit board)
As I remember, about 1 in 6 Blue Angel users will end up with a whistling screen after owning the device for a month so you probably have that to look forward to aswell.
My 1.40 iMate ROM may have helped too.
Read the wiki and upgrade to wm5. Problem has not happened for me in months.
I'm having the same problem for a week now...
I was on the street with my BA making calls and all went ok. I use it for my work, so I do lots of calls a day. Suddenly, I realized, when I call, that the other can not hear me, nor can I hear them! The counter is running, the screen says "Connected". I haven't done anything to change the configuration, nor it have dropped it from my pocket.
I'¡m getting crazy. I don't know what I've done wrong.
Things tried unsuccessfully:
-Lots of device resets..... Between tryes and Updates.
- Reinstalled WM5 using a different ROM. Now I have TM 1.3. [http://forum.xda-developers.com/viewtopic.php?t=42632]
- Upgraded Radio to 1.15 (previously, I had 1.13)
- Used a Bluetooth headset. It worked, I could hear the sound from the phone, at least. Only thru the bluetooth headphone. Still, I could not hear any phone-sound from the loudspeaker when I turned off the headphone and the bluetooth headset were disabled, even with the Bluetooth signal ON, as suggested on other post. Each try with a new call.
- "Installed" the Unidirectional patch (copied the AudioGW.dll file over the old one successfully, reset, etc..)
- Turned off the device and leave it off for a while. Take off the SIM card, touch it (cosmic vibrations ) Sometimes, before, the SIM card went a little nuts if I resetted the device too much -maybe :?- or if I got the battery off...
Sorry if this has been posted before, but, at this point, when I've been tried almost (I think) everything, i couldn't find anything relevant using search.
Please, any help will be greatly appreciated!!! Maybe I can use at least a link to another thread..
Thanks
come on, people, a little bit of help here Still making calls with my old Nokia
Out of interest... do you have any wisbar apps installed?
No wisbar apps installed. Thanks
I'm having the same problem. Most of the time this occurs the first time I use it in the morning. The other side can hear me, but I can't hear them. I softreset and it works again.
Yes, I've checked and there's lots of posts about this problem. It differs from mine in the sense that the other CAN hear you. In my case, nor I or the other part can hear us....
As you can read, I've done lots of soft-resets, now I have also 3 hard-resets with everything "at 0" (clear Registry Hive and format Storage). But the problem remains. The only thing I see I can do now is downgrade to wm2003 and see.......
Thanks for your answer.
mutho said:
I'm having the same problem. Most of the time this occurs the first time I use it in the morning. The other side can hear me, but I can't hear them. I softreset and it works again.
Click to expand...
Click to collapse
I've moved to the "BA upgrade, etc" forum. Please, help me from there!! Still looking for an answer
http://forum.xda-developers.com/viewtopic.php?t=44440
there is an issue with BT and this behaviour. Either you need to always have BT activated or once you have deactivated BT you need to reboot your device. I have the same problem myself.
Regards,
Fredrik
I'm using an SX66, with the official WM2003 SE firmware.
Sometimes when I get a call, I can't hear anything....and I don't think they can hear me. When I do a soft reset, it starts working again for a while.....but then the problem starts again. So I have to do a soft reset every few days, and it's getting annoying.
Doesn't anyone know what the problem is and/or how to fix it?
i have the same problem with my XDA IIs. in addition i have downloaded the patch in the Wiki but the problem still remain, sometimes it happens.
try to turn on your bluetooth, it will fix the problem in my device..... but still its very annoying..
i have the same problem, i have i-mate.... PDA2k, i should reset it every day, i think there are a program could do it at any time i adjust, it's called auto reset
I know that iMate released a "single direction voice patch" to fix a problem that existed with not being able to hear the person calling you (while they could hear you). It sounds like what you're describing, it used to happen me and this patch actually fixed it. I don't know if it's good for the SX66 but it worked for my PDA2K.
http://www.clubimate.com/t-PDA2K.aspx
Yeah it happens my xdaIIs. not so much latley but it still happens. i have searched and searched but cannot find a soloution.
Hi all,
I have a problem with my HTC TP2. All of a sudden, the microphone stopped working... There are a couple of strange things though!
- First of all, it came out of nothing. I didn't do anything special when the problem came...
- Headset works, so I first thought it was a hardware problem, but after some hardware resets, it started working again! Unfortunatly, it didn't last for long. 5 minutes later it was stuck again :s
So it is probably a SW bug...
- If I talk really loud, you can hear something, so probably the amp doesn't work correctly... But why does it work with the headset then...
I've seen others with the same problem, but haven't found a real solution, but to send it to HTC for repair... I would rather avoid this!!
Can anyone help me please?
I have the same problem. At first it started just happening every once and a while I would get or make a call and the person on the other end couldn't hear me, now it's probably 90% of the time they can't hear me. I've even tried booting into android and it still doesn't work which leads me to believe my issue is hardware unless someone else has a better idea
If it is not working properly after a hard reset without installing any applications, then it most likely hardware related. Send it in for repairs.
one of my touch pro 2s had this problem, i just took it sprint and they gave me another one.
I've been having a weird issue with my phone muting the mic during calls. This mute seems to be independent of the mute softkey on the phone (when it gets muted, the softkey is not lit, nor does toggling the softkey unmute the mic). This is incredibly annoying as once it mutes, the only way to continue the conversation is to hang up and redial. This issue occurs both using the phone normally (phone to ear), with a wired headset (so no possibility of cheek activating softkey), and with a bluetooth headset. In all 3 scenarios the mute will toggle on its own, seemingly randomly. I can go through a 40 minute call with no problems, yet sometimes it seems to mute right after I make the call.
Has anyone else had this issue?
This is what I have done to troubleshoot the issue:
1) With the original phone that I bought, I reset that phone back to factory settings and set it back up. Issue still persists.
2) Had the phone swapped out at the same Verizon store that I bought it at. Issue still persists.
3) Reset the new phone back to factory defaults. Issue still persists.
I will try the following:
Reset phone back to factory defaults and not install any apps whatsoever (running only apps that came with the phone, won't disable anything such as VZW Backup Assistant, etc either). Something tells me that this won't fix the problem either.
Does anybody know what I can do? This is a great phone but I'm a little miffed about not actually being able to make calls with it. I called VZW tech support and they are willing to replace the phone, but I basically have to go from a NEW phone to a certified like-new device (which VZW allows up to a maximum of 2 blemishes on the back, which I am not ok with) through no fault of my own.
See this thread on the Google Code bugtracker: (Hm.. I can't seem to post a link as a new forum member.. well its bug ID 24019 on the android bugtracker off of code.google.com) Don't want to munge up a link and piss off a mod or anything.. sorry guys :/
That im affraid is a nasty bug that is yet to be fixed.
Have you experienced this bug? I'd like to hear from members of this forum on if they have this issue, and how they resolved it (if at all). I was surprised that something so blaring isn't on the list of known GNex/ICS bugs (at least not on the one I saw on androidforums.com). I'm just uncomfortable with how the Verizon reps are pretending to not know about this issue...
//Edit: Oops. Found the other thread in this forum on this issue. It seems that I'm describing this as a mic muting issue, whereas other people are describing it with "mic cutting out" so I can never find their posts. Post ID 1403051 in Galaxy Nexus General.