Related
I got my Rezound right after Black Friday, and have had it about 6 days.
My fiance and her dad both complain that my voice sometimes goes in and out for a bit sometimes, making it hard to hear me, or not hearing me at all. At the same location I wipe out my incredible and it does fine, for a phone call that last 2 hours. This has happened quite a few times.
This isnt isolated to just my apartment, it happens everywhere i guess. I have an HTC Incredible that never gives me this issue.
I've pulled the battery, did a factor reset, did a prl update, but nothing seems to fix the problem. And of course the problem isnt consistent since it happens whenever it wants.
I noticed the phone also has a mic on the back, so I have tried to hold the phone differently to see if thats an issue, but the problem still happens.
Anyone else with the same issue? Amazon said they would just ship me another phone. I guess I will chalk this up to a hardware issue.
That was pretty much the only issue i've had, so I'm praying that the one they send isnt one having some of the other issues i've been reading about.
Could just be a faulty phone. But I have seen a review state that it happened to him too, could just be a bad batch. You never want to do a PRL update with 4G phones, *228 is not necessary for these devices. Also by doing *228 on a 4G device, you have a chance of frying your SIM chip. I'd say give the new device a shot and see what happens and if it still cuts out or not. If it still does then it could just be the device needs an update from HTC. I personally have not had this issue happen to me. Hope it works out for you.
I'm really not trying to offend and it sounds like you have tried to deal with this issue already BUT...
Is it possible you could still occasionally be covering up the main mic on the bottom of the phone while holding it? I use my pinky finger on the bottom of the phone to help support it/hold it up and have now had to train myself to be careful not to cover the mic on the bottom of the phone (on my OG Droid it was on the front face of the phone). You may have a real hardware issue with your phone, but maybe do a test where you cover it up on a call to the same people that had trouble hearing you before and ask them if it sounds similar?
Good luck!
Thanks
zetsumeikuro said:
Could just be a faulty phone. But I have seen a review state that it happened to him too, could just be a bad batch. You never want to do a PRL update with 4G phones, *228 is not necessary for these devices. Also by doing *228 on a 4G device, you have a chance of frying your SIM chip. I'd say give the new device a shot and see what happens and if it still cuts out or not. If it still does then it could just be the device needs an update from HTC. I personally have not had this issue happen to me. Hope it works out for you.
Click to expand...
Click to collapse
You have seen a review that had a posssible bad phone that had problems with his voice being heard too? Do you by chance iknow where I can view that review?
Either way, thanks for the info, and tip on *228. I plan on trying the new device and hopefully it goes well.
Thank you.
Hmmmm
derekisthematrix said:
I'm really not trying to offend and it sounds like you have tried to deal with this issue already BUT...
Is it possible you could still occasionally be covering up the main mic on the bottom of the phone while holding it? I use my pinky finger on the bottom of the phone to help support it/hold it up and have now had to train myself to be careful not to cover the mic on the bottom of the phone (on my OG Droid it was on the front face of the phone). You may have a real hardware issue with your phone, but maybe do a test where you cover it up on a call to the same people that had trouble hearing you before and ask them if it sounds similar?
Good luck!
Click to expand...
Click to collapse
Not offended at all. You know I thought that too, so I started watching how I held it. I tried holding it different and nothing changed. The bottom mic im used to since I believe the Incredible had one in the same location.
I also tried to keep my hand somewhat off the microphone on the back also.
I tried covering up mics and was unable to decide if that was the issue. The replacement will be here in 2 days, so i play to play with this one some more till then.
You brought up a good point though, and something that I have been keeping my eye on.
Thanks.
dccoh said:
You have seen a review that had a posssible bad phone that had problems with his voice being heard too? Do you by chance iknow where I can view that review?
Either way, thanks for the info, and tip on *228. I plan on trying the new device and hopefully it goes well.
Thank you.
Click to expand...
Click to collapse
http://www.theverge.com/2011/11/14/2557172/htc-rezound-review is where I saw the comment about the calls. No problem! Hope the 2nd phone doesn't have this issue for you.
I've also had a complaint about this, its only been from one person though. And he as commented on it sounding like I was muffled and he will interrupt and ask how I'm holding it, I was holding the phone normally and not destructively each time :-\ he hasn't said anything about it in a few days though, idk if its the phone or the network lol :-\ but... Ive also had this issue, I'm kind of scared to get another one because of all the other issues some people are having with them.
Edit: also I tried to catch it happening by recording audio for about an hour with my phone in front of the TV and it never happened. So idk :-\
Sent from my ADR6425LVW using Tapatalk
My girlfriend has also began complaining about this.
The only possible explanation I can work up is that I've noticed it happens when my mouth isn't close and directly in front of the mic. So maybe the noise cancelling mic's on the back of the phone are picking up my voice also and therefore cancelling them out.
got556 said:
My girlfriend has also began complaining about this.
The only possible explanation I can work up is that I've noticed it happens when my mouth isn't close and directly in front of the mic. So maybe the noise cancelling mic's on the back of the phone are picking up my voice also and therefore cancelling them out.
Click to expand...
Click to collapse
I also think the same tbh... I'm thinking that one gets too sensitive possibly, because I've been told it happens, when I notice that I talk louder or closer to the mic. And it doesn't do it all the time. Its very limited and random, I think its only happened like 3 or 4 times total, since I've had it... I wonder if it is the noise canceling being too sensitive. I bet a software update would fix it.
I was thinking that If it was the mic messing up it would happen more often. but I made a post about it I think a week or so ago, glad I'm not crazy though :-D
Edit: err.. I just realized my otterbox commuter case covers those back mics. I have a whole in the side at the top where that one is though. I suppose I could be touching that one some how, but what does that one even do lol?
Sent from my ADR6425LVW using Tapatalk
got556 said:
My girlfriend has also began complaining about this.
The only possible explanation I can work up is that I've noticed it happens when my mouth isn't close and directly in front of the mic. So maybe the noise cancelling mic's on the back of the phone are picking up my voice also and therefore cancelling them out.
Click to expand...
Click to collapse
Well at least i'm not alone. Her dad complained about it first, then she did. I've never had this kind of issue, so I assumed it was there phone.
I even called my third's line google voice number and recorded myself walking around talking on the phone, to myself. I'm sure the neighbors might think i'm nuts at this point.
I listened to the recording, and I didnt hear any issues. *sigh* Well, if its how i'm talking into the phone, I don't know what to do about that. I've been talking on the rezound like I have every cell phone that i've ever owned.
I dont 'death grip' the phone, and I hold it like normal. Would hate to think I'd have to baby how I hold the rezound, but eh, anything can happen.
If my next phone does this, I guess I have to decide if I have to listen to her complain, or get a different phone (unless I write HTC and see if they have a fix on the horizon software wise). Bad thing is there is no other phone close to the Rezound right now.
I don't want to deal with a Razr right now, with having a non replaceable battery (by normal means), plus i'm not into motorola.
The holes on the back are NOT mics.
The mic is on the side. Those holes are antenna traces.
eallan said:
The holes on the back are NOT mics.
The mic is on the side. Those holes are antenna traces.
Click to expand...
Click to collapse
Hehe gud to know. I probably cover it or hit it a lot when talking hmmm ill have to experiment further
Sent from my ADR6425LVW using Tapatalk
zetsumeikuro said:
Could just be a faulty phone. But I have seen a review state that it happened to him too, could just be a bad batch. You never want to do a PRL update with 4G phones, *228 is not necessary for these devices. Also by doing *228 on a 4G device, you have a chance of frying your SIM chip. I'd say give the new device a shot and see what happens and if it still cuts out or not. If it still does then it could just be the device needs an update from HTC. I personally have not had this issue happen to me. Hope it works out for you.
Click to expand...
Click to collapse
Funny story: The day I got my phone I put it together, turned it on, did initial setup, and out of habit from flashing Dinc ROMS every other day for the last year I immediately did a *22899 and it popped up some message basically saying "don't do this" so I'm not even sure it will let you "fry" your SIM chip by doing the update.
hey guys
my galaxy s2 has been on the fritz with the power cord recently. it thinks its plugged in when it isnt and i cant use usb mode
any help?
much, much appreciated.
yashimototumah said:
hey guys
my galaxy s2 has been on the fritz with the power cord recently. it thinks its plugged in when it isnt and i cant use usb mode
any help?
much, much appreciated.
Click to expand...
Click to collapse
ruh roh. Did this behavior just start on its own randomly? Sounds very similar to what mine was doing due to a failed USB port. I think there is at least one, maybe a couple more, other users on the forums here who also experienced USB port hardware failure. ended up doing a warranty replacement for mine.
Sent from my SGH-I777 using XDA App
Ya it completely started happening on its own.
Definitely seems to be the usb port.
Thanks for the heads up, gonna be contacting att in the morning
yashimototumah said:
Ya it completely started happening on its own.
Definitely seems to be the usb port.
Thanks for the heads up, gonna be contacting att in the morning
Click to expand...
Click to collapse
Yea that's a common problem. USB port defect.
Sent from my A500 using xda premium
I've already brought back 2 of these because of the same exact problem. I'm really starting to think it's because there is no cover/door over the USB port. Loved the slider on the cappy. Need a case that covers the port
Sent from my SAMSUNG-SGH-I777 using XDA App
There's a few threads on this. I personally started one. Best thing to do is just take it back to att.
Sent from my SAMSUNG-SGH-I777 using xda premium
Cdub5 said:
I've already brought back 2 of these because of the same exact problem. I'm really starting to think it's because there is no cover/door over the USB port. Loved the slider on the cappy. Need a case that covers the port
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
While I certainly can't argue that covering the USB port is a bad thing, I carried an HTC aria (same port location, same type of case, same pocket) in a construction environment for more than a year with no USB port problems. While it certainly could be caused by lack of protection (pocket lint was my first thought when mine happened) I suspect a bad batch of Ports made it into the assembly line, due to the number of reports I've seen here. My bad one was purchased on launch day - anyone else have one go bad on a significantly more recent purchase?
Sent from my SGH-I777 using XDA App
Mine was doing the same thing, as well as going into "car mode" randomly and freezing up completely. I found a thread that suggested swabbing out the port with rubbing alcohol and a small paint brush. I did that and it cured the problem, but I also bought a case that covers the usb port (otterbox).
This all went down about three weeks ago and it hasn't happened since.
Racer447 said:
Mine was doing the same thing, as well as going into "car mode" randomly and freezing up completely. I found a thread that suggested swabbing out the port with rubbing alcohol and a small paint brush. I did that and it cured the problem, but I also bought a case that covers the usb port (otterbox).
This all went down about three weeks ago and it hasn't happened since.
Click to expand...
Click to collapse
Wow, good to know...I was getting the car mode deal too. I'll be keeping this in mind for post-warranty issues. Thanks.
Sent from my SGH-I777 using XDA App
Seems like a common problem from a specific batch of them, so shouldn't be an issue to get a replacement.
Good luck!
Sent from my SGH-I777 using xda premium
dandrumheller said:
While I certainly can't argue that covering the USB port is a bad thing, I carried an HTC aria (same port location, same type of case, same pocket) in a construction environment for more than a year with no USB port problems. While it certainly could be caused by lack of protection (pocket lint was my first thought when mine happened) I suspect a bad batch of Ports made it into the assembly line, due to the number of reports I've seen here. My bad one was purchased on launch day - anyone else have one go bad on a significantly more recent purchase?
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Got my first one on black Friday, second one two weeks later, third one, a week or so after that. First two were a 1108, and 1110 builds from what I recall. Not sure what my latest build is, but I got this one at a different best buy (first two from the same best buy) so hopefully if it was a bad batch it won't happen to me with this new one. Knock on wood. This time I got best buy insurance. Seems good, $9.99 a month, no copay for replacement.
Sent from my SAMSUNG-SGH-I777 using XDA App
same usb problems
I am having some of the same problems. My phone thinks it is always charging, the fully charged notification is almost always up, and my computer cannot recognize the phone. I would send my phone in for a replacement, however the water indicator sticker is red (it got slightly wet).
Does anyone have any idea on what to do. Has anyone else had the rubbing alcohol method work?
I just went through this same issue, but I managed to fix mine on my own. I don't have the phone insurance through ATT, and the overseas warranty support center did everything that they could to deny service. Every time that I would call, they would repeat the steps that we had already been through in troubleshooting. I knew from reading here and other sites that the usb connector, or usb board was my problem. I started out cleaning it with alcohol and that seemed to help a little bit. The ultimate answer was to bend the pins in the middle of the USB connector in the direction of my screen, just a little bit. I have been three months now with no problem whatsoever. I didn't tell ATT that I did this, but I wanted to get a new phone, thinking that this fix would eventually cause the port to break altogether.
This ordeal was extremely frustrating for me, because I have been into phone hacks/flashing roms since the WinMo days. They tried to tell me on one of the calls that they had pushed an update to my phone that would fix it. I promptly told the lady on the phone that she was full of @#$#, as I knew the phone had obviously not been flashed or updated by her text message. She finally backpedaled and admitted that she was lying. It was hard to deal with this conversation without admitting what I knew about these phones. The sad fact is that at this time, my phone wasn't even rooted yet.
In the end, I did get a new, factory battery out of the deal. These idiots thought that a new battery would resolve the issue, even though I told them exactly what the problem was.
I was really pissed about the service I received. I am over an IT helpdesk for a software company. If any of my employees treated our customers like I was treated, they would be looking for work. I expect that they are just doing their jobs as supportbots, just like ATT wants them to.
I decided that if I ended up having to replace the USB board on my own dime, I was going to fix it, root it, unlock it and fleabay the thing. I was going to use the proceeds to pay the early termination fee and say goodbye to ATT forever.
I know that this was longwinded, but I have been holding this in for a while now. I posted this in one of the earlier threads, but then deleted it, thinking that I might need to reference the thread to show ATT that the USB issue was a known problem.
I don't have this issue, but a friend does. What would one do if this happened while their phone was rooted? How would you get back to stock with a dead port?
I had this issue a few weeks ago. About 100 times a day the phone would chime, thinking it had just been plugged in/unplugged. I cleaned out the USB port very well with rubbing alcohol (used a small paintbrush), as well as the internal battery contacts. I also stopped taking the phone in the bathroom while I showered, thinking that perhaps steam from the shower could be causing the problem. I'm not sure if the alcohol or keeping it out of the bathroom did it, but within a day or two the problem stopped, and hasn't repeated itself for 3 weeks or so.
candersonosu said:
I am having some of the same problems. My phone thinks it is always charging, the fully charged notification is almost always up, and my computer cannot recognize the phone. I would send my phone in for a replacement, however the water indicator sticker is red (it got slightly wet).
Does anyone have any idea on what to do. Has anyone else had the rubbing alcohol method work?
Click to expand...
Click to collapse
There was somewhere on XDA a thread on how to make the moisture indicator white again. Bleach or something i believe, Maybe someone else here knows/remembers?
L8sho said:
I just went through this same issue, but I managed to fix mine on my own. I don't have the phone insurance through ATT, and the overseas warranty support center did everything that they could to deny service. Every time that I would call, they would repeat the steps that we had already been through in troubleshooting. I knew from reading here and other sites that the usb connector, or usb board was my problem. I started out cleaning it with alcohol and that seemed to help a little bit. The ultimate answer was to bend the pins in the middle of the USB connector in the direction of my screen, just a little bit. I have been three months now with no problem whatsoever. I didn't tell ATT that I did this, but I wanted to get a new phone, thinking that this fix would eventually cause the port to break altogether.
This ordeal was extremely frustrating for me, because I have been into phone hacks/flashing roms since the WinMo days. They tried to tell me on one of the calls that they had pushed an update to my phone that would fix it. I promptly told the lady on the phone that she was full of @#$#, as I knew the phone had obviously not been flashed or updated by her text message. She finally backpedaled and admitted that she was lying. It was hard to deal with this conversation without admitting what I knew about these phones. The sad fact is that at this time, my phone wasn't even rooted yet.
In the end, I did get a new, factory battery out of the deal. These idiots thought that a new battery would resolve the issue, even though I told them exactly what the problem was.
I was really pissed about the service I received. I am over an IT helpdesk for a software company. If any of my employees treated our customers like I was treated, they would be looking for work. I expect that they are just doing their jobs as supportbots, just like ATT wants them to.
I decided that if I ended up having to replace the USB board on my own dime, I was going to fix it, root it, unlock it and fleabay the thing. I was going to use the proceeds to pay the early termination fee and say goodbye to ATT forever.
I know that this was longwinded, but I have been holding this in for a while now. I posted this in one of the earlier threads, but then deleted it, thinking that I might need to reference the thread to show ATT that the USB issue was a known problem.
Click to expand...
Click to collapse
Awesome help mate. Got me going. Alcohol, toothbrush and bending the pin up with a needle.
JeremyLeroy96 said:
I don't have this issue, but a friend does. What would one do if this happened while their phone was rooted? How would you get back to stock with a dead port?
Click to expand...
Click to collapse
I had the same issue and I manage to get to stock usingh Mobile odin, I went to the DSC or how ever is spell The repair center for att. and the guy took it tried to fix it but was no good, so he gave me a new one. And as the chatter kept going he said they would still take them even if there rooted becouse Samsung can just restore them back to stock much easier than we can. Maybe he was blowing smoke but sounded kinda true.
he said mine hjad some sort of corrosion on the USB port that made it think it was connected that's why it showed that.
I am currently having the same issue. I have an SGH-S959g, which is Straight Talk/Net 10's S II. I'm posting here because my phone is physically identical to the AT&T S II. At the suggestion of multiple forums, I've tried cleaning it out with rubbing alcohol. I even took apart the phone and cleaned the soldered connections to the logic board. There was virtually no corrosion on any of the port. I tried bending the pins slightly forward as well, because that has helped with other phones (Samsung and otherwise). None of this is solving my problem and, unfortunately, my month-to-month service means I have no option of being sent another phone. Any help would be immensely appreciated (especially if it contains a new idea or two to try).
Thanks in advance.
camkatastrophe said:
I am currently having the same issue. I have an SGH-S959g, which is Straight Talk/Net 10's S II. I'm posting here because my phone is physically identical to the AT&T S II. At the suggestion of multiple forums, I've tried cleaning it out with rubbing alcohol. I even took apart the phone and cleaned the soldered connections to the logic board. There was virtually no corrosion on any of the port. I tried bending the pins slightly forward as well, because that has helped with other phones (Samsung and otherwise). None of this is solving my problem and, unfortunately, my month-to-month service means I have no option of being sent another phone. Any help would be immensely appreciated (especially if it contains a new idea or two to try).
Thanks in advance.
Click to expand...
Click to collapse
Had same issue, fixed it with ebay item 270993875674. I can't post links so you will have to search. I bought my S2 in fall of 2011, tried a different board it did not work. The Q&A forum led me to this ebay item to fix it. It's an easy fix, takes maybe 15-20 mins if you are being ultra careful.
Hi guys I have a problem I can't seem to solve I never use Wifi as I have no need for it because I'm on unl data but I needed it today for an app well my Wifi doesn't turn on at all it says error I'm not rooted and in rocking an extended battery cover
Sent from my ADR6425LVW using XDA
Have you not tried flashing anything whatsoever and are 100% Gingerbread stock? I saw you asking about the leaked ICS builds. The WiFi "error" message is common when flashing the kernel, have to do it twice to make sure it takes it.
croonux said:
Hi guys I have a problem I can't seem to solve I never use Wifi as I have no need for it because I'm on unl data but I needed it today for an app well my Wifi doesn't turn on at all it says error I'm not rooted and in rocking an extended battery cover
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
If you are not rooted and 100% stock. then perhaps you set wifi incorrectly.
PhantasmRezound said:
Have you not tried flashing anything whatsoever and are 100% Gingerbread stock? I saw you asking about the leaked ICS builds. The WiFi "error" message is common when flashing the kernel, have to do it twice to make sure it takes it.
Click to expand...
Click to collapse
Yup 100% stock I haven't tried flashing anything at all yet But I'll probably due tonight and its not only my wifi apparently my bluetooth does not connect as well it just keep saying turning on but it doesn't actually turn on and wifi just says "error"
Hmm...
croonux said:
Yup 100% stock I haven't tried flashing anything at all yet But I'll probably due tonight and its not only my wifi apparently my bluetooth does not connect as well it just keep saying turning on but it doesn't actually turn on and wifi just says "error"
Click to expand...
Click to collapse
Very odd it would have those problems fully stock. Did you get it from an authorized seller or Verizon new, or did you get a CLN Verizon replacement or buy it secondhand from elsewhere? Could still be an issue with a bad flash by a previous owner if the latter holds true.
Well I was about to suggest running an .exe version of a Gingerbread RUU from this thread, which should correct any errors, but you'll need to back up all internal SD data and put it back on the phone memory due to wiping. And re-download all your apps and reconfigure all your customizations, etc.
And just to toss it out there, third party extended battery covers may have shoddy antennas or none at all. Suggested you check all connections against the stock backplate layout. Should still not wind up with a straight "error" message that way, though...
if the RUU tidying up the software don't fix it, that may just be straight hardware damage. Killed my WiFi and bluetooth on my iPod touch a while back with some liquid and got the same symptoms.
PhantasmRezound said:
Very odd it would have those problems fully stock. Did you get it from an authorized seller or Verizon new, or did you get a CLN Verizon replacement or buy it secondhand from elsewhere? Could still be an issue with a bad flash by a previous owner if the latter holds true.
Well I was about to suggest running an .exe version of a Gingerbread RUU from this thread, which should correct any errors, but you'll need to back up all internal SD data and put it back on the phone memory due to wiping. And re-download all your apps and reconfigure all your customizations, etc.
And just to toss it out there, third party extended battery covers may have shoddy antennas or none at all. Suggested you check all connections against the stock backplate layout. Should still not wind up with a straight "error" message that way, though...
if the RUU tidying up the software don't fix it, that may just be straight hardware damage. Killed my WiFi and bluetooth on my iPod touch a while back with some liquid and got the same symptoms.
Click to expand...
Click to collapse
thanks for all the help I pretty much did everything here before making the thread I checked the cover saw the metal made sure everything clicked compared my extended battery cover to the regular cover but everything seemed the same, tried the extended battery and regular battery but same problem no wifi connection giving me an error it's already fixed I fixed it by upgrading to the ICS leak and now i can connect to wifi no problem I was started to think it was hardware wise from a drop or something but nope it was somehow software idk how it got messed up since I was 100% stock, well thanks once again for your help and I feel you on the ipod same thing happened to me after going snowboarding, I went to mamoth and I was snowboarding and I had my ipod on one of the gazillion pockets of my jacket when I got to the cabin I was tripping out of where I left my ipod (had barely bought it) so I was looking all over the cabin untill I stuck my hand inside my open pocket and there was my ipod with a bunch of Melted ice submerged on water my headphone jack got messed up so no matter the pair of headphones I couldn't hear from one side and wifi got messed up so I fixed the ipod at apple store and I stepped on it 2 months later breaking the screen I refixed it again, and one day I was messing around with my little sister and I was holding half her body over a swimming pool and to "rescue her" my other lil sis pushed me into the pool and my ipod got messed up again and the extra casulty was my OG droid may it RIP (tried to turn it on later after putting it on rice only for it burn and the screen get foggy) after that I said F this ish and never bought an ipod again :\ and I was stuck with a crappy black berry for like 3 months before getting the rezound... wow mini essay going on here...
croonux said:
thanks for all the help I pretty much did everything here before making the thread I checked the cover saw the metal made sure everything clicked compared my extended battery cover to the regular cover but everything seemed the same, tried the extended battery and regular battery but same problem no wifi connection giving me an error it's already fixed I fixed it by upgrading to the ICS leak and now i can connect to wifi no problem I was started to think it was hardware wise from a drop or something but nope it was somehow software idk how it got messed up since I was 100% stock, well thanks once again for your help and I feel you on the ipod same thing happened to me after going snowboarding, I went to mamoth and I was snowboarding and I had my ipod on one of the gazillion pockets of my jacket when I got to the cabin I was tripping out of where I left my ipod (had barely bought it) so I was looking all over the cabin untill I stuck my hand inside my open pocket and there was my ipod with a bunch of Melted ice submerged on water my headphone jack got messed up so no matter the pair of headphones I couldn't hear from one side and wifi got messed up so I fixed the ipod at apple store and I stepped on it 2 months later breaking the screen I refixed it again, and one day I was messing around with my little sister and I was holding half her body over a swimming pool and to "rescue her" my other lil sis pushed me into the pool and my ipod got messed up again and the extra casulty was my OG droid may it RIP (tried to turn it on later after putting it on rice only for it burn and the screen get foggy) after that I said F this ish and never bought an ipod again :\ and I was stuck with a crappy black berry for like 3 months before getting the rezound... wow mini essay going on here...
Click to expand...
Click to collapse
Holy run on sentence batman
Sent from my ADR6425LVW using Tapatalk 2
nrfitchett4 said:
Holy run on sentence batman
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
ha what can i say high school didn't teach me how to write well... (true story) (now in college I need to take a specific class that teaches me how to write, :\ )
Rooted s-on amaze No audio from loudspeaker or headphone jack. Only earpiece or bluetooth make sound. Phone just went for warranty a month ago and they said they replaced the motherboard. Now I a couple weeks out of warranty and they are telling me tough luck. Lucky me... What could cause this? I have tried several different firmwares, kernels including going back to stock. No change.
Doesn't look like a common issue. I can't find any info on this that helped at all. Please help.
Just going out on a limb here, the phone's already been repaired at least once--I would suspect a bad component.
pbergonzi said:
Just going out on a limb here, the phone's already been repaired at least once--I would suspect a bad component.
Click to expand...
Click to collapse
+1
Seems like a logical diagnosis to me too. It could be anything from a bad headphone jack or speaker to a failed board component. The fact that you've had it serviced before for the same issue suggests it wasn't properly repaired the first time. Sorry, but this doesn't sound like a software issue.
Thank you for quick reply. Guess its tough s*** for me
Symptoms--did it just stop out of nowhere, or did you install something and it stopped? If it just stopped out of nowhere, go fishing around in the phone, see if there's some kinda loose cable or if the earplug assembly is loose or something. Much of troubleshooting is just discovery. Amaze are pretty affordable if you have to replace it--check craigslist or swappa. Maybe your provider will set you up with something, doesn't even have to be Amaze for you to have functionality.
I have the very same problem and this is the first thing I've seen about it. No sound from loud speaker or headphone jack. I haven't pinpointed something I installed to make it quit working, I've tried different roms, etc to see if it would work. No luck. The sound even decides to work every couple weeks for a total of maybe a minute and it stops again. If anyone discovers a solution I'm all ears. I have no warranty, I'm on T-Mobile with a no contract plan. Thanks for any help..
I am waiting on some micro torx bits to do some exploratory diagnosis. I do have an electronics/electrical background but my skills are limited in this case to monkeying with connections and perhaps some basic metering. I will post when I have done so. i have a feeling it is likely a loose/poor connection that has caused this since it has only just come back from repair and the motherboard was supposedly replaced. However, wether or not the put a NEW board in is an unknown.
In terms sysptoms and there was no audio distortion or any signs of any thing wrong at all before. This was sudden and without warning. It was not in the middle of use of the head p. jack or the loud speaker either. I had not installed any apps for at least a few days before this happened so I am inclined to not believe it is software related.
So far I am stumped we will see what happens when I do a little surgery. If the patient dies I will go by a S3...People still want 120 bucks here for their amazes.Thanks all for input.
To @the jew hunterhunter--your troubleshooting skills are similar to mine--poke around--and then some. Poking is especially is especially handy when the problems are physical.
Clever "replaced but don't know if it was new."
Good luck in your investigation.
I know the headphone jack itself can be problematic, something in the design that can allow just a tiny displacement of the plug to result in disconnection, don't know if purchasable replacements are better or not, however that is probably completely unrelated to your sound issues. Yet..., I would look at that component first.
I am glad you will post results.
To @marshallrounds, you can see from this thread that it is probably hardware, as no one else has found or mentioned any software-caused issues or fixes.
no workie
So i tried to goof with it but there was nothing I could do with my limited poking and hoping skills. Must be a bad component or some microcode glitch. Out of my hands so I bought a used nexus 4 for 190$ MUCH HAPPIER NOW nexus 4 makes the amaze look like a bad joke. Thanks to amaze ppl out there for everything tho!:good:
the jew hunter said:
So i tried to goof with it but there was nothing I could do with my limited poking and hoping skills. Must be a bad component or some microcode glitch. Out of my hands so I bought a used nexus 4 for 190$ MUCH HAPPIER NOW nexus 4 makes the amaze look like a bad joke. Thanks to amaze ppl out there for everything tho!:good:
Click to expand...
Click to collapse
There ya go.
Holla fellows, on my LG G5 I am facing a very bizarre issue. When I activate my speakers my microphone stops working. when on earpiece they work like a charm. Also microphone didn't work when used my other applications like skype or hangout, but while using earpiece they are perfectly fine. Anyone else got this issue on G5 or anyother device ? Any suggestion or advice is greatly appreciated.
I'm having the same issue. Literally just got the phone 4 days ago. Pretty happy about it. Have you reset?
jkieffer46 said:
I'm having the same issue. Literally just got the phone 4 days ago. Pretty happy about it. Have you reset?
Click to expand...
Click to collapse
Yes, I tried resetting via backup and restore under settings menu
Reset mine and thought about the mic being housed in the battery holder bottom part. Why not take it out and clean connections....mic works great now. Dunno if from reset or alcohol cleaning connections. Give it a shot.
Same here i purchased the phone on 5-5-16 it will reboot on its own almost everyday till 5-19-16 when it completly just gave up and wouldn't turn on. So i went to tmobile and they replaced it for a new one. But now the replacement gave up yesterday 5-28-16. It has managed to turned on once but the device was too hot that i turned it off to cool it down and it wont turn on anymore. Sucks that is long weekend and i wont be getting s replacement soon.
I too am having this issue, however mine has one other weird glitch. If i put the phone on speakerphone and talk into th phone like normal (phone up to my ear) i can hear myself in the phones speaker faintly and the mute button does no work at all. Works fine on normal mode but not on speakerphone. To me this is a software issue vs hardware issue, I bought the phone second hand so I dont really have any warranty. Anyone have anything to offer up to try? Ive tried a different battery module base and no luck, same issues. Its almost like the phone needs a entire reflash done to it. Other then this issue the phone rocks.
The phone is a Canadian H831 model.
I had similar issue with older device. Read on some thread and they suggest disable Google now. It worked for that device. I am not sure if it will for you guys?
Sent from my LG G5 using XDA Labs
kingzslayer said:
Holla fellows, on my LG G5 I am facing a very bizarre issue. When I activate my speakers my microphone stops working. when on earpiece they work like a charm. Also microphone didn't work when used my other applications like skype or hangout, but while using earpiece they are perfectly fine. Anyone else got this issue on G5 or anyother device ? Any suggestion or advice is greatly appreciated.
Click to expand...
Click to collapse
How are you resolve this problem? New phone from box I have some problems Model LG G5 H820 AT&T
Deleted.
I had the same problem a while ago, here's my fix, hope it helps
https://forum.xda-developers.com/lg...-mode-call-t3565646/post71243431#post71243431
Thanks for the link @marac1993 will check
I had the same problem. It turned out to be a "hardware" thing. There are two microphones, one at the bottom of the phone which works when on earpiece, and the second one on the top of the phone (above earpiece) which works when on speaker mode. I cleaned the first one several times without noticing there is a second one on the top. It turned out that the second microphone was blocked by some dirt. I cleaned it and now it works like a harm when on speaker mode.