I had that problem on the windows wallet... I assume there is a database-check that goes on, without telling you, which stalls the downloading. Eventually, it continued, and quickly pulled a bigger list of peers.
Chances are, you got to the end, on the chain, and picked-up one partial bad block from someone who didn't have the update. All wallets seem to have issues not being able to go backwards through the database, and remove blocks, in order to go forward again. (That is one of those situations where you have to delete the whole damn database, and download it again. Or, restore from a backup which was more complete, but did not contain the fork-block itself, or any other forward-blocks on that fork.)
That, is one thing the devs can look into. Since no wallet, to date, has been able to do that. (It sees the other fork, which is longer/taller or more-populated, but it never joins it. Or it does, but never rebuilds from the point of the fork. Causes YOU to be rejected by the network, and you to reject them for failing to accept you.
Each thinks the other is "misbehaving". Returning you to the bad fork, or leaving you alone with others who are all stuck at the same point.)
