Skip to content

Releases

Loopr 1.19: 3D models

Choose a tag to compare

@PortableDiag PortableDiag released this 13 Nov 05:27
  • 3D models. ⋮ › 3D models shows VRM avatars (0.x and 1.0), GLB and glTF files — the same formats Loopr Desktop opened in 0.2 — in a full-screen viewer: drag to turn, pinch to zoom, two fingers to pan, double tap to reset; Front / Back / Side / Top, Spin, a ☀ Light slider and a choice of background; ⏮ / ⏭ step through the folder. Drawn by Google's Filament in the rest pose with the model's own textures and materials; animation, spring bones, expressions and outlines are not drawn, as on the desktop.
    • Android's media permission doesn't cover model files, so Loopr finds them in its own folder (Android/data/com.loopr.player/files/Models), in folders you add with Android's picker, and in files you open. A file manager can open a .vrm, .glb or .gltf straight into the viewer.
    • The grid shows each VRM's own thumbnail.
    • Fixed before it shipped: most VRMs first came out as flat yellow silhouettes. Their exporter writes "image\/png" (legal JSON) and Filament's loader compares that text literally, finds no PNG decoder and drops every texture. Loopr now rewrites the escape before loading.
  • The local API does all of it. Two new tools, named as on Loopr Desktop: loopr.model (rotate, zoom, pan, preset views, reset, spin, light, background, next / previous / jump) and loopr.screenshot (a JPEG of a player, a floating window or a model view — the picture alone, or the screen as drawn). loopr.library and loopr.folders list models too, with a kind; loopr.open opens them; loopr.players, loopr.queue and loopr.window close cover model views. New routes /api/models… and /api/players/{id}/screenshot. Over MCP a screenshot comes back as an image. New tools start switched off on existing keys, as every tool does.

Loopr 1.18: local API on port 8793

Choose a tag to compare

@PortableDiag PortableDiag released this 27 Oct 21:45
  • The local API moved to port 8793. 8792 was free on the phone but not on the computer, where TrellisBridge already listens on it — so adb forward tcp:8792 tcp:8792 failed there. 8793 is free on both and in every other in‑house app. If you already changed the port yourself, yours is kept.

Loopr 1.17: a local API

Choose a tag to compare

@PortableDiag PortableDiag released this 27 Oct 19:12
  • A local API, so scripts and agents on your phone can use Loopr — the same shape as DialX, TextX and NotifX, so PhoneAPI can take it on as a provider later without changes. Off until you turn it on (⋮ › Local API).
    • It does everything the app does: browse and search the library and its folders, fetch thumbnails, open a video full screen or in a floating window (with the whole library, its folder, or just that video as the queue), play, pause, seek, rewind, skip and jump through the queue, set and clear the A–B loop, change speed, mute, resize, repeat, shuffle and zoom, float, expand, picture‑in‑picture, rotate, move and resize floating windows, close players, and read or change the settings.
    • This phone only, on 127.0.0.1:8792. A web page can't reach it by pointing its own name at the phone.
    • A key per caller, and a new key can do nothing. Each of the 12 tools is its own switch, off until you tick it; changes apply at once, a key can be revoked at any time, and each keeps a list of its recent calls. Loopr stores only a fingerprint of a key, so it is shown once.
    • REST for scripts, MCP for agents, and one gate behind both. GET /api/docs with a key is the full reference.
    • When it can't do something it says why and what's left — floating needs "Display over other apps", three windows is the limit, B has to come after A — rather than failing silently. Granting Android permissions stays with you.
  • The library list moved out of the main screen so the grid and the API read exactly the same videos in the same order.

Loopr 1.16

Choose a tag to compare

@PortableDiag PortableDiag released this 15 Sep 00:40
  • Fixed floating windows dying with "Can't play this video in a window" after you open a video from a different folder. Your description of it was exactly right, and the cause is the folder: the permission to read a video that a file manager gives Loopr belongs to the screen that received it, and Loopr closes that screen the moment it hands the video to a floating window. The window keeps playing on the file it already has open — and dies the next time it re-opens it, which is every few loops of a short clip and every move to the next video. Opening another video from the same folder hid it, because a file manager hands over the whole folder, so the older window's file got its permission renewed by accident. From a different folder, nothing renewed it.
    • From your phone's own log: SecurityException: Permission Denial: opening provider androidx.core.content.FileProvider from com.loopr.player … that is not exported from UID …, reported to the player as a plain I/O failure — which is why Loopr thought the video was broken, skipped to the next one, and closed the window when that failed too.
    • Loopr now passes the permission on to the window when it hands over the video, and back to full screen when you tap ⛶, so a window holds the files it is playing for as long as it is open.
    • A permission can't outlive the app's process, so a window restored after Android kills Loopr still can't read files opened from a file manager. It now says so plainly instead of hunting through the folder first.
  • Fixed Loopr running out of memory and taking every floating window down with it. Each player was allowed to read ahead by up to 128 MB — ExoPlayer's default — and Loopr can have four going at once (three windows plus the full-screen player) inside an app limited to 256 MB. On an ordinary video it never showed; on a high-bitrate one the second player tipped it over, and Android kills an app that runs out of memory instantly and without a word. That is a popup disappearing for no reason you could see.
    • Found on your phone, not reasoned about: one window playing a 20 Mbit/s file was holding 139 MB, and floating a second video died inside a second with java.lang.OutOfMemoryError on ExoPlayer's loader thread.
    • Every player now reads ahead by at most 16 MB — all four together use less than one of them used to. These are files on your phone; reading further ahead buys nothing but risk. The same window now sits at 26 MB.
  • A floating window can now be made nearly as big as the screen. The old ceiling was 60% of the screen's width, barely a step above the smallest a window is allowed to be — so making one bigger stopped almost as soon as it started. It now goes to 95% of the width, or as tall as the screen allows for an upright video, whichever comes first.
  • Pinch inside a floating window now zooms the picture, 1× to 5×, exactly as it does full screen — for when you can't quite make something out. While zoomed, dragging moves the picture rather than the window, and a double tap zooms to 2× or back.
    • The window itself is now resized by the grip in its bottom-right corner, which appears with the controls. One gesture can't mean both zoom and resize without guessing which you meant, so the picture kept the pinch and the window got a handle.
  • Settled, and unchanged: opening a new video never pauses the ones already playing — that is what multiple players is for — and every floating window keeps its own A–B loop, set before you floated it.

Loopr 1.15 — the crash that was closing your popups

Choose a tag to compare

@PortableDiag PortableDiag released this 13 Sep 17:07

Fixed the crash that took Loopr down — and every floating window with it.

Tapping ⏪, or double-tapping the left of the screen, in the first ten seconds of a video crashed the whole app whenever the player hadn't worked out that video's length yet. Rewinding ten seconds from three seconds in asks for a negative position, and the check meant to keep the position in range couldn't cope with one.

Loopr is a single app process, so the floating windows live in it too: one bad tap in the full-screen player closed every window you had open, instantly and without a word. That is why the popups looked like they were dying on their own.

Found in the phone's own crash log rather than guessed at:

java.lang.IllegalArgumentException: Cannot coerce value to an empty range:
maximum -6424 is less than minimum 0.

A video's length is now picked up whenever the player works it out, not only at the single instant playback starts. When the two didn't line up, Loopr treated that video as having no length for as long as it played — a seek bar stuck at zero, a running time stuck at 0:00, no A–B markers, and the rewind crash above armed for the whole video instead of for a fraction of a second.

Covered by tests that include the expression that shipped in 1.14, asserting it still throws on the exact value from the crash. 15 instrumented tests pass on API 35.

Loopr 1.14

Choose a tag to compare

@PortableDiag PortableDiag released this 30 Aug 04:33

Loopr now asks for notification permission instead of quietly going without it.

It was declared in the manifest but never actually requested, so on a fresh install Android denied it by default — confirmed on a clean install: POST_NOTIFICATIONS: granted=false.

That hides more than the floating-windows notification. Android throws away an app's on-screen messages entirely when its notifications are off, so every explanation Loopr gives you — why a window closed itself, why a folder couldn't be read — was being discarded before it reached the screen. A window closing with a reason looked exactly like Loopr being killed.

Loopr asks once, when you turn floating windows on, and explains why first — as a dialog, because a toast is the one thing it can't show while the permission is missing. Say no and it won't ask again.

Verified on a clean install: prompt appears, granting sets granted=true, the ask-once flag persists across relaunches, and the toast suppression in the system log is gone. 9 instrumented tests pass.

Loopr 1.13

Choose a tag to compare

@PortableDiag PortableDiag released this 30 Aug 02:56

Fixed floating windows vanishing while you're in another app.

They were never closing themselves — the whole of Loopr was being shut down. A floating window outlives the activity that opened it, so the only thing holding one is a background process. When the system reclaims that process every window goes at once, in silence, taking the queue, the position and the A–B points with it, because they only ever existed in memory — and nothing brought them back.

Loopr now writes the open windows down as you use them and puts them back when the system restarts it: same size, same place on screen, same video, carrying on from where it got to.

  • It gives up after three restores in quick succession and says so, rather than fighting the system for your battery.
  • Windows you close yourself stay closed; only ones taken away from you come back.
  • Covers the process dying for any reason — memory pressure or a crash. Android shows you nothing in either case, which is why the two look identical from the outside.

Also

  • A window that fails to go back up after a rebuild is now closed properly, instead of leaving a player running with nothing on screen.
  • Every reason Loopr closes a window is now written to the log as well as shown. Android suppresses an app's toasts when its notifications are turned off, so on a phone where that's the case Loopr's explanations were being swallowed and windows appeared to vanish for no reason.

Verified on the emulator: three floating windows, one dragged somewhere distinctive, killed with SIGKILL — all three came back at identical geometry, on their own videos, playing on from where they were.

Loopr 1.12 — the black floating window, root-caused

Choose a tag to compare

@PortableDiag PortableDiag released this 19 Aug 00:05

Fixes the floating window that stops playing and turns black — root-caused, not another safety net.

When a video hits a playback error ExoPlayer parks itself in an idle state, and an idle player does not restart on its own. Loopr moved the queue on to the next video but never told the player to load it, so the window sat there with no picture, no sound, and a play button that did nothing — which is why closing and reopening the window was the only way out.

Nothing ever noticed, either: both signals in the stall watchdog only run while the player claims to be playing, so the exact state this failure lands in switched the whole watchdog off. Two releases built to catch this could not see it by construction.

  • A video that fails is retried where it stopped first — a momentary fault shouldn't cost you the video you were watching. It moves past it only on a second failure, and closes the window with a reason only once nothing in the queue will play.
  • A decoder taken back by the system, which is what happens when something in the foreground wants one, is now retried instead of treated as the device being out of decoders.
  • The watchdog can now see playback stopping — a third signal alongside the two frame signals, recovering by reloading the video, reloading it where it was, then moving past it. The log names which tripped: signal=playback, signal=composite, signal=frames.
  • The same defect is fixed full screen, where a failed video left a black screen with dead controls.
  • Both play buttons now recover a stopped player instead of doing nothing.

Reproduced on an API 35 emulator with a deliberately truncated video: before, the window was uniformly black for the whole run with not one watchdog line; after, it retries and moves on within four seconds. Verified on the signed release build. Covered by a test that fails against 1.11 and passes here.

Loopr 1.11

Choose a tag to compare

@PortableDiag PortableDiag released this 17 Aug 01:18

A floating window that goes black is now noticed even when the video is still decoding perfectly.

1.10 watched the frames the player handed to the window. That turns out to be the wrong question: those frames keep flowing into a window that has stopped putting anything on screen — so the black window 1.10 was built to catch was exactly the one it could not see.

  • Each window now also watches frames actually reaching the screen, so the two signals together cover both halves of the failure.
  • New recovery step for that case. Handing the surface back doesn't help a window whose drawing is itself dead, so before giving up Loopr takes the window down and puts it straight back up — rebuilt from scratch, video carrying on from where it was.
  • The diagnostic now says which signal tripped: signal=composite for a dead picture under a healthy player, signal=frames for playback itself stopping. That is the detail that names the underlying bug.
    adb shell setprop log.tag.LooprQueue DEBUG
    adb logcat -d -s LooprQueue | grep -E 'stalled|recovered|rebuilt'
    

Still a safety net, not a root-cause fix. The failure has never been reproduced away from the reporting device — eight scenarios were run against it on an API 35 emulator this session (three windows through a full-screen video, seven trim-memory levels, screen off/on, rotation, Settings on top, the notification shade, and a soak) and none of them produced it. What this release does is close the blind spot that stopped 1.10 from seeing it, and make the next occurrence say what it was.

Verified not to fire on a healthy window across all of the above, on the signed release build from a clean install. All 6 instrumented tests pass.

Loopr 1.10

Choose a tag to compare

@PortableDiag PortableDiag released this 15 Aug 16:53

A floating window that goes black while the video carries on playing now notices and fixes itself.

Loopr already closed a window with a message whenever the player reported a failure. But a video surface can stop putting frames on screen without reporting anything at all, and nothing in that path fires — so the window was left as a black rectangle with no way to recover it.

Each window now watches the frames actually being drawn rather than taking the player's word for it. If they stop for three seconds while it still claims to be playing, it hands the surface back, then reloads the video at the same spot, and only if neither works does it close the window and say why.

  • Quiet about it — a window that recovers just carries on playing.
  • Stays out of the way when frames stop for a good reason: screen off, or the system hiding overlays over Settings and permission dialogs. Verified against a long A–B loop, which seeks back every few seconds and is the case most easily mistaken for a stall.
  • When it does fire it records whether the playback clock was still running — the detail that says whether the picture died or playback itself wedged. adb shell setprop log.tag.LooprQueue DEBUG.

Verified on an Android 15 emulator against a clean install of this signed build, plus six instrumented tests driving a real overlay window.

Honest limit: the black window this addresses was seen once, briefly, and could not be reproduced — so this is a safety net and a diagnostic, not a confirmed root-cause fix. If a window still goes black, the log now says what happened.