Llama - Who's Using It and Any Good Examples?

[buggy_droid]

@bcchgeneral

So, your question pertains to two similar but separate events, correct? One changes the profile to loud and set retest=0, the other changes the profile to normal and set retest=0? Which one is failing? How often it fails? And, how does it fail (is it only not changing the variable, the event is not triggered at all, or something else)?
If one of them works but the other fails, I'd suspect the area condition isn't specified correctly, or the variable name is misspelled in the event definition. I noticed you are mixing upper and lower cases in you post. Other than that, your events are simple enough and hard to screw up (assuming you have told us exactly how your events are set up).

Assuming that you made sure the event immediately before the ones in question (the one that unlocks the profile) ran, it's highly unlikely that Llama service had been killed by the OS or by another app. If Llama is awake the whole time, the fact that the event fails randomly suggests some cell IDs are not recognized as you expect, but the fact that area condition tests green precludes this possibility.

Assuming Llama never stopped working and all conditions are tested true as you said when the event in question fails to run, the only other possibility I can think of is the presence of another event that sets retest=1 (or you could be hitting your shortcut to set retest=1) while the area conditions for the events in question test false. That way, when you tap on the shortcut to unmute, the variable has already been =1 and the condition tests true when you check but the event won't be triggered because there is no change in the condition. If you can confidently exclude this possibility, then I have no logical explanation as to why the event won't run, be it never or sometimes.

Reinstalling Llama (an older or newer version), factory reset, trying different ROMs, may help. I can tell you that it never failed on Galaxy s2 with OS 4.1.2, but it could be that I didn't test it long enough to see a fail. You wouldn't want to switch to a 3-year-old model just for this anyway.

 

[bcchgeneral]

@buggy_droid

Thanks for working with me on this!

Yes, my question pertains to two similar but separate events.
Yes, that's what they each do.
The one that I have noticed failing is the one that changes the profile to loud and sets retest = 0. But it's intermittent, so I'm not sure if the other has the same problem.
I'm not sure how often it fails - I'm still testing it - but it's definitely failed more than once.
It fails by not changing the profile to loud, and not changing the variable to 0. The event history says that it didn't happen at all.
Yes, I did mix upper and lower case in my post (sorry!) but there is definitely only one 'Retest' variable in my Llama.

Hmm, I think you're right: another event left the 'Retest' value as '1' instead of resetting it to '0' - I've changed this now, and I'll see if that fixed it.

Thanks so much for walking me through this!

 

[sivakrr]

Hi All,

Could u guys pls guide me how to set a small vibration when the user picks up the call at other end while calling (in other words at 0th second when we make outgoing call)

So that we need not keep the phone all the time at the ear.

I tried "Call State:In a Call"

It vibrates when we hit the call button (not when the user at other end picking)

Help would be appreciated.

 

[buggy_droid]

@bcchgeneral
Welcome
Let us know if that works.

@sivakrr
You don't need Llama for that
"Vibrate Call - Android Apps on Google Play"

 

[Emilio Donoso]

Hi,
Recently discovered Llama, that seems an incredibly powerful app to change many settings according to the cell mast your phone is connected to.
I trained two areas, Work and Home, and they show no cells in common.

The problem is that cell detection, and consequent firing of events while entering or leaving an area, only happens after pressing the power button to wake up the screen. I have tried turning on Cell Polling mode, with various options (Awake while polling, incresing cell polling active time, lower cell polling intervals...). None of them seems to work. Events (i.e. entering/leaving area) are triggered only after waking up the screen, meaning I have to remember to press the power button every time I get in/out of an area to change volume profiles, which defeats the main purpose of the app. I also can't rely on Wifi detection to establish a location.

Any ideas or experience? I would appreciate very much!
I read somewhere that Android could bekilling the process that watches these events. If that is the case, how to find it out?
FYI, using Moto G with stock KitKat, no battery saver app.

Thanks

 

[buggy_droid]

@Emilio

Sorry to hear that Llama loses track of whereabouts on your phone
Luckily, you already have an answer. Since Llama (or the OS) on your phone checks for cell ID when the screen turns on, just make an event in Llama that turns the screen on every 5 min (or whatever the frequency you want). Llama will then (presumably) check your whereabouts every 5 min. You can also queue another event that turns off the screen after 1 sec, thereby minimizing battery use.

If you don't like the idea of your screen automatically turning on every so often, you can try what bcchgeneral did (see post #639). Instead of turning screen on/off, make an event that toggle a Llama variable between 0 and 1 at a regular interval. Then, add a condition "when (your llama variable) is 1" to your events that change the profile according to the area you are in. Theoretically, toggling the variable will make Llama to check if the other condition (the current area) is also true. Hopefully this is enough to wake up Llama and/or the OS to look for the current cell ID.

On the separate note, in the JB 4.1.2 OS settings, there is "location services" under which a check box for "use wireless network: location determined by wi-fi and/or mobile networks". I don't know if Kitkat has the same option, and if so, whether you check the box. Llama does just fine on my phone without checking this box, and checking the option uses additional 1 to 2% per hour of battery, so I leave it unchecked. But this might just work for you.

We would appreciate if you tell us which option did/didn't work. That will help me when I buy a Moto G. It's about time I get a new phone
Good luck!

 

[Olivier D]

For those of you having trouble with Llama, enable these two features in settings :
settings>security>device administrators>check the Llama box
settings>accessibility>turn Llama on
Quit Llama and launch it back

 

[anon8164182]

Does anyone know if it's possible to delete files with Llama?

I have a cuple of apps that create large temporary files, so wondered if I could set Llama to delete the temp folders every couple of days, saving me having to use Clean Master.

 

[buggy_droid]

@edithswanneck
It is possible

1) Install a script editor, either Script Manager, or SL4A.
2) Write a script to delete your files using the script editor you chose in 1).
Sample script here.
3) Use locale plugin action (SL4A) or application shortcut action (Script Manager) in Llama to run your script.

Enjoy

 

[msurg]

Even with this option turned off LLama should know which area you are in, right?

In my case my WiFi SSID is Coconut and the area which Coconut is in is named as Home_Wifi.
When "Check for WiFi Networks" is checked LLama knows the area and shows as "Home_wifi". When it is not checked Llama shows it as "Unknown Area" while it is already connected to Coconut.

I am sure that Llama is aware of SSID name because events with SSID name (Coconut) trigger normally where events with area name (Home_Wifi) don't.

Fow known networks, regardless of "Check for WiFi Networks" option Llama should know the WiFi Network when it is connected to that network, right?

It is the same on rooted and stock SGS3 4.3 with Boeffla Kernel as well as on rooted and stock Nexus 10 4.4.3.

Any clues?

Anyone?

 

[buggy_droid]

@msurg

Even with this option turned off LLama should know which area you are in, right?

No. Llama will not know that you are in an area you defined with SSID (or with MAC address).
Llama will still know that you are in an area you defined with cell ID, though.
But, you already know that ↓.

In my case my WiFi SSID is Coconut and the area which Coconut is in is named as Home_Wifi.
When "Check for WiFi Networks" is checked LLama knows the area and shows as "Home_wifi". When it is not checked Llama shows it as "Unknown Area" while it is already connected to Coconut.

Fow known networks, regardless of "Check for WiFi Networks" option Llama should know the WiFi Network when it is connected to that network, right?

Correct. Llama is aware of the SSID you are connected to. You can run events off of the network you connected to/disconnected from.
However, Llama doesn't know that you are in the area you defined with the SSID (Why? Because you turned off the option).
Since Llama doesn't know you are in the area defined by the SSID, you can't run events off of entering/leaving the area.
But, you already know that ↓.

I am sure that Llama is aware of SSID name because events with SSID name (Coconut) trigger normally where events with area name (Home_Wifi) don't.

I am sorry but I really don't know what question you are asking.

 

[anon8164182]

@edithswanneck
It is possible

1) Install a script editor, either Script Manager, or SL4A.
2) Write a script to delete your files using the script editor you chose in 1).
Sample script here.
3) Use locale plugin action (SL4A) or application shortcut action (Script Manager) in Llama to run your script.

Enjoy

That sounds a bit over my head, although if it's as easy as the sample looks then I might be okay. Thanks for the help! I'll try and give it a go over the weekend.

 

[kaixokaixo]

Hey guys, just starting with Llama and having a problem which I realize is very basic. I want Llama to do the same thing Battery Defender does: turn off wifi when the screen turns off and then turn wifi back on when the screen is on (no, that's not all, wait for it). Now, I'm able to make an event turning off wifi when the screen is off, that's easy of course, and to turn it on when the screen is on - both events work. The thing is, I only want wifi to turn BACK on when the screen is on - only if it HAD BEEN CONNECTED BEFORE THE SCREEN WENT OFF; that is, I don't want wifi to turn on just because the screen is on and eat my battery when I'm on the bus or something. I hope I'm being clear. I'd very much appreciate your help!

 

[Olivier D]

Hey guys, just starting with Llama and having a problem which I realize is very basic. I want Llama to do the same thing Battery Defender does: turn off wifi when the screen turns off and then turn wifi back on when the screen is on (no, that's not all, wait for it). Now, I'm able to make an event turning off wifi when the screen is off, that's easy of course, and to turn it on when the screen is on - both events work. The thing is, I only want wifi to turn BACK on when the screen is on - only if it HAD BEEN CONNECTED BEFORE THE SCREEN WENT OFF; that is, I don't want wifi to turn on just because the screen is on and eat my battery when I'm on the bus or something. I hope I'm being clear. I'd very much appreciate your help!

With cell area conditions you can make Llama learn where you want the wifi conditions to trigger. If your trusted wifi your device connects to automatically is at work, when you're at work make Llama recognize the cells as your "at work area". It's close to what you want to do. And just to let you know, every possible conditions you can set up are in the conditions list. If it doesn't exist, then Llama cannot simply execute it.

 

[kaixokaixo]

Thanks for your reply. Yeah, I know all that, but I don't want wifi to always connect in certain locations, only to reconnect if the connection was broken by a screen off→wifi off action. Maybe Llama just can't do that, although that would surprise me given the multitude of the conditions and actions it offers...

 

[buggy_droid]

@kaixokaixo
If you want “only to reconnect if the connection was broken by a screen off→wifi off action”, then just let Llama know whether the connection was broken by this action or by you manually, then tell Llama to turn wifi back on only when it was broken by its action.
Easy, isn’t it?

If you are connected to a wifi network when the screen goes off, have Llama turn wifi off and set a Llama variable (name it whatever you want) =1. This variable will let Llama know that the connection was broken by its action. When the screen comes back on, have Llama check this variable, and have wifi turned back on only if the variable has a value of 1. Make sure to reset the variable =0 in the same event, or when you are connected to a network again. Otherwise, the variable stays =1 forever.

Any question? Let us know.

 

[edkate]

Hi guys,

I have been reading these forums for sometime now and I NEED your help!

I love Llama and I HATE Llama!
I am not a newbie with android phones...

I currently have this setup for Work:
Mon-Fri, 8-5, Vibrate (gave up on tower cells for Work area as they keep disconnecting)

EACH TIME there is a call, my phone switches to Normal and RINGS! It started to upset people in the office.

What could be the reason to it?


Normal, cottage, screen disable, wi-fi ...all works fine! except for WORK events.z

 

[buggy_droid]

Hi,
Could you post the details of the event and profile you are having the issue with?

I currently have this setup for Work:
Mon-Fri, 8-5, Vibrate (gave up on tower cells for Work area as they keep disconnecting)

EACH TIME there is a call, my phone switches to Normal and RINGS! It started to upset people in the office.

What could be the reason to it?

 

[edkate]

Hi,
Could you post the details of the event and profile you are having the issue with?

Hi,

thank you kindly for your help!
I use Quiet @Work Event and Work Profile
I have attached these images

 

[raino]

Hi,

thank you kindly for your help!
I use Quiet @Work Event and Work Profile
I have attached these images

I have a similar event (minus the Bluetooth action,) and the only difference is that under Conditions, I have days (just like you,) but unlike you, I have time nested under the And condition. My event works 100% of the time, so why don't you give it a try?