View Single Post
  #1065 (permalink)  
Old 01-19-2012, 02:37 AM
arrrghhh's Avatar
arrrghhh
Testing Extraordinaire
Offline
 
Join Date: Mar 2007
Posts: 3,604
Reputation: 7360
arrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the community
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: [TESTING] - NAND OMGB (1.2.3)

Quote:
Originally Posted by [ACL] View Post
3) When you notice loss of sound, put the phone near your ear and see if you hear buzzing. I noticed when i was testing that if i lost all sound, the speaker would buzz. Also, if you ADB shell into the phone when this happens and do a logcat i would see some errors which might be helpful.
Sorry, missed this one. Meant to respond .

Every single time I've lost audio it has been in this condition. Buzzing speaker - like it was turned all the way up, but no input going thru it.

Here's some really good HaRET logs on the bug.

The reason I say really good is he said he made a call, was fine. About an hour or so later, made another - no audio. I can see that in his logcat, so perhaps this will capture the failure somewhere inbetween?

Always see this:
Code:
01-17 21:13:07.740 W/AudioTrack( 1298): obtainBuffer timed out (is the CPU pegged?) 0x46dd50 user=000012c0, server=00000000
Reply With Quote