Decoding images is already implemented in native code. That decodeFile function is the call into native code, so if that is the hot spot moving your other stuff to native code isn't going to help.
On Mon, Jun 25, 2012 at 6:45 PM, Guilherme Utrabo <utr...@gmail.com> wrote: > In the application I'm working on, the user selects several images and > opts to process them. > The application go through those images getting the thumbnail for each > one, and then save some info about the image on the database. > Today this process takes about 3 minutes to complete for about 300 images. > We are trying to reduce it to less than a minute. > I saw in the Method Profiling that the current culprit is the method > decodeFile, called internally by MediaStore.Thumbnails.getThumbnail() > I'm already using inPreferredConfig RGB_565 and MICRO_KIND as the size of > choice. > Should I consider using NDK to optimize this part of the code? Any advice? > > Thanks in advance. > > Regards, > Guilherme > > -- > 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 -- Dianne Hackborn Android framework engineer hack...@android.com 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. -- 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
