Samsung Galaxy S24 Ultra hits NPU wall

Hot take: this is a software-stack problem more than a silicon problem.

• –Samsung's own specs list the Ultra with Snapdragon 8 Gen 3 for Galaxy, so the real issue is the Android acceleration layer, not a magic Samsung-only NPU switch. (https://www.samsung.com/us/explore/mobile/buying-guide/introducing-samsung-galaxy-s24/)
• –Android's NNAPI is deprecated, and Google now points developers to LiteRT delegates and acceleration services for GPU/NPU paths. (https://developer.android.com/ndk/guides/neuralnetworks, https://developer.android.com/ai/custom)
• –MLC's Android docs note that some devices only support OpenCL and most support Vulkan, which is why backend choice matters more than brand-labeled NPU access. (https://llm.mlc.ai/docs/install/tvm.html, https://llm.mlc.ai/docs/deploy/android.html)
• –Open-source apps like SmolChat and MLC Chat show the current pattern: local GGUF/MLC runtimes with GPU-oriented backends, not a universal NPU API. (https://github.com/shubham0204/SmolChat-Android, https://llm.mlc.ai/)
• –The user’s vibe-coded app hitting a wall is the expected pain point: exposing drivers cleanly is harder than writing the chat UI.