Develop Reference

Android Emulator ISO?

I am trying to setup a testing environment for the development of java apps.
I do not have any dedicated server right now and I am using one KVM VPS to write a code and on another one I am running Android x86 8.1 RC2 in Debug Mode to catch the contents of /data/log.txt. Everything works nice and smooth.
Yet right now I need to test the app on Android 9.0 Pie. There is no ISO images of Android x86-pie yet, only sources. So I wonder if I should try to build myself Android x86 9.0 from the sources or there is another option..?
(I tried to install Bliss OS, but failed: https://forum.xda-developers.com/showpost.php?p=80086490&postcount=1070 )
So apparently there is Android Emulator available: https://androidstudio.googleblog.com/2019/08/emulator-29110-canary-android-q-beta-6.html but it requires /dev/kvm (which means that I probably should run it on dedicated server?).
How this emulator works? Is it possible to make an ISO image and install it on VPS?
Edit:
This is the Android 28 system image that sdkmanager provides:
I wonder if it is possible to convert this one into ISO for installation on VPS.
Edit2:
Tried Android x86 9.0.0 r34... It doesn't work yet.
https://github.com/android-x86/android-x86.github.io/issues/52#issuecomment-524590033

how to ask qt create apk package for android without start a simulator

The android simulator is very slow, I don't want to debug with a simulator. I just want the qt create the APK file, and copy it to real hardware, and test.
But seems there is NO option to let qt just create the APK file.
I use qt5.1.0 in windows 7 64bit
Can anyone there know how to do it?

The android simulator is slow because most android device is arm architecture. You can use android sdk create a X86 avd(or use genymotion) and compile your qt project in X86 android mode. It will make test and run extremely fast.
Alternatively, you can build your project in command line (not in qt creator). Here is a post that will show you how to do that.

Here's a very fast alternative:
genymotion
which you can launch from eclipse and android studio as well

Running program: console of Linux kernel image (Android) vs Android APK

I'm very new with Android. Now I have a project about driver and library (C/C++) of a device on Android. I can boot the device up with Android, and also can boot it up with only the Linux kernel image in Android package.
While the library can be reuse from the same product on Linux and the driver has already configured for new board on Android, I really don't care about implementing Android application APK to test both library and driver. I also don't care about ADB connection. I just want to use the same application (console) from Linux project and rebuild it for Android by NDK for testing.
My question is that if there is any different between running a program on console (after booting only Linux kernel image) and running it on GUI of Android (in top of a bunch of Android library/framework). Everything I know up to now is to create a Android APK and use JNI to call library. I don't know if there is any chance for a code that worked well on just-kernel-image will be failed on Android-whole-system.

Breakpoints in Android Platform source

Using Intellj-idea I'm trying to debug into the Android source API 17 but when I set breakpoints in the platform source they are being ignored when run. Looking at the breakpoint whilst debugging there is a cross in it with a message stating "no executable code found at line 15,508 in class android.view"
I've tried running against an emulator with API 17 set as well as a phone with Android 4.2.2 but both don't work. I can sort of debug into the methods but the cursor jumps around.
So I'm guessing that there is no debug info as well as some optimisations that have gone on. So my question:
Is there a way I can properly debug the Android Platform from the perspective of my application and set breakpoints that work in it? Maybe a an emulator that has been been built with debug info?
Any help would be appreciated?
Regards
Lee

It depends on what application you are trying to debug: your own application, a system application such as android.process.acore.
To debug platform source running in your own application
The main issue is the line numbers of the platform source you have downloaded on your computer must match what is running on the device. Your best bet will be to debug on Google Nexus device such as the Nexus 5 or Nexus 7 since it should be running a compiled version of the source exactly as it was released by Google which you downloaded with the Android SDK. Just add the sourcepath to the sdk in IntelliJ, attach the debugger and set the breakpoint. Make sure you choose the same API level source as is running on the device. That should do it.
To debug platform source running in a system application
You will need eng build of the Android platform to debug system processes. If you haven't built and installed the Android platform before it is quite a bit of work and requires an unlocked bootloader. Maybe there are prebuilt eng builds of cyanogenmod or something that can be downloaded but I can't find any after some trivial Googling. You may also make an eng build of AOSP yourself and run the emulator on your machine. See Running emulator after building Android from source and the "Choose a target" section on the AOSP site for info on building your own eng build if you are feeling very ambitious.

apk build by corona is not install in device

I am new with corona developing.
I am creating a new project and them build as android apk target 2.2.
It will make build successfully bt if i run this build on my device it shows "not installed".
I am using trial version of corona is this make a problem?
Thanks for your valuable time.

When I had a similar problem, it was because the architecture on my device wasn't ARMv7.
The developers behind Corona have made these points regarding Android deployment:
You do not need to install the Android SDK. However, you will need to install the x86 (32-bit) version of the Java 6 Development Kit if you're using Windows. Corona does not support JDK7. See Java Development Kit Setup for details.
The Android build process generates a standard .apk file. You can build and test apps on Android devices without creating a Google developer account, but you will need an account if you wish to publish to the Google Play marketplace. The current price of the program is $25, mandated and managed by Google.
We only support Android devices that run Android 2.2 or higher with an ARMv7 processor. This can create some confusion because ARM processors are identified by both a family and an architecture. Family names do not have a "v" in them. For instance, the ARM7 processor is actually a ARMv3 architecture, and ARM11 is a ARMv6 architecture. See this guide to help identify the various processors.
Source: http://docs.coronalabs.com/guide/distribution/androidBuild/index.html (worth a read if you haven't seen it already)

Download some app to your device like app manager or Es File Explorer(
https://play.google.com/store/apps/details?id=com.estrongs.android.pop&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5lc3Ryb25ncy5hbmRyb2lkLnBvcCJd)
And open that app, select your .apk file, and there u can install it.
Good luck ;)

I find the simplest way is to just attach the .apk file to an e-mail and open the attachment in Gmail on the phone.
You can build for Android using the Trial version of Corona. Just use the default key. (I might have enabled a setting under Apps to allow installing apps from outside Google Play, I don't remember.)

I had to install my app via a adb console with my phone's USB debugging turned on for it to work.
The command was:
[path to adb.exe] install -r [path to apk file]

I've had this problem before so I will share you my experience.
It could be one of two problems:
Your device isn't ARMv7. That means it needs to be 2.2 or higher. I would recommend using Android 4.0 or higher for a test device, that's just my opinion though.
You could have a syntax error or you could be requiring a document that doesn't exist. In some rare instances Corona doesn't detect the error until it's on the device. To see what the error is, run adb logcat.
Let me know if this works for you :)