[Q] Wireless Keyboard -> crash - Gen8, Gen9, Gen10 Accessories

Hi,
if I connect an usb dongle to drive a wireless keyboard (several tested) with my Archos 101 internet tablet and use the touchscreen it hangs after some touches and reboots after a couple of seconds.
I have the latest Firmware.
What could cause this?
Thanks.
BTW: It doesn't happen if I connect a wired keyboard.

Related

Problem with Logitech Tablet Keyboard for Android 3.0+

I am using the above keyboard with my Samsung Galaxy S3 (also connected to a monitor). The keyboard pairs and connect without a problem and seems to work fine. However, as soon as I add a Logitech Tablet Mouse, the keyboard starts to go into sleep mode very quickly (after a few seconds) as soon as I use the mouse to navigate. The keyboard wakes up after about a second when hitting a key, but it is still very annoying. I searched for similar reported problems, but I did not find any yet. Any suggestions?

How use screen keyboard when bluetooth mouse is active

I'am Evo 3D user and my Adnroid version is 4.0.3
I use my phone at TV with mhl hdmi adaptor.
I connect my bluetooth mouse and I use it far from phone and TV
When I connect mouse screen keyboard disappear.
I want to use screen keyboard with bluetooth mouse. What could I do?

[Q] USB / Bluetooth Keyboard ends up as Player 1

Hey All,
I've contacted OUYA support (and have a dialog going with them) about this, but thought I'd throw a line out here as well.
I've got a bluetooth Microsoft Entertainment Keyboard 7000 as well as a USB Logitech K400 keyboard.
Both work pretty well with the OUYA (though I don't use both simultaneously for obvious reasons).
One thing I've noticed, however, is that no matter what order I pair the OUYA controllers and keyboard (or connect the USB keyboard) in, the keyboard ends up being player 1 after a period of time.
Example:
Pair OUYA controller 1
Pair OUYA controller 2
Connect USB keyboard
After a day or so, and possibly a full power cycle of the device, the keyboard ends up being Player 1.
This doesn't pose an issue for the most part (the OUYA controllers display that they are players 2 and 3), but some games specifically rely on the device that is identified as Player 1 to actually be an OUYA controller in the game, and therefore I have to go through a whole rigamarole of unpairing all controllers / keyboards, disconnecting the USB keyboard, and doing a full shutdown of the device, then powering it back on and waiting for the pairing wizard to pop up so I can re-pair my controllers.
The real question here is, has anyone else experienced this, and if so have you found a viable workaround?
I'd prefer that the keyboard (whether USB or bluetooth) doesn't get detected as a controller period, but simply acts as an auxiliary means of input for fields where I need to type something in, move a mouse, etc.
Thanks!
pitcherj
Yes, I have exactly the same issue with a Logitech K400 as well. Very annoying, I haven't found a workaround yet.
I have an Ouya controller, a PS3 controller and the K400 in that order and after a while the K400 takes over controller position 1.
There needs to be some way of locking controller 1, or at least a way to quickly change controller positions from within the interface without needing to repair everything.
I had the exact same problem, after looking around for several days trying to find a way to get my controllers paired to slot 1&2. Installed the Blue Board app from the OUYA market.
I've been installed it on my phone, got to to to pair, and used it a couple of times. After that I noticed that my controllers properly paired to slot 1 & 2, and if I hook up my keyboard it properly goes into a different slot.
Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
Over here it is the same problem.
I use a Rapoo E2700 Keyboard with touchpad. It is connected via a seperate USB wireless-dongle.
[A little o.t. but i want to tell everybody thant the keyboard is working great! The Touchpad is super smooth and (unlike the Ouya Controller Touchpad) realy good to navigate a mouse cursor]
It would be nice if there was a menue where you could assign wich Device takes wich controller-slot. Working without a keypboard is a little annoying to me.
Same for all my keyboards, i think it might be intentional.
Everytime I plug in my keyboard dongle it causes the system to lock up and i have to restart, but if I boot with the keyboard hooked up its player 1. They need to get this fixed
Edit: It seems that removing my hub and pluging straight into the ouya works... but now I've no way to use xbox controllers...
After reading through this thread, I'm beginning to wonder if it has something to do with using keyboards meant for PC. The reason I say this is I have had my Motorola Bluetooth Keyboard made for the Xoom paired since the day i got it and it never took over any controller port, but 1 full power cycle with my Logitech USB keyboard and it took over 1st controller.
Does anyone else have a android BT keyboard they can try?
Xbox wireless dongle as well as a el'cheapo GE USB keyboard do the exact same thing... very very annoying
Sent from my Nexus 10 using Tapatalk HD
JLCollier2005 said:
After reading through this thread, I'm beginning to wonder if it has something to do with using keyboards meant for PC. The reason I say this is I have had my Motorola Bluetooth Keyboard made for the Xoom paired since the day i got it and it never took over any controller port, but 1 full power cycle with my Logitech USB keyboard and it took over 1st controller.
Does anyone else have a android BT keyboard they can try?
Click to expand...
Click to collapse
I think this is tied to USB taking priority over Bluetooth. Every USB HID I plug in ends up becoming player one.
Sent from my MB860 using xda app-developers app
---------- Post added at 01:47 AM ---------- Previous post was at 01:44 AM ----------
Sinderan said:
Everytime I plug in my keyboard dongle it causes the system to lock up and i have to restart, but if I boot with the keyboard hooked up its player 1. They need to get this fixed
Edit: It seems that removing my hub and pluging straight into the ouya works... but now I've no way to use xbox controllers...
Click to expand...
Click to collapse
Are you using a powered USB hub? My non powered USB hub does the same thing.
If a powered hub doesn't do it, it might have something to do with the power draw on that single port.
Sent from my MB860 using xda app-developers app
ja450n said:
I think this is tied to USB taking priority over Bluetooth. Every USB HID I plug in ends up becoming player one.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I think its more just because The USB connects on boot, while the bluetooth controllers and keyboards have to be turned on. Since the USB where already there they get the first spot and the rest get whats there when they connect.
ja450n said:
Are you using a powered USB hub? My non powered USB hub does the same thing.
If a powered hub doesn't do it, it might have something to do with the power draw on that single port.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Yea I think I need a powered hub. I left one at my moms house I'll probably go pick up today when I remember. (Wow I never thought that hub that came with Rock Band 1 on Xbox would ever be useful again lol)
https://support.ouya.tv/entries/247...A-controller-not-shown-as-Controller-1-or-if-
This is their solution.
Sent from my Transformer TF101 using Tapatalk 2

Problems with bluetooth controle after 51.1.5.0_515020820

Hi Everybody,
I upgraded my FireTV to the latest pre-rooted 51.1.5.0_515020820. Followed all the steps in FireTV News and used rbox's package.
The update was successful but right after update I begin to notice problems with my fire tv controller.
I takes too much time to start working, and for some reason, my Logitech wireless keyboard and mouse are not working after the update. Some times the screen saver even kicks in before the remote starts to work.
Has anybody experiencing the same kind of problems?
I'm attaching a logcat from the boot until the remote starts working.
EDIT: Just realized I had enabled USB debugging. Disabling that made at least my keyboard work again, but the mouse is not functioning. Both are connected to the same Logithech unifying dongle and both do work on a computer.
danielcbit said:
Hi Everybody,
I upgraded my FireTV to the latest pre-rooted 51.1.5.0_515020820. Followed all the steps in FireTV News and used rbox's package.
The update was successful but right after update I begin to notice problems with my fire tv controller.
I takes too much time to start working, and for some reason, my Logitech wireless keyboard and mouse are not working after the update. Some times the screen saver even kicks in before the remote starts to work.
Has anybody experiencing the same kind of problems?
I'm attaching a logcat from the boot until the remote starts working.
EDIT: Just realized I had enabled USB debugging. Disabling that made at least my keyboard work again, but the mouse is not functioning. Both are connected to the same Logithech unifying dongle and both do work on a computer.
Click to expand...
Click to collapse
Youre not the only one. I had something similar pointed out to me in another thread. Havent had time to test but logitech k400 mouse pad is having issues. Keyboard appears to work fine.
Any one else having these kinds of problems with the fire tv bluetooth control?
I also noticed that my remotes is disconnecting from FireTV randomly. Sometimes when I'm watching something, the remote does not respond. I have to wait from seconds to minutes until the remote starts to respond again.
I also have in the area my FireTv is several BLE beacons, I'm starting to think that they might have something to do with that problem.

[Q] severe Bluetooth lag

Hi,
I've been connecting my ps4 controller to my nexus via Bluetooth. I've been using fpse and epsxe emulators. The controller works fine for about 20 seconds then all of a sudden a huge delay happens. E.g if I press x there's about a 2 or 3 second delay. Is there anyway to fix this?
Android version
KitKat 5.0.2
Thanks!
i think its an issue with nexus not maintaing enough juice to the micro usb otg.
i believe its the root cause of my wireless keyboard timing out

Categories

Resources