as some of you may have heard I have been tinkering with an native port. It is based on slime's fantastic GLES port and uses the 0.9.1 API. As it is a native port with only little code changed pretty much everything should work. However there is no guarantee but should "just work" most of the time.

Differences to the standard LÖVE:
* It uses GLES which requires different shaders and also the graphics module has a slightly different architecture than standard LÖVE on the engine side (but not API wise!). There might linger some hidden bugs there.
* love.system.getOS() returns "Android"
* features multitouch functions love.touchpressed (id,x,y,p), love.touchreleased (id, x, y, p), love.touchmoved (id, x, y, p)
* back button is assigned to the "escape" key
* text input: use love.keyboard.setTextInput(true) or set keyboard position using love.keyboard.setTextInput(enable, x, y, width, height)

Quickstart to get your game running
* Extract your game to /sdcard/lovegame such that main.lua is located at /sdcard/lovegame/main.lua.
* Run the app

0.9.2 (2015-04-10):
- updated API to match that of LÖVE 0.9.2
- love.window.setFullscreen can be used to switch between regular and immersive mode without status and navbar
- added loading of games by opening a main.lua file
- quitting LÖVE now conforms to the Android application lifecycle
- stop vibrator when app is paused
- fixed battery drain by properly pausing OpenAL device
- fixed printing of non-number and non-string values
- fixed compilation of Android NDK r10
- fixed compilation warnings concerning APP_PLATFORM
- old instance is shut down when opening a new game (note: it may crash when opening games at a high frequency, e.g. more than 2 per second)
- updated OpenAL-Soft to version 1.16.0
- updated to newer SDL version (f9244b2a151)

0.9.1:
- uses 0.9.1 API
- fixed crash on Moto G (and possibly other devices). This was a nasty bug that would just show a blue screen without an error message. The bug was resolved using the help of headchant
- fixed loading of jpegs (it probably hasn't worked up to now)
- fixed issues with looping over active touches. This fix was sponsored by slime!