-
Notifications
You must be signed in to change notification settings - Fork 8
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
Beta test: Haptics Playground 1.1.1 Android app #855
Comments
I've noticed that, turning on sound, the sound may be off the first time something is played. This is either after first turned on, or not having been used for awhile. For instance, the first buzz of a set may not play or buzzes may run together. The actual haptics don't seem to be impacted. |
QA spot check is done. Checked on one device (the haptics capable tablet in the office). Check was fairly quick/light. |
I've seem similar behavior on our sims on all manner of devices. I think that devices often turn off the amplifier that drives the speakers in order to save power when they are not being used, and it takes a bit of time for it to come on when sound is produced after a long idle time. If my supposition is correct here, there isn't much the code can do about it. |
Thanks for the testing QA team! I'll close this issue and move forward with the next steps. |
The Android version of the Haptics Playground app is ready for beta testing. The previous (alpha) test was completed, and a couple of the issues were addressed. I have provided @KatieWoe with a Samsung Android tablet that supports haptic vibration, so she should be able to test on that device for this round of testing.
As was noted in the previous testing issue, this testing is intended to be fairly light since this is not expected to be a widely used app for PhET. It is being published for potential use by the community of designers who are working to add multi-modal capabilities to educational apps. The bottom line is that we're not looking for perfect behavior, but rather something that can be used by motivated designers. Testing should focus on making sure that the app doesn't crash, that the primary functions appear to work correctly, and that there isn't anything that is terribly confusing about how the UI works.
Testers must be signed in with their pre-registered Google accounts, and can install the app from https://play.google.com/apps/internaltest/4701271652165855719. Please contact @jbphet if other testers need to be added.
Issues should be logged at https://github.com/phetsims/quake/issues.
Issues to verify:
Assigning to @KatieWoe and @kathy-phet for prioritization.
The text was updated successfully, but these errors were encountered: