For the second time in two days, the launcher unreliably crashed and would not restart. All it wants to do is keep crashing until I reinstall it or restore a backup that isn’t my latest backup.

All Apps was accessible without crashing, so I went to settings and restored backup, but I could not restore the latest backup from 2-3 hours ago (this death-of-launcher crash could’ve happened way earlier than this, my phone was charging and not with me). It just kept crashing again and again when trying to restore it. So I had to restore an older backup from more than a day ago, and I lost so many changes.

This is the second time this exact thing has happened in two days. I believe it started when I started making backups of the launcher (manually). Somehow it crashes soon after a backup has been made? Makes no sense to me. And I can’t restore that backup.

Here’s the scene to understand better why I think it has to do with backups:

I have five backups.

The oldest one – the fifth one – is the one I made before this death-of-launcher happened for the first time. I couldn’t restore that backup and kept crashing.

Then the three in the middle are fine. They can be restored successfully.

The latest one from 5 hours ago cannot be restored. (The launcher crashes while trying to restore it.)

After the first crash I couldn’t restore the fifth backup, and I still can’t after this crash. So that backup was always created corrupt. Same as the latest one. And the death-of-launcher crash occurred a few hours after their creation.

So if a corrupt backup file is created these events occur? My evaluation could be completely wrong too because I don’t know much about how the backup and restore system functions.

SO. Thoughts?

I have obviously reported crashes often, but since there is no response from Pierre I thought I’d post here. I really require some answers to this problem.

Whether the crashes are related to creating backups or not, I really need this to not happen.

I create backups to make sure my data (read: my time, money, sanity) is saved, but in this case the opposite has happened, twice.

]]>

Tasker integration problem:

Setting a variable to 0 works, but setting it to 1 doesn’t.

Replicate:

Go to Bindings of an item, and set the Visibility property to $aVariable.

Go to Tasker, create a Task to set $aVariable to 0 (with Lightning Launcher Variable plugin).

Play the Task. The item should now be hidden.

Go back to Tasker, change the Task to set $aVariable to 1.

Play the Task. Nothing will have changed.

Tested with the following values: 0, 1, 2, 5. Works only with 0.

]]>