The speaker on my fuze doesn't really work unless I sometimes tap it lightly, and even then it crackles. it started happening suddenly a few days ago. its really annoying because I can't hear incoming calls anymore, and the speakerphone feature doesn't work either. I'm using NATF's 3.4 ROM, and have been since it came out, but this only started suddenly. I've noticed a small "popping" noise ever time I get an incoming text/call/ or some type of incoming signal.
I think its obvious that this is a hardware problem. If I remember correctly, I think HTC devices come with a 1 year manufactuer's warrenty. Maybe I can make use of it?
Would I also have to unflash the phone and bring it to factory settings?
bump? can someone please give me some advice?
same problem...
speaker
Same problem, speaker stops working then works.
same problem, Mine finally went out all together, and I can only hear it when my ear is RIGHT NEXT TO THE SPEAKER....its very low...I need to go ahead and try to get a warranty replacement.
I suggest contacting ATT ASAP. even if you didn't purchase a replacement plan, HTC provides a warrenty for a certain amount of days. As long as your phone isn't otherwise damaged you can send it back
I did it, and got a newphone in about 4 days (though you can get expedited shipping for $12)
So while I was impaired, I managed to drop my skyrocket in a toilet about a month ago. Fished it out, dried it off for a couple days, thought it was fine when the radios started working again. First time I actually used if for a call after that the speaker seemed scratchy, so I just started using my work cell for voice calls because I didn't have the time to deal with it.
I finally looked at it again today, and from what I can tell neither the speaker nor the microphone work anymore, and I can't use headphones with it either. Bluetooth does work though, so if I really need to make a call on it, I can go out to my car and call from there... /o\
Edit: I just tested with the youtube and voice recorder apps, and they work fine. So it's something wrong with the phone app? I'm now really confused, since I was leaning toward it being a hardware issue, but that doesn't seem to be the case.
I called AT&T technical support and said I "dropped" it. They said that dropping voids the warranty anyway, and suggested a factory reset. Still no dice, so now I'm looking to the internet. Any suggestions?
its no doubt because you dropped it into water. If it powers on fine try taking it apart and giving it a good cleaning. Maybe corrosion somewhere. IDK, but thats what I would do
If this just happened I would have suggested using the rice trick, but seeing as how it was so long ago, im not really sure.
I've had my Skyrocket (I727-R) for little over a year now. Bought it used. For the first seven or so months everything seemed to work fine. I had no issues and was flashing ROMs fine. Around November last year, I attempted listening to music only to realize that I couldn't hear anything from my earbuds. At first I thought it may have been my crappy old earbuds so I tried playing music without the earbuds and making a call. The other side could hear me but I could not hear anything. Since then, I've taken it back to the place I bought it from and they have been co-operative. Usually they charge for diagnostics and such but since I was a recurring customer they did it for free. Anyways, at first, it seemed like they had fixed it by replacing the speaker. They also wiped my SD, flashed the phone back to GB and told me not to root or update the software. I didn't see why it would be an issue however so I used Odin to update to stock JB and root, flashed some ROMs, etc. The audio worked for a day and stopped again while listening to music the next day. I took it back to them and they said it was a motherboard defect and would cost as much as a new phone to replace the motherboard.
I am currently running Dirty Unicorns 4.4.2, 20140331-0105, radio is T989UVMC6 (I'm on Mobilicity's network)
My question is, is there anyway I can be 100% sure it is a motherboard issue? And if it isn't, how can i fix the audio? If it is in fact the motherboard, what is the recommended course of action?
Thanks.
Right! Samsung S8+ owners,
Has anyone experienced this issue, so I receive a phone call and place the call on loudspeaker but the phone decides after awhile it wants now not to be on speaker and goes back to earpiece. This is with the screen locked I will be talking and the next minute I can’t here the person as it’s reverted back to earpiece, it is very strange. I visited Samsung last week with an issue and they flashed my phone apparently.... I think all they did was click factory reset. I was told to come back if still facing the issue and since they got there hands on it the device now does this.
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
Yes and it is quite irritating.
Hi, I have exactly the same problem.
Do you have a case on the phone? Perhaps it's detecting that you are in dock mode? Just throwing some things out there since it does not seem to be widespread.
squareballz said:
I'm having this issue, it defaults to loudspeaker 70% of the time, incoming and outgoing calls.
I need to tap the loudspeaker icon twice to disable it.
Factory reset done, clear Phone app cache done, reinstall updates on phone app done.
still no fix.
anyone having this issue as well?
Click to expand...
Click to collapse
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.
bakemcbride21 said:
I thought I was going crazy when I picked up a call it was super loud prior to putting it to my ear lol I have no case nor screen protector so this is a legit bug.
Interesting....just applied March update. I'll see if this remedies it.
Click to expand...
Click to collapse
March update did not fix it. It's getting really annoying
Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app
I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.
bobby janow said:
Time for an RMA. This can't be software related since very few are seeing it. Could be hardware so a different unit is in order. Good luck.
Sent from my Pixel 2 using XDA-Developers Legacy app
Click to expand...
Click to collapse
RMA time??? Not on Verizon lol I don't use my phone to talk enough to justify getting an unlockable phone on RMA.
I'll deal with the occasional speakerphone pickup for the $50 I paid for the phone (well work paid) and having it unlocked/rooted etc
jascolli said:
I'll bet this is happening to more people than we think. Very rarely do I chime in, I'm usually a lurker. But I figure I better say something because this problem has already happened to me twice today. It is really really frustrating. Especially for a device as expensive as this one.
Click to expand...
Click to collapse
I'll bet it's not. The device has been out 6 months and I see 4 users with the problem out of thousands out there. If you don't want to RMA then there is no reason to complain especially if you paid 50 bucks. That's why they do RMA for instances like this. Manufacturing flaws happen, deal with it or replace the device
'nuff said.
Sent from my Pixel 2 using XDA-Developers Legacy app
Guys, I think I found out what's causing this to happen.
The 3.5 audio adapter.
I did not plug in the adapter for 2 days, and the phone did not default to loudspeaker during phone calls.
But last night I plugged in and listen to music, after unplugging, the phone all go into loudspeaker again when phone calls are made/received. Restart the phone and now it never happened.
Gonna monitor few more days and update here.
OK, it is confirmed after using the audio adapter, the phone will definitely switched to loudspeaker mode during phone calls on default , it happens randomly and i would say 70 percent of the time.
its been the 5th day i did not plug in the audio adapter , all my phone calls are not defaulted to loudspeaker, and worked flawlessly.
Google team if you're seeing this, please make a fix to it!
I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.
miamistevie said:
I've had this issue a few times and I've never used the audio adapter. I did send Google feedback about it through the settings menu a couple of months ago, but I've never heard back from them. It's been a while since I've experienced this issue and for sure it's annoying when it happens. I thought it happened because of a previous phone call loudspeaker state. If you had the loudspeaker on on a previous call then the next call would also have the loudspeaker on when it shouldn't.
Click to expand...
Click to collapse
I still use the loudspeaker during phone calls, but at the next call, the phone does not default to loudspeaker.
I have been having two problems with my Pixel 2:
1) i cannot use a headset all the time for phone calls. I have to reboot the phone first then it's ok. I don't use the phone enough to have determined what has been done beforehand to cause this.
2) Sometimes the phone defaults to speaker phone for a phone call. Rebooting fixed it. I did use the headset the other day and then the past 2 calls were on speaker phone and tapping the speaker button did not change the setting.