Llama bug fix

This version fixes a bunch o bugs from the last version.

Llama.1.2013.04.24.2337

• Fixed Android Intent action bug
• Fixed event filtering tickboxes not working
• Event filtering shows a message when you have no conditions
• Event filtering works with conditions stashed in an AND/OR
• Event history tells you what conditions triggered an event in an AND/OR, rather than saying the AND/OR itself

As usual, back up your settings, cos I can't code properly ;)

Download

Llama Triggers

Llama's events fire when all of the conditions in an event are true (i.e they show as green), and one of those conditions caused a 'trigger' to occur (if you're quick you may see this as a green underlined condition in Llama's Events tab). A trigger is something like the moment you enter your home, or the moment it becomes 7pm. However, there are times when you'd only want Llama to run the actions when a certain condition is triggered.

Llama now lets you decide which triggers can cause an event to fire. You can modify this under the 'advanced' part of the event editor. If you deselect a condition, it will still be checked to see if the event should fire, but it will never cause the actions to be run (another condition will need to do that). By default all conditions added to an event will act as triggers, unless you edit the event to say otherwise.

...and there's some bug fixes and smaller changes in this version too.

Llama.1.2013.04.21.1651

• Trigger filtering for events
• Fixed possible crash caused by airplane mode condition
• Fixed airplane mode condition not working from the last version
• Intent action string extras can now use variable names. Use double-hashes. e.g. ##variablename##
• Llama home-screen shortcuts will no longer show any previous Llama activities that you may have had open (Android 3+ only). You'll need to recreate your shortcuts, as the flag for this is stored by your launcher, not Llama :'(

This version tweaks the event saving format of Llama, so backup your data before moving to this version just in case you have to uninstall it.

Download (fixed, now has all languages again)

500,000 Llamas

Just a quick post to say thanks for the Llama love over the past two years and a bit, and for recommending it to all your friends.

Llama's download counter has just clicked over 500,000, which is rather awesome... and also making me think I should have charged a quid for it. Ah well! :D

Here's to many more happy years of Llama-ing, cheers!

MCC Llama

A few months have passed and I figured I should actually write a blog post. The main change in this version is Llama can now let you make events bassed off MCC and MNC. These are Mobile Country Code and Mobile Network Code, and lets your identify the phone network you are connected to. This will allow you to determine which country you are in, as well as a different way to check if you are roaming or not. Since I live in London, far away from any border, I haven't been able to test it 'in the field' (maybe I should go on holiday more?), so any feedback on how well it works is appreciated!

There's a few other changes too...

Llama.1.2013.03.29.2027

• MCC/MNC condition
• Added 'contentDescriptions' for accessibility, so blind people can use Llama easier
• Google Play bumped up their maximum in-app purchase price, so there's a new crazy donation option. If any one ever uses this:
  • You have far too much money!
  • Thanks! ;)
• Fixed scrolling problem in SignalLevelCondition
• Less crashy on ROMs with weird WiFi permissions
• Wireless charging added to charging condition
• Updated Japanese, Russian and Polish translations. Thanks guys!
• Keyboard now forced open in more text fields
• Added android.permission.ACCESS_SUPERUSER permission, which has a scary message on the Play Store install page. This may get relegated to something like the CALL_PHONE build of Llama, since I can predict the influx of 'OMFG WTF SUPERUSER' comments. Llama won't request it unless you use an action that requires it, so we shall see...

As usual, export your Llama data before installing test versions.

Download

Signal Strength Llama

The version contains one new condition and a handful of bug fixes.

The documentation for GSM signal levels is pretty good. However, I can't say the same for CDMA or TDMA networks. If your phone is a CDMA or TDMA phone please let me know how you get on with the signal strength condition.

Llama.1.2013.01.07.2205

• Roaming condition is alive
• Change ringer/silent/vibrate setting in profiles can be used without volumes again
• Wifi MAC address beacons also store their network name. Looks ugly for the mo.
• Devices with dodgy WiFi drivers/software no longer crash Llama because of the UPDATE_DEVICE_STATS permission problem. Instead, Llama will show an error notification.
• When checking if volumes have changed, Llama will now wait a bit after the call ends, because some phones were still reporting the wrong volume levels.
• Stop learning an area if it's deleted

As usual, back up you Llama data before installing test versions.

Download

And we're back.... for now

If you have a system volume defined in one of your profiles Llama will now set it before doing anything else. This means the system volume is likely* to get changed by your ringer volume if you have one defined in a profile. It also means that when Llama asks for silence, it won't then be forced into vibrate mode by the system volume setting.

* ringer and system volume are now linked for some versions of Android and some ROMs

If you have problems, email me. If lots of you have problems Llama's going to hibernate again until everyone and their phone is happy :)

Llama.1.2012.12.29.1412 is on the Play Store (in about 30 mins to 1 hour.)

Llama's having a quick break

Llama's off the market for now while I investigate a pain-in-the-butt problem involving silent mode, vibrate mode and the dreaded System Volume level.

Changing the system volume in Jelly Bean now changes the ringer volume. I can't find anywhere in the Android SDK that documents this, which is rather infuriating. Feel free to look through here and see if you can spot it.

Changing the ringer volume (or the system volume since they are now related) will flick a silent phone to vibrate, even if the new ringer volume is zero. So everyone that previously had a fairly sensible 'set system volumes to silent' may now find your phone will vibrate.

Fun fun fun.

Why were previous versions of Llama behaving? Because it was naive, and literally dumped out the values from a profile to the AudioManager. Now Llama tries to be slightly smarter about setting the values... e.g. if you choose a Silent ringer mode, it will set the volumes to zero, rather than the values you picked from the profile. However, this exacerbates the problem described above.

Anyhew...

I think it's fixed in this version, but no doubt there's some manufacturer out there that has tweaked their version of Android to have a system volume. Ideally, I'd want to hide the system volume from the profile editor if you're running Jelly Bean, but since there's now no way of knowing if a device supports system volumes or not it will have to stay :'(

I'll put this version on the market tomorrow morning, when I can fire-fight any more stupid that may arise.

Llama.1.2012.12.29.0128

Download

It'd be awesome if you could let me know if the above version works for you... ideally activating a loud, silent and vibrating profile, and letting me know if the volume icons changes to the correct one. Cheers!