Is there an option to start the app drawer from the first page after a while?
Is there an option to start the app drawer from the first page after a while? Haven’t seen it so far. Even after I restart LLX the app drawer still opens the page that was viewed last.
Pierre Hébert
The newest beta has been awesome so far, love the unlocker! The ripples look really cool!!
Unfortunately unlocking still activates the notification bar even if it’s been hidden from everywhere. Unlock -> notification bar shows -> desktop appears, it takes ~1-1,5 seconds. Seemed a bit quicker before, but can’t be certain because I haven’t used it for a few days because the call screen thing was driving me nuts. =D
Just got a crash, sent you the logs and NOW after that, when I lock and then activate the screen via power button, first the lockscreen is shown for 0,5-1 seconds, the unlocker doesn’t even have time to apppear, and then it already unlocks, without me touching the screen!!
]]>
D5 Creation
< ![CDATA[
Regarding the app drawer there is no way to start it on another page at the moment. It always saves the last page and position. This is something that can be improved indeed.
The crash is due to an out of memory error, maybe this is related to some widget has it seems the amount of memory used by the launcher itself is not unusual, however it may hide another problem. Could you try to add a dynamic text “heap free” somewhere and have a look at it from time to time ? In theory it should decrease when you load the app drawer, open some folders, but after a while it should reach a stable value. If this is not the case then there may be some leak somewhere. The startup delay is a hint that it may be related to widget though.
On my device the status bar sometimes flicker (I can see it but it always disappear soon after). I think there is something special on some devices regarding this bar, but maybe if I can find a way to remove this brief status bar flicker, it would solve the problem on devices where it remains visible.
]]>
< ![CDATA[
Setting the lockscreen again – still the same behaviour.
Restarted LLX – still same behaviour, unlocker is now shown at least!
LLX beta lockscreen issue
Sry for the video quality, I’ve got no root and this seemed like the best choice for a free no root recorder, have to mention it’s 4fps not laggy!
LLX beta lockscreen issue
Amazingly quick response Pierre Hébert !!
]]>
< ![CDATA[
Humm… I think I understand… In Android security you disabled the lock screen, did you ? If yes, could you try to enable the “swipe” screen lock ?
]]>
< ![CDATA[
The first waking of the screen is from a power button and the second is from the home button – if it makes any difference.
]]>
< ![CDATA[
Heap free:
created – 19-24 MB
opened app drawer – ~4MB
it stayed around that for some time
LLX crashed – 54-55MB
opened app drawer (it opened as quick as if I had already loaded it just before) – ~24MB
….
….
When I try to go to customize->more on the heap free dynamic text LLX crashes, same result several times.
]]>
< ![CDATA[
Could you send me an export of your setup (export for apk) ?
Since your device is configured for 128M, the fact that the launcher starts at 54 means that 74M are used right at startup. From the log it appears that LL uses 20M for items excluding widgets, so there is a gap here…
]]>
< ![CDATA[
Yup, I disabled it, because it worked better on the previous beta this way and on this one as well at the beginning!
Setting the unlock screen to swipe got the lockscreen to stick and wait for the unlocking command =D
Thanks, Pierre ! ! Really quick and efficient counselling ! =D
And Edit.>customize->more doesn’t crash the heap free dynamic text anymore, too!
]]>
< ![CDATA[
great ! but I think that there is a real problem with memory (not linked with the lock screen, but a real problem anyway)
]]>
< ![CDATA[
Do you want the template that the export for apk creates or an actual apk?
I can manage the first, but have zero experiance with the creation of apks.
]]>
< ![CDATA[
Yes, just the Template file, it will contain the list of widgets so that I can have a look at them
]]>
< ![CDATA[
https://copy.com/bSDzfhIgK1NMktDR
Here you go!
Heap free is usually around 20MB or if I haven’t opened the app drawer by that time it’s <10MB.
Also if I open the app drawer right after a restart I see a reasonable delay, but if the heap free is around 20-25MB then the app drawer takes reallly long to open up.
The huge chunck of memory going away somewhere is propably to blame, that I’m getting more crashes than average (or so it seems to me at least)? And the crashes when I try to apply an adw icon pack?
After a restart the heap free of 54MB was an exeption, after that it usually start 50,50MB and drops instantly from there.
]]>
< ![CDATA[
Thanks! I will have a look at this tomorrow. I have loaded it on my tablet, all I need to do now is make the analysis…
]]>
< ![CDATA[
Now that I’ve had a few calls, it needs mentioning, that after removing the phone from my ear the call screen comes up nicely, BUT while it’s next to my ear the display flickers on and off, with the lockscreen visible!
]]>