I've searched all over for some kind of manual for Droidfish to answer this and can't find one. Can you pause the analysis mode, but keep the most favorable line it has calculated displayed? If you toggle the analysis mode it goes back to the last position and erases the line it calculated. If you leave analysis mode running while you play through the line, you (at least on my phone) run into memory issues. I even get a "com.android.systemmui has stopped" error if I leave it running long enough.

I use only the Windows version of Stockfish (with Arena), but even it can't be paused. If it's stopped and then restarted for the same position, it starts from small depths again but recalls the evaluations of positions deep in the decision tree that it has made before (in the same session), hence the lines that it gives right upon restart are close to those that it was giving just before it was stopped. So it doesn't 'erase the line' totally - the arising potential positions are stored in its cache - but neither does it restart from exactly the same point where it was stopped.

As Stockfish prunes the game tree aggressively (to achieve a greater search depth), I guess running it several times for the same position up to a fixed depth is still more useful than running it one time - each new time, it evaluates some nodes that it skipped before, hence the optimal line search results are refined at each run.

To clarify, by "erase the line" I meant it stops displaying it. I didn't intend to make a declaration about its memory management methods.

Thanks for the quick response.

Well, if your only problem is that the line stops being displayed, then just take a screenshot before stopping the engine. (How to take it depends on the Android version, so I can't tell it here, do the research yourself if you don't know it.)

I could take a digital camera and take a picture of it as well, or write it down with pen and paper. That is beside the point.

When possible, I try to find a solution within the application itself. A workaround gets *around* the immediate problem, but doesn't resolve the underlying issue. I just think it's odd that it was coded to stop displaying the most promising line. It's not a design choice I would have made, so I was trying to determine if the application itself had a feature I had not discovered yet.