Hey all, thanks for your interest in mFakeCaller lol You all have such great ideas, let's hope somebody who knows how to do them all gets involved and does them

It took days of wrestling with autobuilder to get the project into extras-dev, but during this time I went ahead and created a few of the other features I was going to wait on. For example, user selectable caller names, caller images, backgrounds, and ringtones are currently in the initial release already. The trick is you have to set these when calling the application directly, not from clicking the icon. For example, here's a screenshot I tweeted a couple of weeks ago from my N900 using a panther image for the caller image and the background,



To make the 0.1 test version accept new values, you have to pass them to the application by calling from xterm or through a shell script. The shell script is great because then you can schedule it with alarmed

If anyone's interested in the method and not sure how to do it, let me know and I'll write a proper post on how to do it.

From my own testing, it seems a bit slow for the form to load and the ringtone playback starts a second or two behind the vibration. From chatting at the MeeGo conf, it appears that it might be a good idea to move away from forms to use QML for the user interface which should be quicker. Also the slow audio issue appears to be a well known gstreamer problem on the n900. It's annoying but not too bad, I might just have to learn to live with that.

You might have seen from the dev forum that me and QtCreator are falling out these days, once we're back on speaking terms I'll start rewriting the UI in QML just to see if there's an improvement. I'll start write a GUI front end to enable changing of settings from the icon click, that's going to be more user friendly for people than working with a shell script ofcourse.

There's also a problem with the application manager icon in v0.1, it's missing. Doesnt affect the application at all but you dont see an icon when in app manager. So i need to find out what's wrong wit that too. I think it's the base64 encoding in the file that went into autobuilder.