Related
While downloading a few apps, like the Wii controller mod made by one of our own xda developers, it appears that the desire has a non-standard bluetooth arrangement compared to something like the Nexus One? Rather than timing out, the application isn't even recognizing that bluetooth is turned on. The help section tells me vaguely that its an issue with the device itself...
What are the details on this? I've read that this is a flaw with any Sense UI device. I don't have any other bluetooth devices to test it with (except a Wii controller) but does bluetooth even work on the desire?? Would rooting fix my issues?
Macca2805 said:
While downloading a few apps, like the Wii controller mod made by one of our own xda developers, it appears that the desire has a non-standard bluetooth arrangement compared to something like the Nexus One? Rather than timing out, the application isn't even recognizing that bluetooth is turned on. The help section tells me vaguely that its an issue with the device itself...
What are the details on this? I've read that this is a flaw with any Sense UI device. I don't have any other bluetooth devices to test it with (except a Wii controller) but does bluetooth even work on the desire?? Would rooting fix my issues?
Click to expand...
Click to collapse
I have the same issue connecting a Wiimote to my Desire. My Bluetooth does work though, with everything but the Wiimote, I expect your bluetooth is also fine.
I expect the Wiimote app is conflicting with something about the Sense UI. Maybe the fact that Sense-enabled handsets also come with HTC's IME keyboard stock, since the Wiimote app is in fact a replacement IME.
I read somewhere that the HD2 supports bluetooth keyboards. Does anyone know if it's the same with the EVO?
Maybe, I hope so because I intend on testing it with an apple wireless keyboard
Not natively, but it should work with third party driver/apps like KeyPro.
Sweet I have my Apple Keyboard and Mouse.
I have heard a rumor that the Incredible does not support BlueInput (because of an older BT stack implemented by HTC) like-wise the EVO. I would be unhappy given the lack of a physical keyboard on the phone.
http://www.teksoftco.com/forum/viewtopic.php?f=30&t=2414
That was the same error I was getting on my Sprint Hero, but the KeyPro guys made a version of the drivers that worked anyway. I think they can do the same if the EVO has the same issue.
galt said:
That was the same error I was getting on my Sprint Hero, but the KeyPro guys made a version of the drivers that worked anyway. I think they can do the same if the EVO has the same issue.
Click to expand...
Click to collapse
Unfortunately it may be more OS related than a BlueInput problem.. Either way it would appear we arent getting HID anytime soon.
http://community.htc.com/na/htc-forums/android/f/91/p/2201/8561.aspx
zonyl said:
Unfortunately it may be more OS related than a BlueInput problem.. Either way it would appear we arent getting HID anytime soon.
http://community.htc.com/na/htc-forums/android/f/91/p/2201/8561.aspx
Click to expand...
Click to collapse
Mmm, so that explains why Wiimote Controller does not work on "devices running Sense"
FYI, using a beta version of KeyPro I was able to connect my Freedom Universal Keyboard 2 to the EVO, but the keyboard mappings were off. I've contacted the developer of KeyPro (who has been very responsive to tweaking the app for Sprint Hero support), I'm pretty sure this is something they can resolve.
Will report back...
My bad, I forgot to change the keyboard type in the KeyPro options - it works GREAT with the EVO!
Good stuff! Thanks for the notice!
galt said:
My bad, I forgot to change the keyboard type in the KeyPro options - it works GREAT with the EVO!
Click to expand...
Click to collapse
With what keyboard?
galt said:
...I was able to connect my Freedom Universal Keyboard 2...
Click to expand...
Click to collapse
It's a pretty nice keyboard. http://www.freedominput.com/technical-support/technical-support/universal-keyboards
I should note, it provides for good text entry and some hotkey functions, but it seems that much of Android's interface isn't accessible via these kinds of devices. You are still going to have to poke at your screen to do some things. Bluetooth mouse support would make this a bit easier...
I use the v-tech virtual keyboard via KeyPro. Works quite well.
Ceger
What did you do that I can't figure out?
I've spent the best part of 8 hours trying to get my Freedom Universal 2 keyboard to connect using Keypro. The developer said not to bother purchasing the key if I couldn't get the keyboard working without it. Were you able to get it working on the trial version? Or did you have to purchase the key? I've managed to get the keyboard paired but not connected. Thanks for any tips / pointers.
Are you using the beta version from the keypro forum? The one they cooked up for the hero works for me. Which ROM are you running, and what are the symptoms of your connection problem?
The version I've been trying to get working is Keypro 2.00.08 trial.
Android version 2.2
The phone appears to pair with the keyboard when the keyboard is set to SPP, but not in HID, but they never actually connect. I've not yet been able to use the keyboard or assign shortcuts using Keypro. Thanks.
I was counting on using my think outside Serria full size folding bluetooth to work, ltd proving tto be difficult so far.
This was and perhaps is one of best keyboards but it don't matter if it doesn't even connect
Any one have an approach they could suggest?
bigwavebrian said:
The version I've been trying to get working is Keypro 2.00.08 trial.
Android version 2.2
The phone appears to pair with the keyboard when the keyboard is set to SPP, but not in HID, but they never actually connect. I've not yet been able to use the keyboard or assign shortcuts using Keypro. Thanks.
Click to expand...
Click to collapse
I recently purchased the Freedom Pro keyboard from Amazon. I figured if I could not get it to work, I could send it back to Amazon. I originally tried to use the keypro apk, but was unsuccessful. Then I downloaded the android driver from the Keyboard site, that also would connect, but not pair. I then downloaded the instruction manual and followed their directions. Still no success. Then I got the bright idea of shutting down the phone, and then trying to pair my Evo to the keyboard. Success!!!! You click on the connected part of the driver software (read the installation manual) and this time it connected. There is an area on the driver you can use to check and see if you are connected. My Evo is unrooted (since 2.2). This has replaced my laptop for on-the-go business related work.
Hi Guys,
I tried apple magic mouse and apple wireless keyboard (old version with number pad) and they both are not working on my tab 10.1 wifi. So I want to know if any of you guys successfully using any bluetooth keyboards and mouse with the tab?
My brother has the new imac keyboards, well not really new but the ones that come with the macs, and it worked perfectly, I just had to set the keyboard on the tab to the samsung one and no issues. As for a mouse, I have no idea.
In my experience, the apple magic mouse connected to the tab, but no cursor appeared, nothing at all. And Apple wireless keyboard (older version with numpad) didn't even connect .
I tested the one without the number pad. Worked great. Try to get your hands on that one.
Anybody had any luck with a BT mouse?
I've been using the Microsoft Bluetooth Notebook Mouse 5000 with my LTE Tab for several weeks with no problems. It's not very sexy, but it's cheap and gets the job done well.
I've also used the Logitech Tab 10.1 Keyboard Case and the Microsoft Bluetooth Mobile Keyboard with no problems. The Logitech case is spendy, but the Android-specific keys are nice, and I doubt you will find a more compact Tab/keyboard pairing, if that's a concern (it is for me).
just tried my logisch dinovo edge it's a Bluetooth Keyboard with a touchpad on it, and it works great, mouse Cursor shows the instant i move it clicking also works! Keyboard input as well
endursa said:
just tried my logisch dinovo edge it's a Bluetooth Keyboard with a touchpad on it, and it works great, mouse Cursor shows the instant i move it clicking also works! Keyboard input as well
Click to expand...
Click to collapse
Interesting, could we get a link to that?
jonnyg1097 said:
Interesting, could we get a link to that?
Click to expand...
Click to collapse
Here you go: Do a search for Logitech diNovo Edge
Expensive and not too convenient to travel with.
I use the below and it works great.
http://www.logitech.com/en-us/tablet-accessories/for-android/devices/tablet-keyboard-android
I havent tryed a mouse yet, but i love my bt keyboard!!
Sent from my GT-P7510 using XDA Premium App
ehupp01 said:
I use the below and it works great.
http://www.logitech.com/en-us/tablet-accessories/for-android/devices/tablet-keyboard-android
Click to expand...
Click to collapse
I want this keyboard! I am just looking for the best place to get it from.
And by best place I mean the cheapest.
The apple bluetooth keyboard without the numeric block works great exept some special characters : on the german keyboard layout the @ normally is only accessible with Alt gr + a. This does not work on apples keypad. I read that this was a bug from the Galaxytab, because it works with other android tablets without a hassle.
Still looking for a solution.
Does anyone know if HP's Touchpad Bluetooth keyboard will work with Android? It's on sale now:
http://slickdeals.net/permadeal/596...keyboard-25-two-hp-folio-case-for-touchpad-35
microsft mouse 8000 paired but not pointer at all
itry the mucrosft 8000 mouse bluthooth but dont pointer at all. It paired and connect but nothings happends.
Iwant to know if any of you have look with it.
bluetooth mouse
I have apple blue tooth mouse and works fine.
Is anyone else having issues with their bluetooth keyboard when paired with the Nexus 7? I have an Apple Bluetooth keyboard and it repeats characters, and inserts the spaces out of order.
(Yes I'm aware of External Keyboard Helper, and it does help but it makes my typing laggy)
BubbleSort said:
Is anyone else having issues with their bluetooth keyboard when paired with the Nexus 7? I have an Apple Bluetooth keyboard and it repeats characters, and inserts the spaces out of order.
(Yes I'm aware of External Keyboard Helper, and it does help but it makes my typing laggy)
Click to expand...
Click to collapse
I can't even get to pair with my Motorola 89451N. I am guessing it's firing off random characters during the pairing security process.
These are exactly the type of issues I was hoping to avoid with a Nexus device. Google needs to up their QA
Sent from my Nexus 7 using Tapatalk 2
I have a Logitech Bluetooth keyboard with the same issues. My Bluetooth mouse is fairly unless as well.
Here's hoping it gets straightened out soon...
Sent from my Google Nexus 4
smithk86 said:
I have a Logitech Bluetooth keyboard with the same issues. My Bluetooth mouse is fairly unless as well.
Here's hoping it gets straightened out soon...
Sent from my Google Nexus 4
Click to expand...
Click to collapse
There is a bug filed with Google which might be relevant, but it doesn't give much hope of quick resolution because it has been open for about a year.
My Logitech keyboard works well with my (non-Nexus) phone with CM10, but a different build of the ROM with a newer kernel has issues.
I've renamed the keyboard file, and I still have issues with characters repeating and lag. I think the issue might be the Bluetooth connection being flaky.
The lag is most noticeable in SSH apps
EDIT: I traced this problem to an issue with WiFi+Bluetooth. When I tether to my phone and turn WiFi off, my keyboard acts as it should. I'm not happy with this workaround, but at least I can get some work done.
Sent from my Nexus 7 using Tapatalk 2
BubbleSort said:
I've renamed the keyboard file, and I still have issues with characters repeating and lag. I think the issue might be the Bluetooth connection being flaky.
The lag is most noticeable in SSH apps
EDIT: I traced this problem to an issue with WiFi+Bluetooth. When I tether to my phone and turn WiFi off, my keyboard acts as it should. I'm not happy with this workaround, but at least I can get some work done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
maybe try finding a keyboard ime and enabling it so it profiles the keyboard input.
http://www.androidpolice.com/2013/0...-compatibility-with-many-bluetooth-keyboards/
Sent from my Nexus 7 using xda app-developers app
https://code.google.com/p/android/issues/detail?id=58467
Here is a bug report for Bluetooth keyboards dropping when using WiFi.
Sent from my Nexus 7 using Tapatalk 2
BubbleSort said:
Is anyone else having issues with their bluetooth keyboard when paired with the Nexus 7? I have an Apple Bluetooth keyboard and it repeats characters, and inserts the spaces out of order.
(Yes I'm aware of External Keyboard Helper, and it does help but it makes my typing laggy)
Click to expand...
Click to collapse
Verified. I stopped using my Apple Keyboard with my N7 for this reason. It worked perfectly with the previous gen N7 (2012).
Thank God CM 10.1 added support on the Nook HD+ last week! Yay for CyanogenMod!!
Ironically, my crappy knockoff Chinese BT keyboards work perfectly. It's the exact same as the Saxony Bluetooth Keyboard on Amazon, but I bought it off the boat from China.
My Microsoft Mouse 5000 is also very sketchy with BT on the N7. Again, works perfectly on Nook CynogenMod, and previous N7 (2012).
-Pie
BubbleSort said:
https://code.google.com/p/android/issues/detail?id=58467
Here is a bug report for Bluetooth keyboards dropping when using WiFi.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I have the same problem with my Logitech bluetooth keyboard. It works fine until I turn on wifi, after which is starts disconnecting and reconnecing every few seconds. It's completely unusable. Didn't have this problem with the same keyboard on my Nexus 10 or Nexus 7 (2012).
Typing this on my HP Touchpad Keyboard. No disconnects or erratic key behavior here. Some of the function keys don't work as expected, but volume up/down, media keys, and power key works just fine in additon to the normal array of keys. Running CM10.2 unofficial nightly 8/12 and elementalX 0.9 kernel. Had stock for like 3 hours so i didn't get a chance to try the keyboard out with that.
Sent from my Nexus 7 using Tapatalk 4 Beta
Called Google support
BubbleSort said:
Is anyone else having issues with their bluetooth keyboard when paired with the Nexus 7? I have an Apple Bluetooth keyboard and it repeats characters, and inserts the spaces out of order.
(Yes I'm aware of External Keyboard Helper, and it does help but it makes my typing laggy)
Click to expand...
Click to collapse
So I called Google support (24 hour line) and spoke to them about the keyboard issue
(I too have an apple bt keyboard)
from my understanding of what they told me, bluetooth 2.0 (which many keyboards run on) is running at about 2.385Ghz band while the 2.4Ghz wifi band is there very near it. In fact, it is near enough that it will interfere with the polling.
I asked why it doesnt happen with my SGS4 SGH-I337 (aka AT&T version) and they told me it is because it (the SGS4) is running a Qualcom processor, whereas the N7 (Flo) is running a Snapdragon processor.
Last i heard of the Snapdragon processors, they were integrating Bluetooth and Wifi onto the same processing chip which would make sense as to why we have the bluetooth lag.
The rep advised me to try out and/or get a bluetooth 3.0 or higher keyboard saying that should alleviate the problem. This would make sense as to why some people are having this issue while others are not (such as the logitech K810 keyboard)
Just my 2 pennies
I'm using Microsoft Wedge Mobile Keyboard (BT) with External Keyboard Helper Pro and I don't have any problem.
I'm using the wedge as well. No problems at all.
Sent from my Nexus 7 using Tapatalk 4
This is one annoying problem. Have tried all the BT keyboards I have and they all have the repeating char issue.
Same keyboards were all working on my N10 previously on CM10.1 (aka 4.2.2). Have not tried it since updating to CM10.2 since my daily driver is now the 2013 N7. I'm going to try this and see if it is an issue with 4.3 or something specific to 2013 N7.
I have to say it's been so nice taking the BT keyboard for granted. Having to type on the virtual keyboard onscreen is such a pain.
BubbleSort said:
Is anyone else having issues with their bluetooth keyboard when paired with the Nexus 7? I have an Apple Bluetooth keyboard and it repeats characters, and inserts the spaces out of order.
(Yes I'm aware of External Keyboard Helper, and it does help but it makes my typing laggy)
Click to expand...
Click to collapse
Works (mac alu kb, german layout + nexus7 lte, original untouched rom JLS36C) in any combination of BT, Wifi or 3G without issues here.
http://forum.xda-developers.com/showthread.php?t=2432018
I even type this post in the n7's chrome browser right now :victory:
Hi:
My Perixx folding BT keyboard doesn't work with 4.3 period, not on the Nexus 7 2013 nor Nexus 7 2012. My friend is using it on his Nexus 7 2012 running 4.22, not yet upgrading to 4.3.
On 4.3 it pairs but the keyboard won't type anything, a paper-weight.
Tom
So it's quite likely this isn't fixable via software and the only way around it is either to replace the keyboard with a BT3.0 device OR upgrade your router to one which supports 5.0ghz wifi?
I have the same issue with everyone here.
My keyboard is Microsoft Wedge Mobile Keyboard which using Bluetooth 3.0 technology but it no help
Hi all, I just bought a COD (TM) Bluetooth Keyboard Stand from Amazon. The stand is great, but the bluetooth keyboard keep losing its connection, even when I'm typing.
What could be the cause? Does anyone know how to fix this? Your help is much appreciated.
EDIT :
Try this to fix your BT problems .
Go to settings > Connections > Bluetooth > Hit menu button > Visibility Timeout > and change it to Never
Thanks to Geordie Affy.
Thanks in advance.
eddlum25 said:
Hi all, I just bought a COD (TM) Bluetooth Keyboard Stand from Amazon. The stand is great, but the bluetooth keyboard keep losing its connection, even when I'm typing.
What could be the cause? Does anyone know how to fix this? Your help is much appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Try disabling the onscreen keyboard when connected to bluetooth. Some have reported this to help. I do not know for sure as I dont have BT Keyboard yet. There is some talk in one of the threads here about it. I dont remember where ATM but will look again for it and post a link to it if I can find it. Otherwise you can search in the threads for it here yourself
Here is the link I mentioned:
http://forum.xda-developers.com/showthread.php?t=2526070
ArticFox918 said:
Try disabling the onscreen keyboard when connected to bluetooth. Some have reported this to help. I do not know for sure as I dont have BT Keyboard yet. There is some talk in one of the threads here about it. I dont remember where ATM but will look again for it and post a link to it if I can find it. Otherwise you can search in the threads for it here yourself
Here is the link I mentioned:
http://forum.xda-developers.com/showthread.php?t=2526070
Click to expand...
Click to collapse
BarryH_GEG said:
Click to expand...
Click to collapse
Thanks for your reply. I tried this trick with no luck. It automatically switch back to Samsung keyboard after 2 second. Grrrrr...very annoying
Google "android 4.3 bluetooth keyboard". Android 4.3 breaks most bluetooth keyboards and it appears Google has no desire to fix it with 4.4 out now. There are fixes out there but they involve rooting and voiding your warranty on this tablet. I think those of us who use bt keyboards and want a warranty will just have to wait for Samsung to roll out 4.4.
I almost returned the tablet over this but I get enough out of it that I'll wait. Hopefully they'll roll out 4.4 soon.
Sent from my SM-P600 using xda app-developers app
LaRoach said:
Google "android 4.3 bluetooth keyboard". Android 4.3 breaks most bluetooth keyboards and it appears Google has no desire to fix it with 4.4 out now. There are fixes out there but they involve rooting and voiding your warranty on this tablet. I think those of us who use bt keyboards and want a warranty will just have to wait for Samsung to roll out 4.4.
I almost returned the tablet over this but I get enough out of it that I'll wait. Hopefully they'll roll out 4.4 soon.
Click to expand...
Click to collapse
I use my Samsung BT keyboard for hours on end and have never had a single issue with it. If BT is on, my N10.1-14 auto-connects when I turn on my BT keyboard and disables the onscreen keyboard. Samsung doesn't use Android's stock BT stack so any problems in generic Android wouldn't affect their devices. There are quite a few people here that aren't having issues with BT keyboards which would lead me to believe that it's the keyboards that some people are using that are causing issues. Interestingly, I had issues with the same keyboard I'm using now on my N10.1-12 where it would fight with the onscreen keyboard and randomly pop-up accented characters if I typed something like an "a" and left my finger on the key too long. It drove me crazy and I don't have any of those issues with the N10.1-14.
It's not clear exactly what the problem is, but here are a couple of observations, from what I've noticed:
- In some cases, the problem may be related to conflicts with other apps installed. The problem became much less noticeable after i uninstalled MightyText. May be coincidence, but I definitely see a big improvement. I still get an occasional disconnect with the Logitech K810, at most once every half hour of so. When MightyText was installed, I got disconnected every couple minutes.
- I also have a Samsung BT keyboard. I very rarely get disconnects with the Samsung KB.
@BarryH_GEG
I'd like to know where it was published that Samsung isn't using the stock Android BT stack? I've tried numerous keyboards that work with my desktop, iphone, and original GN 10.1 without any issue whatsoever, but are useless with this tablet. All of the symptoms are consistent with what others have reported on android 4.3. Hard to imagine that being a coincidence. Glad you found one keyboard that works. We can add it to the (short) list of ones that do.
dpersuhn said:
@BarryH_GEG
I'd like to know where it was published that Samsung isn't using the stock Android BT stack? I've tried numerous keyboards that work with my desktop, iphone, and original GN 10.1 without any issue whatsoever, but are useless with this tablet. All of the symptoms are consistent with what others have reported on android 4.3. Hard to imagine that being a coincidence. Glad you found one keyboard that works. We can add it to the (short) list of ones that do.
Click to expand...
Click to collapse
Kind of simple really. BT's been broken in AOSP since 4.2.
Bluetooth Is Basically Broken
Known affected devices: Nexus 10, Nexus 7, Galaxy Nexus.
Documented? Android bugs [1] [2], XDA [1] [2], Google+.
We've already received numerous emails about this issue, and I've confirmed it myself: Bluetooth on everything but the Nexus 4 (apparently) is in an absolutely sorry state right now. Audio streams extremely choppily, sounds mediocre, and often loses connectivity entirely. 3rd party Bluetooth apps that create compatibility with devices like the Sixaxis or Wii controllers no longer function at all, and throw an error instead.
This is bad. This is the kind of thing that makes someone return a phone or tablet, because A.) people have no patience for stuff like this, and B.) there's zero reason something as simple as Bluetooth should be broken so badly out of the box. Google needs to mark this one "critical" and fix it ASAP.
http://www.androidpolice.com/2012/1...major-issues-plaguing-googles-newest-release/
Samsung's 4.2 devices weren't affected which means they had to be using either their own BT s/w or made major modifications to BT in AOSP. As for a "short list," how do we know it's of "working" peripheral's vs. "broken" peripheral's? I've only seen about a half-dozen BT connectivity complaints and really wasn't aware of the problem until it was pointed out to me in another thread. In my case I have about six BT devices I use regularly including speakers, headphones, mice, and keyboards and if asked I'd say they work better on the N10.1-14 then they did on the N10.1-12. I'd define "better" as connecting faster automatically, staying connected, and playing well with others when multiple BT devices are connected. To your point, I could be the anomaly but as posted in this and other threads disabling the onscreen keyboard and checking for conflicting s/w seems to have helped some people so it wouldn't appear BT issues are that widespread (yet).
I agree that the onscreen keyboard adds much to the frustration, as it's default behavior mimics the problems folks have been reporting on other 4.3 devices. Most of what I've come across cites keyboard issues that many have experienced immediately after upgrading to 4.3, but that doesn't really meet the requirements of being evidence either. I suppose the only real way to know would be to grab the base android build that Sammy used and compare files.
As for compatibility issues beyond keyboard input, I can't really speak to that, as I only have a few audio devices and one gamepad. It isn't really a large enough sampling to suggest that the entire stack is hosed up. My issues have been entirely related to BT keyboards, so I'm more focused on that.
You mention conflicting software, which brings up a question. Since the BT stack would be considered part of the protected core OS, apps would require root to mess with it, wouldn't they? The six axis app being a good example, as it requires root. To hook the BT stack at a low enough level to add profiles or override existing ones for compatibility isn't something that should be possible with a user level app. I could be off base here and the reports of user apps affecting BT are an interesting coincidence, but I'm not sure I can quite see where the two cross paths. The alternative is surely more concerning, as it would imply that core OS functions in this tablet are somehow exposed to being overridden by user space apps.
dpersuhn said:
I agree that the onscreen keyboard adds much to the frustration, as it's default behavior mimics the problems folks have been reporting on other 4.3 devices. Most of what I've come across cites keyboard issues that many have experienced immediately after upgrading to 4.3, but that doesn't really meet the requirements of being evidence either. I suppose the only real way to know would be to grab the base android build that Sammy used and compare files.
As for compatibility issues beyond keyboard input, I can't really speak to that, as I only have a few audio devices and one gamepad. It isn't really a large enough sampling to suggest that the entire stack is hosed up. My issues have been entirely related to BT keyboards, so I'm more focused on that.
You mention conflicting software, which brings up a question. Since the BT stack would be considered part of the protected core OS, apps would require root to mess with it, wouldn't they? The six axis app being a good example, as it requires root. To hook the BT stack at a low enough level to add profiles or override existing ones for compatibility isn't something that should be possible with a user level app. I could be off base here and the reports of user apps affecting BT are an interesting coincidence, but I'm not sure I can quite see where the two cross paths. The alternative is surely more concerning, as it would imply that core OS functions in this tablet are somehow exposed to being overridden by user space apps.
Click to expand...
Click to collapse
Great post and it touches on one of Android's key weaknesses. "Core" like everything else is nothing but a guideline. OEMs like Samsung and app developers color outside the lines all the time for their own benefit. In Samsung's case it was beneficial because BT in 4.2 was a mess and based on your findings still is so Samsung's meddling helped their audience. Android's kind of like the wild wild West in that regard. Add to that something like BT which itself is kind of like the wild wild West with frequent complaints about incompatibility between devices and you end up with the situation we're discussing. In every phone forum I've seen there's always multiple threads on "can't connect to my [insert brand of car]'s BT system." If the phone and car's BT implementation followed prescribed standards that wouldn't be the case. But who knows who's fault it is - the device OEM or the car manufacturer.
Here's another thing to consider about Samsung devices. ROMs from different regions with the same build and change list number released within days or weeks of each other can have different versions of included apps and s/w. As an example, some users on the N10.1-12 forum couldn't import PDFs in to S Note while the majority could. Those that could successfully imported the same PDFs that those that couldn't were having issues with. With some sleuthing we discovered there were almost a dozen different versions of S Note and that two had the PDF issue. And that was with the N10.1-12 being out for about three months. I'm on a Latin American SM-601 so there's the possibility that my BT might be different from U.S. (and possibly other region) SM-600's.
You might want to try a Samsung BT keyboard that you can return if you want to see if the BT issue is pervasive. If Samsung's KB works then you'll know that BT isn't totally borked and that perhaps updates might correct incompatibility issues with other keyboards.
The OEM customizations necessary to fit android to a particular platform is a necessary part of enabling the OS on vendor specific hardware platforms. I get that part, but replacing the entire stack instead of just creating the kernel driver component would definitely be an aggressive move. If this is the case, I would really be surprised that apps outside of the ones Samsung has written or bundled would be able to interfere with it. Maybe I'm giving samsung too much credit by assuming that they would leave the baseline android security model intact, but to deviate from it that badly is asking for a major vulnerability trainwreck. The inclusion of Knox (I won't get started on that in this thread) would imply that they are trying to prevent such a thing.
I obviously don't have the details necessary to speak decisively about what Samsng May or may not have done, but if what you say is correct and they have inserted some other BT stack, KitKat may not help us either. The stock BT stack in it adds support for HID over GATT (HOGP), enabling A number of BT 4.0 LE devices that currently won't work (MS Arc Touch for Surface Pro, for example). I'm hoping we might see an update to 4.4 in Q1 '14, so it'll be interesting to see how an updated release affects BT functionality.
Anyone try the app external keyboard helper?
Sent from my SM-P605 using XDA Premium HD app
matsuru said:
Anyone try the app external keyboard helper?
Click to expand...
Click to collapse
I gave the free version a shot but it didn't work. I tried some of the steps listed for Samsumg devices as well but no go...
matsuru said:
Anyone try the app external keyboard helper?
Sent from my SM-P605 using XDA Premium HD app
Click to expand...
Click to collapse
I tried it as well with no luck. Bluetooth keyboard connection is very intermittent. Connection still broken while typing.
Sent from my SM-P600 using XDA Premium HD app
I have a logitech k810 bluetooth keyboard and have no issues with disconnects, whatsoever. Maybe its a problem with the keyboards trying to conserve energy?
ChrisNee1988 said:
I have a logiteck k810 bluetooth keyboard and have no issues with disconnects, whatsoever. Maybe its a problem with the keyboards trying to conserve energy?
Click to expand...
Click to collapse
Could you describe your device details?
I'm having this problem with logitech k810 keyboard and android mouse. I have the pro version of the keyboard helper and it has no effect.
Here is a video of the issue = http://youtu.be/WlCgFQ0cAO0
It is much worse with the keyboard than the mouse. My Note 3 running android 4.3 has no issue with galaxy gear, keyboard, mouse and allshare cast all connected at once. I expected the same out of this tablet. I may be returning this tablet, I do not find this acceptable.
My device is a 32GB white SM-p600 USA version.
BT problem exists at initial boot, and was tested after each incremental firmware update to still be present.
Action B said:
Could you describe your device details?
I'm having this problem with logitech k810 keyboard and android mouse. I have the pro version of the keyboard helper and it has no effect.
Here is a video of the issue = http://youtu.be/WlCgFQ0cAO0
It is much worse with the keyboard than the mouse. My Note 3 running android 4.3 has no issue with galaxy gear, keyboard, mouse and allshare cast all connected at once. I expected the same out of this tablet. I may be returning this tablet, I do not find this acceptable.
My device is a 32GB white SM-p600 USA version.
BT problem exists at initial boot, and was tested after each incremental firmware update to still be present.
Click to expand...
Click to collapse
I saw your video (nice nicknames for mouse and note btw). I have the USA p600 16GB wifi only - white. I don't have a bluetooth mouse so I can't try that but it seems to work flawlessly with my K810 keyboard with my limited trials. I haven't done any extensive like write a paper but i've done some messaging and emails. Also i've only tried it with the latest firmware. I'd recommend doing a factory reset, and if that doesn't fix it, maybe exchange it for another unit.
Action B said:
BT problem exists at initial boot, and was tested after each incremental firmware update to still be present.
Click to expand...
Click to collapse
Since there's no possible s/w conflicts and I'm assuming you disabled the onscreen keyboard during your testing it might be the keyboard itself. If your keyboard is older/newer than @ChrisNee1988's it might have a different chip or f/w in it. Peripherals aren't built to exacting standards whereas it's unlikely for there to be h/w differences between two SM-600's built so close together.
BarryH_GEG said:
Since there's no possible s/w conflicts and I'm assuming you disabled the onscreen keyboard during your testing it might be the keyboard itself. If your keyboard is older/newer than @ChrisNee1988's it might have a different chip or f/w in it. Peripherals aren't built to exacting standards whereas it's unlikely for there to be h/w differences between two SM-600's built so close together.
Click to expand...
Click to collapse
The keyboard works great on my note 3 so it's fine.
Sent from my SM-N900P using Tapatalk