• 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

I'm having the phone issues and its killing me. I guess its my own fault for upgrading to a leaked version. I'd love to take this phone to VW and get a new one. Its driving me nuts! Can't make phone calls with my PHONE!
 
thenestor, keep this thread alive and I will do my best to post what I was doing beforehand to try and see if it was something I was doing that triggered it....

this phone, like many others have stated, would be amazing if the phone part actually worked like it was supposed to
 
I updated 1.5 to 2.1 v3 last night, have 50% time w/o signal bug, but not sound issue, I don't use bluetooth, hardware version is 002, and I'm not sure if this has anything to do with anything but I'm curious how many people with the bug use the stock 8GB SD card, I use a 16GB one from my old droid
 
Here is my observation...I went 2.1v3 last night but before that I was having the loss of audio issue about every other day. I spent the last few weeks trying to figure out what was causing it and for the last 7 days I left my wifi turned off and did not have to reboot all 7 days and never once had loss of audio?
 
i know it has nothing to do with wifi... because i never touch wifi, and it is always off, yet i still have the dropped audio
 
Alright guys, just had the dead speaker happen to me on the beta 3. Starting messing around with the settings (without a restart, so speaker is still dead). I messed around with call volume, media volume, etc.

I was able to move the slider for the call volume, I realized I had changed the notification volume to be the same as well, so I went ahead and did that too. Still no sound.

I made my way to the media volume, because I remember the phone stays in the media volume a lot of the time when the speaker outage happens. Tried to edit it by clicking on it and the phone became unresponsive.

While the phone was still stuck on the settings screen, presumably trying to get in to the menu, I pressed the power button and put the phone to sleep. Then pressed it again to wake it up. There was a considerable lag between waking it up and gettng to the slider screen. I hit Menu to get past it, but it wouldn't work, and still lagged quite a bit. So I began to mash on the power button, putting the phone to sleep and waking it up rapidly. Finally, I got a message I have never seen before relating to this issue and it was the force close error for "Activity Sound and display" saying it was not responding. I hit wait and put it to sleep again. Same unresponsive lock screen.

I'm still trying to mess with some more variables and see if I can get the sound back. Airplane mode didn't work either.

I'm not expecting any important calls or texts today, so I'll see if leaving it alone will get this thing to straighten itself out. Not that it will help if it does end up doing that, because a restart would be easier, but...

We'll see.

Just posting what I found so maybe someone with some knowledge on the OS can have something more to work with.
 
Alright guys, just had the dead speaker happen to me on the beta 3. Starting messing around with the settings (without a restart, so speaker is still dead). I messed around with call volume, media volume, etc.

I was able to move the slider for the call volume, I realized I had changed the notification volume to be the same as well, so I went ahead and did that too. Still no sound.

I made my way to the media volume, because I remember the phone stays in the media volume a lot of the time when the speaker outage happens. Tried to edit it by clicking on it and the phone became unresponsive.

While the phone was still stuck on the settings screen, presumably trying to get in to the menu, I pressed the power button and put the phone to sleep. Then pressed it again to wake it up. There was a considerable lag between waking it up and gettng to the slider screen. I hit Menu to get past it, but it wouldn't work, and still lagged quite a bit. So I began to mash on the power button, putting the phone to sleep and waking it up rapidly. Finally, I got a message I have never seen before relating to this issue and it was the force close error for "Activity Sound and display" saying it was not responding. I hit wait and put it to sleep again. Same unresponsive lock screen.

I'm still trying to mess with some more variables and see if I can get the sound back. Airplane mode didn't work either.

I'm not expecting any important calls or texts today, so I'll see if leaving it alone will get this thing to straighten itself out. Not that it will help if it does end up doing that, because a restart would be easier, but...

We'll see.

Just posting what I found so maybe someone with some knowledge on the OS can have something more to work with.

Same thing happened to me, sort of.

I was playing Solitaire (the paid-app, Mega Pack thing) for a little while, and it kept fc'ing, so I uninstalled it. I also uninstalled Google Sky Maps. Later, I was setting the alarm, and I went to test the volume for the alarm and everything was silent. The alarm clock app (native) fc'd, the htc ringtone picker fc'd, and another program fc'd. I went into the settings to do the airplane trick, no dice. I went into Settings -> Sounds and Display to make sure that everything was not silenced, and it fc'd on me. I tried erasing call log, sleeping and waking the phone, putting phone on vibrate or silent and setting it back to normal - nothing worked, I just no rebooted because I need my alarm clock to work in the morning.

tl;dr - uninstalled some apps, everything started fc'ing, got the no-audio-bug
 
Random thought, but have any of you tried turning on/off voice privacy?
Also, have any of you messed around with tty mode?
 
The no audio thing happened to me early last night... I was listening to Pandora radio when I got a call... so I immediately answered the call and within a minute or two into the call all audio dropped out... so I had to restart...

I will try to duplicate this later
 
Random thought, but have any of you tried turning on/off voice privacy?
Also, have any of you messed around with tty mode?

I haven't played with either of those settings, and I have the issue. Luckily(?) no one ever calls me.

I also use non of the programs in the last two posts, nor have I had any force closes.

Just every once in a while, no ringtone sounds. The one time I was able to test it, the trackball flashed and the screen came on, but no sound
 
I'm starting to think that it isnt one particular app that is causing this issue but that the device itself in 2.1 is having a problem with multiple audio outputs...

Maybe this is why we have yet to see the OTA reach our phones
 
Zombie phone happened to me last night for the first time on the v3 leak. I just finished playing Robo Defense and then I went to text my friend. After that, I tried pressing Volume Up to check to see if my sounds were still working. It's become a habit of mine to check every few hours. Sure enough, no beep and there was major lag with trying to adjust the volume. I knew my phone had turned into a zombie so I rebooted and everything was back to normal.

I know the problem isn't with the game because it happens at seemingly random times. At least this time, it wasn't an incoming call that triggered it. I still haven't had this happen with an incoming call with the v3 leak, so maybe that's a good sign. Or maybe it'll happen sooner or later. :(
 
I had it again yesterday afternoon (on leak v3).

I was browsing in my phone's browser, got a call from someone in my phone book, answered it, everything was fine... hung up using the touch screen "end call" button, immediately went back to the browser, searched for a business, tapped its phone number to dial, hit send, and... no sound.

Hung up, verified that the phone was experiencing audio loss, and rebooted. I didn't try replicating because I was in a hurry.

PS - Volume rocker was not stuck on "media volume" this time, so apparently that's not a reliable symptom.
 
Signed up for the forums to post on this issue...

Me and my wife are both running 2.1 v2. I do not have the issue at all and I use the phone for everything. She has very few apps and what not, doesn't use Mail that often. Mostly Facebook and the browser. She does have the problem daily. I tried to replicate it on her phone but it seems completely random. It happened after charging all night twice and every other time just randomly. A few of the times nothing was being done on the phone as all account syncing was off.

Curious... she has quite a few custom ringtones. Does everyone else? Or everyone using stock tones? Doubt it'll affect it but w/e.
 
Signed up for the forums to post on this issue...

Me and my wife are both running 2.1 v2. I do not have the issue at all and I use the phone for everything. She has very few apps and what not, doesn't use Mail that often. Mostly Facebook and the browser. She does have the problem daily. I tried to replicate it on her phone but it seems completely random. It happened after charging all night twice and every other time just randomly. A few of the times nothing was being done on the phone as all account syncing was off.

Curious... she has quite a few custom ringtones. Does everyone else? Or everyone using stock tones? Doubt it'll affect it but w/e.

I'm using custom ringtones for calls, custom notification sound for SMS, stock notification sounds for email. And the "Facebook Pop" from the Facebook app is technically also a custom notification sound. I'm pretty sure some people on XDA reported this problem right after a factory reset, though, so they didn't have any custom ringtones set up.

EDIT: I set all of my notifications and ringtones to factory ones, and then as luck would have it, I got the bug a few hours later. So no, it doesn't seem to matter if you have custom ringtones.
 
OK, it just happened again. I was using Meebo and chatting with a friend, but when I went into the settings to pick a different ring tone, everything froze and after a couple minutes, I got an error saying htc.ringtonepicker (or something like that) isn't responding and I can either force close it or wait. I closed it and I didn't have any sounds for anything.

Rebooted phone and back to normal again. Something's obviously triggering this error...I hope someone finds out what it is soon!
 
My God... it has happened to me four different times today...

I was doing completely different things every time it happened....

I have insurance on my phone.... any idea how to get a new Eris or even a refurbished one???
 
My God... it has happened to me four different times today...

I was doing completely different things every time it happened....

I have insurance on my phone.... any idea how to get a new Eris or even a refurbished one???

This is another good example of why it would be great if we could produce a replicable way of causing the sound bug: You could take it into Verizon and get your phone replaced under warranty.
 
The one time I could pinpoint it happening to me, was when I was talking to someone on the phone, and wanted to switch to speakerphone so I took the phone away from my face. the screen was still dark, so I wasn't able to hit the speakerphone button. I pressed the trackball I think? or another key, and eventually the screen came on. I hit the button, but didn't hear anything. hit it again to turn it off, and still nothing. The call timer was still live, and when I called the person back after rebooting, she said the line just went dead, but her call timer was still going.

From what I gather, (and what was said earlier) I feel as if it's an issue with the dialer just not taking over the phone properly? <---totally a guess here.

I just upgraded to 2.1 v3, and really hope that it doesn't happen to me anymore, but after reading the responses here, not sure anymore. :(

I'm not going to install any new applications just so I'd have a clean test environment to make sure it doesn't happen. I also plan to really give the phone a bit of time inbewteen key inputs, to make sure it's caught up before I start queuing up commands and it starts to lag.
 
FYI:

I took one for the team yesterday and performed a factory reset on my phone, reinstalled 2.1 V3, 228 Option 1 and 2 and NOTHING else, not a single app or widget...I did not even change my scene or a single setting. In other words, bone stock!!

Made 1 phone call, hung up to make another and BAM, the damn thing was dead!! I think we can now safely rule out any Apps being the cause. It is definitely something native on the device!

~Jim
 
Leak 2 I would take a few days before it would happend. I installed version 3 Thursday I think? Anyways today I mowed the yard using my Bluetooth headset and it happend twice in a 30 minute span. I think the Bluetooth excels the bug.
 
Honestly I think that its coincidence that avalaunch was able to get it to happen consistently. when I was on a 2.1 rom it happened when I had it on vibrate for 2+ hours in a movie and hadn't touched the phone at all in that period. It happened after calls, before calls, after bluetooth, on days I didn't use BT at all....
That is why the leaks have all been testers, they obviously hadn't worked out all the bugs, this obviously being one of the major ones, and it isn't carrier specific. It is in HTC kernel, and most likely won't be fixed untill the source comes out.
I am rooting for you guys though I hope that one guys cousin in that other thread comes through with a 100% way back to 1.5.
 
Guys I really think we are beating our heads against a wall trying to pinpoint a cause by looking at Apps or certain other activities. The ONLY thing I have not ruled out without 100% blaming the Hardware/OS combination would be *default system settings*!

As I said, I am currently running a completely virgin 2.1 V3 on a factory reset device and I got the bug on the second call!

This may be asking a lot, but is there anyone NOT experiencing this bug that would be willing to review some of their "Sound and Display" settings and post them here?

I am willing to act as a guinea pig (thenestor may as well) to try out settings to see if anything helps!!
 
Back
Top Bottom