Randomly closing app - Input Manager -

by Genc » Wed, 07 Jul 2010 06:40:50 GMT


Sponsored Links
 Hi all,

I've a very simple app, similar to fingerpaint application. I'm
drawing some lines on the screen with my finger.

My problem is that, app closes itself randomly, taking me back to
Android home screen.

Only log I can see on LogCat is that line:

(Warning) Tag: InputManagerService: Got RemoteException sending
setActive(false) notification to pid 4962 uid 10077.

No exception is thrown.

I've tried compiling project against Android 2.0, 2.1 and 2.2...

I've tried disabling debuggable attribute in manifest.

I'm having this problem on both Nexus One and 2.2 Emulator.

Any help is appreciated.

Thanks in advance.

--



Randomly closing app - Input Manager -

by TreKing » Fri, 09 Jul 2010 00:26:04 GMT


 




These are the worst issues. I would throw a ton of logging in there every
step of the way and see how far you get before you it craps out. Then add
more detailed logging around the point that it fails. Rinse and repeat until
you come to some conclusion.

-------------------------------------------------------------------------------------------------
TreKing - Chicago transit tracking app for Android-powered devices
 http://sites.google.com/site/rezmobileapps/treking 

--


Sponsored Links


Randomly closing app - Input Manager -

by Genc » Thu, 15 Jul 2010 05:06:21 GMT


 Hi TreKing,

Thanks for interest. I've sorted it out:

The problem that I was drawing on canvas from within 2 different
threads.

I was playing around Android's FingerPaint.java SDK sample and it's
accessing canvas within onTouchEvent. However I was also using my
SurfaceView and drawing on Canvas within my animation thread.

Removing canvas access from within onTouchEvent(main app thread)
solved the problem.

Thanks again.

Kind regards.








--



Other Threads

1. [Camera API] Programmatically Update Flash Setting (or any Camera.Parameters)

I'm trying to avoid having to rewrite the Android source for the
native camera app (as it is a cluster***k of code), but am curious as
to the proper, most efficient away of being able to update the Camera
Parameters AFTER the SurfaceView of the Camera has been created and
"opened".

For example, if you have a button that toggles the setting of On, Off,
or Auto for the Flash, this initial parameter value is set when the
Camera is initialized (let's say Auto by default, if, of course, the
device supports it).  If you want to switch it to Off, WHILE the
current view is the instance of the Camera/SurfaceView, you press the
button and it "sets" the new parameter to the camera to "OFF";
however, the CURRENT instance of the camera does not update it's
camera settings, meaning if you take the picture the Auto flash
setting is still enabled.

Now, if you say launch a new Activity, like a Preferences screen, and
then go back to the Camera view, the camera now has the "OFF"
setting.  This clearly has to do with the surfaceChanged() method as
it is grabbing the NEW camera parameters and updating the camera
settings to reflect that.

In a nutshell, I'm wondering if there is a way inside to update the
CURRENT instance of the Camera and what a preferred approach would be.

Thanks!

-- 

2. How to vertically center text inside TabWidget tabs?

How can I make the text in each tab within my TabWidget vertically
centered.

-- 

3. adb_usb.ini documentation?

4. The apk must be signed with the same certificates as the previous version.

5. Creating an image programmatically

6. Some comment spam squashed?

7. [wta] setelah di inject knp masih sinyal 1x??