Hi all

Hi all

I’ve set an event at Launch for my main Desktop

Sometimes the event is not triggered. Did you noticed the same ? 

]]>
« (Previous Post)

9 Commentsto Hi all

  1. Anonymous says:

    < ![CDATA[

    Which event are you talking about? 

    ]]>

  2. Anonymous says:

    < ![CDATA[

    TrianguloY Launch event

    ]]>

  3. Anonymous says:

    < ![CDATA[

    Launch event is only fired when LL starts if I remember correctly. Or if that particular desktop is accessed for the first time.


    You might try “resumed” event, which is fired everytime the desktop is, well, resumed. I.e. when returning from an app to LL.

    ]]>

  4. Anonymous says:

    < ![CDATA[

    Ah, the “load” event. Yes, that is fired only once until the desktop gets unloaded.



    If you use a different language pack, it is a good idea to switch to English and check the exact words instead of your own translations.

    ]]>

  5. Anonymous says:

    < ![CDATA[

    TrianguloY i’m using English version


    Lutz Linke​ I want to run an app when LL is launched


    Sometimes this event is not triggered. Could be a bug.


    Resumed : I only need a 1 time launch so could be not fine for me, or I can use resumed like calendar icon script 😊

    ]]>

  6. Anonymous says:

    < ![CDATA[

    Oh, ok.



    The event is triggered only when the desktop is loaded, so if you restart the launcher but you open a different desktop it won’t be fired. Also if you open the desktop a second time it won’t be fired neither (unless the launcher restarted itself in the middle)



    Maybe it is in fact a bug. Could you find some steps to reproduce it?

    ]]>

  7. Anonymous says:

    < ![CDATA[

    TrianguloY rebooting my smartphone : sometimes the event is not fired. I’ll try to check a logcat when not working

    ]]>

  8. Anonymous says:

    < ![CDATA[

    There is something that could explain this: on my old Motorola I noticed that the home screen (the dashboard activity) is sometimes started, stopped, and restarted during the boot process. This is only one activity, not the whole app and as a consequence desktops were not unloaded but kept into memory, and first time animations couldn’t be seen.


    This strange behavior was seen on a old device running 2.3 so I don’t know whether the same thing could happen on a newer device from another manufacturer.


    If you can capture the log of your device from the boot, you may be able to look for lines like:


     START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=net.pierrox.lightning_launcher_extreme/net.pierrox.lightning_launcher.activities.Dashboard}


    (Although it seems those infos have been stripped from the logs in samsung devices)



    Another test you could make is to run a script for the load event which would store the current date somewhere in a tag, then read this tag again: if the date is a few seconds ago then this mean the event has been run during the boot process, otherwise it means the event has not been fired at all (but I am skeptical).

    ]]>

  9. Anonymous says:

    < ![CDATA[

    Ok thanks I’ll recheck

    ]]>

Leave a Reply

Your email address will not be published. Required fields are marked *