Hello,
Even I am facing the same problem.My gallery application crashes when I open any of the folders.I am running it on an omap beagleboard with 2.6.29 kernel and 256 MB ram. Abukustfan, Did u find any reason why it is happening ? How can I verify if the device actually went into a low memory issue .The log clearly shows that it is killing empty process media and hence everything closes. One weird thing I have notice the media scanner results with Volume id -1 always.I thought every time it scans it results in a different id. Regards, Vishal 2009/11/27 Dianne Hackborn <[email protected]> > Okay I would guess that for some reason you have the app crashing. Please > look in the kernel log to see if the oom killer has decided to kill it; > probably not, and you need to figure out why it is crashing. (Also the > total RAM is not the most important thing -- it is the RAM available to the > kernel -- but 256MB of RAM should leave at least 100MB available to the > kernel, which is what the G1 and myTouch have.) > > 2009/11/26 abukustfan <[email protected]> > > I tried this on >> - kernel 2.6.31 and 2.6.32 >> - android-1.6_r1 >> and the RAM on my board is 256MByte. >> >> Normally, the Gallery should work as, >> (select Gallery) -> show folder -(select folder)-> show thumbnail >> but what I saw is >> (select Gallery) -> show folder -(select folder)-> show thumbnail but >> return back to show folder in a split second with previous log. >> >> I will check the kernel again. >> Thanks. >> >> >> On 11月27日, 午前4:45, Dianne Hackborn <[email protected]> wrote: >> > I don't know. I don't know what your kernel is, what version of the >> > platform you are running, how much RAM your device has, what issues you >> are >> > actually seeing in the UI (vs. stuff you are picking out of the log), or >> > really much of anything else. There's not much more I can do to help at >> > this point. >> > >> > On Thu, Nov 26, 2009 at 1:52 AM, abukustfan <[email protected]> >> wrote: >> > > I found out the following message not only print out when Gallery run >> > > but also booting. >> > > I/ActivityManager( 1647): Exiting empty application process >> > > com.android.xxx >> > > (android.os.binderpr...@xxx) >> > >> > > Does this mean the binder not working well in my kernel? >> > >> > > >> ------------------------------------------------------------------------------------------------------------- >> > > [KERNEL BOOT] >> > > <snip> >> > > D/AndroidRuntime( 1630): >>>>>>>>>>>>>> AndroidRuntime START >> > > <<<<<<<<<<<<<< >> > > <snip> >> > > I/ActivityManager( 1647): Start proc com.android.calendar for >> > > broadcast com.android.providers.calendar/.CalendarReceiver: pid=1941 >> > > uid=10009 gids={3003} >> > > I/ActivityManager( 1647): Exiting empty application process >> > > com.android.mms >> > > (android.os.binderpr...@3b378980) >> > > I/Process ( 1647): Sending signal. PID: 1794 SIG: >> > > 9 >> > > D/ActivityManager( 1647): Received spurious death notification for >> > > thread >> > > android.os.binderpr...@3b378980 >> > > D/ActivityManager( 1647): checkComponentPermission() adjusting >> > > {pid,uid} to >> > > {1631,1013} >> > > D/MediaScannerService( 1903): done scanning volume >> > > internal >> > > I/ActivityManager( 1647): Stopping service: >> > > com.android.providers.media/.MediaScannerService >> > > D/ActivityManager( 1647): checkComponentPermission() adjusting >> > > {pid,uid} to >> > > {1631,1013} >> > > D/ActivityManager( 1647): checkComponentPermission() adjusting >> > > {pid,uid} to >> > > {1631,1013} >> > > I/ActivityThread( 1941): Publishing provider calendar: >> > > com.android.providers.calendar.CalendarProvider >> > > D/ActivityManager( 1647): checkComponentPermission() adjusting >> > > {pid,uid} to >> > > {1631,1013} >> > > D/ActivityManager( 1647): checkComponentPermission() adjusting >> > > {pid,uid} to >> > > {1631,1013} >> > > E/MediaPlayerService( 1631): Couldn't open fd for >> > > content://settings/system/notification_sound >> > > E/MediaPlayer( 1647): Unable to to create media >> > > player >> > > W/NotificationService( 1647): error loading sound for >> > > content://settings/system/notification_sound >> > > W/NotificationService( 1647): java.io.IOException: setDataSource >> > > failed.: >> > > status=0x80000000 >> > > W/NotificationService( 1647): at >> > > android.media.MediaPlayer.setDataSource(Native >> > > Method) >> > > W/NotificationService( 1647): at >> > > android.media.MediaPlayer.setDataSource(MediaPlayer.java: >> > > 621) >> > > W/NotificationService( 1647): at >> android.media.AsyncPlayer$Thread.run >> > > (AsyncPlayer.java: >> > > 76) >> > > W/ActivityManager( 1647): Unable to start service Intent >> > > { act=android.accounts.IAccountsService >> > > cmp=com.google.android.googleapps/.GoogleLoginService }: not >> > > found >> > > W/AccountMonitor( 1941): Couldn't connect to Intent >> > > { act=android.accounts.IAccountsService >> > > cmp=com.google.android.googleapps/.GoogleLoginService } (Missing >> > > service?) >> > > I/ActivityManager( 1647): Exiting empty application process >> > > com.android.alarmclock >> > > (android.os.binderpr...@3b3bce08) >> > > I/Process ( 1647): Sending signal. PID: 1918 SIG: >> > > 9 >> > > D/ActivityManager( 1647): Received spurious death notification for >> > > thread >> > > android.os.binderpr...@3b3bce08 >> > > I/ActivityManager( 1647): Start proc com.android.mms for broadcast >> > > com.android.mms/.transaction.MmsSystemEventReceiver: pid=1952 >> > > uid=10014 gids={3003, 1015} >> > > I/ActivityManager( 1647): Stopping service: >> > > com.android.providers.downloads/.DownloadService >> > > I/ActivityManager( 1647): Exiting empty application process >> > > com.android.calendar >> > > (android.os.binderpr...@3b3c96b0) >> > > I/Process ( 1647): Sending signal. PID: 1941 SIG: >> > > 9 >> > > D/ActivityManager( 1647): Received spurious death notification for >> > > thread >> > > android.os.binderpr...@3b3c96b0 >> > > W/Process ( 1647): Unable to open /proc/1941/ >> > > status >> > > W/Process ( 1647): Unable to open /proc/1794/ >> > > status >> > > I/ActivityManager( 1647): Start proc com.android.calendar for >> > > broadcast com.android.calendar/.AlertReceiver: pid=1962 uid=10009 >> gids= >> > > {3003} >> > > I/ActivityThread( 1962): Publishing provider calendar: >> > > com.android.providers.calendar.CalendarProvider >> > > W/ActivityManager( 1647): Unable to start service Intent >> > > { act=android.accounts.IAccountsService >> > > cmp=com.google.android.googleapps/.GoogleLoginService }: not >> > > found >> > > W/AccountMonitor( 1962): Couldn't connect to Intent >> > > { act=android.accounts.IAccountsService >> > > cmp=com.google.android.googleapps/.GoogleLoginService } (Missing >> > > service?) >> > > D/dalvikvm( 1647): GREF has increased to >> > > 301 >> > > I/ActivityManager( 1647): Stopping service: >> > > com.android.mms/.transaction.SmsReceiverService >> > > I/ActivityManager( 1647): Exiting empty application process >> > > android.process.media >> > > (android.os.binderpr...@3b29f538) >> > > I/Process ( 1647): Sending signal. PID: 1903 SIG: >> > > 9 >> > > D/ActivityManager( 1647): Received spurious death notification for >> > > thread >> > > android.os.binderpr...@3b29f538 >> > > I/ActivityManager( 1647): Stopping service: >> > > com.android.calendar/.AlertService >> > >> > > >> ------------------------------------------------------------------------------------------------------------- >> > >> > > On 11月25日, 午後4:17, Dianne Hackborn <[email protected]> wrote: >> > > > I strongly recommend you not change those values unless you know >> what you >> > > > are doing. >> > >> > > > Look in the kernel log to see if the Android out of memory killer is >> > > killing >> > > > the process, and it should also give some indication of why. >> > >> > > > It could also just be the process crashing in native code. If it is >> > > > actually the process running the foreground activity that is going >> away, >> > > it >> > > > is 90% likely that this has nothing to do with out of memory >> killing, but >> > > a >> > > > crash. >> > >> > > > On Tue, Nov 24, 2009 at 10:16 PM, abukustfan <[email protected]> >> > > wrote: >> > > > > The Gallery UI show each folder with thumbnail properly. >> > > > > but when I touch either folder icon, it show the detail thumbnail >> but >> > > > > flash back to folder thumbnail immediately. >> > >> > > > > I changed the memory thresholds as below, >> > > > > [ro.FOREGROUND_APP_MEM]: >> > > > > [3072] >> > > > > [ro.VISIBLE_APP_MEM]: >> > > > > [4096] >> > > > > [ro.SECONDARY_SERVER_MEM]: >> > > > > [8192] >> > > > > [ro.BACKUP_APP_MEM]: >> > > > > [8192] >> > > > > [ro.HOME_APP_MEM]: >> > > > > [8192] >> > > > > [ro.HIDDEN_APP_MEM]: >> > > > > [10240] >> > > > > [ro.CONTENT_PROVIDER_MEM]: >> > > > > [11264] >> > > > > [ro.EMPTY_APP_MEM]: [12288] >> > >> > > > > and check the memory info, it seems still have a lot of MemFree >> here. >> > > > > # cat /proc/ >> > > > > meminfo >> > > > > MemTotal: 255840 >> > > > > kB >> > > > > MemFree: 145872 >> > > > > kB >> > > > > Buffers: 64 >> > > > > kB >> > > > > Cached: 49328 >> > > > > kB >> > > > > SwapCached: 0 >> > > > > kB >> > > > > Active: 42856 >> > > > > kB >> > > > > Inactive: 35984 >> > > > > kB >> > > > > Active(anon): 32740 >> > > > > kB >> > > > > Inactive(anon): 0 >> > > > > kB >> > > > > Active(file): 10116 >> > > > > kB >> > > > > Inactive(file): 35984 >> > > > > kB >> > > > > Unevictable: 0 >> > > > > kB >> > > > > Mlocked: 0 >> > > > > kB >> > > > > SwapTotal: 0 >> > > > > kB >> > > > > SwapFree: 0 >> > > > > kB >> > > > > Dirty: 0 >> > > > > kB >> > > > > Writeback: 0 >> > > > > kB >> > > > > AnonPages: 29472 >> > > > > kB >> > > > > Mapped: 29600 >> > > > > kB >> > > > > Slab: 4356 >> > > > > kB >> > > > > SReclaimable: 1768 >> > > > > kB >> > > > > SUnreclaim: 2588 >> > > > > kB >> > > > > PageTables: 1380 >> > > > > kB >> > > > > Quicklists: 76 >> > > > > kB >> > > > > NFS_Unstable: 0 >> > > > > kB >> > > > > Bounce: 0 >> > > > > kB >> > > > > WritebackTmp: 0 >> > > > > kB >> > > > > CommitLimit: 127920 >> > > > > kB >> > > > > Committed_AS: 4070336 >> > > > > kB >> > > > > VmallocTotal: 524204 >> > > > > kB >> > > > > VmallocUsed: 7344 >> > > > > kB >> > > > > VmallocChunk: 507304 kB >> > >> > > > > Any setting I miss?? >> > >> > > > > On 11月25日, 午後12:45, Dianne Hackborn <[email protected]> wrote: >> > > > > > Are you seeing something wrong in the UI? Having processes >> killed in >> > > the >> > > > > > background is normal, expected, desired behavior. It is unusual >> to >> > > have >> > > > > all >> > > > > > of the background processes killed -- this typically means there >> is >> > > not >> > > > > > enough memory to run them along with the foreground processes >> and >> > > > > services. >> > > > > > That may be normal, or not, depending on what you are doing. >> > >> > > > > > On Tue, Nov 24, 2009 at 6:38 PM, abukustfan < >> [email protected]> >> > > > > wrote: >> > > > > > > Hi all, >> > >> > > > > > > When I run Gallery application on my target board, it shows >> > > thumbnail >> > > > > > > on each folder. >> > > > > > > But when I select either folder, it shows the following >> message. >> > > > > > > (The images in SD card is four 800x600 JPEG files.) >> > >> > > > > > > Could someone help me to solve this problem? >> > >> > > >> ----------------------------------------------------------------------------------------------------------------------------- >> > > > > > > I/ActivityManager( 1678): Starting activity: Intent >> > > > > > > { act=android.intent.action.VIEW >> > > dat=content://media/internal/images/ >> > > > > > > media cmp=com.android.camera/.ImageGallery (has >> > > > > > > extras) } >> > > > > > > W/Process ( 1678): Unable to open /proc/2614/ >> > > > > > > status >> > > > > > > I/ActivityManager( 1678): Displayed activity >> > > > > > > com.android.camera/.ImageGallery: 673 ms (total 673 >> > > > > > > ms) >> > > > > > > I/ActivityManager( 1678): Exiting empty application process >> > > > > > > android.process.media >> > > > > > > (android.os.binderpr...@2cd28a88) >> > > > > > > I/Process ( 1678): Sending signal. PID: 3094 SIG: >> > > > > > > 9 >> > > > > > > I/ActivityThread( 3084): Removing dead content provider: >> > > > > > > media >> > >> > ... >> > >> > もっと読む ≫ >> >> -- >> unsubscribe: >> [email protected]<android-porting%[email protected]> >> website: http://groups.google.com/group/android-porting >> > > > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -- with regards vishal -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
