[Q] Bluetooth handsfree problem - Samsung Galaxy S II Plus

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?

Related

[Q] Tasker on MIUI/WajkIUI

Hi all.
Sorry if this is the wrong place to post, but this thread is regarding bugs on custom ROMs, so here I am.
A while back I switched from CM7 to WajkIUI, and I really have enjoyed this ROM since trying it. Recently however, I've noticed a couple of issues regarding MIUI/WajkIUI and Tasker. I've mentioned my problems in the relevant ROM thread here, and also on MIUIandroid.com, but nobody seems able/willing to help.
I have profiles configured within Tasker that will switch my phone to mute (Silent Mode) when I'm at work (based on WIFI near attribute, which is working fine). WajkIUI ROMs subsequent to 1.9.2 are unable to switch this, or indeed make any changes to volume.
I also have a profile that will switch on Bluetooth when I get an incoming call (using the Incoming Call option in Tasker). I've no idea when this stopped working, I'm on 1.9.2 at the moment, and it doesn't work here. I've tested the profile activates, and it does - but it doesn't switch on Bluetooth.
Finally, my third bug relates to the above, but not Tasker. If I switch Bluetooth on manually and pair with my headset - I can't get my headset to answer the call or to ring the last number (two things it has always done before).
Is there ANYONE who can help fix these? Are these issues solely on MIUI based ROMs, or does CM7 also have this issue - as I'm seriously considering switching back.
Thanks.
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
simon211175 said:
250+ views and not one response? Boy do I feel lonely now.
So, seeing as how nobody can offer any help on my actual problems - can someone give me a clue to how I go about decompiling a ROM to check the code out myself please?
Click to expand...
Click to collapse
Try to update to 1.9.23
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
simon211175 said:
Will that work? I've tried all of them up to that, but every time had to downgrade due to the problems. I got fed up of installing a ROM only to have to uninstall it five minutes later.
Click to expand...
Click to collapse
I think it's a bug in MIUI itself. If you check the app on market, there's a lot on Market who says so.
that's what I thought - I've an ignored thread in the bug forum on miuiandroid, hence my last question about decompiling the ROM so I can investigate myself.

[Q] Bluetooth Issue - All Jellybean ROMs - All Kernels

Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!
turn your phone s-off if u ain't.
:-??
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
lassykk said:
Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!
Click to expand...
Click to collapse
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.
Skipjacks said:
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.
Click to expand...
Click to collapse
Hi thanks for replying.
I will try Bruce's ROM but the official CM10 ROM didn't work for me.
I don't have any apps that could be interfering as all I have done whilst testing this problem is do a full wipe, install the JB ROM and go and check the bluetooth.
I will check tonight if the issue exists on another bluetooth device and report back any problems.
Cheers
AW: [Q] Bluetooth Issue - All Jellybean ROMs - All Kernels
Delete please

[Q] Headset issue with Sebastian Kernel's ROM

Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Sorry for bumping it up. Anyone has experienced same issue? @SebastianFM, could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
pdbc said:
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Click to expand...
Click to collapse

[Q] Relay can't hear input from any bluetooth device, LAME

Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)
Epiclectic said:
Am I the only Relay user having trouble using voice command thru bluetooth?
I'm running Cyanogenmod 10.2, on tmobile, and using google voice/talktone for calls.
On both bluetooth car kits I've tried (Blueant Commute and Kinivo BT450), things work fine (music, navigation, reading incoming texts, taking calls) until I try to voice command the phone thru the BT unit.
I've tried:
~ google now, voice search, voice dialer
~ turning on talkback (hate that constant reading of each page, AGHH!)
~ blueant app (does F%&&% all)
~ every tip on both gear's support pages
~ tmobile's support page (HA!)
~ even reverted back to stock (in case it was CM), and IT STILL SUCKED MY @**#&#$
I am ready to throw this POS phone against the nearest underpass..... if someone can solve this, I will send you thanks, and a present. Seriously.
(I appreciate all advice, but feedback from those who have this prob, or solved this prob are the most helpful. THX)
Click to expand...
Click to collapse
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.
Magamo said:
We (TeamApexQ) have thrown ourselves against this wall a few times, to no avail. This is a known issue in our sound configuration. It really comes out of the fact that getting this to work would involve having a bluetooth device work in two separate profiles (A2DP for output, SCO for input) at once which is not a trivial or easy thing to implement. What we need are more logs of this issue, and probably some direct communication in IRC with a couple of testers to bang this one out.
Click to expand...
Click to collapse
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?
Epiclectic said:
OK, so I'm not a retard. hehe, thanks for that, I was going crazy thinking it must be some setting I overlooked. Strange though, it still didn't work when I reverted to stock.... no? (THAT must be something I am doing wrong...)
After 6 months enjoying CM10 (big thumbs up for TeamApexQ!!), I can't bear the thought of trying to suffer thru stock rom....what's the closest rom to CM that has good bluetooth integration..?
Click to expand...
Click to collapse
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.
Magamo said:
Now, someone can correct me if I am wrong on this, but I believe all of the community images are using the same sound configuration that TeamApexQ has been developing since CM 10.1, so... None of them. Again, with some community assistance, logcats, testing, and patience we can fix it.
Click to expand...
Click to collapse
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?
Epiclectic said:
I thought I heard CM9 had working BT... if not, what can I do to help? how do I capture and send you the logs?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1726238
Please, please, please issue a 'logcat -c' before doing this proceedure to capture a log of the issue, to clear the log, and to avoid having us to sift through every log your phone has taken since reboot.
Also, send us the contents of the 'dmesg' command after encountering the issue, just to rule out anything on the kernel side.

[Q&A] [ROM][LP][5.0.2] CyanogenMod 12 - UNOFFICIAL BUILD for M4

Q&A for [ROM][LP][5.0.2] CyanogenMod 12 - UNOFFICIAL BUILD for M4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LP][5.0.2] CyanogenMod 12 - UNOFFICIAL BUILD for M4. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Giving it a shot
I'm not a big camera user anyway, so I'm going to give this a shot. Wish me luck!
Hi Plesse fix camera THX
Hi there..
Is 4g/Lte working?
4g LTE dont work
Great job!
Thanks for your work! This ROM is awesome and if you fix the camera too you're a god. By the way... on this forum there is another Lollipop ROM (Candyrom) where the camera is working. Can you use that? i'm a noob so don't judge me
Just flashed earlier today and seems to be working great! cheers man. Any update on the camera?
Thanks
Camera Works!!!
Great job!!! The camera works and the system is very fluid. i notice some problems on activating mobile data. First time i tried it didn't work. I switch some APN, turned Airplane mode on/off (strange, it required me to enter the PIN 2 times in a row). Finally it worked (i saw the LTE text on signal bars and i was happy ). Another thing i noticed is that the Prefered Network was 3G and i couln'd choose LTE only if i select 2G first and then LTE.
Thanks again!
no sim found
i have a problem, the rom can't find my sim, anyone had a solution?
SIM
(This rom doesn't ask for my PIN so I guess it doesn't read my SIM at all? Clean install (I guess), everything else I tried is working quite fine.)
Settings say baseband version is unknown.
They can't hear me well
Another problem that i noticed is that the other person i'm talking to hears me, and i quote them, "like you are in a tunnel". At first i thought that is their phone, but multiple persons reported that to me. Also, this happened after i flashed this rom.
Baseband Unknown
Hi,
Just installed this and everything works great except for the mobile network. Settings say baseband version "Unknown", doesn't detect sim at all.
Does anyone has any idea on how to fix it?
Cheers!
....
Hello , I friend says to me : "You don't need root to install cyanogenmod on m4 , only TWRP (teamwin or something like this..) "
And my question is : Is this real ? I don't need root , only TWRP? to install cyanogenmod on m4 ?
Installing the app Selinux and setting it to permissive fixes APN and mobile network problems. I would advise doing some background reading of this app first though.
Flashed it 2 days ago, everything is fine. Sometimes it is a bit laggy, but it looks very nice!
First i had problems with the google play music app. I was not able to listen to music with my headphones but now it works... Don't know why ?
cm12
who can do not be razognanoe kernel on cm12? you're welcome
Hello Guys,
I just tested the CM12 build for the One m4 and i have some issues... i cant connect to my carrier and somehow i can't install the gapps. i downloaded the one provided in the first post and i tried to download the most recent ones. If i try to install the gapps, my recovery just pops up the main menu with no error-codes or something. it is just loke blown away, if you know what i mean... and, yeah, i cant connect to my carrier, which is like... meh... not actually good for daily use... :/ if there is a way to fix it all, please let me know, i could use some help here.
Greetings Meritili
Edit:
Managed to install the gapps, carrier Problem is still there, help please!
Great Rom !! Thnx
Nice Rom
but... vibration intensity does not work
Bluetooth Problems
Hi, first of all thanks for providing this ROM. I tried both the 5.0 as well as the fresh 5.1 build and most things, apart from some spontanious reboots, are working exceptionally well (IMO better than CM11).
One problem I observed is that I can't use bluetooth to make calls. I am not sure, whether this is a general CM12 problem, or whether it's specific to our device. The same problem is also present when using the other Lollipop ROM based on CM12 in the forum (Candy5). I also found some reports of users of other devices that also have bluetooth problems when using CM12 or some other Android 5.x based ROM.
To clarify: I can pair and connect to bluetooth devices that offer headset functionality (tried bluetooth headset and bluetooth radio in car), and I can also stream music via bluetooth. What I can't do is making actual calls via bluetooth. Both bluetooth devices noticed that a call is about to be made, and also the correct number was displayed in the radio display. But no sound was audible and the other side couldn't hear me. The call itself was okay when switching to internal speakers. Dis-/Re-enabling of bluetooth options did not fix anything.
Audio playback over bluetooth is also rather sluggish and sometimes leads to freezes. Also sometimes the option to use bluetooth for media playback has to be disabled and reenabled for it to work.
Unfortunately I can only test bluetooth in my car (the headset wasn't mine) so it is kinda hard to generate logs. I will try over the next few days to produce one.

Categories

Resources