Ok, i spend alot of time on this forum and its the most informative one on the internet. But, i haven't been able to find a solution to the problem that i've had for a year and 2 phones later. When i receive an incoming call and i push either the green button or the answer soft key, the call gets rejected. My carrier is t-mobile and the 1st dash that i bought started doing it about a month after i got the phone. I kept dealing with the inconvenience, then it started to do it about 3 to 4 times a day. I sent the phone back under warranty and got a refurbed one. Didn't do it for about a month then back to same old same old. Thats when i started to read this forum and discovered there were other versions of windows to install. So, i installed Ricky's rom (which is great) and didn't have the problem for another 2 or 3 months. I thought the problem was fixed until yesterday, it happened again about 4 times with a full signal. I made sure that the "disable reject call registry edit" was turned off when i first in stalled Ricky's rom. I can't figure it out for the life of me what the issue is (carrier, radio, other people's phones lol), I rarely ask for help because everything on this forum is very helpful and easy to find solutions to, except this. Please help.
No offense at all, but is sounds like you are "hard" on phones. From what you describe it sounds like you have been pushing the keys hard, and now they are worn out. Maybe not, but you had a Dash, it worked fine, then it broke within a month, then you gotta new one, then IT broke within a month, the common denominator here is YOU. So, I would try to be more careful with my phone, other than that, just get T-Mo to send you a new one forever. They will, if your phone doesn't work. That's how they are.
I don't think its the button because it works fine when i call somebody. Its only on the incoming calls. Can't figure it out for the life of me. When I got the refurbed phone it did it until i installed Ricky's rom. then it went away for about a month. Could it be my sim? Or maybe even the network? It gets progressively worse over. Check out this web page about the same problem.
http://metroplexdirectory.com/blog/archives/113
This guy had the same problem as me except, I had the problem with both WM5 and WM6. Go figure, might be time for a blackberry.
hello all...
i'm looking for some help. a couple of days ago my VZ's GNex speaker stopped working. it occured on my way home. my son was watching a cartoon on YouTube and the audio was streaming through my cars head unit via BT. everything was fine. when i turned the car off...the audio didnt transfer to the speaker...as it usually does.
since then...no notification sounds...no ringtones...NOTHING!!!
my headphone jack works fine. my earpiece (for listening to calls) works fine. the phone is ok...except for the speaker.
i am on CM9 running Francos Kernel.
i pulled the battery and rebooted. nothing. i relouded an back up (one that i knew everything was fine)...NOTHING!! i played with every single setting i know...nothing!!
my question is. is it hardware or software? and how do i find out. if its software...then maybe i can fix it...but if its hardware...i think i am going to need a new phone.
any body else encounter this problem? any fixes??
thanks!
so a quick update:
i started all over...went back to 4.02 using the GNex ToolKit...NOTHING!!!
speaker is still not working!!!
so i guess i'm going to head into a VZ store today...
alright...so here is my final status.
i called VZ last night and explain the situation. they transferred me to Asurion, who basically didnt do anything for me. except try to get 100 bucks from me to get a replacement. so after 30mins of a heated conversation...they basically said...we cant do anything...so go talk to VZ.
so i called VZ...and they transferred to Tech Support. and after a 30 second conversation (with the best tech support guy EVER!!) he said...we'll be sending you a replacement phone. should be here tomorrow.
i know that doesnt fix the issue...but i guess its a manufacturer defect...
long story short...i'm getting a new phone tomorrow to fix my speaker issue...
For the last two days I have experienced a faint ringing noise coming from my ear piece. The ring sounds like the phone is ringing but there is nothing that is running or any notifications. I experienced this once on my HTC evo LTE on sprint when I was still with them. The only way to get the noise to stop is to either reset the phone or make a call. It happens at random times. I have searched the Web for answers but got nothing. Anyone experiencing this or know of a fix?
Sent from my HTC One
Maybe you are going insane?
GrayTheWolf said:
Maybe you are going insane?
Click to expand...
Click to collapse
Ha this could be an explanation, but I have read where other HTC ones on Verizon are experiencing this. I also had the one on sprint and never had this problem.
Sent from my HTC One
I experienced the same thing sans ear piece a couple of weeks back. A reset was the only thing I could find to get rid of it for me and it hasn't seemed to come back. I was riding passenger in an unfamiliar car about a week after I had just started using my one and took a good 15 minutes trying to hunt down the sound haha.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
I had the exact thing happen to me a couple of nights ago. I thought maybe it was caused from being on the charger. I had to restart the phone to get it to stop and haven't heard it since.
Check that the roaming notification is turned off and also check for data notifications. Fixed mine.
Sent from my HTC6500LVW using Tapatalk 2
Turned both of them off as soon as I bought the phoen
Sent from my HTC One
I've noticed mine would do it in a low service area. It eventually quit doing it.
Sent from my HTC6500LVW using Tapatalk 2
I have this problem at least once a day while at work. I've talked to Verizon and HTC over this and each time they act like they've never heard of this problem. It looks like we have narrowed it down to low signal and either trying to connect to a certain band or switching between bands. You can get the ringing to stop by switching your phone to gsm only. I have the app LTE on/off and it has been said that disabling EvDo utilizing only LTE/CDMA resolves the problem. That basically disables your 3G coverage. I will be testing it out this upcoming week.
My one did this when I got a robo call. When I answered the ringing started
Sent from my SCH-I925 using xda premium
Me too + solution
Mine does this too (or at least I believe it's the same thing) seemingly at random. My simple fix is to place a phone call, even to just voicemail, and it goes away right away.
It also must be hardware-related because it would even ring faintly for like 10 seconds after I turned off my One completely. It would then immediately startup when I pressed the power button even without holding it to turn the phone back one.
As a funny side note, I literally spent nearly an hour searching for the noise in my house and wondering why it seemed to be coming from every direction and following me
Only happened to me once though since I've gotten the phone.
bericp1 said:
Mine does this too (or at least I believe it's the same thing) seemingly at random. My simple fix is to place a phone call, even to just voicemail, and it goes away right away.
It also must be hardware-related because it would even ring faintly for like 10 seconds after I turned off my One completely. It would then immediately startup when I pressed the power button even without holding it to turn the phone back one.
As a funny side note, I literally spent nearly an hour searching for the noise in my house and wondering why it seemed to be coming from every direction and following me
Only happened to me once though since I've gotten the phone.
Click to expand...
Click to collapse
If you didn't have fastboot turned off when you restarted the ringing won't stop, your phone doesn't fully shut down on a restart with fastboot enabled.
Took mine back to Verizon and I was outside of my 14 days but they still gave me a brand new one. Went through about three of them getting one without gaps and a good camera. Woke of this morning and this one was ringing too. I am in low service area part of my house where I sleep.
Sent from my HTC6500LVW using Tapatalk 4
I just got off the phone with HTC and they have started tracking this problem. They asked for the location that it occurs, the MEID #, software version, and baseband #. I would advice everyone who has the problem to call HTC and report it. The more people who call to complain may speed up the resolution to this problem.
if you search for this issue with the DNA it happened with that also.
I reported it on the 3rd day the phone was out. I was driving and using it for Navagation, Pandora, and making a call (My phone didn't like me for a while when I was testing its limits) and it started making the beeping noise.
I agree it appears to either be a low service area (Since I was driving cross country) or the other thing DNA users said is it may be the internal battery temp warning, as mine was blazing hot (Obviously)
The annoying thing about this ringing is that it goes through bluetooth audio. so within pandora you could hear the ringing. A phone call didn't solve it for me. I had to turn off fast boot and shut down for 5 minutes and boot back up.
I'm thinking it has to do with low signal or switch between bands. Everytime it happens I am in the same part of my house where I fluctuate from 3g to 1x to no signal without even moving. My phone was not even being used any of the times it Happened, so I'm not thinking it is a temp issue
Sent from my HTC ONE
teamrealtree said:
I'm thinking it has to do with low signal or switch between bands. Everytime it happens I am in the same part of my house where I fluctuate from 3g to 1x to no signal without even moving. My phone was not even being used any of the times it Happened, so I'm not thinking it is a temp issue
Sent from my HTC ONE
Click to expand...
Click to collapse
that wouldn't surprise me. I am very disappointed with the reception of this phone. I've had sms failures, and dropped calls. Signal seems worse than my note 2. My rezound and kids dna's work great at my house, so this is disappointing. My only guess is that the aluminum body is blocking the antenna.
Bought this on edge and am past my 14 days. Wonder if they would swap for the droid ultra.
nrfitchett4 said:
that wouldn't surprise me. I am very disappointed with the reception of this phone. I've had sms failures, and dropped calls. Signal seems worse than my note 2. My rezound and kids dna's work great at my house, so this is disappointing. My only guess is that the aluminum body is blocking the antenna.
Bought this on edge and am past my 14 days. Wonder if they would swap for the droid ultra.
Click to expand...
Click to collapse
My reception is on par with my dads S4 and my moms droid mini. We just live in an area where any kind of cell service is spotty.
Sent from my HTC ONE
HTC is aware of the problem
It's happened to me 3 times in the few weeks I've owned the phone. Spoke with Verizon & they spoke with HTC and told me that they are aware of the issue and looking into a fix. Who knows how long that'll take. For now we're stuck rebooting. Not necessarily a bad thing to reboot every once in a while, tho it'd be nice it I could pick when that time is.....
I can also verify that fiddling with the roaming options doesn't help.
Sure would be nice to be able to install some custom ROMs on this thing. I bet that'd fix it.....If it weren't for my unlimited data plan and the network coverage, I'd be with a carrier that didn't lock **** down so hard.
teamrealtree said:
For the last two days I have experienced a faint ringing noise coming from my ear piece. The ring sounds like the phone is ringing but there is nothing that is running or any notifications. I experienced this once on my HTC evo LTE on sprint when I was still with them. The only way to get the noise to stop is to either reset the phone or make a call. It happens at random times. I have searched the Web for answers but got nothing. Anyone experiencing this or know of a fix?
Sent from my HTC One
Click to expand...
Click to collapse
I've ran into it twice. Happened when I was sleeping once and I woke up and went insane trying to find it. I then figured out it was my phone. Weirdest part about it was the fact that it "Pulsed" so it was hard to find.
This is driving me crazy. I bought the LG G3 about two months ago and a month in i dropped it and the screen broke. I had to wait three weeks for them to repair it because they ****ed up and I just got it back today and behold, I can't hear when people call me. They can hear me and I can hear them on both speaker and with headsets. There is no buzzing or anything like that, just no audio. The speakers work fine with everything else.
Before you answer, No, it's not on mute, yes I checked all the settings to make sure everything was like it should be and I even reset it to factory settings. Please help someone, i'm pissed of to no end and I would love whoever helped me fix this. I really dont feel like waiting another three god damn weeks for my phone back seeing how I've had it for not even a day now.
hundur1995 said:
This is driving me crazy. I bought the LG G3 about two months ago and a month in i dropped it and the screen broke. I had to wait three weeks for them to repair it because they ****ed up and I just got it back today and behold, I can't hear when people call me. They can hear me and I can hear them on both speaker and with headsets. There is no buzzing or anything like that, just no audio. The speakers work fine with everything else.
Before you answer, No, it's not on mute, yes I checked all the settings to make sure everything was like it should be and I even reset it to factory settings. Please help someone, i'm pissed of to no end and I would love whoever helped me fix this. I really dont feel like waiting another three god damn weeks for my phone back seeing how I've had it for not even a day now.
Click to expand...
Click to collapse
I had the same problem. Never dropped mine though. On hindsight, I recall a few people stating I was difficult to hear and vice versa up to a week before I ran into the same thing as you. Suddenly (as of last Friday, I lost all audio through the earpiece (speakerphone and BT were all that worked). I went in to a TMO store Friday afternoon and am happy to say I got my warranty replacement this afternoon. So far all is OK.
The whole thing was really disappointing. I had just gotten the phone as of 8/12
I'm pretty sure it's a well-known fact that the bottom speaker on the pixel 2 XL Buzz's in a lot of circumstances. In my case it's whenever I listen to voicemail or turn any video or notifications up past 50%.
Has anybody heard anything about Google acknowledging this and finding a fix?
This is a definite design flaw probably software-based because the volumes aren't balanced between the two speakers and I hate that nothing is being done about it.
i RMA'd
i RMA'd my device 3 days ago (sent it back for a new one) becasue of this and hopefully the next one i get dosnt have this problem.
ewaite21 said:
i RMA'd my device 3 days ago (sent it back for a new one) becasue of this and hopefully the next one i get dosnt have this problem.
Click to expand...
Click to collapse
I'm on my third RMA. The last one I got was manufactured in January 2018 and it still has the same issue.
Sent from my Pixel 2 XL using Tapatalk
I don't know man I'm on my 6th device because of speaker issues. Two RMA's I got had dead pixels so those just went straight back to Google. I had ones with decent speaker max speaker phone call with next to no distortion but one of the speakers went out that has a build date of dec. The most recent dead pixel replacement was built in late dec and the speaker sounded like ****. I just got a new replacement from Google and the device was from the first batch of phones. Guess they really didn't sell that many black ones vs the panda. Anyways no dead pixels, some blue shift (like every single one) and the speaker sounds like absolute **** on calls after 50%. Not sure if I want to put up with this rubbish or not anymore. They know it's an issue and are gladly RMAing for it apparently. But you figure it's probably a software fix that they would push it out right away. It's already coming up on the 5th month since the launch. There hasn't been any official announcement from Google regarding the fix yet.