I'm not seeing this issue getting worked on any time soon. I don't think this will be fixed at all if nobody steps up.

As we discussed on the meeting, the purpose of this task is to look out for issues in the public API that would prevent KIO from working properly on android

Talked to Marco, the problem is that we are apparently running on the fallback style, not the Material one. Need to investigate deployment and style configuration there.

https://gitlab.com/fdroid/fdroiddata/merge_requests/6193

As there seems to be little documentation about those changes, the following Qt git revisions are relevant:

• c8b07f7da3ff55f92378a1e98522f318bbc43077 (qtbase)
• 5bb178c479a247720fbc3fbb7f06a32b725193ac (qtbase)
• 670fdcc3f23493bc039a2676ce69892cc152dc6b (qtdeclarative)

MR for FDroid packaging: https://gitlab.com/fdroid/fdroiddata/merge_requests/5840

sorry, I somehow keep misclicking the approve button, was meant to +2 this too of course

Work ongoing, see e.g. D17851 and D17986.

• Delete everything in android-builder and point to kdeorg/android-sdk

@dfaure it's absolutely fine for me to dump this repository and reference kdeorg/android-sdk. The ci-tooling repository looks much more mature and we should not have two competing solutions for an infrastructure task (especially, since the ci-tooling one is actively used and maintained)

In D12864#380354, @apol wrote:

Please use this one: https://phabricator.kde.org/source/sysadmin-ci-tooling/browse/master/system-images/android/sdk/Dockerfile
It's what serves this image: https://hub.docker.com/r/kdeorg/android-sdk
There's also some tooling documented here: https://community.kde.org/Android/Environment_via_Container

factorize into build scripts, add qtquickcontrols, select the right version of the tools.

Up to r17c, but now I'll try the CI's dockerfile...

I tried NDK r18 with cmake 3.10, and cmake is missing commit ca97d4cb5 (from cmake git) which adds support for r18 (starting from 3.12.2). Without that fix, cmake can't find the STL, iirc.

Please use this one: https://phabricator.kde.org/source/sysadmin-ci-tooling/browse/master/system-images/android/sdk/Dockerfile

yes, cmake cmake-3.10.2 should be ok with any NDK (including NDKr18)

In D12864#380259, @dfaure wrote:

Hi Bogdan, thanks for the info.

"Use sdkmanager (from Android SDK) to install Google's cmake."

Any further hints on how to do that?

android-sdk-linux/tools/bin/sdkmanager cmake
Warning: File /home/kdeandroid/.android/repositories.cfg could not be loaded.
Error: Failed to find package cmake

Hi Bogdan, thanks for the info.

I recommend you another approach:
Use sdkmanager (from Android SDK) to install Google's cmake. Personally I'm using it also to install the ndk, but NDKr18 removed the gcc support.
If you need also gcc the best NDK is r17c (has a non-buggy clang and gcc).

Adding Aleix, as I know he's worked on some Android stuff (I only vaguely recall this repository though).

Upgrade to 15c to get a later version of clang 5.0

In https://community.kde.org/Android/BinaryFactory

I wanted to say that http://code.qt.io/cgit/qt/qtandroidextras.git/tree/examples/androidextras/notification is a good start but I changed my mind very fast.
I don't think it's possible to do it entirely from C++, mostly because you need to get notified when the user taps on that notification (I don't know KNotifications API, but I assume it has something like that) , so a small java code is still needed.

I'm offering help on this. I'm quite familiar with the notification Java API, but not so much with Qt on Android.

@mart that piece of code is not that ugly ... it does its job ;-)

From vague memory, I think it should be possible to remove both the widget and the dbus dependency on Android. I'd also focus on the notification frontend API and ignore all the config possibilities on Android.

and we will also eventually need api for having the system bars going over our window as well i guess (like in a photo viewer often you see the photo under the top panel)

in kirigami gallery i'm using this ugly jni code in main.cpp:

Can improve the metadata but some of it is there and that can be improved

https://community.kde.org/Android/FDroid

I guess this can be closed now, correct?

Had a discussion with F-Droid today. Now the plan is to create our own F-Droid repository with the Android binaries coming from binary-factory.kde.org.

KPhotoAlbum should be compatible with both C++11 and C++14. Your change works with both, so: ship it!

Looks fine. Ship it!