Develop Bugs

Bluetooth phone function not working?!?!?!?

My HTC Incredible was working perfectly with my bluetooth car stereo up until about a month or so ago. The weird thing is now it will still pair properly with my car stereo and I am able to play music from my phone through the car stereo but when making or receiving phone calls it will not make any sound through the stereo or speakers.
It will place the call, the other person will be able to pick up and receive the call but they can't hear anything I am saying and I can't hear anything they are saying.
This used to work perfectly before and what's baffling me is I can still play music from my phone with the bluetooth fine without any issues.
I have an AMOLED screen incredible running 2.2 and Unrevoked. I installed Skyraider 3.5 (most current one whatever that is) I have used Metamorph to place my handcent where the + symbol is on the bottom rosie bar, I have also flashed the Berzerker mod for splash of red to make everything red and also provide 6 signal bars instead of 4. I am also running KingKlix BFS#6 kernel. Other than that everything is unchanged.
I have also tried to pair with other car stereo's with the same outcome. What did I do and how can I get this to work again? Is there a bluetooth folder on the system files that I can check to see if there is a change in there or something? Any help with this would be greatly appreciated. Thank you in advance!

GatorsUF said:
Click to expand...
Click to collapse
I don't think break dancing is gonna fix my bluetooth thanks though

1967ls2 said:
My HTC Incredible was working perfectly with my bluetooth car stereo up until about a month or so ago. The weird thing is now it will still pair properly with my car stereo and I am able to play music from my phone through the car stereo but when making or receiving phone calls it will not make any sound through the stereo or speakers.
It will place the call, the other person will be able to pick up and receive the call but they can't hear anything I am saying and I can't hear anything they are saying.
This used to work perfectly before and what's baffling me is I can still play music from my phone with the bluetooth fine without any issues.
I have an AMOLED screen incredible running 2.2 and Unrevoked. I installed Skyraider 3.5 (most current one whatever that is) I have used Metamorph to place my handcent where the + symbol is on the bottom rosie bar, I have also flashed the Berzerker mod for splash of red to make everything red and also provide 6 signal bars instead of 4. I am also running KingKlix BFS#6 kernel. Other than that everything is unchanged.
I have also tried to pair with other car stereo's with the same outcome. What did I do and how can I get this to work again? Is there a bluetooth folder on the system files that I can check to see if there is a change in there or something? Any help with this would be greatly appreciated. Thank you in advance!
Click to expand...
Click to collapse
This is not development related. Might fit better in Q&A.
Have you tried a wipe and reflash of the ROM? Or wipe/flash a different ROM? You likely downloaded/flashed something funky thats messing with it. Even a VZW rep will tell you thats the first step in troubleshooting any issues. If all else fails, RUU back to stock. If it still isn't working properly, you have something wrong with your device and it needs to be sent back for warranty.
Furthermore, I would recommend not making any manual edits to /system. Although you're not likely to brick your device doing so, you're going to cause yourself more trouble and likely break other things in an attempt to fix bluetooth.

I will try to go back to stock & then keep adding things until it no longer works. Hopefully once I go back to stock it works again.

You might try Bluetooth Fix Repair from Market. Delete the pairing from the car bluetooth first then run the Bluetooth Fix Repair on the Incredible then re-pair. This has helped me when phone would not connect before and hopefully will help you.
Doc

I completely unrooted my phone and went back to OEM. Tried to connect the phone to the bluetooth with the same outcome.
It is definitely a hardware issue with the phone and not any software issue.
I contacted Verizon they sent me a new one over night and just finished rooting it and running my last nandroid to it. I am back where I began with everything loaded back up properly the way it was. This one also works perfectly with Bluetooth!

Glad you got it resolved.
Doc

simultaneous bluetooth A2DP and HFP issue

i believe there is a bug in either the GNex's bluetooth hardware or Android ICS.
i have an A2DP adapter in my car to play music from my phone on my car stereo. my car also comes with the ability to connect to a phone for the purpose of taking and making calls thru its stereo and mics (using bluetooth HFP). when both are enabled simultaneously, i am able to listen to my music fine. if i get or make a call, the phone pauses the music, as you would expect, and goes into the call (although when i receive calls there seems to be a delay before the GNex switches over), but in the call the audio is garbled/robotic/scrambled...whatever you want to call it. this is the case both for what i hear and for what the person at the other end hears.
i wanted to start this thread to get more info about this problem from others that have experienced it, and maybe see if we can come up with a workaround.
there is an AC thread about this here:
http://androidforums.com/samsung-galaxy-nexus/524885-galaxy-nexus-bluetooth-bug.html
and i put in a bug at google here:
http://code.google.com/p/android/issues/detail?id=29564
any more info is appreciated!

According to other posts in the forums, the AOKP ROM does not have these issues.
I really did not want to root this device. I know, that's just not cool. But everything else was just working.
My Sensation did not have these problems, but alas I dropped it and it died and I was still on contract. The Nexus was more cost effective than bending over for the off-contract price from TMO.
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.

I would be kind of surprised if it didn't exist in AOKP, because the problem definitely exists in CyanogenMod 9 (and AOKP is essentially a kang of that). In fact, I uninstalled CM9 and reverted to stock expressedly because I initially thought that this bug was a CM9 issue and it was annoying enough that I figured I'd revert to stock until CM9 reaches stable, only to discover that the problem is in the official Google builds as well.

ianken said:
Anyway, chalk me up as a "me too" on this issue. I'm going to root tonight and try AOKP.
Click to expand...
Click to collapse
Please let us know how it goes! I've been using Bugless Beast, but would switch to AOKP if it fixes this bug.

I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.

ianken said:
I've yet to find a build without BT issues of some sort.
The garbled call audio is new to me. I've not see that on other devices but have yet to find a GN ROM that mitigates it. This is in addition to issues that go back to the Nexus 1. There was an audio.conf fix for that, I'll see if I can wrangle it up and see if it helps here.
My setup: Factory BT hands free (crap Audi OEM goo) + FIPO A2DP device for music. So, two completely discrete BT devices.
Edit:
try this: edit etc/bluetooth/audio.conf and set master=true (backup the file first)
I also set HFP=true (it's commented out in the file)
What I found:
1- Calling: audio quality was still pretty poor with a lot of pops. It sounds a bit "hot." Quite inferior to other devices I've used with this setup.
2- However: A2DP playback no longer glitches. In my case audio played fine after the first connect after BT was turned on. But subsequent connects, say after leaving and the returning to the car would result in glitchy audio.
So far this tweak seems to have improved things. I'm really bummed by the audio all quality.
Click to expand...
Click to collapse
audio.conf does not seem to exists in 4.2.2. Has anyone found audio.conf in 4.2.2?

[REQ] Running a custom ROM? Could you check something for me?

Hello all --
I'm trying to check if a problem I'm having with my S3 is hardware or software (and see therefore if it's possible to fix.)
If you're running a custom ROM and have a car with Bluetooth and a stereo with an Aux in:
-Connect your phone to the stereo via the proper cable and start listening to music
-Turn on Bluetooth
Try to make a call (or receive one) via Bluetooth.
With the stock firmware, the music cuts off when a call comes in or goes out, but you can't hear the caller (and they can't hear you).
I'd like to know if this is the case with custom ROMs for the S3, or if it's a unique problem with the stock software.
Thanks for your help!

Can anyone confirm? Seems like a pretty common issue, but I can't get Samsung or Sprint to give an answer on whether it can be fixed or not...

zipr said:
Can anyone confirm? Seems like a pretty common issue, but I can't get Samsung or Sprint to give an answer on whether it can be fixed or not...
Click to expand...
Click to collapse
i can try to verify this in either a couple hours or tomorrow morning at latest.

Does not happen for me, but I am running custom rom. FreeGS3

Thanks Naddict -- so you can listen to music via the headphone jack and make calls over bluetooth at the same time? Good to know -- and it gives me hope that hands-free calling may be possible on my S3.

sqwigy224 said:
i can try to verify this in either a couple hours or tomorrow morning at latest.
Click to expand...
Click to collapse
Thanks -- appreciate you taking the time to help me out!

Np... I did see another post somewhere in here... About blue tooth 4.0 issues... Might want to poke around some more...
Sent from my SPH-L710 using xda premium

[Q] S3 4.3 AT&T S-voice no longer works with Bluetooth mic.

Well, I dug myself a hole by allowing the OTA to 4.3.
On my AT&T S3, SGH I747, I was running 4.1.1 stock rooted, with a toggles mod, and the At&T update got pushed to the phone one night. It could not get past TWRP so I swapped back to a stock recovery. The update ran again, and failed at about 25%. I didn't think anything of it since the phone worked fine, until I discovered that I could no longer change the icons on the lock screen (settings would stop working). So, I installed Kies (which it turns out will not connect over a USB 3.0 port, but thats another wasted couple of hours and another story) and backed up my accounts, settings, etc.
I then flashed to a stock 4.1.1, and then allowed the OTA update to 4.3. This time it went (Yay..sort of).
So, I'm looking at the new features, and finding some useful and overall enjoying thew update, but ran into trouble with S-voice and bluetooth, specifically, the microphone in my car. This used to work. I could press the mic button on the cars Nav unit (Parrot BT) and I could say "call "X" mobile" or "play Concrete Blond" and the phone would do what I told it to, more or less.
Now, It will not connect to the mic, I get a brief message "Check in-car audio" and after 3 seconds the car reverts to playing music (it mutes when you press the mic button). The other BT functions work. My contacts are transferred, I can force music to the unit, I can place calls and we can hear each other, etc.
After a bit of reasoning, I began to zero in on S-voice as the culprit. I confirmed this by installing Bluetooth connect and pointing to Google search when the mic button is pressed. This allows me to make calls via voice command, but that's all.
I used this feature a lot., probably 3rd or 4th down on my priority list, after phone and camera. I'd like to use it again.
Here are my options as I see them.
-Leave well enough alone and wait for Sammy, or my Navs mfg to fix their stuff and use google search instead for now. (Will they do it faster if I hold my breath?)
-find a 3rd part app to make S-voice do what its frikken supposed to do. (Not sure if their is one)
-find an older version of s-voice and install it over the current one, which may or may not work. This would require that I have a working backup plan in place and since I understand that the bootloader I now have (MJB) is a one way trip, this limits my options. (can't flash back to 4.1.1 and don't have a 4.3)
So... does anyone have..
-any sympathy? (It's Christmas day)
-a solution to my problem?
-a recommended app to patch this?
-an older version of S-Voice form a S3 phone?
-info on any of the 4.3 roms floating around (can they be installed over a stock 4.3?)

I'm having the same problem. I didn't know S-Voice was broken until I did a factory reset last week to fix problems with T-Mobile wifi calling. I had been using Utter! for voice control, which has pretty good voice recognition, but randomly stops working with bluetooth. Since I hadn't tried S-Voice for a long time, I wanted to see if there had been any improvements. Once bluetooth is connected, the S-Voice mic button is disabled and the bluetooth button has no effect on it. I may end up going back to Utter!. Unfortunate, since almost every option except S-Voice is just too open-ended for use in the car. I don't want to ever be required to look at or touch the screen. For all the complaints I have seen, nothing can top Sync in my Ford. Voice recognition is excellent and everything can be done by voice.

well, I'm glad at least I'm not the only one. after some experimentation, I bought an app called Klets, which works with specific music players, Poweramp being one, so I got it as well. I had no luck with utter.
Klets works using google's voice recognition engine and works well. You can add custom commands to the already huge list it has. Well worth 2 bucks! Like all VR apps, it has issues with background noise. It is also written by an Italian, so some of the translations are a bit off. When calling a contact, you get "I'm starting to call towards (contact)"
Poweramp also has the advantage of boosting the volume a bit, which helps with the car since the input volume for BT is set so low, or BT output is low. Either way, it helps. Plays FLAC too.

[Q] Sound + Root Issues on Z1C

Hey folks,
So I have a problem with my Sony Xperia Z1C (D5503), and would appreciate some input on my theories as to how to fix it, at which I have yet to be successful.
I live in China, and I bought my lovely device on Taobao a few months back for a very discounted price (risky, of course, and to be certain this is where the issues stem from). I purchased the Hong Kong version instead of the Chinese version, because the Chinese version is built to block Google Play by default and comes with a bunch of junk apps. Anyway, I was stupid and didn't get a chance to use it before the seller's 7-day return policy was up, so it was too late for a return after I found out about its issue.
The issue is this: when I receive a call, the caller cannot hear my voice. Not that it's completely silent, it's just muffled and quiet. I've tried various things, turning on and off the Microphone Noise Suppression option, adjusting the caller's sound options, but nothing; it seems there's a defect with the microphone. When I switch to speakerphone during a call, however, there are no problems. On a related note, the same thing is true when I use apps like Skype and particularly WeChat: if I send someone a voice message, they can barely hear me. Only when I use a headset are there no problems. So, to continue using this phone, I've succumbed to bringing my headphones around with me and plug them in when I receive calls or have to send a voice message.
So the microphone's screwy? Interestingly, when I record with other apps, like the Sound Recorder app, there are no problems. It picks everything up perfectly. It must be recording on "speakerphone" for this app, if that makes sense; right?
Anyway, I was wondering (hoping) if the kernel loaded on my phone has anything to do with it. It's the stock kernel but one that seems to be used more for the Xperia Z1. Since I'm mentioning it, here are all the specs:
Model: D5503
Android Version: 4.4.4
Baseband version: 8974-AAAAANAZQ-10270054-61
Kernel version: 3.4.0-perf-gaee6e5a [email protected] #1 Thu Oct 9 09:14:33 2014
Build Number: 14.4.A.0.157
Anyway, I still have this hope that the problem is fixable. I am inclined to wait for the rollout of Lollipop for the Z1C, but that could be months, and this has been going on long enough as it is.
I'd appreciate any input, especially if you think I'm on (or not on) the right track thinking that flashing a new kernel may make a difference, assuming it is a conflict with the firmware. Or, perhaps I should just accept that I was sold a defective product for a decent price (I mean, everything else is working OK...).
Should also add, running the service diagnostic test for both primary and secondary microphones provides clear, audible results.
A few additional details, that may be of interest: my phone is rooted, with SuperSU as the app. The stock version of the app is a system app, but when I update the app, it loses its system app status and also does not successfully update the binary. I couldn't install busybox for the longest time but was finally able to do so through the advanced root options FlashTool. This is interesting, I think. Also, there is no recovery mode.
Thanks for your time!

jujube123 said:
So the microphone's screwy? !
Click to expand...
Click to collapse
Looking at the Sony forums there are a lot of complaints about muffled calls and poor microphone on voice calls, with no comment from any Sony moderators, which isn't a good sign.
One suggestion was to turn off the "Microphone noise suppression" option in call settings. Another was to not have the call on speakerphone.
Someone else suggested editing build prop, which if you've got a rooted phone should be easy.
persist.audio.fluence.voicecall : false
I think this turns the audio post processing off.
You should get recovery working, try installing the latest recovery from NUTs dev page, this installs from your PC. This will help you get a working SuperSU as it will restart in recovery mode.
The file you are looking for is called
Z1C-lockeddualrecovery2.8.2-RELEASE.installer.zip
Once you have recovery you could do a nandroid backup and experiment with a factory reset.
If all that fails, it looks like it's a problem limited to Sony stock builds, so it might be worth experimenting putting a CM rom on your phone. Obviously read up on how to do this properly, and make a copy of your TA partition so you can back to stock if you change your mind.
This page is a good place to start.