TL;DR
G2X w/ CM7 Bluetooth Streaming media text (track info) works, but calling doesn't
G2X w/ 21Y Bluetooth calling works, but streaming media text doesn't.
Is there a way to fix one or the other?
Hello,
I have a T-Mobile G2X and use a base install of CM7 with gapps.
I recently purchased a Pioneer FH-X700BT stereo receiver for my vehicle. The nice gentleman who installed it briefly went over the features including the bluetooth. When using the bluetooth media streaming it worked superbly. Whether I used the device music player, Google Music or Akimbo (for my audiobooks) the song track / artist info is displayed. However when he attempted to use the bluetooth calling features there was just hissing and static. He wasn't able to figure out why this was and showed me how it functioned correctly with his blackberry phone. I figured: "well crap, maybe there is finally a reason not to use CM7 on my phone."
After returning home I reverted my phone back to a backup of 21Y. Bluetooth calling works great, but now my media info is no longer displayed. Back and forth, same problems.
After searching on XDA I came across the New Baseband Fix (http://forum.xda-developers.com/showthread.php?t=1776843) thinking it might be related, but alas no such luck.
It seems I can have bluetooth calling or bluetooth media info, but I would like both (even if I have to use stock). Is there an app that will make sure my track info is streamed while using stock? Is there a ROM that has both bluetooth calling and track info streaming?
Thank you for your assistance,
BigRedOgre
Yes this is a problem with the new baseband (March 2012) I don't think there's a fix for it yet. There's a few methods to downgrade back to the old baseband where it was working but it's sorta hit or miss. A lot of people have trouble getting it to work.
TwitchyEye said:
Yes this is a problem with the new baseband (March 2012) I don't think there's a fix for it yet. There's a few methods to downgrade back to the old baseband where it was working but it's sorta hit or miss. A lot of people have trouble getting it to work.
Click to expand...
Click to collapse
TwitchyEye,
Yes, I found that in my searches; concerning the bluetooth calling. I didn't find anything on the streaming media info. Are they both related to the baseband?
Regards,
BigRedOgre
I'm not really sure about the streaming. My understanding is it was working fine, but I haven't tried it myself. Surely someone around here has personal experience with that end of it.
TwitchyEye said:
I'm not really sure about the streaming. My understanding is it was working fine, but I haven't tried it myself. Surely someone around here has personal experience with that end of it.
Click to expand...
Click to collapse
Yeah, New baseband with CM7 = no call audio but media should work. T-Mobile 2.3.4 stock = both working.
If you want CM7 and both working you need to downgrade the baseband.
-- The noob says:
It's alive!
(Adopted from Robot Chicken for the g2x.)
this is the ONLY issue I have with my phone on new baseband with CM7. Especially since my car has built in bluetooth calling. I misses it =(
mansa_noob said:
Yeah, New baseband with CM7 = no call audio but media should work. T-Mobile 2.3.4 stock = both working.
If you want CM7 and both working you need to downgrade the baseband.
-- The noob says:
It's alive!
(Adopted from Robot Chicken for the g2x.)
Click to expand...
Click to collapse
but you have to go with an older version of CM7 right? 7.2 didn't work for me with the new baseband. no audio.
jblah said:
but you have to go with an older version of CM7 right? 7.2 didn't work for me with the new baseband. no audio.
Click to expand...
Click to collapse
Not quite. CM7 with new baseband requires flashing new baseband zip file (search the forum), but you would have just media over Bluetooth, not call audio over it, however call audio over phone and speaker should work.
-- The noob says:
It's alive!
(Adopted from Robot Chicken for the g2x.)
Related
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Additionally here is a video on the Voice Actions for Android, NOTE: This is different from the Bluetooth Voice Dialer as it has additional features
http://www.youtube.com/watch?v=tPPcTN5sdX4
and
http://www.youtube.com/watch?v=8Ml34vtrGwc
Wow, this is fantastic. I was following the info posted in that AR 3.2 thread, so I'm happy to see something posted.
I'll give this a try tonight.
legend221 said:
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Click to expand...
Click to collapse
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
BillTheCat said:
I'm running RCMix 5.3 and the BT voice dialer works alright for me. Do I need this fix? The one thing I'd really like from the current ROM for BT voice dialing is to have a tone to cue me when the applet is ready to listen.
Click to expand...
Click to collapse
Thats exactly what this does, install and you'll see this for yourself mate.
Sent from my fast / stable HTC Inspire 4G
I am running AR 5.1.3. Voice dial works fine from the phone but when I try to initiate it from my bluetooth headset I get a Force Close of processcom.android.voicedialer. I uninstalled voice dialer with TB and then installed the bluetooth voice dialer from this thread via CWM and I still get the force close when initiating from my bluetooth.
Any ideas on how I can fix this other than flashing a new rom?
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Wow this is cool to have. Im not having much accuracy though. Ive got a 2 year old Jawbone Prime so my bets are that its the problem. Looks cool but hasnt played nice since day one. Anyhow this does work if you got a decent headset
Did you ever figure this out?
toadleyb said:
Okay I just flashed to LeeDroid which claims to have fixed the Bluetooth Voice Dial Problem and I still get a force close when initiating it from my headset.
Anyone have any ideas please????
Click to expand...
Click to collapse
svarzaru said:
Did you ever figure this out?
Click to expand...
Click to collapse
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
xperi said:
I'm having the same problem and would really like to see this fixed. When I tap the voice dialer app on the phone, it works as it should. However, it always FC when pressing the bluetooth button. I think the settings file associated with connecting the bluetooth button to the app is the problem, but I don't know what file it is or how to make it better.
Click to expand...
Click to collapse
Download Cyberon Voice from the market. It does cost a couple of bucks but it makes all problem go away on every rom you need BT with. At least for me it did!
Confirmed working with Virtuous Unity 1.24.0 Sense 3.0 based on Pyramid with Vlingo
Man just what I was looking for will give it a try.....Thanks
Sent from my Inspire 4g using XDA Premium App
missing voice dialer
I tried to flash it, and it didn't do anything. I'm using Virtuous Unity v1.27.0. I even tried to extract the app from the zip (which currently doesn't exist on my phone) and install that way, but it says "application not installed". Nothing happens at all when i hit the button on my bluetooth. With the stock rom, before installing VU, it would pull up the voice dialer. But i can't even install it now. Can anyone help me out? Thanks!
EDIT: Got it to install, but now it force closes when I try to use it, with or without a bluetooth headset.
awesome!!!!!
I'm running AHD 6.1 but it lacks the ability to let bluetooth headset to do voice command. but after i flashed this it worked out fine!!
and btw im using vlingo to do voice dialing, its an awesome app!!
legend221 said:
All credit goes the great mike1986. as this was taken from his thread.
Thanks to him Ive successfully been able to fix the bluetooth voice earpiece feature that was not working on the Rom in the signature.
Ive flashed my share of Froyo Roms and it seems that a lot of them have the same problem as well as some Gingerbread maybe.
The idea is to push the call/end button on your bluetooth connected earpiece to do various call related features without having to grab your phone, its all controlled via voice command.
Many people have been looking for a fix for this.. well here it is.
Directions:
Flash via CWM, reboot and you should have the feature fully functional.
*More information on what this does here: http://www.androidtapp.com/true-hands-free-driving-and-bluetooth-voice-dialing-is-in-android-2-2/
Click to expand...
Click to collapse
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
crypted said:
Will this work with Gingerbread ROMs? mike1986's current DHD/Inspire4G ROM does not support voice dialing via bluetooth. Kind of a pain in the rear not having it!
Click to expand...
Click to collapse
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
homeslice976 said:
The post before yours says they're running "AHD" 6.1 with this dialer and it works fine. I'm assuming this was supposed to be ARHD 6.1 which is a GB ROM
Click to expand...
Click to collapse
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
crypted said:
Yeah, I wasn't clear. I figured it would work since it worked on the one before, but I wasn't sure if the previous post was confirming 6.1.0 or 6.1.1. So, I'm hoping for 6.1.1 support confirmation so I don't brick this puppy.
Click to expand...
Click to collapse
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
homeslice976 said:
6.1.0 was the first version of his new base (2.3.5GB based on HTC 3.06.405.1)
6.1.1 is the same base with updates/enhancements from mike1986. I can't imagine this would bork you. If you're too worried, make a backup. This isn't going to brick your phone to a point where you can't get to recovery and flash your backup
Click to expand...
Click to collapse
Right. That was my assumption and my plan once I got home tonight to do that assuming no-one confirmed it for me. Will flash after while and edit post with results.
I flashed this to arhd 6.1.1. It don't work. App did not appear to be installed. I tried installing the apk and it would just say application not installed.
So it appears to be a no go.
Sent from my HTC Inspire 4G using XDA App
FYI, there is an issue with pretty much all ICS ROMs and the BT stack included in them. I have a brand new, top of the line Jawbone BT that supports everything, works flawlessly in Cyanogen and non-ICS ROMs, but will barely work in ICS.
Basically, after a reboot, it connects and says Connected (no media), then switches to Connected. Everything works fine until I disconnect and reconnect again.
After that, it will work for only voice calls. Media will always go out the speaker. I have tried everything to fix it to no avail. The only resolution to get A2DP media streaming back is to reboot.
When it happens, the media checkbox is still there and checked, but it doesn't work. I switched back to HyperSensation (Cyanogen) and everything works as it is supposed to.
Apparently ICS bluetooth works fine for some BT headsets and not others. This also seems to be an ongoing problem for other phones as well, even non-ICS.
I am not well versed in reading the debug logs, but if anyone is interested I can post them here, provided they tell me which ones they want.
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
I can confirm the issue with the virtuous ICS as well. I have bt stuff from Jawbones to BlueAnt's and all have the same issue. Prior to this was the issue of cutting out and now it's the off/on bt streaming. To "fix" the issue, is to reboot. Annoying yes. But ICS is still so sexy
I've got the same problem, ROM Elegancia ICS 1.0.6 and 1.1.0
After pairing with bluetooth headset, first time I play music everything is ok. after re-connecting, music controls works ok, but sound is thru phone's speakear not thru the headset.
After rebooting the phone the situation is the same- first connection everythings ok, another ones not.
Checked with SE MW600, Jabra extreme and car's bluetooth.
The problem occurs even with clear installation (before I restore backups).
Still can not find solution so I got back to GB.
So its not just me! I can confirm that my Beats Wireless acts exactly like described.. And with a reboot fixing it again!
I think the devs here might be able to fix it, but its properly not going to be an importent issue to fix.. Fingers crossed for a fix, or maybe the future leaks will have it done!
Sendt fra min HTC Sensation Z710e med Tapatalk
ftblstr2319 said:
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
Click to expand...
Click to collapse
Vlingo has always been problematic for me... My solution (worked on ICS too) was to get it working on an older ROM (not sure which one anymore) then use titanium backup and back up APP+DATA on a ROM that it is working on. Then, restore APP+DATA on the new ROM.
The first time you hit the button on your headset it will ask you what app you want to use for voice dialing and give you Vlingo, Vlingo InCar, or Voice Search. Choose Vlingo and check the box to make it default and you are good to go.
Just make sure after you get it working on the new ROM to back it up again... then the next time you switch ROMs, restore whatever the latest backup is. I am not sure what it changes, but I have been through Cyanogen, all of the ARHD versions, all of the InsertCoin versions, and a few others (I can never make up my mind on ROMs) and this trick has worked in all of them.
IMPORTANT: Make sure in Titanium Backup to uncheck the option to restore system libraries in ROM (that can cause issues going between major versions of android), and make sure toenable the features in Titanium Backup for attempting to migrate data.
I also get the same issue when I try to connect my MW-600 with ARHD ICS 6.0.2.
Can anyone help?
You guys who just have to reboot your phone are getting off easy. When I lose Audio Streaming to my car head unit, I have to delete the device and re-pair it to my phone after a reboot.
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
dante-fu said:
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Well, the ROMs are still there to download
With 4.0.1 I was on radio version 10.59. I am not expert on radios and RILs but I guess these things affect also BT performance. Right?
Sent from my HTC Sensation using Tapatalk
Shidapu said:
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Click to expand...
Click to collapse
I reverted back to the virtuous 4.0.1 build from the most recent (having the new fw and radio) and has fixed the Bluetooth issue. Now I just have to live with messed up signal bars and a browser that randomly exits.
Sent from my HTC Sensation using xda premium
Hi,
Reporting this BT issue for me (SGS 2 with ICS 4.0.3, XXLP2 that can be found on XDA, originally from samfirmware):
I try to send files from my laptop to my SGS 2, 1 at a time and the transfer will suddendly halt some of the way through and ICS looks like it's rebooting but it's actually not, I mean not a full proper reboot; the phone does not switch off, the boot anim plays as if restarting, first BT is off then the icon come up in the top bar...
Hopefully, the Simple & Clean, ICS version, is round the corner ;o)
beng
using arhd 6.1.1 here on sensation XE with SE mw600 headset, no issues, calls and media working as normal
BT connectivity seems to be fixed in the latest leaked ICS + Sense RUU.
Is the sensation supposed to support any other remote control features than pause and play over BT?
I can confirm that on my Galaxy s2 using the 'official' ICS rom released yesterday still causes my phone to reboot.
This happens when bluetooth is paired with my car stereo and streaming audio or voice calls. It causes a reboot, usually happens after 10-15 minutes.
Never happened on gingerbread of any version. And has happened on all versions of ICS leading up to 'official' release.
I can confirm that bluetooth will cut off and be off completely quite randomly while listening to music or Pandora.
Only a reboot gets bluetooth to turn back on.
I have experienced this on two Motorola S9-HD headsets on various ICS roms
Sent from my HTC Sensation Z710e using Tapatalk
I'm one of the unlucky few who can't get Bluetooth to work with UCLD2 leak ICS.
It doesn't affect everyone. Just some folks.
It crashes for me and I've tried three different ROM's.
UCALC4 doesn't have the problem with bluetooth for me.
Just wondering if anyone out there has come up with a fix for it, or if you have found any custom ROM's that don't have the problem?
Please don't say CM9 because it's using the older Bluetooth code from Gingerbread (IMO) and has a couple other issues that aren't working out for me. Great ROM otherwise though.
CZ, u tried sky ics ucld2 base with the different cwm flashable Bluetooth fixes seanscreamz has? It seems he tried to import the stack from uclc4
icenight89 said:
CZ, u tried sky ics ucld2 base with the different cwm flashable Bluetooth fixes seanscreamz has? It seems he tried to import the stack from uclc4
Click to expand...
Click to collapse
Yep, tried the base by itself, then also tried the #1 and #2 bluetooth fix.
None work for me.
Had to go back to SkyICS UCALC.
My stereo is the double-din JVC unit.
bluetooth fix
I read that a new base is out for SKY ICS and a lot of people are saying that it fixes the bluetooth issue for them.
Tried it. Twice.
Sent from my SAMSUNG-SGH-I727 using xda premium
Duplicate post
Sent from my SAMSUNG-SGH-I727 using xda premium
CZ Eddie said:
Tried it. Twice.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Are you using darkside to wipe between flashes if so don't. And check your md5s with the files on the SD
Sent from my SGS2 LTE
mr_clean5953 said:
Are you using darkside to wipe between flashes if so don't. And check your md5s with the files on the SD
Sent from my SGS2 LTE
Click to expand...
Click to collapse
I do use darkside.
Sometimes before wiping and sometimes after.
Have downloaded UCLD2 twice, so that's *probably* not the problem.
I hope this Canadian ICS release has some additional Bluetooth fixes.
Otherwise, I may go back to Gingerbread before long.
did you install the radio following Sean's instructs:
http://forum.xda-developers.com/showthread.php?t=1600420
My first ICS rom was a bust.
Then I installed the radio and afterwards installed Sean's 4.2d9:
http://forum.xda-developers.com/showthread.php?t=1602216
I did it exactly, no superwipe, used the cwm touch he said to. Installed the base, then the update. Did not install the bluetooth mods. Only thing I installed was a different battery to fix the ics signal bars from greay to blue.
BT works better than it ever has. I was streaming Slacker and running nav on the way via BT to my Ford truck via Sync to test.
(Sync in my 2010 has always been twitchy; never worked right with my Atrix <previous phone>)
Also BT to a home speaker system is great, also.
rpolansky said:
did you install the radio following Sean's instructs:
http://forum.xda-developers.com/showthread.php?t=1600420
My first ICS rom was a bust.
Then I installed the radio and afterwards installed Sean's 4.2d9:
http://forum.xda-developers.com/showthread.php?t=1602216
I did it exactly, no superwipe, used the cwm touch he said to. Installed the base, then the update. Did not install the bluetooth mods. Only thing I installed was a different battery to fix the ics signal bars from greay to blue.
BT works better than it ever has. I was streaming Slacker and running nav on the way via BT to my Ford truck via Sync to test.
(Sync in my 2010 has always been twitchy; never worked right with my Atrix <previous phone>)
Also BT to a home speaker system is great, also.
Click to expand...
Click to collapse
You should go on sync my ride site make an account and ask them when are you getting a SYNC update, I got my usb and sd car(with new map) two weeks ago, and my car is 2011. The new SYNC is amazing, smooth.
---------- Post added at 03:40 PM ---------- Previous post was at 03:35 PM ----------
I am Running Seans Sky Ice, amazing ROM
Issue for me is car bluetooth, and after working for couple of days it started to connect and reconnect again, after I've been listening to music, so my guess (and this is after testing new radios and few other things) is stock music player does something to bluetooth or bluetooth permissions (as as well as phone it also connects to the car) and once there some connection issues when trying to turn it on through the car, the whole thing just does not work properly.
I never had a problem from update 1 to 6, it started on 8 and seems to happen on 9 again. So for the threads out there that say I've tried all the ROM and it's the same, no it's not it was fine on Update 6 here.
If you are running any other ROM, do a back up and flash Fix 2 first and then if it does not for flash Fix 1, thank you to seanzscreams.
Possible Fix:
What I did is i did a nandroid restore ( and yes it is a good idea to do a back up right after you flashed both base and update and set up LTE, to keep a clean copy)
!!!1) Before setting up or even turning it on, in Titanium Back up, freeze stock music player. !!! and it is important to do so before touching BT, as it may affect permission and this will not work(make sure not to touch MusicFX as it also affect BT permissions)
2) Reboot the device
3) Open Google Music Player and set up your music( please note if you have more then one playlist, make sure you set them up right as songs wont play continually and you will not have ability to skip them using car controls)
Google Play is same as stock, meaning same functionality, same car features and all, so you are not really loosing anything.
4) No close it
5) Go ahead set up BT with the car, you should get two messages one to permit access to phone book and one to permit accesses to call history (well it depends on the car, but if you have a newer system in it they yes) check mark the box so it does not ask you again and click yes/accept.
6) Enjoy. Should be good from now on, I've been listening for it all day, will test it more and let you know.
Please also share your experience and thought on the problem, so maybe I am wrong and it's not the issue and it's something else and we can all get it fixed.
Thank you.
BLUETOOTH IS WORKING NOW!!!!
Unfortunately, none of the possible fixes listed above ever worked for me or other JVC car stereo guys that I know about.
But the newest leak, UCLE2 is working just fine.
Thought it took much longer to recognize my stereo than normal (could just be a one-time issue), it was buzz free, error free and playing my Pandora perfectly!
Here's the leak download:
http://forum.xda-developers.com/showthread.php?t=1652679
CZ Eddie said:
BLUETOOTH IS WORKING NOW!!!!
Unfortunately, none of the possible fixes listed above ever worked for me or other JVC car stereo guys that I know about.
But the newest leak, UCLE2 is working just fine.
Thought it took much longer to recognize my stereo than normal (could just be a one-time issue), it was buzz free, error free and playing my Pandora perfectly!
Here's the leak download:
http://forum.xda-developers.com/showthread.php?t=1652679
Click to expand...
Click to collapse
Ha! Finally! alright, good deal man
Did this fix the timeout issue as well? I'm running UCLE2 as well but still get the timeout once in a while
mine seems to be working fine now on UCLE2 but I've only tested it for a day.
Has anyone had any success using an AOSP based rom and syncing their phone with the new GM car radio, MyLink? I tried many different AOSP roms and although it paired and seemed successful, I couldn't get the radio to play the music from the phone. As soon as I put a Touch Wiz rom on it, it worked really well. I think what is happening is after it pairs and connects, the phone is supposed to prompt me to accept the connection, but it never does. Anyhow, if there is a trick to get this to work, I would really appreciate it. Thanks.
icon123 said:
Has anyone had any success using an AOSP based rom and syncing their phone with the new GM car radio, MyLink? I tried many different AOSP roms and although it paired and seemed successful, I couldn't get the radio to play the music from the phone. As soon as I put a Touch Wiz rom on it, it worked really well. I think what is happening is after it pairs and connects, the phone is supposed to prompt me to accept the connection, but it never does. Anyhow, if there is a trick to get this to work, I would really appreciate it. Thanks.
Click to expand...
Click to collapse
was abt to open a similar thread, any news on this side? Soonish i might have a mylink and im running AOKP..
wanted to know if i'll be able to use all the apps and listen music or if ive to flash some stock or some modded rom
Edit: just saw i did a search fail
ive a samsung sg2
I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...
Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel
Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.
Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?
Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?