Force closes around 10 times a day since latest two beta releases.
No specific pattern. Can be in any app, on the desktop, or phone idle on the side. When it happens, most times it freezes even when I try to type the error report to email Pierre. This is ONLY since the latest 6 and 7 Beta releases with the new menus. I have removed the app completely, cleared system cache, reinstalled, and it still happens. Ive given up now and remembered I bought Nova a good few years ago, so I have re-loaded that, and amazingly it is now faster than Lightning. Previously I replaced Nova with Lightning over 2 years ago because it was faster, now it looks like it’s the other way round. But I hate Nova its so boring, so really would like to get this fixed. Does anyone else have the same issue ?
Stock Galaxy S5 and LLX lockscreen.
]]>
D5 Creation
< ![CDATA[
What happen if you change the image pool size in General settings to 0%?
I also have a similar issue, and that reduced the amount of problems per day
]]>
< ![CDATA[
Thanks for the advice. I am just reinstalling LL and will try that. Did it reduce it to zero FC problems ?
]]>
< ![CDATA[
I don’t have force closes, only the launcher is restarted. With the setting set to 0 it still happens, but less times.
I asked just to check if something can be related, but I don’t know if it will be better (or worse! ) that’s why I only asked.
]]>
< ![CDATA[
I have set this to 0 now. I will monitor how it goes. So far so good. Thanks TrianguloY.There is nothing weird or quirky about my phone setup and I only have 3 3 desktops and 2 widgets, so I’m surprised no-one else has chimed up here.
]]>
< ![CDATA[
TrianguloY, just curious I still don’t understand the image pool so much, what would be best if I am using a lot more images, closer to 0 percent or closer to 100
]]>
< ![CDATA[
Pierre Hébert will explain better, I only know the description shown when long clicking that option
]]>
< ![CDATA[
Lol I honestly can’t tell any difference so I jus leave it alone
]]>
< ![CDATA[
Again, I am more thinking at an issue with widgets. The fact that it happens at random times is an indication that the launcher doesn’t crash because it does something for “itself” but because something else asked it to do something. The something else is usually a widget app. Also if the issue persists after you uninstalled/cleared LL data, then this is also an indication that the root cause is outside. I may be wrong though, but I would bet that this has something to do with memory. Nigel Pugh , are you able to send me a log, or look at the device log for something like “IRemoteView” or “OutOfMemoryError”?
Regarding the image pool, 0 is the same as 100%. Lightning will try to not use more than N% of the virtual machine memory for bitmaps. For instance, if N is 33 and the memory limit is set to 128M, Lightning will try to use no more than 42M for images (icon, background), images for widgets are not in this pool.
]]>
< ![CDATA[
The only widgets I use are NILS lockscreen widget (on LL lock screen) and weather widget on my desktop. I have used these since before LL and they have never given any issues previously. My phone has minimal apps on it, nothing new, and only started this since the re-work of the menu system.
Can you tell from the logs I sent you what is causing the problem at all ?
]]>
< ![CDATA[
Hmm interesting, yea I think I got a lil more studying to do before I fully grasp the whole concept lol
]]>
< ![CDATA[
I didn’t received your logs Nigel Pugh , could you try on pierrox.net@gmail.com please ?
Corey Spell the whole concept is quite complex for such a basic feature! Displaying a lot of images (or large images) is a pain on Android.
]]>
< ![CDATA[
Hi Pierre, that is bizarre. Every time the app has failed it has asked me to send the logs.they are automatically prepared in an email and I just add a brief description. I have been sending them for days now, off the “report” option when it fails.is that a Google play thing or llx ?. I am not sure how to send them another way if you aren’t receiving them via that.
Nigel
]]>
< ![CDATA[
Nigel Pugh He does receive them but can’t reply to them all. I definitely recommend sending them if they are unexpected and not explained by a reported bug. Make sure you provide steps to replicate the issue too.
]]>
< ![CDATA[
James, Pierre has already said in his posting that he had not received them.
They have all the required information in them. I am the md of a software testing company so am probably the best person to describe and diagnose a defect, however, as I mentioned in them, there is no way of replicating the issue. Does not matter what apps are running, what apps,or desktop has focus, what I have just done or am just about to do, the force closes are random. The failure reports supply all my hardware and software versions and the llx releases that cause the issue.
]]>
< ![CDATA[
I have set the image pool size to zero and still getting the same problem. The report option when it fails, does send to the email address you mention, however only a couple seem to be in my sent items, so when it says email sent successfully in the toast, clearly it isn’t sending them. How else can I collect the logs at the point if failure ?
Nigel
]]>
< ![CDATA[
I confirm that I received none of them, at least not since April 7 (it was out of memory error with widgets). Maybe the emails are held in the outbox?
Widgets in your setup are provided by the apps above. Try to uninstall/reinstall each of them . My guess is that one of them could trigger the issue, uninstalling one at a time could help to fous more rapidly on the issue.
com.devexpert.weather
mikado.bizcalpro
com.roymam.android.notificationswidget
com.clockinn
]]>
< ![CDATA[
Nigel Pugh look more closely… LL doesn’t send to the email he mentioned. He asked you to send to an alternate one.
]]>
< ![CDATA[
I can almost assure the royman Notifications widget is the culprit.. I have used it and sometimes it would randomly jump up to over 350 mb of ram and send the garbage collector into overdrive lol
]]>
< ![CDATA[
I have never had any problems with it, and have been on his beta testing group since he first set it up, however, I have to say, I have removed it today, and so far have not had any issues. So it is potentially looking like that is the culprit.unfortunately due to the llx lock screen being integrated, it’s one of the only notification apps that’s half decent that you can use with llx
]]>
< ![CDATA[
Ok, nils had been removed and it’s still having the same problem, so that isn’t the culprit.
]]>
< ![CDATA[
Replying to Chris Chastain above. I know he asked me to send to a different email address but the failure reporting process does not allow me to select another email address or even copy the data to send via conventional email. Pierre it would be easier if your failure report logging sent to an email address that you have access to. There is no other way I can capture the data. However nils has gone and I still have the problem.
]]>
< ![CDATA[
The email address is correct… When I use gmail to send the mail I can change the receiver.
When a crash appears Android should ask you which way you want to share the data. In the list there should be apps such as gmail, drive, evernote, etc. If not, then you need to clear defaults on the app which is always launched, and select another decent tool (that let you modify the receiver email 😉 )
]]>
< ![CDATA[
Nigel Pugh hmm… When I send a crash log, I select my gmail and it pops up an email, ready to send, read, change To address, whatever. Weird.
]]>