Comment 2 for bug 1600582

A reboot of the handset, and it is now working. It doesn't look like any of the partitions are full, so it's not clear what the cause of the issue is:

$ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 484932 4 484928 1% /dev
tmpfs 97460 324 97136 1% /run
/dev/mmcblk0p7 12243756 199988 11421872 2% /userdata
/dev/mmcblk0p6 2076276 1719668 251136 88% /
/dev/loop0 145328 143528 1800 99% /android/system
none 4 0 4 0% /android
tmpfs 487284 4 487280 1% /etc/fstab
/dev/disk/by-path/platform-mtk-msdc.0-part5 705512 17100 652572 3% /android/cache
none 4 0 4 0% /sys/fs/cgroup
tmpfs 487284 24 487260 1% /tmp
cgmfs 100 0 100 0% /run/cgmanager/fs
none 5120 0 5120 0% /run/lock
none 487284 112 487172 1% /run/shm
none 102400 0 102400 0% /run/user
tmpfs 487284 0 487284 0% /media
tmpfs 487284 0 487284 0% /var/lib/sudo
tmpfs 97460 40 97420 1% /run/user/32011
tmpfs 97460 0 97460 0% /run/user/0

(andrdoid/system is expected to be full - that's it's normal state)

That said, it doesn't look like the click has installed at all after the reboot.