The Galaxy S has a really "clever" storage chip, which, combined with its
"clever" file system, can be up to 10-30 times slower than a previous
generation phone (e.g. Motorola Milestone). Those numbers are based on
application-specific benchmarks I've done with SQLite.

So, if you're saving your data to a file, it can be very slow.

TreKing's suggestion of using an AsyncTask can make this less visible to the
user - but if you're doing any kind of network I/O, you should not be doing
it on the UI thread anyway. So a good idea in any case.

-- Kostya

2011/6/10 TreKing <[email protected]>

> On Thu, Jun 9, 2011 at 2:54 AM, srikanth vikkurty <[email protected]>wrote:
>
>>  This process works faster on most of the devices except Samsung Galaxy S.
>> Could anyone suggest an alternative for overcoming
>> the same.
>>
>
> You should not be counting on some network operation to operate quickly on
> any device. Run it in the background using AsyncTask, properly handling the
> time the user is waiting with a dialog or something, and it won't matter how
> slow the device is.
>
>
> -------------------------------------------------------------------------------------------------
> TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
> transit tracking app for Android-powered devices
>
>
>  --
> 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
>

-- 
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

Reply via email to