You may want to add all of those into the `app/src/main/AndroidManifest.xml` instead of per-individual AndroidManifest.xml in normal/playstore/embed variant.

Do you even try that?

I'd say this is only useful for Lua C modules that have been written by someone else and you want to use it to the fullest. For example, LuaSocket, but it's bundled with LOVE anyway. Most people who use LOVE against using external C modules because it's hard to maintain for all platforms that LOVE n...

Make sure to multiply all the mouse coordinates by love.graphics.getHeight()/game.screen_height too.

It's not possible. You have to use Android API which interacts with LOVE code and pass the file streams over.

The bolded part is important. You're not allowed to pass file paths since Android 7.

For the unicode problem in io.open(), you can just slap https://gist.github.com/MikuAuahDark/d6 ... d710347ac0 and pass UTF-8 files.

No, you can't really do that. I think you may want to release a game under MIT License, then yes you can do that while having LOVE under zLib license. The LOVE zLib license only applies to LOVE itself. You can, however modify LOVE and use the modified LOVE in conjunction with your own game, but you ...

I am actually using the unix terminal of the android device. local dir = io.popen ("ls "..someDir) io.input(dir) I dont know if this is portable to any other android device I think yes. I will take a look to how works that library u mentioned. That works, but you have to request external ...

Yeah, I have plans to turn on LuaJIT for Android in LOVE 12.

One of the currently most annoying problem with LÖVE Android is that it can't open *.love files inside the filesystem. The reason behind this problem because Android Nougat changed completely how file should be handled to another program , but at same time this also completely broke file association...