Hi guys,
It seems I have a big problem with my TF. I updated to 3.2 several days ago, everything running smooth and OK, but this evening while I was watching a movie, sound went dead on the right speaker and the left one followed pretty soon. I tried rebooting the device and playing a song and I'd get sound out for about 1-2 secs and then it dies. After another reboot same problem, 1-2 secs I have sound then all dead. I wiped the device and tried a fresh install and guess what, I have sound for 4-5 secs and then it dies again. Very very uncool ...
I bought the device from Amazon.uk, do any of you guys know how they deal with things like this? This is the first gadget I've bought from Amazon.uk so I don't really know yet.
Had it since June, very happy with the way it performs and anxiously waiting for the TF2 but this really bursts my bubble .
Regards,
Try and flash the voodoo speaker fix, you can find it somewhere in the dev section. It's a software error with honeycomb.
Hey, thanks for the post, but I don't think its a software issue. First of all, it worked OK until now, and it worked for more than a week on 3.2, second of all if I shake it or tap on the backside, near the right speaker, it seems to work, at least for a couple of seconds, so it's hardware related
Related
I just picked up this tablet today and I'm running TNT lite 2.2. I seem to be having issues with the sound now. It is coming out all staticy and crackling... When it happened the first time, I rebooted and it went back to normal. But now it has happened again 20 min later...
Anyone else experience this?
sano614 said:
I just picked up this tablet today and I'm running TNT lite 2.2. I seem to be having issues with the sound now. It is coming out all staticy and crackling... When it happened the first time, I rebooted and it went back to normal. But now it has happened again 20 min later...
Anyone else experience this?
Click to expand...
Click to collapse
with fring, but that's about it... tnt2.2.1 here.
I had the same problem with the original one that I purchased with no new image put on it yet. I exchanged it and the new one is fine. BTW, I did notice that the sears employee marked it as having a sound problem so you didn't get mine.
I am as well
Having issues with the sound. At times when a sound is to be played, I hear a loud static noise. It only happens a few times. Also, when I plug in headphones, only the Right side is heard and not the Left. Any help??
For any sound issues, I would suggest going back to stock and trying it. I have had a lot of mod issues, but staticky sound is not one of them.
I have a sound issue where there is a loud static sound and its intermittent.. pressing any buttons seems to stop it. it goes away after reboot.
Return it! I had this issue with my first G tab. It got progressively worse over the course of 2-3 weeks, until I had no functioning sound. My new unit has not had this problem at all.
P.S.
any one picking up a refurb in santa cruz, ca beware...Sears employees asked 0 questions when I returned it
Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
as i'm a developer i didn't this it's a bug ithink it's accidentaly and you were at that place again like other time
But that's quite too big to be jusn an accident. I had this phone for half a year and nothing. Well i'll try this Friday not to put it on top of the receiver and will post what happened. This thing scared my quite big, i thought that mmc is broken but i have checked the bootloader (i don't know how the screen with 4 colors is called, i think it's bootloader) and it showed my mmc working perfectly. If it was not because of microphones what could then be the problem?
OK tried that this Friday too. Same think - phone near the receiver - phone dies and i must hard reset it to work again. How is this possible? Which part of the phone messes?
Very possible that a strong magnet could do this. Internally the surround uses a microsd (there are guides here for upgrading it but taking the phone apart). I imagine a strong enough field could corrupt a microsd pretty easily. When u say wireless mic do you mean bluetooth?
No no no, i mean microphones which are used on stages, i work as a sound engineer and my phone always is close to receivers, close to controlers and other stuf i use. So to avoid further coruptions i should put my phone further from all equipment right?
OK after this other few tries i have found out that it does indeed mess my phone, i have tried holding it near wireless microphone receiver and my phone have frozen and when i placed my phone further from receiver nothing happened. So look out for that
r0mka said:
Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
Click to expand...
Click to collapse
Is frozen screen? Still completely can't use? I feel a little bit like WM6 era's problems. After a certain amount to you. May is hardware have dark disease.
Hi guys,
I am very, very sure that when I first got my A510 in June, it had amazing sound. Whenever I listened to songs w/o head or ear phones, I would only need to put the volume to half and the song would play loud enough.
But something bizarre has just happened - the speaker quality has deteriorated greatly! I think the Android system has 10 different sound volumes. When I am at the first 3-4 volume range, nothing is audible! When I get to the 5th I can hear a little, and at max volume the sound is actually around the same loudness as it would previously be at half.
The strange thing is I cannot pin point when exactly this happened. It must've been in the past 2 weeks. I never installed any ROMs. I just rooted my tab over a month ago but I don't think it had anything to do with that.
By not being audible at the first 3/4 levels, I mean I can place my earn at the speakers and not hear a thing. So I am certain there's some issue here.
I've checked all my tablet settings including for Dolby but nothing is out of place. Will really appreciate your help.
Thanks!
Same here! Acer Iconia A511, stock rom, not rooted!
i have no idea, why this happens! I just found out, if you go to the voice recorder and you record something, the sound comes back to normal. Unfortunately not all sounds, e.g. whatsapp notification is still missing.
After booting the device all is fine again. If anyone has a solution for this, please advise!
Hey guys,
It's Sachin here. A new member or the forum. Currently I'm running Android 4.0.4 with CleanROM 5.1 Early yesterday I was doing some tests with my guitar and I wanted to see what would happen if I plugged in my aux cable into my phone. If it would record it or not. I tried doing the same thing but plugged in my phone to laptop and wanted to see if it would pick up sound as well. Well anyways, it was either that or something else that triggered an audio problem. Now I can only hear out of my right earphone. The weird thing is, when I reboot the phone it works perfectly for a 20-30 seconds. Afterwards, the left earphone buzzes out and I'm only able to hear the right one (I have tried multiple earphones and every single one does the same thing). Moving on, I called A.T.T. and the guy walked me through a restoration of the phone (Still on CleanROM, he didn't know obviously). He said I would have to bring it in to an A.T.T. center and that they would have to look at it or replace it for me (still in the 90 day fixing period). I'm scared they won't look at my phone knowing that I do have a custom rom on there. Plus it being rooted. If someone could help me PLEASE figure out how to get to this thing unrooted and back on stock, I would appreciate it soooooo much!
Running TWRP Recovery
Too Loooong Did Not Read Version:
-Left headphone starts buzzing, tried different headphones still didn't work
-Might be a software issue as it works temporary then doesn't
-Called A.T.T. and the gave me an adress where I could go get it fixed
-Have to flash back to stock so they don't refuse service but don't know how
Thanks for taking the time to read through this thread.
Sachin192 said:
Hey guys,
It's Sachin here. A new member or the forum. Currently I'm running Android 4.0.4 with CleanROM 5.1 Early yesterday I was doing some tests with my guitar and I wanted to see what would happen if I plugged in my aux cable into my phone. If it would record it or not. I tried doing the same thing but plugged in my phone to laptop and wanted to see if it would pick up sound as well. Well anyways, it was either that or something else that triggered an audio problem. Now I can only hear out of my right earphone. The weird thing is, when I reboot the phone it works perfectly for a 20-30 seconds. Afterwards, the left earphone buzzes out and I'm only able to hear the right one (I have tried multiple earphones and every single one does the same thing). Moving on, I called A.T.T. and the guy walked me through a restoration of the phone (Still on CleanROM, he didn't know obviously). He said I would have to bring it in to an A.T.T. center and that they would have to look at it or replace it for me (still in the 90 day fixing period). I'm scared they won't look at my phone knowing that I do have a custom rom on there. Plus it being rooted. If someone could help me PLEASE figure out how to get to this thing unrooted and back on stock, I would appreciate it soooooo much!
Running TWRP Recovery
Too Loooong Did Not Read Version:
-Left headphone starts buzzing, tried different headphones still didn't work
-Might be a software issue as it works temporary then doesn't
-Called A.T.T. and the gave me an adress where I could go get it fixed
-Have to flash back to stock so they don't refuse service but don't know how
Thanks for taking the time to read through this thread.
Click to expand...
Click to collapse
Need to lock your bootloader again in fastboot then use evita rom for your phone, you might need at&t one. This process will wipe your phone including photos/videos.
They will see if they are looking that it is relocked in fastboot.
Good luck
I want to take a minute and share a bluetooth issue I've had with my Galaxy S6. Maybe others have observed the same thing, and while I'm not specifically looking for a solution, suggestions are welcome. The S6 is about 3 months old, Andriod 5.0.2, unrooted, and other than Apex launcher pretty vanilla.
For the record, with the exception of the issue I'm about to describe, this phone has been phenomenal.
I use the phone in my car over bluetooth to and from work every day. For the first two months this worked great, no problems at all with podcast addict or poweramp. Then, I noticed the audio would dip momentarily. As if someone turned the volume down and back up. The bluetooth connection never gets lost, just the audio dip. Then, eventually the problem became perpetual. I will describe the symptom the best I can, as if the volume were being turned up and down. This wasn't the case, more like the bluetooth stream was somehow going away and coming back.
I tried all the obvious things, like re-pair the phone to the car, clear the bluetooth cache, Volume Up + Home + Power button and then "wipe cache partition". As a last resort I did a factory reset. This last step actually solved the issue, for a while. This was a few days ago, but this morning I noticed the same periodic blips in the sound, so I suspect over time the same problem will once again return.
<rant>
I was in touch with Samsungs customer support, who is supposed to "values you as a customer and want to insure that we have provided you with the answer you were looking for". Unfortunately, the blunt truth was they ended up being useless with an offer to allow me to send my 2 month old phone to them and wait for an undisclosed time, for what might end up being a refurbed replacement.
</rant>
Since I don't see mention of this in the forums, maybe it's not a wide spread problem. Maybe a compatibility problem between these two specific chipsets? Whatever the issue, hopefully some future update comes out that fixes things. Defaulting the phone every few months would be a considerable drag.