Does Application Error Reports support crashes in native code?

by Shri » Fri, 20 May 2011 02:15:51 GMT

Sponsored Links
 Does the Application Error Reports infrastructure described at 
work for crashes in native code?

It sounds like the mechanism works by using
Thread.setDefaultUnhandledExceptionHandler which only works for Java
code, and so it will not work for native code. Are there any solutions
for native code? I am working on registering a signal handler which
starts a separate process (since crashes in native code can leave the
process in a bad state) to get the logcat logs and then send those.
Just wondering if there is any better solution.


Other Threads

1. Not able to write to /storage

I have an application with the following manifest settings:

     android:sharedUserId="android.uid.system" >

Within this application, I am attempting to "tar" some bunch of test
files and write it out to "/storage" on the device. This fails for "/
storage", though works for "/data".

Any hints?



2. onNewIntent() is never called when use Icons


What I'm trying to do was supposed to be very simple, but is not
working. :)
I would like to have 2 Icons that will call my activity, that is the
only one in the package.
But, when the activity is called, I would like to know which of these
Icons was used.
In the logs, I'm able to see that the Intent sent asap after press the
icon is sending this message like:
I(  569:0x23d) Starting activity: Intent
{ action=android.intent.action.MAIN categories=
{android.intent.category.LAUNCHER} flags=0x10200000 comp={teste.teste/
teste.teste.alias1} }

But, my override of onNewIntent is never called and the onResume is
receiving a modified version of the Intent:
D(  896:0x380) Intent is Intent { action=android.intent.action.MAIN
categories={android.intent.category.LAUNCHER} flags=0x10200000 comp=
{teste.teste/teste.teste.mainapp} }

As you can see, the alias1 packagename was modified to mainapp. And
because of this, I'm unable to check which button was applied.

My code in the manifest file is simple:
 <application  android:icon="@drawable/icon"  android:label="@string/
app_name" android:debuggable="true"  >
            <activity android:name=".mainapp" android:label="@string/
app_name" android:configChanges="orientation"
android:name="android.intent.action.MAIN" />
                <activity-alias android:name="alias1" android:label="alias1"
android:icon="@drawable/icon" android:targetActivity=".mainapp"
android:launchMode="singleTop" >
android:name="android.intent.action.MAIN" />
android:name="android.intent.category.LAUNCHER" />
                <activity-alias android:name="alias2" android:label="alias2"
android:icon="@drawable/icon" android:targetActivity=".mainapp"
android:name="android.intent.action.MAIN" />
android:name="android.intent.category.LAUNCHER" />
                <receiver android:name=".BootMainapp">
android:name="android.intent.action.BOOT_COMPLETED" />
android:name="android.intent.category.HOME" />

As you can see, I'm using the singleTop definition, as a requirement
for onNewIntent call.

Any ideas what could be wrong here? Or, How can I have a way to check
which Icon was used to call my Acitivity?

Thank you,
Joao Sauer


3. Rotational forces doesn't work if the Activity is behind another Dialog-themed Activity

4. Debugging on HTC Tattoo

5. Rotational forces doesn't work if the Activity is behind another Dialog-themed Activity

6. how to know whether a resource is compressed or not?

7. Gallery stays dim??