• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Phone is Useless when the Phone Goes Silent Multiple Times a Week

Frisco said:
So it's an app (or group of like apps) causing this? I've never had the issue, but I'm startled that this has not been discovered before by those with the bug.
Click to expand...

Oh, heck no, we're just looking for easy ways to replicate the bug. It can be triggered by any app or built-in phone feature that makes sound (including notifications and ringtones). The point of using the HTC music widget to test was just that it was an easy way to play sounds without constantly sending yourself a text message, emailing, or calling.

The bug can show itself even after a factory reset, before any third-party apps are installed. One guy even got it without ever setting up a google account on the phone (there's a way to bypass the initial setup), so we even ruled out google sync as the cause of it. Now, google sync might *trigger* it, but it doesn't *cause* it.
 
puppeteer said:
According to HTC's twitter feed, the Eris 2.1 source just got posted.
Click to expand...

Yeah, it was actually posted April 30. That's why they've been able to do overclocking in the root ROMs. Not sure why they randomly decided to mention it on Twitter, except maybe they're trying to encourage developers to solve their bugs for them, free of charge. ;)
 
There's no two ways around it. They use people like us here on this forum, to leak our

phone's, then use all the feedback for free beta testing. The least they could do would

be to give the leakers the first OTA 2.1, instead of last, and that's if at all. Or allow a

way back to 1.5, or to change Hboot. Anything man!
 
I had experienced the silent treatment only a few times, and never after I installed the V3 leak - but...I used the fact that it had happened as an excuse to satisfy my OCD and get myself a fresh, officially upgraded phone - Verizon sent me one out - got it today - did the 2.1 upgrade when prompted - activated phone - and viola! On my very first incoming call, I HEARD NOTHING. I rebooted - heard nothing - factory reset - heard nothing -

Luckily, I had not reset my original phone, which was working fine on V3 - VZW sending me out another phone - I'll report in after that one arrives -
 
Jacklad said:
I had experienced the silent treatment only a few times, and never after I installed the V3 leak - but...I used the fact that it had happened as an excuse to satisfy my OCD and get myself a fresh, officially upgraded phone - Verizon sent me one out - got it today - did the 2.1 upgrade when prompted - activated phone - and viola! On my very first incoming call, I HEARD NOTHING. I rebooted - heard nothing - factory reset - heard nothing -

Luckily, I had not reset my original phone, which was working fine on V3 - VZW sending me out another phone - I'll report in after that one arrives -
Click to expand...

Hey, when you get the new one, if you wanna open up the battery door of both phones and tell me if you see any noticeable differences (besides the ESN and MEID and such), that would be awesome. If it really is an issue with the kernel not being compatible with a certain batch of hardware (which is the best guess at this point), it'd be handy to know which batch of hardware that is.
 
Faulty g sensor. Try calibration a few times. Had the same prob on v2 and after that, never happened again. Moving the phone would give me the silent bug.
 
jimigood said:
Faulty g sensor. Try calibration a few times. Had the same prob on v2 and after that, never happened again. Moving the phone would give me the silent bug.
Click to expand...

Hi jimigood, can you elaborate on that?

I'm sure I moved the phone during a call and didn't get the silent call bug more often than I moved the phone during a call and did. And I know I ran the g-sensor calibration. But what intrigues me about what you're saying is that the g-sensor calibration always failed the first time I tried it, and I always had to do it a second time. On my new phone, calibration succeeds the first time.

Also, for me the bug always showed up right after a phone call, never during. (Naturally, I usually didn't notice until I placed the next phone call.) It sounds like you're saying that it happened to you during a call (when you moved the phone).
 
I went from 1.5 to 2.1 OTA (not manual). Now I too have this issue. Happened twice in a week so far. I was on bluetooth headset when it happened. Tried to replicate it with no success. Took my excitement away for getting the 2.1. Hope someone finds a fix.

My G-sensor would not calibrate when I tried the first few times. But I could do it just now. Don't know if that makes any sense.
 
Anyone else want to try calibrating their g sensor? It's the last item under settings : sound & display. It would tell us a lot if the non-silent phones can calibrate easily and the affected phones have trouble.
 
It didn't always happen during a call. Had same issue as everyone.
The g sensor give your phone some sense of orientation. It seems in sone phones it lies, the phone thinks its in one spot and not. Another. I e tilted left or right, laying flat, or upright.
I don't know why, but it seems to confuse the phone during and before calls, especially when using blue tooth.

That's my best to offer. I do know after calibration I never saw the bug again.
 
Just tried the calibration, it worked on the first try and I've had the silent bug since v2, upgraded to v3 and still had it, maybe the calibration will solve the problem.. not holding my breath though
 
2.1 OTA here and having the same issue. Usually happens when I am placing a call. I will hear the ring once or twice then silence. Always have to do a battery pull to get it back.

Just did the calibration and it was successful on the first try.
 
Lucidot said:
2.1 OTA here and having the same issue. Usually happens when I am placing a call. I will hear the ring once or twice then silence. Always have to do a battery pull to get it back.

Just did the calibration and it was successful on the first try.
Click to expand...

So there goes that theory. Still, the goal here should be to find a reliable way to replicate the bug (so that Verizon will be more accommodating). We're not likely to "solve" it.
 
Dottom22 has been able to replicate it on his phone this way:

Dottom22 said:
"Silent Call"/"Phone going Silent" Bug Update -

Ok, I've narrowed it down. Anyone that sees this pattern too let me know.

This issue seems to happen prominently after someone leaves me a voice mail and I select to listen to it from the Notifications bar at the top. It's happened consistently!

I'll get a call, which I hear just fine. They leave a voice mail, which I hear the notification just fine. But once I select to call my voice mail from the notification bar, I never hear the voice mail operator. Then it all just goes to pot, the phone lags when I use the dialer and volume and everything. Then I reboot and the call to VM works.
Click to expand...

That wouldn't have worked for me since I never dialed into voicemail. Maybe it will work for some though.
 
I haven't been able to find anybody who is rooted reporting this problem...I assuming since the cooks are going crazy with all the ROMS they haven't had time to have this issue as they are loading or updating their ROMS.

DO ANY ROOT USERS HAVE THIS PROBLEM WITH THE NO MIC NO SOUND BUG?
 
I've had the silent call issue 3 times now since a manual upgrade from stock 1.5 to 2.1 four days ago. My issue seems similar to everyone else except that it seems I'm losing signal all together. Every time it has happened, it's been during a call. Everything goes silent. I can then hang up and attempt to call the person back. I notice that the phone never actually initiates the call. The new vibrate feature when dialing out helped me notice this. Once I try to return the call, the screen just sits on dialing. It never gives the single vibration to tell me the call is connecting. A reboot seems to solve the problem temporarily. Gonna try the G-sensor calibration and will report back.
 
The calibration never failed for me either. When I went to v3 I got the bug back. So I did it again and no probs. So please let me know if this works for someone else.
 
thenestor said:
Anyone else want to try calibrating their g sensor? It's the last item under settings : sound & display. It would tell us a lot if the non-silent phones can calibrate easily and the affected phones have trouble.
Click to expand...

I just tried calibrating the g-sensor and I'm on LV3 with silent call issue. It aborted three times before finally calibrating. We'll see if I continue to get the silent call problem. FYI--the issue has never happened during a call--like Thenestor, it's only happened to me after a call. I also had the issue on LV2, but never on 1.5.
 
I have had the silent call issue since v1 and again in v3. I even disabled sense to see if it helped and it doesn't. did make the phone run faster. I just tried to calibrate the g sensor and it worked right away. Is everyone with the silent bug have major speed issues with their phone? I did a factory reset after installing v3 because my phone would slow way down (even not adding apps). It appears right before my phone is going to go silent, everything is laggy to the point I can't even use the phone. my phone seems to be fast right after reboot and then slowly goes downhill.
 
You must log in or register to reply here.
Back
Top Bottom