Your library
Profiles & Device Sync
Separate libraries and pair trusted devices without a cloud account.
Local profiles and Device Sync solve different problems. A profile separates parts of a library on one device; synchronization exchanges supported records between trusted WizeStream devices. Neither requires a WizeStream cloud account.
Create a useful profile structure
Create profiles for the contexts you actually need, such as Personal, Work or Study, and switch from the navigation drawer. Profile-owned subscriptions, playlists, feed groups, history and playback positions remain distinct.
Do not assume every setting is profile-specific. Some controls, learning notes and selected synchronization categories are app-wide. Review the individual setting and the sync category list before relying on separation for a particular record type.
Pair two devices
- Put both devices on the same reachable Wi-Fi, Ethernet or local hotspot network.
- Open Settings → Device synchronization on both devices.
- Choose Show pairing code on one and keep that screen visible.
- Choose Scan pairing code on the other and scan the QR code.
- Wait for confirmation, then select Sync now for an immediate exchange.
The QR code expires after five minutes and is single-use. Successful pairing establishes trust between device identities, so ordinary later synchronization does not require rescanning.
Select what to synchronize
| Category | Behavior |
|---|---|
| Profile-owned libraries | Subscriptions, groups, playlists, history and progress preserve supported profile identities. |
| Search history | Excluded unless enabled on both devices. |
| Selected settings | Only explicitly supported or allowlisted settings are exchanged. |
| Content filters | Supported blocking and filtering choices can be exchanged. |
| Learning records | Notes and supported optional difficulty ratings have their own controls. |
| Completed downloads | Metadata is synchronized; media-file contents are not. |
AiSList synchronization transfers your selected behavior, not a shared copy of its upstream data. Each device downloads its own cache when that feature is enabled.
Background behavior
After pairing, automatic synchronization can attempt an exchange roughly hourly over Wi-Fi or Ethernet when battery and reachability conditions permit. An optional charging condition can further constrain scheduled work.
While automatic synchronization is enabled and a trusted device remains paired, a foreground listener can show a low-priority Device synchronization notification. A temporarily offline peer remains paired; use Sync now when both devices are available.
Merging and deleting profiles
Synchronization merges supported records. It is not a one-way replacement or a full backup. Stable profile identifiers help prevent similarly named profiles from silently merging into each other.
Deleting a non-default profile is a local action. It does not remotely delete every record already synchronized to another device. A local tombstone prevents that same profile identity from silently reappearing on the deleting device.
Kids Mode and Incognito
Kids Mode uses a local parent PIN to protect settings and profile changes and restrict selected YouTube actions. It does not inspect every video or provide an automatic guarantee that content is suitable for children.
Incognito pauses supported activity recording. It does not make network requests anonymous or hide your IP address from media services, proxies or network providers. See privacy and networking.
Disconnect and recover safely
Use Clear trusted devices to remove pairings. Devices must pair again before exchanging data. Maintain an independent portable backup through Settings → Backup and restore; a synchronized deletion or unwanted merge can propagate to peers, so sync is not your recovery history.
If pairing fails, check local-network reachability, guest-network isolation, camera permission, expired QR codes and Android battery restrictions. Do not expose the synchronization listener to the public internet as a workaround.
Project references
Reviewed against the documented development snapshot. Documentation links follow the current repository paths; code links use the reviewed snapshot. Check the release notes for installed-build availability.