[Abe]

The open source library androidnative offers an advanced system integration for Android apps that goes significantly beyond Felgo features. Can I combine this library with Felgo and if so, how? However, the library was last updated two years ago, so the question arises whether it makes sense to build on this or to migrate the project to the JNI integration from Felgo.

[Abe]

I have added his instructions how to integrate the library. This may help to answer my question.

https://forum.qt.io/post/576710

[AlexFelgo Team]

Hi Abe,

what feature(s) are you interested in particularly? You can integrate native libs with Felgo the same way as with Qt. If you create a custom activity, make sure to derive your own activity from the Felgo (V-Play) activity like mentioned here: https://felgo.com/developers/forums/t/change-of-activity-name-in-androidmanifest

Cheers,
Alex

[Abe]

Androidnative requires a special instantiation in the main class. This might be a conflict:

#ifdef Q_OS_ANDROID
#include <AndroidNative/systemdispatcher.h>
#include <QtAndroidExtras/QAndroidJniObject>
#include <QtAndroidExtras/QAndroidJniEnvironment>

JNIEXPORT jint JNI_OnLoad(JavaVM* vm, void*) {
    Q_UNUSED(vm);
    qDebug("NativeInterface::JNI_OnLoad()");

    // It must call this function within JNI_OnLoad to enable System Dispatcher
    AndroidNative::SystemDispatcher::registerNatives();

    return JNI_VERSION_1_6;
}
#endif

Android native offers a convenient way to bridge QML and the Android Java API. It even offers already some convenient QML types and methods, for example to retrieve messages or make a call. Felgo offers only the standard way for JNI and a limited set of convenient methods like retrieving the address book.

[AlexFelgo Team]

Hm, I don’t see an obvious reason why this should not work from within the Felgo main.cpp as well. You might wanna give it a try, and if you do not succeed we can pull in one of our native implementation specialists.

Cheers,
Alex

[Abe]

Thanks. I’ll try it.