I suddenly have no sound while doing screen mirroring with my Samsung ShareCast Hub. It was working fine, and then it just stopped outputting sound. I have verified that the device is working properly with my girlfriends Note 2. All other sound components working properly, verified with MHL adapter, headphones, and built-in speaker. All video streaming looks normal, as it did before the issue. I think it stopped working after an xposed framework update, but I forgot to take a backup. I am currently running 4.4.2 stock NC1 Rom and have verified every audio setting that I can think of but can't get it to work. I'm thinking that I may need to replace some of the screen mirroring components at the OS level from the original files, but I've not done much modification of this type before and could use some guidance.
Related
I have a Archos Gamepad running the stock ROM. When I boot the device, the sound works perfectly fine. But as soon as the tablet goes to sleep, the sound stops working. No output from the speakers or headphone jack.
The only way to get it working again is to reboot the tablet. Has anyone heard of this happening before and is there any fix?
I have the Virgin Mobile version. Android 4.4.2 rooted with towel root. knox bootloader not tripped.
I have no media volume from my external speaker. I does produce sound such as ringtone, alarms, notifications and system sounds without problems.
I have media sound from my external speaker for about 30sec on boot but it stops working after about 30 sec.
It was working fine until I installed the xposed modules, android apps theme engine, android theme engine, youtube ad blocker, app ops, and the download bar tweak.
I played with all of them then realized I had no external volume. My headphone jack works fine. xposed framework had been installed with other modules without any problems.
I tried uninstalling the newly installed xposed modules one at a time and rebooting in between but nothing fixes the problem.
What is going on? How do I fix it? Why do I have sound for about 30 sec on boot then lose it?
I figured it out. I assumed because I had been playing with xposed framework that I had messed something up. I was wrong.
I blew out the headphone jack with compressed air and all is well. Must have had something in there I couldn't see.
Hey all. I'm a new LeEco Pro3 user, and I've noticed a weird issue: audio output through headphones will stop working after a few hours of not using it.
Basically, you can connect your headphone adapter with your headphones plugged in, play an audio file, and it will play through the speakers instead of through your headphones. Unplugging and replugging doesn't fix it. Raising or lowering the volume doesn't fix it. It cannot play audio through the headphones unless you reboot the phone.
I don't know what triggers it. All I know is, when this issue pops up, the the "Sounds and Vibration" sections of the Settings app crashes. When you try to enter it, you'll go to a black screen. Which is very, very weird. Could it be due to the USB-C audio driver crashing? What could cause it to crash?
The only solution is rebooting the phone. I really don't want to do that every time it crashes, as it has crashed on me 3 times so far in the past few weeks. :/ It actually started the second week I received the phone. I hadn't listened to music in a while, so I went to connect my headphones, and... lo and behold, it refused to play audio through the headphones no matter what I did. But the first time the issue occurred, I didn't bother going into the Settings app, which was stupid of me. I should have checked to see if the Settings app's Sound section crashed on me or not.
I have Dolby Atmos disabled, though CDLA headphones show up as "enabled" in the Sound section, but grayed out, so I can't disable that option. Dunno why. I have the stock equalizer disabled in Settings, and I don't use an equalizer in my music app. Maybe the CDLA option is causing audio to crash...?
I'm running 6.0.1 on the Banggood vendor ROM. No issues on the ROM, other than this audio issue. I don't even know if it's a software issue or not, could be a hardware issue, or an issue with the USB-C standard itself. After all, even the Pixel and the iPhone 7 have this issue and similar issues. I checked Apple's forums and some people are complaining that the Lightning adapter doesn't always work, or cuts out, and only unplugging and replugging it, or rebooting the phone fixed headphone audio. As for the Pixel, apparently some Pixels didn't charge until they were rebooted. But a software update fixed this(?)
I even saw a similar issue affecting the LeEco Pro3, same as the Pixel--some Pro3s won't charge unless they're rebooting, and someone on here mentioned a kernel fix for it. Something about a USB-C controller going haywire. But that fix is only for the x720, and I have the x722. I haven't had any charging issues so far, just headphone issues. Keeping my fingers crossed.
I'm thinking this is one of 3 things:
-Software issue with the ROM I'm running, or a kernel issue
-Issue with the dongle itself (I'm using the one I got in the box; i.e. the legit one)
-Issue with the USB-C port (could be loose, could be damaged; I cleaned it out, it's perfectly clean)
I'm leaning towards a software issue, if only because the "Sounds and Vibration" setting crashes when the issue occurs. If it was a hardware issue, surely the ROM would behave normally. Then again, what do I know, I'm no dev!
Anyone else having audio issues with their Pro3? I don't want to switch to Bluetooth because I have perfectly good headphones already, plus I would hate having another thing around to charge.
I'll try to take a video of the issue once it occurs again, but weirdly enough, it only happens when I'm preparing to leave for work. Hasn't happened to me at home once. I just don't get it.
oops posted on wrong board somehow
Can someone move to galaxy s5e?
Recently on my husband's tab the audio has been out of sync from video.
Specially on YouTube the audio is in FRONT of the video which is weird.
It's all stock firmware etc. Latest updates. Running build ending in AESB
One UI version 1.1
Android 9
Rebooting fixes for a little bit but then it just comes back
Have cleared cache etc
Any ideas?
nikkitaw said:
oops posted on wrong board somehow
Can someone move to galaxy s5e?
Recently on my husband's tab the audio has been out of sync from video.
Specially on YouTube the audio is in FRONT of the video which is weird.
It's all stock firmware etc. Latest updates. Running build ending in AESB
One UI version 1.1
Android 9
Rebooting fixes for a little bit but then it just comes back
Have cleared cache etc
Any ideas?
Click to expand...
Click to collapse
same here. WIFI version of tablet. after reboot jus until tablet goes to sleep all is ok. after wake up, video and audio is out of sync... any ideas how to fix this ?
Uninstall YouTube completely from Playstore?
Or to test audio video stack: find an audio Bluetooth device, connect it with the tablet. Is the audio and video still out of sync? Even over Bluetooth?
Since there are several audio routes in Android, temporarily using and testing might give information.
I don't have it with either normal speakers or Bluetooth.
Happened to me before. Disappeared after reboot.
It happened on mine when using HD HomeRun
Reboot helps somewhat
I am not sure if Dolby Atmos options for better sound is involved. However since Android audio stack is difficult to understand, I would like you to ask:
What happens if you turn on/off Dolby Atmos in Sound Advanced options?
Here how I discovered there is a bug in using Dolby Atmos for me too. Others reported this bug also.
https://forum.xda-developers.com/showthread.php?t=3847815
My mobile was working well until I updated it to V-063 (I know Im a bit late )
After the update, No audio device is working. No speaker output or mic input, Cant play any Audio or Video in any app whatsoever. Not even the headphone jack is working
Tried 3 Custom Roms and older stock ROMs by AFT(334 & etc) and even flashed Viper and Dolby but still nothing.
Someone had a similar issue in 2018 but that threat is not solved till now (He might have had warranty at that time)
Please suggest any possible solution that I might have missed or suggestions :fingers-crossed: