Hello everyone. I've been having bad bluetooth issues since I moved to ICS (LPQ at first). Most importantly:
random disconnects (at least once every time)
no metadata sent to the car stereo (in gb I used to see the song name etc, not on ICS)
I've read that deleting the bluetooth pairing and redoing it from scratch would fix the issues. I went ahead and deleted the pairing on both the car and phone side. I then proceeded to reconnect the two devices. I pressed "new device" on my car stereo, which placed the car's bluetooth in "available", also this popped up on screen: "You can now start the lookup of this stereo from your cell phone. The pin is: 1234". So, looking up for devices from my galaxy s2 I was able to properly find the car's stereo. Pressed on it, the pin dialog popped up, I entered 1234, but the phone goes back to the bluetooth screen, and the car says "wrong pin". Tried many times, nothing. Changed the pin on the car's side to 5678, retried, still "wrong pin"...
Anyone knows how to fix this? I'm currently on XWLP8.
Thanks,
TD
Noone has encountered a similar issue with ics?
find out the address of ur bt and use the last 4 0r 5 digits as password..
rocky23 said:
find out the address of ur bt and use the last 4 0r 5 digits as password..
Click to expand...
Click to collapse
You mean the address of my car's bluetooth or my phone's?
tylerdurden83 said:
You mean the address of my car's bluetooth or my phone's?
Click to expand...
Click to collapse
no ur phones...and yes did u try ur cars bt a reset...an one other way is try fresh pairing ,remove all pairs on phone aswell as on cars bt then try to pair...sometimes the cars bt is limited to 5 or 6 pairs....
Related
Its a very nice bluetooth sterio headset / hands free.
Usual pairing, finds device - but says code is incorrect, and wont lock the device as trusted, any ideas?????
I use these with my HD no problem.
When setting up the pairing are you using four zero's "0000" as the passkey.
have done the 0000
with no luck - says wrong code...
having major probs everytime i switch the headset back on....
My BT experience is limited.
Are your S9s are paired with anything else, laptop maybe? If connected to something else when attempting to pair to your HD, maybe this would throw up that error?
I had a similar experience trying to connect to my laptop, I didn't realise they were still connected to my HD in the other room using the same headphone profile.
mmmm!....
nope, not paired anywhere else
If all else fails perhaps a factory reset?
I read this.
- Turn the Bluetooth Headset on
- Connect it to the charger
- Disconnect it after 5 seconds
- Reset is done.
Click to expand...
Click to collapse
Could be worth a try?
S9 headphone
I used my S9 with my blackstone a few times and had no problems.
You should pair the headphone first through
Settings\connections\bluetooth with headphone profile and passkey 0000
If you put in passkey just in the application (e.g. coreplayer) then the device is possibly not paired and you have to put in the passkey next time again.
The S9 can save a device list of 8 devices and connect automaticaly to on of them if it found one of them working. This worked very well at my headphone.
Best regards Wolf_munich
I have a problem with the s9 with my htc hd. I pair up the device no problem but when i play a movie or music the volume is very very low almost can't hear a thing. i use the s9 with htc cruise don't have the low volume problem. Anyone know how to fix that problem
Im using a motorola S9 with my HD in playing music and videos with no problem, works perfect.
Applepie2649 said:
...i play a movie or music the volume is very very low almost can't hear a thing...
Click to expand...
Click to collapse
Using Coreplayer? check the volume pre amp value is not set too low.
i had trouble pairing after a reflash of my titan, entered the 0000 as per this thread and im away!
cheers folks
Motorola s9 handsfree
how to open it any idea?
I have the s9 aswell and ive had no problems pairing it with my hd though one time i didnt have a problem pairing it wih my computer i tried everything on the forums about reseting it and that didnt help. What i found to work was pairing the device with another bluetooth handset (xda orbit in my case) then trying to pair it again with the computer and that worked fine.
good luck with it and if all else fails you could always phone up motorola and get a replacement if its still in the 12 months.
keep us updated
danum said:
If all else fails perhaps a factory reset?
I read this.
Could be worth a try?
Click to expand...
Click to collapse
Thank you for this, I've been trying everything to re-pair my s9 with my htc rhodium 400, passkey 0000 wasnt working, i kept getting errors, turned bt radio and device on and off and on and off and same problem, until i did the factory reset, then it took 0000 like a champ and paired up fine!
I have managed to pair my phone with my parrot hands free unit in the car. How ever it will not remember the pairing, and each time I step into the car I must manually pair, any ideas?
hmm... from past experiences from SGS1 and SNS
they are bound to automatically re-connect to my car for BT audio streaming, i use it practically everyday
that being said, the experience is the same with past old phones like Treo and Windows phones, although those had some minor annoyances. similar to what you have just described specially the windows phones.
so, it might be possible the SGS2 BT audio profile might not be fully compatible with your car BT receiver.
does it automatically pickup phone calls using the BT headset (handsfree) profile ?
Same here too! Sometimes with my Motorola S7HD or my Sony car stereo x.x
I'd have to go to Settings -> Wireless network -> Bluetooth and manually pair them myself. Ugh.
Any fix for this guys?
I know it sounds silly but after pairing are you accepting the notification to always allow it to pair?
krabman said:
I know it sounds silly but after pairing are you accepting the notification to always allow it to pair?
Click to expand...
Click to collapse
I have this problem with my landrover bluetooth, (I have to pair each time I use the car) However I have never seen a notification to 'always allow it to pair' am I doing something wrong? or is there a setting somewhere that I have missed.
Tom
In my case the problem is not actual pairing. I have a Pioneer bluetooth car stereo. It has been paired but for it to see the S2, the phone must be made visible each time. Despite being paired it still needs to be made visible.
Despite extensive searches, I have never found a way to make it permanently visible. There is a silly timer which turns off visibility after 120 seconds.
Previously, with my old Windows 6 and even Windows 5 phone, I used to just go into my car and go - no fiddling with phones - never even took it out of my pocket. Now I need to make it visible each time and this really bugs me.
Don't tell me it is more secure - that's my choice and should not be Android's choice.
Mahniex said:
In my case the problem is not actual pairing. I have a Pioneer bluetooth car stereo. It has been paired but for it to see the S2, the phone must be made visible each time. Despite being paired it still needs to be made visible.
Despite extensive searches, I have never found a way to make it permanently visible. There is a silly timer which turns off visibility after 120 seconds.
Previously, with my old Windows 6 and even Windows 5 phone, I used to just go into my car and go - no fiddling with phones - never even took it out of my pocket. Now I need to make it visible each time and this really bugs me.
Don't tell me it is more secure - that's my choice and should not be Android's choice.
Click to expand...
Click to collapse
have you tried editing the /system/etc/bluetooth/main.conf file
there is a line
#how long to stay discoverable mode before going back to non-discoverable
#The value is in seconds, (0=stay pairable forever)
DiscoverableTimeout =120
Needless to say try it at your own risk, you will probably need a rooted phone and something like root explorer to edit the file.
Hope this helps
Tom
I too have the same problem. My Philips SHB1400 does not get auto paired. I have manually pair it when ever I want to make a call. Never had this problem with same BT Headset and Nokia 5800
frogfoot said:
have you tried editing the /system/etc/bluetooth/main.conf file
there is a line
#how long to stay discoverable mode before going back to non-discoverable
#The value is in seconds, (0=stay pairable forever)
DiscoverableTimeout =120
Hope this helps
Tom
Click to expand...
Click to collapse
I tried that but I am afraid it doesn't work. I think other people have also tried it in other threads and it does not work either. The timer stays at 120 secs
has anyone tried playing with the blacklist file in the above directory? I tried renaming it and rebooting but it made no difference for me, but my Landrover is not specificaly blacklisted.
Pairing bluetooth with Caddy SRX.... NOT....
I downloaded the Bluetooth File Transfer app and that worked for awhile ... off and on ...... but hasn't worked for two weeks now. I've been to Cadillac - I've been to ATT store - everything is checked correctly that needs to be. This has been ongoing issue for a year now. Any other new updates about this problem ?
Thanks.
I do not get the 'notification to always allow it to pair' on some devices but do on others.
Anyone know why?
I am trying to pair a Uniden cordless phone and keep getting the pin request every time I connect.
While on my car I do get the always allow pair request and everything is fine.
So my Jawbone Prime was connecting fine before I updated to ICS LPQ (was on GB LA4 before) and now it doesn't even show up on the devices list even when I try to re-pair or reset the headset.
I tried 2 different sets to no avail.
Anyone know of a solution?
Connects to A2DP BT Headset (Motorola) but only allows media audio to connect. Phone audio doesnt stick.
ICS has some compatibility issues with certain bluetooth devices.
GB my phone always paired with my car stereo and streamed music without any issues.
So far every ICS release, even official, has caused my phone to reboot after streaming music over BT for 10+ minutes.
Its pretty sad they dropped the ball here. GB worked fine, and they borked it.
Well I can connect my BT keyboard fine. I just tried my Motorola BT earphones which are A2DP and it connects but won't allow phone audio to go through the BT earphones. However Media does go through. At least it detects it.
It doesn't detect it at all on the Jawbone Prime (which is not A2DP).
Update:
I managed to connect my jawbone and actually have 2 phone calls on it. After that I had the phone in my pocket and when I checked maybe 15mins later it had frozen and I had to keep power pressed to shutdown/reboot.
It kind of matches Chakker3D's pattern of working then not working. It's like there's a memory leak in the bluetooth stack? maybe I'm just spitballing here.
What I know is that in GB whenever I deactivated BT it took a good 20-25secs. In ICS it's instant to turn off or on. In GB however there was 0 issues.
I just really hope Samsung addresses it. Or if we are lucky, a dev will rework a rom so this problem is gone.
But from what I can tell, very few are having this problem.
Airbag888 said:
So my Jawbone Prime was connecting fine before I updated to ICS LPQ (was on GB LA4 before) and now it doesn't even show up on the devices list even when I try to re-pair or reset the headset.
I tried 2 different sets to no avail.
Anyone know of a solution?
Connects to A2DP BT Headset (Motorola) but only allows media audio to connect. Phone audio doesnt stick.
Click to expand...
Click to collapse
Sometimes is helps when you change kernel. Give a try
078gregory said:
Sometimes is helps when you change kernel. Give a try
Click to expand...
Click to collapse
Another update:
Without any intervention on my part other than keeping on trying it finally discovered my BT headpiece. In fact it discovered both.
Now it's still not 100% perfect because it discovers it, connects and immediately disconnects. If I press a button on the headpiece while it connects then it stays connected and it hasn't restarted/locked the phone yet. I even connected my 2nd headset (another Prime) and it worked.
Keeping fingers crossed. Now I need to see what happens when I walk out of range and back in range.
Has anyone come across this before: my obd2ecu adapter keeps asking for a pin every time I connect. Once connected it's fine until I close the app but next time it asks again...... this used to work fine on my one x and my s2.
Any suggestions?
Thanks
My Galaxy Nexus is doing the same thing with my new Passat's Bluetooth connection.
I had to make my GN discoverable and initiate the pairing from the car, which I think might be part of the problem. When the phone isn't in the car, the car doesn't show up in the list of paired bluetooth devices, and when I start the car, it asks for the PIN twice and pairs... without me setting my phone discoverable.
Thoughts, anybody?
Rob
Mine is doing the same ???
Hello,
I have upgraded to Android 4.1.2 and my Kernel is JZ054K.I9100XWLSD. Since the upgrade I face problems with bluetooth. Everytime I conncect via bluetooth to our car telephone system (Audi), I get connected. After 30s I get reconnected than connected again. I had version 4.0.4 before and did not have any problems with bluettooth connections to my car. Does anyone have an idea? Does the 4.1.2 in general has this problem? How to fix it?
Thank you very much for any suggestion ort support!
That's strange. How did you update? Does is connect as rSAP or only with Handsfree profile? Did you already try to remove the pairing from the car and to do a new pairing?
I updated three days ago using KIES from 4.0.4 to 4.1.2 and I do not have any problems with connection to my VW FSE Premium. Everything is working like before I didn't even need to do a re-pairing, the old configuration was still working.
AndDiSa said:
That's strange. How did you update? Does is connect as rSAP or only with Handsfree profile? Did you already try to remove the pairing from the car and to do a new pairing?
I updated three days ago using KIES from 4.0.4 to 4.1.2 and I do not have any problems with connection to my VW FSE Premium. Everything is working like before I didn't even need to do a re-pairing, the old configuration was still working.
Click to expand...
Click to collapse
I updated via WiFi. Re-paring was not necessary. I switched not to visibility from 2 Minutes to always. Need to see, if this helps.
I do not need to set/change the visibility on my phone. I switch on bluetooth and when I enter my car, the car "takes" the sim card. When I switch off bluetooth or leave my car, the phone is getting access back to the sim card.
SGS 2 Jelly Bean 4.1.2 - Bluetooth connection problems to car telephone system
AndDiSa said:
I do not need to set/change the visibility on my phone. I switch on bluetooth and when I enter my car, the car "takes" the sim card. When I switch off bluetooth or leave my car, the phone is getting access back to the sim card.
Click to expand...
Click to collapse
I've had similar issues with my SGS2 on ICS and now with 4.1.2 (XXLSJ). I'm convinced the problem is a combination of the phone's current processes and how often the car kit retries to connect. I have a Parrot based bluetooth kit factory fitted in my 2006 Mitsubishi. It usually connects within about 20 seconds of starting the car. It often won't connect for about a minute and sometimes doesn't connect at all (maybe 1 in 20 times). When it doesn't connect, I turn off bluetooth in the SGS2 wait about 15 seconds and turn it back on. It usually connects again without touching the car kit.
I've noticed that if I unpair the car kit at the SGS2, the car kit will try to reconnect about once a minute and the phone makes a noise to tell me that something is trying to connect.
Recently I took a vacation and rented a 2012 Toyota Camry and paired my SGS2 to its bluetooth. The phone connected faultlessly very time, there were no issues.
My theory is that if the phone is busy with some process or another when the bluetooth kit tries to connect, it misses the connection. If the kit retries several times (I'm guessing the Toyota kit did this), then there seem to be no issues.
I can only guess that if the SGS2 bluetooth stack is given a higher priority it would be less likely to miss the connection. Clearly that's impractical because bluetooth only needs to connect (maybe) 3-5 times a day and may exclude a more frequently used process.
Just my 2 cents worth - I hope that helps
DaGroover said:
I've had similar issues with my SGS2 on ICS and now with 4.1.2 (XXLSJ). I'm convinced the problem is a combination of the phone's current processes and how often the car kit retries to connect. I have a Parrot based bluetooth kit factory fitted in my 2006 Mitsubishi. It usually connects within about 20 seconds of starting the car. It often won't connect for about a minute and sometimes doesn't connect at all (maybe 1 in 20 times). When it doesn't connect, I turn off bluetooth in the SGS2 wait about 15 seconds and turn it back on. It usually connects again without touching the car kit.
I've noticed that if I unpair the car kit at the SGS2, the car kit will try to reconnect about once a minute and the phone makes a noise to tell me that something is trying to connect.
Recently I took a vacation and rented a 2012 Toyota Camry and paired my SGS2 to its bluetooth. The phone connected faultlessly very time, there were no issues.
My theory is that if the phone is busy with some process or another when the bluetooth kit tries to connect, it misses the connection. If the kit retries several times (I'm guessing the Toyota kit did this), then there seem to be no issues.
I can only guess that if the SGS2 bluetooth stack is given a higher priority it would be less likely to miss the connection. Clearly that's impractical because bluetooth only needs to connect (maybe) 3-5 times a day and may exclude a more frequently used process.
Just my 2 cents worth - I hope that helps
Click to expand...
Click to collapse
Actually, we own two SGS2 phones: Both pair with our Audi telephone kit. The first reconnects after 30 sec./ 1 minute and then reconnects. The later stays connected. However, if I try to use the phone to dial a number via the Audi telephone unit.....the Audi telephone unit starts to dial and then stucks. The first phone is able to dial.....as I have seen in the web others seem to have the same problem with SGS 2 4.1.2. I even bought BLUETOOTH KEEPALIVE...no succces. With version 4.0.4 neither of the phones had a problem with paring with the Audi device. Any other ideas?
Same for me
Im also having the same issue, I have a SEAT Altea and after upgrading to JB on my S2 i have exatly the same issue.
Connecting to the Blue Tooth now takes a lot longer than previously and i get a rapid reconnection about every 30 seconds or so (could be slightly longer i havent measured it). There is no disconnect sound from the hands free though only a conneciton sound.
Please post if you find a resolution to the issue.
Regards.
Jason...
Problems with Bluetooth
Hi All,
I have the same problem. I upgraded to 4.1.2 recently and immediately after all was OK. However now it has developed a new problem.
It will connect to the Car Bluetooth and will play music however the minute I start a call it will only use the small speaker designed for when you hold it to your ear. I will not allow me to press the headset button and will not automatically switch to headset/Bluetooth. This is seriously irritating and I have tried all the usual options of rebooting and unpairing etc. but to no avail...
Your pearls of wisdom would be gratefully received
Using a Samsung Galaxy S2 with Android 4.1.2 Build JZ054K:I9100XWLSW
Regards
Fiachna
I report the same issue between my SGS2 and my '04 BMW 3-series.
With the 4.0.3 ICS no problems: the phonebook is shared correctly and visibile with the car, without loosing the connection.
Starting from 4.1.2 JB I'm not able to keep up the connection for more than 30 seconds, and I cannot read also the phonebook: in this way the phone cannot be used in the car.
The only way to have JB and the bluetooth working togheter is to install a custom ROM (4.2.2 SuperNexus or RootBox 4.2).
Try it!:good:
Install File Manager which can access system files
go to System/etc/bluetooth
in file called main.conf add
IdleTimeout=0
save file - it worked for me