Open Webreaper opened 6 years ago
Any update on this? It's currently so bad that I'm thinking of ditching Twidere and switching to another client right now.
I'm not a developer... but did you try to increase the database size in the storage settings?
Yes, I set it to the max setting, 200.
On Fri, 23 Feb 2018, 20:48 Dave, notifications@github.com wrote:
I'm not a developer... but did you try to increase the database size in the storage settings?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TwidereProject/Twidere-Android/issues/1074#issuecomment-368133839, or mute the thread https://github.com/notifications/unsubscribe-auth/AErI7g15EFVqegKDyzOYb8g63HT4X3rWks5tXyPGgaJpZM4R26dE .
Interesting. I can set it up to 500 objects. And Cache Size up to 500MB.
Oh, maybe it was 500. I have it set to the max. Doesn't help though. The timeline refreshes and I end up at the top and have to scroll down through 500 tweets.
On Fri, 23 Feb 2018, 23:10 Dave, notifications@github.com wrote:
Interesting. I can set it up to 500 objects. And Cache Size up to 500MB.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TwidereProject/Twidere-Android/issues/1074#issuecomment-368165146, or mute the thread https://github.com/notifications/unsubscribe-auth/AErI7lIi8PobdQU4FjUgpQyehdLsoW4rks5tX0VMgaJpZM4R26dE .
Wonder if this is related to https://github.com/TwidereProject/Twidere-Android/issues/1076.
I've uninstalled Twidere now and switched back to Talon, as Twidere is unusable for me until this is fixed.
If I don't read twitter for a few days, and my timeline gets long (700+ tweets) when I launch Twidere it will occasionally do a refresh and leave me with just 200 items in the timeline. All the previously-loaded tweets are discarded, and my remembered position is lost. I have to scroll down many times, loading 2-3 new pages of tweets, in order to find where I was last at and then continue reading up.
If I have 'remember timeline position' enabled, it should always be honoured and the timeline should not be discarded.
Interestingly, refreshing the timeline on a bad connection results in the tweets being displayed with all of their pre-cached images intact, so I presume that they're not being explicitly cleared, just that the timeline is doing some sort of 'full' refresh and losing its place.
Android version: (version code here): Latest from Google Play
Network type:
App version: (version code here)
Build variant:
Micro-blogging service:
App settings: