Pocket App 0.4.5 +211 sync improvements, ghost recordings, and timestamp fix

General
1

Hey all, I updated my Pocket app to 0.4.5 +211 (still running Firmware 0.8 / Wi-Fi v4) and have been testing it through tonight’s city commission meeting. A few interesting things to share for anyone else checking out this version:

What’s new / what I’m seeing:

The “Look up Device Files” option now works and shows unsynced recordings on the device.

The FAQ, Support, and Community links in Settings are finally live.

The calendar bar at the bottom of the main screen is gone, but events still seem to link correctly to recordings.

When I recorded tonight’s meeting, it first showed up in Look up Device Files with tomorrow’s date. After choosing Sync to Pocket Cloud and then tapping Check for new Memories in Settings, it reported one file available. After download, the file appeared on the main screen with the correct date.

What seems to be happening:

Looks like Pocket is now using a two-step sync process, record locally first, then push to the cloud where it gets the proper timestamp. The UTC-offset date only shows up before the upload finishes.

Still seeing:

Deleted or “ghost” recordings are re-appearing after sync, so the deletion flag isn’t sticking yet.

Overall:

This version feels focused on data integrity and sync stability. The new file view makes it easy to see what’s actually stored on the device, and manual cloud sync is working reliably now. The only quirks left are the time-offset preview and the ghost re-imports.

Questions for the Pocket team:

1. Is the +1-day timestamp bug already on your radar?

2. Will the ghost recordings issue be addressed in the next delta-sync patch?

3. Should we keep manually syncing from Look up Device Files, or will those auto-upload eventually?

Hope this helps others testing 0.4.5 +211 — curious to hear if your results match mine.

2 Likes
2

hey so the settings files list is not in the users time zone as of now. the device stores it in UTC so thats why you are seeing +1 day.

You will still see the sync recording option in the home screen to sync.

1 Like
3

have messaged you about the ghost recording issue do let me know!

currently auto uploads are under development so we will keep you updated on that

1 Like
4

@mhirrrr I have the ghost recording issue - I had deleted them, and removed them from trash, but 4 of them still show up. Let me know if you need another example.

Android, SW 0.4.5+211, FW 0.7, WFW V4

1 Like
5

hey guys gonna have one of my engineers @bharat to look into this will keep you updated thanks

3 Likes
6

3. Should we keep manually syncing from Look up Device Files, or will those auto-upload eventually?

We recommend continuing to use the regular sync flow. However, if you notice any irregularities or wish to remove specific files from your device manually, you can use the Browse Device Files feature to do so.

Will the ghost recordings issue be addressed in the next delta-sync patch?

The ghost recordings issue should be resolved in the current version. However, please note that this fix won’t apply to files that were previously deleted in older version; you can manually remove those using the Browse Device Files feature.

If you continue to experience the issue after updating, please share a screen recording with us at tech@heypocket.com so our team can investigate further.

3 Likes
7

Hi @mhirrrr and @bharat,

I’m running the latest Android build (Pocket App 0.4.5 +211, FW 0.8, WFW v4) and performed a fresh test regarding the ghost recording issue.

Here’s what I observed:

I deleted the “Focaccia or Baguette” recording and renamed “The Kevin Roach Starter Kit.”

After closing and reopening the app, the deleted recording reappeared and the renamed file reverted to its original title.

Some of the earlier ghost recordings (pre-update) appear to have finally cleared, which suggests partial success with the new deletion system.

It looks like deletions and renames made in 0.4.5 +211 still don’t persist through a full sync cycle.

Happy to run additional tests or provide a screen recording if that would help your team verify the behavior.

— Andrew

8

@bharat will be taking a look at this thanks

9

Hey @arigsbee , DMing you for deeper analysis.