Assigned
Status Update
Comments
ve...@google.com <ve...@google.com>
ra...@gmail.com <ra...@gmail.com> #2
Also confirmed issue persists on 4.4.
ve...@google.com <ve...@google.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.
ad...@google.com <ad...@google.com>
vi...@google.com <vi...@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.
be...@gmail.com <be...@gmail.com> #5
Please fix
be...@gmail.com <be...@gmail.com> #6
Yes, please fix it. =)
vi...@google.com <vi...@google.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.
vi...@google.com <vi...@google.com> #8
[Comment deleted]
be...@gmail.com <be...@gmail.com> #9
fix will ya? make the android better more
be...@gmail.com <be...@gmail.com> #10
Yes, count me as someone who would like to see this fixed. It apparently isn't fixed in KitKat.
vi...@google.com <vi...@google.com> #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.
ma...@gmail.com <ma...@gmail.com> #12
Please roll back previous API. This fratura is importante.
vr...@gmail.com <vr...@gmail.com> #13
Android 4.3 killed my super mario :(
mr...@gmail.com <mr...@gmail.com> #14
Please fix, pretty please
vi...@google.com <vi...@google.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
te...@gmail.com <te...@gmail.com> #16
Please fix this!! We want to play with us wii u pro controller!! C'mon Google!!
am...@gmail.com <am...@gmail.com> #17
PLEASE GOOGLE, LET US HAVE BLUETOOTH FREEEEEEEEDDDDOOOOOOOOOOOOOOOOOOM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
gu...@gmail.com <gu...@gmail.com> #18
Google, please fix this issue. many games are unplayable with said issue.
[Deleted User] <[Deleted User]> #19
Please google, can someone please fix this issue. thanks
wa...@googlemail.com <wa...@googlemail.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!
di...@gmail.com <di...@gmail.com> #21
Just want to play some Bayou Billy for nes on my Note 3 with wiimote controller please.
th...@gmail.com <th...@gmail.com> #22
[Comment deleted]
th...@gmail.com <th...@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?
ni...@regainapp.ai <ni...@regainapp.ai> #24
I, like many others, wish to enjoy computer gaming nostalgia via excellent emulators. Please fix my first world problem...
vi...@google.com <vi...@google.com>
je...@gmail.com <je...@gmail.com> #25
Please fix. This is really dissapointing and I think I'm switching to Apple.
mo...@gmail.com <mo...@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 !!
cc...@gmail.com <cc...@gmail.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.
bh...@techind.co <bh...@techind.co> #28
Please support Bluetooth L2CAP. This is important to me. It's hard to believe the famous Android lacks such a basic Bluetooth function.
gr...@gmail.com <gr...@gmail.com> #29
Still don't work...
sa...@gmail.com <sa...@gmail.com> #30
Please fix this.
Description
I did some tests with UsageStatsManager.queryUsageStats.
The bucket that are build by that method are however rather unexpected.
For INTERVAL_DAILY I would expect buckets which begin and end at e.g.
2018/10/28 00:00:00 | 2018/10/29 23:59:59
2018/10/29 00:00:00 | 2018/10/29 current time of query
However, UsageStats.firstTimeStamp and UsageStats.lastTimeStamp suggest a different behaviur.
Buckets seem to begin and at just at some "random" time during the day. That is not even the same time for every day on one device. Also, it differs from one device to the next.
The same goes for other INTERVALs.