Note that there are some explanatory texts on larger screens.

plurals
  1. POFailed looking up window - different behaviors from same app on 2 galaxy nexus
    primarykey
    data
    text
    <p>I have two Galaxy Nexus phones. The phones are the same firmware version 4.0.2, same build number, same kernel version. When I deploy the same exact app to both of the phones using Eclipse, I see different behaviors from each.</p> <p>On one phone, everything works as expected. On the other phone, the main Activity crashes when switching to another activity and back to the main one, both by back button and by other activities finishing and returning to the activity that created it. The only clue I have to this problem is this error:</p> <pre><code>04-18 17:43:30.811: I/ActivityManager(207): Displayed org.mitre.Mobile/.Activities.QueryActivity: +430ms 04-18 17:43:30.819: I/n*.w*.w*.ZoomButtonsCo*(4962): invoke: onVisibilityChanged listener: org.osmdroid.views.MapView$MapViewZoomListener@4181ecd8 04-18 17:43:30.843: E/InputQueue-JNI(4962): channel '41d66628 Panel:org.mitre.Mobile/org.mitre.Mobile.Activities.MobileActivity (client)' ~ Publisher closed input channel or an error occurred. events=0x8 04-18 17:43:30.843: W/WindowManager(207): Force-removing child win Window{41d66628 Panel:org.mitre.Mobile/org.mitre.Mobile.Activities.MobileActivity paused=false} from container Window{420815c8 org.mitre.Mobile/org.mitre.Mobile.Activities.MobileActivity paused=false} 04-18 17:43:30.850: W/WindowManager(207): Failed looking up window 04-18 17:43:30.850: W/WindowManager(207): java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@41f9e658 does not exist 04-18 17:43:30.850: W/WindowManager(207): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7029) 04-18 17:43:30.850: W/WindowManager(207): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7020) 04-18 17:43:30.850: W/WindowManager(207): at com.android.server.wm.WindowManagerService.removeWindow(WindowManagerService.java:2180) 04-18 17:43:30.850: W/WindowManager(207): at com.android.server.wm.Session.remove(Session.java:149) 04-18 17:43:30.850: W/WindowManager(207): at android.view.IWindowSession$Stub.onTransact(IWindowSession.java:124) 04-18 17:43:30.850: W/WindowManager(207): at com.android.server.wm.Session.onTransact(Session.java:111) 04-18 17:43:30.850: W/WindowManager(207): at android.os.Binder.execTransact(Binder.java:338) 04-18 17:43:30.850: W/WindowManager(207): at dalvik.system.NativeStart.run(Native Method) </code></pre> <p>I haven't really found anything useful on the internet related to this error message. I have some experience with android, but this one has really stumped me. I initially thought this was a nova launcher problem (the phone with the problem has it), but I installed nova on the other phone and still saw the same behaviors.</p> <p>The phone with the app that doesn't work properly is my personal phone, the other is a work phone.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload