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!
Related
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...
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..
I upgraded to the Lollipop 5.0.2 Stock firmware yesterday from KitKat - everything seemed to go smoothly but I am experiencing a problem with my Logitech Pro Keyboard.
I can scan and discover the keyboard, connect and enter the PIN and the keyboard shows up as being present, connected and an input device. However, no key presses are registered by the tablet at all from the keyboard. I have tested the keyboard with another tablet - a 2011 Nexus 7 running 5.1.1
Has anyone got this keyboard working with the stock firmware?
danburycollins said:
I upgraded to the Lollipop 5.0.2 Stock firmware yesterday from KitKat - everything seemed to go smoothly but I am experiencing a problem with my Logitech Pro Keyboard.
I can scan and discover the keyboard, connect and enter the PIN and the keyboard shows up as being present, connected and an input device. However, no key presses are registered by the tablet at all from the keyboard. I have tested the keyboard with another tablet - a 2011 Nexus 7 running 5.1.1
Has anyone got this keyboard working with the stock firmware?
Click to expand...
Click to collapse
Nope.... this seems to be a major bug with this initial release of 5.0.2 for the P900. I have the same with my Logitech Pro and also a Logitech K810.
From what I've seen so far no BT keyboards work except for Samsung (model unknown) where I've seen one report of it working.
Well, the issues with 5.0 and Bluetooth are universal, so I'm not at all surprised....
ShadowLea said:
Well, the issues with 5.0 and Bluetooth are universal, so I'm not at all surprised....
Click to expand...
Click to collapse
Bummer... Should we expect Samsung to address this issue in a future release, or are we stuck with an expensive cover with keys? (I'm just wondering if Samsung actually tracks those issues and if they are willing to fix it...)
Really too bad it works for the 'original' Samsung keyboard cover, if that were broken too it may have been a bigger incentive for Samsung to fix this BT problem
And I haven't seen keyboard issues with CM12 on the Note 12.2, so that makes me wonder if this is a Lollipop issue, I would guess it is more a Samsung problem. I remember the BT stack on my SIII being 'different', it didn't work too well with my car kit...
"....... or are we stuck with an expensive cover with keys?" It seems we are
COF4 for Canada and Cellular South with a different build date is now available so it'll be interesting to see if it has the same problems.
BOF2 is also now available for Switzerland but it has the same build date/time as the Netherlands build.... so much for country variations :silly:
Cheap Polaroid bluetooth keyboard working fine with 5.02 on a P900 here. Maybe this is Logitech specific?
netizensmith said:
Cheap Polaroid bluetooth keyboard working fine with 5.02 on a P900 here. Maybe this is Logitech specific?
Click to expand...
Click to collapse
what fw build have you flashed/updated to.... BOF2 or COF4 ?
BOF2. Just checked again and all is working well. Note that I did a full reset after flashing because clicking "Toolbox" in the settings->Device caused settings to crash. That might be something to try (I know it's a common suggestion and one that's a real pain to do but if that's the only difference between our devices then maybe try it).
netizensmith said:
BOF2. Just checked again and all is working well. Note that I did a full reset after flashing because clicking "Toolbox" in the settings->Device caused settings to crash. That might be something to try (I know it's a common suggestion and one that's a real pain to do but if that's the only difference between our devices then maybe try it).
Click to expand...
Click to collapse
Ok, thanks for the info.
I did a full reset after flashing as I wanted a clean build.
Same issue here
Installed 5.02 .. Logitech keyboard no longer working.
As I never use my tablet without a keyboard and supplies of the original Samsung keyboard are not exactly great ( at least in the UK and NL ) I have ordered a US keyboard from Ebay - Not ideal, as I will be using 3 different keyboard layouts each day, but I wanted to make sure that I got one before they all disappear.
Maybe something logitech should fix then given that Polaroid and Samsung keyboards work.
Sent from my D6603 using Tapatalk
JimMNH said:
Installed 5.02 .. Logitech keyboard no longer working.
Click to expand...
Click to collapse
Which 5.0.2 did you install? BOF2 (Dutch) too or the Canadian COF4?
Tonv said:
Which 5.0.2 did you install? BOF2 (Dutch) too or the Canadian COF4?
Click to expand...
Click to collapse
I installed the BOF2 - Dutch version.
Where can I download the COF2 version ?
EDIT: found it - downloading now - will try and report results.
My tablet originally came from the US - I wonder if North American versions have something different at the hardware or OS level that is different from European models ?
Tonv said:
Bummer... Should we expect Samsung to address this issue in a future release, or are we stuck with an expensive cover with keys? (I'm just wondering if Samsung actually tracks those issues and if they are willing to fix it...)
Really too bad it works for the 'original' Samsung keyboard cover, if that were broken too it may have been a bigger incentive for Samsung to fix this BT problem
And I haven't seen keyboard issues with CM12 on the Note 12.2, so that makes me wonder if this is a Lollipop issue, I would guess it is more a Samsung problem. I remember the BT stack on my SIII being 'different', it didn't work too well with my car kit...
Click to expand...
Click to collapse
It's Google's fault, actually. They messed up the Bluetooth protocols.
How come my.Bluetooth keyboard works on my note pro and my z3, both on lolipop? Also my Bluetooth speaker and my car both work fine with both devices. Can't be a.general lolipop bug surely?
Sent from my D6603 using Tapatalk
Just updated my P900 to 5.0.2 and my logitech keyboard does not work. I updated my US purchased tablet OTA if that helps.
Same on us version
Just updated to 5.0.2 on us bought tablet with us ota and yes logitech bluetooth keyboard will pair but no keys do anything. This is pathetic, why break things?
Anyone have a fix? If not can I go back to a version of android that actually works? If so, how?
---------- Post added at 01:09 AM ---------- Previous post was at 12:20 AM ----------
The logitech blutooth kbd does not work with the galaxy note pro 12.2 OTA (US) 5.0.2 update however it works fine with my nexus 4 running android 5.1.1. Point is that I can use the phone to act as a keyboard using a number of apps (for example im typing this through an2an remote 3.2.4)
You guessed it, the logitech keyboard is paird to the phone and the phone is running as a remote control keyboard and its working. There is some light lag (only some of the time) and at least I can get on with writing my document now. Wierd to be bouncing the keyboard off the phone to the tablet but thats better than not being able to use the keyboard at all.
The spesfic app im using on the phone has to be open in order to work so I couldnt use the phone for anything else (or have any other screen open on the phone) so this is not a long term solution however it will allows people to do some typing on the galaxy note pro with 5.0.2 and the logitech keyboard in the short term.
Absurd
Really, this has to be a joke. I have the same issue here. Did a factory reset fix it for anyone?
Tarps.nj said:
Really, this has to be a joke. I have the same issue here. Did a factory reset fix it for anyone?
Click to expand...
Click to collapse
I havent tried that yet but i agree its very disapointing. The logitech keyboard works fine on my nexus 4 running android 5.2.2 so its not an android thing, its a "we couldnt be bothered to test it" thing and unfortunatly samsung dont release updates very often so it could easily be 6 months before this is fixed (if its ever fixed). There are only a couple of keyboard cases designed to fit the 12.2 inch device so this will affect a LOT of people - I would have prefered to not update (and in future may hold of on updating) as everything was working fine before and now the keyboard I use every day no longer works, great work samsung.
This is the second or third time an android update has given me nothing I wanted and broken something I actualy relied on
Samsung released a Marshmallow (Android 6.0/M update to the Gear app, the Gear Plugin, and the Samsung Accessory Service apps on October 12. They then released updates again on October 15 and 16.
None of these three updates allow the S2 to stay connected via Bluetooth to your Marshmallow phone. Phone will connect once, and then fail to reconnect UNLESS you do a "Light" or "Factory" reset. Of course you lose some or all of your data and settings. And then if your S2 goes out of range of Phone, reset time again.
Just wanting folks to be aware. Suggest you leave a comment in Google Play for all three apps, but who knows if Samsung even reads those comments. At this point I don't even know if the people at Samsung who need to know about this, are even aware of issue.
I hope this is fixed soon... I left negative feedback until it is resolved.
I replied to you on the other thread, did you make sure permissions were set for both Manager and Plug In apps?
I learned awhile back ago, first to update is the first to find the new problems. Automatic updates and being the first to download is COOL, but not always functional.
15 days, and still not working on Android 6.0 Marshmallow phones. Apparently if you are on Marshmallow, and hadn't already installed the Gear app from the Play Store, you're now seeing "your device is not compatible" and you can't install it.
A user on Android Central with a Nexus 6 on Marshmallow is reporting that there is a firmware update under About Gear in the Gear app that has fixed the Bluetooth connection issue. I don't have my S2 with me at the moment, so anyone with a Marshmallow phone should check for the Firmware. Please let us know if you're successful in repeatedly reconnecting without having to do a reset every time you go out of range. Thanks!
I can confirm that I have repeatedly been able reconnect my S2 to my Nexus 5 on Marshmallow after I installed the S2 firmware update that was available in the USA in the Gear app under the About Gear settings. I went from firmware version R720XXU2AOIL to R720XXU2AOJ3. I found that even after installing the firmware, I had to do one Light Reset on the S2 before the S2 would reconnect.
So far so good. Have intentionally gone out of range 6 times and reconnected all 6 times. Will report back if situation changes.
FitzAusTex said:
I can confirm that I have repeatedly been able reconnect my S2 to my Nexus 5 on Marshmallow after I installed the S2 firmware update that was available in the USA in the Gear app under the About Gear settings. I went from firmware version R720XXU2AOIL to R720XXU2AOJ3. I found that even after installing the firmware, I had to do one Light Reset on the S2 before the S2 would reconnect.
So far so good. Have intentionally gone out of range 6 times and reconnected all 6 times. Will report back if situation changes.
Click to expand...
Click to collapse
I literally sold my S2 Classic recently because of this issue. It's really fixed now? I need to learn to exercise patience.
Yeah, been working all day, so I'm optimistic that it's fixed.
I'm about to upgrade my phone to Marshmallow. Did this issue get fixed? Can the Gear S2 connect with Marshmallow phones?
I'm on a Note 5 with Marshmallow and have had no problems with connectivity to my Gear S2.
Thank you! I updated my phone to Marshmallow too and it's working fine since yesterday.
Ive got a htc one A9 running marshmallow 6.0.1 does anyone knows if is 100% compatible with the gear s2 i hear people telling me it is but at what end? Do all functions work with non samsung devices? I use a lot of gmail and whatsapp and i hope to reply via the gear s2 so just wondering. Thanks to anyone that helps
Hey guys,
today I received my Mi Band 1S and wanted to pair it with my G930F, but then this error from above occures. Any ideas what I can do? I restarted bluetooth several times, but it did not work.
Some time ago I also had a problem with pairing a Jambox Mini. I was paired but the Jawbone app said, that there is no Jawbone device conneted.
Any ideas how I can connect my Mi Band to the S7?
Thank you!!
I've never had luck pairing my MiBand to any phone. I typically just do it through the Mi app and it works like a champ. Mine ( Mi Band 1S ) is currently paired to my SM-G930F via the app, doesn't show up under bluetooth devices, but, the app works perfectly, and my band syncs and gets all the notifications perfectly.
its like fitbit, it pairs thru the app
Thanks! Problem solved...
How did you get it solved? Same problem with my S6. Cant pair even thru app.
I have the same problem with Samsung S6. It pairs only thru Mi Fit app
But if you can't pair your MI1s with phone Bluetooth you can't use Smart Lock...
wait for an update for the app
app update?
How can it help?
The problem is we can't pair the MIband as a bluetooth device for it to work with smart unlock.
I think it's some samsung stock-rom issue.
Anyone solved this problem without changing rom?....
RamiBot said:
app update?
How can it help?
The problem is we can't pair the MIband as a bluetooth device for it to work with smart unlock.
I think it's some samsung stock-rom issue.
Anyone solved this problem without changing rom?....
Click to expand...
Click to collapse
I've got the same pb... seems like because of Android 6.
I'm on a Samsung Galaxy Note Edge, and since I got the Marshmallow Rom, I can't pair with the Bluetooth yet!
I tried on a Galaxy A7 (SM-A700F, not rooted!), with Android 5, the pairing is instantly effective. I tried to upgrade through OTA, and since it's now on Marshmallow, the pairing fails. Smartlock is OK and approved... and still no pairing.
But on my Note 2, rooted, and on CM13 (Android 6), the pairing works perfectly.
Don't know where the pb is... Guess it's because of Samsung?!?
Any solutions?
Thanks a lot
V.
**Little up**
Hi all,
The Mi-Fit has got a recent update and still no pairing... damned!
I have note 4 with 6.0.1 stock rom and am facing the same issue. Literally tried every solution over the Internet and am really frustrated now. Can't use my band as a trusted device now, which is important as I hand having to unlock my phone again and again, but for security sake can't do without it:/
---------- Post added at 03:13 AM ---------- Previous post was at 02:26 AM ----------
I wonder if this is a Samsung problem.