Blender, the famously open-source 3D application, has landed on Android tablets—just not with any official fanfare, and certainly not with production-ready stability. Developer epai recently released an unofficial port of Blender for Android, with tests running on hardware like the Xiaomi Pad 7 and Samsung tablets. While it boots and basic modeling is possible, feature completeness is a distant dream.

Rendering: Black Holes for Material Spheres

According to epai’s technical logs on the Blender devtalk forum, this Android port boots and can handle simple modeling and animation tasks. However, material previews in the shading workspace are visually broken: only small portions of the preview sphere are lit, while the rest are black. The root cause is incomplete support for OpenGL ES—specifically, textures for probes such as probeHdr, probeDepth, and probeCubes do not display as intended.

This is not a trivial bug. As Sergey, a Blender core developer, points out in the same thread, OpenGL ES is not fully supported by Blender’s rendering engine. The upcoming Vulkan backend, currently in beta for Blender 4.3, is likely the only realistic path toward better compatibility and future mobile support.

Still a Hobby Project

The port remains a one-person, experimental project. There is no official support or endorsement from the Blender Foundation. Current releases are not linked on blender.org, and users looking for APKs or source code must hunt through developer forums for the latest builds. epai has stated his intention to improve input handling (touch, keyboard shortcuts), but stable releases or user support are not available.

Input: Stylus, Touch, and Basic Shortcuts

Early builds can register touch input and basic shortcuts, and epai notes limited success with modeling and simple animation creation on Android devices. Advanced input—such as pressure-sensitive stylus support or multi-touch gestures—is not mentioned in any available logs. If you like your 3D work with an extra side of beta-testing, you’ll feel at home here.

Blender on android test
byu/notrealadnan inblender

Hardware: Can Android Keep Up?

Anecdotal commentary from the r/blender Reddit thread suggests that today’s Android tablets are “almost as fast and way more efficient” than the laptops Blender ran on fifteen years ago. While this points to decent baseline performance, it says nothing about stability, feature parity, or support for complex production scenes. No benchmarks, stress tests, or comparative statistics are available.

Vulkan or Bust

The consensus, both from epai and Blender’s own developers, is clear: don’t expect reliable rendering or full feature support until Blender’s Vulkan backend is both finished and well-supported on Android devices. Vulkan is actively being developed for Blender 4.3+, but Android drivers and device support remain variable and unpredictable.

Download If You Dare

Anyone brave enough to test this Android port should expect instability, major rendering bugs, and missing features. As always, experimental builds must be thoroughly tested before risking them on live productions.

The post Blender on Android: Ported, Not Polished Yet first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

You should have a working connection from DaVinci Resolve (DR in short) via an I/O device by Blackmagic to a monitor or TV of acceptable quality up and running. And then, you need a probe, like a ColorMunki, and should be able to start DisplayCal. Oops, macOS complains that it’s not by a certified developer? Try again, by a right-mouse click on it, and choose to open it against overprotective mum’s advice. If you got it from the link provided in part 2, there’s no reason for concern. You can’t expect a developer of free software to spend time and money on Apple notarisation, as it’s called officially.

Connecting the software

To generate a correction LUT for your monitoring path from DR you need to have both programs running and give DisplayCal access to your screen. To measure the whole signal chain, it’ll need to control the display from the inside of DR. This possibility is already built into DR under “Workspace” for calibration with Calman, a commercial solution. But you’ll find the entry “Monitor Calibration” only when the Color page is open, it’s greyed out on the other pages. Once the lower of the two entries is selected you’ll see a box waiting for an IP address.

On the side of DisplayCal you need to choose the generation of a 3D LUT for Resolve under “Settings”, and Display needs to be set to Resolve. On the right you should see your connected probe and for “Mode” we use LCD (generic). We have “Correction” left on “Auto”, since we don’t know exactly what our screen is using for backlight, but you can find quite a few popular displays in the list to choose from. If you now go for “Calibrate & Profile” and say “No” to the next choice, the software will tell you it’s waiting for a connection by a specific IP address.

Switch to DR and type that IP address into the box waiting there. Don’t try to enter the whole line, only the first four numbers separated by periods. The last number is the port, which should already be showing up under “Port” in DR. Alternatively you can also enter your local host, since we are connecting on the same machine. That would be written as “Name-OfYour-Computer.local”, while also giving the port below. Clicking on “Connect” should do just that, and you are ready to start. If it doesn’t connect, check if the address is already in use.

Adjusting your screen

Any display should offer a brightness setting, which would be around 120 nits for Rec. 709 / Rec. 1886, which you’ll see while “Measurement” is running. It would be also desirable to adjust Red, Green, and Blue independently, which our monitor offers under “Custom” for “Color temperature”. We got remarkably close to perfect balance, as indicated by the green values with a checkmark. But don’t worry if that doesn’t show up, just get these as close as possible. Once set, don’t forget to note the custom settings of your screen somewhere, in case anyone may fiddle with those.

Now stop the measurement and start profiling. Depending on your probe, it may ask you to first calibrate itself, like our ColorMunki Photo, which even did this three times throughout the process. The ColorMunki Display doesn’t ask for this, since it should have its own presets. But that’s also the reason why it will not work well with backlight technologies that didn’t even exist when it was made. Neither would we expect the ColorMunki Photo to handle anything with OLED well, since these have such deep black.

Profiling aka calibration

There are some rumours claiming that the relatively cheap ColorMunki Display had the same hardware as the more expensive models and was simply throttled by slower timing. We can’t verify that, since either probe needed 6 to 7 minutes on our MacBook M1 Pro. But as already explained in part 2, the more expensive Spectrometer may get equally slow due to less sensitivity in the deep shadows. Don’t get fooled by the predictions for a single patch, there are many more to wait for. Whatever, the results were impressive for a Xiaomi G34WQi Ultrawide Gaming Monitor for around 300,- €. After all, it came with a quite similar individual factory profile in the box.

But you can’t rely 100% on one single result, since all cheap probes have a certain level of tolerance and sample variation. There’s a reason why professional probes like a Klein K10-A not only cost as much as a serious motorbike, but also need to be re-certified regularly. If you know somebody with such an instrument, he/she can check yours for deviations. We made another test with the ColorMunki Display. It failed once for unknown reasons, but on second try we got a pretty good result too. The slightly larger, but still perfectly usable values don’t necessarily tell you about a weaker device, but might as well be more realistic.

Update on September 18th, 2025

Please make sure that you use the latest version of DisplayCal, which is 3.9.17 as of this day. There was a bug in earlier ones where the black point correction was applied even if switched off, which would make your blacks muddy.

The post Calibration for less – Part 3 first appeared on DIGITAL PRODUCTION and was written by Uli Plank.