Ethiopian Pregnancy Calculator Android Application

As I’ve mentioned before many of the Health Extension Workers (HEWs) we’re working with have trouble using the Gregorian calendar. Much of the work we’re doing with the HEWs depends on them having a good idea of the expected date of delivery for pregnant women. To help the HEWs calculate the expected delivery date, in Ethiopian date format, for the pregnant women they are working with, we have developed a small application which gives them the expected delivery date based on the date of the last menstrual period.

With the application the HEW can enter the last menstrual period in Ethiopian date format and it will give them and the pregnant woman the expected delivery date in the date format they are used to using in their day-to-day lives.

We’ve made the application available for anyone to download and use on their Android phone – just download the app and install on your Android smartphone.

I should give a big thanks to the developers of Joda Time (a java library for working with alternative calendaring systems) which made the development of the application so much easier!

Any feedback or comments welcome. If anyone is interested in developing the application further then we’re very happy to give access to the source code – just contact me :-)

Installing Ge’ez Virtual Keyboard on Android Devices

Update (2-Jan-2012): more up to date instructions can be found here: http://alexlittle.net/blog/2011/06/03/installing-geez-virtual-keyboard-on-android-devices/

Instructions for installing a Ge’ez Virtual Keyboard on Android:

  1. Root your device – exactly how this is done will depend on your device and you’ll need to look up on Google how to do this – note that rooting is not the same as unlocking your phone, rooting means you get administrative privileges to update system files, such as the font files we’ll update below.
  2. Download the files DroidSans.ttf and RootExplorer-v2.15.apk and copy these onto the phone’s SD card (or equivalent)
  3. Install and run the RootExplorer application and go to the sdcard folder
  4. In rootexplorer, find the DroidSans.ttf file and copy it
  5. Go to the /system/fonts folder and push the button marked “mount R/W”, the button will the change to be marked “mount R/O”
  6. Paste the DroidSans.ttf file into this folder – replacing the existing DroidSans.ttf file. Leave all the other font files as they are. It’s probably a good idea to make a backup of the original DroidSans.ttf file first, before you overwrite it. Just rename the original file to (something like) DroidSans.ttf.bak.
  7. Now restart the phone and the new font will be installed
  8. Now to install the keyboard, download the keyboard apk file
  9. Copy this to your phones SD card and install the application
  10. You should now be able to switch between the standard and Ge’ez keyboards. You may need to enable the keyboard by going to: Settings -> Language & Keyboard then select check the box to enable the new keyboard
  11. To find out how to switch between keyboards, watch our video:

We have tested this installation procedure on a few different phone models, though obviously we can’t cover every possible phone type and can’t guarantee it will work for every device. If you have any problems/issues then please post a comment. We’d also be very happy to hear that it did work for you!

Video Content Management and Streaming with Kaltura and Moodle

Through the elearning training we are trying to encourage teachers to make more use of video and other multimedia content in their courses. This presents us with several issues, mainly because most video streaming sites are blocked by the University (to save bandwidth). This means we either don’t include the videos or we download to run them locally. So far we’ve just been uploading them into the Moodle course, which is fine for relatively low numbers of videos (or for very short videos), but is soon going to become unsustainable. Also, we’d like to suggest video content teacher may wish to use – so it wouldn’t be appropriate to have these filling up the Moodle server.

One solution is to use a multimedia management streaming server, so over the last few days I’ve been testing out Kaltura. It’s an open source video content platform and has plugins for Moodle, WordPress amongst others.

Installation was straightforward enough on my laptop, once I’d got the necessary prerequisite packages installed and settings. Couple of issues I did come across:

1) On my first attempt at installation, it installed on the root of my webserver, so I was unable to access my other web applications. This was because I specified ‘localhost’ as the domain. I tried to figure out how to move to a subdirectory (see: http://www.kaltura.org/moving-installation-new-directory) but haven’t got that one figured out yet. So I just set up a new host (http://kaltura.localhost) and used this instead. So now I can access Kaltura and my original webapps, with out switching configurations and restarting apache.

2) When the prerequisites say that you need a mail server, it really does mean that you need one! After installation, when creating publisher accounts, the login details are emailed only – so there’s no way to set the password except by following the link in the email. I assumed I’d be able to reset the passwords manually and so the mail server integration wouldn’t matter to much. Given that this is just running on my laptop, I haven’t got a mail server running, so then had to set about trying to get one configured. Fortunately I found these instructions on how to configure postfix to relay through a gmail account on Ubuntu (I’m running 10.10). I set up a clean/default postfix installation and used the settings/instructions posted in the comments by Michael M. I used a ‘disposable’ gmail account, so that if something goes wrong, I won’t get blocked from my normal gmail account, but seems to be working well so far. It’s also good now that I can have emails sent for all the webapps on my machine.

So after I had these 2 issues resolved, I was ready to start having a play. All seems to be working well, although I was hoping that people would be able to browse the uploaded content without having first logged in. I guess we’d just need to create a generic account. If anyone knows how to set this up then please let me know – or if there is a generic Kaltura content browser application that I could use?

I tried uploading a few flv and mp4 videos to embed onto a webpage, and seem to work well. A little slow on my machine, but then my netbook probably isn’t designed to be a media processing and streaming server!

My final experiment was to look at the Moodle plugin, unfortunately I had a few more issues with getting this working. When trying to register the module in Moodle, I kept getting the error that ‘Your Kaltura registration failed. Missing KS. Session not established’ when trying to enter the url, username and password for my Kaltura server. After a bit of investigation I found it was a bug with how the partnerId was(n’t) being passed. I found a hack around this, see: http://www.kaltura.org/config-moodle-mod-moodleadmin-page, but it’s not pretty!

Now I have the option to add a video resource in Moodle directly from my Kaltura server, or so I thought I had, currently whatever I seem to search for (tags, video titles, categories which I know exist in the account I have) returns no results. Next step is to try and figure out why I can’t seem to find any of the videos I have uploaded…

Testing alternative thin-client server solutions

The thin client solution we currently have running in Mekelle is based on using OpenSolaris and we have a variety of terminals – a mixture of SunRay 1′s, SunRay 2′s and Nortech clients. Using sun ray session server, the sunray terminals are performing well, but when we have the labs full of students, the Nortech terminals are significantly less responsive. There are a number of possible reasons for this, the protocols used, the network amongst others. There is a huge range of other configurations and technologies we could use to provide a robust and scalable thin client architecture.

I’ve spent a few days this week in Barcelona with Cast-Info investigating their Desktop4All solution, which we’re looking to trial as an alternative to the OpenSolaris setup we currently have. Goitom, one of the phds students from Mekelle will spend the next few weeks based in the Cast-Info offices, learning how to install and set up the server system used for Desktop4All, with a view to installing this when back in Mekelle in a couple of months.

Desktop4All, based on Linux, is a set of integrated open source applications. It’s likely to produce a similar end result to the solution that we already have running with OpenSolaris, but the main advantage for us will be in the support and documentation available as a reference. Testing out Desktop4All will give us the opportunity to collaborate in the development and to investigate whether we get similar types of issues arising as we have had with OpenSolaris.

When we started the Digital Campus project, I think there was some concern over whether the students would need much training in how to use a non-Windows operating system, given that much (all?) of their previous experience of using computers/pcs was with Windows (usually XP). This has turned out not to be the case, given that many students have had limited time to become locked in Windows, we’ve found few issues with students being unable to navigate the interface or use applications. I suspect we don’t always give the students credit for their ability to adapt to new interfaces and systems (especially judging by how quickly they find their way to webmail, youtube and facebook).

Scroll to top