I have to second this. Serious attempts to use the NDK for application-layer work will turn your hair white. It's by far the most god-awful mobile/quasi-embedded tasks I've had professionally. In my experience it's second maybe only to porting C-decompiled FORTRAN between families of obsolete and badly documented DSP chips.
If you have anything compute-intensive enough to affect battery life in an Android app, you really ought to use the NDK, and Go will probably be officially supported: https://docs.google.com/document/d/1N3XyVkAP8nmWjASz8L_Ojjnj...
Or if you want Android/iOS portability, find a common API for SQLite and implement in C.
https://github.com/seclorum/ios-go-ipfs/blob/master/ipfsios/...
What's going on here?
[ * - See https://en.wikipedia.org/wiki/Bridging_(programming) ]