DalvikVm crash While starting Wifi service

by >> JJ » Tue, 30 Dec 2008 21:30:14 GMT

Sponsored Links
 i all,

Could some one help me with the below error logs.. I am running
Android on a PXA platform with a custom wifi driver. when I try to
invoke Wifi Manager from settings, the GUI crashes. I am attaching the
logs below..

Thanks in Advance..

I/ActivityManager( 713): Starting activity: Intent {

action=android.intent.action.MAIN comp=

{com.android.settings/com.android.settings.wifi.WifiSettings} }
V/WifiMonitor( 713): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 713): Changing supplicant state: INACTIVE ==>
D/SettingsWifiEnabler( 882): Received wifi state changed from
Enabling to

I/ActivityManager( 713): Displayed activity

com.android.settings/.wifi.WifiSettings: 369 ms
V/WifiMonitor( 713): Event [CTRL-EVENT-SCAN-RESULTS Ready]
D/LocationManagerService( 713): NetworkStateBroadcastReceiver: WiFi

point 1
W/dalvikvm( 713): threadid=15: thread exiting with uncaught

E/AndroidRuntime( 713): Uncaught handler: thread

exiting due to uncaught exception
E/AndroidRuntime( 713): *** EXCEPTION IN SYSTEM PROCESS. System will
E/AndroidRuntime( 713): java.lang.RuntimeException: Error receiving

Intent { action=android.net.wifi.SCAN_RESULTS } in


E/AndroidRuntime( 713): at


E/AndroidRuntime( 713): at android.os.Handler.handleCallback

E/AndroidRuntime( 713): at android.os.Handler.dispatchMessage

E/AndroidRuntime( 713): at android.os.Looper.loop(Looper.java:
E/AndroidRuntime( 713): at com.android.server.ServerThread.run

E/AndroidRuntime( 713): Caused by:

key.length > 31
E/AndroidRuntime( 713): at android.os.SystemProperties.get

E/AndroidRuntime( 713): at


E/AndroidRuntime( 713): at


E/AndroidRuntime( 713): at


E/AndroidRuntime( 713): at


E/AndroidRuntime( 713): ... 4 more
I/Process ( 713): Sending signal. PID: 713 SIG: 9
I/ServiceManager( 652): service 'SurfaceFlinger' died
I/ActivityThread( 863): Removing dead content provider: settings
I/ActivityThread( 781): Removing dead content provider: settings
I/ActivityThread( 773): Removing dead content provider: settings
I/ServiceManager( 652): service 'power' died
I/ServiceManager( 652): service 'telephony.registry' died
I/ServiceManager( 652): service 'package' died
I/ServiceManager( 652): service 'activity' died
I/ServiceManager( 652): service 'batteryinfo' died
I/ServiceManager( 652): service 'meminfo' died
I/ServiceManager( 652): service 'content' died

Other Threads

1. on text input, AVD unexpectedly displays logograms (perhaps hanzi)

On some of the AVDs I've created, input text gets displayed as
logograms, even in the emulated Browser application (see the screen
shot at http://eduneer.com/screenshot_avd_text.png).  Has anyone else
experienced this or have a tip on fixing it?

OS: Vista
Eclipse version: 3.5.2
JDK version:



2. Touch Event flood

I just coded up a simple performance for a project of mine and found
that the touch event flood problem is back in town albeit with a new
face. Here's a simple test case which:

<pre lang="Java">
package com.badlogic.gdx;

import javax.microedition.khronos.egl.EGLConfig;
import javax.microedition.khronos.opengles.GL10;

import android.app.Activity;
import android.opengl.GLSurfaceView;
import android.opengl.GLSurfaceView.Renderer;
import android.os.Bundle;
import android.util.Log;
import android.view.Window;
import android.view.WindowManager;

public class LagTest extends Activity implements Renderer
        public void onCreate( Bundle bundle )
                super.onCreate( bundle );
WindowManager.LayoutParams.FLAG_FULLSCREEN );
                GLSurfaceView view = new GLSurfaceView( this );
                view.setRenderer( this );
                setContentView( view );

        long startTime = 0;
        int frames;

        public void onDrawFrame(GL10 gl)
                if( System.nanoTime() - startTime > 1000000000 )
                        Log.d( "Lag Test", "fps: " + frames );
                        startTime = System.nanoTime();
                        frames = 0;

        public void onSurfaceChanged(GL10 gl, int width, int height) {
                // TODO Auto-generated method stub


        public void onSurfaceCreated(GL10 gl, EGLConfig config)
                startTime = System.nanoTime();
                frames = 0;

What this does is simply setting up a GLSurfaceView and output the
frames per second each second. If you watch your LogCat output while
touching the screen and dragging your finger you'll see the fps
counter go crazy. On my Droid with Android 2.0.1 it changes between 55
frames and 59 frames. As soon as i lift the finger it's back to 60
frames per second. Setting an OnTouchListener and sleeping in the
onTouch method does not solve the problem. Can anyone confirm this?


3. Problem with viewflipper animations and drawing cache

4. layout-land with onConfigurationChanged

5. PendingIntents in Notifications

6. New Market Concept

7. Proper way to update remote views in notifications?