Hi!
Hi!
I’m using LL since a few weeks … i did a lot of customization stuff on different desktops for testing.
since i’m testing LL, i had 5-6 time the same problem:
1. LL crashes
2. Android Launcher APP Selector appears
3. I select LL
4. LL crashes again (1.)
the only fix i found is to reinstall LL and restore latest backup … but this task is very annoying …
can everybody help me out … with a more “powerfull” solution?
D5 Creation
After remove LL and installing it again, LL executes correc
But I can’t get into the layout editor of random panels.
If I create a new panel the layout mode works random…
I have already tested the following things:
– multiple times uninstalled & installed LL
– disabled floating desktop
– disabled the script execution
Infos about my Device:
Device: Samsung Galaxy S6 (64GB)
OS: Stock Android 6.0.1
Launcher: Lightning Launcher v12.9.1 (r2583)
If you need further information, please feel free to contact me!
https://plus.google.com/photos/100854826756922530252/albums/6344711268562704897/6344711269991638930
To enter layout mode for a panel or folder, you have to long-click that panel or folder canvas.
To enter layout mode for your whole desktop and edit where these panels are, hold the “back” key to get to the settings menu.
This may not be related at all to your problem.
If you can zoom in the screenshot, you can see that the panel is in layout mode
I have already tested to add items to the panel while layout edit bug happens.
I can add an item but the item didnt have an icon or an label after creation.
While testing in the faulty edit mode (add / remove items, moving “invisible” icons arround), LL crashes at random actions.
Maybe this screenshot helps to identify the problem:
https://plus.google.com/photos/…
I fear you just hit a bug that has been here for a while. Either nobody reported it or this one is difficult to trigger and rarely found. Or maybe your setup has been subtly corrupted by another previous bug.
I can suggest two things at the moment:
– if you wish/can, send me a backup of your setup, and if needed with instructions on how to reproduce the error. I may be able to analyse data and see what’s wrong. I am not certain however to publish a fix for the current stable V12x version, as I am currently focusing on the next V14 version
– if you feel adventurous, try the current v14 beta, it’s quite stable. If data in your setup aren’t corrupted then chances are that it will solve the bug.