I have tried several, including:
Both paranoid android roms
Carbon
AOKP
xone
Liquid smooth
The bluetooth "works", but it takes a lot of fiddling with. Which is fine at times. I am looking for a non touchwiz ROM though that the Bluetooth works better on.
Most of the above I have to dial using the phone because voice dial isn't recognizing a voice or the buttons on my headset/car are not working.
Couple of the above voice works OK but if I listen to music it dorks it up and I have to resync before I can use the phone.
Yes, I am sure it has been asked in some form before and I'm sorry but I could fine any real answers and it has been awhile since it was asked.
Any help or pointing me in the right direction would be most appreciated.
Sent from my GT-N7105 using Tapatalk 2
Spoontain said:
I have tried several, including:
Both paranoid android roms
Carbon
AOKP
xone
Liquid smooth
The bluetooth "works", but it takes a lot of fiddling with. Which is fine at times. I am looking for a non touchwiz ROM though that the Bluetooth works better on.
Click to expand...
Click to collapse
The latest vanilla rootbox works best for me. I use multiple bluetooth devices every day and am constantly switching between the two in my car (one for audio, one for phone), headphones, and a headset, and listening to music and talking on the phone, and I have had the least problems with that rom out of all the non-TW. I think there is a setting to tell the phone to use a bluetooth device for voice commands, but I forget where it is and I don't know if it works (although that may be a TW setting, I forget that too).
Related
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.
Hi everyone,
The bluetooth on my GSIII has been a complete failure. You can follow the saga here (http://www.benzworld.org/forums/w245-b-class/1662643-2009-w245-samsung-galaxy-s-iii.html), but basically it connects to my car and has no sound with the stock ROM and refuses to connect to the car at all with the AOKP JB build. It suggests an android problem, so I'm wondering if the bluetooth stack can be reloaded to reflashed with something different. If anyone has any ideas, I'm all ears. Thank you!
I have a problem with one of my Bluetooth devices dropping and reconnecting. Not sure why is just one. It works fine on an iPhone. I'm guessing your GS3 isn't the international version?
Sent from my SGH-I747M using xda premium
Nope not international, SGH-I747M from Bell.
I'm trying this. Will report back.
evilmonkey1987 said:
I'm trying this. Will report back.
Click to expand...
Click to collapse
Sweet! please let us know!
I'm having a different issue. it connects and stays connected, plays music but it doesn't list the song/artist info on my eclipse screen but the SG2 will..
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
evilmonkey1987 said:
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
Click to expand...
Click to collapse
Try CM9. Bluetooth works much better with it. CM10 should have it fixed as well in a day or two.
Here's a 'six months later' update. My phone went through various android updates and I'm now on Android 4.1.1 (up from 4.0.4). The problem was still not solved, but instead of no audio, I now have one way audio, where people hear me but I don't hear them through bluetooth. I have also gone through a number of custom ROMs and kernels for my phone (including CM9/10 and AOKP) and nothing helped with the issue.
A couple of days ago, my girlfriend's HTC One X (finally!) got its Android update, also from 4.0.4 to 4.1.1. Her phone now works like a charm with the in-car bluetooth.
The solution I ended up with was a car cradle and a couple of NFC tags to control my phone in the car. My NFC tag that's stuck to my car cradle turns off WiFi, starts car mode, starts a car home app and turns my volume to max. All I have to do after that is connect the 3.5mm audio cable and I use my phone in place of the car's infotainment system. That way the phone integrates into the car as well and the only thing I lose are the steering wheel controls (they still work for volume).
My less technologically inclined girlfriend now has everything work auto-magicallly with bluetooth. So I guess all's well that ends well, but to anyone considering a US-spec Galaxy S III, watch out: the bluetooth issue is still not fixed. If bluetooth is critical, consider the HTC One X (but be warned: it has awful battery life!)
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
colbynmeghan said:
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
luncht1me said:
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
Click to expand...
Click to collapse
What's wrong with stock? I have no major issues with streaming BT from my phone to my Mazda 3 head unit, or to my Sony MW600 earphones. Even track titles work (the only thing that doesn't work is time display). In my experience, Bluetooth works best on the stock ROM.
Stock Rogers ROM (DLK4 - JB 4.1.1), rooted
KT747 (1/9/2013) kernel
CWM Recovery 6.0.2.3
PlayerPro Music Player
On my old Xperia X10, I had CM7 and had no end of issues with BT:
- Sometimes it would connect and there would be no sound
- Sometimes it wouldn't connect at all
- Sometimes it would cut out after switching songs
- It would stutter a lot whenever Wi-Fi was enabled (but I think that was a problem with the Xperia).
When I tried CM10.0 on my S3 I had similar connection issues, just not as bad. Also, the volume gain over BT was much lower, so I had to turn the car speakers way up. Stock 4.1.1 doesn't have any of these problems. The only problem I had was the audio switching over to speaker after turning off the car, but I fixed it.
Also, BT is apparently broken in 4.2.1 in general, not just CM10.1. Google confirmed a BT patch that works on the Nexus 7, due for release with 4.2.2: http://www.expertreviews.co.uk/smar...confirms-android-4-2-bluetooth-streaming-flaw
TIP: Don't forget to turn up the volume on your phone. I don't know how many times I accidentally turned down the volume and thought that it wasn't working. Now I have Tasker do it for me whenever I connect. :good:
4.1.2 has Bluetooth working use it everyday. (Stock and ROM.) Can't tell u which combo I use at a time. I flash a different ROM everyday. As 4.2.1bluetooth is broken expect for task's AOKP. He has it workingish.
Now as connecting to a car. Depends on what it connects as. And I've learned going to and from ROMs when u connect a source hit the volume up 9/10 times it works
Sent from my SGH-I747 using Tapatalk 2
I have had a terrible time finding cm10 based roms with working bluetooth. My car stereo might work for 3 or 4 hours but then after a certain ponit all of the roms lately start playing from the phones speaker. Ive tried the latest cm nightly, euroskanks, slimbean, etc.
The only one I can keep working consistently is the slimbean 2.5 with bluetooth on my pioneer deck. Many of the nightly builds from different versions say they have improved bluetooth but I'm still having issues where it decides to switch audio players or won't play through the car deck at all.
So tonight I'm doing a full wipe and reload of the slimbean 2.5 which is frustrating as it's something I need to work as my daily driver. I understand the CM10 is opensource framework and things like bluetooth have to be played with but it feels like they are going backwards with it most of the time. Is there other roms I should be looking at or a universal bluetooth patch that will work on any rom? What is different about slimbean 2.5 that gets my bluetooth working? I figure if I can get some light on the topic that I might be able to get the support I'm after on newer roms myself.
here
This is the specific CM10 commit that got bluetooth working for my audio devices in my car.
cyanogenmod.com/#/c/23361/
Hello all,
Like the title says, do any of the current JB 4.1 ROMS have working bluetooth for phone calls?
I'm currently on SlimBean, and bluetooth will pair with my car, but there is no audio. I can't hear the caller, and they can't hear me. There is some magic happening, because my car will tell me when the call connects and when I hang up.
It did work with LiteRom, so I know BT works in the car, but I am loving the battery life/features of the JB roms. Anybody have suggestions? I suppose I could install every current JB ROM and test, but would like to ask the community before going through that hassle.
Thanks,
I'm on dman's cm10 and my bt headphones work well for calls/music and the music controls (play/pause/skip) all work as well.
Tyfighter said:
I'm on dman's cm10 and my bt headphones work well for calls/music and the music controls (play/pause/skip) all work as well.
Click to expand...
Click to collapse
Appreciate the feedback, unfortunately CM10 didn't work for me either. I ended up loading CM10, CAMP, PAC and SlimBean, none of them had audio on my cars bluetooth. Like I said, it's very close to working. The display in my car will show the number I am dialing or the incoming number, it connects, just no audio at all. I went back to LiteROM and it works as normal. It's a bit of a bummer too, I was really please with AOSP/CM based ROMs, and the battery life was fantastic. Guess I'll have to wait for a few more bugs to get worked out.
By the way, the vehicle is a 2012 Chevrolet, so I would hope that its JB compatible.
Thanks.
Slim had bluetooth working for me, but it took a couple times to pair to my car. You try a full wipe before flashing?
Sent from my SGH-I927 using xda app-developers app
andy775 said:
Slim had bluetooth working for me, but it took a couple times to pair to my car. You try a full wipe before flashing?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
That I did. Old habit of mine, I don't dirty flash anything unless it's an update of the same ROM. Googling the issue seems to show mixed results for JB ROMs based on what kind of device you're pairing with. I have a feeling it's just an issue with BT not being 100%. I can wait patiently while the devs do their magic, just have to stick with ICS until then (have to have the handsfree for driving).
Thumbs up to the devs in this section by the way. My personal phone is an HTC One X. When running CM10 on the Glide, it's easily as fast as my one X.
I'm hoping someone here has a bit of magic mojo that can help me get my S3 with the S3Rx 2.2 ROM (4.1.2) with the Faux123 kernel working with Google Now. I've read every thread I can find, but I still can't get GN to pick up commands via a Bluetooth headset. Using Bluetooth Launcher from the app store, I'm able to launch GN. The "beep" that signals GN is listening is coming through the headset, but it's not picking up what I'm saying. The circle around the mic icon doesn't move, which I'm assuming means it's not picking up any sound.
First, does anyone actually have this working, and please share how you did it.
I really like the TW interface along with motion, smart stay, the lock screen, and other features, so I would prefer to not switch to an AOSP ROM.
Help?
Best regards,
Mike