Status Update
Comments
ad...@google.com <ad...@google.com> #2
sc...@gmail.com <sc...@gmail.com> #3
ad...@google.com <ad...@google.com> #4
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
dk...@gmail.com <dk...@gmail.com> #5
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Locked up 3 times already today 5/3/2023.
Won't come out of it. I have to do a soft reset EACH time to get it to work.
Debugging information
Google Play services
com.google.android.gms
Version 231516044 (23.15.16 (190400-527344967))
System App (Updated)
Android System WebView
com.google.android.webview
Version 561513534 (112.0.5615.135)
System App (Updated)
Network operator: AT&T
SIM operator: AT&T
Filed by Android Beta Feedback. Version (Updated): 2.33-betterbug.external_20230301_RC01 (DOGFOOD)
To learn more about our feedback process, please visit
jo...@gmail.com <jo...@gmail.com> #6
The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(
si...@gmail.com <si...@gmail.com> #7
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Phone auto restart and freeze or hang to much
Debugging information
Google Play services
com.google.android.gms
Version 231516044 (23.15.16 (190400-527344967))
System App (Updated)
Android System WebView
com.google.android.webview
Version 573501443 (114.0.5735.14)
System App (Updated)
Network operator: AirTel
SIM operator: airtel
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visit
br...@gmail.com <br...@gmail.com> #8
sa...@gmail.com <sa...@gmail.com> #9
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Phone freezes. You have to get out of what you're doing and start over.
Debugging information
Google Play services
com.google.android.gms
Version 231613044 (23.16.13 (190400-527363516))
System App (Updated)
Android System WebView
com.google.android.webview
Version 561513634 (112.0.5615.136)
System App (Updated)
Network operator: AT&T
SIM operator: AT&T
Filed by Android Beta Feedback. Version (Bundled): 2.25-betterbug.external_20220328_RC02
To learn more about our feedback process, please visit
ke...@gmail.com <ke...@gmail.com> #10
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Freezes frequently. System UI quits responding.
Debugging information
Google Play services
com.google.android.gms
Version 231613044 (23.16.13 (190400-527363516))
System App (Updated)
Android System WebView
com.google.android.webview
Version 561513633 (112.0.5615.136)
System App (Updated)
Network operator: Verizon
SIM operator: Verizon
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visit
ap...@gmail.com <ap...@gmail.com> #11
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
This is when it froze while I was using it
Debugging information
Google Play services
com.google.android.gms
Version 231613044 (23.16.13 (190400-527363516))
System App (Updated)
Android System WebView
com.google.android.webview
Version 561513634 (112.0.5615.136)
System App (Updated)
Network operator: AT&T
SIM operator: AT&T
Filed by Android Beta Feedback. Version (Updated): 2.34-betterbug.external_20230413_RC05 (DOGFOOD)
To learn more about our feedback process, please visit
ko...@gmail.com <ko...@gmail.com> #12
ni...@gmail.com <ni...@gmail.com> #13
mb...@gmail.com <mb...@gmail.com> #14
sa...@gmail.com <sa...@gmail.com> #15
ba...@gmail.com <ba...@gmail.com> #16
em...@gmail.com <em...@gmail.com> #17
ko...@gmail.com <ko...@gmail.com> #18
js...@gmail.com <js...@gmail.com> #19
ni...@gmail.com <ni...@gmail.com> #20
sa...@gmail.com <sa...@gmail.com> #21
Please do that.
jo...@gmail.com <jo...@gmail.com> #22
um...@gmail.com <um...@gmail.com> #23
mb...@gmail.com <mb...@gmail.com> #24
ko...@gmail.com <ko...@gmail.com> #25
um...@gmail.com <um...@gmail.com> #26
um...@gmail.com <um...@gmail.com> #27
ke...@gmail.com <ke...@gmail.com> #28
na...@gmail.com <na...@gmail.com> #29
sa...@gmail.com <sa...@gmail.com> #30
Also I formatted my phone again yesterday, and controller support worked on my one controller for about a day. Today though, even though I've maintained the same pairing on both controller and phone, it doesn't work today. The only thing that changed on my phone is that I paired a set of wireless bluetooth headphones. So maybe you can't pair any devices after the one controller, or it'll break?
sa...@gmail.com <sa...@gmail.com> #31
Why would Bluetooth controllers work on those phones, when they don't on ours?
um...@gmail.com <um...@gmail.com> #32
If it's fixed on the 4a 5G and 5 it will be because they got a patch to fix it. Also if thats the case we would probably get it first. Otherwise they will be broken too.
sa...@gmail.com <sa...@gmail.com> #33
I'm not kidding at all when I say this is going to seriously influence which phone I get next.
um...@gmail.com <um...@gmail.com> #34
fl...@gmail.com <fl...@gmail.com> #37
ap...@gmail.com <ap...@gmail.com> #38
ap...@gmail.com <ap...@gmail.com> #39
um...@gmail.com <um...@gmail.com> #40
um...@gmail.com <um...@gmail.com> #41
um...@gmail.com <um...@gmail.com> #43
sc...@gmail.com <sc...@gmail.com> #44
um...@gmail.com <um...@gmail.com> #45
ir...@gmail.com <ir...@gmail.com> #46
si...@gmail.com <si...@gmail.com> #47
controller issue. Is it then on these 3rd party developers to come up with
a fix or is there a system level fix that the Android team will need to
implement?
On Wed, Oct 7, 2020, 9:09 PM <buganizer-system@google.com> wrote:
ta...@gmail.com <ta...@gmail.com> #48
1. (Super Status Bar - Gestures, Notifications & more)
2.(Volume Styles - Customize your Volume Panel Slider)
Solved this issue on my pixel 4 android 11.
ap...@gmail.com <ap...@gmail.com> #49
th...@gmail.com <th...@gmail.com> #50
sa...@gmail.com <sa...@gmail.com> #51
(It's Accountable2You, might as well get it out, not mentioning it by name isn't helpful for troubleshooting.)
LastPass app's autofill service doesn't seem to affect it, but Accountable's does.
Which, I had that same accessibility service on 24/7 on the same phone with the same controllers on Android 10 and it never stopped it before, so I wonder if it's on Android team to fix this new issue, or if they changed something about accessibility and sent notices to app developers, and it's on them to update their app, I have no idea. But being able to switch that service off and have it work is a huge deal for me, as it basically fixes my problem!
On one of the threads on the r/Stadia subreddit, a Google rep actually said that they are planning a fix for late October, so this may not be an issue for much longer, fingers very crossed.
um...@gmail.com <um...@gmail.com> #52
ko...@gmail.com <ko...@gmail.com> #53
br...@gmail.com <br...@gmail.com> #54
lu...@gmail.com <lu...@gmail.com> #55
xa...@gmail.com <xa...@gmail.com> #56
da...@gmail.com <da...@gmail.com> #57
um...@gmail.com <um...@gmail.com> #58
js...@gmail.com <js...@gmail.com> #59
mu...@gmail.com <mu...@gmail.com> #60
ri...@gmail.com <ri...@gmail.com> #61
I had to disable button mapper.
If i enable button mapper, dead cells cannot register any screen touch and wired/bluetooth joystick doesn't work properly.
If i disable button mapper in accessibility, dead cells register touch events and wired ps3 controller works as expected.
This only occurs on android 11 (beta and final), it did not occurred on 10.
um...@gmail.com <um...@gmail.com> #62
ap...@gmail.com <ap...@gmail.com> #63
um...@gmail.com <um...@gmail.com> #64
tr...@gmail.com <tr...@gmail.com> #65
mi...@gmail.com <mi...@gmail.com> #66
be...@gmail.com <be...@gmail.com> #67
Using Xbox controller but the analog sticks don't work when connected via Bluetooth
be...@gmail.com <be...@gmail.com> #68
Using Xbox controller but the analog sticks don't work when connected via Bluetooth
an...@gmail.com <an...@gmail.com> #69
ch...@gmail.com <ch...@gmail.com> #70
Sort it the fuck out Google, its been an issue since the launch of the update.
Quicker the better, get it done.
sc...@gmail.com <sc...@gmail.com> #71
be...@gmail.com <be...@gmail.com> #72
be...@gmail.com <be...@gmail.com> #73
ed...@hypafamily.com <ed...@hypafamily.com> #74
sn...@gmail.com <sn...@gmail.com> #75
kh...@gmail.com <kh...@gmail.com> #76
Did anyone was able to fix it?
jn...@gmail.com <jn...@gmail.com> #77
si...@gmail.com <si...@gmail.com> #78
is connected over bluetooth. Said profile uses the Secure Settings app to
read which Accessibility apps are currently enabled, stores it as a global
variable, and then disables all Accessibility apps. When the gamepad is
disconnected a second task is triggered that re-enables the apps based on
the global variable.
On Fri, Nov 27, 2020, 1:22 PM <buganizer-system@google.com> wrote:
um...@gmail.com <um...@gmail.com> #79
ni...@gmail.com <ni...@gmail.com> #81
ch...@gmail.com <ch...@gmail.com> #82
Upgraded to a oneplus 7 pro and left it on android 10, will not be upgrading to android 11 until Google decides to fix the fuck up and sort this annoying issue out.
f....@gmail.com <f....@gmail.com> #83
cj...@gmail.com <cj...@gmail.com> #84
I'm also experiencing the same issue with Razer Kishi which is direct connected via USB. It works all over the phone and even in the menu of gaming apps, but once a game goes fullscreen the input is dead.
Really need a fix for this ASAP. I know I can turn off the accessibility services to bypass the problem but I should be able to do both just like I could before on Android 10.
cj...@gmail.com <cj...@gmail.com> #85
ph...@gmail.com <ph...@gmail.com> #86
c0...@gmail.com <c0...@gmail.com> #87
On Fri, Dec 18, 2020, 7:09 PM <buganizer-system@google.com> wrote:
ni...@gmail.com <ni...@gmail.com> #88
xa...@gmail.com <xa...@gmail.com> #89
different brand. I currently own a pixel 2 I have loved the phone for the
most part. My pixel 2 stopped recognizing my PS4 controller over 2 months
ago. None of the updates or "fixes" have worked to fix the Bluetooth
controller issue. Now Google has stopped providing updates for anything
older than Pixel 3's. Since google feels that anyone with a 2 year old
model phone doesn't deserve updates I will not be buying another google
device. I recommend everyone to do the same. Google is no longer the
company they once we're. The need for profits over quality have ruined what
thy once stood for. DONT BUY GOOGLE PHONES. THEY ARE JUST AS SHADY AS APPLE
AT THIS POINT.
On Mon, Dec 21, 2020, 5:08 PM <buganizer-system@google.com> wrote:
cj...@gmail.com <cj...@gmail.com> #90
cj...@gmail.com <cj...@gmail.com> #91
co...@danielvallerand.com <co...@danielvallerand.com> #92
c0...@gmail.com <c0...@gmail.com> #93
some games with it, but not COD mobile and that's what I play most
On Wed, Dec 23, 2020, 11:57 AM <buganizer-system@google.com> wrote:
gc...@gmail.com <gc...@gmail.com> #94
wh...@gmail.com <wh...@gmail.com> #95
Same behavior with an xbone controller, and with a ps3 dual shock controller
la...@gmail.com <la...@gmail.com> #96
All other buttons and paddles work as expected except the two L1/L2 triggers. My understanding is this issue has been seen in other controllers as well.
Testing the controllers on other platforms do not repro the issue. I have only seen this on Android platforms.
Please fix this issue ASAP!
Thank you.
c0...@gmail.com <c0...@gmail.com> #97
button also quit working as a home screen shortcut.
On Fri, Dec 25, 2020, 7:20 PM <buganizer-system@google.com> wrote:
ro...@gmail.com <ro...@gmail.com> #98
ll...@gmail.com <ll...@gmail.com> #99
b3...@gmail.com <b3...@gmail.com> #100
ki...@gmail.com <ki...@gmail.com> #101
Where it works:
* I'm the Android UI
* In the Testing App linked above
* In Minecraft Android edition
Where it doesn't work:
* Xbox Game Pass App (After you begin streaming a cloud game all thumbstick/directional buttons/triggers stop functioning)
* GeForce Now (same issue above)
* Steam Link (same issue above)
Please fix the Android gamepad support.
se...@googlemail.com <se...@googlemail.com> #102
DS4 (v2) controller worked without problems with Android 10, now it can only be used to control the launcher / home menu but isn't recognized correctly in any game or streaming app (e.g. PSPlay Unlimited Remote Play, Grid Autosport, Dolphin Emulator)
pa...@gmail.com <pa...@gmail.com> #103
please get this sorted as soon as possible. very annoying i can't sell my s9 because that's the only way i can still play until fixed.
la...@gmail.com <la...@gmail.com> #104
assignment!
I understand that there is a underlying blocking bug as well. Hopefully,
fixing the underlying bug in a timely manner will allow for the higher
priority of this nasty thing.
Just saying... Whoever (PM or Dev) that decided P3 was an acceptable
assignment for this bug (especially since if drastically affects
functionality) should maybe rethink their decision. They need to think
about how this affects their current section or future potentially larger
section of the market.
In video gaming systems like other technologies, once a customer switches
platforms is extremely difficult to get them back!
Because of this issue, if I spend the large amount of money purchasing say
an Xbox, or PS5 leaving the Android platform because of a simple controller
mapping fix, I am not coming back because I'm already vested in games and
hardware that only works for that purchased system. If the experience on
the new platform that I discovered works better than I had hoped then you
know, I'll never be back. Just not worth it!
Increase the priority and fix this please. Google must be losing huge
amounts leaving this bug active.
Worst Christmas ever! Happy holidays to all!
On Wed, Dec 30, 2020, 1:21 PM <buganizer-system@google.com> wrote:
me...@gmail.com <me...@gmail.com> #105
The sad part is that this was reported when the A11 was in the beta before being released, as several reports in the web shown. For both Google and the publisher Activision and none of them have done anything. The troubleshooting of COD mobile still refers to an issue with Android 9 and 10, although those were fixed because my controller was working just before the update.
Hoping this is fixed soon my dexterity with the controls on display is very bad.
c0...@gmail.com <c0...@gmail.com> #106
rat race with Apple and this is leaving an extremely bitter taste in my
mouth, I feel fucking betrayed
On Thu, Dec 31, 2020, 1:04 AM <buganizer-system@google.com> wrote:
ms...@gmail.com <ms...@gmail.com> #107
jo...@gmail.com <jo...@gmail.com> #108
ms...@gmail.com <ms...@gmail.com> #109
se...@googlemail.com <se...@googlemail.com> #110
I tried my v1 dualshock, just to test everything but it has the same input lag like on android 10. BUT: after disconnecting v1 and connecting v2, the v2 seems to work without problems! Hope this will help for some of you...
um...@gmail.com <um...@gmail.com> #111
la...@gmail.com <la...@gmail.com> #112
This affects functionality. A controller is considered an actual input
device for Christ sake.
Just saying, if I was the PM or test manager on the team overseeing this
issue, heads would be rolling in the halls and jobs would be on the line!
The blocker should have been fixed and this issue put to rest months ago!
WTF is going on at Google?
On Mon, Jan 4, 2021, 12:26 PM <buganizer-system@google.com> wrote:
ms...@gmail.com <ms...@gmail.com> #113
de...@gmail.com <de...@gmail.com> #114
ml...@gmail.com <ml...@gmail.com> #115
de...@googlemail.com <de...@googlemail.com> #116
5th month without a solution for this thread/problem . This is disappointing.
ms...@gmail.com <ms...@gmail.com> #117
c0...@gmail.com <c0...@gmail.com> #118
ms...@gmail.com <ms...@gmail.com> #119
va...@gmail.com <va...@gmail.com> #120
I've tried to disable all accessibility options and reboot the phone but that didn't fix the problem for me
fr...@gmail.com <fr...@gmail.com> #121
va...@gmail.com <va...@gmail.com> #122
ms...@gmail.com <ms...@gmail.com> #123
la...@gmail.com <la...@gmail.com> #124
On Tue, Jan 19, 2021, 6:12 AM <buganizer-system@google.com> wrote:
eb...@gmail.com <eb...@gmail.com> #125
Same problem.
On Tue, Jan 19, 2021, 11:16 AM <buganizer-system@google.com> wrote:
sh...@auctionmobility.com <sh...@auctionmobility.com> #126
ba...@gmail.com <ba...@gmail.com> #127
ms...@gmail.com <ms...@gmail.com> #128
ad...@gmail.com <ad...@gmail.com> #129
ms...@gmail.com <ms...@gmail.com> #130
c0...@gmail.com <c0...@gmail.com> #131
Samsung advocate. I can't believe I'm gonna do it.
On Wed, Jan 20, 2021, 7:51 PM <buganizer-system@google.com> wrote:
xa...@gmail.com <xa...@gmail.com> #132
gamepad? Seems extreme to switch over one update. I mean I have a Pixel 2
and have been told that my phone will never be updated again by Google...
That seems like more of a reason to go iphone. I still won't... Iphones are
evil plain and simple. I definitely won't buy another google branded phone.
But switching to iphone isn't happening.
On Wed, Jan 20, 2021, 9:24 PM <buganizer-system@google.com> wrote:
c0...@gmail.com <c0...@gmail.com> #133
play games on my phone, Can I know that that's why people spend that much
money on the damn phone, If they can't keep it working the way it was
supposed to when I bought it. It's been what 3 months fuck them
On Wed, Jan 20, 2021, 8:33 PM <buganizer-system@google.com> wrote:
xa...@gmail.com <xa...@gmail.com> #134
tier. Like I said this appears to be an android 11 issue. Some phones
aren't experiencing this problem. Seems to be mostly Pixel phones, and
Samsung. Neither of which I will ever get my money again. Lately I have
been looking at the OnePlus phones or maybe a dedicated gaming phone like
the ROG 3
On Wed, Jan 20, 2021, 9:44 PM <buganizer-system@google.com> wrote:
c0...@gmail.com <c0...@gmail.com> #135
On Wed, Jan 20, 2021, 8:47 PM <buganizer-system@google.com> wrote:
ba...@gmail.com <ba...@gmail.com> #136
Although maybe all these comments will finally get Google's attention...
xa...@gmail.com <xa...@gmail.com> #137
the gamepad issues like the rest of us have. That's not saying that none
have had an issue. I just haven't seen anyone report them here. That may be
because every gaming based phone I have looked at has dedicated software
built-in for managing games and controller settings.
On Wed, Jan 20, 2021, 9:49 PM <buganizer-system@google.com> wrote:
xa...@gmail.com <xa...@gmail.com> #138
pad issue resolved might as well chat about other things to pass the time.
Google has made it very clear that they do not and will not care about
gamepad issues. Hence the reason they aren't reported as a source of input
events. This thread has been ru ning since October... If that doesn't tell
ya they don't care then you aren't listening...
On Wed, Jan 20, 2021, 9:52 PM <buganizer-system@google.com> wrote:
c0...@gmail.com <c0...@gmail.com> #139
On Wed, Jan 20, 2021, 8:57 PM <buganizer-system@google.com> wrote:
ap...@gmail.com <ap...@gmail.com> #140
la...@gmail.com <la...@gmail.com> #141
-Xbox Elite 2 wired/wireless (bluetooth) controller
- I've tried using the controller both wired and wireless
- All buttons and paddles work on every console I own (Nintendo
Switch/Xbox) and Windows PC except on my Android 11 device
-When using on my Android device the L1/R1 button triggers do NOT work
On Thu, Jan 21, 2021, 12:42 PM <buganizer-system@google.com> wrote:
jc...@gmail.com <jc...@gmail.com> #142
-Android 11
All controllers stopped working post update.
-Razer Kishi: Left side is completely unresponsive. Right side still functions in apps.
-DS4: Doesn't recognize any input across any apps or on homescreen.
he...@gmail.com <he...@gmail.com> #143
You'd think they'd stop rolling out the update for more phones if there's an existing issue this big or at least make people aware of the issues before updating so we can opt out. Mobile gaming is why I got this phone in the first place. Is there any way to revert to the previous update?
em...@gmail.com <em...@gmail.com> #144
However, I've now come up against the same issue on my MiBox 3, which I'd been streaming games to using Shadow. Ever since updating to the latest software, my Steam controller works for a few seconds absolutely perfectly before it stops working completely - exactly the same as with my Pixel. There are no accessibility features on my TV which I can turn off.
This will clearly be a long-term if not indefinite bug with Android across every platform. Is there some process to escalate this from P3?
um...@gmail.com <um...@gmail.com> #145
We need action on this bug. Acknowledgement of the bug. Honestly MS, Nvidia and any other cloud streaming service should start using their legal muscles to get Google to address this.
he...@gmail.com <he...@gmail.com> #146
Go into Settings
Then Accessibility
Then Installed Services
And disable Control Center
I just tested it out in Fortnite and its registering input. Obviously it's not ideal but it's a workaround as long as you don't depend on Game Center running.
r....@gmail.com <r....@gmail.com> #147
Galaxy s20+
Ps4 controller not working in codmobile.
fu...@gmail.com <fu...@gmail.com> #148
Samsung Galaxy S20
PS4 controller not working in CODmobile and XCloud
su...@gmail.com <su...@gmail.com> #149
Sony Xperia 1ii, was fine when on Android 10. Once updated to Android 11 the PS4 Dualshock 4 controller (V1 and V2 controllers) do not work properly on COD mobile.
ko...@gmail.com <ko...@gmail.com> #150
em...@gmail.com <em...@gmail.com> #151
Whoever this is assigned to at Google isn't paying attention - I've been getting near-daily IssueTracker emails about this since October and the situation's only gotten worse.
ko...@gmail.com <ko...@gmail.com> #152
go...@gmail.com <go...@gmail.com> #153
ml...@gmail.com <ml...@gmail.com> #154
Thank you! It's working on my Pixel 4xl again for Stadia and Xbox remote play with Xbox One controller again!
po...@gmail.com <po...@gmail.com> #155
no...@gmail.com <no...@gmail.com> #156
Pressing B or Y closes the game back to the app launcher, so the controller is definitely connected and working.
so...@gmail.com <so...@gmail.com> #157
c0...@gmail.com <c0...@gmail.com> #158
fr...@gmail.com <fr...@gmail.com> #159
al...@gmail.com <al...@gmail.com> #160
hello i have Xperia 5 after upgrade android 11, no more PS4 controler for COD mobile, but with ppsspp emulator is working, why? please fix it google
ma...@gmail.com <ma...@gmail.com> #161
dualshock 4 for online gaming can you help me please.
Thank you
MajlouCZ
Dne čt 4. 2. 2021 13:23 uživatel <buganizer-system@google.com> napsal:
de...@gmail.com <de...@gmail.com> #162
I just had another person review my app (negatively at first) because they updated their Samsung Galaxy Tab S7+ to Android 11 and just turning on my app's (Keyboard/Button Mapper) accessibility service caused their physical keyboard to use the US English keyboard layout rather than the Norwegian one. The key events had a -1 device id. This happens with accessibility services from other apps as well. My app could actually fix the bug by consuming and then inputting the same key events through the app's IME service but with the correct device id.
I'm going to see if I can create an app to work around this bug. I can definitely fix key events not being inputted correctly. I can't guarantee that I can fix motion events. Whatever the solution is, sending motion events will require using [Shizuku](
Can whoever created this issue please change the title/description to say that it isn't just Bluetooth gamepads. 🙂
PLEASE INCREASE THE PRIORITY OF THIS BUG GOOGLE!!!
hw...@gmail.com <hw...@gmail.com> #163
ki...@gmail.com <ki...@gmail.com> #164
there is my story with with Samsung S10 (Exynos version) and official upgrade to Android 11.
I am using universal gamepad, that can emulate Nintendo Pro / Xbox 360 gamepad. It depends on phone device site and type of connection wired-USB or BT. On Android 10 I succesfully used wired connection. My Gamepad has identified as Xbox 360 controller. BT connection partially connected, but there was no controller in the system. So I used wired. It was OK.
After the upgrade to Android 11, I am not able to connect with wired connection to gamepad. With BT connection is it slightly better. I see new Nintendo Pro game controller in the system, but I have no reaction on any buttons. Wired connection change so that Android 11 maybe change it`s identification the connection process is not the same.
I hope that Google will seach solution, to get it work again.
va...@gmail.com <va...@gmail.com> #165
Mame4droid (0.139u1)
DraStic
Nostalgia.NES
RetroArch
In Mame4droid I had to choose "General Multi Controller" in settings for External controller mode, it didn't work in other modes
I tested other emulators that didn't work:
PPSSPP
Citra
Snes9x
M64Plus
Redream
de...@gmail.com <de...@gmail.com> #166
After some digging around I think I found the commit which initially caused the bug.
The commit was supposed to fix another bug. Happens to the best of us... 😂
I had a crack at figuring out how input events are processed in Android and so I want to share my explanation for why this is happening because its interesting. I'm not a seasoned Android developer so I could be wrong. 😄
The InputManagerService controls the flow of user inputs in java code. An InputFilter is used to filter input events so that they are sent to accessibility services. Here is where the AccessibilityInputFilter sends the input events to the accessibility service.
The filter ultimately injects the events back into the native input manager
Because the input event has been filtered, it is injected and eventually run through the code causing the bug
I tried to figure out which accessibility service features were causing the issue and accessibility services which request to filter key events or perform gestures only seem to cause the bug to happen. This agrees with the code explanation above.
My "solution" (with Shizuku) for game controllers won't work because it ultimately goes through the same input event injecting code that is causing the issue. Keyboards can be fixed though because an input method can input the key events with the correct device id without having to inject the key events.
no...@gmail.com <no...@gmail.com> #167
xg...@gmail.com <xg...@gmail.com> #168
fr...@gmail.com <fr...@gmail.com> #169
c0...@gmail.com <c0...@gmail.com> #170
everything but COD mobile on my s20
On Fri, Feb 5, 2021, 6:22 PM <buganizer-system@google.com> wrote:
jo...@gmail.com <jo...@gmail.com> #171
jo...@gmail.com <jo...@gmail.com> #172
c0...@gmail.com <c0...@gmail.com> #173
po...@gmail.com <po...@gmail.com> #174
c0...@gmail.com <c0...@gmail.com> #175
On Tue, Feb 9, 2021, 7:16 AM <buganizer-system@google.com> wrote:
jo...@gmail.com <jo...@gmail.com> #176
po...@gmail.com <po...@gmail.com> #177
po...@gmail.com <po...@gmail.com> #178
jo...@gmail.com <jo...@gmail.com> #179
po...@gmail.com <po...@gmail.com> #180
jo...@gmail.com <jo...@gmail.com> #181
jo...@gmail.com <jo...@gmail.com> #182
ma...@gmail.com <ma...@gmail.com> #183
mt...@gmail.com <mt...@gmail.com> #184
mt...@gmail.com <mt...@gmail.com> #185
ch...@gmail.com <ch...@gmail.com> #186
fr...@gmail.com <fr...@gmail.com> #187
f....@gmail.com <f....@gmail.com> #188
wo...@gmail.com <wo...@gmail.com> #189
po...@gmail.com <po...@gmail.com> #190
an...@gmail.com <an...@gmail.com> #191
bx...@gmail.com <bx...@gmail.com> #192
ki...@gmail.com <ki...@gmail.com> #193
la...@gmail.com <la...@gmail.com> #194
traction on this annoying issue???
Please escalate.
Thank you.
On Tue, Feb 16, 2021 at 2:03 PM <buganizer-system@google.com> wrote:
la...@gmail.com <la...@gmail.com> #195
Would prefer Google to spend time on more testing than new fancy icons and widgets.
This is a major fail guys, sorry.
js...@gmail.com <js...@gmail.com> #196
using bluetooth controllers!
On Fri, 19 Feb 2021, 13:52 , <buganizer-system@google.com> wrote:
mr...@gmail.com <mr...@gmail.com> #197
ma...@gmail.com <ma...@gmail.com> #198
es...@gmail.com <es...@gmail.com> #199
ki...@gmail.com <ki...@gmail.com> #200
ma...@gmail.com <ma...@gmail.com> #201
js...@gmail.com <js...@gmail.com> #202
This is a message someone just got back from in-game COD Mobile support on the controller Android 11 problems..
PLEASE CAN YOU ALL COMPLETE THE FORM USING THE BELOW LINK TO REPORT THIS
Hello There,
Thank you for contacting Activision player support. We apologies for the delayed response. I am glad to assist you with the issue.
I understand your concern regarding that you're facing an issue in connecting the controller in the game.
Currently, all players in the game are facing this issue after the game after Android 11 update.
In this case, I request you to report this issue to our official team on the below:
This is relevant for us because it helps us to improve the game and experience for all players! In the past, changes were made in other Call of Duty titles on other platforms based on player's reports.
If you have further questions, please reply to this transaction or visit our support page for additional help
je...@gmail.com <je...@gmail.com> #203
ya...@gmail.com <ya...@gmail.com> #204
la...@gmail.com <la...@gmail.com> #205
severity and priority of this bug too low...
Your best bet is to do what I did and go back to Xbox, PS4/5, or Nintendo
Switch and stop using the Google platform for gaming altogether.
They'll eventually get the message too late and finally figure out why
people are switching over to another manufacturer for gaming.
On Wed, Feb 24, 2021, 10:42 AM <buganizer-system@google.com> wrote:
xa...@gmail.com <xa...@gmail.com> #206
doesn't give 2 shits about it. It's been broken since October. They won't
fix it for Android 11. Those of use who have phones that will never see an
update to android 12 are completely screwed.
On Wed, Feb 24, 2021, 1:47 PM <buganizer-system@google.com> wrote:
sh...@gmail.com <sh...@gmail.com> #207
xa...@gmail.com <xa...@gmail.com> #208
aren't doing anything about it.
On Wed, Feb 24, 2021, 2:26 PM <buganizer-system@google.com> wrote:
ab...@gmail.com <ab...@gmail.com> #209
Got a cod mobile challenge to finish.
lu...@gmail.com <lu...@gmail.com> #210
rs...@gmail.com <rs...@gmail.com> #211
Its very easy
On Sat, 27 Feb 2021, 00:13 , <buganizer-system@google.com> wrote:
rs...@gmail.com <rs...@gmail.com> #212
They don't know that no one will ever buy Android if they took this functionality away from Android.
This is the only beauty of Android, freedom
But now they look like follow IPhone footstep.
Boycott Android 11 Worldwide to teach them the lesson.
an...@gmail.com <an...@gmail.com> #213
xa...@gmail.com <xa...@gmail.com> #214
c0...@gmail.com <c0...@gmail.com> #215
On Fri, Feb 26, 2021, 5:19 PM <buganizer-system@google.com> wrote:
rs...@gmail.com <rs...@gmail.com> #216
ke...@gmail.com <ke...@gmail.com> #217
am...@gmail.com <am...@gmail.com> #218
The ONLY THING I've found that aloud me to have on ny phone using a gamepad again was neither a fix nor a workaround, instead i bought a dualsense controller, its worked for every game I've tried from cod, to remote play even xbox game pass, although the mapping is weird for the latter.
I know it's not a fix, and it's not what any of you want to hear, but if you're like me and have a lot of down time at work and you're losing your sanity investing in a dualsense may be worth it.
st...@gmail.com <st...@gmail.com> #219
la...@gmail.com <la...@gmail.com> #220
Maybe it's time Rage Against The Machine played outside Google's offices instead of the New York Stock Exchange 🤔
va...@gmail.com <va...@gmail.com> #221
va...@gmail.com <va...@gmail.com> #222
ne...@gmail.com <ne...@gmail.com> #223
au...@gmail.com <au...@gmail.com> #224
ri...@gmail.com <ri...@gmail.com> #225
po...@gmail.com <po...@gmail.com> #226
po...@gmail.com <po...@gmail.com> #227
ya...@gmail.com <ya...@gmail.com> #228
js...@gmail.com <js...@gmail.com> #229
sp...@gmail.com <sp...@gmail.com> #230
il...@gmail.com <il...@gmail.com> #231
la...@gmail.com <la...@gmail.com> #232
I wonder what number this has to reach before Google actually DOES something and COMMUNICATES with its "valued customers".
ma...@gmail.com <ma...@gmail.com> #233
il...@gmail.com <il...@gmail.com> #234
- Accessibility options did not work (none are enabled by default, toggling ON and then OFF did not help).
- Enabling USB Debugging ON and Wireless Debugging ON made the Kishi be detected in the menu, but it stops working once an app is launched.
- Restarting the phone resets Wireless Debugging, but same issue as the previous point persists.
This is rather frustrating to say the least. I sold my Xiaomi Mi 9T because MIUI12 broke USB-connected gamepads and got the A71 specifically to use it with the Kishi (which I paid over $120 USD for, imported it) believing that Samsung devices offer the best overall compatibility and now I can't even use it. I've probably used the damn Kishi less than 15 times since I bought it due to work and family...
Oddly enough the Kishi works fine on my wife's Note 10 Plus (Snapdragon variant) running One UI 3.1 (Android 11), so this seems to affect some Samsung models but not others. Will test it later today on the Note 10 Plus again just to make sure it is working there still.
I hope this gets patched soon.
rs...@gmail.com <rs...@gmail.com> #235
As the person above said controller works fine with his wife's Note 10 (SD variant).
May be Samsung know their Exynos phone are shite and that's why may they done that
Same the case with other phones like Google pixels
May be they don't want people to buy those phone gaming because they know people give negative comments when their performance is lesser than competitors who using Snapdragon.
il...@gmail.com <il...@gmail.com> #236
I managed to get the Kishi to work by disabling the Edge panel. If you have any apps/functions that draw over other apps or on the home screen (including Accessibility overlays), you may want to disable them. I'll be testing the Kishi with my phone for the next day or so to make sure the issue does not start up again.
la...@gmail.com <la...@gmail.com> #237
OMG I am ridiculously happy!
And in the pause, I discovered SOCOM Confrontation on the PS3 is back online too 😀
no...@gmail.com <no...@gmail.com> #238
pp...@gmail.com <pp...@gmail.com> #239
la...@gmail.com <la...@gmail.com> #240
I'd already updated COD and it didn't fix it. Turning off edge afterwards did though.
[Deleted User] <[Deleted User]> #241
c0...@gmail.com <c0...@gmail.com> #242
fr...@gmail.com <fr...@gmail.com> #243
bl...@gmail.com <bl...@gmail.com> #244
ya...@gmail.com <ya...@gmail.com> #245
j....@gmail.com <j....@gmail.com> #246
ro...@gmail.com <ro...@gmail.com> #247
"This was the result of the code that
Google created to prevent apps that
use InputFilters to automatically
click on advertising programs or
unintended behavior by users.
In this case, the device ID was
returned to -1, which made this
problem. Google should have done
a thorough review of these
modifications .
Known Google issue. Google said
'this is no fix yet but a flx is planned
for S.'"
So, there you go: Google inadvertently broke it, knows it, and no fix is planned until Android S is released.
bl...@gmail.com <bl...@gmail.com> #248
ec...@gmail.com <ec...@gmail.com> #249
ec...@gmail.com <ec...@gmail.com> #250
ec...@gmail.com <ec...@gmail.com> #251
1. I force stopped, cleared memory and uninstalled the Razer Kishi App.
2. I did the hold B+Y+ Start button while plugging into phone thing. (When you do this, the whole gamepad is unresponsive)
3. I installed and opened the Razer Kishi App.
4. Upon opening the app, I was greeted with a message letting me know about the failed update and it asked me if I wanted to complete the update. Yes. Do that. Can't imagine it would make the controller any more of a paper weight.
5. After the update completed successfully, I removed the gamepad and plugged it back in. I'm now on Gamepass playing Forza.
For the sake of clarity, I'm on a Galaxy S21 US version. Android 11. Samsung OneUI 3.1.
ma...@gmail.com <ma...@gmail.com> #252
js...@gmail.com <js...@gmail.com> #253
Just retested Dualshock and IT NOW WORKS FINE WITH CORRECT BUTTON MAPPING!!
So someone fixed something on either COD Mobile or Android 11 with that patch. Check your software and app updates to the latest verison folks and recheck your controllers!
ja...@gmail.com <ja...@gmail.com> #254
tr...@gmail.com <tr...@gmail.com> #255
and direct connect via USB-C experience same bug when any accessibility
options is in use.
On Mon, Mar 22, 2021, 4:09 AM <buganizer-system@google.com> wrote:
ch...@gmail.com <ch...@gmail.com> #256
ch...@gmail.com <ch...@gmail.com> #257
al...@gmail.com <al...@gmail.com> #258
go...@gmail.com <go...@gmail.com> #259
jo...@gmail.com <jo...@gmail.com> #260
jo...@gmail.com <jo...@gmail.com> #261
ja...@gmail.com <ja...@gmail.com> #262
se...@gmail.com <se...@gmail.com> #263
ia...@gmail.com <ia...@gmail.com> #264
I can get connected but Pascal's Wager doesn't seem to know I have a controller connected wirelessly via BT.
ba...@gmail.com <ba...@gmail.com> #265
ga...@gmail.com <ga...@gmail.com> #266
ch...@gmail.com <ch...@gmail.com> #267
ac...@gmail.com <ac...@gmail.com> #268
ni...@gmail.com <ni...@gmail.com> #269
an...@gmail.com <an...@gmail.com> #270
sl...@gmail.com <sl...@gmail.com> #271
ya...@gmail.com <ya...@gmail.com> #272
li...@gmail.com <li...@gmail.com> #273
de...@gmail.com <de...@gmail.com> #274
jj...@gmail.com <jj...@gmail.com> #275
ke...@gmail.com <ke...@gmail.com> #276
sy...@gmail.com <sy...@gmail.com> #277
hr...@gmail.com <hr...@gmail.com> #278
Please address this as soon as possible.
mu...@gmail.com <mu...@gmail.com> #279
yo...@gmail.com <yo...@gmail.com> #280
sa...@gmail.com <sa...@gmail.com> #281
cr...@gmail.com <cr...@gmail.com> #282
jj...@gmail.com <jj...@gmail.com> #283
ru...@gmail.com <ru...@gmail.com> #284
Me ajudem eu gosto muito do ppsspp e não quero trocalo. Obg pela atenção !
ga...@gmail.com <ga...@gmail.com> #285
I have an Ipega controller and already shared a video on my YouTube channel showing the brand new controller, but this issue kept happening to me in the past, even with the old Xiaomi device. I'll have to write down a pinned post telling that there's nothing that can be done for now.
People told about some workarounds, but I don't trust any of them.
Right now, the controller is just getting dust since there's nothing exactly that can be done to fix this.
la...@gmail.com <la...@gmail.com> #286
controller a go again on Fortnite and my Samsung S20 Ultra phone.
Without changing any assessibility or gesture settings (I do have some
enabled on my phone) I re-paired my Xbox controller via Bluetooth by
holding down the Bluetooth icon from the top pull-down menu on my phone and
selected the Xbox controller in the menu after poking the little Xbox sync
button on the top of the Xbox controller device itself.
The phone discovered my controller and when prompted I accepted the pairing
alert that showed up on the bottom of my phone screen.
After (and this is important) I clicked the little cog wheel in the
Bluetooth menu to the right of the paired controller name, and then the
pill shaped slider that was labeled "Input device".
Once that was done my controller worked. You may have to click and unclick
the slider a couple of times but now when I restart my phone and restart
the game it still works flawlessly both controller triggers (swinging the
pixaxe, firing a weapon, paddles, etc.)
Note: A couple of things...
My Xbox controller and paddles were previously setup on my Windows PC using
the "Xbox Assessories" app from the Windows store.
When playing Fortnite I used the same profile and paddle settings as I did
when playing on my Windows PC. You may need to go into your Fortnite
settings in game and double check to make sure they are all correct.
-Make sure that your Fortnite settings have 3D set to max, graphics set
from "Epic" to "Low", and fps from "30fps" to "60fps".
-Make sure that all of your Fortnite aim and build settings, HUD, etc. are
correct.
-Make sure that your profile button on the controller (1 of 3 different
lights) is lit to your correct Windows PC profile.
I could not get the controller to work correctly connected via USB cable so
you will need to use Bluetooth only.
Also, I have my Samsung S20 Ultra connected to a 27" external ViewSonic
monitor via HDMI cable and a small UtechSmart Type-C Hub Pro (that also
charges my phone via USB-C) Model#UCN3270.
Playing Fortnite the phone gets hot so to rectify the issue and still get
between 50-60fps I placed a few folded layers of aluminum foil (6"x8")
about a mm thick under the phone when I play and the phone gets a little
warm and all is good.
Also, close out all other apps and Windows and only have Fortnite open so
your phone proc isn't over powered and cause your monitor or sound to
intermittently cut out. Once I did that and used the aluminum foil all
performance problems have gone away.
Enjoy!
On Sun, May 16, 2021, 4:52 PM <buganizer-system@google.com> wrote:
ro...@gmail.com <ro...@gmail.com> #287
I've tried:
Two Xbox One Controllers
One Xbox Series X Controller
One Xbox Elite 2 Controller
... with
Pixel 2
Pixel 3a, and
Pixel 5
tr...@gmail.com <tr...@gmail.com> #288
su...@gmail.com <su...@gmail.com> #289
lo...@gmail.com <lo...@gmail.com> #290
cj...@gmail.com <cj...@gmail.com> #291
jo...@gmail.com <jo...@gmail.com> #292
ch...@gmail.com <ch...@gmail.com> #293
ms...@gmail.com <ms...@gmail.com> #294
Same issue, can't move character or player in games with controller
ha...@gmail.com <ha...@gmail.com> #295
ol...@gmail.com <ol...@gmail.com> #296
ca...@gmail.com <ca...@gmail.com> #297
ca...@gmail.com <ca...@gmail.com> #298
gu...@gmail.com <gu...@gmail.com> #299
ar...@gmail.com <ar...@gmail.com> #300
si...@gmail.com <si...@gmail.com> #301
ch...@gmail.com <ch...@gmail.com> #302
gu...@gmail.com <gu...@gmail.com> #303
Some programs can detect Joysticks, direction pad and LT/RT (triggers):
RT triggered
Right Joystick triggered
Left Joystick triggered
My D-Pad triggered
Share button triggered Key Code 130
la...@gmail.com <la...@gmail.com> #304
Active" controller with my Fortnite settings and buttons then go into
Fortnite settings to map button functions to get it to work on my Samsung
S20 Ultra.
When pairing the controller with Bluetooth (the only way I got it to get
all triggers, buttons etc. working properly) then go into the Bluetooth
paired setting after and slide the little button slider labeled "Input
Device" to "On".
Remember to use the same controller settings as you would on the Windows PC.
On Tue, Jun 22, 2021 at 6:12 PM <buganizer-system@google.com> wrote:
al...@gmail.com <al...@gmail.com> #305
ch...@googlemail.com <ch...@googlemail.com> #306
ad...@google.com <ad...@google.com> #307
The issue has been fixed and it will be available in a future build.
um...@gmail.com <um...@gmail.com> #308
el...@gmail.com <el...@gmail.com> #309
a....@gmail.com <a....@gmail.com> #310
buttons were not recognised.
After the update this didn't change. Then I tried pairing both joycons then
connecting them separately. (joy-con R + joy-con L)
It works when both are connected. It works as a single controller.
On Thu, 22 Jul 2021, 10:26 am , <buganizer-system@google.com> wrote:
sy...@gmail.com <sy...@gmail.com> #311
ra...@gmail.com <ra...@gmail.com> #312
bl...@gmail.com <bl...@gmail.com> #313
tr...@gmail.com <tr...@gmail.com> #314
Android version 12. Many of us have to use some sort of accessibility
options which is the primary issue with controller connectivity and Android
11. Regardless of if the controller is Bluetooth or not, it loses button
events when ANY accessibility options are enabled.
On Tue, Jul 27, 2021, 3:53 AM <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #315
sy...@gmail.com <sy...@gmail.com> #316
fr...@gmail.com <fr...@gmail.com> #317
Oxygen OS 11.0.2.1.HD65AA
Still no fix. 😢
jb...@gmail.com <jb...@gmail.com> #318
in...@gmail.com <in...@gmail.com> #319
When I get the option to auto-bind keys it recognizes the controller and binds the keys correctly but when I have to manually bind keys it doesn't work. Keybindings get registrated as virtual buttons and analog sticks and D-pad keys don't work. I thought i fixed it a few times but every time the phone reboots the problem is back and previous fixes don't work anymore. Really annoying
hi...@gmail.com <hi...@gmail.com> #320
as...@gmail.com <as...@gmail.com> #321
Was using xbox series controller on redmi note 8. Miui12. 5.1
cr...@gmail.com <cr...@gmail.com> #322
du...@gmail.com <du...@gmail.com> #323
ad...@google.com <ad...@google.com> #324
mr...@gmail.com <mr...@gmail.com> #325
bt...@gmail.com <bt...@gmail.com> #326
je...@gmail.com <je...@gmail.com> #327
di...@gmail.com <di...@gmail.com> #328
c....@gmail.com <c....@gmail.com> #329
an...@gmail.com <an...@gmail.com> #330
c0...@gmail.com <c0...@gmail.com> #331
in...@gmail.com <in...@gmail.com> #332
Some issue, only works A, B, X and Y bottom, not working others. Pixel 4A Android 11 version. I checked with XBOX One S and XBOX series S controllers.
r....@gmail.com <r....@gmail.com> #333
r....@gmail.com <r....@gmail.com> #334
cr...@gmail.com <cr...@gmail.com> #335
cr...@gmail.com <cr...@gmail.com> #337
j1...@gmail.com <j1...@gmail.com> #338
ke...@gmail.com <ke...@gmail.com> #339
soon
On Fri, Nov 5, 2021, 9:38 AM <buganizer-system@google.com> wrote:
j1...@gmail.com <j1...@gmail.com> #340
fc...@gmail.com <fc...@gmail.com> #341
I have the same trouble. When i playing with my game sir x2, the game don't know thé pad. I' m waiting a fix. Could you update on mi 9t pro Android 12?
si...@gmail.com <si...@gmail.com> #342
gr...@gmail.com <gr...@gmail.com> #343
be...@gmail.com <be...@gmail.com> #344
Version Android : 11 RKQ1 201112.002
Version MIUI : Globale 12.5.6 Stable (RKAEUXM)
va...@gmail.com <va...@gmail.com> #345
I changed my Poco F2 Pro to a Samsung Galaxy s21 FE and I have again the same issue. When using Poco F2 Pro, what fixed the problem was to disable one handed mode. There is such mode on my new Galaxy, but it is already disabled, I cannot find how to fix the problem. Anyone solved the problem on a Galaxy phone enabling / disabling accessibility functions??
Thanks in advance! It's very frustrating to see that the issue is still there on Android 12
lo...@gmail.com <lo...@gmail.com> #346
same problem here, with Samsung Galaxy s21 FE and one ui 4.0 (android 12). My dualsense controller won't work, despite Sony and Google saying that android 12 would fix the compatibility issue.
Tried enabling / disabling accessibility functions, to no avail.
Very frustrating indeed, can't understand why it's not a simple problem to solve.
va...@gmail.com <va...@gmail.com> #347
Works flawlessly with Real Racing 3, and some emulators like PPSSPP or Dolphin, but it gets tricky with Mame4droid for example. I got it working on Mame4droid, but I had to set it up as "General multi controller" mode and define keys manually (it was set up by default as gamepad number 0, but gamepads are detected starting on number 1.
I got it working on all my apps now. If someone is still having trouble, try to disable somme accessibility setting like one handed mode, it worked for me on my previous phone (Poco F2 Pro)
Happy gaming!
ko...@gmail.com <ko...@gmail.com> #348
The controller didn't work with RetroArch and Stadia, but sometimes it does after a while when I change apps via the phone's left-most software button (not sure what it is called). Not sure why, but sometimes this make things work, HOWEVER even if the gamepad works like this Gamedpad Tester still reports ID -1 and vendor 0000.
Now, I read the accessibility thing here in this thread. I opened this submenu in the settings, played with it, turned on and off the magnification system, change my text-to-speech engine from Google's to a custom one I have and back to Google's, turned off auto-rotate and back in my "physical" settings, etc.
After this (not sure which change) Gamepad Tester displays a different ID (17 maybe) and the vendor is Microsoft, everything just works.
Rebooted the phone, turned off the controller then reconnected it.
Starred Gamedpad Tester first chance I could ... ID -1 and vendor 0000 is virtual.
Gone to the accessibility settings, turned on and off the magnification thing.
It works. Gamepad Tester displays what it should, Stadia works, etc. I would expect everything else.
Hope this helps someone else. I've tried the magnification thing a while back but for me the way it was described didn't pan out.
el...@gmail.com <el...@gmail.com> #349
mv...@gmail.com <mv...@gmail.com> #350
sz...@gmail.com <sz...@gmail.com> #351
My device Poco F2 Pro (up to date firmware 18-04-2022) , Razer Kishi with updated firmware 2.7.0 , games only detected buttons Y and B but not all and that button work as Back button
ho...@gmail.com <ho...@gmail.com> #352
f....@gmail.com <f....@gmail.com> #353
You probably have not enabled USB-OTG in the settings of your Android device or your USB cable doesn't support OTG. Just a guess though this bug should be fixed on Android 12.
ho...@gmail.com <ho...@gmail.com> #354
f....@gmail.com <f....@gmail.com> #355
Not sure but on my Oppo device I followed this tutorial
Afterwards it worked
ho...@gmail.com <ho...@gmail.com> #356
an...@gmail.com <an...@gmail.com> #357
I need help as nothing I do makes my controllers work...
I've disabled every single Accessibility option/feature, but I suspect there's still something that is not on the normal Accessibility menu (like one-handed mode wasn't), so there has to be a way to fully disable everything. (or just fix the stupid bug.)
If anyone knows what else could be the issue (on TCL UI v3.0.8DH9, Android 11) please help, thank you.
al...@gmail.com <al...@gmail.com> #358
Thank you your good
th...@gmail.com <th...@gmail.com> #359
Please fix the bug. Tried Accessibility and auto rotate but neither worked.
Thank you!
ka...@gmail.com <ka...@gmail.com> #360
mu...@gmail.com <mu...@gmail.com> #361
dr...@gmail.com <dr...@gmail.com> #362
aa...@gmail.com <aa...@gmail.com> #363
DualShock 4 on OnePlus 7T Pro and on Samsung Galaxy Note 20.
The first ever connection on each device worked as expected, then later, on reconnect, it no longer identifies correctly and leads to game bugs where it doesn't function as intended, notably the right stick stops responding. Power cycling the controller ends up disabling the left stick also (as in it makes the issue worse)
Same exact bug on two different brands of phone and different SOC's.
Thanks for working to correct this error.
se...@gmail.com <se...@gmail.com> #364
is...@gmail.com <is...@gmail.com> #365
ap...@gmail.com <ap...@gmail.com> #366
te...@gmail.com <te...@gmail.com> #367
an...@gmail.com <an...@gmail.com> #368
gu...@gmail.com <gu...@gmail.com> #369
ml...@gmail.com <ml...@gmail.com> #370
Zj
fe...@gmail.com <fe...@gmail.com> #371
ts...@gmail.com <ts...@gmail.com> #372
gi...@gmail.com <gi...@gmail.com> #373
an...@gmail.com <an...@gmail.com> #374
the last 3 phones I have are unusable with bluetooth controllers :)
TCL 10 Plus seems like they won't upgrade to Android 12
waste of money getting an Android 11 phone, this is so stupid and would never happen in an iOS update, and that's the truth.
eg...@gmail.com <eg...@gmail.com> #375
ak...@gmail.com <ak...@gmail.com> #376
sa...@gmail.com <sa...@gmail.com> #377
do...@gmail.com <do...@gmail.com> #378
al...@gmail.com <al...@gmail.com> #379
al...@gmail.com <al...@gmail.com> #380
1341772152
Description
* Are you an Android developer? Y
* Which Android Developer Preview build are you using? RPB3.200720.005
* Is this a regression from Android 10 to 11? Y
* What device are you using? Pixel 3 XL
* What are the steps to reproduce the problem?
Get controller tester app
connect xbox one s or xbox elite series 2 (or possible others) bluetooth gamepad,
when pressing buttons observe the device identified is the Virtual Device instead of the gamepad itself
* Issue Category Framework
* What was the expected result? Events be tied to the correct device id.
* Can you provide the API document where this expected behavior is explained?
The following eventTypes getDeviceId() shoukld return the device, not -1 (virtual)
* What was the actual result?
Device ID (-1) was returned
* Relevant logcat output.
08-07 20:27:31.421 2570 2570 I TrustAgent: TAG: TrustAgent.Tracker. [BluetoothConnectionTracker] Bluetooth connect broadast for Xbox Wireless Controller C8:3F:26:89:42:BA [CONTEXT service_id=84 ]
08-07 20:27:31.441 1940 2663 W bt_btif : bta_hh_co_open: Found an existing device with the same handle dev_status=2, address=c8:3f:26:89:42:ba, attr_mask=0x8057, sub_class=0x40, app_id=2
08-07 20:27:31.441 1940 2663 W bt_btif : new conn_srvc id:23, app_id:2
08-07 20:27:31.442 1940 2064 W bt_btif : btif_hh_upstreams_evt: BTA_HH_OPN_EVT: handle=0, status =0
08-07 20:27:31.442 1940 2064 W bt_btif : BTA_HH_OPEN_EVT: Found device...Getting dscp info for handle ... 0
08-07 20:27:31.442 1940 2064 I bt_btif_dm: get_cod remote_cod = 0x00000508
08-07 20:27:31.442 1940 2064 I bt_btif_dm: get_cod remote_cod = 0x00000508
08-07 20:27:31.443 1940 2064 W bt_btif : btif_hh_upstreams_evt: name = Xbox Wireless Controller
08-07 20:27:31.443 1940 2064 W bt_btif : bta_hh_co_send_hid_info: fd = 235, name = [Xbox Wireless Controller], dscp_len = 334
08-07 20:27:31.443 1940 2064 W bt_btif : bta_hh_co_send_hid_info: vendor_id = 0x045e, product_id = 0x02fd, version= 0x0003,ctry_code=0x00
08-07 20:27:31.443 1940 2064 W bt_btif : bta_hh_co_send_hid_info: wrote descriptor to fd = 235, dscp_len = 334, result = 0
08-07 20:27:31.460 1500 1843 D EventHub: No input device configuration file found for device 'Xbox Wireless Controller'.
08-07 20:27:31.464 1500 1843 W EventHub: Unable to disable kernel key repeat for /dev/input/event4: Function not implemented
08-07 20:27:31.464 1500 1843 I EventHub: usingClockIoctl=true
08-07 20:27:31.464 1500 1843 I EventHub: New device: id=17, fd=144, path='/dev/input/event4', name='Xbox Wireless Controller', classes=0x80000141, configuration='', keyLayout='/system/usr/keylayout/Vendor_045e_Product_02fd.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false,
08-07 20:27:31.464 1500 1843 I InputReader: Device added: id=17, eventHubId=17, name='Xbox Wireless Controller', descriptor='f6a3e356fefcb08f9fa109c1a16b11ae1420aa25',sources=0x01000511
* Link to captured Android bug report (shared privately in Drive.)
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)