Related
I'm using HTC Trinity WM6 and wish to use my old Stowaway universal Bluetooth keyboard working? i cannot find driver for WM6. anyone have it?
please help!! i love my BT keyboard and wish to get it work again.
thanks
Attached is the driver I use for my Kaiser WM6/6.1, dunno if it'll work on your Trinity or not.
If not here is the drivers page: http://corporate.igo.com/support/Drivers.asp. Just choose your manufacturer and model.
Note that WM6 comes with basic keyboard drivers -- you only need to install a driver if you want to use special functionality such as customized keys. I use the built-in drivers on my Kaiser with a BT keyboard (not the Stowaway, but supposedly compatible).
htc tytn II and sierra bt keyboard
everybody,
trying to connect / use my new sierra bt keyboard with my htc tytn II and nothing works,.... if i go through the htc the keyboard is detected, asks for a security code, does not recognise the one i put in, (although the instructions say pick one of your choice), and does not connect.
if i go through the keyboard CAB installed on the htc, still cannot connect,.... i am not exactly a 'newbie' but if someone could give a step by step direction on how to get this to work, i would be very grateful,....
thanks,
ek
sorry everyone, i used elyspar's CAB file on my htc tytn II,.... thanks for your help,....ek
found a vid on youtube very helpful,.... it's actually quite simple to connect, so maybe i need to retract, i am a newbie,....
here's the link, http://www.youtube.com/watch?v=P8HAge9yJu4
no functionality though, just basic input, good for emails / word, but limited,....
guess i have to install the driver on my kaiser somehow,....
Hi everybody, can you tell me which driver i have to install for my Niki? It's not on the list...
Thank you very much.
ekacz24 said:
everybody,
trying to connect / use my new sierra bt keyboard with my htc tytn II and nothing works,.... if i go through the htc the keyboard is detected, asks for a security code, does not recognise the one i put in, (although the instructions say pick one of your choice), and does not connect.
if i go through the keyboard CAB installed on the htc, still cannot connect,.... i am not exactly a 'newbie' but if someone could give a step by step direction on how to get this to work, i would be very grateful,....
thanks,
ek
Click to expand...
Click to collapse
I could use an Apple Alu BT KB with HTC TyTN (not II). Paired. Without any special driver. Remember to press Enter on the KB after the code. Now I have a new Touch HD and I get it paired but nothing happens clicking on the keyboard...
I will start installing drivers which I find here suggested and will report.
iGo stowaway BT keyboard and WM6
Hello all,
I originally posted this message in a Blackstone forum, but as this problem probably relates to WM6 in general I thought I would post here
I have an igo bluetooth keyboard and I am using Blackstone phone (running the usual WM6.1 proffessional. I installed the igo software and everything worked fine except that phone crashed a lot. Not so useful. I then uninstalled the software and paired the keyboard using the onboard Bluetooth keyboard drivers. All worked well for one run through and I was able to type away. However I have not got the thing to work again since, even after re-pairing the devices. Does anyone haev any thoughts about what I might be doing wrong?
Thanks.
Tom
Hello Guys, partly not to the topic hear....
I have an igo stowaway keyboard and a travel mouse and i have been using them with my fusi n560 (wm 6.0). Now I bought a Nokia 5800 mobile phone with symbian s60v3 touch. The keyboard came with multiple driver including both wm and symbian versions, but the mause came only with wm driver. Now the question is: do you happen to know how could I use my mouse with my symbian device? Sorry for asking symbian related question here....
Special Characters and the Sierra Stowaway
I have previously used the Sierra Bluetooth Keyboard and it worked flawlessly on my T-Mobile Wing running WM5... I recently tried to port the same driver suggested by ek... (PPC5) to the T-Mobile HTC Touch Pro2, WM6.1.
It works on all keys, including the function keys, but cannot produce the specialty characters on the 5th, number-row, i.e., [email protected]#$%^&*()
Everything else seems to work fine... anybody come across a fix for this?
Thanks!
JSS
I've been interested in acquiring an Apple Wireless Keyboard for my PDA too.
But from skimming other people's post, looking at what was successful on the internet (e.g. the guy on youtube with the Mio who paired with the Apple BT Keyboard), it seems that all the success stories come from people running WM5/6
Anything 6.1 and above seems to not work in general, although you have some success stories like from http://forum.xda-developers.com/showthread.php?t=486595
Has anyone successfully paired with 6.1-6.5?
jstapley said:
I have previously used the Sierra Bluetooth Keyboard and it worked flawlessly on my T-Mobile Wing running WM5... I recently tried to port the same driver suggested by ek... (PPC5) to the T-Mobile HTC Touch Pro2, WM6.1.
It works on all keys, including the function keys, but cannot produce the specialty characters on the 5th, number-row, i.e., [email protected]#$%^&*()
Everything else seems to work fine... anybody come across a fix for this?
Thanks!
JSS
Click to expand...
Click to collapse
I have similar problems with my Samsung Omnia, WM6.1 and the German Stowaway Keyboard (QWERTZ) with the driver 4.51.
Just the keys !$& are not working.
Could there be a workaround like using ASCI numbers?
I tried ALT+33 to get a "!" but had no success.
Does anybody else has some suggestions?
Thanks,
Sigi
sigi-s said:
I have similar problems with my Samsung Omnia, WM6.1 and the German Stowaway Keyboard (QWERTZ) with the driver 4.51.
Just the keys !$& are not working.
Could there be a workaround like using ASCI numbers?
I tried ALT+33 to get a "!" but had no success.
Does anybody else has some suggestions?
Thanks,
Sigi
Click to expand...
Click to collapse
I solved my problem:
I installed the English driver 4.52
(I have an English ROM and use a German Keyboard)
The driver was changed from version Ger4.51 to Eng4.52 on several places and I think they solved some Bugs.
I resetted my Omnia after the installation.
Because the problem still existed, I resetted the Omnia once again, while the Stowaway keyboard was selected in the keyboard menu.
After that reset all the characters worked like the should.
Hope that helps.
I'm having trouble pairing my Desire my with Parrot bluetooth car kit. Keeps saying pairing failed on the phone, which is set to discoverable. I've tried 0000 and 1234 as the codes and neither seem to work. (Can't remember using a code for the iphone) I have also cleared all paired devices on the parrot to start from scratch and no luck
any ideas?
Just managed to fix this, and for anyone having issues the reason it wasnt pairing/accepting the 1234 code was that I was holding the letters to input those numbers, switched the keyboard to numbers, input it, and it paired first time..
confirmed: when it pops up to enter the bluetooth code, change the keypad to numbers and type the 1234. It will pair immediately.
not sure where is the bug on HTC or Parrot side... but at least we have a workaround
dolon said:
confirmed: when it pops up to enter the bluetooth code, change the keypad to numbers and type the 1234. It will pair immediately.
not sure where is the bug on HTC or Parrot side... but at least we have a workaround
Click to expand...
Click to collapse
slightly odd isn't it! at least there's a way to do it!
There is no bug, the keypad simply shows the location of the numeric characters on the alpha keys for when you do switch to the numeric/symbol pad. I'm presuming you had it on alpha when entering numbers. My 3100 connected no problem.
Sent from my HTC mDesire using the XDA mobile application powered by Tapatalk
[email protected] said:
There is no bug, the keypad simply shows the location of the numeric characters on the alpha keys for when you do switch to the numeric/symbol pad.
Sent from my HTC mDesire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Say what ?
When you press and hold an alpha key, say "R", the number 4 is displayed in green, tap it and it enters the number "4" into the input box.
HTC Desire + Parrot 3100 and 3300 + SatNav
Hi
Was wondering if anyone who has the Desire and a parrot carkit has tried any satnav apps with it? I have and the results are a odd! First of all the instructions are not routed through the car stereo which they were with previous winmo devices (this is not a big problem for me tho) however they ARE routed trhough the car stereoWith NDrive and Sygic Mobile Maps ONLY when IN A CALL!!! which really IS a problem since you can not hear a thing the caller says during the voice instructions it is that loud!! Any ideas how I can stop the app using the bluetooth connection for instructions when in a call?
It seems totally the wrong way round.. voice instructions through the phone speaker when not in a call and through the car when in a call
i'm also wondering this.. best to start a new thread i think.
Original message regarding paring HT Desire and Parot CK3100
Hi, i'm also having difficulty paring my devices. I note your comments regarding using the correct keyboard. I'm only presented with a numeric keyboard and i've tried everying to get a different one so i can try what was suggested above for paring.
Any help anyone can provide me with this would be much appreciated.
Thanks in advance.
Simon
selby1 said:
Hi, i'm also having difficulty paring my devices. I note your comments regarding using the correct keyboard. I'm only presented with a numeric keyboard and i've tried everying to get a different one so i can try what was suggested above for paring.
Any help anyone can provide me with this would be much appreciated.
Thanks in advance.
Simon
Click to expand...
Click to collapse
I just found on another forum, that you have to delete other old paired devices from Parot CK3100 in some cases to pair with a new phones.
Try this and let us know.
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 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
Device: sm-t715 (purchased eBay, factory refurbished)
build number NRD90M.T715XXU2CQCL
Android 7.0 installed
Keyboard device Lenovo thinkpad ebk-209a German DIN
Searched Google and XDA, no related results.
This keyboard works fine on both my previous tab (T713) and my phone (sm-g900v), but the settings for my new t715 won't let me set the keyboard type, which renders the keyboard useless. The default is US english, and this is different from the bluetooth keyboard in several respects. Is there some back way in, or do I need to get a different ROM for it? If the latter, where would I find it (or do one of you have one)?
Additional data availabe on request.
Gnudoll said:
Device: sm-t715 (purchased eBay, factory refurbished)
build number NRD90M.T715XXU2CQCL
Android 7.0 installed
Keyboard device Lenovo thinkpad ebk-209a German DIN
Searched Google and XDA, no related results.
This keyboard works fine on both my previous tab (T713) and my phone (sm-g900v), but the settings for my new t715 won't let me set the keyboard type, which renders the keyboard useless. The default is US english, and this is different from the bluetooth keyboard in several respects. Is there some back way in, or do I need to get a different ROM for it? If the latter, where would I find it (or do one of you have one)?
Additional data availabe on request.
Click to expand...
Click to collapse
Bump
[SOLVED!?!]
I did nothing, but it is working now (at least the keyboard type is correct for the keyboard). I do not know which is worse: The inital problem? or it seeming to fix itself, with nothing done by me? It is not a solution, but it is working. . .