Database Users

Rapoo E6300 bluetooth keyboard problems

Not so much Nexus-7 specifically related, as the problem occurs on both my Droid 4 and my Nexus 7, but I hope someone can help me solve this problem:
Starting from a 'clean' situation with the keyboard unpaired to the tablet, I set the keyboard in pairing mode by pressing the 'connect' button until the bluetooth LED starts flashing rapidly.
I then go to the bluetooth settings of one of the above devices, I select the bluetooth keyboard from the 'available devices' list.
My Android device then prompts me to enter a certain passcode on the keyboard, followed by the ENTER key.
I do this and the keyboard successfully registers in the Android device as a paired device.
At this point I am able to use the keyboard without any problems.
However when I turn off the keyboard, or let it go to sleep, and then turn it back on later, the keyboard connects successfully (I can see 'Connected' in the bluetooth settings screen), but it's not possible anymore to enter any text or use any of the keys.
I try reconnecting several times each time turning the keyboard off in between, but alas, nothing helps.
If I 'unpair' the device from my Android device and re-pair it, it works fine again until the next time I turn it off.
Needless to say it's not really a workable solution having to re-pair the keyboard each time I want to use it.
To rule out the Android devices being the culprit, I have tested the same process with another bluetooth keyboard (Logitech DiNovo Edge) and it doesn't have the problem.
However, using the Rapoo keyboard on a colleagues iphone, everything works perfectly.
I've come across other people having this problem, and some say it used to work fine in Android 2.3, but at this moment I haven't got a device with 2.3 on it to test with.
I tested with a colleagues 2.2 Android phone but that one wouldn't even pair.
I will try tonight with my girlfriends 2.3 Moto Defy+ and report back.

Didn't get around to trying this on 2.3 yesterday.
I also sent an email to Rapoo support asking them if they knew any fix for this, and this was what I got in the mailbag this morning:
Dear Customer,
Hello!
Please note that E6300 is specially designed for Ipad.It works with other computers which use Windows or Mac operation system, the shortcut keys for Ipad may be useless.Besides, the only cell phone it supports is Iphone 4 and the the shortcut keys for Ipad may also useless.
Thanks for your support to our products.
Best regards,
Click to expand...
Click to collapse
What a bunch of horse dung...

i have the same problem with my nexus 7 and the rapoo 6300.
i allready tried different kernels and roms.
at first i also had to repair the keyboard once it disconnects. (happens quite fast, sometimes after not typing for some seconds, but sometimes it keeps connected and usable for about 10 minutes)
but i figured out that you don´t have to repair it when it disconnects. when it says "connected" but it is not possible to write something, just wait some seconds, and it will work. (at least at my device, stock kernel @ smooth rom)
still very annoying, but i think it shows that there is a solution for this problem.
After some research i found out that some people had this problem since android 4.0. (worked fine at gingerbread)
but i tested the keyboard at a friends nexus s with jellybean miui rom and it worked fine.

gnomedroid said:
After some research i found out that some people had this problem since android 4.0. (worked fine at gingerbread)
but i tested the keyboard at a friends nexus s with jellybean miui rom and it worked fine.
Click to expand...
Click to collapse
Another observation, when connected to an Ubuntu 10.04LTS (kernel 2.6.32-44-generic) desktop, the same behavior happens.
To repeat, you can pair the keyboard, and after the first sleep, even when it reconnects (pressing the Connect button helps), it does not generate input events for the desktop either.

Same problem here. Tested with a GNEX and a N10. Even with the latest 4.2.2 it shows the same problem … one sleep and you have to pair again. POS!

Any comments on Nexus 7 with CM or AOSP? I heard these mods use a different keyboard driver...

: I tested with a colleagues 2.2 Android phone but that one wouldn't even pair.
I will try tonight with my girlfriends 2.3 Moto Defy+ and report back.[/QUOTE]
I tested Rapoo e6300 against a HTC desire HD with 2.3.1. No chance: it will not pair. Rapoo can not be used with my N7, it just worked ten minutes after it is paired, and then it starts disconnecting. And no input gets through. Waiting a few seconds have no effect, Bluetooth is basically not working.

Got major connectivity issues with Rapoo E6300 here too on Nexus 7 with SmoothROM 4.4 (Cm based on 4.2.1)
Swapped it for a Rapoo E6100: works great! I did get some issue with reconnecting to Nexus 7 after I tried to pair the keyboard to my HTC
One X (which didnt work at all).
Had to reset the whole connection with nexus, but as long as i dont switch off Bluetooth on the nexus it works fine. Switching off or sleepjng the keybord is fine.
Sent from my Nexus 7 using Tapatalk HD

seriously?

even after the 4.2.2 update bluetooth is still not fully working?
Does anyone here use blueput droid ? Basically turns your phone into a touchpad and keyboard for other devices.. but on every rom, i get "bluetooth stack not supported try a rom like cyanogen" but even on cm10.1 i get this -__-
any help?

I get a different issue. If Bluetooth is enabled the Wi-Fi cuts out on certain streaming apps like Skype, groove ip, and even Google + when scrolling quickly through the feed.
Sent from my Nexus 4 using xda app-developers app

brolic925t said:
even after the 4.2.2 update bluetooth is still not fully working?
Does anyone here use blueput droid ? Basically turns your phone into a touchpad and keyboard for other devices.. but on every rom, i get "bluetooth stack not supported try a rom like cyanogen" but even on cm10.1 i get this -__-
any help?
Click to expand...
Click to collapse
I'm not perfectly clear on the exact reasons, but what I've heard is the BT is wonky because Google switched from a closed source, more compatible BT source to a less reliable open source to be more compliant with the open standard that Android is trying to promote. In doing so, it broke some of the functions. They're trying to fix it and did part-way with 4.2.2. Maybe they'll get there eventually, but not in the near-future, I don't think.
Other manufacturers have a second BT stack that they use that is closed source that makes it more compatible with BT devices.
At least that's what I've heard and what I remember. Maybe I'm completely wrong, but thought I'd like to spread the info. It's not the fault of the devs, it's Google.

ELM327 OBDII scanner bluetooth

I have this model: http://www.newegg.com/Product/Produ...la-_-Diagnostic+&+Test+Tools-_-9SIA0WP08G3580
It paired with my Nexus 7 (2012) fine, but my new Nexus struggles to pair with it, and finally says it cannot communicate with it. Did they change the bluetooth stack? Is there a OBDII scanner that does pair?
Thanks.
Jim

I haven't had any issues with that unit on my n7, n7 2013, s3, or gnex.... What app are you using, I use torque. On a side note I just got the n7 2013 and I haven't let it update android yet so maybe its a 4.3 update thing.
Sent from my SAMSUNG SGH-I747 running CyanogenMod.

jmdearras said:
I have this model: http://www.newegg.com/Product/Produ...la-_-Diagnostic+&+Test+Tools-_-9SIA0WP08G3580
It paired with my Nexus 7 (2012) fine, but my new Nexus struggles to pair with it, and finally says it cannot communicate with it. Did they change the bluetooth stack? Is there a OBDII scanner that does pair?
Thanks.
Jim
Click to expand...
Click to collapse
i have the same scanner and paired it to my n7 fhd yesterday. code 1234 for pairing, i was using 0000 a few times and it didnt work.

bjohnston115 said:
i have the same scanner and paired it to my n7 fhd yesterday. code 1234 for pairing, i was using 0000 a few times and it didnt work.
Click to expand...
Click to collapse
the code for mine is 6789, strange, I'll try again on the way home

Maybe it has to do with the Bluetooth Smart implementation (?). Just a shot in the dark - I need to study up on the topic.

My nexus 7 actually pulled down two updates and the reader no longer works. It has to be the smart/low power Bluetooth, or maybe a compatibility issue with Bluetooth 4.0. After all these are cheap Chinese knockoffs. I'll just use my old galaxy tab 2 7 to leave in the car. They are cheap enough now I may just install it in the car for good. I was flirting with the idea of replacing my old double din head unit with it and run the speakers off my amp anyway...but I digress....
Sent from my Nexus 7 FHD using Tapatalk 2

[Q] problem with nexus 4 bluetooth

Since i upgraded to Android 4.3 from 4.2.2 my ipega bluetooth controller has a big input lag. Its not usable anymore. Ipega work great with my NVIDIA shield and Samsung tab2. No input lag at All. Should i downgrade to 4.2.2. My nexus 4 is not rooted. Thanks for help.

renejr902 said:
Since i upgraded to Android 4.3 from 4.2.2 my ipega bluetooth controller has a big input lag. Its not usable anymore. Ipega work great with my NVIDIA shield and Samsung tab2. No input lag at All. Should i downgrade to 4.2.2. My nexus 4 is not rooted. Thanks for help.
Click to expand...
Click to collapse
It's a problem with your ipega bluetooth and 4.3 you can try a full reset and test again. There have been a lot of reports regarding the bluetooth and the wifi not working together, but I never had this issue. I use a LG bluetooth (the one I use for my PS3) and have no lag. My Jambox also works well. I have used the jambox via bluetooth while web browsing using wifi and had no problems also.

zcucurullo said:
It's a problem with your ipega bluetooth and 4.3 you can try a full reset and test again. There have been a lot of reports regarding the bluetooth and the wifi not working together, but I never had this issue. I use a LG bluetooth (the one I use for my PS3) and have no lag. My Jambox also works well. I have used the jambox via bluetooth while web browsing using wifi and had no problems also.
Click to expand...
Click to collapse
Finally it seem a problem with nes.emu only. Even erasing data and cache and reinstalling dont help. I use retroarch instead no lag at all

moto x 4.4.4 bluetooth - not fixed

For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).

I am guessing that it isn't built on the 444 kernel, so, don't get too discouraged yet
Sent from my Nexus 7 using Tapatalk

ghstudio said:
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
Click to expand...
Click to collapse
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.

jaykresge said:
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
Click to expand...
Click to collapse
It is 4.4.4 kernel. I think I've found the issue and it's unique to "techies". I have a pebble smart watch which uses google...the connection to the car system (2014 MB) uses bluetooth. If I don't wear my watch, the connection to the car works...no loops/etc. When I wear the watch in the car, the car/phone link goes all screwy. I suspect that one of the bluetooth stacks doesn't like to share....and I'd bet it's the moto-x stack which can either use the bluetooth or the car link, but not manage both together, even though everything is paired correctly. I haven't checked to see if pebble and the MB use the same protocols...it may be that they both share txt even though I only need phone on the car link.
I'll post more when I get further into this....I just stumbled on the cause today when I didn't wear the watch and repaired the phone with the 4.4.4 kernel.

Next time, get a Cadillac.
FORD -Fix Or Repair Daily

abuttino said:
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
Click to expand...
Click to collapse
I've heard them all, but we've had precisely zero issues with the Fusion, and one with the Edge that was fixed free of charge due to silent recall.
My only issue with Sync is that my Fusion has the Gen 1 version, and the most recent software update removed the key reason I chose this car over the then comparable Sonata. Without that feature, I would have gone with the Sonata.