Last night I updated my g tablet to the most recent VEGAn ROM 5.1. I wiped all the data from my device via clockwork, wiped the Dalvik cache and repartitioned the internal memory as well. The install went smooth and everything is running great except for the fact that I now have no audio coming from my speakers. Turning the volume all the way up does nothing. I tried reinstalling the ROM but the issue repeats itself. Anyone have the same problem? Or, anyone have an idea how to fix this? Thanks.
Sound works fine here. I did have to take it out of silent mode.
bartonhen said:
Last night I updated my g tablet to the most recent VEGAn ROM 5.1. I wiped all the data from my device via clockwork, wiped the Dalvik cache and repartitioned the internal memory as well. The install went smooth and everything is running great except for the fact that I now have no audio coming from my speakers. Turning the volume all the way up does nothing. I tried reinstalling the ROM but the issue repeats itself. Anyone have the same problem? Or, anyone have an idea how to fix this? Thanks.
Click to expand...
Click to collapse
Sound fine here too. Volume rocker ONLY sets Media Volume in this ROM. Go to Settings->Sound->Volume and manually set volumes up, see if it fixes.
Thanks for the responses guys(or girls...one never knows). Silent mode is definitely turned off and I have also tried to address the issue by going into the volume settings. I have turned everything all the way up but I still get nothing. I'm gonna restore it to beta 4 and see what's up and then try and reflash 5 again. Wish I knew what was going on but thanks for the input.
Just reflashed to beta 4 and audio worked perfectly. I then reinstalled beta 5.1 and the audio disappeared again. Am I the only one?
bartonhen said:
Just reflashed to beta 4 and audio worked perfectly. I then reinstalled beta 5.1 and the audio disappeared again. Am I the only one?
Click to expand...
Click to collapse
I am actually still using beta 5, not beta 5.1, so not sure if something changed when Gojimi updated it this morning?
A quick suggestion - can you try first backing up everything in Clockwork Mod, then wiping user data and see if it makes a difference (i.e. if audio is still screwed up on a fresh install of beta 5.1).
Sound is fine for me in 5.1. All he changed was the G sensor stuff...
Backed it up, wiped user data, did a fresh install and still nothing. Maybe it is specific to my device(although I could not understand for the life of me why). Sad...I am loving VEGAn especially this newest update. I guess I will just wait for the next release to see what happens.
bartonhen said:
Backed it up, wiped user data, did a fresh install and still nothing. Maybe it is specific to my device(although I could not understand for the life of me why). Sad...I am loving VEGAn especially this newest update. I guess I will just wait for the next release to see what happens.
Click to expand...
Click to collapse
If it works in Beta 4, but not 5 maybe download the file again. Besides the G sensor stuff in 5.1 I think Gojimi also uploaded a new file to fix some boot.img size problem. Can't hurt to try the latest if you haven't already...
Did you try the headphone trick? (insert headphone plug into port, then unplug) That was an early issue that was resolved, but maybe it's making a reappearance.
I'm not on 5.1 yet, working on that today.
(btw, when I first read the title, I thought you were trying to do surround sound off your GTab!)
Brilliant! I've spent hours flashing and reflashing trying to get this thing to work and all I needed to do was plug in some headphones and then unplug them! I wish I would have found this out sooner so I wouldn't have wasted everyone's time. Thank You!
P.S.- Yeah I could see how there could be some confusion about title to this post...ha, I'll have to clarify more next time.
bartonhen said:
Brilliant! I've spent hours flashing and reflashing trying to get this thing to work and all I needed to do was plug in some headphones and then unplug them! I wish I would have found this out sooner so I wouldn't have wasted everyone's time. Thank You!
P.S.- Yeah I could see how there could be some confusion about title to this post...ha, I'll have to clarify more next time.
Click to expand...
Click to collapse
Only thing is you should not have to do that anymore. I bet you still have fragments of old roms hanging out. I do not have to do the headphone trick anymore and I am using 5.1. Haven't had to use that trick for a while now.
Whenever I flash something new I always do a factory reset, and a cache wipe. Every now and then I will use Nvflash to restore all the way back to brand new out of the box status. Too much of the old is getting mixed up with the new in a lot of cases causing lots of people to have weird issues that really don't exist.
Makes it hard for a developer to really know what is working and what is broken..
I just installed beta 5.1 and no audio issues, yet. Did you do a data wipe? Maybe there's something in /data causing the issue, that's my only guess.
Data wipes between mods and major updates is always recommended. I know it's a PITN but it can reduce the number of weird issues. I use Titanium Backup religiously.
I have never had to do it before with any older ROMS. I have only been using VEGAn ROMS since beta 3 came out. I also have been doing factory resets, wiping the cache, and repartitioning the sdcard consistently between installs. I might need to use Nvflash just to be safe and install a totally clean version.
bartonhen said:
I have never had to do it before with any older ROMS. I have only been using VEGAn ROMS since beta 3 came out. I also have been doing factory resets, wiping the cache, and repartitioning the sdcard consistently between installs. I might need to use Nvflash just to be safe and get it to stock.
Click to expand...
Click to collapse
I think the framework changed between beta 4 and beta 5. Different stuff. Maybe that's why you have been fortunate until now...
I got No sound too. Plugging in headset makes sound work On headet but when unplugged my sound is gone again. was working perfect on Beta 4.
Just flashed to Vegan Beta5 2 hours ago. My audio is working fine. Playing "Hall of the Mountain King" atm from speakers.
I update Vegan-tab 5.1 and the sound was working, i watched couple of movies, and today evening no sound, tried in setup and no sound.
I was turning sound off/on from the screen unlock, window, by swipe down the speaker icon. Now i have no sound.
I don't know what i did to make the sound goaway.
Update: now i got the sound back, don't know how i got back since i did all the tricks said in this forum.
1. did the settings->volume-> changed all 3 volume increase.
2. reboot may times.
don;t remember the order. so don't know which one cleared it.
So far I have not run into the no sound problem with b5.1. I sure hope it doesn't crop up because I leave today for a week long trip.
Last night i had installed FRING and Yahoo Instant Messenger, with the Voice/video add-on. And my media volume was muted, couldn't get it to go up. Even when going into setting, and increasing it, it wouldn't increase. I uninstalled those programs and it started working again after a reboot. Running VEGAN 5.2.
"Long-pressing" Bluetooth earpiece call button is no longer launching "Voice Talk". I can't get any help from Samsung or AT&T. All I can find through Google searching are people trying to disable the feature. But I like it, and I want it back. I thought I might have accidentally messed up a setting, but after factory resetting the phone it's still not working. How can it go from working, to not working? I'm still using the same brand new Plantronics Bluetooth I was using when it was working. Thanks for the help.
I have noticed this also. I'm on s8 and assumed it had something to do with the custom ROM but maybe not. I hope someone knows more than we do and knows how to fix it.
I figured out my problem. I had installed BTmono, to listen to music through the earpiece. Once I uninstalled it, all went back to normal. Try looking for any Bluetooth related programs you may have installed.
Sent from my SAMSUNG-SGH-I777 using XDA App
Recently my phone has decided that it will allow me to call other phones but it won't let me hear the other person or speak to them. Every other voice activated application works and as do the speakers, it is only during phone calls. I have tried resetting the phone but the problem persists. I was using Omega v26 and have recently upgraded to v27. Does anyone have a solution, or know where to find the thread that deals with this problem? I have had a look, but there is always the chance that i missed something.
I restored an Omega V13 backup and the problem seems to have disappeared. I still have no idea what went wrong. I'll try reflashing one of the jelly bean roms and see if the problem returns.
Hey, i am currently having the same problem. i could hear the other person, but they cant hear me, and sometimes i cant hear them as well. but other voice apps such as viber and skype both can work. i recently tried to install Ressurection Remix but failed to boot, then i restored to the backup i put in place before. any help?
I have been rooting and installing custom roms for a while. I'm no expert, but now newb either. I recently rooted my S4. It's running on the stock verizon ME7 build.
The problem I have been having is that a few minutes after I reboot it all the sounds stop working. No music, notification or in call sounds. If I restart it goes away for a little while, but soon comes back. I tried factory defaulting it, which worked for a little while, but it recently started doing it again. The only thing I can think of is I installed avast Anti-theft with root access recently. Has anyone else had this problem & do you know of a solution? I can always try factory defaulting it again to see if that helps, but I would like to know if anyone else has any ideas.
Odined back
I tried everything I could thing of, then decided to Odin back to stock. Same problem started almost immediately . There are no system sounds and I can not hear anything when I call. Also it does not pick up sounds from my voice via voice commands & the person on the other end of my calls can not hear me. At this point I wonder if blocking is some how activated. Since Verizon was nice enough to prevent me from making changes to it I can't check.... Upwards on onward. I will keep this updated in-case someone else has this problem.
I have noticed that when I am in recovery, if I try to wipe the cache partition. I get a android on his back with a triangle exclamation point & then it reboots itself... Is this normal. I have never experienced this behavior before.
I installed the blocking mode MOD. It does not seem to be the problem. No sounds after using the phone for a few minutes. I guess its time to send it back. I really enjoyed the phone. But I seems like a received a bad one. Unless anyone has anythoughts.
When your sound stops have you tried to see if it is working with headphones or Bluetooth? If there is no sound using headphones or a Bluetooth device there's probably an issue with the phone itself. If you've done a stock Odin flash and its still doing it, I would have to guess the phone is bad. Send it back. The only problem you might have is if they check the flash count, you may end up paying for a new phone. I've never had to use Triangle Away to reset my flash counter, but I believe it needs to be flashed in a custom recovery (which you don't have).
Sent from my SCH-I545 using Tapatalk 4
My calls are always on speakerphone, doesn't matter if the speakerphone button is on or not, I don't believe this is a hardware problem even though my screen was replaced a few days ago, I mean how could it possibly be. I can't be the only one with this problem, I have searched everywhere, seems like I am. I'm running stock (rooted) so I don't believe it is a software problem either, I have tried rebooting and clearing cache so far.
Details: Stock E2303 MM Rooted. Only thing that could be screwing with audio is Viper4Android, and I uninstalled its drivers already. Also the headphone jack is dead if it matters.
Sorry for creating thread ahead of time, but the problem has been fixed by flashing stock using Flashtool, incase someone has the same problem.