Develop Bugs

[Q] BlueAnt V1 Headset + Evo

Trying to find some feedback from anyone using the BlueAnt V1 bluetooth headset with the EVO.
I'm having problems with the headset not answering calls maybe 85-90% of the time. It announces there is a call, but will not answer via voice command or hitting the button. I can answer via the phone but when I do it doesn't transfer voice to the headset. The headset thinks it is connected because when the call is ended it tells me.
Have done two factory resets on the phone and resets on the headset with no change. Also spoken to Blueant tech support and they weren't much help. All they said is they haven't heard of it having problems with the EVO and should be compatible with all Android devices. Their suggestion was to try it with another EVO and see if the problem still exists. Well, I don't have another to test it on so that does me no good. This headset worked great on both my Blackberry phones before I got the EVO and has the latest updates installed.
BTW...I'm running Myn's RLS4 w/ #17.
Thanks.

Well I don't think it is the Bluetooth , it is the Rom. I have problems with myns #4 with the sync in my email. I have a blue ant also and it does the same thing . I have tried other roms including virus and it works on them , try that .
sent from the phone that is EVO

Pretty sure I tried this headset when the phone was stock and with some other Sense and non-Sense roms. It has never worked properly.
Not sure if it has something to do with the lockscreen or not. The first time it is connected to the phone it works fine. But every time after that, it doesn't connect the call.
I haven't had any problems running anything on Myn's. But just to make sure, when I switch a rom again I will reset and try the headset.

yeah mine does the same thing, it works if i answer w/ voice command but if i press answer button most of the time the audio is route to phone speaker......Lame!
has anybody with a blueant tried it with cyanogenmod? i wonder if the different bluetooth stack yields different results. I'd like to see an app update for the blueant software too (had a cheaper headset that stayed connected way better)

When I pair the headset, it connects and works great the first call I get whether using voice command or button to answer. Then every time after that, it won't connect the call.
Maybe it has something to do with the lockscreen or the phone going to sleep. I will have to do some trial and error.

Currently I am trying out the headset with MikFroyo 4.2 (Sense rom) to see if it makes any difference. This rom is really close to stock so maybe it will work?
I will post back with my conclusion.

My headset works fine now. I have found there is a coding issue that exists in certain roms such as Myn's and CM that prevent proper operation. CM seems to have put together a fix for it. Myn's still does not work at this time. It has been requested as a fix for RLS5 final.
Running eVoKINGS Black Titanium with Mik's 4.2 base and my headset works good.

hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.

jbrazee said:
hey where is the fix for CM or is it just in some of the versions? cause i just flashed CM7 and some of the features i loved about the Blue Ant before are not working like it will not play my audio like it did before i use to be able to listen to my music and what not through the blue tooth. if there is a fix for it i would love to get that working again.
Click to expand...
Click to collapse
Sorry...it's been a while and can't remember where I read about the fix. If I run across again will let you know. Might try downloading "BT mono" from the Market to see if that helps. Not sure if it is effective on AOSP or not but worth a look.

Bluetooth problem!! Can anyone help?

Hi guys,
Because of this problem I get almost sorry that I had taken a Galaxy Nexus.
I can pair Nexus with my carkit (parrot) and I can play audio through the speakers.
My problem is: When I call or receive a call I can hear almost nothing. Sound is so low that I can not even notice that the sound from the speakers or coming from the phone. I am using Volume+ too but nothing helps!!
It's look like that Nexus somehow even loses the connection, without any reason.
It's a rooted Nexus and running on AOKP.
Is there a better ROM for my bluetooth issue or do you guys have any suggestions?
Thanks in advance..

No one??
Has nobody has an idea or experince with this??

The market description for Volume+ says:
A Cyanogen Mod 7 or MIUI ROM is HIGHLY recommended. Running this app on a Stock ROM/Kernel may result in it not working, being far too quiet, or getting even quieter. PLEASE don't comment or rate badly if you are on a Stock ROM as this is most likely the problem.
Click to expand...
Click to collapse
The feature list for AOKP says it uses the "Unsecure boot.img (stock AOSP kernel)."
You might want to try uninstalling the application to see if that fixes your sound issues over bluetooth.

I am using a stock (unrooted) GSM Galaxy Nexus. It pairs just fine with my Jawbone Era bluetooth headset and do not have an issue when making/receiving calls with volume. Where I notice the volume is quite low is the voice dialer prompt only (the actually call is fine). Apart from that, no issues.

miui..
Hi guys,
Thanks for your replies.
I flashed the rom of miui and it's seems to work till now. So this rom dealing better with bluetooth.

[Q] Wicked ROMs and Bluetooth connection call connection

Had Wicked V3 installed and then upgraded to V5. Both ROMs exhibit the same Bluetooth issue - when it connects to my car amp or my headset, it's like it has answered a call.
I see a counter on my car's amp display and can't switch modes on it until I go to the phone and originate a call then hang up. After that, all works fine.
I thought it was a problem with the phone since I installed Wicked only a couple of days after I got it. Using the cool installer with V5, I tried a couple of different kernels (Faux and Trinity), but both seemed to act the same way.
To confirm it's an issue with software instead of hardware, I restored the stock ROM and it connected and worked normally.
I really like Wicked! But this glitch with the Bluetooth may be a deal breaker for me. Is there something I can do to make this work properly?
Thanks!
DownloadBob

Bit finally fell into the bucket?
downloadbob said:
Had Wicked V3 installed and then upgraded to V5. Both ROMs exhibit the same Bluetooth issue - when it connects to my car amp or my headset, it's like it has answered a call.
I see a counter on my car's amp display and can't switch modes on it until I go to the phone and originate a call then hang up. After that, all works fine.
I thought it was a problem with the phone since I installed Wicked only a couple of days after I got it. Using the cool installer with V5, I tried a couple of different kernels (Faux and Trinity), but both seemed to act the same way.
To confirm it's an issue with software instead of hardware, I restored the stock ROM and it connected and worked normally.
I really like Wicked! But this glitch with the Bluetooth may be a deal breaker for me. Is there something I can do to make this work properly?
Thanks!
DownloadBob
Click to expand...
Click to collapse
After all my testing with stock, restored back to Wicked V5 but forgot to wipe anything. Tried to connect to car amp but no luck. After struggling with it a bit, finally got it to pair/connect.
For some reason, now it's working as it should! Beats me why, but I'll take it!
Don't know if this will help anyone else, but this is my experience!
Good Luck!
DownloadBob

[Q] Headset Issues

Hi All,
I've been looking all over the forums, so forgive me if I missed something.
I'm running P.A.C. 19.3.0 by ChillyBean and have been loving it, at least for the last couple of days that I have been using it. My issue is this, when I attempt to use a wired headset it will work if I turn on the speaker phone and back off, but sometimes it will just "freak" out and start screaming and making terrible noises. After that it seems to also mess with the non-headset mic as well, at least until I'm able to toggle the speaker phone again.
Is this an issue that anyone has had any luck working with? I've tried three different headsets with the same issues. I really want to stay with the ROM, but having a little more stable headset is kind of a big deal for me. It isn't a huge deal to have to toggle the speaker phone and I realize that, just hoping to not have to do that.
If I just need to go to Chilly's CM10 or PA ROM I am okay with that, I would really just like to have that issue resolved
Kernel: 2.6.35.14-ae-15 [email protected] #1
Thanks!
Nick

Bluetooth phone call issues in car

Hey there,
I'm currently running a OP3 with the OmniDragon 8.1 ROM and previously the ResurrectionRemix ROM. However, I do not believe this issue to be a ROM issue so that's why I'm posting here instead.
I've recently been having some issues with bluetooth and was hoping someone could help. I can connect my phone to my cars handsfree system perfectly fine and it works correctly. I can play music via Spotify and any other music player fine.
However, as soon as I make or receive a phone call I'm left where the person can't hear me, and I can't hear them. I can't even hear the ringing tone when phoning someone. However, as soon as I turn it from bluetooth back to the phone or just regular speaker, it works fine.
This previously was not the case when I was running Nougat.
But as soon as I upgraded to 8.1 this issue started happening.
I don't think it has anything to do with the ROM and is actually something to do with perhaps OP3 Firmware/Modem or something similar.
Car hands free works fine with other phones like an iPhone, so that's out of the question.
I've attached a catlog to this post from when this issue was happening in the car, so hopefully someone can narrow it down for me.
Any help is appreciated!

Actually many roms have been having issues with BT calls. It's due to some of the changes in the telephony package.

Hello, did you manage to find any Oreo rom that fixed this issue for you? Would appreciate any tips.
I too have had similar issues with Oreo and OnePlus 3. Using an handsfree Jabra Freeway and the microphone often does not work when I answer or phone someone during a drive. Which is extremely annoying and dangerous.
I had hopes that with the release of some alpha Android Pie roms, these BT issues would be fixed. But the issue seem to persist, at least for my device.
My only fix was to go back to nougat. The most stable rom i've found is the unofficial lineage 14.1 by sultan. This have been my daily driver for awhile now and seems to work fine.