Database Users

Loosing all sound?

Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S

sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have the exact same issue. Very strange and rare. So the occasional reboot fixes it but annoying at times.

sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have come across the same today on the 2.05 revision. It started this afternoon, since I have had to reboot 5 times. The latest was only about an hour or so apart. When I make calls, I do not hear any sound, no ring tone, not the other person. Also adjusting the ring volume with the volume keys does not make any sounds. Even on my bluetooth headset I do not get any sound. No rings on incoming calls, no speaker phone ... absolutely nothing. This has become a huge issue an I'm going back to my 1.5 image at this point.

Actually, reading through threads about both ROMS, I'd say there are quite a few people starting to encounter this problem...has anyone with this issue gone back to 1.5 to see if it goes away then?
S

just a note, the people on the other end when making a call can't hear anything either but the call does go through. i had to use the g/f BB to call and my buddy thought it was his phone. I'm so mad because I thought this was a done deal but looks like I gotta go back to 1.5

+1 same issue on Fresh 2.0d
When it happened it affected incoming and outgoing calls, earpiece, speakerphone, microphone -- the works. Person on other end could not hear anything either. Fixed with reboot.

me and my coworker both have this issue with our heroes, he couldn't stand it and went back to fresh 1.1 and it went away
I still get the issue once a day, full reboot solves the issue.
I cant seem to pinpoint when it happens, it just happens.
it started with the first fresh 2.0 and then continued with every 2.1 i have tried
i couldn't find a post in this forum relating to a fix for this, unless someone can prove me me wrong and i hope someone does

+1 same issue on Fresh 2.0d and DCv1
Same as others, a reboot will fix it but by that point you just missed a call.
Or if the sound goes out you might miss a few calls from not being able to hear the phone ring.

yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap

Avalaunchmods said:
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Click to expand...
Click to collapse
Thanks. You're speaking greek to me as far as the boot.img and all that but if you have an idea of what's going on I'm all ears on fixing it. If there is any sort of info we can provide just let us know.

Im here to help as well, If you need any testers I am willing to do what ever is needed! Anything to fix this problem!

Related?
10chars
http://forum.xda-developers.com/showthread.php?t=657244
Click to expand...
Click to collapse

DroidDhakan said:
Related?
10chars
Click to expand...
Click to collapse
Of course it is,its the fix(hopefully) for it

Answering a Call

Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)

yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.

Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.

Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).

Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.

What carrier are you on?

this happens to me too.its so annoying. im on att

Can't find the thread but it was pretty long.

nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.

This sounds like an att problem not a nrsux one problem

I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.

I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One

Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.

I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.

I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?

khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.

Sounds more like a network issue than a hardware issue, IMO

This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.

Can't be heard after some time.

This is very frustrating.
I use my phone for calls between 3-5 hours a day. I've been having this issue where I'll be on a call and after some time (ranges between 2-10 minutes) I can continue to hear people but they can't hear me. I use the Samsung headphones with a built in mic to talk. I'll notice that they can't hear me, I'll unplug the headphones and they still can't hear me. I hit speaker phone and still can't be heard. I end up hanging up and calling back. This happens about 30% of the calls I'm on. I also bought other Samsung headphones and the problem persists. It's also not always with my headset. I've had this muting issue happen while talking directly on the phone.
Here is the kicker. I'm on my 3rd s6 edge+ and I've had the problem with all 3!! My first phone the microphone by the speaker stopped working. My second one started having the same issue with the mic. But all three had the same exacting muting issue.
Anyone else in the same boat? Any suggestions on fixing this?
Thanks

mikeysweet said:
This is very frustrating.
I use my phone for calls between 3-5 hours a day. I've been having this issue where I'll be on a call and after some time (ranges between 2-10 minutes) I can continue to hear people but they can't hear me. I use the Samsung headphones with a built in mic to talk. I'll notice that they can't hear me, I'll unplug the headphones and they still can't hear me. I hit speaker phone and still can't be heard. I end up hanging up and calling back. This happens about 30% of the calls I'm on. I also bought other Samsung headphones and the problem persists. It's also not always with my headset. I've had this muting issue happen while talking directly on the phone.
Here is the kicker. I'm on my 3rd s6 edge+ and I've had the problem with all 3!! My first phone the microphone by the speaker stopped working. My second one started having the same issue with the mic. But all three had the same exacting muting issue.
Anyone else in the same boat? Any suggestions on fixing this?
Thanks
Click to expand...
Click to collapse
Doh. I dont know which firmware/rom/kernel you're running but maybe you should wipe cache/dalvik or clean re-flash.. If already rooted, give a try a custom kernel. Hope you solve it. Thanks.

I have the exact same issue, except my call quality is poor and calls drop a lot as well. Im on my 3rd phone as well. All the issues have followed me on the phone. T mobile told me that I would have to wait for the marshmallow update since its a known issue with the phone and it should correct it. I told them it wasnt a good answer so they are sending me a new sim card to try out and see if that helps. Personally I hope it doesnt so I can get a new device

Konsstantine34 said:
Doh. I dont know which firmware/rom/kernel you're running but maybe you should wipe cache/dalvik or clean re-flash.. If already rooted, give a try a custom kernel. Hope you solve it. Thanks.
Click to expand...
Click to collapse
Oops!
I'm running completely stock, no root/rom/kernel changes at all:
Build# LMY47X.G928AUCU2AOJ1
Android: 5.1.1
Kernel Version: 3.10.61-5921265

bb4ninja said:
I have the exact same issue, except my call quality is poor and calls drop a lot as well. Im on my 3rd phone as well. All the issues have followed me on the phone. T mobile told me that I would have to wait for the marshmallow update since its a known issue with the phone and it should correct it. I told them it wasnt a good answer so they are sending me a new sim card to try out and see if that helps. Personally I hope it doesnt so I can get a new device
Click to expand...
Click to collapse
Ugh. It's going to take forever for Marshmallow to come out. First Samsung needs to rip it apart, then AT&T before it gets to me.
Let me know how the SIM change works for you. That's one thing I've yet to try.

mikeysweet said:
Oops!
I'm running completely stock, no root/rom/kernel changes at all:
Build# LMY47X.G928AUCU2AOJ1
Android: 5.1.1
Kernel Version: 3.10.61-5921265
Click to expand...
Click to collapse
Umm. I see thats AT&T, isnt it? If so, you have got locked bootloader etc, I dont have proper info about it sorry. I prefer you to try something like wipe cache/dalvik etc but it may bricks your phone. So you better ask that in AT&T Forum Good luck.
Edit: I saw your post after posted mine lol. I've simfree g928C btw.

speakerphone software problem - really low

even though no one seems to suffer from that problem, i must ask again-
the problem is a low volume while talking on the phone using the speaker. THEN AND ONLY THEN.
it's working perfect while playing videos, games or music. there are no complaints from the other side of the conversation. no problem while talking with headphones or w/o other devices. nothing. only on my end.
it's probably not a matter of hardware because a lab switched my speaker with another one's and mine worked perfectly on his and his didn't on mine. (same problem that is)
ALSO, i've already updated twice 7.0.1-->7.1.0-->7.1.1 and no changes.
I've already factory reseted, wiped all, cleared cache and data, and did everything i could think of, but burning the damn thing.
the ONLY conclusion i got to (me and the lab) is that there's a code or other software glitch that limits the volume.
PLEASE THINK OR TRY TO FIGURE THIS PROBLEM OUT

I got a similar problem like you.
The RECEVIER doesn't work while talking on the phone.
But the speaker works perfect.
Weirdly the RECEIVER works perfect when I use the other APPs like Wechat to listen some voice messages.
PLEASE THINK OR TRY TO FIGURE THIS PROBLEM OUT

domuzy said:
even though no one seems to suffer from that problem, i must ask again-
the problem is a low volume while talking on the phone using the speaker. THEN AND ONLY THEN.
it's working perfect while playing videos, games or music. there are no complaints from the other side of the conversation. no problem while talking with headphones or w/o other devices. nothing. only on my end.
it's probably not a matter of hardware because a lab switched my speaker with another one's and mine worked perfectly on his and his didn't on mine. (same problem that is)
ALSO, i've already updated twice 7.0.1-->7.1.0-->7.1.1 and no changes.
I've already factory reseted, wiped all, cleared cache and data, and did everything i could think of, but burning the damn thing.
the ONLY conclusion i got to (me and the lab) is that there's a code or other software glitch that limits the volume.
PLEASE THINK OR TRY TO FIGURE THIS PROBLEM OUT
Click to expand...
Click to collapse
Did you try and run the phone in safe mode to rule out a third party app causing the problem? If that makes no difference you could either do a clean install of the latest Android image or if the phone is under warranty try and contact Google or Huawei for support.

didn't try safe mode. will try now. already contacted huawei, no response yet
jhs39 said:
Did you try and run the phone in safe mode to rule out a third party app causing the problem? If that makes no difference you could either do a clean install of the latest Android image or if the phone is under warranty try and contact Google or Huawei for support.
Click to expand...
Click to collapse
THANK YOU

nooooooooo
jhs39 said:
Did you try and run the phone in safe mode to rule out a third party app causing the problem? If that makes no difference you could either do a clean install of the latest Android image or if the phone is under warranty try and contact Google or Huawei for support.
Click to expand...
Click to collapse
unfortunately, safe mode didn't help, so it's probably not an app that blocks it.
is there a good confirmed link to a guide of a clean install?
my 6p is not rooted, if it matters

WiFi static noise/buzzing sound

Hi, when WiFi is enabled (doesn't matter if connected to a wireless network or not) I can hear from the top of the phone static noise probably due to interference, this is very annoying during calls. When I turn off WiFi this strange noise disappear.
I think this isn't so normal. Has anyone run into the same issue?*

Send phone back to OnePlus, they should give you a new one.

Same with me. But is barely noticeable!

I'm experiencing this on Wifi and on cellular data as well. It's actually very annoying. Does anyone know why this could be happening? Is this like a warranty thing? Or. I have no idea how to approach this sort of thing.

It happened to me too one time. but it went away after a second update. No issue there. Happens to a lot of phones. Nexusline and even iPhones have it.

xgerryx said:
I'm experiencing this on Wifi and on cellular data as well. It's actually very annoying. Does anyone know why this could be happening? Is this like a warranty thing? Or. I have no idea how to approach this sort of thing.
Click to expand...
Click to collapse
It seems completely fixed with last update (4.5.3). Try and let me know.

einermusstot said:
It happened to me too one time. but it went away after a second update. No issue there. Happens to a lot of phones. Nexusline and even iPhones have it.
Click to expand...
Click to collapse
I'm on 4.5.3 now and no change at all. Never have experienced this before and this is my like, 10th Android phone.

xgerryx said:
I'm on 4.5.3 now and no change at all. Never have experienced this before and this is my like, 10th Android phone.
Click to expand...
Click to collapse
maybe it depends on more than just your wifi, there could be many interference signals. I dunno, I am not a developer.

xgerryx said:
I'm on 4.5.3 now and no change at all. Never have experienced this before and this is my like, 10th Android phone.
Click to expand...
Click to collapse
The unusual thing for me is that the issue disappeared and came back 2 or 3 times from Friday to today.

capitanouncino said:
The unusual thing for me is that the issue disappeared and came back 2 or 3 times from Friday to today.
Click to expand...
Click to collapse
I was finding that when I moved my head away or pushed the phone against my ear that the frequency of the sound would change too. Kind of like it was reacting to the distance. It could have also been that the tone changed since I was at different distances. I don't even have enough posts to submit a bug report on the OP forums. Can someone go do that? Maybe this is a warranty item. I saw nothing at all there about this issue when I scrolled through 10 pages of other things.

In have the same issue, on wifi and cellular data. It's not that annoying, but still.. Hope this can be fixed with an update.

OP5 brand new mobile creates buzzing sound
really i am also facing this buzzing issue at the receiver ...i have tried in safe mode also *#808# but no use the same buzzing sound comes ...... not continuous , but often which irritates and annoys me ..

The 4.5.5 update fixed my issue. Hopefully it does for everyone else. I will report back here if it happens again.