Need help from an S3 user who can capture logcat output - Galaxy S III Q&A, Help & Troubleshooting

So the Samsung Clock is force closing when passing it an alarm intent from NFC Task Launcher. I need someone with an S3 to capture that logcat output and send it to me so I can see if I can fix it. Any takers?
Edit:
I made a quick APK, no NFC tag needed - anyone can test this, I just need the logcat output. The following APK should make the S3 clock app crash when it's run (in theory). I need to know why (logcat output would be really helpful).
APK in the 4th post
http://forum.xda-developers.com/showpost.php?p=27742575&postcount=4

---

Anybody I can create a quick APK to simulate this if anyone wants to do it but lacks NFC tags.

---

I have S3 and have NFC tags...if you tell me EXACTLY what to do, I will help.
ANDREW

---

adchesney said:
I have S3 and have NFC tags...if you tell me EXACTLY what to do, I will help.
ANDREW
Click to expand...
Click to collapse
I made a quick APK, no NFC tag needed - anyone can test this, I just need the logcat output. The following APK should make the S3 clock app crash when it's run (in theory). I need to know why (logcat output would be really helpful).
In case you are curious about nefarious activities, here's the code:
Code:
public class ClockTestActivity extends Activity {
@Override
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
}
public void setAlarm(View v)
{
Intent intent = new Intent();
intent.setAction(AlarmClock.ACTION_SET_ALARM);
intent.putExtra(AlarmClock.EXTRA_HOUR, 3);
intent.putExtra(AlarmClock.EXTRA_MINUTES, 25);
intent.putExtra(AlarmClock.EXTRA_SKIP_UI, true);
startActivity(intent);
}
}
Edit: Capturing logcat output:
If you have ADB set up you can merely plug the device in and issue:
adb shell logcat > debug.log
This will dump all output to this file. Run the app, hit OK on the crash. Break the dump (ctrl-c) and send the log file.
If you don't have ADB set up you can use something like aLogcat (https://play.google.com/store/apps/details?id=org.jtb.alogcat). Install and start that. Same as above, run the application and let the clock app crash. Go back into aLogcat and send the log (can reach me at gmail, krohnjw) or attach it here.

---

Email sent with attachment...I hope I've done it right.
ANDREW

---

adchesney said:
Email sent with attachment...I hope I've done it right.
ANDREW
Click to expand...
Click to collapse
You did, thank you. Now to see if I can get it sorted out. If anyone is curious here's the exception that's causing some perfectly valid code to crash on this device.
Code:
E/AndroidRuntime( 4529): FATAL EXCEPTION: main
E/AndroidRuntime( 4529): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.alarm.HandleSetAlarm}: java.lang.NullPointerException
E/AndroidRuntime( 4529): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1970)
E/AndroidRuntime( 4529): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1995)
E/AndroidRuntime( 4529): at android.app.ActivityThread.access$600(ActivityThread.java:128)
E/AndroidRuntime( 4529): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1161)
E/AndroidRuntime( 4529): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4529): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 4529): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 4529): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4529): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 4529): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:993)
E/AndroidRuntime( 4529): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:760)
E/AndroidRuntime( 4529): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4529): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 4529): at com.sec.android.app.clockpackage.alarm.HandleSetAlarm.onCreate(HandleSetAlarm.java:54)
E/AndroidRuntime( 4529): at android.app.Activity.performCreate(Activity.java:4562)
E/AndroidRuntime( 4529): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1053)
E/AndroidRuntime( 4529): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1934)

---

krohnjw said:
You did, thank you. Now to see if I can get it sorted out. If anyone is curious here's the exception that's causing some perfectly valid code to crash on this device.
Code:
E/AndroidRuntime( 4529): FATAL EXCEPTION: main
E/AndroidRuntime( 4529): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.sec.android.app.clockpackage/com.sec.android.app.clockpackage.alarm.HandleSetAlarm}: java.lang.NullPointerException
E/AndroidRuntime( 4529): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1970)
E/AndroidRuntime( 4529): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1995)
E/AndroidRuntime( 4529): at android.app.ActivityThread.access$600(ActivityThread.java:128)
E/AndroidRuntime( 4529): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1161)
E/AndroidRuntime( 4529): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 4529): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 4529): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 4529): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 4529): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 4529): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:993)
E/AndroidRuntime( 4529): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:760)
E/AndroidRuntime( 4529): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4529): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 4529): at com.sec.android.app.clockpackage.alarm.HandleSetAlarm.onCreate(HandleSetAlarm.java:54)
E/AndroidRuntime( 4529): at android.app.Activity.performCreate(Activity.java:4562)
E/AndroidRuntime( 4529): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1053)
E/AndroidRuntime( 4529): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1934)
Click to expand...
Click to collapse
Hey krohnjw! Were you able to figure out the issue and a work around? I also have an app that sends an alarm intent and I'm hearing issues from users with Samsung devices (it works perfectly on all other devices) and I can't really pinpoint the issue (I only have a Galaxy Tab 10.1). One user told me that he has a Galaxy Note With ICS 4.0.4 (Touchwiz) and one person wrote a review saying that the app was being funky on his GSIII with the preinstalled alarm app anddd I got a ANR report from a GT-I9100M (which after a quick Google search shows that it's a GSII) . This is pretty confusing and a bit frustrating since I don't have the issue right in front of me. Hopefully you can shine some light on this issue :/

---

Game4set said:
Hey krohnjw! Were you able to figure out the issue and a work around? I also have an app that sends an alarm intent and I'm hearing issues from users with Samsung devices (it works perfectly on all other devices) and I can't really pinpoint the issue (I only have a Galaxy Tab 10.1). One user told me that he has a Galaxy Note With ICS 4.0.4 (Touchwiz) and one person wrote a review saying that the app was being funky on his GSIII with the preinstalled alarm app anddd I got a ANR report from a GT-I9100M (which after a quick Google search shows that it's a GSII) . This is pretty confusing and a bit frustrating since I don't have the issue right in front of me. Hopefully you can shine some light on this issue :/
Click to expand...
Click to collapse
yeah. Send me a pm. I'm a bit busy tonight but I can send you over the relevant info by tomorrow evening most likely.
Sent from my Nexus 7 using Tapatalk HD

---

krohnjw said:
yeah. Send me a pm. I'm a bit busy tonight but I can send you over the relevant info by tomorrow evening most likely.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
PM sent!