-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Already downloaded images disappear while scrolling upwards in listview, loads slowly #845
Comments
Are the source bitmaps too big to download? Slow network connection? Did you try another image loading library? If you do and it works great, please let me know and I can take a look. I have a feeling this is not picassos fault. Paste a URL that you use or a bunch of them and I will put them in the sample app. |
I have the same problem on less powerful smartphones. I am using the recyclerview pattern for the list and definitely had a better cache performance with the volley library: https://github.com/mcxiaoke/android-volley |
By using this my issue resolved |
Images are reloading in the recyclerview even volley using LruCache class ? |
@raj9686 will you plz tell me, where to use this line?? |
Just Use Glide, it solved my problem and it's easy to change. https://guides.codepath.com/android/Displaying-Images-with-the-Glide-v3-Library |
Hi everyone,
My listview loads Picasso images slowly. I often have wait on it to download one image, scroll a bit, and wait on it to download the next image in the listview, it doesn't work in advance.
Downloaded images also disappear when I scroll back up. It feels as if Picasso is only loading 4-5 images at a time and replacing the ones already loaded to make room. Here's (http://i.imgur.com/SvzGWLI.png) what my memory looks like right now as I scroll up and down and wait for images to load.
I have already posted this concern on SO (http://stackoverflow.com/questions/27771646/picasso-keeps-reloading-images-while-scrolling-upwards-in-listview-loads-slowly) but was unable to find a solution. I was wondering if you guys, as a last resort, could help me figure it out? I am already using the fit() call, so I don't think it's a resizing issue. Any help would be greatly appreciated, thanks!
The text was updated successfully, but these errors were encountered: