📸 ZimaOS v1.8.0 Released: A Native Photos Experience, Life in Full View

Great job overall, but i am not pleased with the Photos app being forced on us, it has consumed a lot of RAM without ever setting it up, personally i would prefer for the app to be optional, and uninstallable. Thanks!

Thank you for your feedback. We understand that the current layout could provide a clearer overview of your photo library and make browsing easier.

Timeline navigation and ascending/descending sorting are already in development. Our team is also designing clearer ways to display the selected time period and filters. For browsing photos by location, please use the dedicated Map page in Photos.

We’re also planning a “one-click organize” feature to help you manage similar photos more easily. You’ll remain in control of which photos to keep or delete—Photos won’t delete them automatically.

Thank you for helping us improve Photos!

Memory page always shows “Memories are still being prepared”: server rejects the page’s request (ZimaOS 1.8.0)

The Memory page requests GET /v2/photos/memories/suggestions?limit=50, which returns 400 Bad Request every time (seen in the browser console, MemoryPage → getMemorySuggestions). The page then shows “Memories are still being prepared”.

The same endpoint works with a smaller limit. The home page’s call (limit=6) succeeds and the log shows [memory] suggestions ready count=4 items=place_flashback:8615;trip_story:2952;on_this_day:22;auto_highlight:24.

So the memories exist, but the Memory page asks for more than the server accepts. Looks like a frontend/backend limit mismatch.

Server response for the 400: (Bad Request)

Hi, thanks for the detailed report and for comparing the two requests.

Based on what you’ve shared, this looks like a mismatch between the limit=50 requested by the Memories page and what the backend accepts. The successful limit=6 request and the “suggestions ready” log indicate that memory suggestions are already available, so the “Memories are still being prepared” message appears to be misleading in this case.

I’ll pass this on to our development team to investigate both the request limit and the page’s error handling. In the meantime, you can continue viewing the available memory suggestions on the home page.

To help us confirm why the request is being rejected, could you open your browser’s Developer Tools → Network, select the failed limit=50 request, and share the contents of the Response tab? Copied text or a screenshot is fine. If it only says “Bad Request,” please let us know.

Thanks again for providing such useful details!

Thanks for looking into this! Here’s the Response tab for the failed request:

GET /v2/photos/memories/suggestions?limit=50
Status: 400 Bad Request
Response: {“error”:“memory project not found”}

So it may not be the limit after all. The server says it can’t find a “memory project”. A few more details that might help:

The same 400 comes from both the Memory page (MemoryPage) and the Collection page (CollectionLandingPage), both calling getMemorySuggestions with limit=50.

The failing request never appears in the Photos log. Only the limit=6 calls show up ([memory] suggestions request … limit=6 → suggestions ready count=4).

It still happens after a complete reset: I stopped Photos, moved AppData/photos aside, started fresh with a single local source, and the error came straight back. So it isn’t old or corrupt data.

Individual memories open fine (e.g. a place memory with 443 photos), so the memory data exists. Only the Memory list request fails.

My guess is that /memories/suggestions is being matched as /memories/{project_id} with suggestions taken as the project ID, which would explain “memory project not found” and why it never reaches the suggestions handler. Happy to test a build or share more logs.

It seems like you may have previously installed a beta version of Photos.
Can you run this command to see if there are any remnants of the old “photos” package?

ls -lh /var/lib/extensions/

Thanks! There’s no Photos package in /var/lib/extensions/, so no beta remnants:

doconverter.raw
icewhale_files.raw → /usr/lib/zimaos/modules/icewhale_files.raw
icewhale_peerdrop.raw → /usr/lib/zimaos/modules/icewhale_peerdrop.raw
zimaos_zvm.raw → /usr/lib/zimaos/modules/zimaos_zvm.raw

systemd-sysext status shows only those four active on /usr. Photos is the built-in binary: /usr/bin/zimaos-photos, 57,729,488 bytes, dated 21 Apr 2026 (same as the original poster’s). I’ve never installed a beta or test build.

The Memory page error is still GET /v2/photos/memories/suggestions?limit=50 → 400 {“error”:“memory project not found”}, and it persists after a complete reset of AppData/photos.

After resetting the directory, do you have run this commands?
systemd-sysext refresh
systemctl daemon-reload
systemctl restart zimaos-photos