Hi everyone. I'm facing a connectivity problem in my IM-client for a long time already, but still can't find out how to fix it. Found a similar bug report here: http://code.google.com/p/android/issues/detail?id=2059 except PowerManager.SCREEN_DIM_WAKE_LOCK didn't work for me :(
So here is the problem: when device goes idle, wifi is being kept connected for some unpredictable time(1-20 min), but then established connection brakes and here is what i see on the ddms console: 06-22 14:19:30.398: VERBOSE/WifiMonitor(53): Event [CTRL-EVENT- DISCONNECTED - Disconnect event - remove keys] 06-22 14:19:30.398: VERBOSE/WifiStateTracker(53): New network state is DISCONNECTED 06-22 14:19:30.408: VERBOSE/WifiMonitor(53): Event [CTRL-EVENT-STATE- CHANGE id=2 state=0] 06-22 14:19:30.408: VERBOSE/WifiStateTracker(53): Changing supplicant state: COMPLETED ==> DISCONNECTED 06-22 14:19:30.500: VERBOSE/WifiMonitor(53): Event [CTRL-EVENT-STATE- CHANGE id=2 state=2] 06-22 14:19:30.508: VERBOSE/WifiStateTracker(53): Changing supplicant state: DISCONNECTED ==> SCANNING 06-22 14:19:30.518: VERBOSE/WifiMonitor(53): Event [Trying to associate with 00:19:5b:66:13:06 (SSID='shape' freq=2437 MHz)] 06-22 14:19:30.518: VERBOSE/WifiMonitor(53): Event [CTRL-EVENT-STATE- CHANGE id=2 state=3] 06-22 14:19:30.548: VERBOSE/WifiStateTracker(53): Changing supplicant state: SCANNING ==> ASSOCIATING 06-22 14:19:31.408: VERBOSE/WifiMonitor(53): Event [CTRL-EVENT-STATE- CHANGE id=2 state=4] 06-22 14:19:31.408: VERBOSE/WifiStateTracker(53): Changing supplicant state: ASSOCIATING ==> ASSOCIATED 06-22 14:19:31.418: VERBOSE/WifiMonitor(53): Event [Associated with 00:19:5b:66:13:06] 06-22 14:19:31.418: VERBOSE/WifiMonitor(53): Event [CTRL-EVENT-STATE- CHANGE id=2 state=7] 06-22 14:19:31.418: VERBOSE/WifiStateTracker(53): Changing supplicant state: ASSOCIATED ==> COMPLETED 06-22 14:19:31.428: VERBOSE/WifiMonitor(53): Event [CTRL-EVENT- CONNECTED - Connection to 00:19:5b:66:13:06 completed (reauth) [id=2 id_str=]] 06-22 14:19:31.428: VERBOSE/WifiStateTracker(53): New network state is CONNECTED and "-1" is coming on read() from input stream or SocketException is raised. Then my app is trying to reconnect and sometimes it's successful almost immediately, but sometimes it takes more than 2-3 tries to reconnect(WifiMonitor logs reconnects again and again) with 10 seconds timeout. Preventing some advices - yes, there is a PARTIAL_WAKE_LOCK and wifilock held by my app, but as i can see this is not enough. 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
