KlakNDI
KlakNDI copied to clipboard
Finding sources fails on Android after application has been in background for a while
It seems that there's an issue with finding sources in an Android build after that build has went to the background and is reinstanted after a while (network goes to sleep? not sure).
The issue manifests in that the same set of sources as when the application went to sleep is forever returned, until a full application restart.
To reproduce, build to Quest 2 (or probably any other Android device) with a source selection UI. Turn the screen off, wait a while, turn the screen back on. Expected: sources can be found still after a device has been sleeping Actual: app needs to be restarted so current sources can be found
Let me know if you need more help in reproducing, I can probably put together a minimal sample case (or, if you have a Quest, add you to the release alpha channel to test live).
I think that's reproducible on normal Android devices. I'll try it later.
I'm interested to try it on a PICO Headset the last days of the next week. I hope it helps... to have more feedback.
This issue doesn't reproduce on my Pixel 5 with Android 12.
Help wanted: I want to know if this issue is reproducible on any other Android device.
If you have Quest 2, please try reproducing it on your device. I want to know whether it's a device-dependent problem or not.
@hybridherbst: If you have any other Android device, could you try reproducing this issue on it?
I'll try to repro on a Mi 9 phone. My best guess so far is that a difference is that when Quest goes to sleep, it actually shuts down all network activity besides system activity, and that this makes things go rogue.
One preliminary result from testing on the Mi 9 might be another small bug, hopefully related: when setting a phone to Flight Mode and querying sources again, the expectation would be that "no sources" is reported, however, the last found set of sources is kept around.
Edit: seems it doesn't repro on Mi 9 :(
Thanks for the clarification. It's useful information; Now I know the behavior of Quest 2 is very different from other Android devices. I should find a way to test it.