I can’t claim to have figured this out by my self…
Source link

EDIT: For whoever had the problem with blue video output – You don’t have to deactivate hardware acceleration. When using Nvidia drivers and VDPAU you should locate libflashplayer.so and run the following command in its directory:

sudo perl -pi.bak -e 's/libvdpau/lixvdpau/g' libflashplayer.so

locate libflashplayer.so
Mine were located in: /usr/lib/flashplugin-nonfree/

Welcome to this short summary of useful commands for X11.
I have written it to avoid having to resort to googling next time I forget Xephyr.
Also it might be interesting for others as well…

Servers inside your X11 server

xoo with a ipaq3800 skin

Why would you want to run a X11 server on your X11 display

Well for starters you might want to try out your UI on a device with a lower screen resolution than your development machine.
You might also want to code an application running at a different colour depth than you desktop, maybe a rotozoomer in 16bit
You may also simply want to try out a couple of applications on a low res. screen prior to buying a table with a low res. screen…

Xoo

A wrapper for xnest and Xephyr that allows one to create a skinned X11 display.
You can even have working buttons that you can click.

sudo apt-get install xoo

Xnest

Haven’t used it myself.
As far as I know Xephyr has some advantages in the supported extensions over xnest

sudo apt-get install xnest

Xephyr

Based on the kdrive xserver supporting extensions such as render and composite.
xnest package actually recommends this package over it self…

sudo apt-get install xserver-xephyr

Utilities and tools

Xpra aka. “screen” and turbo for X11 applications

Screen is a wonderful tool for command line tools.
Xpra gives you the same capacity to leave the program running on the remove even if you close/losses the connection.
Also xpra “compresses” the stream of X11 commands by using a different protocol than X11, reducing the problems caused by low latency connections.

sudo apt-get install xpra

And as with my QNAP I would like a filter that prevents most of the dust in my living room from entering the Proliant.
Before I build a filter out of a piece of cardboard and some paper towel for the QNAP I have once had to vacuum it due to a slight build-up of dust.
After the filter the inside remained a lot cleaner and I only had to clean/replace the filter, a lot safer and easier than cleaning the whole thing.

If some paper towel works for a QNAP then why not a Proliant?
Anyway here is a tiny How to “build” a simple and cheap filter for a Proliant N40L

In order to do that you need to remove the lock this involves: Removing the screw holding the metal “bar”, then removing the nut that holds the locking mechanism in place.

You can now remove the plastic covering the metal door by carefully releasing the thee plastic hooks at the top of the door.

Next you need to cut a 19×14.5 cm piece of paper towel.

I removed half the layers of paper to keep the pressure drop across the filter low.
Last time around I used paper towel with only two layers which was much easier to separate than the 4 layer stuff I used this time…

Now you need to tape the paper towel onto the outside of the metal door.
If the Proliant is running and the door is closed the paper will be held in place by suction, making it a very easy job indeed.

Cut a hole in the paper towel for the locking mechanism.

Put the plastic covering back on, hiding the filter.

Reinstall the locking mechanism.

Close the door and admire your handy work while drinking your favourite beverage.
(Beer can be used during this step)

So I could either keep the old N6100, buy a new low end feature phone or get a fancy smart phone.

Until recently I thought that I would end up buying a new feature phone.
But disappointment in the evolution of T9 (none) on dirt cheap phones and the continued desire for a computer in my pocket lead me back to smart phones.

So I ended up ordering a GeeksPhone One.

Just for completeness some pro/con thoughts about the alternatives.

Nokia N900

Pros:

• Very cool hardware (it even got a hardware keyboard).
• Runs a Debian based distribution.

Cons:

• Quite expensive.
• Nokia left me for dead with the Nokia 770 tablet (NO I will never forget this).
• Closed source just like the Nokia 770 (I can’t build a firmware for it, see above).
• Maemo 5 has a relative small user base.
• Maemo 5 is dead? Long live MeeGo?

IPhone

Pros:

• Good question… highest sex appeal perhaps?

Cons:

• Steve (Apple) wants to decide how and for what I use the phone.
• Oh, and it is expensive.

Android phones (HTC, Samsung, etc.)

Pros:

• Decent to very nice hardware.
• Large user base => lots of applications.

Cons:

• “They” want the same control as Apple.
• Not free and hacker friendly.
• Can be quite expensive.

GeeksPhone ONE

Pros:

• Decent hardware that includes a hardware keyboard.
• Rather cheap, they had them on sale for €159 (out of stock right now).
• No need to “root” the phone as it is not locked.
• You can build new firmwares for them (rmcc has created quite a few new firmwares).
• They encourages people to do so.
• As it runs Android there should be a large selection of applications.

Cons:

• Firmware contains closed binary blobs (as far as I know)
• Currently only runs Android, no Debian, SHR or FSO yet.
• Open schematics and chip documents would have been nice.
• The community is VERY Spanish, “Google Translate” is really a useful tool here.
• The “One” is soon to be replaced by two new models.
• Why god, why did they have to write “GeeksPhõne” on the back of the unit?

Copyright Peter Ward and licensed for reuse under this Creative Commons Licence

RIP

Before or during the holidays I noticed that projects.openmoko.org were down.
As no one seemed to take action I decided to attempt to locate the person(s)  that had the power to do anything about the problem…
Long story short, I eventually received the following e-mail:

---------- Forwarded message ----------
From: Harald Welte <laforge@gnumonks.org>
Date: Wed, Dec 29, 2010 at 1:00 PM
Subject: Re: openmoko.org services / projects is now down..
To: "Risto H. Kurppa" <risto@kurppa.fi>

On Wed, Dec 29, 2010 at 12:41:47PM +0200, Risto H. Kurppa wrote:
> Hi Harald!
>
> There has now been some reports about projects.openmoko.org being down..
>
> I this permanent? If yes, it'd be good to create a forward to take the
> users to a wiki page telling what's happened and why. If it isn't
> permanent, some kind of announce would be useful. As far as I know,
> there is code that the developers / users would definitely want to
> backup before removing the whole projects.openmoko.org.  

The change is going to be permanent, as the current installation is
unmaintained for about a year and poses severe security risks.

Anyone who's interested in backups should contact gismo and/or roh, they will
then provide snapshots of the requested information (e.g. cvs/svn/git
repository)

If somebody steps forwared to take the existing information and put all of the
repositories + downloads online somewhere (read-only) for historic reference,
I'd be more than happy to provide the respective account/data.

Regards,
 Harald

Which is also available at: http://lists.openmoko.org/pipermail/community/2010-December/064043.html

Maybe not entirely dead yet.

I am not subscribed to that particular mailing list, but I noticed that Alfa21 might have stepped forward to host and maintain it…

Running my own

It also made me reconsider running my own private FusionForge
(I am quite happy with SourceForge except for the fact that it is hosted in the USA, which has silly software export laws)

Also an idea struck me.

Wouldn’t it be nice if there existed a sort of BitTorrent for hosted projects?
Something that enabled anyone to set up a “project”.
The bug tracker, Source control, everything should then automatically be “cloned” to the network of hosts.
This would allow the network to help load balance the setup.
But most importantly if the original host dropped the interest in the hosting/project the network could ensure the continued availability of the software.

Well one is allowed to dream…

YouTube video of strokerecog

In yet another shameless self promotion/public information attempt I bring you a video of strokerecog my “handwriting recognition” keyboard application.

Unlike initially for the matchbox finger friendly theme there is already a .deb package that can be used to install stroke-recognition on your phone.
You may download it from HERE.

However the stroke-recognition-x11_0.29_armel.deb package is not as polished as the matchbox theme .deb file
(The theme is by now installable using apt-get install)

YouTube video of the theme

Edit: The package is apt-get able from the official  pkg-fso.alioth.debian.org

The package is not include in the official  pkg-fso.alioth.debian.org repository yet, but you can download the files HERE.

I still need to figure out if is okay that the changes file is labeled as i386 or what I need to do differently.
But at least it passes “lintian -i -I –show-overrides –pedantic matchbox-theme-finger-friendly_7svn_i386.changes” without any problems.

YouTube video of the theme

Finger friendly window manages presents special challenges mostly caused by the need for larger controls due to inaccurate finger tapping.
On small screen devices like mobile phones this presents another challenge, we do not want to use too much of our small screen for controls.
On the Neo/Freerunner this is made even more complicated as the bezel around the screen makes it hard to tab the edges.
And the edges are where we normally put the controls.

But Nokia seemed to have succeeded in making the Matchbox window manager finger friendly on the 770.
And while the 770 does have a larger screen, why not our Freerunner?

I am not graphics artist so I am pretty sure that it could have been made to look nicer but here is what I have done.

• The top window border have been enlarged to 48px, no other border needed.
• The window chooser and close buttons have been made larger and moved away from the left and right edge.
  (But the entire area left or right of the icon can be clicked)
• Only a small area above the window chooser displays the window title (also activates the chooser)
• The font size used for the chooser and application launcher has been increased to allow using them with your fingers
• The remaining space is used to “dock” the matchbox-panel , so it does not have to use valuable screen estate.

There are still plenty of things that remain to be done most importantly create a Debian package to allow others to install the theme easily.

And since there MUST always be one window open to show the  launcher I should probably while(true) spawn either zhone
or some sort of home window in .xsession.

And something must be done to the launcher, as it does not show half of my installed applications including any terminal (shiver), I could either:

• Fix the launcher config files, I do belive that can be done…
• Remove the launcher from the panel and replace it with the “home window” thing.
  This would also free the panel space for extra notification icons

Photo courtesy Photos8.com

Ok, maybe not the killer but then at least the delayer.
But it did get your attention right?

As usual I am struggling just to get the phone working as a receiver of SMS messages.
Trying to figure out where gsm0710muxd writes it log files by default I fetched the source.

I know it is sort of deprecated but I’m trying to get my Debian based install up and running.
And the Debian dependency graph lists it as a dependency of fso-frameworkd…

gsm0710muxd states: THIS_IS_DEPRECATED_USE_LIBGSM0710MUX
libgsm0710mux states: DEPRECATED_PLEASE_USE_CORNUCOPIA
And of course there is also
fso-abyss.git the “GSM 07.10 Multiplexer (NG)” (which is deprecated in favour of cornucopia)

To sum it up we have 4 different implementations of a GSM multiplexer… no wonder I am a bit confused which to use.

But why not just “apt-get install cornucopia” and leave the past behind?
Well I would but unfortunately it seems that the bleeding edge phone software needs a bleeding edge “valac 0.9.3-3″
which even the vala developers consider a development release which prevents it from entering the Debian unstable distro.

Being a fan of C and C++ (if you can spare the “disks” space for the std. library)
I sure would have preferred if the more proven and stable platform  C were used than this new kid on the block valac
which I did not even know existed prior to its usage on the Neo/Freerunner.
It sure would make it easier to port it to other distros than SHR.

And then there is SHR and the whole home-grown Illume 1and 2 issue, focus bugs, all new bugs in V2 (I have not tried it as the mailing list scared me away).
Being slightly conservative with regard to this whole new software ting. What is wrong with say matchbox as far as I know it mostly just works.
Okay it is not thumb friendly per standard, but a little themeing seemed to do the trick for Nokia and the 770/800/810.
And GTK seems to do the trick for my desktop PCs, and it seems slightly more stable that the fancy Enlightenment tool kit.
At least I can not remember having any problems giving focus to a text input field.

But is  SHR not the  most advances phone distro?
It is, however it lacks the diversity of available packages of Debian, and I find the the build system beaks way to easily for my taste.

Why do I believe that all this may be harmful?

• If there are lots of things that do not work you are more tempted to not use the FSO phone this includes UI misfeatures.
  I once used it as my primary phone but have reverted back to an ancient Nokia 6100.
• Using new tools makes it harder to gain support from the community as less people know them.
• Lots of rewrites causes bad documentation, as no one has the time to write it.
  It also makes it harder for the occasional hacker to get anything done as everything is new at each rewrite.
  It also puts an increased strain on other distro maintainers as they have to keep up, not only with the new services but also the new dependencies.

Last but not least:
Remember the ones writing the code is always right.
If you don not agree with them do not write blog entries, write code.

To: Michael ‘Mickey’ Lauer, the SHR and Pkg-FSO team
Keep up the good work, I can not imagine how you get any real life activities done as well as coding this much.

/etc/ssl/certs/dovecot.pem and /etc/ssl/certs/dovecot.pem were the default locations check your /etc/dovecot/dovecot.conf before running.

openssl req -new -x509 -nodes -out /etc/ssl/certs/dovecot.pem -keyout /etc/ssl/private/dovecot.pem -days 3650

/etc/init.d/dovecot restart

I got tired of renewing the certificate so I issued one that lasts 10 years.
(apparently it does not take that much to make me tired)