Hi,
My Safestrap rooted phone started having call audio problems soon or immediately after upgrading from 4.4.2 to 4.4.4 (I337UCUFNJ4 ATT stock rooted ROM). I also installed Wanam Xposed and DroidWall and a few other utilities at the time. I since disabled Wanam Xposed in the framework. I finally figured out how to duplicate the problem reliably:
1. Reboot phone to start from known state. NOTE: failure even happens in Safe Mode!
2. Connect to bluetooth car stereo or Motorola earpiece (Media and Phone)
3. Make a call and everything works normally. Hang up.
4. Make or receive a second call. There is no audio in either direction. However, if I press a number key, I can hear a beep over the bluetooth and the other end hears a tone.
• I have not been able to find any way to get the Phone audio to start working again without rebooting. (ex: I turn bluetooth off and there is still no Phone audio.)
• Turning cellular radio off/on doesn't bring audio back.
• Media audio apps like Music player continue to work.
• It appears I can make calls all day long without bluetooth.
• "OK Google" detection often quits working, but in my short test above it seems to keep working even though Phone audio is not. I'm not 100% sure this is related.
Anybody know what's going on or have debugging suggestions?
Nevermind for now
I bricked my phone trying to restore a Safestrap backup, so for now I've reverted back to 4.4.2. My battery life was horrible in 4.4.4 anyway.
I had the same problem. Go to Google app , menu, settings, voice, ok google detection, turn off from any screen.
Related
Hi everyone,
First off, I'd like to start by wishing to everyone happy Holidays!
I have been literally searching all over the Internet for any information regarding the issue I am about to describe in detail and since no solutiuon was found, there's nothing left for me to do but ask for help, and hopefully get the right answer. That's why I want to be as specific and informative as I can.
The problem I am having is this; I recently purchased a new Jabra Motion bluetooth headset and decided to start using the voice dialing function on my Galaxy S4, since it works very well (when it works) and is really a breeze, especially while driving.
In short, the problem is that the S4 completely loses audio (other party hears nothing as well) after initiating a call, via voice dial commands through any bluetooth headset (I'll get to that). When that happens, the phone has no in-call audio whatsoever (with headset on or off, with speakerphone or earpiece on), no matter how many times I start or receive a call and nothing brings audio back, except a reboot from the i9505's power button menu. All other audio works, like videos, unlock sounds, ringtone, music, even the little chirp right before the other party's phone starts ringing and the hangup chirp can also be heard. The worst part is, that it occurs completely at random, it can happen on the 1st time I voice dial or the 10th time, for example. The problem has not shown itself, when initiating a call normally or picking up with a headset connected, before audio gets lost.
Before purchasing the Jabra Motion I've been using an earliest model Jawbone Icon and had never even tried the voice dialing feature on any previous phones or the S4. After encountering this problem I tried to test whether or not it would happen when using that headset, the result was yes, so it is safe to say it will happen when using any bluetooth headset, with the same randomness.
This is what both headsets launch on the phone, when attempting to voice dial:
View attachment 2474439
The phone itself is a completely stock and un-rooted 16GB Galaxy S4 i9505, running the latest available Jelly Bean 4.3, build: XXUEMJ7.
The headsets are always connected to 2 devices simultaneously (in case that might shed some light)
What I've tried so far (no difference made, at all):
- Toggled bluetooth off and on
- Tried unpairing and re-pairing both headsets on both phones, or only on i9505
- Tried factory resetting both headsets
- Tried to toggle, while in call, between speakerphone, earpiece, headset, turning off headset and all possible combinations
- Removed Jabra companion app and services app, then reinstalled, then tried without the apps installed.
- Cleared cache from both Jabra apps.
- Cleared cache from system apps such as dialer, bluetooth and Google Search.
- Contacted support of both Samsung and Jabra (huge waste of time)
Sorry for the very long post, but I want to be clear and comprehensive as possible. Any help would be highly appreciated.
Please no factory reset suggestions, I am aware of that possibility, but do not want to go through all the trouble to set up tons of apps and stuff again.
Thanks in advance to anyone willing to help!
Anyone?
Please?
I have a stock, non-rooted Verizon GN3, which behaved pretty much flawlessly in general, and with Bluetooth Headsets in particular, prior to the KitKat update.
This behavior occurs with both my BlueAnt S4 Visor device, and a Bose Series 2 Headset. When I turn either on, it quickly connects. With the phone locked, screen off, if I initiate the connection from either device, the Voice Dialer comes up, and I can initiate a call. The call connects, and I can hear and speak through the Bluetooth device. Everything works as expected.
But if I then try to make another call, it takes at least 2 additional tries to get the Voice Dialer to come up. The first time, the screen comes on briefly, then turns off, sometimes with the grey screen preceding the Voice Dialer briefly appearing. After a couple of more tries, the Voice Dialer comes up.
But after I have it place a call, the audio send/receive stays in the phone, and doesn't transfer to the Bluetooth device. This pretty much defeats the purpose of having it in the first place!
If I turn off either Device, turn it on and reconnect, the same cycle starts up again. It works properly the first time, but messes up after that.
With the BlueAnt S4, I removed the pairing from my GN3, effectively deleting the device, and then turned off the phone. I then did a complete reset on the S4. Turned the phone back on, re-paired, but this didn't fix it.
This is extremely annoying, to say the least.
I have examined all my settings, and they seem correct. I went to Google Search settings, Voice settings, and tried it with the Bluetooth headset ('records audio through Bluetooth headset if available') both checked and not checked, and observe the same behavior.
I welcome suggestions on how to fix this, and getting it to work consistently and correctly, as it did before KitKat.
I would consider a factory reset on the GN3, if I were convinced this would fix the problem. But I'd hate to go through that hassle, and encounter the same problem again.
I have noticed several anomalies with the kitkat update. I was hoping there was a way to roll back the update
Sent from my SM-900V, unrooted
Well, I've made some progress, and I think the problem originates in a recent update to "Google Search." I found many reports of Bluetooth related problems that were remedied when the update was rolled back.
So, I went ahead and rolled back the Google Search Update, and in fact, went ahead and Turned if Off completely.
I tried out my Bluetooth Headset (the Bose earpiece, haven't tested on the BlueAnt yet), and it works perfectly, as before. And better yet, when I touch the BT button, S-Voice comes up, rather than the plain Voice Dialer, so I can not only place calls, but initiate navigation, send a text, or whatever I would like to do. And it seems to respond each and every time.
We'll see what happens over time, and if there are any unanticipated consequences to turning Google Search off, but so far so good.
If this turns out to be the answer, it will be a Google Search issue (which would hopefully be fixed over time), rather than a KitKat issue as such.
Randomly when I make calls or receive calls I have no sound. I can't hear them and they can't hear me. Rebooting the phone will fix the issue for a short while. I have been able to reproduce this by connecting to my cars blue tooth and making a call. The 1st call works however all calls after the first call I have no sound again. When the phone in the no sound state (Phone Call) Bluetooth media still works just no sound while in a call. The speakers work because I can play music and the mic still works because I can still record sound. This issue seams to be related to the phone app its self???
My phone is a Samsung S4 (AT&T) with Android 4.4.2 (Rooted via Towelroot) with SuperSU by chain-fire installed.
Here is some of the trouble shooting I have already done.
1. Factory Rest the Phone via Stock Recovery (Still can reproduce the issue)
2. Played around with various settings i.e. Google Now Bluetooth options. Un-paired all Bluetooth devices and then re-paired one to try (Still having same issue)
3. Cleaned out all app cache (Still having same issue)
4. Re-installed pre-installed apps that I removed once rooted.
Long story short, this one has be baffled. The only thing that fixes the issue is re-starting the phone.
Thanks in advance for any assistance
AG007
Same Problem Here, I may have figured it out:
After I rooted I used some apps to auto kill some running, supposedly non-essential apps. This caused my phone call problems, same exact issue as you're having. A reboot fixed it for me as well. I will let you know if it happens again without closing any apps.......
Hello gals and guys, you are my last hope.
I have a Galyxy S7 Edge G935F bought in Germany with no sim lock, i got it with G935FXXU1APAW, updated to G395FXXU1APC8. Yesterday i rooted it with CF-Auto-Root-hero2lte-hero2ltexx-smg935f based on XXU1APBF. I still have stock recovery.
The Problem:
Sometimes, while sleeping, the phone disables all sound.
This happens mostly while recharging, but it happened also while simply sleeping and not recharging. It is not reliably reproducable, sometimes the phone works for 2 or 3 days without the error occurring. Which makes the error very hard to find of course.
Sound off means: No media output is working (games, video, music), notifications are not sounding only vibrate, the phone doesn't ring when someone calls, just vibrates. No calls and notifications means, this is very severe.
When i plug in earphones or headphones, there is also no sound on the headphones. Putting in and pulling out the headphones does not reactivate the sound, so it seems not to be a problem with the headphone jack. The jack is very loose, though, doesnt hold the headphones strongly; but thats another problem.
The sound can be reactivated by the following:
- rebooting
- calling someone (i used to call my provider) or getting called (the first call gets lost, but when i get a second call, it works again)
- i installed an app called SoundAbout, which lets me route the sound to different outputs. I must first route media output to "earpiece" (the small loudspeaker you hold on your ear during calls) and then route the media back to "Speaker". Only this combination reactivates the sound again. Just activating "Speaker" or any other combination like for example first "Wired Phones" and then "Speaker" does not work. It must be "earpiece" and then "Speaker".
What i tried, without success:
- deleted all bluetooth devices
- disabled bluetooth
- enabled "prevent USB audio routing" in dev options
- uninstalled all kinds of apps having to do with sound or lockscreen
- played with all kinds of settings having to do with sound or lockscreen
I searched everywhere. A call to Samsung was not very helpful either. I might have to try a factory reset after all, but even if its good at factory, i still won't know the culprit.
But since the problem can be solved via software, i suspect it is software related or is at least diagnoseable via software.
Of course, it would be insanely awesome when someone could just present me the solution, but i would do all the debugging myself, if i only could.
I am a developer myself, but only on windows. My experiences on linux don't go much further than doing an "ls -la" on commandline and i am a total noob on android. I will not be afraid of using a terminal or adb, as long as i am guided a bit.
I hope, somebody can point me out how to diagnose and this thing.
Can one diagnose the current state of audio routing ? Can i manipulate it via commandline ? Are there other relevant components which i need to query ?
Could i write a script that pulls those queries every minute or so ?
And finally, if the wrong settings are found, are there log files which can point out who messed with those settings. Which apps would you recommend for those actions ?
Thanks to everyone in advance ...
Correction
just getting called doesn't fix anything. Only when i accept the call it gets fixed and then the next call rings again, of course. So this means, while the bug is active, i miss all calls.
Mainly all Viper4Android issues from what I can tell.
These are probably linked to one solution, but being able to fix these problems will be greatly appreciated.
1. As I turn on my phone and continue to plug in my headphones, the phone acts as if there are no headphones plugged, which in then returns me restarting the phone and SOMETIMES it will come up with the headset icon in the statusbar which normally means it is going to work.
2. As in the previous problem I said 'normally means it is going to work' SOMETIMES no sound plays at all from anything, not from speakers not from headphones.
3. Bluetooth. When I turn on and use a Bluetooth speaker, I hear a slight pop from the speaker as it connects and nothing happens then when proceeding to turn off Bluetooth knowing it's not going to work, no audio happens at all leading to me rebooting the phone.
4. And most of all the most annoying thing in somewhat having a working daily driver, whenever in my pocket or FACE UP in a DARK ROOM, the phone will just switch off. Nothing else happens I can't bring it back at all, I just have to hard reset (hold the power button for 20 seconds until it turns back on)
5. (Edit) Also half the time my microphone doesn't work. Leading to me needing to restart my phone.
My Phone:
OnePlus 3t
OOS Beta 10 (7.1.1)
Magisk (13.3)
Viper4Android
"Allow Mediaserver/Audioserver
Emoji One
OOS call recording enabler
ATM I have the Xposed framework because it is pretty stable, but these problems we're here before Xposed framework, so that isn't the issue
Anyone being able to help with these problems will be greatly appreciated
If you need any logcats or whatever just let me know how to do them, and I'll do it for you.
Thank you so much! ~Ryan