Crashing Frequently!
Crashing Frequently! !! Sent several reports via saransorb@gmail.com. Fix this or provide an update please. ..Thank You…
]]>
© 2024 Lightning Launcher Google+ Archive | DISCUSSION Theme by: 
D5 Creation | Powered by: WordPress
D5 Creation | Powered by: WordPress
< ![CDATA[
What does the logcat look like?
]]>
< ![CDATA[
Thomas Milne what’s that sorry…😐
]]>
< ![CDATA[
– Logcat Extreme – Android Apps on Google Play – https://play.google.com/store/apps/details?id=scd.lcex
]]>
< ![CDATA[
Thomas Milne thank you…installed it now…
]]>
< ![CDATA[
What phone
]]>
< ![CDATA[
stєvє chαvís this one is Note 4
]]>
< ![CDATA[
Thomas Milne installed it. ..how do I share the log with you now please. ..
]]>
< ![CDATA[
Crashes a lot on my N6 too, especially when changing icons, fooling with widgets, or adding apps to folders
]]>
< ![CDATA[
Reports sent this way are anonymous I don’t know which one is yours. Indeed, as Thomas suggested, a logcat would be an easier way to analyse this issue. My guess however is out of memory error, this is by far the most frequent cause for crash. Usually this happens because of large images or numerous smaller images (including widgets).
]]>
< ![CDATA[
Pierre Hébert Don’t you need root for logcat?
]]>
< ![CDATA[
Only from Android 4.1
]]>
< ![CDATA[
Pierre Hébert thank you. Tried Log Cat. But it didn’t work. My phone is not rooted😐 I guess it could be memory. ..as the phone tends to go really slow before LL crashes. How do I fix this?
]]>
< ![CDATA[
In order to confirm whether this is a memory issue or not, add two dynamic texts somewhere on your desktop. Configure one to heap free and the other one to heap max. If the heap free decreases until 0 (near 0) then try to identify which component is causing the issue:
– either it is regularly decreasing and it means there is a memory leak somewhere, in which case I may be able to fix it if you manage to find which steps causes the memory to be used and never freed
– either heap free is low very soon, and it means that there’s a memory hog somewhere. In this case try to remove items one by one to find which, starting with larger objects (make a backup first)
]]>
< ![CDATA[
Pierre Hébert Thank you…I’ve added heap free and heap max…now how do I use them to identify what you’ve asked me to please…
]]>
< ![CDATA[
*If the heap free decreases until 0 (near 0) then try to identify which component is causing the issue:
– either it is regularly decreasing and it means there is a memory leak somewhere, in which case I may be able to fix it if you manage to find which steps causes the memory to be used and never freed
– either heap free is low very soon, and it means that there’s a memory hog somewhere. In this case try to remove items one by one to find which, starting with larger objects (make a backup first)*
Exactly how he said
]]>
< ![CDATA[
Jay M Heap Free has been fluctuating in between 29-57 and Heap Max is constant at 256 .
]]>
< ![CDATA[
So this means some item(s) is(are) using a lot of memory. Try to look at items with images (backgrounds, widgets, large icons, wallpapers, …)
I forgot to say don’t forget to remove these heap dynamic texts, they are slowing down the app.
]]>