You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 27, 2024. It is now read-only.
@barbeau Thank you for opening this. About volume tracking, I found a couple of solutions on StackOverflow to be really useful for monitoring current volume especially when the user changes the volume while using the app. Feel free to let me know your thoughts on implementing something similar to this if not, the same. https://stackoverflow.com/a/18273761 (getting current volume) https://stackoverflow.com/a/15292255 (listening to the volume button and monitor when the user adjusts volume)
The current implementation tracks the volume and the device on which the user is currently listening to the song. The app can actively detect the device type even when the user continuously chooses to switch the output device.
However, per discussion today, we think the current implementation for tracking Bluetooth devices may not be the best way due to the variety of these devices. For example, measuring loudness could be a bit unreasonable when Android generalizes and classifies a Bluetooth speaker and a Bluetooth headphone as TYPE_BLUETOOTH_A2DP as the loudness measure could potentially be the same for both the devices for the same volume.
barbeau
changed the title
Add volume, headphones, chromecast, and bluetooth presence to data tracking
Add Chromecast to data tracking
Jan 8, 2021
Is your feature request related to a problem? Please describe.
We should track for each event values related to how the user experiences the music.
Describe the solution you'd like
Per today's discussion, we should also be recording for each event:
The text was updated successfully, but these errors were encountered: