Maybe try changing this line:
public static final Executor SERIAL_EXECUTOR = Utils.hasHoneycomb() ?
new SerialExecutor() :
Executors.newSingleThreadExecutor(sThreadFactory);
to this:
* public static final Executor SERIAL_EXECUTOR = *
* Executors.newSingleThreadExecutor(sThreadFactory);*
Thanks.
On Tuesday, April 16, 2013 7:35:15 AM UTC-5, tsioularisa wrote:
>
> i read this and maybe is this a possible fault as i run the app in
> Gingebird! But except the asynchtask that is being used in the clearCache()
> in the beginning of the imageWorker in the loadImage the following
> asynctask is being used.
>
> // NOTE: This uses a custom version of AsyncTask that has been pulled from
> the
> // framework and slightly modified. Refer to the docs at the
> top of the class
> // for more info on what was changed.
> task.executeOnExecutor(AsyncTask.DUAL_THREAD_EXECUTOR, data);
> }
>
> is this a possible part of code which causes the problem? Which is your
> proposal for clearing the cases every time the user leaves the activity! In
> my app when the user leaves this activity he doesn't totally close the app.
> He navigates back to the home activity? Also how do you explain that the
> problem is being caused only when i switch between wifi and data package
> network and relaunch the app? As you can see from the logcat the previous
> loadimage hasn't been totally cleared? What do i do wrong?
>
--
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
