Profile your code to see where it is taking its time to optimize those critical paths.
If you are implementing the decryption in Java, you may be seeing differences in the hardware or Dalvik such as: - CPUs with or without floating point. - Different CPU speeds. - Older versions of the platform that don't have the Dalvik JIT. - Other recent optimizations to Dalvik that are not in older platforms. And of course when writing IO code make sure you are reading/writing data in large blocks (whichever APIs you want to use to accomplish that), avoid creating temporaries and causing lots of garbage collection, etc. It is hard to say much more than that to such a general question. On Wed, May 25, 2011 at 12:02 AM, Hitendrasinh Gohil < [email protected]> wrote: > hi, > > i am just writing the decrypted file from encrypted one,this takes a 4 > to 5 secs in galaxy tab, around 6 sec in htc and with zte blade it > stucks,taking more than 30secs. > > so what points need to be consider while writing the code for file > operation. > > -- > 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 > -- 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. -- 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
