You'll get it probably next week from Nokia Store. I'm uploading the new version there tonight.

ProfileMatic version 1.6.0 has been pushed to Nokia Store.

Here's the changelog as far as I can remember:

- Multi-rule activation
- Active rules are shown in main page
- Stand-by screen action (contributed by Ferdinand Mayet)
- Background connections action
- Idle condition
- Custom action for when rule is deactivated
- Custom action has test button for testing
- Location by cell id has timeout option
- Shows warning if ProfileMatic has lost the credentials needed for flight/power saving mode. Reinstalling is needed then.

Special thanks to Ferdinand Mayet for his contribution for stand-by screen! And many thanks to all who beta tested the new version.

You rock !!! Thank you very much . I wanted the background connections and multi-rules very badly

Thanks for update!
This is a same version like 1.6.0-beta3 ?

There is many small tweaks and fixes in the final release.

Thanks, we need to remove beta before?

No, Nokia store version will install fine over the beta.

Only for the betas must store version be removed first. Nokia as origin is more important than origin from me, or something like that.

My Nokia Store is still only showing 1.5

Yes sorry for my vague words. I sent it yesterday to Nokia store, but they have to approve it before it becomes visible. This can take 5-7 days, but hopefully it's there during next week.

I will post an update when store informs me they've approved the new version.

Now that 1.6.0 is submitted to the store, I want to start looking at NFC support for the next version.

First things first, can anyone recommend me a good place to buy empty tags to use with N9?

I've only taken a cursory look at the NFS APIs available for N9, but here's my current idea how ProfileMatic would support NFC:

- A new NFC condition
- The condition view would be similar to the current WLAN condition and Cell location views. Ie. you could collect number of NFC tags under one rule.
- The matching would be done by the tag's "uid". This is supposed to be "universal identifier" so it should, with high probability, be unique for every tag. I'd think that's good enough, or is there more conditions for matching needed?
- The condition with NFC tag would activate the rule for the duration that N9 is kept near the tag.
- Optionally, and highly likely (because I would have need for this ), I'd like to implement it also as a "toggle". Ie. when bringing N9 near the tag, it will toggle the condition on. When bringing it again near, it will toggle the condition off. This would require in the UI a manual way to release the on condition, as it's too easy to forget toggle the condition off.

That's in short my current plans. I want the support to be as simple and focused as possible. This means for example that I wouldn't want to put any NFC tag writing support into the application - there's apps for that already I think? Also I'd like the matching to be by one attribute only. The "uid" seems the intuitive one.

Please let me know if such a scheme would match your needs, and if not tell me more about your use case.

Thanks.