• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Apps LogCat Errors

Hi, hopefully this is the right, else please move me... cheers!


I'm running an app i'm developing and am getting some errors in logcat.

Can anyone please show me where to find specific error code lists, etc... (so I don't have to ask first!)

Here are the first set (non sound issues)

Code:
E( 2087* 2087) Dispatching key KeyEvent{action=0 code=4 repeat=0 meta=0 scancode=158 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (enter ViewRoot)
E( 2087* 2087) Sending key event to IME: seq=1 event=KeyEvent{action=0 code=4 repeat=0 meta=0 scancode=158 mFlags=8}  (ViewRoot)
E( 2087* 2087) Dispatching key KeyEvent{action=0 code=4 repeat=0 meta=0 scancode=158 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (exit ViewRoot)
E( 2087* 2102) rececive IME message viewRoot = Handler{2feb5dc0}  (ViewRoot)
E( 2087* 2087) IME finished event: seq=1 handled=false event=KeyEvent{action=0 code=4 repeat=0 meta=0 scancode=158 mFlags=8}  (ViewRoot)
E( 2087* 2087) Dispatching key KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (enter ViewRoot)
E( 2087* 2087) Sending key event to IME: seq=2 event=KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8}  (ViewRoot)
E( 2087* 2087) Dispatching key KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8} to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (exit ViewRoot)
E( 2087* 2104) rececive IME message viewRoot = Handler{2feb5dc0}  (ViewRoot)
E( 2087* 2087) IME finished event: seq=2 handled=false event=KeyEvent{action=1 code=4 repeat=0 meta=0 scancode=158 mFlags=8}  (ViewRoot)
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88 touchevent action is 0 X= 226.54366 Y=483.63242  (ViewRoot enter )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (ViewRoot exit )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88 touchevent action is 2 X= 226.03053 Y=484.14856  (ViewRoot enter )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (ViewRoot exit )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88 touchevent action is 2 X= 227.05678 Y=486.47125  (ViewRoot enter )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (ViewRoot exit )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88 touchevent action is 2 X= 229.36583 Y=492.40698  (ViewRoot enter )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (ViewRoot exit )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88 touchevent action is 1 X= 229.36583 Y=492.40698  (ViewRoot enter )
E( 2087* 2087) Dispatching touchevent to com.android.internal.policy.impl.PhoneWindow$DecorView@2feb0e88  (ViewRoot exit )

Tell me about a single one or the the lot. I set it to only record Warnings and above. But on some searches people say some of these aren't even errors... so???


Many thanks!
 
None of those lines looks like errors to me.

To view your errors in Eclipse, click on Window->Show View->Error Log, and/or Window->Show View->Problems.

I hope this helped.
~ Danial ~

Errors shown in that view are compilation errors. That's not what he wants. He wants runtime errors. He is doing it correctly, however he doesn't seem to be pasting his entire logcat output, as none of the lines he has posted are error lines.

EDIT: Or rather, they are system-level errors that can be ignored by the developer as they are handled by the system automatically. What you need to be watching for are uncaught exceptions, such as NullPointerException, or IllegalStateException, etc... These are application-level errors and ones that you need to fix.
 
  • Like
Reactions: bigchibi
Upvote 0
Hi, sorry for taking so long to get back, unexpected holiday :D

Yes I was running a logCat app on the actual phone. I'd also applied a filter just to get this apps process id, and only captured warnings and errors.

A couple of times i've had crashes and the audio has continued playing, which I find a bad user experience because you have to restart (I did anyway) your phone to get rid.


I'm happy if those errors are not really my fault. I can research them more leisurely now...



Here's the actual app: Mars Invaders
It won't have any ads for another week or so (depending on available free time). Any feedback would be greatly appreciated.

Thanks for all help ;)
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones