Cloning repos is extremely slow

[amberin]

I think there's a real risk that users will believe the app has frozen, and try to abort the cloning.

I just tried re-cloning a repo of mine with a size of 2,7 MB on the server. If I clone the repo to my laptop it takes about 3 seconds. When I cloned it to Orgzly, it took almost a full minute.

Something must be wrong in the cloning-related logic, because I cannot imagine that disk I/O or the git clone command itself is being this slow.

IIRC, there are also quite a few deprecated methods involved in the current cloning-related code, so I suppose we could start by cleaning that up a bit.

[alensiljak]

How did you get git to even work?

[amberin]

How did you get git to even work?

Please describe what steps you take and what happens in #58, or in a new issue, if it's something completely different.

I did my last clean install and re-cloning of my own repo only a few weeks ago. Android 13 on a Pixel 5.

Since I don't have any issues myself, we need more info in order to troubleshoot.

[amberin]

Seems like this might be a JGit issue. Don't have a good link right now, but I've been looking at the JGit forums a bit, and cloning being slow seems to be a common complaint.