Magic Cube

up library versions.

Up version to 1.8.4

Fix the long-standing problem that putting app to the background would not stop the 'solving' counter.

Fix the reddening the Lock icon.

Fix a rare crash.

Introduce a BlockController - a watchdog which makes sure the Touch and UI blocks do not take too long.
If it detecs a long block, it unblocks and reports the situation to Crashylytics.

Add a 'give up' dialog - if one made at least 10 moves when solving and presses a 'back' button, one needs to confirm.

Always set the back move icon when we clear moves

Give visual indication when dragging is locked.

Change the 'Cube Back' icon when there are no moves to back.

Abstract the part that controls the 'Locked' and 'Back Moves' buttons from the two activities: the main one and the tutorial one.
This code had been duplicated there.

Add flag of Botswana.

New Kilominx mesh.

Important bugfix: no we cannot unblock touch when WIN effect finishes, because

1) starting the WIN effect does not block touch in the first place
2) it can happen that this unblocking happens when we have started finishing the rotation but haven't removed it yet...

Corrections for the new Pyraminx5 patterns.

We've got lots of bugfixes, some 400 new Pretty Patterns.

Bump version to 1.8.3

Update the Pyraminx5 pretty patterns.

New Megaminx & Gigaminx pretty patterns.

Convert the move format to one which can hold moves of the Megaminx and Gigaminx (in preparation for introduction of the Mega& Gigaminx Pretty Patterns)
Now we use 2 bits for the angle, 3 bits for the axis and 5 bits for the bitmap of layers. This totals 10 bits so 1024, but the whole thing will not spill over 3 digits, because in the Minxes we have total of 6 axis, not 8.

Workaround for a crash.

Correct the Redmi mesh to eliminate the visible seams.

Correct the dino mesh to eliminate the visible seams.

Correct rotations of the Cube - eliminate one cse when four consecutive rotations collapse into one or a NOP.

Correct rotations of the Pyraminx - eliminate one cse when three consecutive rotations collapse into one.

Separate the notion of maxLevel (in DB) [which has to stay backwards-compatible with previous versions of the app] and 'numScrambles' - the number of times an objects gets scrambled in the 'full scramble' mode. Now the second can be whatever we want without breaking backwards compatibility.