Any idea why the following code crashes the app? It happens in calculateGmt()

by Justin Anderson » Wed, 21 Apr 2010 15:53:15 GMT

Sponsored Links
 First thing I noticed right off the bat is that you aren't checking for the
case where the input can't be parsed to a double...  That throws an
exception and since you aren't handling that that would crash your app.

Second thing I noticed is that hideous @SuppressWarnings thing....  In my
opinion if you need to do that then you need to rethink what you are doing.

Last, but not least, check the logcat output when you get a crash... it will
tell you more about why it is crashing.

There are only 10 types of people in the world...
Those who know binary and those who don't.


Any idea why the following code crashes the app? It happens in calculateGmt()

by Indicator Veritatis » Thu, 22 Apr 2010 06:48:29 GMT

 I'm not seeing enough info for me to run this myself under Eclipse
DDMS and see the exception -- which is probably your best bet for
diagnosing the problem. Or, if it crashes before it waits for user
input, you should use Debug: 1) set a breakpoint by double-clicking on
the bar to the left of the line number in the Java source code editor
2) instead of doing Run As (or ctl-F11 or the corresponding tool),
launch the debugger by clicking on the tool that looks like a bug or
by doing F11 instead of ctl-F11. You can always switch back to DDMS
perspective in Eclipse after that and look in the Logcat output for
the exception.

Or, as either an alternative, or in addition to the above, you might
want to break up complicated lines like

"double val = Double.parseDouble(gmtinput.getText().toString());"

into multiple assignment statements. That will reveal where, for
example, you forgot to actually allocate memory for the result.


Sponsored Links

Any idea why the following code crashes the app? It happens in calculateGmt()

by Indicator Veritatis » Thu, 22 Apr 2010 06:57:11 GMT

 ll good points!

In particular, the OP should have told us what the warning suppressed
really was. It might have been the hint he needed to solve the
problem. Or it might have been just another attempt to suppress the
spurious warning messages from Eclipse -- which sometimes says you
need to Override a method you have already Overriden.

And just to connect a few dots: the easiest way to get to Logcat and
search the output is to switch to DDMS perspective, find the Logcat
tab, bring it to the front and maximize it. Then you can delete the
previous contents of the log and just watch the world scroll by. Or
play around with filters, though that is not necessary for this

It also helps to watch this Logcat output on a known good program run,
so that you can get used to which error message can be ignored.
Unfortunately, even for a program running perfectly OK on the
emulator, we see Java exceptions and other error messages in Logcat.

On Apr 21, 12:51am, Justin Anderson <> wrote:
> >

Other Threads

1. foe codeing

i want to developed a android apps in which any thing write on
EditText should be save textfile in my machine.


2. PreferenceScreen conflict?

I'm using a third party binary only barcode scanner by dropping
in their .jar file.  Today I was learning how to implement preferences.
I made a .xml file:


   <PreferenceCategory android:title="First Category">

....  etc ...

And I made a main menu item called Settings and was
able to start a new activity extending PreferenceActivity.
Everything went swimmingly.  I had a preferences system
working, and I could read the preferences from other activities

Then I noticed that the barcode scanning part was not working anymore.
In the logcat:

E/AndroidRuntime( 2886): java.lang.RuntimeException: Unable to start activity 
ComponentInfo{com.rcsreg.exposmart/com.rcsreg.exposmart.ScannerActivity}: android.view.InflateException: Binary XML file line #2: 
Error inflating class PreferenceScreen

E/AndroidRuntime( 2886):        at
E/AndroidRuntime( 2886):        at
E/AndroidRuntime( 2886):        at$2300(

When I remove my res/layout/preferences.xml, the barcode scanning works again.
So has the third party software locked me out from using preferences?




3. AndEngine resolution problem

4. Website Interaction

5. localhost on android

6. LG Ally app closes on load

7. Modify sign and install default apks