-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Device doesn't show up again after a rescan #186
Comments
it is a little confusing. 4 to 7 is expected AFAIK. If you have connected to the hotspot. "scan again" will not show the hotspot again because last connection has stopped discovery mode in bluez. Pressing the button is the only way to get it back. If it is desired we will have to modify application logic to keep triggering discoverable till a min 5 mins have passed. |
@pritamghanghas I don't think this is what's desired. Because a user can enter into WiFi Network settings accidentally and would like to go back and enter into Diagnostics. Since Helium App is disconnecting with the Android back button it's not possible right away. Either a reboot or a discovery timeout waiting are required to regain access to the device over BT. Or Helium App is keeping the connection (hence device is not discoverable anymore) but don't give a chance to use that existing connection again. This means it is an upstream issue. Then we should figure out a workaround. |
Button press will allow him to make it discoverable again. |
Nope, it's not right now. You need to wait for the timeout. |
@MuratUrsavas is this still an issue? |
Reproduction Sequence
Acceptance Criteria
The text was updated successfully, but these errors were encountered: