Hi,

Warning: I am NOT a lawyer

That said, and to the best of my knowledge, you have to provide requesters with the object files generated at compilation time so that they can link modified versions of Qt if requested ☺️

@J.Hilk I could have sworn that the SDK manager installed the latest NDK.
I updated manually and now it works. Thank you so much for your help!

Unfortunately it didn't work. I still get the same value. Any other suggestion?

I have updated Qt to version 5.12.1 and IIRC never seen the message again.

Therefore, I have checked and went back to target API level 24 and the message pops up again. Going back to API level 28, the message is coming anymore. I will stay so far with Qt 5.12.1

@koahnig
try:

QAndroidJniObject arrObj = nObject.callObjectMethod<jbyteArray>("getData", "()[B"); jbyteArray arr = arrObj.object<jbyteArray>()

(jbyteArray is of type jarray, which is of type jobject)

@J-Hilk

Yes, I can start two instances of creator and use different settings for Android devices.
Not really comfortable, but it is working.

@raven-worx

OK, thanks. That seems to work.

@morte said in detecting status ("on"/"off") of location services:

This is brobably Qt bug

I'd call it working as designed, although the design could differ from your expectations :-)

Seriuosly, I guess you can post a feature request to ask for the error status to be cleared once positioning data resumes.

For the time being, I guess you need to stop checking for error status once you resume receiving data, or you could even emit a signal of your own once you know data is back again.

Switched back to newer SDK folder holder a different adb version 1.0.40. That version did not support the run-as command as indicated above. Exited creator, started it again and did a rebuild and started debug on Nexus 7 without problems.

BTW all has been tested with creator 4.8.1 after I have seen no difference to old creator version 4.5.2.

The problem could be solved by updating the Android suite to newest version.

@morte

ApplicationWindow { Item { id: banner x: 0; y: 0 width: parent width; height: 50 } Item { id: content width: parent.width anchors { top: banner.bottom bottom: parent.bottom } } }

@koahnig So there's config and rebuild needed. Thank you very much for the helpful reply.

@koahnig Thank you for your reply

@Qjay said in QtAndroid local notifications , notifications poping up immediately:

the notifications are popping up almost instantly ( despite me providing time for it ).

you pass the time you want it to be triggered from now on. The API expects a time since EPOCH (as your comment in the code also states) which are the milliseconds from 1970/01/01 on.
So in your JAVA code add new Date().getTime() milliseconds to your current timeout.

So far i am able to get the notifications ( but not on Android O )

did you read this already?
Alos chekc the Qt debugger console and/or LogCat for suspicious messages regarding notifications.

@noone You will need to extract the content from qrc file to some location writable by your application and then load it from there in webview.

Hi,
Did you succeed to compile the PostgreSQL plugin for android?

It was me doing stupid things on JNI_Onload for application, and being called also for service; then crash.

Alright, I found the error:

In the TextEdit {} I had inputMethodHints: Qt.ImhNoPredictiveText because in earlier tests, sending emojis to TextEdit crashed the app.

But with PredictiveText disabled, all fancy input methods and hence the different keyboards don't work. Also, Emojis are no problem anymore and animated Gifs are disabled.

Did you find something about that ? I'm also interested by subscriptions in Qt Purchasing

Thank you very much.

Hi,

IIRC, you can't directly do that. However, there where some scripts in the qtqa repository to run the tests in the CI, you might be able to leverage that.

Hope it helps

No, because they were neved emitted. I just found this: https://bugreports.qt.io/browse/QTBUG-38401, it seems that they are not implemented yet for Bluez 5. However, I would like to set the pin in only one-way, the raspberry shouldn't accept any pairing if the pin code (probably hardcoded in the raspberry) is different from the one entered by the user. Anyway, I'm not sure if this is possible.

You need to set ANDROID_NDK_PLATFORM=android-19 to set the NDK definition correctly. The ANDROID_API_VERSION is for the SDK.

@BINALECTRUM said in Android build and deploy. 64bit, Clang, new app store developer console rules [2018 & 2019]:

Is Qt going more in embedded/car side and just slowly drops Android/mobile platform? In Roadmap 2018 there is nothing new about mobile platform.

i heavily doubt that.
I guess the reason is more because Qt runs more or less stable on Android. There are no bigger features which need to be implemented, mostly bug fixing.

What is your move Qt team on new app store rules in developer console: minimal platform-26 in August 2018 and 64-bit apk in 2019? Some new changes in build and deploy area?

i asked this at the beginning of the year, but unfortunately haven't received an answer.

@noone Would this be of any help to you? https://forum.qt.io/topic/79730/no-build-step-for-android

It seems this guy had the same problem and solved it with adding gradle.

Usually that error has to do with missing ndk/sdk or the more likely ant/gradle. Try running the build or deploy on the command line and see if it gives you more information.

Then it's strange, OAuth is the third protocol in the list of the Apereo CAS Implementation part of the article you linked.

If found the way by myself, if this can help to someone, is a question of attaching the texture again and change it before the fbo generation.

Like:
```
glBindTexture(GL_TEXTURE_2D, d->fbo->texture());
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); // Linear Filtering
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); // Linear Filtering

Hi,

AFAIK, no. Modifying system settings like that is something that is outside of Qt's scope (I don't meant you can't do it using Qt but it has no direct support for that).

Hi @tansgumus ,

Apple is very conservative in allowing developers long term background threats/events.

Taken from the Apple docu:

Implementing Long-Running Background Tasks For tasks that require more execution time to implement, you must request specific permissions to run them in the background without their being suspended. In iOS, only specific app types are allowed to run in the background: Apps that play audible content to the user while in the background, such as a music player app Apps that keep users informed of their location at all times, such as a navigation app Apps that support Voice over Internet Protocol (VoIP) Newsstand apps that need to download and process new content Apps that receive regular update from external accessories Apps that implement these services must declare the services they support and use system frameworks to implement the relevant aspects of those services. Declaring the services lets the system know which services you use, but in some cases it is the system frameworks that actually prevent your application from being suspended.

That said, a navigation app should fall in this category. But as it is, you're bound to do it in OBjective-C but its relative easy to include ObjectiveC code in Qt.

I solved it for now by using a size relative to its parent and calculating a scale from it. Also applying the same scale to the position of the Pathview gives a usable solution, but it requires a few additional calculations.
I see how the (617 * 411) resolution occurs.
So the Windows width: and height: properties are not sizes in pixels..

Desktop - 1920*1200 or 2560x1440
density 4.2969047380546925
pixelRatio 1

Mobile
density 6.5092731829573935 - 1620 x 1080
pixelRatio 2.626672502927989

1620/2.6266... gives 617
1080/2.6266... gives 411

Hi,

No it's not. Your application becomes a library loaded by Android's runtime which requires a small amount of Java but you are writing and using C++. You can access Android's Java functionalities through JNI if needed.