I am also facing similar problem;
Device: Galaxy S3, Samsung Rugby, Samsung skyrocket
Scenario: Random; while navigating from one activity to other.
08-01 14:04:34.122: E/InputTransport(6669): channel '42eb8978
xx.xx.xx.xx/com.xxx.XXActivity (client)' consumer ~ Error -1 pinning ashmem fd
Hi,
Thank you for your reply. I want to know how I avoid problem? I check
the log, in the previous run program has occurred
E/InputDispatcher( 83): channel '406f6928 com.android.test/
com.android.test.test1 (server)' ~ Consumer closed input channel or an
error occurred. events=0x8
Even I have the same issue... Please help...
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
What is the problem? The log messages don't necessarily indicate a problem.
Is there an actual problem you are seeing in your app?
On Wed, May 25, 2011 at 5:43 AM, wang svnzk...@gmail.com wrote:
Hi,
Thank you for your reply. I want to know how I avoid problem? I check
the log, in the
Hi,
This is the main log, it can occurred black screen, click back button
don't have response, only click home button can leave.
E/InputTransport( 83): ashmem fd is 0 in publishInputEvent.
E/InputTransport( 83): result is -1 in publishInputEvent.
E/InputTransport( 83): channel '4063c3b8
Those are two completely different things. The first is just messages in
the log, usually a result of various things cleaning up after a process goes
away. A second is an application crash, because it is trying to use a
surface that is no longer valid.
On Wed, May 25, 2011 at 7:41 PM, wang
this is the next Log
05-20 16:43:57.714 I/WindowManager( 102): WINDOW DIED Window{40540858
com.android.test/com.abdroid.test.Test1 paused=false}
On May 23, 11:41 am, wang svnzk...@gmail.com wrote:
Hi,
I run into many applications in the Android 2.3, but when every time I
perform to a
Your process is going away. Either it had a Dalvik crash and is now being
killed, some native code in it crashed, or it was in the background and the
OOM killer is removing it to reclaim memory.
On Sun, May 22, 2011 at 8:45 PM, wang svnzk...@gmail.com wrote:
this is the next Log
05-20
8 matches
Mail list logo
