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

Enable tap has no effect on Enable Exposure Notifications on Alcatel 5056W, Android 6.0.1 #100

Open
Dar-Scott opened this issue Jun 29, 2020 · 4 comments

Comments

@Dar-Scott
Copy link

Dar-Scott commented Jun 29, 2020

Alcatel 5056W
Android 6.0.1
Wifi on
Bluetooth off

This is on an old phone with a cracked screen given to me for testing.

In my setting up the phone for CW, I get stuck at the Enable Exposure Notifications screen. I hear a snick when I tap Enable, but nothing happens. I clicked a few more times and waited an hour. Not even a busy indication.

See also #95.

@Dar-Scott
Copy link
Author

Workaround? Context?

@Dar-Scott
Copy link
Author

Dar-Scott commented Jun 30, 2020

The problem occurs for a another phone of the same model in much better shape but with Bluetooth on. Eventually tapped "not now" and then "see exposure summary". From there I could not get back.

Tried that on the first phone and the same thing, even though Bluetooth was off. Afterward, Bluetooth was still off.

@Dar-Scott
Copy link
Author

This seemed to make some progress, but I don't think it is working.

  1. (I upgraded Google Play Services. This is probably a red herring.)
  2. I went to Settings-->Apps-->CW Demo and tapped Force Stop.
  3. I restarted CW Demo by tapping on its icon. This got me back to the CW Demo screen I was on, but this time there was a banner at the top indicating that EN needed to be enabled.
  4. I did that and got a system notification dialog box and I dismissed that.

Maybe it is working. But, maybe not, my GAEN sniffer, which works fine for iPhone, is not receiving any packets.

I suspect something was blocking the system notification window (or whatever Android calls it) and that caused the hang at the Enable button in the beginning.

@Dar-Scott
Copy link
Author

Maybe working. Details to come

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

No branches or pull requests

1 participant