Problem with handling long threads combined with focus loss

Version: 1.25.2
Android: 16

Long threads (with hundreds of post) are split. The first part is loaded without any issue. The second part is loaded post for post. That is relative slow but works. But if the app loses focus (another one is used for some time, say some seconds) and RedReader get focus again (is shown on the display), there are a reproducible issue: Often no further post can be loaded due to a connection problem. That seems to depend on the time RedReader is out of focus (if is are few seconds the issues seems not to occur). That is very inconvenient if you reads threads with multiple thousand posts.

Reproduce the issue with a thread containing hundreds or thousands of posts, then leave RedReader unfocused for several seconds and return to it. Trace the code responsible for loading the split thread's second part and handling focus or lifecycle changes. Done means post loading continues reliably after returning to the app without the reported connection problem.