Skip to content
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

Open
MuratUrsavas opened this issue Apr 7, 2022 · 5 comments
Open

Device doesn't show up again after a rescan #186

MuratUrsavas opened this issue Apr 7, 2022 · 5 comments

Comments

@MuratUrsavas
Copy link
Contributor

MuratUrsavas commented Apr 7, 2022

Reproduction Sequence

  1. Enter into an existing Hotspot in Helium Mobile App
  2. Tap on settings icon (gear)
  3. Select Pair
  4. A RockPi hotspot should show up. Select via tapping on it.
  5. Pairing service menu should show up
  6. Tap on rescan
  7. Device should show up again, but it doesn't

Acceptance Criteria

  • Device has to show up in the last step
  • Device can be selected and service menu has to be available for it
@pritamghanghas
Copy link
Contributor

pritamghanghas commented Apr 18, 2022

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.

pariing_screen_helium

@MuratUrsavas
Copy link
Contributor Author

MuratUrsavas commented Apr 18, 2022

@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.

@pritamghanghas
Copy link
Contributor

Button press will allow him to make it discoverable again.

@MuratUrsavas
Copy link
Contributor Author

Nope, it's not right now. You need to wait for the timeout.

@marvinmarnold
Copy link
Contributor

@MuratUrsavas is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants