Serious issue with bluetooth after update to 2.3.6 Samsung Galaxy Exhibit 4g - General Topics

On my Samsung Galaxy Exhibit 4g (aka Samsung Exhibit II 4g) I have not been able to use Bluetooth ever since the update to 2.3.6. I have tried to un-pair and re-pair my Bluetooth mouse and keyboard, but neither of those device work. The phone says they are paired but it wont let me connect to them and input from these Bluetooth devices does not work. Also if it matters, I am rooted...

odysseyofnoises said:
On my Samsung Galaxy Exhibit 4g (aka Samsung Exhibit II 4g) I have not been able to use Bluetooth ever since the update to 2.3.6. I have tried to un-pair and re-pair my Bluetooth mouse and keyboard, but neither of those device work. The phone says they are paired but it wont let me connect to them and input from these Bluetooth devices does not work. Also if it matters, I am rooted...
Click to expand...
Click to collapse
They all worked fine under 2.3.5 ?
I also ran into the same issues, but I only started trying after stock update to 2.3.6 >> rooted ROM >> RebelROM
Bluetooth keyboard doesn't work on either custom ROM
Headset works just fine. But not with Skype. I tried some BT mono app to reroute the audio, but the app claimed it's a issue w/ Skype / Samsung.
I wonder if a stereo headset would work.
I'd really want to use the kb though. Please keep us up-to-date w/ your findings. Thanks !

edit: wanna do further testing before i come to more than half-baked conclusions...

Related

Plantronics Voyager Pro

I just bought a Plantronics Voyager PRO headset for my Nexus One (running 2.2). The headset won't stay connected. It's paired and could make calls right after pairing, but now it won't connect unless I remove the device and repair it.
Is there anything else I can try? Any firmware updates for bluetooth on the phone or the headset? Any ideas??
StevoDevo2 said:
I just bought a Plantronics Voyager PRO headset for my Nexus One (running 2.2). The headset won't stay connected. It's paired and could make calls right after pairing, but now it won't connect unless I remove the device and repair it.
Is there anything else I can try? Any firmware updates for bluetooth on the phone or the headset? Any ideas??
Click to expand...
Click to collapse
Got the same - works.
Which rom are u using?
Edit: i bought discovery 925
I'm just running the standard out the box Android 2.2.1 (Build FRG83). What ROM are you running? Perhaps I should look at installing another ROM - always need a new project!
StevoDevo2 said:
I'm just running the standard out the box Android 2.2.1 (Build FRG83). What ROM are you running? Perhaps I should look at installing another ROM - always need a new project!
Click to expand...
Click to collapse
Running MicroMod's HD port....very stable and reliable for daily usage, but got some bluetooth troubles as well... try latest cyanogen, should help out. BT was working vor me with the plantronics....simply gotta love their headsets

[Q] Infuse wont see bluetooth devices on stock rom

I have a bluetooth OBD2 reader for my car and while using the stock rom on my infuse, the phone never sees the device so I cannot pair it. I was using the serendipity rom and it sees the reader and pairs perfectly. Are the two roms using different bluetooth protocols? Is there an update of some kind to get it to work?
forgot to mention the bluetooth adapter i am using is an ELM327. I used it with no problems on my Evo and on the infuse using the s7 rom. The stock rom will not see it at all.
kdmcameron said:
I have a bluetooth OBD2 reader for my car and while using the stock rom on my infuse, the phone never sees the device so I cannot pair it. I was using the serendipity rom and it sees the reader and pairs perfectly. Are the two roms using different bluetooth protocols? Is there an update of some kind to get it to work?
forgot to mention the bluetooth adapter i am using is an ELM327. I used it with no problems on my Evo and on the infuse using the s7 rom. The stock rom will not see it at all.
Click to expand...
Click to collapse
That's weird... I know that Samsung-derived ROMs have issues in their Bluetooth stack - it's why you can't use Wiimotes or the Sixaxiscontroller app for PS3 controllers.
However - stock ROM and S7 should be identical in this regard other than maybe Gingerbread vs. Froyo.
CM7 is where you should see significant differences in terms of support for "unusual" devices like Wiimotes and such.
Can anyone else confirm that their S7 rom (NOT CM7) can see a wiimote or ps3 controller?
antuus said:
Can anyone else confirm that their S7 rom (NOT CM7) can see a wiimote or ps3 controller?
Click to expand...
Click to collapse
I haven't even tried - I assume it won't. Will try tonight but I'm assuming failure.
A pseudo-serial device like that OBDII unit may be an oddball corner case.

S3 Bluetooth Voice command via headset

Anyone having issues with giving a bluetooth command to the S3 via bluetooth? (Verizon)
I have a S4 BlueAnt car speaker and a Interphone F5 motorcycle headset (bluetooth) and both will not allow voice commands. (Voice dialing)
I can remove all security, and the voice prompt will come up, but won't hear me.
When I use the phone alone, no issues.
However both these bluetooth devices worked perfectly with my old HTC Thunderbolt.
I have heard of some kinda of "Samsung Bluetooth Bypass" is not allowed. Any info on this please?
Anyone have a fix other than going root!? I wanted to try to keep this one stock for now... but may have to root if I can't find a way.
Thanks
bigb78 said:
Anyone having issues with giving a bluetooth command to the S3 via bluetooth? (Verizon)
I have a S4 BlueAnt car speaker and a Interphone F5 motorcycle headset (bluetooth) and both will not allow voice commands. (Voice dialing)
Click to expand...
Click to collapse
Yes! Ford Sync, which worked fine with Thunderbolt, Galaxy Nexus, and iPhone 4S, and cannot send bluetooth audio to my Verizon S3. This seems like such fundamental functionality that I think I must be doing something wrong. I like almost everything about the S3, but I am seriously missing hands-free voice commands in the car.
blooks said:
Yes! Ford Sync, which worked fine with Thunderbolt, Galaxy Nexus, and iPhone 4S, and cannot send bluetooth audio to my Verizon S3. This seems like such fundamental functionality that I think I must be doing something wrong. I like almost everything about the S3, but I am seriously missing hands-free voice commands in the car.
Click to expand...
Click to collapse
Hoping it gets addressed.
Verizon is aware, and says they can't do anything about it, all on Samsung.
They are my next call. Tried every app possible, not software (or downloadable software)
I have a US Cellular SIII and voice works fine from my plantronics bluetooth. Call (whoever), what time is it, take me home(nav to home). Thats all I've tried so far but works fine. No special software or settings. A little slow to respond but acceptable. Finally, I don't have to say the name I want to call exactly as in the contact. First name is fine if its the only one. I used to have to say "call (first name, last name, mobile)"
Since rooting no issues
Not that you want to hear this.
Since I have rooted and running
Synergy 1.7 no issues with running
mult bt devices so far. Only issues
is with my bose bt once in a while I
have to pair it again on the S3 if I was
using it with my I-touch prior.
Cheers,
Azbobs
INC > TB > S3
drum4ever said:
I have a US Cellular SIII and voice works fine from my plantronics bluetooth. Call (whoever), what time is it, take me home(nav to home). Thats all I've tried so far but works fine. No special software or settings. A little slow to respond but acceptable. Finally, I don't have to say the name I want to call exactly as in the contact. First name is fine if its the only one. I used to have to say "call (first name, last name, mobile)"
Click to expand...
Click to collapse
It's a Verizon thing. Samsung just replied to my email and said it is at the specs wanted by Verizon.
Root here I come. What's the best, stable ROM out that is fairly close to stock? Suggestions?

My Touch 4g and the ELM 327 interface for OBDII data - BT compatible ROMs?

I've been cruising on cyanogenmod 7.1 for about 2 years now, and since the auto store no longer reads OBD II codes for customers, I decided to purchase one of the $10 Bluetooth ELM 327 devices off ebay, and use the Tourque app to read the data from my car.
The app works great, but it only works if you have a notification pop up asking to pair with the device, and I've only been able to get BT to work with this device so far with a 4.2.2 ROM --> http://forum.xda-developers.com/showthread.php?t=2204963 (only JB one I've tried). The other ICS ROM's I've tried so far along with CM 7.1 just won't connect. Has anyone else found a good ROM that works, or a way to trigger a bluetooth notification?
Basically, I turn on Bluetooth in all the ROMs, it detects the device, I select the device, and it says "Paired but not Connected" If you long press or hit the gear symbol, the only option is to "unpair". Pairing with other phones works perfectly fine, but with this device the option/notification to connect never comes up.
Anyone know of any ROMS prior to Jellybean that work with similar BT devices? .. Dunno if there is a way to trigger a notification; I do like JB, but once everything I need is working, my #1 goal is then responsiveness.
Any ideas/insights/experiences are much appreciated.
Have you tried any Sense roms?
Well, as it turns out, after I did a complete wipe, and was trying cyanogenmod 7.2 out, I was able to connect..... in fact, I'm able to connect on good ole 7.1 as well, and mytouchUXv3... which I didn't want to uninstall- seemed to have a snappier ui. I have no idea why I was unable to connect yesterday, but on whatever ROM i've tried today, if I start bluetooth, then run the torque app, then go back to the bluetooth app with the torque app running, and select pair/unpair/pair/unpair, it connects pretty soon. *scratches head*
One reason I stick to cm 7.1 is that I've read of many users experiencing diminished battery life with cm 7.2
1LordAnubis said:
Well, as it turns out, after I did a complete wipe, and was trying cyanogenmod 7.2 out, I was able to connect..... in fact, I'm able to connect on good ole 7.1 as well, and mytouchUXv3... which I didn't want to uninstall- seemed to have a snappier ui. I have no idea why I was unable to connect yesterday, but on whatever ROM i've tried today, if I start bluetooth, then run the torque app, then go back to the bluetooth app with the torque app running, and select pair/unpair/pair/unpair, it connects pretty soon. *scratches head*
One reason I stick to cm 7.1 is that I've read of many users experiencing diminished battery life with cm 7.2
Click to expand...
Click to collapse
Yeah I've read the battery life thing too.
What do we lose if we stick to 7.1 instead of 7.2
Sent from my myTouch 4g using xda app-developers app
I've been using CM10.1 for the past year and have had sucess with my Bluetooth OBD II reader.
Here is the ROM I have been using. The camera is a bit slow on this ROM but other than that I love it:
http://forum.xda-developers.com/showthread.php?t=2204963
Just to confirm, it ALSO works well with Vipertouch 2.1.4.
Buddy of mine passed me his cheap ELM ODB II Bluetooth unit, (he could not connect to it, since he had some chinese S3 knockoff phone).. Worked perfectly first time.
Paired no problem, and connected using Torque Pro and read quite a few of the sensors on my honda without an issue.
Thanks to all the devs for keeping these older phones alive..

Bluetooth keyboard doesn't work with Galaxy S7

Hi everyone,
I've been using a bluetooth keyboard (iClever BK03) with my Samsung J5 on Android 7.0 without any problems, but when I switched to the Samsung S7 on Oreo, it doesn't work. It either says it connected and doesn't do anything, or it says it can't connect. I've tried everything in the system itself. Is there a way I can make the phone recognize it?
Nikolakv said:
Hi everyone,
I've been using a bluetooth keyboard (iClever BK03) with my Samsung J5 on Android 7.0 without any problems, but when I switched to the Samsung S7 on Oreo, it doesn't work. It either says it connected and doesn't do anything, or it says it can't connect. I've tried everything in the system itself. Is there a way I can make the phone recognize it?
Click to expand...
Click to collapse
The keyboard Bluetooth connection standard is 3.0 and the S7 is 4.2. Its often the case that devices are not backward compatible. Check iclever website for a Bluetooth firmware upgrade.
Also worth noting that devices will be moving away from Bluetooth when the new short range WiFi standard is rolled out.
cooltt said:
The keyboard Bluetooth connection standard is 3.0 and the S7 is 4.2. Its often the case that devices are not backward compatible. Check iclever website for a Bluetooth firmware upgrade.
Also worth noting that devices will be moving away from Bluetooth when the new short range WiFi standard is rolled out.
Click to expand...
Click to collapse
Makes perfect sense, thank you!

Categories

Resources