OpenMoko – Thomas Woodhttps://blogs.gnome.org/thos
My WeblogTue, 03 Sep 2013 13:45:45 +0000en-UShourly1https://wordpress.org/?v=4.9.8OpenedHand Newshttps://blogs.gnome.org/thos/2008/08/28/openedhand-news/
https://blogs.gnome.org/thos/2008/08/28/openedhand-news/#commentsThu, 28 Aug 2008 16:26:41 +0000http://blogs.gnome.org/thos/2008/08/28/openedhand-news/We just updated our website with some exciting news…
]]>https://blogs.gnome.org/thos/2008/08/28/openedhand-news/feed/15Openmoko Freerunner Test Applicationhttps://blogs.gnome.org/thos/2008/07/01/openmoko-freerunner-test-application/
https://blogs.gnome.org/thos/2008/07/01/openmoko-freerunner-test-application/#commentsTue, 01 Jul 2008 13:18:16 +0000http://blogs.gnome.org/thos/2008/07/01/openmoko-freerunner-test-application/Continue reading Openmoko Freerunner Test Application]]>A while back I wrote a little script in Python to test some of the new features of the Openmoko Freerunner. Several people have requested the source code, so I’ve cleaned it up a bit and made it available here: http://folks.o-hand.com/thomas/openmoko/gta02.py

There are a couple of items on the todo list and I’m sure anyone with more decent Python skills than me could do a fair amount of cleaning up with it. However, it works and is useful at least as a demonstration.

It requires python and pygtk.

]]>https://blogs.gnome.org/thos/2008/07/01/openmoko-freerunner-test-application/feed/3Contacts 0.9 Releasedhttps://blogs.gnome.org/thos/2008/06/06/contacts-09-released/
https://blogs.gnome.org/thos/2008/06/06/contacts-09-released/#commentsFri, 06 Jun 2008 16:38:34 +0000http://blogs.gnome.org/thos/2008/06/06/contacts-09-released/Continue reading Contacts 0.9 Released]]>
Plenty of bugs fixed in this version. I am hoping to use this as the release candidate for version 1.0, so please send in any updated translations either to me (thomas at openedhand.com) or attach them straight to bugzilla. Also, I haven’t fixed many Maemo issues because we don’t really support the Maemo version (Maemo already has an address book anyway…). However, I’m more than willing to apply patches if people are able to supply them.

I’d like to add a special thanks to Adrien Bustany and Gilles Dartiguelongue for their patches that I’ve included in this release. If anyone else has any (small) feature of bug fix they would like to see done before 1.0, now is the time to start working on your patches!

Overview of Changes in 0.9 (since 0.8)

Bugs fixed:

139: Contacts does not exit cleanly, leaves socket behind

169: horrificially non-obvious choices of field names

224: Search chokes on non-ascii chars

275: tab key behavior inconsistent

305: Available labels for email are insane

306: Better location labels for us stupid Americans

308: No way to view “unfiled” contacts

309: Groups dropdown in main window not alpha-sorted

310: Contacts does not create “file under” field, not usable in Evolution

318: Do not show fields that are blank

338: Possible to add duplicate groups to a contact

339: Keyboard shortcut conflicts

341: Unexpected triple-click behavior in Name/Groups display

368: Should import concatenated vcards

489: Missing field definitions in Contacts.

492: Only installing 26×26 icons when building for Maemo platforms.

659: New contacts do not have a N: field – my mobile reject them

774: Fails to build from source under Ubuntu Hardy

808: All vcards for companies are displayed as ‘Unnamed’

885, 42: Attributes not sorted in view mode

888: Contacts segfaults when provided with incomplete options on command line

]]>https://blogs.gnome.org/thos/2008/06/06/contacts-09-released/feed/4Opkg Memory Cleanuphttps://blogs.gnome.org/thos/2008/05/21/opkg-memory-cleanup/
https://blogs.gnome.org/thos/2008/05/21/opkg-memory-cleanup/#commentsWed, 21 May 2008 13:59:07 +0000http://blogs.gnome.org/thos/2008/05/21/opkg-memory-cleanup/Continue reading Opkg Memory Cleanup]]>Last Friday I decided to use Valgrind to check the memory usage in opkg and discovered that it was leaking quite a substantial amount of memory.

Over the last two and a half days I’ve been fixing all the memory leaks exhibited by running my libopkg_test application. I have reduced the directly lost and indirectly lost memory to 0 bytes. The reachable memory at exit has been reduced to 29kB (down from ~13MB), with the ﻿﻿remaining blocks belonging to libgpgme and libcurl which does not appear to be freed by their
respective de-initialisation routines.

Having had such a detailed look at the code, I am fairly certain further optimisation work is possible in terms of both memory usage and speed.

Some interesting statistics:

I’ve add some 65 additional free and deinit statements

… of which 52 are additional free() calls alone

18 files changed, mostly in libopkg, but also one in libbb

There where a total of 184 lines inserted and 25 lines deleted in the full diff

I used Valgrind’s memcheck tool to help identify the leaks and massif to visualise the memory usage. It seems the Valgrind authors have remove the postscript output from massif in favour of an ascii chart. I’d be interested if anyone knows a way to display the massif output in a more graphical (non-ascii) way.

N.B. The scales on the two graphs are different, so be sure to read the axis when comparing!

The two peaks in the graph represent the parsing of the repository data into a hash table. In my test application, the repository data is updated from the feeds, so the package lists are re-parsed. Previously, the main de-initialisation procedure for opkg (which, I hasten to add, was inherited from ipkg) did not free the hash table of packages properly, which meant every time the package list was refreshed, the entire hash table of packages would be leaked. Had a user refreshed the package list several times in one session, it’s likely the device would very quickly have run out of memory.

I’m pleased to say that during my own testing I had no problems and it even works with WPA encryption. Good job Samuel!

]]>https://blogs.gnome.org/thos/2008/04/16/openmoko-wifi-driver/feed/1OpenMoko FreeRunner LEDs, etc.https://blogs.gnome.org/thos/2008/04/10/openmoko-freerunner-leds-etc/
https://blogs.gnome.org/thos/2008/04/10/openmoko-freerunner-leds-etc/#commentsThu, 10 Apr 2008 23:32:51 +0000http://blogs.gnome.org/thos/2008/04/10/openmoko-freerunner-leds-etc/Continue reading OpenMoko FreeRunner LEDs, etc.]]>Before I took my FreeRunner prototype along to Ole’s OpenMoko talk in London yesterday, I hacked up a little demo application in python/pygtk to display various new features in the FreeRunner (Wifi, accellerometers, LEDs). If you where there yesterday, you probably saw this live in action:

On my previous post OpenMoko post, someone asked about the LEDs on the FreeRunner. Obviously, you can’t see any proof of the LEDs in screenshots, so I took some very quick photographs:

If you have a OpenMoko build set up, you can try it out. Firstly you need to build the package and then rebuild the package index:

bitbake moko-gtk-engine && bitbake package-index

You may have issues if you have built this before, because I did made some changes to the repository that svn can’t handle very cleanly, so if you have problems, wipe your svn checkout and start again.

Here are some more screenshots of the theme running on the device. There are still some bugs with colours in a few places, so testing would be much appreciated.

I think the GPS icon is green because the GPS chip was on when I took the screenshots. I’ve been testing a couple of the peripherals on my GTA02 lately and I’m happy to report so far Wifi, GPS, accellerometers and the LEDs all seem to be working correctly. I got a fix from the GPS today which according to Google maps, was within 1 meter of my actual location.

]]>https://blogs.gnome.org/thos/2008/04/07/more-moko-gtk-theme/feed/9Brand New Moko Theme (Idea)https://blogs.gnome.org/thos/2008/04/02/brand-new-moko-theme-idea/
https://blogs.gnome.org/thos/2008/04/02/brand-new-moko-theme-idea/#commentsWed, 02 Apr 2008 21:55:23 +0000http://blogs.gnome.org/thos/2008/04/02/brand-new-moko-theme-idea/Continue reading Brand New Moko Theme (Idea)]]>Inspired by ScaredyCat’s discovery that the default GTK+ theme was much faster on the Neo1973 than the current pixbuf based theme (well, no real suprises there…), I set to work stealing his colour scheme and completely redesigning my Moko theme engine. This time totally optimised for speed and simplicity. It’s still a work in progress, but here are some screenshots to give a general idea:

Lines and other visual distractions are kept to a complete minimum. Although it doesn’t look that great on a desktop display, when it is on a 2.8″ 285dpi touch screen, it feels a lot better.

]]>https://blogs.gnome.org/thos/2008/04/02/brand-new-moko-theme-idea/feed/12OpenMoko Presentation in Londonhttps://blogs.gnome.org/thos/2008/04/02/openmoko-presentation-in-london/
Wed, 02 Apr 2008 09:13:16 +0000http://blogs.gnome.org/thos/2008/04/02/openmoko-presentation-in-london/UKUUG is hosting a talk by Ole Tange about OpenMoko next week in London (9th April). I’m planning to go along and take the latest GTA02 (FreeRunner) prototype if anyone is interested in seeing it in action. I’ll probably stick around afterwards to chat and grab some dinner.