Tuesday 24 December 2013

Merry Bugfix Christmas Llama

This version fixes a few issues with Llama.


  • Fixed bug caused by weird Bluetooth device names
  • Ignore cells that are Integer.MAX_VALUE, since they are clearly wrong
  • When a profile is locked until a certain time, and then you relock to that profile again, Llama will just adjust the unlock time, rather than cancelling the lock altogether.
  • Updated Russian translations


Wednesday 16 October 2013

Little Llama Update

Some small updates... nothing too exciting!

  • Ability to stop queued sounds with the play a sound action
  • Headset condition can differentiate between a headset that has a microphone or no microphone
  • Can now import from a Llama URL, since clicking Llama links is flakey :(
  • Updated Russian translations

As always, backup your data before installing test versions


Monday 12 August 2013

Market time!

It's market time again! ...or at least it will be in a few hours for 10% of you. Staged roll-outs are lovely. Of course, if you're reading this blog your probably aware that you can get the exact same version from the link below. This version contains all the stuff from the previous versions as well as....


  • Updated French translation
  • Nexus 4 -1:-1:-1 cell ID between every cell change fix



Monday 29 July 2013

Llama flight

In Android 4.2 airplane mode was made a system setting, so Llama couldn't change it without root access. After 4.3 Llama can no longer use normal API calls to send the broadcast that needs to be dispatched after changing the airplane mode setting. Therefore, Llama now sends this broadcast using root access and the am command.

Here's an Android issue tracker item that's related.


  • Fixed flight mode in Android 4.3 (still requires root access)
  • Added Brazilian translation
  • Updated French translation

As usual, backup your data before installing test versions.


Monday 24 June 2013

Llama vs S4: Round Two

I've had some luck getting Llama to play nicely with the Galaxy S4's default messaging app notification tones. Llama will now try and detect if your phone is an S4 and apply sound profiles slightly differently. This is exposed as a tickbox in Llama's settings named 'Use deprecated vibrate API'. Galaxy S4 owners should have this setting unticked. Llama should set it automatically the first time you run this new version. If you have a Galaxy S4 and it isn't ticked please send me your phone's 'Model number' under About in your phone's settings app.

In Android 4.1+, the setVibrateSetting was deprecated. This API was great... it allowed you to set vibrate differently for ringer and notifications. It also seemed to turn off notification vibrations globally, depending on how an app would read this setting. Anyway, it's gone now... but Samsung's stock SMS app must have still been reading its value and then interpreting the value differently to every other app under the sun. If you don't have a Galaxy S4, you can just leave it ticked and Llama will behave exactly as before.


  • Galaxy S4 notification fix (hopefully)
  • Updated German and spanish translation

Please export and backup your Llama data before installing test versions!


Thursday 23 May 2013

Traditional Llama

Llama now speaks Traditional Chinese. Thanks to Hector Lin! Not much else to report really. I still don't know why the S4's built-in SMS app notifications don't play nice with Llama, but I do know that it doesn't affect every S4. I can only suggest you install it and see how you get on.


  • Added Chinese (Traditional) translations
  • Updated Japanese translations
  • Notification mode can now be set to normal for Android 4.1+

As usual, backup your settings before installing test versions just in case you have to go back to the Play Store version.


Wednesday 8 May 2013

Llama vs S4

Something on the Samsung Galaxy S4 breaks horribly when Llama is installed, but I have no idea what. That's why it ain't on the market. You're welcome to install the versions from the blog posts below and give it a try to see if you have any issues.

From various emails and bug reports this is what appears to happen.

  • After installing Llama, only the SMS app is unable to play notification sounds.
  • Other apps (e.g. Gmail) are able to play notification sounds.
  • Uninstalling Llama does not fix the problem, nor does playing with volume settings nor reassigning a notification tone in the SMS app.
  • Everything goes back to normal when Llama is uninstall and the phone is restarted.

So, what has Samsung (or I?) done to make all this not work? I have no idea. It'd be great if someone with a Galaxy S4 could lend a hand in diagnosing what's going on.

I'd need a system-wide dump of the logcat. You'll either need to be rooted and install something like CatLog, or install the Android SDK on your PC, connect your phone via USB then run adb logcat. Get in touch if you can lend a hand: kebabapps@[everyone's favourite Google-provided email domain]


Wednesday 24 April 2013

Llama bug fix

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


  • 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 ;)


Sunday 21 April 2013

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.


  • 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)

Wednesday 10 April 2013

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!

Wednesday 3 April 2013

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...


  • 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.


Monday 7 January 2013

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.


  • 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.