Develop Bugs

Pls Vote, Problem with "NO SOUND"

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.

phone stops ringing after a split second

i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help

Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300

Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.

Rhodium400 in-call problems with hearing either side (proximity sensor?)

I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.

Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.

I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.

I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.

[Q] random calls...anyone else have this issue ?

I am not entirely sure if it is an android bug or specifically samsung. Anyway on my s5 and my N4 if I go to make a call occasionally it will say call not sent...when I go to redial the number the phone has already chosen a different contact at random to call...to make the issue worse the screen will then blink on and off in succession preventing me from stopping the random call...this seems to happen once or twice a week...I have already disabled the gesture option that calls people so I am at a loss here...anyone else experience this?

Not an Android bug. I've had it where the phone would try to connect and give up, but the second attempt would go through. That's a reception issue though.
It sounds like your software is glitch in for some reason. Usually a factory reset will fix this (unless you rooted and did something to alter the system, in which case, your alteration could be the cause). If not, then warranty time.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk

Yes, I have this too. Really annoying, happens every few weeks, and seems to go away after a restart.

Sorry to bring an old thread back to life but, has anyone figured out this problem? This happens on my Verizon Note 4 as well, so it is not carrier specific.
Everywhere else I have searched no one has an answer.
Just usually a call is placed. Then a quick message pops up with "Call not sent". Then another contact gets called instead. For me I don't see any pattern to how the wrong contact gets chosen.
This happened in KitKat and now is happening still in Lollipop.
Also I did a factory reset when I upgraded to Lollipop. Any ideas?
Edit: Just thought about this. Do any of you who have the problem use Google Voice?

Phone Call Sound Problems

Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.

erickh0 said:
Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.
Click to expand...
Click to collapse
Maybe a theme issue?

Nope. Just reformatted the phone and did not install any theme/launcher apps

Same issue
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.

Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
same here

Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Me too. Bumping in hopes of a fix.

Same. I'm running a custom ROM and haven't upgraded to 8.0 yet. Does the issue persist with 8.0? Google told me today to revert to stock and upgrade to see if that fixes it.
Sent from my Pixel using Tapatalk

Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help

Having the same issue on a regular Google Pixel. Also Google Assistant is not working using the "Ok Google" voice command and the phone app - answering and ending calls lag - same issue mic and speaker do not work. In Safe work, they work but on rebooting same issue persists.

xbiggyl said:
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help
Click to expand...
Click to collapse
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.

me too
jasona08 said:
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.
Click to expand...
Click to collapse
stock O, Rogers.
bump - hoping someone has heard something somewhere.

Same here for my regular pixel, this is really annoyed. It just starts happening after almost 12 months since I got it.
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse

I have been having these same issues with my phone. I noticed it happened after I downloaded the what's call app to make a WiFi call. I noticed another user had the problem after installing what's app to her phone. Could this somehow be the problem? I am not super tech savvy but I am convinced it is related to my downloading the what's call app. I have uninstalled the app. Still the problem remains. Any ideas? Thanks.

Has anyone that posted in this thread was able to resolve this issue? I also have this problem, I'm currently waiting for it to happen again so I can pull logcat but no idea what I should be looking for since I have no idea what can cause not being able to hear the caller so randomly.
I was originally suspecting V4A, but last night I flashed stock system img, did not install V4A and same issue occurred.