Curious debugging problem

by MrChaz » Fri, 17 Apr 2009 01:13:09 GMT

Sponsored Links
 I'm getting a force close on a real device but I can't replicate it on
the emulator which means I can't find out why it's crashing.
For some reason the debugger never attaches when I try and debug on
the actual device.
I'm running Vista and SDK 1.1

Any and all help welcome :)

Curious debugging problem

by Al » Fri, 17 Apr 2009 02:41:25 GMT


For debugging on a real device, you have to enable it under Settings-
manifest. E.g.

<application ..... debuggable=true> ..... </application>


Sponsored Links

Curious debugging problem

by Al » Fri, 17 Apr 2009 02:42:31 GMT

 Forgot to mention, you should be able to read logcat messages from the
device. Inside Eclipse and also from terminal/command prompt: adb -d
logcat. It should give you a trace of where the crash happened and


Curious debugging problem

by MrChaz » Fri, 17 Apr 2009 16:00:53 GMT

I didn't hzve the manifest entry.



Other Threads

1. Using internal API

Is it possible to use* API in
application? I would really need to use some classes from there, since
there is no other way I can make my app answer incoming call, send dtmf
and etc.



2. clipping in ViewGroup

I have  a ViewGroup with three  children which are Views containing
bitmaps.  Two of the children are to the left and right (off screen)
and one child is in the middle of the screen and visible.  It is like
a gallery, but my own flavor.

When the user is dragging left or right, the ViewGroup tells each of
the children, scrollBy( x, 0 ).  This seems to work great for
scrolling left to right.  However, when going right to left, the left
side of the bmp gets clipped.

I have added the following code in View group, after the children have
been added, but to no effect.  Can anyone help?


3. Android Advertising Exchange

4. Implementing 'push technology' into Android apps

5. android 2-0 screenshots

6. Exception Activity Not Found

7. Intent is not properly returned through onActivityResult