Is it possible to debug a native Android application with eclipse and the Android SDK. I have downloaded the sources. Would I have to build the app and then deploy it onto the device to debug it (like any other debugging process)? If so, how would I go about doing that (can use messenger/call app if needed).
You can debug native android applications using eclipse and ndk-gdb. The detailed information you can find here
Related
How can I deploy Oracle-MAF in Android Studio?
I googled it a lot, but without avail. The only way I have found seems hard. Is there something easier?
Follow the steps .
Steps
Install android studio and create a new project (this is to enable emulator)
In jDeveloper Preference select Mobile Application Framework, select `Android platform.
Set Android SDK Location, Android Platform Location, Android Build Tools Location.
Generate Keystore entries.
Create one Deployment profile for Android (You can debug in simulator or run within your device).
Run/ Debug the application
There's an option in the Android project settings in the Android Options section on the Packaging tab that lets you choose between the Xamarin debugger or the Microsoft debugger. The Xamarin debugger works, but not as good as the Microsoft one might. Unfortunately I get an error message when trying to use the Microsoft debugger and deploy on one of the Visual Studio Android Emulators.
Unable to start debugging. Non-debuggable application installed on the target device. Required file '/data/data/My.Application/lib/gdbserver' could not be found on the device. Please install a debuggable version.
Is there any way to get the Microsoft debugger to work?
The Xamarin debugger can only debug managed (i.e. C#) code. Breakpoints only work with the Xamarin debugger if the project being debugged is a managed project. They don't work if the project is a native app or native library.
The Microsoft debugger can only debug native (i.e. C/C++) code. Breakpoints only work with the Microsoft debugger if the project being debugged is a native app or native library, or if it is attached to an already-running Android process.
To get gdbserver into the app package, you either have to reference a native code library from your managed app, or include it (with build action set to AndroidNativeLibrary). I found you can also add a link to gdbserver (again, with build action set to AndroidNativeLibrary) from a project and make use of path sniffing to select the gdbserver from the matching ABI. Snippet of project file:
<ItemGroup>
<AndroidNativeLibrary Include="$(ANDROID_NDK_ROOT)\prebuilt\android-arm\gdbserver\gdbserver">
<Link>lib\armeabi-v7a\gdbserver</Link>
</AndroidNativeLibrary>
</ItemGroup>
Also please see my answer to a similar question.
I updated my SDK tools and SDK platform tools to the latest and to my horror found that AppEngine Connected Android project's emulator not launching if I do Debug as > Local AppEngine connected Android Project.
I am working on a project and also have done quite a lot of work using this plugin option. Is there a way that I can still develop. Maybe someway I could start the AppEngine Seperately and Android Project Separately and still they would work( debugging as remote AppEngine is not a problem).
To what I have read, I think they doing it because they are deprecating C2DM messaging. And instead they bringing the option of Make AppEngine Backends. But unfortunately they have still not worked on the docs or support.
Is there any way I can still keep working till they release the docs or how can I make the transition myself?
Here is how I debug localy since the sdk update:
Debug the app engine project as Web Application
Run the AVD with the manager
Debug the android project as Android Application
Remotely:
Run the AVD with the manager
Run the android project as Android Application
Hope this helps.
Edit:
After debugging remotely it seems that the AVD still speaks to the remote server eventhough you wipe out data and ask for "Debug android project". In this case do a "Debbug as local app engine connected android application". This will start the local server but not the Android app. Then Debug the android project as Android Application and it will talk to the local server.
I have a reasonably large Qt project which I don't want to rewrite in Java for Android. So I downloaded and installed Necessitas SDK and managed to compile the project as an apk file.
So far so good. It also executed successfully in emulator, but then I got stuck. First problem was that Necessitas Qt Creator always produces a "Debug" apk file, even though I set the project config to "Release". The second problem, it allows me to deploy the app to emulator only, but I want to install and test it on a real Android device.
How can I find and copy the necessary Qt libraries manually to the device?
Install Ministro from the Market to get the Qt libraries. Your app will dialog with Ministro to get the needed libraries from the net. See the How to write Qt apps for Android guides for more information.
Necessitas is still alpha, so the libraries are indeed debug ones (to get debug messages), but stripped of the symbols.
I want to deliver a finished and working Titanium App to Android customers. But I can't find any documentation about how to produce something like a jar-file that I can create to directly install it on Android devices without the Android market or the Titanium IDE at hand (I can't expect my users to install Titanium IDE first, right).
When you do a build for device in titanium studio, titanium studio creates an apk file for you.
You can find this at Titanium Workspace/Your Project/Build/Android/bin/app.apk. This is the app file you want.
This file can be e-mailed to your customers, and if the android phone is set to accept apps from 3rd party locations, they can install it through this e-mail.
See the Appcelerator Wiki:
https://wiki.appcelerator.org/display/guides/Deploying+to+Android+devices
and
https://wiki.appcelerator.org/display/guides/Distributing+Android+apps