u/Perza

First of all I really like Nuvio, I'm a supporter and love what the devs are doing so far. But since I was having constant issues with playback on my xioami mi tv 3rd gen, at first I was using Just player to solve that. But let's be honest, who doesn't like a nice player UI and the intro skipping feature, automatic subtitles and what not... So I stumbled upon a forked version by the user Ysors123:

https://github.com/ysosrs123/NuvioTV-Fork

And holy hell, this guy is all about optimizations for the essential thing about Nuvio, playback. You play the heaviest stream available and after that, an automated feature in settings sets your player preferences for flawless playback. From native exo memory to buffer and network settings, everything is explained and set for your particular device and network, so no more buffering, stutters, jitters and other playback glitches. I was blown away how good this is implemented. He's also doing great optimizations to the ui and background stream fetching, so when you open details, the streams are already fetching in the background and the best one with indicating badges ready for playing in a few seconds. It's seriously good. I know I maybe sound like a commercial but if anyone is having playback issues or is simply willing to try the fastest playback possible, give this fork a go. The guy is constantly optimizing and documenting the newest releases. Peace 💙

Ok, so I've tried both 0.8.2 versions, the github apk and the one from the Playstore and the gui performance difference on my Xiaomi mi tv 3rd gen streaming box is huge. The app was installed, opened once, closed, then opened again when I recorded the two videos. So basically a cold start of the app. I remember some old posts when some users were having the same experience and even Tapframe asked me to record a video but I haven't really had time until now so here it is. I also asked Gemini what could be causing this difference and this was the answer:

"Yes, it is entirely possible and quite common for a GitHub APK build to perform noticeably worse on cold start than the exact same version downloaded from the Google Play Store. The UI stutter you are experiencing on Nuvio’s GitHub release stems from key differences in how Android compiles, packages, and optimizes apps for the Play Store versus standalone APKs. Key Reasons for the Performance Gap

1. Missing Baseline Profiles & AOT Compilation (The Primary Culprit) Nuvio is built using Compose Multiplatform / Jetpack Compose. Declarative UI frameworks generate thousands of dynamic rendering functions that require heavy CPU work on initial launch.
   Play Store Version: When you install Nuvio from the Play Store, Google Play automatically delivers Baseline Profiles. Android Runtime (ART) uses these profiles to Ahead-Of-Time (AOT) compile critical UI paths and layout routines into native machine code at install time. Cold starts run immediately pre-compiled at 60/120 FPS.
   GitHub APK: Sideloading a generic APK bypasses Google Play’s Cloud Profile compilation. Your phone falls back to Just-In-Time (JIT) compilation. On every cold start, ART has to interpret and JIT-compile the Compose rendering pipeline on the fly, leading to obvious frame drops and UI stuttering.
   (Note: If you leave the GitHub APK installed and leave your phone idle on a charger overnight, Android's background maintenance job dex2oat will eventually compile the app locally, reducing the stutter over time.)
2. Universal APK vs. Device-Optimized Split APKs (App Bundles) Play Store (AAB): Google Play generates split APKs tailored specifically to your device’s exact architecture (arm64-v8a), CPU instructions, and display density. GitHub Releases: GitHub releases often package a Universal APK containing native binaries (armeabi-v7a, arm64-v8a, x86_64) and uncompressed fallback assets for maximum hardware compatibility, leading to larger memory overhead and slower initial DEX loading.
3. Differences in R8 / Code Shrinking Optimizations To publish on the Play Store, developers typically run heavy R8 full-mode optimization, which removes dead code, inlines functions, and rewrites bytecode to minimize runtime overhead.
   Automated GitHub CI/CD build scripts sometimes build standard release APKs with partial R8 optimization or without specific ProGuard rules to ensure the build doesn't fail across generic environments. What You Can Do If you want to keep using the GitHub build, the initial cold-start stutter will usually smooth out after a few days as Android's local background compiler profiles your usage patterns and pre-compiles the app automatically. However, for UI-heavy Compose apps like Nuvio, the Play Store version will almost always provide the smoothest out-of-the-box experience."

Would like devs to chime in on this, and would also like to hear if other users are having the same experience.

I'm using tam-taro complete sel template and inbuilt formatters and the issue is, the tags in formatter aren't legit. The video isn't hdr and doesn't include the dts hd ma track. Haven't tinkered anything with regex, basically stock template. What say you?

If they're not accurate they're basically useless...

I'm using tam-taro sel template which I love btw and was wondering if I even need these two preinstalled add-ons enabled. I'm using only real debrid for streaming and added debridio. Thanks!