Hello everyone!
I'm having another problem with my milestone that I'd like to share
with developers and Android coders: Whenever I run memory-intensive
applications while I have an IM app running in the background, the IM
app is often killed without any user notification whatsoever.
Take this scenario for instance (works every time on my Milestone):
1. A few background apps are already running: Sipdroid, Locale,
Titanium Backup's service...
2. Launch Nimbuzz (or Fring, eBuddy or Meebo - it's reproducible on
all of them)
3. Use lots of memory - for instance with a browser (open lots of
windows will full desktop sites), or by launching multiple memory-
intensive applications at once (Maps Navigation or other navigation
apps work well)
Sure enough, the logs show the following:
06-23 17:39:44.542: INFO/ActivityManager(1286): Displayed activity
com.nimbuzz/.MainScreen: 705 ms (total 705 ms)
06-23 17:39:44.558: WARN/InputManagerService(1286): Client not active,
ignoring focus gain of: com.android.internal.view.IInputMethodClient
$stub$pr...@4514e388
06-23 17:39:45.402: WARN/KeyCharacterMap(12195): Can't open keycharmap
file
06-23 17:39:45.410: WARN/KeyCharacterMap(12195): Error loading
keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'.
hw.keyboards.65538.devname='qtouch-touchscreen'
06-23 17:39:45.410: WARN/KeyCharacterMap(12195): Using default
keymap: /system/usr/keychars/qwerty.kcm.bin
06-23 17:39:45.456: INFO/ActivityManager(1286): Starting activity:
Intent { act=android.intent.action.MAIN
cat=[android.intent.category.HOME] cmp=com.fede.launcher/.Launcher }
06-23 17:39:45.628: WARN/IInputConnectionWrapper(12195):
showStatusIcon on inactive InputConnection
06-23 17:39:47.331: INFO/ActivityManager(1286): Starting activity:
Intent { act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10000000
cmp=mobi.mgeek.TunnyBrowser/.BrowserActivity }
06-23 17:39:53.941: WARN/InputManagerService(1286): Window already
focused, ignoring focus gain of:
com.android.internal.view.iinputmethodclient$stub$pr...@44f9bbf0
06-23 17:39:55.777: WARN/webcore(13158): Can't get the viewWidth after
the first layout
06-23 17:39:58.652: WARN/InputManagerService(1286): Window already
focused, ignoring focus gain of:
com.android.internal.view.iinputmethodclient$stub$pr...@451162b0
06-23 17:40:02.886: WARN/webcore(13158): Can't get the viewWidth after
the first layout
06-23 17:40:04.277: INFO/ActivityManager(1286): Process
com.motorola.worldclock (pid 13198) has died.
06-23 17:40:04.277: INFO/ActivityManager(1286): Low Memory: No more
background processes.
06-23 17:40:51.339: INFO/ActivityManager(1286): Process com.nimbuzz
(pid 12195) has died.
06-23 17:40:51.347: WARN/ActivityManager(1286): Scheduling restart of
crashed service com.nimbuzz/.services.NimbuzzService in 5000ms
06-23 17:40:51.347: INFO/ActivityManager(1286): Low Memory: No more
background processes.
06-23 17:40:51.355: INFO/WindowManager(1286): WIN DEATH:
Window{44fad130 com.nimbuzz/com.nimbuzz.MainScreen paused=false}
06-23 17:40:51.355: INFO/WindowManager(1286): WIN DEATH:
Window{452b9728 com.nimbuzz/com.nimbuzz.InitScreen paused=false}
06-23 17:40:56.371: INFO/ActivityManager(1286): Start proc com.nimbuzz
for service com.nimbuzz/.services.NimbuzzService: pid=13215 uid=10122
gids={1006, 3003, 1015}
06-23 17:40:57.839: INFO/ActivityThread(13215): Publishing provider
com.nimbuzz.contactlistsearchprovider:
com.nimbuzz.services.ContactListSearchProvider
06-23 17:40:57.870: WARN/Service(13215): setForeground: ignoring old
API call on com.nimbuzz.services.NimbuzzService
06-23 17:41:00.097: INFO/ActivityManager(1286): Start proc
com.motorola.worldclock for broadcast
com.motorola.worldclock/.WorldClockWidgetProvider: pid=13221 uid=10029
gids={}
06-23 17:41:00.222: INFO/dalvikvm(13221): Debugger thread not active,
ignoring DDM send (t=0x41504e4d l=38)
06-23 17:41:00.245: INFO/dalvikvm(13221): Debugger thread not active,
ignoring DDM send (t=0x41504e4d l=50)
06-23 17:41:00.753: INFO/ActivityManager(1286): Process
com.motorola.worldclock (pid 13221) has died.
06-23 17:41:00.753: INFO/ActivityManager(1286): Low Memory: No more
background processes.
06-23 17:41:03.941: INFO/NotificationService(1286): enqueueToast
pkg=mobi.mgeek.TunnyBrowser callback=android.app.ITransientNotification
$stub$pr...@45260c28 duration=0
06-23 17:41:58.808: INFO/ActivityManager(1286): Starting activity:
Intent { act=android.intent.action.MAIN
cat=[android.intent.category.LAUNCHER] flg=0x10200000
cmp=com.nimbuzz/.InitScreen }
06-23 17:41:58.824: WARN/ActivityManager(1286): Activity
HistoryRecord{44ec7da0 com.nimbuzz/.MainScreen} being finished, but
not in LRU list
06-23 17:41:59.324: WARN/ActivityManager(1286): Activity pause timeout
for HistoryRecord{45345898 mobi.mgeek.TunnyBrowser/.BrowserActivity}
06-23 17:42:00.003: INFO/ActivityManager(1286): Start proc
com.motorola.worldclock for broadcast
com.motorola.worldclock/.WorldClockWidgetProvider: pid=13231 uid=10029
gids={}
06-23 17:42:00.105: INFO/ActivityManager(1286): Starting activity:
Intent { cmp=com.nimbuzz/.MainScreen (has extras) }
06-23 17:42:00.113: INFO/dalvikvm(13231): Debugger thread not active,
ignoring DDM send (t=0x41504e4d l=38)
06-23 17:42:00.113: INFO/ActivityManager(1286): Starting activity:
Intent { cmp=com.nimbuzz/.MainScreen (has extras) }
06-23 17:42:00.128: INFO/dalvikvm(13231): Debugger thread not active,
ignoring DDM send (t=0x41504e4d l=50)
06-23 17:42:00.511: INFO/ActivityManager(1286): Process
mobi.mgeek.TunnyBrowser (pid 13158) has died.
06-23 17:42:00.511: INFO/WindowManager(1286): WIN DEATH:
Window{4518ae00 TunnyStatusBar paused=false}
06-23 17:42:00.519: INFO/WindowManager(1286): WIN DEATH:
Window{4510f328 mobi.mgeek.TunnyBrowser/
mobi.mgeek.TunnyBrowser.BrowserActivity paused=false}
06-23 17:42:00.753: WARN/InputManagerService(1286): Got
RemoteException sending setActive(false) notification to pid 13158 uid
10108
06-23 17:42:00.995: INFO/ActivityManager(1286): Displayed activity
com.nimbuzz/.MainScreen: 861 ms (total 1673 ms)
As you can see, Nimbuzz's background service is killed at 17:40:51 due
to low memory. This happens without fail...
Now, my questions are:
1. Why am I, the user, not informed the the application has died, and
hence, the connection has been lost?
2. Why are all the IM apps being killed, and not my other background
apps? Sipdroid and Locale have NEVER been killed in this fashion.
What can one do, either as a user, or as the user of one of the above
IM apps, to prevent the app just being killed in the background?
Thanks in advance!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
