Check out love.data.encode/decode and ImageData:encode.

You have to try all possible combinations that works. This is the code exactly I used for testing while writing mic support for Android. local love = require("love") local recDev = nil local isRecording = -1 local soundDataTable = {} local soundDataLen = 0 local audioSource = nil local devicesString...

Hmm, I would need new device to test that behaviour. My phone does have space reserved for the navigation buttons so can't really say anything until I have new device.

I think I found the problem. There was some kind of code that conflicts with SDL. Mind if you test this APK?

Looks like code responsible to set the immersive mode is failing. I'll double check the code later, but no promise.

I'll release 11.3b when I fixed/workaround it.

I don't always online in the forum and prefer online in Discord, so sorry for the long delay. [...] In all cases I get getSafeArea equal to 0, 0, getWidth, getHeight, but in fullscreen mode, with usedpiscale=false in my model the width is 2560 and in non-fullscreen it's 2413. The height doesn't chan...

What's the difference between the "embed" APK and the non-"embed" one here? https://bitbucket.org/rude/love/downloads/ The "non-embed" version has complete feature from previous LOVE Android APK. This includes opening games from /sdcard/lovegame, opening .love game files, and .love file downloader....

I also want to mention that LOVE 11.2 APK is already compiled with API 28 and support for ARM64 architecture, so it should be compatible with Play Store requirements. Note that ARM64 version of LOVE lack JIT capabilities due to instability issues of the JIT compiler itself, so it can't be turned on....

LOVE Android operates on DPI-scale.
* When making new Canvas, Canvas expects the size to be DPI-scaled unless you pass {dpiscale=1} to the 3rd argument.
* When drawing image, the image is drawn in DPI-scaled units and not in pixels.

Hello, version 11.2 release of the APK fixed this problem. The APK can be found here.