I'm having an issue with this otherwise excellent bluetooth sink. My Note pairs seamlessly with it and it connects to it without issue if done so manually (from the Note's bluetooth settings you select to connect the phone to the bluetooth device). The issue is my Note won't automatically connect to the bluetooth device when it is within range. If I bring the phone within range while I'm looking at the bluetooth settings on the phone I can see the phone try to connect to the device, but it is not successful. It connects automatically with no issues when I am on CM9. I suspect it's a bluetooth driver issue.
My ROM: Cleanote v6
My Kernel: Hydracore v4
Amazon link to the bluetooth device in question:
http://www.amazon.com/BlackBerry-Remote-Stereo-Bluetooth-Gateway/dp/B00170KUM0
Is anyone else using this bluetooth sink? If so, do you have the same issue?
Thanks!
Hooray! I've finally figured out the problem. The issue is with the kernel. I went back to ICS 4.0.3 (specifically LPY) with a kernel 3.0.15 that was built in May 2012 and the problem went away. All of the other ROMs I had used that had this problem was 4.0.4 with kernel 3.0.15 that was built around August or September (I forget which one). CM9 was probably built from this kernel since CM9 doesn't have this problem. Now I get to experience SMemo and SNote AND have fully working bluetooth. Hopefully Samsung won't release JellyBean with a bluetooth problem.
Related
There are some weird issues I have been noticing with my SGS regarding bluetooth.
At first, I got slightly irritated when I found out I was suffering what I thought to be this issue on my SGS (noticed after flashing to JP6, later on JPX and now also on JPY). But since, I have been carefully narrowing down the problem (there seem to be several variants of the issue bundled within the one linked) and have finally figured out how to reproduce the error (sort of, at least in my setting: SGS-I9000, BMW 1series car BT system).
After setting a custom BT device name and pairing to the car, the BT handsfree works flawlessly on spot and if disconnecting and reconnecting later. The problem starts after rebooting. Now, here's where I'm getting inconsistent results.
Most times the bluetooth info I entered is simply reset to factory defaults: the pairing list is empty and the device name is set to the standard "Galaxy S".
Some other times however, it gets much more annoying: all the settings seem to be intact (pairing and device name stay as set) but BT connection always drops after about 60s (regardless of wheather you start/receive a call or not).
Is this a known issue? Did any of you experience this behavior? Any known fixes?
Thanks!
Phil
What ROM are you running? Get yourself onto the newest Froyo and see if the problem goes away. I definitely don't have problems with mine going to headphones, ear headset, or in car system.
Doc kitchen (jan 3rd) + Hardcore kernel JPY (which means latest kernel/drivers). This has been happening to me all along though, despite of rom changes (also happened with stock JP6 and darky's JPX).
Sent from my GT-I9000
Hi,
same problem for me: the bluetooth connection to my Parrot MKI9200 car audio system drops after a few seconds. This was not the case with ROMS older than JPX/JPY.
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
goodolsen said:
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
Click to expand...
Click to collapse
The issue disappeared on flashing to a new rom. I'm soory not to be able to give you more details because I found out the issue was gone by surprise (I had stopped using the car handsfree alltogether because of the issue).
Right now I'm on a Doc rom (hardcore kernel, JPY radio, ext4 system & data, ext4nj cache) and it works perfectly!
I am currently running Perception 10.2 and the Firebird 2.3 kernel with the I9000UGK4 modem.
My Bluetooth connects to my Ford Sync in my truck but disconnects the phone part of the connection after a minute and only keeps the music side. It also automatically starts the music player every time.
This is a new problem for me. Previously the WiFi seemed to have an issue and when I drove away from my house and lost the WiFi signal the Bluetooth would disconnect also. That was on Cognition. I could prevent that by turning off the WiFi before starting the truck.
My understanding is the I9000 modems sometimes have issues with Bluetooth static vs. HSUPA? I need the Bluetooth more than the data speed.
I ran the Firebird 2 kernel and Cognition 3 and the bluetooth static was so bad I couldn't use it at all.
Are there any Sync users running a similar setup that they like and that works with the Bluetooth?
Should I just flash a different modem or try a different kernel? My suspicion is its the I9000 based kernels but most of the custom kernels seem to be based on the I9000.
I use ford sync. I am using jk4 modem. I am not on perception and I am not using firebird. I have no issues with connection. So, if it means anything it is not the modem. I have been on jpy roms without bluetooth issues, and I am currently on andromeda which is an armani port. No issues.
Maybe try a different kernel although I am unsure why that would make a difference. I would suggest hardcores.
I had these issues when I was on stock 2.1. Sometimes it even used to reboot my phone.
I am Maxima SYNC by the way, but both should be similar. Now I am 2.2.1 based ROMs and able to talk on phone properly.
Something u could try:
1. Delete all bluetooth profiles from ur phone.
2. Delete the phone profile from ur car.
3. Restart ur phone and connect it fresh.
This resolved the issue I once had when on a 2.2 ROM.
Cool. I will try the complete Bluetooth deletes ( I have done them but not both during the same flash or re-pare ) and if that doesn't work I will try the ROMs you both are running to see if that helps.
Thanks for the help.
OK. So just in case someone else has this issue and uses the search function.....
Turn off the Bluetooth audio input selection under the media input area of Sync before trying to pair your phone.
It works fine to go back and select Bluetooth audio after you have started and paired for a bit, but if Bluetooth audio in is selected when you first start your vehicle it will kick off the phone part and only keep the music player connected.
It also automatically opens the music player on the phone and starts playing the last track. Which I would imagine will effect battery life if you have your phone in your pocket and don't notice it.
Not sure if this was happening with other Kernels and ROMs as I only noticed it with this one.
I've never had a problem with any rom not being able to play through bluetooth media on my gf's focus. If you go to the bluetooth options on your phone, hold your finger down the sync connection you can select phone, media and connect. Select phone and media if you want both to be available.
Go to the menu for sync in your truck, I think it's under player settings or something similar, but there's an option for autoplay on or off. Obviously, if it's set to off it won't automatically play your music.
Right now I'm on Serendipity 4.1, Firebird 2 kernel and jl2 modem with no problems. I've also used Cognition roms, and Perception roms, never had any of the problems you're experiencing.
I had a Sync-enabled rental car last week, and noticed it wouldn't stay connected if say for instance I left the car with the phone and still had BT enabled, then came back to the car and tried to just let it auto rejoin. I found everything went smooth if I disabled BT when leaving the car, and reenabled coming back.
ThorGR said:
I had a Sync-enabled rental car last week, and noticed it wouldn't stay connected if say for instance I left the car with the phone and still had BT enabled, then came back to the car and tried to just let it auto rejoin. I found everything went smooth if I disabled BT when leaving the car, and reenabled coming back.
Click to expand...
Click to collapse
It has to be set to your phone as primary to auto connect.
I have had Ford Sync disconnect problem ever since I got captivate in November. Bluetooth randomly disconnects. Both cog 2.3b6 and 2.3b8 gave me problem, although 2.3b8 works better overall. I didn't try latest cognition roms yet.... I have a tasker that turns off wifi automatically when bluetooth is connected -- it improves things, but still I get disconnects every now and then.
I really hope to find a permanent solution to this. This is the most annoying problem with my phone right now....
I had serious disconnect issues too until I did something similar to what someone else already posted.
1. On phone, unpair Sync
2. In Sync, perform master reset (system settings>advanced>master reset) NOTE: This will lose all of your settings
3. Reboot phone
4. Pair phone and Sync. Allow Sync to download phonebook. (If this disconnects, restart at step 1)
5. I always disable automatic downloading of the phonebook and autoplay of bluetooth audio.
Once I get a successful phonebook download with no disconnect, I will not have any more issues with bluetooth.
after upgrading to ICS stock rom, my car no longer connects to note. I have to re pair each time and have disabled screen lock to keep it connected.
i have done factory data reset twice... nothing works..
please provide a solution.
if no solution's available, is there any othe ICS rom which haven't got this bug?
No problems on stock ics for me with my car bt (ford sync)... connects just fine
My car has built in bluetooth connectivity with 2 modes, telephone and media.
Both modes cannot be connected at the same time.
The telephone mode works fine, but the media player mode always fails to connect.
I've had no problems in the past with my SGS1.
I've tried resetting the profiles. I'm on the .350 stock rom but I've added root.
Not sure what I can do now to fix this.
I guess I could upgrade but I'm not sure if it would actually fix the problem.
Does anyone have any ideas?
BTW the car is a Toyota Prius.
All Day On XDA said:
My car has built in bluetooth connectivity with 2 modes, telephone and media.
Both modes cannot be connected at the same time.
The telephone mode works fine, but the media player mode always fails to connect.
I've had no problems in the past with my SGS1.
I've tried resetting the profiles. I'm on the .350 stock rom but I've added root.
Not sure what I can do now to fix this.
I guess I could upgrade but I'm not sure if it would actually fix the problem.
Does anyone have any ideas?
BTW the car is a Toyota Prius.
Click to expand...
Click to collapse
Try repairing it with Sony's PC Companion or Sony's Update Service first.
Remember to backup your stuff before proceeding.
Do full wipes.
Update. The Bluetooth pairing with my car is still very buggy.
A quick google search reveals others are having issues too.
I hope Sony address this issue soon.
I'm not having problems with my Bluetooth unit in the car. It connects to both Phone and Media Server. (I have a Kenwood DNX unit)
So I'm still having problems.
The update to 4.2.2 did not help.
So I tried switching to CyanogenMod but the problem persists.
My other phone also running CM has no problems connecting to the telephone and media mode (Samsung Galaxy i9000) so it has to be something going wrong in this phone.
I'm out of ideas. Toyota say it's not a car fault as other phones connect fine.
New Toyotas have a system that's called Touch'n'Go and I managed to test this phone on that and both modes worked fine.
I guess there is an incompatibility between this phone and a perhaps slightly older Bluetooth module in the car. The car is from 2010.
Would be grateful for any ideas.
Sent from my C6603
Does the 12-12-13 update include kernel changes which are suppose to repair black box issue in default browser api ?
UPDATE: Forgive my ignorance. I now see the commits included in Milaq's CM11 KK 4.4.2 update for the TouchPad (tenderloin). And understand the devs are still working updating 3.6 kernel. So will need to live with the Kernel 2.6.35 for a while longer. But until then apps utilizing default browser api are problematic. At least Chrome and Firefox are working.
I'm running Milaq's 4.4 ROM also. Happy to run with it for now even with "black box" issues, is running incredible smooth so far. Using shortcuts to Chrome bookmarks is my workaround for Gmail etc just now, although same issue in the BBC news app (and others I'm sure
I don't have enough posts to post or reply in development forum so posting here.
On the CM11 dev thread a couple posts about audio issues. I've flashed the 12/10, 12/12 & 12/14 CM11 nightlies and have not observed/heard audio issues.
And BT and WiFi are working ok. And file transfer via USB and BT ok (although BT transfer appears slower from what I recall in CM7/CM9 or WebOS).
Haven't yet figured out how to get BT streaming (from a Windows PC) to work.
If I could get my Plantronics Backbeat 9033+ BT headset to charge correctly, I could test those with CM11 (previously I the BT headset working well in CM9 as well as WebOS). Wish I never bought this particular headset, as they hurt my ears, no matter which eartips I use. And now will not charge. (I only used a few times since purchasing late last spring). Need to look up my warranty. Sorry I digress OT.
woodytrain said:
And BT and WiFi are working ok. And file transfer via USB and BT ok (although BT transfer appears slower from what I recall in CM7/CM9 or WebOS). Haven't yet figured out how to get BT streaming (from a Windows PC) to work.
If I could get my Plantronics Backbeat 903+ BT headset to charge correctly, I could test those with CM11 (previously I the BT headset working well in CM9 as well as WebOS). Wish I never bought this particular headset, as they hurt my ears, no matter which eartips I use. And now will not charge. (I only used a few times since purchasing late last spring). Need to look up my warranty. Sorry I digress OT.
Click to expand...
Click to collapse
When I stated BT was working ok, I was referring to paring the TouchPad with an HP TouchPAd Wireless Keyboard as well with a WIndows XP PC.
I was able to get the BT headset working with my WIndows PC (it was charging ok...issue was operator error). And when I search for BT devices on the TouchPad CM11) my headset displays in the device found list. But when attempting to pair the CM11 Touchpad with the headset, Bluetooth on the TouchPad turns off, and then within a few seconds BT turns back on.
Anyone able to get a BT headset working with CM11...yet?
I probably should just sit back a bit and wait for the updated kernel.