Android app doesn't run
-
@ekkescorner that's a great page. I'm using 6.5.3; do you think your suggestions will work with this version?
@mzimmers will be similar, but not the same. per ex. the Qt FileProvider only exists in 6.6+
-
@JKSH thanks for the warning about the manifest editor -- it looks like TQC has painted itself into a corner on this one.
I was going to try your suggestion, but now I have a different problem: my Android device shows as "disconnected" and I can't figure out what to do about this.
@mzimmers said in Android app doesn't run:
my Android device shows as "disconnected"
connected via wifi or via usb cable ?
-
@JKSH thanks for the warning about the manifest editor -- it looks like TQC has painted itself into a corner on this one.
I was going to try your suggestion, but now I have a different problem: my Android device shows as "disconnected" and I can't figure out what to do about this.
-
@mzimmers said in Android app doesn't run:
my Android device shows as "disconnected"
connected via wifi or via usb cable ?
wrote on 5 Jan 2024, 15:50 last edited by@ekkescorner USB cable. I deleted that device, and am trying to create a new one, but it keeps trying to make an emulator, not a "real" Android device.
-
@ekkescorner USB cable. I deleted that device, and am trying to create a new one, but it keeps trying to make an emulator, not a "real" Android device.
@mzimmers creating devices is for emulators. to connect via USB see https://t1p.de/ekkeManageDevices
-
@mzimmers Click Manage Kits->Devices
select your device in Device combobox since your device may not be the default one.
Then click Debug above Run button and select your connected device.wrote on 5 Jan 2024, 15:56 last edited by@JoeCFD interesting -- I thought I had deleted that device, but it still shows up (and appears to be selected):
I'm not sure what you are referring to with "Debug above Run button." I'm only trying to build a release version. -
@mzimmers creating devices is for emulators. to connect via USB see https://t1p.de/ekkeManageDevices
wrote on 5 Jan 2024, 15:58 last edited by@ekkescorner oh, OK. I didn't realize that.
So...any idea why my device is showing as disconnected?
-
@ekkescorner oh, OK. I didn't realize that.
So...any idea why my device is showing as disconnected?
wrote on 5 Jan 2024, 15:59 last edited by JoeCFD 1 May 2024, 16:03@mzimmers click Devices and show the tabs. I am debugging my app for Android now and have debug build. If you are building release, then it is Release above Run button on the lower left corner of Qt Creator.
-
@mzimmers click Devices and show the tabs. I am debugging my app for Android now and have debug build. If you are building release, then it is Release above Run button on the lower left corner of Qt Creator.
-
@mzimmers is this device correct? Click the down arrow and you can see more.
If yes, check if the cable is on. I had this issue this morning. The cable was off. -
@JoeCFD it's the same device that worked for me last year. And it's indeed connected (I think it would have to be if it's auto-detected).
wrote on 5 Jan 2024, 16:20 last edited by JoeCFD 1 May 2024, 16:21@mzimmers Go to your computer and click this device to see if you are able to browse inside this device. For example, copy a file from this device to your computer. If yes, this means the device is connected to your computer. Otherwise, it is not connected.
-
@mzimmers Go to your computer and click this device to see if you are able to browse inside this device. For example, copy a file from this device to your computer. If yes, this means the device is connected to your computer. Otherwise, it is not connected.
-
@JoeCFD tried that, and it sure appears to be connected:
I'm starting to wonder if there's something wrong with the SDK that Creator downloaded for me.wrote on 5 Jan 2024, 16:33 last edited by JoeCFD 1 May 2024, 16:35@mzimmers yes, it is connected. Click the Android tab to see if anything is not set properly. I am now working with a Galaxy Tab A as well and do not have issues. Do you need to enable debugging in your Tablet? I remember you set it.
-
@mzimmers yes, it is connected. Click the Android tab to see if anything is not set properly. I am now working with a Galaxy Tab A as well and do not have issues. Do you need to enable debugging in your Tablet? I remember you set it.
wrote on 5 Jan 2024, 16:40 last edited by@JoeCFD bingo. Now my device shows as ready to use.
Unfortunately, I'm now back to my original error:
Activity Manager threw the error: Error type 3 Error: Activity class {org.qtproject.example.weatherinfo/org.qtproject.qt.android.bindings.QtActivity} does not exist.And, to @JKSH's suggestion, this is without modifying any of the files in my android directory.
How do these settings compare with yours?
-
@JoeCFD bingo. Now my device shows as ready to use.
Unfortunately, I'm now back to my original error:
Activity Manager threw the error: Error type 3 Error: Activity class {org.qtproject.example.weatherinfo/org.qtproject.qt.android.bindings.QtActivity} does not exist.And, to @JKSH's suggestion, this is without modifying any of the files in my android directory.
How do these settings compare with yours?
-
@mzimmers I have JDK 11 and yours is 17. 17 is for Android 14. I do not think Galaxy has 14 now. Check the Android version in your tablet. Mine is 13.
-
@JoeCFD mine appears to be 11.
When I change my JDK to 11, I get the following errors:
Do I need to dig up an earlier version of the SDK now? The Android Studio download page seems to have only the latest versions. -
@JoeCFD mine appears to be 11.
When I change my JDK to 11, I get the following errors:
Do I need to dig up an earlier version of the SDK now? The Android Studio download page seems to have only the latest versions.@mzimmers said in Android app doesn't run:
Do I need to dig up an earlier version of the SDK now?
That's a bit tricky:
- The Latest version of the SDK Command-Line tools (v11+) requires JDK 17 now. In contrast, v10 of the Tools can work with JDK 11.
- Qt Creator expects you to use the SDK Manager to install the "Latest" version of the tools. So if you've upgrade those tools, you're expected to use JDK 17 too.
And, to @JKSH's suggestion, this is without modifying any of the files in my android directory.
Hmm... that's weird. Sorry, I don't know if it's related to JDK 17 or not. (I haven't upgraded so I'm still using JDK 11 + SDK Command-Line Tools v10)
36/87