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
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.
There are various threads on this forum concerning bluetooth connectivity to the GN 10.1 2014. Most notably, keyboards that keep disconnecting.
I ran into this problem with my Logitech K810 keyboard, which works perfectly on my PC, as well as my Ipad 2 and my Galaxy S4. Three different units, three different operating systems, and with flawless performance.
Then I buy the pinnacle of Tablet technology; a spanking new Galaxy Note, and realize that the keyboard disconnects every three to five seconds.
This is something like buying a shining new bike, coming home full of expectations, and unpack it. Only to discover that the wheels are stuck. They won't turn. It would have been hilarious, if the tablet wasn't so bloody expensive.
I tried various "keep bluetooth alive" and "change to another screen keyboard" apps, to no avail. Then I read a thread from someone who could make the keyboard work if they played music to another unit via bluetooth: I tried this, and voila! As long as I keep my phone paired and connected to the note, the keyboard works perfectly.
This could give a hint as to the nature of the problem; could it be that the keyboard, unlike the Galaxy S4, doen't actively work to keep the bluetooth radio active when you are not typing, and that what ppl assume to be Samsung's new implementation of the bluetooth standard in the GN 10.1 2014 doesn't take such devices into account?
If that is the case, the problem should not be related to hardware issues with the bluetooth antenna, like someone suggested, but is more likely software-related, and hence, a bugfix shouldn't be impossible.
Could this be achieved with an app written by some skilled coder, or do we have to wait for a bugfix from Samsung? Any ideas guys?
Finurliig said:
Could this be achieved with an app written by some skilled coder, or do we have to wait for a bugfix from Samsung? Any ideas guys?
Click to expand...
Click to collapse
It's a h/w problem. There are plenty of N10.1-14 owners that aren't having any BT issues including with the K810 which comes up frequently. I have a BT mouse and keyboard connected for hours at a time without any disconnects. I leave BT on continually on my N10.1-14 and as soon as the mouse or keyboard are turned on they connect immediately. There's a lot of discussion in the BT thread in the general section discussing possible causes on devices having problems. Exchange it or send it in for warranty repair.
BarryH_GEG said:
It's a h/w problem. There are plenty of N10.1-14 owners that aren't having any BT issues including with the K810 which comes up frequently. I have a BT mouse and keyboard connected for hours at a time without any disconnects. I leave BT on continually on my N10.1-14 and as soon as the mouse or keyboard are turned on they connect immediately. There's a lot of discussion in the BT thread in the general section discussing possible causes on devices having problems. Exchange it or send it in for warranty repair.
Click to expand...
Click to collapse
Thanks for advice, but for an exchange of the device to be meaningful, we will need some confirmation that Samsung has identified the problem and corrected it?
Finurliig said:
Thanks for advice, but for an exchange of the device to be meaningful, we will need some confirmation that Samsung has identified the problem and corrected it? Besides, they refused to do just that when I spoke to their support? Nevertheless: I will mail them again about this. Thanks!
Click to expand...
Click to collapse
If you bought from Samsung, I'm not surprised they told you they would not exchange it. Samsung told me they don't warrant that their product will work with a third-party product. They also said there were no Samsung keyboards at this time that were compatible with this tablet. Fortunately I got mine from a retailer that was willing to exchange. Unfortunately the second unit I got about two weeks ago also has the problem.
Your best bet might be to send it to Samsung rather than play "exchange roulette." Here's what to tell Samsung customer support...
"Hi Mary, I spoke to someone earlier about a BT problem I was having. The BT peripherals I connect work fine initially but can't maintain a connection; meaning they drop the connection and either I have to reconnect them manually or sometimes they'll reconnect themselves only to drop out again. The person I first spoke to was pretty sure it was the devices I was connecting and not my tablet.
Here's what I did. I completely reformatted my tablet to the way it came out of the box. I didn't even allow any of my apps to be loaded on it after I reset it. So it was a clean untouched stock as it left the factory Samsung configuration. The same problems of random disconnection occurred. I went to Best Buy and they were really nice. They allowed me to connect all the BT peripherals I was having problems with to their three floor models. They all worked fine and kept the BT connection active. So clearly, there's something wrong with my individual tablet.
I have a couple of friends with this tablet and while the majority of their devices work fine some are having the same issue I am. There's obviously something wrong with a subset of these tablets for individual examples to perform differently with the exact same BT peripherals."
If you still meet resistance...
"I'm sorry you won't help me get my problem solved. Do you think a supervisor might be able to help me or should I just contact the BBB and my local attorney general's office as you're refusing warranty work I'm entitled to in spite of the steps I've taken to isolate a problem and demonstrate to you that there's an issue with my specific tablet. Also, can you please give me your name again? I didn't write it down when you came on the call."
Thanks BarryH.
engaged ricultsc
Good Evening.
There are new on this issue?
I have k810 keyboard too, and in the beginning the keyboard worked normally, but lately, I have more and more disconnections.
Before, it was enough for me to restart the tablet, and the keyboard walked fine.
But now, I have constantly disconnections, every 5 seconds.
It becomes unusable
I tried to flash roms of over counties, I tried CleanRom, but the problem stays.
I'm worried, because my Knox is on 1, and I just read that Samsung voids the warranty, regardless of the problem...
Do you found other solutions since?
(.. and sorry for my bad english..)
.....
Finurliig said:
There are various threads on this forum concerning bluetooth connectivity to the GN 10.1 2014. Most notably, keyboards that keep disconnecting.
I ran into this problem with my Logitech K810 keyboard, which works perfectly on my PC, as well as my Ipad 2 and my Galaxy S4. Three different units, three different operating systems, and with flawless performance.
Then I buy the pinnacle of Tablet technology; a spanking new Galaxy Note, and realize that the keyboard disconnects every three to five seconds.
This is something like buying a shining new bike, coming home full of expectations, and unpack it. Only to discover that the wheels are stuck. They won't turn. When you call the manufacturer support; which I did in relation to the Note, they politely inform you that they have never guaranteed theat the wheels on the bike would turn. They have only said that the bike HAS wheels,..... not that they can actually be used for anything..... so they refuse to take responsibility, and refuse to give you a refund.
This is, in point of fact, the answer I got from Samsung: they market the unit as having bluetooth functionality, but won't take responsibility if it doesn't work, and the user is stuck with a pieece of equipment that can't be used for the intended purpose. It would have been hilarious, if the tablet wasn't so bloody expensive.
So much for Samsungs costumer support. Now to my own investigation into this problem:
I tried various "keep bluetooth alive" and "change to another screen keyboard" apps, to no avail. Then I read a thread from someone who could make the keyboard work if they played music to another unit via bluetooth: I tried this, and voila! As long as I keep my phone paired and connected to the note, the keyboard works perfectly.
This could give a hint as to the nature of the problem; could it be that the keyboard, unlike the Galaxy S4, doen't actively work to keep the bluetooth radio active when you are not typing, and that what ppl assume to be Samsung's new implementation of the bluetooth standard in the GN 10.1 2014 doesn't take such devices into account?
If that is the case, the problem should not be related to hardware issues with the bluetooth antenna, like someone suggested, but is more likely software-related, and hence, a bugfix shouldn't be impossible.
Could this be achieved with an app written by some skilled coder, or do we have to wait for a bugfix from Samsung? Any ideas guys?
Click to expand...
Click to collapse
I have had the same problem with a bluetooth keyboard and mouse not working correctly, I found if I turn off the wifi radio on p600 I have up to 3 co current bluetooth connection going at he same time. when the wifi is on and active the bluetooth is dropping off think it has to do with wifi 4.0 radio in the tablet or the placements of the attennas in the tablet.
What I do is connect a bluetooth device to play music continuesly, so that the connection doesn't drop. Then the BT keyboard and BT mouse will stay connected. Keyboard and mouse disconnect when you stop typing. The music BT device keep the signal alive, and it never drops. You can try this if you want and check if it works for you.
Sent from my GT-N7100 using Tapatalk
I have not experienced this issue and I use a Bluetooth keyboard and mouse abort 20 hours per week.
Via my Note 3
Bit of an old question now, but I'm getting this on my K810 too Did anyone sort it out?
Theres an app called bluetooth keep alive, it works well
Cheers moabizza, I just tried it and sadly it didn't work Oh well, looks like it's going to have to go back for repair.
Don't send your device in for repair- there's nothing wrong with it. I use a BT keyboard and a BT mouse all the time with this device and they work quite well- the issue is pretty obviously the Logitech K810, not the Note 10.1 .
I haven't seen many threads on this and I am curious as to why it is not a concern for many Android users. Maybe it is because many Android users did not move from Apple like I did. The fact is, Apple is still superior to Android in terms of vehicle bluetooth connectivity. The more you need to look at and operate your phone while driving, the more dangerous driving becomes.
The difference between AVRCP 1.3 and AVRCP 1.5 primarily is the playlist selections. Since my car supports this, with 1.5 (iPhone 5) I would be able to see the contents of my library and browse/select music. Then I switched to a Nexus 6 and didn't have this feature anymore. Just a couple days ago I got the Nexus 5X and I am surprised they didn't change this with Marshmallow.
Is Apple always going to hover over Android with their updated bluetooth stacks?
Seems ridiculous that this is still a problem. Its as if no one want to shed any light on this. Talking about this and no apps that expose the Bluetooth stack and avrcp versions to the users who don't know any better. I would be nice if this was a separate module that could be upgraded independently so users could get the functionality they needed. Companies like Samsung rolling there own stack and adding feature is not a proper fix. This should be Android standard.
I have always been thinking the same thing, why is the
bluetooth stack from Google missing so many features.. I have tried both Samsung and HTC and their stack is just so much better.. But I always end up with a Nexus phone again and longing for a better BT stack...
Sent from my Nexus 7 using Tapatalk
BT overall sucks with the 5X. Hissing, popping, laggy stream kills it for me. It can't keep the connection with my car either while iPhones were trouble free. It's almost 2016. Are we asking for too much?
Thought I would add a way to get some info. This is from android.stackexchange.com/questions/43667/discover-version-of-bluetooth
Turn on bluetooth by going to the home screen, clicking menu->settings bluetooth. Pull that to enabled. Make sure it is on.
On the home screen, click menu -> settings -> applications -> 'running' tab.
An item appears called: "bluetooth share".
A screen pops up with information about the program, but it is sparse.
Also you can go to All tab and "Bluetooth Share" to see its actual version number. Though that might not be very helpful.
Also and old article discussing some of the bluetooth stack changes in Android for what its worth.
lwn.net/Articles/597293/
Sorry for the broken url but I've not posted enough on XDA to be allowed proper urls.
I'm going to try keep posting things I find that might be useful just consolidate more info in one spot. Trying to make this problem clearer for myself.
Is there anything new about AVRCP 1.5 features? May it possible to build and install a custom kernel with bluez support (which afaik has avrcp 1.5 support)?
More info on the bluez stack
http://forum.xda-developers.com/showthread.php?t=2640723&page=1
So i deiced to get the 10" Joying rx3188 unit with android 5.1.1 that recently came on the market. So far I rooted it and got it set mostly how i want, but I discovered an issue with bluetooth. Basic phone pairing and functionality works properly and ive also paired my OBD2link MX unit with it as well for the torque app, which works fine as well. the issue i'm having is that other apps that would use bluetooth, think that bluetooth is disabled on the unit. when i try to have them use bluetooth, they ask if they can turn bluetooth on. Selecting yes hangs the app and i have to force end the app to stop it. Even if i go in to torque, it reads bluetooth as disabled even tough the app itself works fine otherwise.
It seems as if the OS is not properly flagging to apps that bluetooth is turned on as far as i can tell. Is there a workaround for this, or something i can do to signal to apps installed that bluetooth is indeed enabled on the HU?
whitetigerlgt said:
ive also paired my OBD2link MX unit with it as well for the torque app, which works fine as well.
Click to expand...
Click to collapse
whitetigerlgt said:
Even if i go in to torque, it reads bluetooth as disabled even tough the app itself works fine otherwise.
Click to expand...
Click to collapse
Sorry i don't understand, Torque is working for you or not?
But, what's the "bluetooth name" of your device? Because to work properly i think it must be "OBD" or "OBD2", otherwise you have to search an Xposed module that can help you.
I'm having the exact same problem with the same unit also on Lollipop. I've notified the developer in the Forum post below and he is looking into it. This now makes a total of 3 people with the same problem.
http://forum.carjoying.com/thread-52.html
whitetigerlgt said:
the issue i'm having is that other apps that would use bluetooth
Click to expand...
Click to collapse
what apps are you having problems with?
also, what car did you put it in? How does it look? 10 inch screen sounds awesome
I'm having two problems right now. The first is that I am unable to pair my Logitech k810 keyboard, and I am unable to connect to a Bluetooth dongle that is used by my radar detector / laser Jammer with an application called Alp connect. I've found quite a few bugs with this head unit and I'm reporting them all to the developer. It works okay my main concern is that it is quite sluggish and I think that is due to the one gigabyte of RAM and lollipop. I installed it in a 2011 Subaru Impreza
sterod said:
The first is that I am unable to pair my Logitech k810 keyboarda
Click to expand...
Click to collapse
I'm fully on board with the concept "your money your car, do what you want" but what do you use a keyboard for in the car?
Quite often I'm too lazy to unpack my laptop when I have to compose a lengthy email on the go so I prefer to do it with a keyboard rather than try to use the touch screen to bash out a couple paragraphs.
popeye70 said:
Sorry i don't understand, Torque is working for you or not?
But, what's the "bluetooth name" of your device? Because to work properly i think it must be "OBD" or "OBD2", otherwise you have to search an Xposed module that can help you.
Click to expand...
Click to collapse
Torque is working, but if you go to adapter status in torque i shows BT not enabled. And thats the issue, the BT status is off when apps check it. For torque, it does not try to turn on BT to function. other apps do, and when they do, they hang.
I need to somehow flag BT as on for other apps so they dont say they need to turn on BT to work.
CadillacMike said:
what apps are you having problems with?
also, what car did you put it in? How does it look? 10 inch screen sounds awesome
Click to expand...
Click to collapse
apps like tablet talk, or obdlink or solostorm. all think BT is off, and try to turn it on when you want to use the BT obd2 adapter.
its in a Mazda MX-5.
sterod said:
Quite often I'm too lazy to unpack my laptop when I have to compose a lengthy email on the go so I prefer to do it with a keyboard rather than try to use the touch screen to bash out a couple paragraphs.
Click to expand...
Click to collapse
If your objective is to solve the problem get a usb keyboard. They work. If your objective is to get bluetooth keyboards working you might have to wait a long time.
Well, I hope you are wrong as my previous NewsMy NU3001 head unit worked perfectly with it. I'm aware I can use a USB keyboard. In any case I'm happy the developer is willing to try and fix it. What is your source for claiming it will be a long time for it to be fixed?
Also to add to this, im also unable to pair my qstarx 10hz BT gps unit.
It may be helpful to post your Bluetooth concerns in the same thread as mine on the Joying Forum I linked to above so that the developer is aware it's not just me and may encourage him to work on this more quickly.
Just popped my head in over there. I was hoping that peeps here would know of a trick or flag for the OS to make all apps think BT is on. then they could get past the check and just access BT, kinda like what the torque app does.
Yeah if someone finds a way to do that I'd be interested to know how as well. Slightly off-topic did you try installing a custom recovery or the Xposed framework on this unit? I have tried and failed many different types of attempts to do it on this unit.
sterod said:
Well, I hope you are wrong as my previous NewsMy NU3001 head unit worked perfectly with it. I'm aware I can use a USB keyboard. In any case I'm happy the developer is willing to try and fix it. What is your source for claiming it will be a long time for it to be fixed?
Click to expand...
Click to collapse
My source? Joying didn't write the software.
And what relevance does that have to the speed at which the issue can be resolved? It seems that you are just being defeating for no purpose. The developer is willing to help and he has expressed that desire in many Communications I've had with him so far. I prefer to be optimistic and that he has the right people to contact to resolve the issue
sterod said:
Yeah if someone finds a way to do that I'd be interested to know how as well. Slightly off-topic did you try installing a custom recovery or the Xposed framework on this unit? I have tried and failed many different types of attempts to do it on this unit.
Click to expand...
Click to collapse
no. i just have it rooted so far with supersu installed. what feature in xposed could be used to help here?
None that I can think of I was just curious if you had been able to install Xposed. I am curious as to how you were able to install SuperSU, as I was only able to install King root.
sterod said:
And what relevance does that have to the speed at which the issue can be resolved? It seems that you are just being defeating for no purpose. The developer is willing to help and he has expressed that desire in many Communications I've had with him so far. I prefer to be optimistic and that he has the right people to contact to resolve the issue
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Generic_Android_Head_Unit/MCU_Explained