Status Update
No update yet.
Comments
rp...@google.com
I am not sure I understand the use case. how can the benchmark be code to real world scenario when it's not possible to do right now ? which scenario is it ?
In any case, since this would be for benchmarking, this would clearly not be available through the public DSL. We should find a semi-private way of doing this (maybe the private variant API object could offer that functionality for instance or a property).
go...@gmail.com
We want benchmarks to measure code after Progaurd / R8, but it's not possible to turn that on for androidTests in library modules at the moment (to my knowledge?)
Benchmarks are also a public facing thing, but we have a plugin to help configure gradle builds for our users, so if support for this ends up in a private API, we could try to keep those usages localized to our code perhaps.
go...@gmail.com
Any update on the status of this request and when it can be supported?
Thanks,
Amanda
rp...@google.com
this is not part of our OKR at this point so we are not talking soon. at first glance, we would need to simulate usage patterns to minify against and such, this seems substantial amount of work. there are not a lot of library module that have android tests, most only rely on unit-tests.
how important is this ? we are out of PM right now but I suspect the next step will be to negotiate with J. Eason and xav@ to scale a priority level.
Description
Version used: Android 14
Devices/Android versions reproduced on: Google Pixel 6
Hello,
We are working on a full hands-free access control use case using UWB. We are now targetting physical access control, but the same issue would occur if we were targetting car access control through CCC (Car Connectivity Consortium), which is promoting UWB for full hands-free car unlock use case. We would like to start UWB Ranging Session while the users keeps the phone into his/her pocket, no need to unlock the phone at all.
Due to UWB access restrictions (
Is there any intention to remove this usage restriction at some point with a new UWB Core library release? How does this limitatio fit within the CCC full hands-free use case?
Regards.