Hi,
here i will post and explain my events.
First a little overview of what Llama does for me, then i will add the events and a little explanation.
I'll start with my scheduled syncronization events.
Basically they simulate Juice Defender behaviour: they activate synchro every few minutes. There are 8 of them, 4 for data (when not in wifi zones) and 4 for wifizones. In each class there are two for weekdays and two for weekends (in weekend the time bettween syncronizations is longer), and they divide beetwen a normal and peak schedule. For instance, in wifizone, in weekdays, normal schedule is every 20 min and peak every 10, and in weekends, normal every 1 hour and peak every 15 min. You can customize it at your will.
Of course, they not execute at night, or with low batery.
My network control events, activates wifi with the screen on if it is disconnected (actually, only when user is present), and desactivates wifi and data (if they are connected) when the screen turns off. And some correcting event like stop wifi syncronization if I get out of a wifi zone and the syncro its been executed, or turning off date if it is enabled and i'm connected to a wifi network,etc
My night event activates the night profile (all volume to zero) and It will turn every syncro off. Then my alarm events (two fixed, and one variable for if i want to wake up later than usual), wake me up xD, turn profile to normal and also give the go to the syncronization events.
Then i have some app control events, like start dropsync syncro after titanium backup make the backup, or controling lux app trough it locale plugin: only enabled when the screen is on.
Then some app network control events, here i set which app will keep wifi or data on with the screen off. Also i don't turn data on with the screen like wifi, only when and app that use it is activated. And also turn on gps with google maps and turning off when maps is closed.
I also have some automated msjs when i arrive or leave work to my wife (copied to someone else here
).
I use a lot of variables, so i have some dedicated events to asign manually values to some of them when its needed. And also, other events asign automatically values to some variables. For example, since i have 8 syncronization events, editing wifizones will make me edit 4 of them too. So i have and event that when i'm in a wifi zone or out of them, it asign the corresponding value to the "wifizone" variable, and is that variable that i use in my synchronization events instead of a location condition.
Like i said a few time before, i use wifipolling with the home and near home areas events. And since bluetooth polling doens't work as i expected, i made my on bluetooth polling that is activated under certain conditions.
One event that could be useful is the one that start the homecreen after a call ends. It also start wave control app and its plugin, to answer/end the call with waves over the proximity sensor.
Also the battery events, when battery level is below a threshold, syncronization is stoped, bright is decreased (trough lux plugin), etc.
Here it goes the back up. You could backup your llama settings, copy them to a save location and then import this one to test the events. Nevertheless, i will add the link (from the share option) of every event and a little explanation later.
Llama backup