As far as I know, the Spanish Cadastre WMS server (run by the Ministry of Economy of Spain) is one of the first to provide its data in the Spherical Mercator projection EPSG:3857 (aka EPSG:3785 and EPSG:900913), so now we can switch between the great cadastre layer and the OSM layers for example. This is the Montjuic Palace in Barcelona:

As we know, the Spherical Mercator projection is conformal (keeps angles and shapes locally) and all parallels have the same length E:

R = 6378137 m
E = 2 * pi * R = 40075016.686 m

But we know that the true length of each parallel is approximately P = E * cos(lat), so if one wishes to measure distances, perimeters or paths directly on a map in EPSG:3857, it’s necessary to multiply the result by a factor f = cos(lat). For areas, f = [cos(lat)]^2. For Barcelona, for example, we have:

lat = 41.402634
f = 0.75008067 (distance)
f = 0.56262101 (area)

According to these results obtained with gvSIG, the perimeter p and area a of that block of buildings should be: p = 0.75008067 * 571.444 = 428.6 m a = 0.56262101 * 22935.684 = 12904.1 sq m The expected values (from the official size of the block shown here) are: p = 418 m a = 12387 sq m Oops, I think I didn’t choose a very standard block.

Finfine, la nova versio de SHR estis publikigita. Vere, ni troe atendis por obteni la novan version… Mi nun estas ĝisdatiganta la operaciumon por OpenMoko. Ĝi estas la unika operaciumo taŭga por *mia* OpenMoko, ĉar mi faris kojonaĵon: mi aĉetis ĝin el Usonano, nesciante, ke la OpenMoko en Usonujo malsamas inter la sama produkto por la eŭropa merkato. Do, ofte mia poŝtelefono ne trafas retkampon aŭ ne sendas mesaĝojn -.-

Se vi havas OpenMoko, bonvolu instali SHR ĉar ĝi estas bone kreita (laŭ la antaŭa versio ).

Kion estas ĝisdatigita?

• xorg servilo astataŭ ol glamo kdrive.
• eglibc anstataŭ ol glibc. Kiel Debiano faris, ni anstataŭigi niajn libc bibliotekon per glibc kaj eglibc.
• gry etoso defaŭlte instalita, kvankam la konkurso por la etoso daŭrigas
• La “neo” etoso estas afabla kaj rapidiga. Ĝi ne estas instalita defaŭlte sed estas en deponejo. Vi povas instali ĝin, tajpante opkg install shr-theme-neo.
• sur-python-bazigita frameworkd estis anstataŭigita bajte kun programaroj verkitaj en Vala. Ni uzas fsousaged anstataŭ ol ousaged, fsodeviced kaj fsonetworkd.
• phonefsod anstataŭigas ophonekitd phone daemon kaj phoneuid/libphoneui estas nun respondeca por la grafika interfaco.
• inkludo de opimd: nun oni povas konservi la el- kaj en- irantaj mesaĝoj
• proksimigo de la integrado de openembedded.org
• mokonnect povas konekti al kelkaj sendrataj retoj sen kolapsi la kernon .

Se vi volas instali ĝin sur OpenMoko, bonvolu elŝuti la novajn bildojn (kompletan aŭ malpezan version) kaj la kernon kaj kopii la dosierojn kiel estis skribita ĉi tie.

Post pli ol unu horo la ĝisdatigo ne finis O_O

Mi atendos, maltrankvile.

via .chourmo.

Recently I had a pretty interesting Facebook-Chat with Valentin Eisendle about the possibilities of a democratic telecommunication-system.  Rumor has it apple is going to include RFID-chips in future versions of the popular iPhone. While Leander Kahney over at Cult of Mac seems to be extremely thrilled about this, it really is a reason for major concern. It’s not just that RFID is extremely unsafe (see here, here, or here), it also raises serious privacy concerns, e.g.: Every single move can be tracked even with GPS and network turned of. And with RFID becoming your main ID, it being hacked could give a hacker access to your wallet, your health details and everything else you want to keep safe from the world.

Something like that could not happen with hardware like openmokos Neo 1973, a completely open sourced mobile phone. This way it would also be possible to develop and deploy a democratic telecommunication-system.

What do we mean by democratic telecommunication?

Basically there are two versions of the idea: One being softcore, one being democratic by design. Let’s start with the softcore-version: With enough open SIP-Servers (SIP being the most popular VoIP-protocol) like egika.net, it would be possible to make free calls with only public WLAN and Google Voice. Of course this would only work with enough public internet around you. So you can see how this is only a dirty hack.
Real democratic telephoning would include a decentralized communication form. Something TerraNet allready experimented with in 2007. Basically what this means is that every phone is directly connected to nearby phones thus forming a meshed net. Phone calls are routed over this net, from phone to phone.

Even though this is technically possible there still are many thinks one has to think about! For example how can you secure calls so that middle-notes cannot listen in on conversations? Or how about scalability?  While the technical questions are rather easily solved (see zfone for security and the amount of private TOR nodes), the real challenge is the socialsystemic component. Or in other words: how do you sell this to the broad masses?

You can now test the new synchronization feature also in your Ubuntu or Windows desktop PC/laptop/netbook – and of course on your Freerunner (Linux/Openmoko) or Nokia N800/N810 (Linux/Maemo). Download your installer now!

		Linux/Ubuntu (tested on 8.04 and 9.04, also for netbooks)
		Linux/Openmoko for Freerunner (tested on SHR)
		Linux/Maemo for Nokia N770/N800/N810
		Windows XP/Vista and Windows 7

• Full install instructions here
• User manual here
• Installers are hosted in the project’s Garage page

This is what you will be able to do:

The Wikireader by Openmoko

Nearly everybody has tried to cheat during an exam! Am I right? I welcome you to the new generation of cheating: The Wikireader. The WikiReader is an electronic device giving a physical form to Wikipedia. The $100 gadget allows you to browse over 4 million Wikipedia entries without the need of the Internet connectivity. But in an age of 3G, free WiFi, smartphones and notebooks who would buy a dedicated reader with no online connectivity?
With my iPhone I can access Wikipedia wherever I want whenever I want. Besides who wants to carry around this clumsy (measures 3.9-by-3.9-by-0.8 inches and weighs 4.5 ounces) device?

The articles are stored on a MicroSD card and for $30 a year the company Openmoko will send out an updated card. Apparently updates are going to be available via downlaod. The Wikireader has just three buttons: a Search, a History and a Random button. By clicking on the search button you are able to type in your request via touchscreen. As soon as you start typing, the WikiReader starts a list of suggestions which is really handy. The History button allows you to browse the articles you’ve already viewed and the Random button gives you random Wikipedia articles. From my point of view the device could use a bigger screen. Openmoko also claims the device can last a year on just 2 AAA batteries. I don’t think it’s possible, but considering the device will only display text in black & white it might work out. We will see!

Openmoko tried to broaden the appeal of the Wikireader to all kind of ages. The official websites shows pictures of little, adorable children using a Wikireader. But this is not the target audience! Instead of concentrating on the young generation the company should focus on elderly persons. They weren’t raised with the Internet and they won’t get used to it, therefore the Wikireader is a good alternative. Have a look at the adorable child:

[Reference]

Oggi ho partecipato al Linux Day di Dalmine (BG), è stata un’esperienza davvero interessante.
Ho avuto modo di vedere in azione macchine con sistema operativo Ubuntu 9.10, la nuova versione non ancora ufficialmente rilasciata (verrà infatti rilasciata settimana prossima), soprattutto ho avuto modo di vedere la potenza del KMS (Kernel Mode Settings) e di constatare che la mia macchina non lo supporta XD.
E ho anche avuto modo di provare 2 HTC Dream, e mi è venuta una certa acquolina in bocca :p
Peccato che fossi il solo ad avere con me l’Openmoko Neo Freerunner, quest’anno
Purtroppo mi sono perso l’unica conferenza che realmente mi interessava (quella sui diritti digitali) in ogni caso è stato interessante, un’esperienza sempre bella, e ho imparato anche qualche nuova cosuccia (tipo come disattivare il KMS, visto che il mio pc non lo supporta XD).

Ho appena caricato on-line il nuovo pacchetto di Buttons, il nuovo tema di icone per SHR…
http://www.opkg.org/package_294.html
Godetevelo!!!

כבר זמן מה שאני רק נתקל בבעיות עם OpenMoko, בהתחלה היה זה SIM שלא זוהה בכלל, למרות שניסיתי כמה SIM של אנשים שונים, אח”כ אחרי שהחלפתי כרטיס SIM שהחליט לעשות לי בעיות גם בטלפון הרגיל (אנשים שולחים לי מייל שאני לא זמין למרות שהטלפון שלי פתוח ונמצא לידי עם קליטה מלאה), פתאום המוקו החליט להכיר בכל SIM שנכנס אליו (לא ראיתי בספק שהוא גם קורא מחשבות… בכלל לא ראיתי שטלפטיה או אמפטיה מותקנים אצלו… נו טוב). אחרי שעברתי את המסוכה הזו, רציתי להתקין את SHR מחדש. טעות !

פתאום המוקו החליט שכרטיסי זיכרון הם מחוץ לתחום של מוקו, ואני שובר את הראש כל פעם להבין מה לא בסדר. העניין הוא שגם בגרסה שצרובה למכשיר, שלא לדבר על כל מנהל אתחול שקיים (בNOR ובNAND, שזה אומר שניסיתי את Qi ואת u-Boot) לא מצליח להבין שיש לו כרטיס זיכרון. זה לפחות עד ל12 בלילה היום. החלטתי לעשות ניסוי, אחרי שנשיפות מאוד חזקות לנקות את החריצי קריאה לא עזרו, ניגבתי אותם במטלית חלקה ונקייה, וזה נראה שעשה את העבודה.

המוקו הזה הוא מכשיר בוגדני, מספיק שיש בעיה הכי קטנה ואתה תזהה אותה הרבה לפני כל מערכת אחרת… מה קרה לתקופות בהם רק שהדברים באמת הגיעו למצב של מוות שאפילו נתיחה אחרי המוות לא תסביר את הבעיה ? למה הם לוקחים מאיתו את הכיף בלא להבין מה קורה איתנו ?!

È passato molto tempo dal mio ultimo lavoretto e sempre sono stato impegnato in questi giorni, quindi mi è stato proprio impossibile farne altri…
Ma ora è il momento di condividere con i miei 6,4 lettori le mie nuove icone, Le icone, attenzione…
A voi 4 icone per farvi gli occhi:

Belle eh?
Al momento sono disponibili per i seguenti programmi: FFAlarms, Checklist, File Manager, TangoGPS, Intone, Leafpad, Midori, Mokomaze, Mokonnect, Neon, Phonelog, Pidgin, Sgt-Puzzles, ScummVM, Settings, Sketchbook, Terminal, VisualBoyAdvance, Numptyphysics, Calculator.
Fatemi richieste!!!

Hello Every one, This small tutorial is about how to port GPRS on Openmoko.

After spending so many weeks on enabling GPRS on Openmoko, I finally found a way how to did.

I waisted more then 4 weeks on enabling GPRS on Openmoko, I hv flashed my Neo more then 70 times for different rootfs and kernels, Even compiled my own to add GPRS support to the kernel, Read every available tutorial on Openmoko GPRS, Did what ever I could, even ported android on it and in the last when couldn’t do any thing, Finally I corrupted one of our Openmoko.

But that was blessing in disguise.

To repair my openmoko, I was reading an article about how to Debug Openmoko using Debug board.

I don’t know what I click and saw a link, I Went to it,

http://www.opkg.org/package_205.html

Clicked the Nice Looking download button and in a fraction of second it got downloaded.

I copied it to my Phone and Installed it.

Added my Service provider’s APN (warid in my case).

Clicked ON and …. You know what happened next. The GPRS Modem was active, I could Browse the INTERNET and don’t ask how much I was happy.

If You want to ask more questions just leav the question in Comment…

Heute Abend war mir ein bisschen langweilig Und was macht man da als Freerunner-User? Genau, man flasht sich ne neue Distribution Für diesen Abend habe ich QTMoko V14 auserkoren, einen Debian-basierten QTopia-Ableger.

QTMoko Homescreen

Die Installation verläuft problemlos. Mittels des vorgegebenen Rootfs und des Kernels von der QTMoko-Homepage sowie U-Boot von der Openmoko-Homepage kann sofort losgeflasht werden. Nach 2 Neustarts zur Initialisierung startet das System ohne Probleme. Die Oberfläche ist QTopia-Standard.  Alle positiven Punkte will ich jetzt mal stichpunktartig zusammen fassen:

1. Sehr schneller Start von Anwendungen
2. Große Auswahl an Keyboards. Es gibt auch welche mit deutschen Umlauten. Dazu kommt ein Terminal-Keyboard und die Handwriting-Methode. Predictive Keyboards lassen sich abschalten.
3. Obwohl das System seine Inhalte auf dem Framebuffer rendert, ist es möglich, auch X-Anwendungen zu starten. Hierzu kann mittels des Programms QX eine Instanz des X-Servers gestartet werden, in der das gewünschte Programm läuft. Dies funktioniert problemlos z.B. mit TangoGPS. Jetzt fehlt nur noch eine Integration in die vorhanden Apps.
4. Voller Zugriff auf die Debian-Repos für ARM-Geräte mit tausenden von Paketen. Das öffnet Tür und Tor für weitere Basteleien.
5. Dokumentverwaltung: Es gibt eine Quelle für alle Arten von Dokumenten (Musik, Text, Videos, …), die sich einheitlich verwalten lässt und von verschiedenen Programmen (Media Player, Hintergrundbild, Image Viewer, …) benutzt wird. Sehr schön
6. WLAN funktioniert, und das sogar über GUI mit WPA2. Ich bin begeistert
7. GPRS funktioniert, und das ebenfalls über die GUI. Ich noch begeisterter
8. Suspend geht ebenfalls, ich werde dies in den nächsten Tagen noch genauer prüfen.
9. Es gibt einen grafischen Package Manager, der jedoch nur eine kleiner Auswahl von Paketen zeigt. Empfehlenswert ist der Browser Arora.
10. Die Speicherkarte wurde nicht von Anfang an gemounted. Mit einer kleinen Anpassung in der fstab funktioniert dies auch. Die vorhandene Musik und die Maps werden richtig erkannt.
11. Was mich bisher an SHR am meisten gestört hat, waren Einstellungen, die nach einem Neustart verloren gingen. Dazu gehört z.B. die Option, bei Anrufen seine eigene Nummer zu senden oder das aktuelle Audio-Profil. Bei QTMoko gehts.

Leider gibts auch ein paar kleine Nachteile:

1. Das Handling der vielen Keyboards ist etwas umständlich, die Umschaltung etwas gewöhnungsbedürftig. Hätte ich genug Zeit, würde ich gleich Handwriting nutzen.
2. Der Start dauert etwas, da U-Boot verwendet werden muss.
3. X-Server-Anwendungen brauchen etwas länger, um zu starten.
4. Es ist immer nur eine Anwendung aktiv. Es gibt keinen Anwendungs-Umschalter so wie bei Illume.
5. Im Adressbuch gibt es keine Auswahl mehr, ob Kontakte von der SIM oder aus der Datenbank angezeigt werden sollen. Nach dem VCF-Import habe jetzt vieles doppelt. Aber vielleicht muss ich nur die SIM-Kontakte löschen. Dank der Buchstabenleiste im Adressbuch kann man Kontakte sehr schnell finden.
6. Einen Last.fm-Client muss ich wohl erst selbst programmieren

Fazit: Bisher haben mich 3 Dinge von QTopia abgehalten: Fehlende Umlaute auf den Tastaturen, keine GPS-Anwendung und das gewöhnliche Handy-Look-And-Feel. Das Look-And-Feel ist zwar noch das gleiche, dafür gibt es viele Funktionen, die besser arbeiten, als bei anderen Distris. Seit der Einstellung von QTopia seitens Nokia hat sich viel getan. QTMoko ist eine schnelle und stabile Distribution, die sowohl als Daily Phone als auch als Bastel-System funktioniert.

Below are the Simple Steps that I followed to Port Android on Neo FreeRunner Openmoko,

1. Download the rootfs for Android, I recommend the one provided by koolu. Click the link below to download it.

http://forum.koolu.org/files/androidfs-koolu-1_0.jffs2

2. Download the kernel for Android, My recommended kernel is given in the link below which is less then 2 mb, use it if you want do it without getting in to any trouble

http://forum.koolu.org/files/uImage-android-patched_bc2caff9cdef8a16.bin

3. Install dfu-utils from synaptic manager (recommended). and download neo tools if you like GUI (I like it).

4. Start your Neo FreeRunner in to NOR menu.

5. Start Neo-tools

• Double Click 2. Flash your Neo
• Select Kernel and rootfs
• In the Dialogue box point to your rootfs and then kernel.
• A strange looking dialogue box will appears, Just waist time reading it, Just click OK.
• If the above steps failed, Repeat it again

The Flashing will going to take some time, so be patiant.

Below are the Steps that we preformed to port IMA plus SELinux on Openmoko. The main idea was to extract patches from the kernel 2.6.30 provided by Mimi Zohar.

See the Details Below.

1. Porting SELinux:

• We used kernel 2.6.29-rc3 because it is the latest being used by the OM kernel community and good support can be taken.
• We cross-compiled it for ARM architecture.
• To enable SELinux, the following modules were enabled in kernel
  • In Security menu we enabled [*] NSA SELinux Support
    [*]    NSA SELinux boot parameter
    (1)    NSA SELinux boot parameter default value
    [*]    NSA SELinux runtime disable
    [*]    NSA SELinux Development Support
    [*]    NSA SELinux AVC Statistics
    (1)    NSA SELinux checkreqprot default value
    [ ]    NSA SELinux maximum supported policy format version
  • Maximum policy support was not enabled because it hangs the system.
  • In file system we enabled <M> Second extended fs support
    Ext2 extended attributes
    Ext2 Security Labels
    Ext2 execute in place support<*> Ext3 journalling file system support
    Ext3 extended attributes
    Ext3 Security Labels

• The kernel was cross compiled using openmoko toolchain.$make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi-

2. Porting IMA:

• To Add IMA support, IMA Patches were added to the kernel.
• These patches were extracted from kernel 2.6.30 which were provided by Mimi Zohar.
• Patches where extracted using git.
• The Command is#git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6 #git checkout -b v2.6.30_local v2.6.30
  #git log –since ”Feb 4” –grep ”Mimi Zohar” — reverse -p > ../ima.patch
• Now we get OM kernel#git clone git://git.openmoko.org/git/kernel.git linux-om-2.6#git-checkout -b andy-tracking origin/andy-tracking
• Patches were applied by using command#patch -p1 <../ima.patch
• We had namei.c Problem, which we solved, but i forgot how we did, Didnt documented it that time, If remember then I will post it here.
• After apply patches successfully we disabled selinux and enabled IMA for testing purpose.
• The kernel was cross compiled and was tested on openmoko.
• After checking that IMA is working fine, we also enabled selinux and was tested again.

3. Problems that we faced:

• First selected kernel 2.6.29-rc3 and patched it with 2.6.26-rc8 patch for LIM/IMA. The patches didnt applied automatically so we applied them manually.
• While compiling, the manual patches conflicted with original code and reported errors.
• Then we extracted LIM/IMA patch from 2.6.30 and applied to the same kernel.
• This time it worked.
• ”depends on ACPI” in Kconfig file in /security/integrity/ima was removed which is for x86 architecture (we are working on arm)and after its removal IMA appeared in the security list.

We at Security Engineering Research group (SERG) in IM | Sciences Peshawar has Ported NSA’s SELinux on Openmoko.

Below is a rough detail the we (me and shahbaz) did to port SELinux on Openmoko (on Neo Freerunner).

1. Obtaining source code

We decided to cross compile the code provided by Willis Vandevanter available at Google Summer of Code.

2. To Enable Auditing:

• The Device was storing all the messages in buffer. This was corrected by modify the file /etc/syslog.conf. In the entry buffer was replaced with file. And hence the problem was solved.

3. Compiling Libraries:

• We downloaded the tool chain for openmoko and was setup accordingly. to cross-compile we setuped the environment by running the script provided by tool-chain#/usr/local/openmoko/arm/setup-env
• The path was exported to to make available the tools provided by tool-chain.#export PATH=$PATHusr/local/openmoko/arm/bin/
• The following two well known commands were used used to compile#./configure
  #make
• libselinux: libselinux was CROSS COMPILED. The problems were with paths. The paths were specified in CFLAGS portion in Makefile by specifying the paths. The Makefile also contain some switches like def, and –z which produced errors, they were removed to solve the errors. The output files libselinux.a, libselinux.so and libselinux.so.1 were copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib and the include folder was copied to /usr/local/openmoko/arm/arm-angstrom-linux- gnueabi/usr/include.
• libsepol: It got the same problems as libselinux. The output files were libsepol.a, libsepol.so and libsepol.so.1 which were copied to /usr/local/openmoko/arm/arm-angstrom-linux- gnueabi/usr/lib and the include folder was copied to /usr/local/openmoko/arm/arm- angstrom-linux-gnueabi/usr/include.
• libsemanage:It also got the same problems as above libraries. The output files were libsemanage.a, libsemanage.so and libsemanage.so.1 which were copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib and the include folder was copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/include.
• Busybox: The commands that were used are:$make menuconfig ARCH=armThen go to Selinux Utilities and enable all enteries. This was done to add additional Applets to busybox to handle SELinux.Busybox provides the following applets for selinux:

  Chcon
  getenforce
  Getsebool
  load_policy
  Matchpathcon
  restorecon
  Runcon
  selinuxenabled
  Setenforce
  setfiles
  Setsebool
  sestatus
  

  The output file was busybox. This file was then copied to /usr/bin folder of openmoko.

3. Compiling the Kernel:

• The Kernel was also CROSS COMPILED for the ARM Architecture. The Command is: $make ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi-
• To add support for EXT2 for using SELinux and Xttented attributes support was added to the Kernel by using the following command.$make menuconfig ARCH=arm CROSS_COMPILE=arm-angstrom-linux-gnueabi-
• Then in File System menu, the following were enabled.<M> Second extended fs support
  Ext2 extended attributes
  Ext2 Security Labels
  Ext2 execute in place support

  <*>Ext3 journalling file system support
  Ext3 extended attributes
  Ext3 Security Labels
  

• Then the Kernel was compiled using the above command. The result was a file called uImage.bin which was copied to the first partition of the SD Card.

4. Flashing Neo Free Runner:

• The Root FS was flashed using the utility called dfu-util. The ROOT FS was flashed using following steps:1. The Neo Free Runner was booted in NOR (AUX+PWR) until the boot menu arrive.
  2. The device was connected to PC via USB cable.
  3. To check whether dfu-util sees your device, run the command:

  $dfu-util –l

• If you get error messages from the dfu-util command then try again. Often it works on the second try.
  The usage of dfu-util is as following:

  $dfu-util -a <altsetting> -R -D <file_name>

  Where:

  -a:  altsetting: Specify the altsetting of the DFU interface by name or by number
  -R:  Issue USB Reset signalling once we’re finished
  -D:  filename: Write firmware from file_name into device

• Flashing the Kernel:Kernel can be flashed by using simple copy paste command as shown above or it can be done using dfu-util. The command format is: $dfu-util -a kernel -R -D /path/to/uImageWhen flashing succeeds the following will be shown:status(0) = No error condition is present
  Done!
• Flashing the Root Filesystem:The Root FS can be downloaded from its website (Given Below).If the file you downloaded is zipped or compressed (has a .gz, bz2, .zip, tar, tar.gz or .tgz extension) you have to uncompress it first. And you can do simple copy paste into SD Card second partition. If the root filesystem is in image in jffs2 format, then you can flash it using the command given below $dfu-util -a rootfs -R -D rootfs_filename.jffs2The flashing process can take up to 15 minutes for a ~70MB image. It is also wise to make sure that your Neo has enough battery charge prior to flashing. When flashing succeeds the following will be shown:status(0) = No error condition is present
  Done!
• Alternative Way: An alternative and easy way to flash Neo Free Runner is by using a graphic utility called NEO TOOLS. Its self explainer in use.

5. Copying Compiled Libraries and other files to Device:

• The compiled libraries and include folder that were copied to /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr and include in previous step, were copied /usr/lib/ and /usr/include/ folder of the device. The files from /selinux-openmoko-read-only/bin were copied to /usr/bin folder of device.Missing files such as setfiles, sestatus and load_policy were provided as soft links from busybox by using the following command:
  
  $ln –s busybox setiles
  $ln –s busybox setstatus
  $ln –s busybox load_policy

6. Adding SELinux FS:

• To SELinux FS fstab file in /etc/ folder on device and the following lines were added to it.none /selinux      selinuxfs     noauto 0    0After that the folder /selinux was created using the following command.$mkdir /selinuxAnd then mounted using following command$mount /selinuxAfter that /selinux-openmoko-read-only/targeted/ folder along with its config file was copied to the /etc/selinux folder of device.
• Reloading and Building the Policy:To build and load the policy the following commands were used in /etc/selinux/targeted folder.To install the Policy:
  #make install

  To Relabel the File System:
  #make relabel

  To Load The Policy:
  #make load

  To Check whether selinux is running use the following command:
  #sestatus

  Also check the var/log/messages file for selinux entries.

7. Trouble Shooting:

• Auditing: When you don’t get messages file in /var/log/, this means they are saved in buffer, to fix this error, Go to /etc/syslog.conf and edit it, change the entry of buffer to file.
• Missing Core Files:When you flush new kernel, the first problem you get is missing core utilities like make, m4 etc. You can download the files from the website (site No. 9).Another way to do is download them directly to your device using opkg. Opkg will download, install and configure your package automatically. The Command to do this is:#opkg install make
  #opkg install m4
  

  For the above process you will need to set Internet on your device through USB Networking, refer to site link No.11 for USB Networking.
  Another easy way to do this is by using wifi, setting wifi is easy and self explainer.

• No selinuxfs: When this problem, it means that you haven’t added selinux support to your kernel, add selinux support to your kernel and then recompile it, for detail see section 3 for detail.
• Mls and other files missing: When you get this error, it means you haven’t mounted your /selinux filesystem.
• Setfiles, load_policy files missing:These files are provided by busybox, to set these files make soft links to set them. The following command shows how to do it#ln -s busybox setfiles
  #ln -s busybox load_policy

  For more information, see section 5.

• Busybox complains about missing applets such as setfiles: This means that you haven’t added selinux support to your busybox. See section 2 for detail.
• Clock skew: This means that the time of device is different then that of files, to fix this error, correct the date and time on your device.
• Policy not loading:
  

  This problem will occur when you try to load policy from ssh. Try loading policy directly from device.

• tmp/load error:This means that load_policy doesn’t take a policy file argument anymore (it always loads policy from the standard location and selects the appropriate version). So just modify your Makefile to omit the policy file or run load_policy by hand with no arguments. If your try this from ssh, your terminal will hang up. Try it directly on your device.

8. List of Websites for Openmoko:

Sites containing ROOTFS and Kernels:

http://downloads.openmoko.org/distro/releases/Om2008.12/
http://downloads.freesmartphone.org/fso-stable/milestone5.1/om-gta02/
http://build.shr-project.org/shr-testing/images/om-gta02/
http://wiki.openmoko.org/wiki/Download
http://downloads.openmoko.org/distro/obsoleteimages/Om2008.8/Om2008.8.rootfs.tar.gz
http://downloads.openmoko.org/distro/obsolete-images/Om2008.9/Om2008.9.rootfs.tar.gz
http://compartida.net/openmoko/FDOM/

Site containing utilities for Openmoko:

http://wiki.openmoko.org/wiki/MokoMakefile
http://downloads.openmoko.org/repository/Om2008.8/armv4t/

Openmoko Wiki:

http://wiki.openmoko.org/wiki/Neo_FreeRunner
http://wiki.openmoko.org/wiki/USB_Networking

Openmoko, open source manufacturer made it possible by bring out the physical form of encyclopedia from all its way to a small sized electronic device which is easy and simple to handle and use, you can access the content anywhere without the need for an Internet connection and this unique feature makes it a cool and welcome-able gadget.., read more>>>

OpenMoko, the company behind the FreeRunner open-source phone, released their latest product today: WikiReader. It’s a small mobile device for browsing Wikipedia. Rather than use a wireless network to pull data off of the web, it has local copy of the database on a 8GB microSD card. This approach has been used before, and it lets the WikiReader be compact and really cheap. It uses a Kindle-esque touch-screen display that allows it to run on 3 AAA’s for about a year. The device itself costs just $99, but you can choose to receive updates by snail mail for just $29/year. Alternatively, you can just download the +4GB file and dump it on the card.

Like the FreeRunner, this project is also open-source. The code isn’t available yet, but they say it will be released soon. With luck, the device will be really easy to hack.

I have “ported” my rotozoomer from the Nokia 770 to the FreeRunner/Neo

For a video output speed comparison I have made a video of it running on a Nokia 770, a Neo and a FreeRunner side by side.

Rotozoomer Demo on YouTube

The result is somewhat sad, but judge for your self.
Just remember that the 770 has 1.25 times the pixel count of the Neo and it is a lot older too.

Sources are obtainable from the Maemo Garage page.

Designing opensource hardware projects with opensource EDA software is a challenge for anyone, well not any-more with the upcoming Fedora 12.

While assessing the risk of the project, one first needs to ensure that he/she has a robust and complete tool set before starting up with the development.

In the past, the critical path of this risk assessment was setting up the development platform, compiling and installing the whole tool set (normally composed of least 8 software) from scratch. That said, the average user should allocate one or two days just for compiling all the dependencies, after he/she has roamed around the internet in search for some possible patches needed to ensure interoperability within his/her tool set.

As the community leader in opensource EDA provider, Fedora Electronic Lab strives to eliminate this painful process by preparing this development platform beforehand and gives Fedora users the opportunity to install the required tool set within 5 minutes. During the last two months, we have been focussing on ensuring that Fedora can satisfy the needs for the electronic hardware development of the OpenMoko community.

Fedora’s Kicad will follow OpenMoko’s development needs. That said, it will require Fedora’s Kicad be pulled from trunk. Jon Ciesla, Jacek Radzikowski and I revised the entire Fedora Kicad package and spec file. It was then updated to snapshot revision 1863. But, stability of kicad will be ensured. One of the goals of FEL is not to just talk how opensource software is good, but also to support opensource hardware development and helping users to develop products out of it.

We hope that the OpenMoko community can now work out of the box with

su -c “yum install kicad fped openocd”

svn co https://svn.openmoko.org/trunk/gta02-core/

cd gta02-core/

make update

make sch

instead of the time consuming process as described on this GETTING-STARTED document.

That said, we sincerely hope that our contribution might help OpenMoko developers seduce more contributors and reviewers easily.

Kicad’s module editor lacks automation and its output is difficult to review. Hence fped comes in as a footprint editor that captures more of the design process and allows one to annotate the footprint with measurements taken directly from the manufacturer’s datasheet.

Dean Glazeski, who was privately packaging OpenOCD, (an Open On-Chip Debugger (OpenOCD) provides debugging, in-system programming and boundary-scan testing for embedded devices.) joined Fedora Project and introduced OpenOCD to Fedora so that a wider userbase can benefit from it.

OpenOCD provides a human-readable telnet interface for manually halting/resuming the target device, reading/writing registers and memory, etc. In addition, it provides a RDI (remote debugger interface) on a TCP port. This interface can be used by gdb (the GNU Debugger).

We currently have the following list of packages under the Fedora Electronic Lab umbrella for the following architectures (i686,x86_64, PPC and PPC64). If you feel that we still lack tools that are important to OpenMoko’s development, please do not hesitate to let us know.

I have done a synchronization test to effectively edit a remote PostGIS table. This diagram describes the situation:

All three devices are using a wireless connection and are updating the same remote table which in turn is used by the server to render a point layer in raster mode (the server is both a synchro server and a map server). You can see a short video here. The remote synchro/map server is not shown:

You can also visit these websites (click on the logo):

	Tellus project blog
	Open mobile IS website

Eine einfache und schnelle USB-Verbindung auf das Openmoko Freerunner (mit Android OS) wird durch ein kleines Skript erleichtert.

androidshell

Hinweis: Dieser Artikel erschien ursprünglich am 11.5.2009 und erfährt aus rein technischen Gründen eine überarbeitete Neuauflage. Danke für das positive feedback!

Nach der Installation von Android will man schnell Daten zwischen dem lokalen Rechner und dem Freerunner austauschen. Dazu nötig ist die korrekte Netzwerkkonfiguration der lokalen Schnittstelle (z.B. usb0, bei Ubuntu 9.04 eth1), eine bestehende USB-Verkabelung (muss zum Bootzeitpunkt des Freerunners bestehen), sowie eine funktionierende Verbindung via adb (Details: Android auf Freerunner: Einstieg und USB-Networking).

Nach der x-ten Verbindung war ich es Leid, dieselben Befehle immer wieder einzugeben. Ich beschloss also, dies durch ein Skript ein bisschen effektiver zu gestalten. Das Resultat in action sieht dann so aus:

androidshell

Ach ja: das schöne (eigentlich vollkommen unnötige Banner) wurde mit Hilfe von figlet erstellt.

Das Skript nun als “androidshell” umbenennen, ausführbar machen und in PATH ablegen.

#!/bin/sh
# Easily connect to Openmoko phones with Android OS.
# This script first configures your local interface.
# This script then utilizes Android Debug Bridge (adb) to connect.
# Possibly you have to change the variable INT.
# INT may vary on different systems (eth1, usb0, eth0 ...).
# All other variables should be fine.
######################### Configure local interface to connect to android by USB
INT="eth1"              # you might have to change this (eg usb0)
IPADDR="192.168.0.200"  # local IP: should be fine
NETMASK="255.255.255.0" # local netmask: should be fine
IPFREE="192.168.0.202"  # IP freerunner (default): fine
PROGNAME="androidshell" # name of program: no need to change
#########################
######################### make a nice banner
clear
echo "                 _                 _     _          _ _ " | grep --colour "."
echo "  __ _ _ __   __| |_ __ ___ (_) __| |___| |__   ___| | |" | grep --colour "."
echo " / _. | '_ \ / _. | '__/ _ \| |/ _. / __| '_ \ / _ \ | |" | grep --colour "."
echo "| (_| | | | | (_| | | | (_) | | (_| \__ \ | | |  __/ | |" | grep --colour "."
echo " \__,_|_| |_|\__,_|_|  \___/|_|\__,_|___/_| |_|\___|_|_|" | grep --colour "."
echo "      Android on Freerunner - adb connector via USB"      | grep --colour "."
echo "--------------------------------------------------------"
echo "2009 by linuxnetzer -GPLv3- www.linuxnetz.wordpress.com"
echo "--------------------------------------------------------"
echo "                 PLEASE MAKE SURE... " | grep --colour "."
echo "... adb is installed in PATH."
echo "... Freerunner was connected whilst booting."
echo "... $INT is your correct local USB interface."
echo "--------------------------------------------------------"
######################## configure local interface
echo "setting up $INT for connection (needs root privileges)"
sudo ifconfig $INT $IPADDR netmask $NETMASK
######################## prepare adb
echo "preparing adb..."
adb kill-server
ADBHOST="$IPFREE" adb devices 1> /dev/null
echo "If prompt has changed (#), connection was successful."    | grep --colour "\#"
echo "Type 'exit' to finish connection. Keep up the vibes!" | grep --colour "exit"
######################## start adb
adb shell
exit

# chmod +x /usr/local/bin/androidshell

Das Skript sollte – theoretisch – “out of the box ” funktionieren. Sollte die lokale Schnittstelle (im Skript: eth1) nicht erkannt werden, muss die Variable ‘INT’ gleich zu Beginn des Skripts entsprechend geändert werden. usb0 ist eine wahrscheinliche Alternative.

Wer solche Skripten wegen ihres “grafischen Overloads” meidet und die Dinge lieber einfach hält, für den tut es auch ein minimalistisches Skript. Zur Erinnerung: Per default hat Freerunner seiner Schnittstelle die IP Adresse 192.168.0.202 zugeteilt. Um mit ihm zu kommunizieren, müssen wir uns in dasselbe Netz begeben…

#!/bin/sh
sudo ifconfig eth1 192.168.0.200 netmask 255.255.255.0
adb kill-server
ADBHOST=192.168.0.202 adb devices
adb shell

Links:

http://linuxnetz.wordpress.com/2009/05/09/freerunner-android-sd-card-vorbereiten/
http://linuxnetz.wordpress.com/2009/05/05/android-auf-freerunner-einstieg-und-usb-networking/
http://wiki.openmoko.org/wiki/Android_on_Freerunner#On_Linux
http://wiki.openmoko.org/wiki/Android_on_Freerunner#Installing_Android_on_an_SD_card
http://www.freeyourphone.de/portal_v1/viewforum.php?f=18

Globalement, le seul et unique ordiphone (ou smartphone) entièrement open source (et par définition et extension “libre”) et sous linux.

* Un projet qui a pour but de fabriquer le premier
smartphone libre. C’est a dire un app…areil conçu dans l’esprit de
développement communautaire propre aux Logiciels Libres et utilisant
des composants matériels ouverts et documentés publiquement.

* La société qui fabrique ces smartphones.
* Le système d’exploitation développé par cette société pour ses smartphones.

* Par abus de langage, ce terme est aussi utilisé parfois pour
désigner les smartphones eux-mêmes (au lieu de “Neo1973″ ou “Neo
freerunner”).

(Source : http://openmoko-fr.org/wiki/index.php/Premiers_pas)

Open mobile IS (aka Openmis) is a Java open source project (GNU LGPL license) that aims to provide all the necessary tools, API and documents effectively enabling the development of mobile applications – not intended especially for GIS applications. It was created by Philippe Delrieu (Ubikis technical leader, based in Lyon, France) and has been used successfully for almost ten years in CDC and CLDC platforms. It’s listed as a mature project in the OW2 (ObjectWeb) consortium forge.

Manuel Gomez (Ubikis R&D officer) kindly invited me to join the Tellus project (visit its blog here) where he is exploring the integration of Openmis and gvSIG Mobile. There are several ways to integrate these two projects. I propose to add the Openmis client module as part of gvSIG Mobile (ideally as an extension). This diagram gives an idea of how Openmis fits our needs. Click to see larger image:

Openmis provides the synchronization engine, user authentication and encryption (this is only a part of all the components available in the Openmis framework). Synchronization happens at client request. The client side FODB (fast object database) lets the user work in disconnected mode, while the conflict resolver in the server side will decide who ‘wins’ if both sides have updated the same feature since the previous synchronization.

You can see a first test on a PC here.

לב מ’ (שם המשפחה לא ידוע לי לצערי), יצר שיר המבוסס על שיר הנושא של סדרת המדע בדיוני (המדהימה לדעתי האישית) Firefly.

השיר פורסם ברשימת הדיוור של OpenMoko ישראל :

Boot from NOR, flash the NAND
Answer calls with shell command
I don’t care, I’m still free
You can not take my phone from me

Keep your hacks and jailbreaks
I ain’t never switching back
Source and hardware are free
You can not take my phone from me

Theres no other phone for me
But the one thats running free

You can not take my phone from me

את השיר המקורי עם המילים אפשר למצוא כאן.

מי מתנדב/ת להקליט את השיר החדש ?

I finally got feed up with having my FreeRunner laying flat on the table.
So I decided that it was time to construct a stand for it.

I had some 3mm extruded polystyrene laying around (which I use for building model R/C planes).
It is actually just floor insulating material…

The parts

Created a simple design for a cradle/stand for the Freerunner.
Sources are include, batteries are not needed.

The assembled stand

The parts glued together.
(Using “UHU Por”, but regular wood glue would have worked as well.)

The paper was intentionally left on as the floor insulation has groves on one side.

MokoStand after 2 coats of acrylic paint

Painted the stand to hide the paper and give it a more uniform look.