Assigned
Status Update
Comments
at...@google.com <at...@google.com>
at...@google.com <at...@google.com> #2
Also confirmed issue persists on 4.4.
sh...@gmail.com <sh...@gmail.com> #3
There are a lot of expensive accessories I've purchased or been gifted that quit workin with android 4.2. Android devs need to get on this. 3 broken versions and numerous minor updates and it hasn't even been triaged yet. Completely unprofessional.
at...@google.com <at...@google.com> #4
We are loyal to Android as and they treat us like this.. I have a google device and yet it still is not fixed.
sh...@gmail.com <sh...@gmail.com> #5
Please fix
at...@google.com <at...@google.com>
vi...@google.com <vi...@google.com>
sh...@gmail.com <sh...@gmail.com> #6
Yes, please fix it. =)
pu...@gmail.com <pu...@gmail.com> #7
I abandoned iPhone to discover something better, but I'm finding a lot of my Bluetooth paired devices won't work properly on android... I hope this gets fixed soon. I don't want to have to buy an iPhone again and suffer with their long agreements and system restrictions.
le...@argent.xyz <le...@argent.xyz> #8
[Comment deleted]
ja...@planetart.com <ja...@planetart.com> #9
fix will ya? make the android better more
sh...@gmail.com <sh...@gmail.com> #10
Yes, count me as someone who would like to see this fixed. It apparently isn't fixed in KitKat.
ar...@beekeeper.io <ar...@beekeeper.io> #11
I have two nexus devices and this is a regular issue. The kid can't play games properly. Way to replace a working stack with a subpar homebrewed one.
dr...@gmail.com <dr...@gmail.com> #12
Please roll back previous API. This fratura is importante.
yu...@gmail.com <yu...@gmail.com> #13
Android 4.3 killed my super mario :(
zh...@gmail.com <zh...@gmail.com> #14
Please fix, pretty please
zh...@gmail.com <zh...@gmail.com> #15
I have a device that worked fine with Bluez and now is broken with Bluedroid. Please add support for devices requiring L2CAP connectivity. From the logs, it seems to try and run L2CAP over GATT/ATT even with devices that are not BLE.
Thanks
Thanks
sh...@gmail.com <sh...@gmail.com> #16
Please fix this!! We want to play with us wii u pro controller!! C'mon Google!!
zh...@gmail.com <zh...@gmail.com> #17
PLEASE GOOGLE, LET US HAVE BLUETOOTH FREEEEEEEEDDDDOOOOOOOOOOOOOOOOOOM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
zh...@gmail.com <zh...@gmail.com> #18
Google, please fix this issue. many games are unplayable with said issue.
sh...@gmail.com <sh...@gmail.com> #19
Please google, can someone please fix this issue. thanks
ha...@qualcomm.corp-partner.google.com <ha...@qualcomm.corp-partner.google.com> #20
Would love to see this resolved. Like a handful of others on here I just wanted to sync a bluetooth controller to my Android device to play some games. (I'm not very good at Megaman X with the touchscreen). I know it isn't a huge system issue, but maybe it could be changed anyway?
Games already look great on the Note 3, would be better with my controller.
Thanks in advance!
Games already look great on the Note 3, would be better with my controller.
Thanks in advance!
zh...@gmail.com <zh...@gmail.com> #21
Just want to play some Bayou Billy for nes on my Note 3 with wiimote controller please.
ha...@qualcomm.corp-partner.google.com <ha...@qualcomm.corp-partner.google.com> #22
Comment has been deleted.
sh...@gmail.com <sh...@gmail.com> #23
I was really upset when I went to use a feature that used to work perfectly, this is stupid, what gives Google?
sh...@gmail.com <sh...@gmail.com> #24
I, like many others, wish to enjoy computer gaming nostalgia via excellent emulators. Please fix my first world problem...
dr...@gmail.com <dr...@gmail.com> #25
Please fix. This is really dissapointing and I think I'm switching to Apple.
sm...@gmail.com <sm...@gmail.com> #26
Several Android devices and several Android versions from 4.2 to 4.4 : I cannot use m'y game contrôler I bought especially for my first Android phone under 2.2. Please fix !!
vi...@google.com <vi...@google.com> #27
Blue Tooth has been broken for nearly a year. How is that even a thing that is? This is how your lose paying customers, Google.
sh...@gmail.com <sh...@gmail.com> #28
Please support Bluetooth L2CAP. This is important to me. It's hard to believe the famous Android lacks such a basic Bluetooth function.
ar...@gmail.com <ar...@gmail.com> #30
Please fix this.
vi...@google.com <vi...@google.com>
hw...@gmail.com <hw...@gmail.com> #31
Comment has been deleted.
hw...@gmail.com <hw...@gmail.com> #32
[Comment deleted]
vi...@google.com <vi...@google.com> #33
Please fix this. I want to pair my Wiimote with my Android phone and tablet.
Description
Problem
After updating to Android14 and developing our app, we found that the debuggable app is very lag.
If setting
android:debuggable=false
, it's back to normalVerify
I write a simple demo which you can view it from the attachment. And test 3 methods:
The result like below:
Test Fibonacci sequence
Code:
Result
Test String.charAt
Code
Result
Test Double.parseDouble
Code
Result
Conclusion
From the results, we can found there have performance loss in Android 14 with debuggable. It make our debuggable app lag.
Expect
This behavior affects our development efficiency and we can hardly develop and use it.
Is this expected behavior or is it a bug?
BTW: This behavior like app is debugging, and app run slow Is it caused by some logic about adb jdwp?
Demo
Please check the HelloAndroid.zip
And you can change the
isDebuggable
value in app/build.gradle.kts (or search TODO keyword)