[Monodroid] App crashing on Droid X device
Sham Singh
sham.singh at gmail.com
Thu Mar 3 02:17:23 EST 2011
I'm able to debug a simple single button app on my Droid 2 device, however,
when trying the same on my Droid X the app starts then crashes. My app is
called MonoDroidPew and here is the device log:
03-02 23:00:21.020 2700 2700 D dalvikvm: GC_EXPLICIT freed 157 objects /
9592 bytes in 86ms
03-02 23:00:45.934 2557 2565 V DeviceStorageMonitorService:
freeMemory=6723633152
03-02 23:00:45.934 2557 2565 V DeviceStorageMonitorService: Threshold
Percentage=10
03-02 23:00:45.934 2557 2565 V DeviceStorageMonitorService: mTotalMemory =
70843269
03-02 23:00:45.934 2557 2565 I DeviceStorageMonitorService: Posting
Message again
03-02 23:00:49.536 2557 2580 D KeyguardViewMediator:
wakeWhenReadyLocked(3)
03-02 23:00:49.543 2557 2581 D KeyguardViewMediator:
handleWakeWhenReady(3)
03-02 23:00:49.543 2557 2581 D KeyguardViewManager: wakeWhenReady(3)
03-02 23:00:49.543 2557 2581 D KeyguardViewMediator: pokeWakelock(10000)
03-02 23:00:49.543 2557 2581 I power : *** set_screen_state 1
03-02 23:00:49.543 2557 2581 D Sensors : using sensors (name=sensors)
03-02 23:00:49.543 2557 2581 D SensorService: android_open numFds = 1
03-02 23:00:49.543 2557 2581 D SensorService: android_open fd = 0x49c14b64
pfd = 0x49c14b60
03-02 23:00:49.653 2557 2581 D KeyguardViewManager: onScreenTurnedOn()
03-02 23:00:49.715 2557 2565 D WifiService: ACTION_SCREEN_ON -- Checked by
Moto
03-02 23:00:49.723 3149 3149 W WidgetAidService: BroadcastReceiver
onReceive called
03-02 23:00:49.723 3149 3149 D WidgetAidService:
ACTION_HOME_SCREEN_CHANGED - 3
03-02 23:00:49.746 2644 2644 D PowerProfileSvc: Receiver: Screen On
03-02 23:00:49.746 2644 2644 D PowerProfileSvc: Start: Received action:
android.intent.action.batteryprofile.SCR_ON
03-02 23:00:49.746 2644 2644 D PowerProfileSvc: Algo:Run: current state
--> 0
03-02 23:00:49.746 2644 2644 D PowerProfileDispCtrl: noteCap: 90,true,0
03-02 23:00:49.746 2644 2644 D PowerProfileSvc: Algo:Run: new state is -->
0
03-02 23:00:49.754 3149 3149 D WidgetAidService: HomeScreen gained
focus/panned
03-02 23:00:49.778 3149 3149 D WidgetAidService: widgetScreenIndex - 5
03-02 23:00:49.973 2557 2564 D SurfaceFlinger: Screen about to return,
flinger = 0x123ee0
03-02 23:00:50.240 2557 2612 D Sensors : accelerometer gesture: 0x84020000
03-02 23:00:50.567 2557 2581 D dalvikvm: GC_EXTERNAL_ALLOC freed 14510
objects / 740328 bytes in 91ms
03-02 23:00:50.582 2557 2581 D KeyguardViewMediator: pokeWakelock(10000)
03-02 23:00:50.721 2557 2612 D Sensors : accelerometer gesture: 0x08020000
03-02 23:00:50.981 2557 2581 D MotorolaSettingsProvider: property:
sys.mot_settings_secure_version=481
03-02 23:00:50.981 2557 2581 D MotorolaSettingsProvider: insert notifying
for
content://com.motorola.android.providers.settings/settings/lock_pin_current_failed_attempts
03-02 23:00:51.020 2557 2581 D KeyguardViewManager: hide()
03-02 23:00:51.028 2694 2694 D UsbService: onReceive(), received
intent:android.intent.action.USER_PRESENT
03-02 23:00:51.043 2557 2690 W InputManagerService: Window already
focused, ignoring focus gain of:
com.android.internal.view.IInputMethodClient$Stub$Proxy at 45c5b778
03-02 23:00:51.528 3846 3846 V MediaPlaybackService: onUnbind start
03-02 23:00:51.528 3846 3846 V MediaPlaybackService: saveQueue begin
03-02 23:00:51.528 3846 3846 V MediaPlaybackService: saveQueue end
03-02 23:00:51.528 3846 3846 V MediaPlaybackService: mNumberOfBinds:0
03-02 23:00:51.528 3846 3846 V MediaPlaybackService: onUnbind end
03-02 23:00:51.535 3846 3846 V MediaPlaybackService: MultiPlayer onRelease
start
03-02 23:00:51.535 3846 3846 V MediaPlaybackService: mMultiPlayer stop
03-02 23:00:51.535 3846 3846 V MediaPlaybackService: mMultiPlayer stop end
03-02 23:00:51.535 3846 3846 V MediaPlaybackService: MultiPlayer onRelease
end
03-02 23:00:51.535 2557 2655 I AudioService: AudioFocus
abandonAudioFocus() from
android.media.AudioManager at 45925788com.android.music.MediaPlaybackService
$3 at 4592c160
03-02 23:00:51.551 3846 3846 V MediaPlaybackService: onDestroy end
03-02 23:00:57.121 4199 4199 D AndroidRuntime:
03-02 23:00:57.121 4199 4199 D AndroidRuntime: >>>>>>>>>>>>>>
AndroidRuntime START <<<<<<<<<<<<<<
03-02 23:00:57.121 4199 4199 D AndroidRuntime: CheckJNI is OFF
03-02 23:00:57.121 4199 4199 D dalvikvm: creating instr width table
03-02 23:00:57.160 4199 4199 D AndroidRuntime: --- registering native
functions ---
03-02 23:00:57.223 4199 4199 D GestureManager:
register_com_motorola_android_hardware_GestureManager
03-02 23:00:57.746 4199 4199 D AndroidRuntime: Shutting down VM
03-02 23:00:57.746 4199 4202 D jdwp : adbd disconnected
03-02 23:00:57.754 4199 4206 I AndroidRuntime: NOTE: attach of thread
'Binder Thread #3' failed
03-02 23:00:58.473 4212 4212 D AndroidRuntime:
03-02 23:00:58.473 4212 4212 D AndroidRuntime: >>>>>>>>>>>>>>
AndroidRuntime START <<<<<<<<<<<<<<
03-02 23:00:58.473 4212 4212 D AndroidRuntime: CheckJNI is OFF
03-02 23:00:58.473 4212 4212 D dalvikvm: creating instr width table
03-02 23:00:58.512 4212 4212 D AndroidRuntime: --- registering native
functions ---
03-02 23:00:58.582 4212 4212 D GestureManager:
register_com_motorola_android_hardware_GestureManager
03-02 23:00:58.692 2557 2690 I ActivityManager: Starting activity: Intent
{ act=android.intent.action.MAIN flg=0x10000000
cmp=MonoDroidPew.MonoDroidPew/monodroidpew.Activity1 }
03-02 23:00:58.723 3149 3149 W WidgetAidService: BroadcastReceiver
onReceive called
03-02 23:00:58.723 3149 3149 D WidgetAidService:
ACTION_HOME_SCREEN_CHANGED - -1
03-02 23:00:58.731 2557 2693 I ActivityManager: Start proc
MonoDroidPew.MonoDroidPew for activity
MonoDroidPew.MonoDroidPew/monodroidpew.Activity1: pid=4219 uid=10113
gids={3003, 1015}
03-02 23:00:58.754 4212 4212 D AndroidRuntime: Shutting down VM
03-02 23:00:58.754 4212 4215 D jdwp : adbd disconnected
03-02 23:00:58.770 3149 3149 D WidgetAidService: HomeScreen has lost
focus, store the previous state and move to pause
03-02 23:00:58.801 3149 3149 D WidgetAidService: Ignoring the
HOME_SCREEN_CHANGED notification as the player is either in paused/playing
state
03-02 23:00:58.817 4219 4219 I ActivityThread: Publishing provider
MonoDroidPew.MonoDroidPew.__mono_init__: mono.MonoRuntimeProvider
03-02 23:00:58.840 4219 4219 D dalvikvm: Trying to load lib
/data/data/MonoDroidPew.MonoDroidPew/lib/libmonodroid.so 0x45830b78
03-02 23:00:58.840 4219 4219 D dalvikvm: Added shared lib
/data/data/MonoDroidPew.MonoDroidPew/lib/libmonodroid.so 0x45830b78
03-02 23:00:58.856 4219 4219 I MonoDroid-Debugger: Trying to initialize
the debugger with options: --debugger-agent=transport=dt_socket,address=
192.168.1.106:61745,embedding=1
03-02 23:01:00.864 4219 4219 I MonoDroid-Debugger: Error connecting stdout
and stderr (192.168.1.106:61746)
03-02 23:01:00.864 32297 32297 I DEBUG : *** *** *** *** *** *** *** ***
*** *** *** *** *** *** *** ***
03-02 23:01:00.864 32297 32297 I DEBUG : Build fingerprint:
'verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys,release-keys'
03-02 23:01:00.864 32297 32297 I DEBUG : pid: 4219, tid: 4219 >>>
MonoDroidPew.MonoDroidPew <<<
03-02 23:01:00.864 32297 32297 I DEBUG : signal 11 (SIGSEGV), fault addr
deadbaad
03-02 23:01:00.864 32297 32297 I DEBUG : r0 00000000 r1 afd14679 r2
00000027 r3 00000070
03-02 23:01:00.864 32297 32297 I DEBUG : r4 afd42328 r5 00000000 r6
00000000 r7 41e86c64
03-02 23:01:00.864 32297 32297 I DEBUG : r8 bec16490 r9 41e86c4c 10
41e86c38 fp bec16454
03-02 23:01:00.864 32297 32297 I DEBUG : ip 00001770 sp bec163a8 lr
deadbaad pc afd11cd0 cpsr 60000070
03-02 23:01:00.864 32297 32297 I DEBUG : d0 6472656767756265 d1
64747320676e6931
03-02 23:01:00.864 32297 32297 I DEBUG : d2 20646e6120747537 d3
2820727265647434
03-02 23:01:00.864 32297 32297 I DEBUG : d4 737365726464612c d5
3836312e3239313d
03-02 23:01:00.864 32297 32297 I DEBUG : d6 363a3630312e312e d7
626d652c35343731
03-02 23:01:00.864 32297 32297 I DEBUG : d8 0000000000000000 d9
0000000000000000
03-02 23:01:00.864 32297 32297 I DEBUG : d10 0000000000000000 d11
0000000000000000
03-02 23:01:00.864 32297 32297 I DEBUG : d12 0000000000000000 d13
0000000000000000
03-02 23:01:00.864 32297 32297 I DEBUG : d14 0000000000000000 d15
0000000000000000
03-02 23:01:00.864 32297 32297 I DEBUG : d16 aca156c0458384d0 d17
3fe999999999999a
03-02 23:01:00.864 32297 32297 I DEBUG : d18 42eccefa43de3400 d19
3fe00000000000b4
03-02 23:01:00.864 32297 32297 I DEBUG : d20 4008000000000000 d21
3fd99a27ad32ddf5
03-02 23:01:00.864 32297 32297 I DEBUG : d22 3fd24998d6307188 d23
3fcc7288e957b53b
03-02 23:01:00.864 32297 32297 I DEBUG : d24 3fc74721cad6b0ed d25
3fc39a09d078c69f
03-02 23:01:00.864 32297 32297 I DEBUG : d26 0000000000000000 d27
0000000000000000
03-02 23:01:00.864 32297 32297 I DEBUG : d28 0000000000000000 d29
0000000000000000
03-02 23:01:00.864 32297 32297 I DEBUG : d30 0000000000000000 d31
0000000000000000
03-02 23:01:00.864 32297 32297 I DEBUG : scr 80000012
03-02 23:01:00.864 32297 32297 I DEBUG :
03-02 23:01:00.910 32297 32297 I DEBUG : #00 pc 00011cd0
/system/lib/libc.so
03-02 23:01:00.910 32297 32297 I DEBUG : #01 lr deadbaad
<unknown>
03-02 23:01:00.910 32297 32297 I DEBUG :
03-02 23:01:00.910 32297 32297 I DEBUG : code around pc:
03-02 23:01:00.910 32297 32297 I DEBUG : afd11cb0 2d00682d e029d1fb
b12b68db c05cf8df
03-02 23:01:00.910 32297 32297 I DEBUG : afd11cc0 f8442001 4798000c
e054f8df 26002227
03-02 23:01:00.910 32297 32297 I DEBUG : afd11cd0 2000f88e eee4f7fb
f7fd2106 f04fe802
03-02 23:01:00.910 32297 32297 I DEBUG : afd11ce0 91035180 460aa901
96012006 f7fc9602
03-02 23:01:00.910 32297 32297 I DEBUG : afd11cf0 a905eb88 20024632
eb92f7fc eed0f7fb
03-02 23:01:00.910 32297 32297 I DEBUG :
03-02 23:01:00.910 32297 32297 I DEBUG : code around lr:
03-02 23:01:00.910 32297 32297 I DEBUG : deadba8c ffffffff ffffffff
ffffffff ffffffff
03-02 23:01:00.910 32297 32297 I DEBUG : deadba9c ffffffff ffffffff
ffffffff ffffffff
03-02 23:01:00.918 32297 32297 I DEBUG : deadbaac ffffffff ffffffff
ffffffff ffffffff
03-02 23:01:00.918 32297 32297 I DEBUG : deadbabc ffffffff ffffffff
ffffffff ffffffff
03-02 23:01:00.918 32297 32297 I DEBUG : deadbacc ffffffff ffffffff
ffffffff ffffffff
03-02 23:01:00.918 32297 32297 I DEBUG :
03-02 23:01:00.918 32297 32297 I DEBUG : stack:
03-02 23:01:00.918 32297 32297 I DEBUG : bec16368 00000015
03-02 23:01:00.918 32297 32297 I DEBUG : bec1636c afd146a9
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec16370 afd425a0
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec16374 afd4254c
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec16378 00000000
03-02 23:01:00.918 32297 32297 I DEBUG : bec1637c afd156c3
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec16380 afd14679
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec16384 afd14679
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec16388 00000070
03-02 23:01:00.918 32297 32297 I DEBUG : bec1638c afd42328
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec16390 00000000
03-02 23:01:00.918 32297 32297 I DEBUG : bec16394 bec163bc [stack]
03-02 23:01:00.918 32297 32297 I DEBUG : bec16398 41e86c64
03-02 23:01:00.918 32297 32297 I DEBUG : bec1639c afd1491b
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec163a0 df002777
03-02 23:01:00.918 32297 32297 I DEBUG : bec163a4 e3a070ad
03-02 23:01:00.918 32297 32297 I DEBUG : #00 bec163a8 00000000
03-02 23:01:00.918 32297 32297 I DEBUG : bec163ac 9dc09e90
03-02 23:01:00.918 32297 32297 I DEBUG : bec163b0 00000802
03-02 23:01:00.918 32297 32297 I DEBUG : bec163b4 bec164b0 [stack]
03-02 23:01:00.918 32297 32297 I DEBUG : bec163b8 00000000
03-02 23:01:00.918 32297 32297 I DEBUG : bec163bc fffffbdf
03-02 23:01:00.918 32297 32297 I DEBUG : bec163c0 bec164b0 [stack]
03-02 23:01:00.918 32297 32297 I DEBUG : bec163c4 00000000
03-02 23:01:00.918 32297 32297 I DEBUG : bec163c8 458384d0
/dev/ashmem/mspace/dalvik-heap/2 (deleted)
03-02 23:01:00.918 32297 32297 I DEBUG : bec163cc 81004830
/data/data/MonoDroidPew.MonoDroidPew/lib/libmonodroid.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec163d0 0000f132 [heap]
03-02 23:01:00.918 32297 32297 I DEBUG : bec163d4 458384d0
/dev/ashmem/mspace/dalvik-heap/2 (deleted)
03-02 23:01:00.918 32297 32297 I DEBUG : bec163d8 41e86c64
03-02 23:01:00.918 32297 32297 I DEBUG : bec163dc afd0cda5
/system/lib/libc.so
03-02 23:01:00.918 32297 32297 I DEBUG : bec163e0 458382c8
/dev/ashmem/mspace/dalvik-heap/2 (deleted)
03-02 23:01:00.918 32297 32297 I DEBUG : bec163e4 002354b0 [heap]
03-02 23:01:00.918 32297 32297 I DEBUG : bec163e8 45836138
/dev/ashmem/mspace/dalvik-heap/2 (deleted)
03-02 23:01:00.918 32297 32297 I DEBUG : bec163ec 0000ab08 [heap]
03-02 23:01:01.418 2557 2572 I BootReceiver: Copying
/data/tombstones/tombstone_04 to DropBox (SYSTEM_TOMBSTONE)
03-02 23:01:01.426 2557 2557 I ActivityManager: Process
MonoDroidPew.MonoDroidPew (pid 4219) has died.
03-02 23:01:01.457 2545 2545 D Zygote : Process 4219 terminated by signal
(11)
03-02 23:01:01.457 2557 2561 W InputManagerService: Window already
focused, ignoring focus gain of:
com.android.internal.view.IInputMethodClient$Stub$Proxy at 45b9d820
03-02 23:01:01.465 2557 2557 I UsageStats: Unexpected resume of
com.motorola.blur.home while already resumed in MonoDroidPew.MonoDroidPew
03-02 23:01:01.543 3149 3149 W WidgetAidService: BroadcastReceiver
onReceive called
03-02 23:01:01.543 3149 3149 D WidgetAidService:
ACTION_HOME_SCREEN_CHANGED - 3
03-02 23:01:01.543 3149 3149 D WidgetAidService: HomeScreen gained
focus/panned
03-02 23:01:01.559 3149 3149 D WidgetAidService: widgetScreenIndex - 5
On Wed, Mar 2, 2011 at 5:21 PM, <monodroid-request at lists.ximian.com> wrote:
> Send Monodroid mailing list submissions to
> monodroid at lists.ximian.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.ximian.com/mailman/listinfo/monodroid
> or, via email, send a message with subject or body 'help' to
> monodroid-request at lists.ximian.com
>
> You can reach the person managing the list at
> monodroid-owner at lists.ximian.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Monodroid digest..."
>
>
> Today's Topics:
>
> 1. Re: New build error, unable to build (Paul Camacho)
> 2. Re: Slow and unreliable device debugging (Aaron Knabb)
> 3. Re: New build error, unable to build (Chris Erickson)
> 4. Re: New build error, unable to build (Jonathan Pryor)
> 5. Re: New build error, unable to build (Paul Camacho)
> 6. Re: Preview 13 Hotfix Released (Stefan Wywior)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 2 Mar 2011 23:16:22 +0100
> From: Paul Camacho <paul.camacho at gmx.de>
> Subject: Re: [Monodroid] New build error, unable to build
> To: "monodroid at lists.ximian.com" <monodroid at lists.ximian.com>
> Message-ID: <D84F0571-97FE-4E63-A764-6069410851A2 at gmx.de>
> Content-Type: text/plain; charset=us-ascii
>
> Is this from Cut and Paste or are you missing the closing bracket on the
> <TextView tag?
>
>
>
> Am 02.03.2011 um 22:56 schrieb Chris Erickson <chris at cartopac.com>:
>
> > That was it, although I think the syntax should be legal. Here it is:
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <LinearLayout
> > android:layout_width="fill_parent"
> > android:layout_height="fill_parent"
> > android:orientation="vertical"
> > xmlns:android="http://schemas.android.com/apk/res/android"
> > xmlns:binding="
> http://schemas.android.com/apk/res/com.cartopac.android.bind
> > ing"
> >>
> > <TextView
> > android:id="@+id/textDisplay"
> > android:layout_width="fill_parent"
> > android:layout_height="40px"
> > android:background="#ffffff"
> > android:text="TextView"
> > android:padding="5dip"
> > binding:text="TextDisplayBinding"
> >>
> > </TextView>
> >
> >
> >
> >
> > Note the binding namespace addition.
> >
> > Ideas on what could be causing this?
> >
> >
> >
> >
> > On 3/2/11 2:47 PM, "Paul Camacho" <paul.camacho at gmx.de> wrote:
> >
> >> Did you modify any XML files in the resource/layout folder since your
> >> last successful build? If so, go back and double check the syntax.
> >>
> >>
> >>
> >> Am 02.03.2011 um 22:41 schrieb Chris Erickson <chris at cartopac.com>:
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 2 Mar 2011 16:43:48 -0700
> From: Aaron Knabb <aknabb at mobileepiphany.com>
> Subject: Re: [Monodroid] Slow and unreliable device debugging
> To: Amir Waldman <amirw2k at gmail.com>
> Cc: monodroid at lists.ximian.com
> Message-ID:
> <AANLkTi=9u8GtWjBmMW_Xa=CBdL87X2PRLYUz5AxN8pXD at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Are you certain that you are running 2.2? I was having significant problems
> with my galaxy s with 2.1. As mentioned in previous previews (
> http://monodroid.net/Releases/Previews/Preview_8), there is a problem with
> Samsung's release of 2.1. I suppose it's also possible that this problem
> persists to 2.2.
>
> -Aaron
>
> On Wed, Mar 2, 2011 at 2:57 PM, Amir Waldman <amirw2k at gmail.com> wrote:
>
> > Just switched wi-fi on the device to always on and tried the ping -t ,
> but
> > it's the same... I timed it to almost 2 minutes (!) for each and every
> step
> > that I debug (I wait 2 minutes every time I click F10)
> >
> > * *
> >
> > I'm debugging a class library, maybe it has something to do with the
> > extreme slowness. Seems like no one else has this kind of delays.
> >
> >
> >
> > Using Preview 13, VS 2010, powerful computer, Samsung Galaxy S with
> Android
> > 2.2
> >
> >
> >
> > Any suggestions why it's so slow?
> >
> >
> >
> >
> >
> > Thanks,
> >
> > Amir
> >
> >
> >
> > *From:* Aaron Knabb [mailto:aknabb at mobileepiphany.com]
> > *Sent:* Wednesday, March 02, 2011 7:08 PM
> >
> > *To:* monodroid at lists.ximian.com
> > *Cc:* Amir Waldman
> >
> > *Subject:* Re: [Monodroid] Slow and unreliable device debugging
> >
> >
> >
> > If you are seeing delays that large, your wifi on the device may be
> > automatically turning off. There is a device setting to avoid this,
> however
> > it didn't seem to work on one of my Motorolas. So, I do a ping -t to
> > constantly ping my device and keep the wifi awake.
> >
> >
> >
> > Hope that helps,
> >
> > -Aaron
> >
> > On Wed, Mar 2, 2011 at 6:48 AM, Amir Waldman <amirw2k at gmail.com> wrote:
> >
> > Any tips for making it go faster? Delays can sometimes be 1-2minutes per
> > step...
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Thanks,
> >
> > Amir
> >
> >
> >
> > *From:* monodroid-bounces at lists.ximian.com [mailto:
> > monodroid-bounces at lists.ximian.com] *On Behalf Of *Aaron Knabb
> > *Sent:* Thursday, February 10, 2011 5:39 PM
> > *To:* monodroid at lists.ximian.com
> > *Subject:* Re: [Monodroid] Slow and unreliable device debugging
> >
> >
> >
> > I see incredibly slow and unreliable debugging as well (device and emu).
> > That and the debugging in a library bug are the only two things that
> greatly
> > concern me with monodroid so far. Everything else seems to work really
> well.
> >
> >
> >
> > -Aaron
> >
> > On Wed, Feb 9, 2011 at 9:58 PM, Nikolai Sander <nikolai at eodsoft.com>
> > wrote:
> >
> > Is it just me or is MonoDroid for Mac impossible to use when debugging on
> a
> > device?
> >
> > I have a Nexus One and startup takes at least a minute if not more.
> > Observing variables is incredibly slow (it'll just say "Evaluating..."
> > forever).
> >
> > 4 out of 5 times its doesn't even run but fails with
> >
> > System.IO.IOException: DWP Handshake failed.
> > at Mono.Debugger.Soft.Connection.Connect () [0x00000] in <filename
> > unknown>:0
> > at Mono.Debugger.Soft.VirtualMachine.connect () [0x00000] in <filename
> > unknown>:0
> > at Mono.Debugger.Soft.VirtualMachineManager.ConnectInternal
> > (System.Net.Sockets.Socket dbg_sock, System.Net.Sockets.Socket con_sock,
> > System.Net.IPEndPoint dbg_ep, System.Net.IPEndPoint con_ep) [0x00000] in
> > <filename unknown>:0
> >
> > The way it works right now the system is impossible to use, leave alone
> > getting any work done. Very frustrating.
> >
> > Am I missing something or do others have similar issues?
> >
> > Thanks!
> > Nikolai
> > _______________________________________________
> > Monodroid mailing list
> > Monodroid at lists.ximian.com
> >
> > UNSUBSCRIBE INFORMATION:
> > http://lists.ximian.com/mailman/listinfo/monodroid
> >
> >
> >
> >
> > _______________________________________________
> > Monodroid mailing list
> > Monodroid at lists.ximian.com
> >
> > UNSUBSCRIBE INFORMATION:
> > http://lists.ximian.com/mailman/listinfo/monodroid
> >
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.ximian.com/mailman/private/monodroid/attachments/20110302/ae1cfad1/attachment-0001.html
>
> ------------------------------
>
> Message: 3
> Date: Wed, 2 Mar 2011 18:52:20 -0500
> From: Chris Erickson <chris at cartopac.com>
> Subject: Re: [Monodroid] New build error, unable to build
> To: "monodroid at lists.ximian.com" <monodroid at lists.ximian.com>
> Message-ID: <C994262B.1639D%cerickson at cartopac.com>
> Content-Type: text/plain; charset="us-ascii"
>
> It is a portion of the xml. It isn't an open/close tag problem. It is
> the elements with the binding: namespace that cause the problem.
>
>
>
> On 3/2/11 3:16 PM, "Paul Camacho" <paul.camacho at gmx.de> wrote:
>
> >Is this from Cut and Paste or are you missing the closing bracket on the
> ><TextView tag?
> >
> >
> >
> >Am 02.03.2011 um 22:56 schrieb Chris Erickson <chris at cartopac.com>:
> >
> >> That was it, although I think the syntax should be legal. Here it is:
> >>
> >> <?xml version="1.0" encoding="utf-8"?>
> >> <LinearLayout
> >> android:layout_width="fill_parent"
> >> android:layout_height="fill_parent"
> >> android:orientation="vertical"
> >> xmlns:android="http://schemas.android.com/apk/res/android"
> >>
> >>xmlns:binding="
> http://schemas.android.com/apk/res/com.cartopac.android.bi
> >>nd
> >> ing"
> >>>
> >> <TextView
> >> android:id="@+id/textDisplay"
> >> android:layout_width="fill_parent"
> >> android:layout_height="40px"
> >> android:background="#ffffff"
> >> android:text="TextView"
> >> android:padding="5dip"
> >> binding:text="TextDisplayBinding"
> >>>
> >> </TextView>
> >>
> >>
> >>
> >>
> >> Note the binding namespace addition.
> >>
> >> Ideas on what could be causing this?
> >>
> >>
> >>
> >>
> >> On 3/2/11 2:47 PM, "Paul Camacho" <paul.camacho at gmx.de> wrote:
> >>
> >>> Did you modify any XML files in the resource/layout folder since your
> >>> last successful build? If so, go back and double check the syntax.
> >>>
> >>>
> >>>
> >>> Am 02.03.2011 um 22:41 schrieb Chris Erickson <chris at cartopac.com>:
> >_______________________________________________
> >Monodroid mailing list
> >Monodroid at lists.ximian.com
> >
> >UNSUBSCRIBE INFORMATION:
> >http://lists.ximian.com/mailman/listinfo/monodroid
>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 2 Mar 2011 19:21:09 -0500
> From: Jonathan Pryor <jpryor at novell.com>
> Subject: Re: [Monodroid] New build error, unable to build
> To: monodroid at lists.ximian.com
> Message-ID: <713D16FB-D121-4D03-A69F-240127CF39DE at novell.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Mar 2, 2011, at 4:41 PM, Chris Erickson wrote:
> > I'm unable to build again, with an unhelpful error. Can anybody add any
> insight?
>
> What, the following isn't clear enough: ;-)
>
> >
> /Users/chriserickson/Projects/MultiTargetSampleIOS/MultiTargetSampleMonoDroid/obj/Debug/res/layout/main.axml:9:
> error: No resource identifier found for attribute 'text' in package
> 'com.cartopac.android.binding'
>
> As per your later email, you have:
>
> <LinearLayout ...
> xmlns:binding="
> http://schemas.android.com/apk/res/com.cartopac.android.binding"
> >
> <TextView ...
> binding:text="TextDisplayBinding"
> ...
>
> The problem is that `aapt` doesn't like this. At all.
>
> Doing the same thing (custom xmlns declaration + binding:text attribute)
> within Eclipse results in the same error.
>
> However, one thing that stood out to me was:
>
> xmlns:binding="
> http://schemas.android.com/apk/res/com.cartopac.android.binding"
>
> This didn't strike me as being "kosher," as you're sticking your own custom
> string after someone elses TLD. Don't do that.
>
> In fact:
>
>
> http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=tools/aapt/XMLNode.cpp;h=c0d74275a8a6a6883fedeed008ab6e993e4658cc;hb=HEAD#l49
>
> If an XML namespace starts with RESOURCES_PREFIX, aka
> RESOURCES_ROOT_NAMESPACE, aka "http://schemas.android.com/apk/res/", then
> `aapt` considers the namespace to be "public" and treats it specially, which
> is your actual problem.
>
> Consequently, if I change the above xml namespace declaration to:
>
> xmlns:binding="http://com.cartopac.android.binding"
>
> then `aapt` builds the Eclipse project fine, so I believe the actual
> problem is that you chose a terrible xml namespace ID.
>
> - Jon
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 3 Mar 2011 01:33:56 +0100
> From: Paul Camacho <paul.camacho at gmx.de>
> Subject: Re: [Monodroid] New build error, unable to build
> To: "monodroid at lists.ximian.com" <monodroid at lists.ximian.com>
> Message-ID: <A3EEBF60-43E3-4EBF-9C26-6883E7A774F0 at gmx.de>
> Content-Type: text/plain; charset=us-ascii
>
> Aaaaaahhhhhhh. Thanks Jon, and sorry Chris - I should of noticed that. I
> must of had my head up my 'aapt'.
>
>
>
> Am 03.03.2011 um 01:21 schrieb Jonathan Pryor <jpryor at novell.com>:
>
> > On Mar 2, 2011, at 4:41 PM, Chris Erickson wrote:
> >> I'm unable to build again, with an unhelpful error. Can anybody add any
> insight?
> >
> > What, the following isn't clear enough: ;-)
> >
> >>
> /Users/chriserickson/Projects/MultiTargetSampleIOS/MultiTargetSampleMonoDroid/obj/Debug/res/layout/main.axml:9:
> error: No resource identifier found for attribute 'text' in package
> 'com.cartopac.android.binding'
> >
> > As per your later email, you have:
> >
> > <LinearLayout ...
> > xmlns:binding="
> http://schemas.android.com/apk/res/com.cartopac.android.binding"
> > >
> > <TextView ...
> > binding:text="TextDisplayBinding"
> > ...
> >
> > The problem is that `aapt` doesn't like this. At all.
> >
> > Doing the same thing (custom xmlns declaration + binding:text attribute)
> within Eclipse results in the same error.
> >
> > However, one thing that stood out to me was:
> >
> > xmlns:binding="
> http://schemas.android.com/apk/res/com.cartopac.android.binding"
> >
> > This didn't strike me as being "kosher," as you're sticking your own
> custom string after someone elses TLD. Don't do that.
> >
> > In fact:
> >
> >
> http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=tools/aapt/XMLNode.cpp;h=c0d74275a8a6a6883fedeed008ab6e993e4658cc;hb=HEAD#l49
> >
> > If an XML namespace starts with RESOURCES_PREFIX, aka
> RESOURCES_ROOT_NAMESPACE, aka "http://schemas.android.com/apk/res/", then
> `aapt` considers the namespace to be "public" and treats it specially, which
> is your actual problem.
> >
> > Consequently, if I change the above xml namespace declaration to:
> >
> > xmlns:binding="http://com.cartopac.android.binding"
> >
> > then `aapt` builds the Eclipse project fine, so I believe the actual
> problem is that you chose a terrible xml namespace ID.
> >
> > - Jon
> >
> > _______________________________________________
> > Monodroid mailing list
> > Monodroid at lists.ximian.com
> >
> > UNSUBSCRIBE INFORMATION:
> > http://lists.ximian.com/mailman/listinfo/monodroid
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 03 Mar 2011 02:21:31 +0100
> From: Stefan Wywior <stefan.wywior at hs-furtwangen.de>
> Subject: Re: [Monodroid] Preview 13 Hotfix Released
> To: monodroid at lists.ximian.com
> Message-ID: <f5e90c44-7073-4e36-b658-7c709dc54556 at email.android.com>
> Content-Type: text/plain; charset=UTF-8
>
> Thanks for the really fast hotfix, everything is working fine now
>
>
> ------------------------------
>
> _______________________________________________
> Monodroid mailing list
> Monodroid at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodroid
>
>
> End of Monodroid Digest, Vol 8, Issue 14
> ****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/mailman/private/monodroid/attachments/20110302/7ff99ca7/attachment-0001.html
More information about the Monodroid
mailing list