-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using WiFi Analyzer as secondary users #112
Comments
Non-primary user testing:
To help us to investigate the issue, please provide the following:
|
Application about screen? What's it? Then I haven't a lot of screenshot to provide. Wifi analyzer shows just nothing (like wifi wasn't even enabled).
I'd be curious to know why this odd additional requirement, anyway yes I'm not using the same google account. |
Application has "About" screen (Application version, OS version, etc). |
Ok so.. this is the screen you asked for. WiFiAnalyzer can work on secondary users accounts IF it is also installed in the primary account. This is probably why you couldn't reproduce. |
Great that you found the "wizardary". |
WiFiAnalyzer must be installed in the primary account, in order for it to work on the secondary accounts. |
Mhh.. okay. |
@mirh Would you like to help us with this feature? It would be great to add another contributor to this project. |
I feel already enough a contributor to have pinpointed the thing 😅 Anyway.. I'd first be curious about whatever's going on to start with. I mean, putting aside that I wonder if you can detect you are falling under that case (for example, I assume you can't know if gps is enabled or not from your side, if you have to put there its 6+ warning irregardless of anything), I'm not sure if this is expected behavior by google in the first place. |
Follows #23 (comment)
I know non-primary users have usually some restrictions, namely developer options, system updates, RadioInfo tests, sim status and imei (more?)
...
Though, I just checked in the Wi-Fi status testing menu, and that's correctly reporting RSSI.
So, it seems a bug on your side.
The text was updated successfully, but these errors were encountered: