[Q]Completelly lost all sound - G Tablet Q&A, Help & Troubleshooting

Hey all,
I have no idea what the hell is going on with my tab. I did not have any issues and all of a sudden lost any and all sound. I was running Vegan 5.11 and then installed Vegan Ginger RC1 and thats when, I think, it started happening. I NVFlashed back to stock and still no sound. Tried to install a bunch of other roms and still no go. I am absolutelly lost of what to do. BTW I tried the earphone plug in and unplug but nothing. The only way anything happens is through bluetooth.
Help!!!!!

System & Alarm OK, No Media Sound
Let my G rested for a few days and last night the sound was cutting in/out. Today the sound is completed back. I am still on stock ROM, did not do anything special, just turned on the “Audible Selection” and rebooted a few times.
I guess it was too much water while putting on Skinomi screen protector...
**************************************************************************
Now it’s confirmed, media sound works, as long as the screen is off.
Tried to play music with stock ROM, as soon as I "saw" music is playing, hit power button to turn off screen, then I can hear music, but as soon as the screen is on, media sound is silent.
Would be great if sound and screen can both be on again. Please HELP!!
***************************************************************************
I installed Skinomi screen protector and after that lost media sound. During the installation I tried to power down my G but as soon as I squeegee the screen (even after confirmed power off) G will come back on and of course a lot of commands were popping up on screen since I could not power it down. After Skinomi installation I lost media sound. At first I thought I drowned the speakers but then realized system and alarm sounds still work, just no media sound.
Then I had another interesting discovery. If I tried to watch Youtube video and while it’s playing, hit the power button to shut off the screen, I can hear the media sound when the screen is off for a little while. As soon as the screen is back up, media is silent again.
I also tried the headset trick and switched from Vegan 5.1.1 to TnT Lite to stock ROM. I believe the silence was caused by pressing keys in special sequence but don’ t know what it was since I was using a squeegee. Otherwise I have had my G since Feb2011 and never had any problem.
I am praying to all you android GODs out there and hoping I can find an answer to have the media sound back again.

I fixed my sound issue that sounds identical
You should appreciate the beauty of the problem and the solution...
After thinking it had to be a software issue (because the sound worked as long as I turned the screen off) and finding no one at all who knew what to do I was about to give up on the sound on my g tablet.
But then I had a crazy thought - what if it was a hardware issue where either a contact on the motherboard melted together or somehow the sound cable was interfered with by a loose connection.
If you open the gtablet case - Gulp! Its actually not that bad...
Using an eyeglass repair kit screwdriver, gently remove the rubber circular pads on the back of the tablet.
Underneath you will discover screws that the eyeglass screwdriver can unscrew.
After unscrewing all four, use a credit card to gently slot between the seals of the casing all the way around. eventually the casing will separate without problems.
Once open, and with the tablet now facedown on your lap. look at the lower right section of the motherboard for a thin brown wire that is connected near the 3.5 mm jack up and connected on the other end near the middle right of the motherboard.
Mine was untaped and loosly laying over two contacts of the motherboard. All I did was gently position that little wire away from those two contacts to the left (right of the metal screen backing wall) so they would not touch those contacts.
Believe it or not - that solved the problem. Turns out that the two contacts when touched by the wire cause the sound to short off. But when not touching them, everything works fine.
The reason the sound would work before when the screen was turned off in sleep mode was because IF THE SCREEN IS OFF THERE IS NO LONGER A CURRENT GOIND THROUGH THE CONTACTS!!! Beautiful....
gently snap the cover back on and ensure it all snaps back all the way around, reinsert the screws and replace the little rubber backings and turn you tablet back on.
Good luck!
What was that? I can't hear you over my newly working tablet speakers!!!

Very interesting. Thanks.
I've been puzzling over (and, frankly, have not been able to diagnose) a similar problem. Looks like bad engineering on VS's (or Malata's) part if 5 users have encountered this same problem.
Karmas coming your way if the user verifies that what you suggested fixed his problem.

Thanks. I had the cover off before to resolder the power jack to the board. This time I accidentally pulled on the headphone cord.
amoffa said:
You should appreciate the beauty of the problem and the solution...
After thinking it had to be a software issue (because the sound worked as long as I turned the screen off) and finding no one at all who knew what to do I was about to give up on the sound on my g tablet.
But then I had a crazy thought - what if it was a hardware issue where either a contact on the motherboard melted together or somehow the sound cable was interfered with by a loose connection.
If you open the gtablet case - Gulp! Its actually not that bad...
Using an eyeglass repair kit screwdriver, gently remove the rubber circular pads on the back of the tablet.
Underneath you will discover screws that the eyeglass screwdriver can unscrew.
After unscrewing all four, use a credit card to gently slot between the seals of the casing all the way around. eventually the casing will separate without problems.
Once open, and with the tablet now facedown on your lap. look at the lower right section of the motherboard for a thin brown wire that is connected near the 3.5 mm jack up and connected on the other end near the middle right of the motherboard.
Mine was untaped and loosly laying over two contacts of the motherboard. All I did was gently position that little wire away from those two contacts to the left (right of the metal screen backing wall) so they would not touch those contacts.
Believe it or not - that solved the problem. Turns out that the two contacts when touched by the wire cause the sound to short off. But when not touching them, everything works fine.
The reason the sound would work before when the screen was turned off in sleep mode was because IF THE SCREEN IS OFF THERE IS NO LONGER A CURRENT GOIND THROUGH THE CONTACTS!!! Beautiful....
gently snap the cover back on and ensure it all snaps back all the way around, reinsert the screws and replace the little rubber backings and turn you tablet back on.
Good luck!
What was that? I can't hear you over my newly working tablet speakers!!!
Click to expand...
Click to collapse

Related

I have some troubles with my Cingular 3125

1- it's reboot many times without any reason(I read one thread about it but i dont understand what to do!!)
2-sometimes 2gb microSd card loosing?(i cant open it from phone...only rebooting helps!!)On other devices card works good!
The usual reason for a 3125 rebooting is that the battery cover has gotten worn down to the point that the micro-switch under it is not fully depressed. There are multiple potential wear-down points. The hooks on either side and the tabs at the bottom can get worn or even broken. There is also a raised pad at the lower left (looking at the cover from the inside) than can get worn, as can the contact point on the switch.
Typical solution, providing the hooks and/or tabs are not totally broken off, is to put a thin piece of plastic or cardstock between the microswitch (lower right of the batter compartment) and the cover. It's a temporary solution (it tends to get continually worse), so if this fixes it, you should check eBay for a replacement cover.
That said, I had a phone that reset for another reason, which I never found. So it could be something else. I ended up buying a phone with a bad keyboard and doing a keyboard transplant from my old one.
I had the same problem and I'll tell you what I did. Open the back cover and you will see a little black switch next to the sim card/below the battery. I took a pair of needle-nose pliers and just twisted that sucker right out like a bad tooth (carefully though, you don’t want to tear up the foil on the board). Then I put a small spot of solder on the two contacts that the switch used to connect to. Never had a random reboot ever again. From then on, just make sure you take the battery out first before ever messing with the sim/sd card.
That worked for me.
Thanks
dexx40steve said:
I had the same problem and I'll tell you what I did. Open the back cover and you will see a little black switch next to the sim card/below the battery. I took a pair of needle-nose pliers and just twisted that sucker right out like a bad tooth (carefully though, you don’t want to tear up the foil on the board). Then I put a small spot of solder on the two contacts that the switch used to connect to. Never had a random reboot ever again. From then on, just make sure you take the battery out first before ever messing with the sim/sd card.
Click to expand...
Click to collapse
i have the very same problem and this sounds like a perfect long term solution.. any chance of getting picture of ur mod for morons like me who need visual stimulation?
regards,

[Q] Aria Front (In-Call) Speaker Stopped Working

The in-call speaker on my wife's Aria doesn't consistently work for calls. I've replaced the digitizer on it, but I don't think it's hardware related, because I took the battery out while it was on, and when I started it up again, it worked; and sometimes it works, then doesn't, then does.
What happens is when she calls or is called the speaker just doesn't work. She transfers the sound to the external speaker and it works fine.
She's running the Liberated ROM (not sure what version, sorry; I can find out if needed).
Thanks for any help!
It's probably a loose connection.
Using a wired headset has screwed 2 arias for me now.sometimes I can wiggle the plug before I remove it and get the speaker to work but generally I just turn speakerphone on and turn the volume all the way down to use the ear speaker.fairly common problem.
Sent from my Liberty using XDA App
drumist said:
It's probably a loose connection.
Click to expand...
Click to collapse
I'm going to agree on this one. I've taken my Aria apart more times than I probably should have... the first cellphone I've ever repaired on my own, so go figure.
My bet would be that the in-call speaker is still in place, but loose. If you open it up again, the piece you're looking for is maybe a half-inch long rectangular block with two prongs on one side. If the phone is sitting screen up, the prongs should be facing down with the points towards the top of the cell phone. It sits in a little recess above the lcd assembly.
You need to push the piece up so it's snug in it's little recess. Easy peasy.
If you've already done a digitizer replacement, you should have the tools to do a quick check and make sure the speaker is secure in the proper position.
I still think it may be a loose speaker connection, but I also think mtnlion could be right, too.
When the in-call speaker does not work, does the phone show an icon in the notification bar that indicates that a headset is connected?
In any case, I do think it's a hardware issue and not a software issue. But if the OP really wants to be certain, he can install another ROM and see if the same problem occurs.
Yeah, I took the thing apart again, and stretched those prongs a bit to make the speaker fit more snugly; hasn't had the problem since. But I think now the seal isn't quite as tight as it used to be so her screen "squishes". That'll be another day.
Thanks for the thoughts on it.
Adhesive issues
I had that issue too. To fix it, all I had to do was use a space heater (or a blow dryer) on the phone (take the battery, sim card and SD card out first) for about 15 minutes. Then take it and smoosh it underneath something flat and heavy like a book, but make sure to put something down beneath it so the screen doesn't get scratched. Once it cools down, it should be significantly less squishy.

x10 half dead, pinched ribbon cable. HELP!

yesterday I decided against my better judgement to try and take apart my x10 to see if I could get to the speakers, it sounded distorted during phone calls when the volume was all the way up. I used the dissasembly guide here: http://www.xperiax10.net/2010/05/10/xperia-x10-disassembly-guide/
however once, i started reading the guide, i realized I had to basically gut the entire phone to get to the main call speaker, so i put it back together. all i did was take out the screws, removed the lower support and used a credit card to pry between the covers and worked my way down. thats as far as i got, I had the back cover off and then I reassembled after reconsideration. however, the phone didn't work when i turned it back on. I mean, it works and I can see the backlighting on the screen but no logo or anything. I know it's actually booting into android because I can unlock the phone by memory and proper finger placement without even having the display working. I hear the "click" when it unlocks my phone and the volume/updown beeps. i've even heard my personal set notification tone go off a couple times. however, aside from the screen not working (besides backlighting), it wont respond to a phone call or chime when you send it a text message. If i use a different phone to call mine, it rings several times until you leave a voice message like normal. so, its not acting like its off. so again, I know it's actually booting into android.
after further inspection I realized that there is a ribbon cable on the bottom right hand side (battery side up) particularly close to where the covers snap together. I don't know if I did it with the credit card swipe or the covers weren't aligned well when I snapped it back together but I can see one little trace with a magnifying glass and a flashlight where it was "nicked" or scored. one teeny tiny little thing and my phone is inop.... does anyone have any suggestions? maybe like where I can get that ribbon cable? I'd start over with a new phone but the ebay prices are ridiculous. this use to be an ATT free upgrade phone and now its discontinued. I really doubt you can fix a ribbon cable... im feeling pretty helpless here.
I think you should send to shop to get professional repair before it getting worse.

LG Bootloop? Only when plugged in? / Battery pull. Pics inside.

I recently flashed Mysteryemotionz v4.1 kernel and about an hour through bench-marking I came back to find my phone rebooting. I assumed it overheated or bugged out during testing and didn't think much of it until it went through the LG logo 3 times.
I noticed it would not turn on at all without the USB plugged in, my first instinct was that the battery became disconnected somehow. I could get to the fast boot and download screens, but any attempt to vol down into CWM was met with failure, and a fresh LG screen over again.
Any combination of buttons that included pressing power would result in the notification LED eventually flashing, approx 10 times. Sometimes slowly for 10x then slightly faster.
It is worth noting the phone would not charge while doing this, but the battery was full prior.
I tried leaving it unplugged overnight, same problem in the morning. Tried leaving it looping all day while at work, no dice. Finally figured I would attempt to see what was with the battery itself. I suppose if you were very patient, you could wait until your battery discharged completely, thus performing a "soft" battery pull, but this will take 4+ weeks at a full charge.
As the other battery pull thread is Sprint specific, here is a refresh for AT&T's LG E970.
I HIGHLY recommend you take a look at nericus' original thread in the Sprint LG Optimus G forum as this is only supplementary.
http://forum.xda-developers.com/showthread.php?t=2108154
The tools I used: {{Picture 0}}View attachment 1931288
T-6 Torx bit - Your mileage may vary, 4's and 5's may also work, start big and do not strip your screws.
P00 Phillips screwdriver to remove the battery plate / connector.
Fingernails
Sewing needle or similar
Optional:
Business Cards (the phone has a tendency to re-engage the plastic clips when removing the back, these were used as shims to place in between the case and the phone while working the other sides)
Magnet (not only to hold the screws but you can magnetize your screwdriver / bits which will help when removing and inserting)
Also, for a little preview of what to expect, user Xiutehcuhtli has made a YouTube video, this is also Sprint specific but a good visual reference.
https://www.youtube.com/watch?v=j3DPxzH3l2c
One of the main differences is that your power and volume buttons will NOT fall out, so you won't need to tape them in place.
Be sure to clear them with the back cover when re-installing it.
Also, you will notice that I did not include a spudger as you most likely will not need it.
Our phone is somewhat "inside out" compared to the original article, our back plate is very shallow and our phone is the cradle compared to the Sprint version. This also means there is different risk areas, and pry methods.
{{Picture 1}}View attachment 1931289
Once you have removed the Torx screws, my initial plan of attack was through the SD Card / SIM card cover. You will notice there is a hairline slit toward the volume buttons on the bottom side of the phone, you can very easily trace this with your fingernail and pop the first tab.
Alternatively, you can spread the phone apart gently from the two surfaces revealed by opening the SD/SIM cover and then work your fingernail or a flat object gently into the gap you created.
View attachment 1931290
Patience is key, the last thing you want is to apply too much force to the back cover in any one spot, it is deceptively thin and you risk cracking the glass.
In my personal experience, once I had a few tabs good on the side I simply traced the outline of the back cover toward the top of the phone, across and back down the opposite side, saving the bottom for last. I noticed after two traces around the perimeter of the phone that the back was still very snug and in random spots, as our tabs tend to re-engage themselves much more readily than the Sprint LG.
View attachment 1931291
My solution was to place business cards under the most exposed tabs and gently work it to cover as many tabs as possible and moving along. You shouldn't need more than two, as this can cover an entire side as well as the top and bottom simultaneously, allowing you to focus on the last side. Again, patience and determination will get you there after some time.
{{Picture 4}}View attachment 1931292
I cannot stress enough to come through at the shallowest angle possible when prying the battery cover with the sewing needle or similar tool.
I have highlighted the points of attack in green, be sure to get in between the two plastic pieces, and gently pry them apart.
Do not get under the entire assembly on accident or try to remove with your finger, it will pop the bottom connector off of the motherboard at the solder points leaving you in a bad situation.
After leaving the battery disconnected for about a minute, and then holding power for a good 10 seconds, I reconnected it and attempted to power on. SUCCESS!! - You can test this with the cover off, so don't make double work for yourself by closing it first.
I hope this helps for a few AT&T LG Optimus G specifics.
Attached should be a zip with a few very large originals if you need a better view.
View attachment 1931327
v/r
Christopher Hurley
SGT, USA
a.k.a [r.]GimP (R - Dot as in Red Dot Society)
YOU SIR ARE A SAINT> i had the exact problem you detailed here with my at&t LGOG, i LGNPST flashed multiple e970 stock roms, and after pulling my hair straight from the follicle, i went out and grabbed the tools, followed your method here and it worked PERFECTLY! THANK YOU GOOD SIR.
So if I pull the battery, wait a minute or two, hold the power down for ten seconds, and then reconnect and nothing happens, and plugging it into a wall charger shows a red flash, does that mean my battery is actually literally dead?
Edit: Also I would recommend following this dude's guide for his plan of attack: http://bit.ly/10VlQWK
I snapped the little bits along the power button and volume. Not a big deal, only aesthetic.. but its something that is avoidable.
Nice. Any idea what caused the boot loop?
i was struggling with ME kernel and rom for about a month. No matter how i wipe and reflash always had reboot/kernel crash/bootloop issues. ME kernel wouldnt even work with the stock rom for me. Now i just run stock rom and kernel, not many issues so far.
swashy said:
So if I pull the battery, wait a minute or two, hold the power down for ten seconds, and then reconnect and nothing happens, and plugging it into a wall charger shows a red flash, does that mean my battery is actually literally dead?
Edit: Also I would recommend following this dude's guide for his plan of attack: http://bit.ly/10VlQWK
I snapped the little bits along the power button and volume. Not a big deal, only aesthetic.. but its something that is avoidable.
Click to expand...
Click to collapse
I would disregard 90% of that video because our back comes straight off, this video is not an AT&T Optimus G.
Especially the part where he is prying by the screen. Someone is going to take that literally and destroy their stuff lol.
Anyway. My guess for your question is that you might have ripped the connector off of the board. Check continuity of those pins in the connector and make sure they didn't come off.
Sent from my Optimus G using xda app-developers app

[Q] Troubleshoot post-liquid-damage; phone boots/responds, but no display

I accidentally bumped a cup of coffee over on the back of my HTC Evo 4g LTE. I bumped a pillow into the nightstand while trying to contort my body in a way that would let me set sleeping my 10mo old into bed without waking him
I turned off the phone immediately, took off my Otterbox Commuter case (not the really waterproof Defender) and found a thin liquid coating on the back housing. Perhaps 1-2hrs later I made the poor estimate that it wasn't "that bad" and tried turning it on. The phone went into what I think was a boot loop (the display never showed anything, so I can't be sure), vibrating every ~30sec as it would if it were constantly trying to turn on and failing. It doesn't have a battery designed for removal, so I just had to let it sit.
Perhaps 6hrs later I went to check on it, and thought it was unresponsive after pressing the power button and nothing appeared to happen. I inadvertently pushed the volume rocker, however, at which point it made a beep as though it were adjusting the volume! After that, I noticed that the power button was also toggling the capacitive navigation buttons, which would illuminate and shut off as if the phone was "running" as well... but I still had no display.
Since then I've done a complete teardown (pop off all cases, separate all ribbon cables, vibration motor, speakers, camera, and removed the battery). I've done a few washes/brief soaks in isopropyl with the motherboard and then put everything in a vacuum chamber overnight at -20 inches of mercury. I also set the display and motherboard it in DriRite (lab-grate dessicant) for about a week now. In the meantime, I assumed the display may have been fried and ordered a replacement since it was only $28 on ebay. I just got it yesterday, but get the same results (phone "turns on," but display never lights up).
Any input on troubleshooting further?
- I've thought about looking at the two ribbon connector receivers for the display under a microscope to see if I can see any residue.
- I've also considered opening my wife's phone (same model) and swapping the batteries based on a probably false idea that if the battery might have gotten zapped, it could power the rest of the phone but not the display? Thinking not, as the power-ups I've attempted have had the USB charger plugged in, but easy experiment.
Would it be possible to short out just something related to the display on the motherboard so that the phone could run seemingly perfectly fine but just with no display? Just seemed so darn unlikely and that if I toasted some circuitry that a lot more would have been toasted in the process.
I plan to reassemble tonight and test for call reception (I think I can guess where the answer button is) and notifications (email myself and see if I get a vibrate/beep). That would confirm that the radios are also still functional.
Sort of at a loss and am not sure what else to do! I'm an engineer and even if the phone is toast... I'd really love to definitively figure out what's causing the issue.

Categories

Resources