All of mine are gathering dust (no they are not, they are safely stowed away) for years now, let me check which models I actually have left, from memory there's a 6000 (not clamshell), a 3000, and a 750 w/ expanded battery. Will fill out the details, when I'm home.

Salve, offenbar fehlen Dir die Schriften. Wenn ich mich richtig erinnere (mein Engagement mit Opie ist schon 4 Jahre her), sind das Pakete, wie qpf-qte, qpf-freemono, qpf-freeserif. Wenn Dein Opie schon ttf benutzt, dann eben ttf-dejavu. Wenn Du die wieder nachinstallierst und neu bootest, solltest Du (hoffentlich) wieder etwas Text sehen.

Viel Erfolg,

:M:

Interesting. That may allow porting my iPhone Retro Player Apps (SidPlayer Pro, Module Player, Pokey Player) to Android.

Ah, too bad. Of all choices, Android is the worst one as it's cannibalizing the Linux ecosystem. Then again, if you're happy with it...

Yeah, that's quite funny, especially considering that Open Embedded (as in the build system) has nothing to do with it. OE is now really an overloaded term

Indeed we all hope that Qi will produce more connected devices eventually... I for one can't wait for a decent free SmartPhone platform...

Hi Oliver, how are you? The recent Openmoko redundancies have left freesmartphone.org without funding, so we're currently looking for alternatives, but other than that everything is ok. I will write a book about Vala this summer and hopefully by the end of this year we have new funding and new hardware on the horizon... (always dreaming, you know)

Thankfully, there's more to OpenEmbedded than just Angstrom. You can tailor it to your liking.

(sales-pitch) This is what freesmartphone.org tries to change. One middleware, multiple application layers on top.

In the age of Android, it's a tough job to work on something like that, but alas they're still enough believing in freedom here.

Hope all is well for you.

Hi Guylhem, hope you're covered from your terrible accidant! Congratulations on your Ph.D, Doc :-)

Yeah, it's fun with the SIMpad. Almost a year after I resigned from OpenSIMpad.org, some folks relaunched the site and joined OE to work on that. I'm glad to see that happening although I no longer have such a device.

The SIMpad was groundbreaking, ahead of its time. Alas, SIEMENS really screwed up marketing that.

All the best.

Hi Speculatrix, thanks for your kind words.

The background on this issue is twofold:

First, I had to realize that I did not have enough time to further contribute directly to Angstrom. Instead, I'm focusing more on getting the metadata in OE right for all kinds of distros -- e.g. the "minimal" one.

Second, I have some personal quarrels with the project leader which are no longer bearable, so I figured I might as well resign to keep my blood pressure under control.

I'm still pretty much around in the community. I work on OE, I work on freesmartphone.org middleware (kindly funded by Openmoko Inc.), and doing my share to bring Linux on all kinds of mobile devices forward.

Since moving more towards smartphones, my Zaurus models only gather dust, but you know, there's only so much hours per day. Still I think that what we do in the freesmartphone.org project, SHR-project, and last but not least OE, benefits also the Zaurus family.

Cheers,

Mickey.

Indeed. It was _really_ awful, but then again... some folks can do art with fewer pixels

Still here, but not very frequently. All my Zaurus models are boxed so that they don't gather dust. Openmoko has kept me more busy than I have ever expected. Still doing lots of work on OpenEmbedded, which has become really huge.

You could make an OE recipe that grabs your libc from your toolchain and packages it up into an ipkg.

Unfortunately not. Nokia goes much further than SHARP, but they still have a bunch of binary only components in their firmware -- which is especially unpleasant for 3rd party distribution builders.

Well, the pdaXrom could be a dedicated team/distro in OE and would benefit from lots of commits that have the same goal -- improving the Linux experience on embedded devices. I don't think anything would have to be lost... except the build system, of course

I know it might be heresy for you guys, but I'm just an old missionary, you know... So forgive me, but

Please consider using OpenEmbedded and joining a huge, vibrant team.

The experience you guys have with X11-focused environments on PDAs is great, it would make a huge difference to the Angstrom initiative.

Now go and flame me for suggesting that

GTA02 will be released early next year, however my realistic assumption (not wearing any OpenMoko hat, but just being a member of the FOSS community) is that it may as well take 12 to 24 months before OpenMoko as a software-stack has the majurity to compete with the big players. Think about how long GNOME and KDE took. I think both desktop environments are just _now_ slowly starting to innovate and leaving their competitors behind.

In few months you will be able to use the current OpenMoko stack on a day-to-day basis, but it's far from the platform for innovation that I have in mind -- and on my personal roadmap (which is not necessarily shared by OpenMoko, Inc.).

I can't see anything in Android compromising OpenMoko's goal. OpenMoko is for people who want to be able to experiment, able to replace anything on their phone, able to have full control over every software component. Android won't give you that. Android may as well be the next Symbian, but it's not sharing the same goal of openness as OpenMoko is. OpenMoko has some years to go until it's ready for mainstream market, but I think until then, we can have enough fun with R&D labs, creative people, geeks, and vertical markets.

Groucho referred to config.log in the source directory of gconf-dbus. You may look there for more information why this particular autoconf test has been failed. Again, I advise using upstream OpenEmbedded instead of the forked and outdated Familiar version...

OpenEmbedded can build Angstrom images for the Nokia770 where a lot of things work. It just needs a bit of love.

Check whether dbus has been built. Nearbye, Angstrom (built using 'the real' OpenEmbedded) may be a better choice.

Depends on the actual packaging. If properly packaged, then you could use update-alternatives for the actual python binary and have python25 is /usr/bin and this reads from /usr/lib/python2.5/*.

As far as I remember, the GPIO where the hinge is connected to can't be configured as a wake-up source.

Up again.