Status Update
Comments
rp...@google.com <rp...@google.com>
zi...@google.com <zi...@google.com> #2
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).
sa...@gmail.com <sa...@gmail.com> #3
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.
Description
Component used:core.uwb(Kotlin)
Version used:1.0.0-alpha05
Devices/Android versions reproduced on: Galaxy S series.
I am developing an app using Ranging between our UWB hardware and Jetpack UWB.
The mobile phone is the "Controlee" and our hardware is the "Controller".
If our hardware(Controller) stops ranging or removes the mobile phone from the controlee list during normal UWB ranging between the above two devices, On the mobile phone side "RangingResult.PeerDisconnected" is raised.
"RangingResult" are no longer received, but the process escapes the "collect" loop through a "throw exception" because it cannot escape itself from the "collect" loop.
I have a question here.
When "RangingResult.PeerDisconnected" occurs Is it to completely stop UWB Ranging internally? After "RangingResult.PeerDisconnected" occurs, is it impossible to perform Ranging again before obtaining a new "SessionScope"?
I removed the code that throws an exception when "RangingResult.PeerDisconnected" occurs on the mobile device so it stays in the "collect" loop, then I tried resurrecting the hardware's controller session, but no "RangingResult" was received.