You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.