Have a firetv rooted running latest 51.1.1.0 FW, managed to get two PS4 dualshock 4s paired via bluetooth, put the fixed up kl file in /sys/usr/keyboard (or whatever path it is) and 1 controller seems to be fine, but when I pair 2 controllers, the general firetv menus act up when using either control - sometimes the input doesn't register, and sometimes the dpad registers 6+ clicks. After awhile still, the input seems to just freeze up spontaneously or the firetv becomes non-responsive, not sure which. This affects all inputs including the remote. Afaik, one controller (and remote) paired doesn't seem to exhibit the problematic behavior.
Not sure if it's because of the updated firmware as I've seen others mention input lag, but I don't think it goes away - it seems to get worse. Strange still is that if i boot up retroarch immediately and pair both controllers then in-game action seems to be fine (all input seems to register) except there is a pretty bad lag - maybe up to 500-750ms?
Any ideas on what could be causing this? Not sure how far I should try to troubleshoot without screwing up the firetv by installing settings.apk from titanium backup to try to see if there's anything in there that might help. I assume that since the DS4s are basically seen as a firetv controller, that this issue should also affect them as well? I don't have any firetv controllers to try. In the end, it would be great to get 4 of these puppies paired but at the issue rate I'm seeing, I don't think dropping another $120 would be wise until this is identified.
crook80 said:
Have a firetv rooted running latest 51.1.1.0 FW, managed to get two PS4 dualshock 4s paired via bluetooth, put the fixed up kl file in /sys/usr/keyboard (or whatever path it is) and 1 controller seems to be fine, but when I pair 2 controllers, the general firetv menus act up when using either control - sometimes the input doesn't register, and sometimes the dpad registers 6+ clicks. After awhile still, the input seems to just freeze up spontaneously or the firetv becomes non-responsive, not sure which. This affects all inputs including the remote. Afaik, one controller (and remote) paired doesn't seem to exhibit the problematic behavior.
Not sure if it's because of the updated firmware as I've seen others mention input lag, but I don't think it goes away - it seems to get worse. Strange still is that if i boot up retroarch immediately and pair both controllers then in-game action seems to be fine (all input seems to register) except there is a pretty bad lag - maybe up to 500-750ms?
Any ideas on what could be causing this? Not sure how far I should try to troubleshoot without screwing up the firetv by installing settings.apk from titanium backup to try to see if there's anything in there that might help. I assume that since the DS4s are basically seen as a firetv controller, that this issue should also affect them as well? I don't have any firetv controllers to try. In the end, it would be great to get 4 of these puppies paired but at the issue rate I'm seeing, I don't think dropping another $120 would be wise until this is identified.
Click to expand...
Click to collapse
I've been experiencing the unresponsive issue as well and have been trying to pin point the issue myself. Im able to pair 2 controllers no problem and the issue of slow down normally happens when i exit from an emulator or game app.
When the slowdown does occur I just turn the DS4 controllers off and after about 10 seconds all is fine again.
Related
Hi, I've got a V500 which I installed infecteds cm11 build, I've since bought an OTG cable and tried to plug in my 360 controller, but I'm having some issues, I downloaded a gamepad testing app and it seems like the button presses are registering, but it's not registering the releases. Is anyone else having this issue or could it just be my cable/controller/tablet?
I just tried with a brand new wireless 360 controller with the adapter and with that controller only the right bumper sticks. This seems like a really strange issue. Is there anyway I can find out what's causing it?
Hi chris
Nice to see I'm not alone with this issue as well.
As far as I've tested, whenever we press the A,B,X,Y,R1,L1 buttons they don't register the releases.
I've tried many different things, such as changing the keyboard layout for the controllers, and even making my own. Not successful though.
Well, I've managed to "bypass" this problem by configuring the gamepad keys on the games (the ones that we can configure, of course) to don't use these buttons I listed.
I changed the A,B,X,Y to the right analog stick, and the R1,L1 buttons to the R2,L2 Triggers (which are analogic).
Then the controller may work flawlessly.
Nice to know I'm not the only one to experience this issue. Weirdly I can use my 360 controller to navigate around the android interface, but struggle to get it to do anything when it comes to using it in game.
has anyone managed to get this to work?
I've tried the same cable with the same pad on my nexus 5 and it works perfectly, so there is something wrong with the USB driver.
All I want to do is play ps1 games on my tablet.
I've been working on a game for the fire tv using the Phaser (Html5) Framework. I've come across a bit of a roadblock though and was wondering if anyone had any suggestions or advice to help?
Basically, The right analog stick and both of the triggers (as well as the dpad) don't show up when getting input from axis or buttons. I currently have some debug text which prints out any axis or button input being received. This checks the first 100 axis and buttons, but yet no input is measured for the right analog stick or the triggers. Unfortunately the game I'm working on requires the right analog stick to be playable.
I'm not sure whether this would be an issue with Phaser or with the Fire TV itself. For example, the game is completely playable when playing on PC using a 360 gamepad, yet using a 360 gamepad on the fire tv has the same problems I mentioned.
I have tried building the project with both cocoonjs and crosswalk, but the problem is consistent across both.
If anyone has any advice or suggestions, they are much appreciated!
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.
I know this is the m8 forum but there isnt one for the m8s.
So the issue is, my ps4 controller connects fine, but the button layout is whack and pressing the right trigger for example also moves the analogue stick according to the phone, this makes playing games with it (using services like moonlight) impossible since I cannot remap the buttons properly or even use the triggers. My wired xbox controller wont work either, the ring keeps flashing and no input is sent to the phone.
Im rooted so if anyone has fixes for either of these issues (preferably the xbox controller one) it would be greatly appreciated
I've had a problem, whenever I connect a wireless controller to my s22, it eats inputs when I press the same button over and over. For example, if I mash the A button, only some of the inputs register and if I mash it as fast as I can, it doesn't register at all making games where I have to press the same button in succession almost unplayable. There also tends to be input lag.
I've tried with to Xbox controllers and an 8bitdo SN30 Pro+ and it happened to all three.
Is there a way to fix this????
I just got a samsung s22 ultra and haven't attempted to connect a gaming controller to it yet, but was curious about the issue you are having. Since I have thought about getting a half keyboard and mouse to hook up to it and play games as well..
A bit of digging and looking and I found this article that explains what issue you might be having and a possible fix for it too.
[Update: Fixed in Android 12] Many Android 11 users are having trouble getting games to recognize their controllers
Some smartphones running Android 11 are unable to connect to gaming controllers due to a bug. This issue has been fixed in Android 12.
www.xda-developers.com