Why playback history becomes fragmented
Audible knows about Audible. Spotify knows about Spotify. A podcast app knows about its own episodes. The separation makes sense, but it becomes awkward when you move between services or want to answer a simple question such as "what was playing at midnight?"
How Android-wide monitoring works
Many Android media apps publish title, playback state, duration, and position through a media notification. With permission, SleepTrack observes that system metadata and stores useful positions locally. It does not record the audio stream.
Support depends on what each player exposes. A well-behaved media session gives reliable positions. An app that hides its notification, omits titles, or reports stale positions may produce incomplete history.
What the history can contain
- Title and source app
- Playback start, pause, resume, and stop timing
- Positions for supported long-form media
- Automatic bookmarks and user-created Sleep Marks
- Tags, notes, and local analytics inside SleepTrack
What it cannot do
Cross-app history does not bypass DRM, open private media databases, or guarantee that another app will resume at a deep link. "Resume in app" depends on the controls and metadata the source app makes available.
Privacy boundary: listening titles and positions are stored on the phone. Optional usage analytics do not include audio or sleep-stage details and remain off until enabled.
Set up automatic bookmarks
- Install SleepTrack Audio from Google Play.
- Read the notification-access explanation and enable the permission.
- Play something in your normal audio app for several minutes.
- Open Bookmarks in SleepTrack and confirm that the title and position appeared.
- Exclude apps you do not want to monitor in settings.
Add sleep matching later
Automatic bookmarks work without a wearable. If you later connect sleep data through Health Connect, SleepTrack can place the playback window beside sleep onset and any stages the source provides.