My LL crashes a lot.
My LL crashes a lot. It sometime can crash from 1 to 6 crashes per day. Most of crashes are when I’m tying to enter drawer, change wallpaper or icon.
My device GT-I9105P aokp 4.4.4
]]>« Currently i installed launcher on my all in one android navi on my car.. (Previous Post)
(Next Post) Found the way to avoid the white BG on shortcuts »
D5 Creation
< ![CDATA[
Really? I’ve been using LL for about a few months now and never experienced such a thing. Why don’t you clean flash a rom and start from the beginning?
]]>
< ![CDATA[
Do you have some custom system wide theme, or are you using xposed to load some graphics, or something similar?
]]>
< ![CDATA[
Well, I have theme, and xposed only with greenify.
]]>
< ![CDATA[
From what I can see from your log the app fails to load some background when loading the screen (before to run the app code), this is at the android level. Either these images are too big, or there is a memory leak somewhere.
Your per app memory limit is low (48M), maybe you have a setting in your rom to change this, try to increase it to 64M: if the problem persists but with a lower frequency then this is probably a leak. If the problem go away, then the theme is using a lot of memory.
]]>
< ![CDATA[
I don’t think I have option to change memory limit. I will disable theme for now. Lets hope it will work.
]]>
< ![CDATA[
I don’t know about aokp, but may you can modify the build.prop file and add:
dalvik.vm.heapsize=64m
]]>
< ![CDATA[
I have dalvik.vm.heapstartsize=5m, dalvik.vm.growthlimit=48m, dalvik.vm.heapsize=128m.
]]>
< ![CDATA[
Sorry, this is growthlimit
]]>
< ![CDATA[
Nope. I still got crashes. I’m afraid I must install other ROM. There will be lot to backup…
]]>
< ![CDATA[
Before to do this, could you try this: add a dynamic text “heap free” and see if the value constantly decrease until it reaches a value near 0 and crashes? Be aware that when this item is displayed it slows down the app.
]]>
< ![CDATA[
How do I add that? I can’t really get used to this new editor.
]]>
< ![CDATA[
long tap on empty space, add item, dynamic text. Then edit the “Text to display” property: enter edit mode, select an item, tap on the pencil icon in the bottom bar
]]>
< ![CDATA[
I was talking about this “heap free” I couldn’t find this. I didn’t though about changing from text to data 🙂
But now I was looking at this it was kinda different: It wasn’t drop to 0 like you said, but when I used options or drawer icon value drops for 0,1MB (options) and 1,1MB (drawer). And You was right, it crashes, but… it was different. Here I got black screen and soon “application Lighting Launcher was forced to stop” (or whatever it looks like in english). Then value back to around 54MB.
But crashes I have daily just froze for moment android, and than I got popup where I can choose how send report.
Here black screen. No report.
]]>
< ![CDATA[
same here, i get black screen when pressing home button on navbar after opening some app.
i need to power off and power on again to pass the black screen
]]>
< ![CDATA[
Strange. I only need hit home or back button and I’m on desktop once more.
]]>
< ![CDATA[
I’m gonna try another rom then
]]>
< ![CDATA[
Pierre Hébert can this bug be related to mine? (In my case it is not a crash, but the launcher gets closed in the background)
I have some scripts to edit launcher files, I can provide them if can help.
]]>
< ![CDATA[
TrianguloY I don’t think the behavior on your device is a bug. Apps (and processes) get stopped and restarted continuously. For instance if your device can hold N apps at once, and N+1 apps need to be run in the background at regular interval (to check mail, fetch rss, receive a sms, notify an expired alarm, etc.) then one has to be removed from memory to free space, in a round robin fashion (sort of…), depending on activation frequencies. On Android all apps should be prepared to be stopped anytime (save data, restore them upon startup). I believe that in your logs you should see regular notices of terminated processes.
Also in Lightning all errors are caught and displayed through another external activity launch. This means that when the app is terminated because of a fatal error, a message is displayed, no matter whether the app is on the foreground or not.
]]>
< ![CDATA[
Pierre Hébert ok. I apologize for the insistence.
]]>
< ![CDATA[
in my case, it’s rom issue, changed to euphoria rom and lightning strikes back again 👍
]]>
< ![CDATA[
I changed ROM and now it works fine. Probably it was bad compilation but who knows.
]]>