Persistent “ghost” memories, empty calendar, and firewall message after Firmware 0.8 / App v0.4.2 (203)

General
1

I’m posting this in case others are seeing similar behavior after the most recent update. I realize this platform is still very much a work in progress, and I view early users as informal beta testers—just without the benefit of a changelog or clear documentation yet.

Since updating to Firmware 0.8, Wi-Fi v4, and Companion App v0.4.2 (203), I’ve been able to reproduce several sync-related issues that seem tied to the new delta-sync engine and Pocket Cloud backend:

  1. Deleted memories reappear after relaunch.

I deleted all memories from the main screen, emptied the trash in Settings, and cleared offline copies.

Offline storage showed 0.1 GB used / 116.5 GB total before clearing and 0.0 GB used / 116.6 GB total afterward.

After closing the app (“Close All”) and reopening, all deleted memories immediately re-download and repopulate the main screen—even though the trash and offline cache both show empty and “Check for new memories” reports none found.

  1. Calendar entries never populate.

The app has full calendar permissions in Android settings.

When I add my calendar, it confirms the account is already added but displays no events.

  1. Frequent connection warning:
    “Unable to connect to server – check your firewall settings.”

Appears intermittently during sync, even on a strong Wi-Fi connection.

When this happens, deletions and calendar syncs fail to persist.

Additional details:

Trash empties successfully but refills after app relaunch.

Offline storage numbers fluctuate slightly (≈115–116 GB range), suggesting the backend index is still re-hydrating.

Behavior repeats reliably across multiple restarts and cache clears.

The Settings → FAQ / Community / Terms links remain inactive (“dead”), which may indicate that parts of the setup and help interface are still placeholders from the current firmware cycle.

Working theory:
The app performs deletions locally, but the backend isn’t committing the corresponding “tombstone” flags. The server still treats the old recordings as active and pushes them back during the next sync. The firewall warning likely reflects failed delta-sync handshakes while the Pocket Cloud migration completes. The inactive setup links may come from the same unfinished rollout, where portions of the new interface shipped ahead of their backend endpoints.

Current status:
Device remains online for extended periods to allow background sync. Calendar still blank; deleted memories continue to return after each relaunch.

I’m not frustrated—just sharing this reproducible sequence in case it helps confirm or diagnose a broader sync issue introduced with the new update. I can provide screenshots if helpful.

Developer Summary (TL;DR):
Firmware 0.8 / App v0.4.2 (203) introduces symptoms consistent with failed tombstone propagation during delta-sync. Local deletions clear correctly but server state re-pushes old recordings on relaunch. Calendar integration fails to populate, and several Settings links (FAQ, Community, Terms) remain inactive. Reproducible with screenshots available.

1 Like
2

hey we have a new release in progress with google which solve all of the above issues we will keep you updated on the same!

1 Like
3

Thanks for the quick response and for confirming a fix is in flight. I’m happy to test as soon as the new build is live. My repro involved idle-session timeouts (firewall banner after device idle), calendars not populating, and deleted memories reappearing after relaunch.

When the update lands, can you confirm whether it’s app-only or also includes backend changes? Any manual steps recommended (sign-out, clear cache, re-add calendars) to ensure a clean state?

4

Thanks for the detailed background-sync explanation, that helps a lot. It also sheds light on the calendar-sync issue I mentioned earlier.

What seems to be happening is that the app successfully gains calendar permission in Android, but the background process dies before it finishes the remote mirror registration. As a result, the app reports “calendar already added” but never pulls in any events.

That would make the calendar behavior, the “check firewall” message, and the ghost-memory re-downloads all symptoms of the same underlying background-process interruption.

For now, I’ve set the Pocket app’s battery mode to Unrestricted to prevent Android from killing it while syncing. I’ll keep it that way until the next release drops.

Appreciate how quickly the team is responding, this explanation really connects the dots between the different issues we’ve been seeing.

1 Like
5

I’m experiencing the same issues. I get that there will be bugs to work out, but unless I am mistaken, i have a 30 day return window that’s closing soon and am so that doesn’t function completely.

I want to like it and want to keep it, but I can’t even try certain things (like the calendar feature) and then when I click support, it doesn’t work…

I appreciate your thorough trouble shooting!

3 Likes