Planet maemo

Raul Herbster
In my current project, the system has to notify the user about a certain action that actually takes place inside the kernel (in this case, transfer of security keys). I don't want to get into too much details about the tasks, but let's consider that the kernel and the Dalvik are the only trustworthy components and the security keys are stored inside the kernel. I've also seen some pieces of code that helps to implement this, but I could not find a end-to-end solution.
Click to read 3836 more words
Categories: android
Raul Herbster
Let's now show how to install a module into the just compiled Android kernel (see this post for more information)

For compiling the module, it's important that you use the same kernel source that is installed in your device. Otherwise, you cannot install the module.

a. Go to the code that contains an example of kernel module for Android (for instance, [your_code]/module/intercept);
b. Update the makefile to point to your kernel source code;
c. You need to set some env variables, including the cross-compiler. In this case, you can use the ones provided by the Android source, in the folder prebuilts:

   @desktop:$ export CROSS_COMPILE=[android_sdk]/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-
   @desktop:$ export ARCH=arm
   @desktop:$ export PATH=$PATH:/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/
   @desktop:$ make
   (a kernel module file will be generated ([your_module].ko) and this is the one that we need to install in our rooted device)

d. Copy the .ko file to the device using the following command:

   @desktop:$ adb push [your_module].ko /data/local/tmp

e. Install the kernel module using the following commands:

   @desktop:$ adb shell
   @android:$ su
   @android:$ cd /data/local/tmp
   @android:$ insmod [your_module].ko

f. You might get some errors, such as "function not implemented". To check more details about what's wrong, you can check the log file by typing the following command.

   @android:$ dmesg

Raul Herbster
As you need to implement your solution into Android system, you end up learning a lot about the different Android layers (kernel, OS and applications) and how to integrate them. I decided to add the following list with some tips, as these small things took me some precious time to get it solved. The list will be often edited:

#01 - Make sure that you're flashing the device with the proper kernel image

This is what happened to me: I had previously built the kernel (something like two months before). Then, I had to build the OS image from scratch, that is, cleaning up the previous build (with make clobber). When I used the command make bootimage, including setting the variables properly, the output always had the wrong kernel image (not the one that I had previously built, but the existing one in the directory prebuilts). The build process won't take too old kernel images. Therefore, make sure that the compressed kernel image is always new. Even if you don't make any change on the kernel source, do make again to generate a new file.



  • Ryan Abel – Hildon Foundation Director
  • Andrew Flegg – Hildon Foundation Director
  • Gido Griese – Hildon Foundation Director
  • Rüdiger Schiller – Hildon Foundation Director, Maemo Community e.V. Director
  • Falk Stern – Maemo Community e.V. Director [partial]

Minutes were produced by Andrew Flegg.


  1. Approval of Corporate Resolution to transfer monies to MCeV and close the Hildon Foundation bank account.
  2. Approval for proceeding with a transfer of all rights, responsibilities and remaining assets to MCeV.


    1. All present Hildon Foundation directors reviewed the proposed wording of the Corporate Resolution to transfer the bank account contents to Maemo Community e.V., and close Hildon Foundation’s bank account. No changes were proposed.
    2. A voice vote was taken on passing the proposed Corporate Resolution. The results were:

      Rüdiger Schiller: yes
      Ryan Abel: yes
      Andrew Flegg: yes
      Gido Griese: yes

      The Corporate Resolution was passed unanimously.

    3. Ryan Abel took an ACTION to produce the document and circulate it for signing physically and electronically. The document will be passed from Ryan -> Gido -> Rüdiger -> Andrew -> Craig. Due date: Thursday, 7th May 2015.
    4. Craig Woodward will also sign the document to represent his undertaking of the tasks laid out in the Corporate Resolution. Once signed, he will return the signed document to Hildon Foundation Board.
    1. Falk Stern, as another member Maemo Community e.V. board joined the meeting to discuss the agreement to transfer all assets, rights and responsibilities of Hildon Foundation to Maemo Community e.V.
    2. All present reviewed the proposed wording of the agreement to transfer Hildon Foundation activities to Maemo Community e.V. No changes were proposed.
    3. A voice vote was taken on passing the proposed agreement. The results were:

      Rüdiger Schiller: yes
      Andrew Flegg: yes
      Falk Stern: yes
      Ryan Abel: yes
      Gido Griese: yes

      The agreement was passed unanimously. MCeV bylaws only require two signatures.

    4. Ryan Abel took an ACTION to produce the document and circulate it for signing physically and electronically. The document will be passed from Ryan -> Gido -> Falk -> Rüdiger -> Andrew. Due date: Monday, 11th May 2015.
    5. Once signed, Andrew Flegg will email the document to both Hildon Foundation and Maemo Community e.V. boards for their records.
    1. AOB: Following on from the execution of these two agreements, Andrew Flegg took an ACTION to work with Craig Woodward and, if possible, Rob Bauer to tidy up the affairs of Hildon Foundation and close the corporation. Before executing this, a further Board Meeting will be held to ratify the closing of the corporation.
    2. With no other business, the meeting was closed at 22:50 UTC.
Categories: Meeting Minutes

Updating Crucial MX100 Firmware with Ubuntu

2015-04-10 20:14 UTC  by  madman2k

There has been a Firmware update for the Crucial MX100 to MU02. In case you are running Ubuntu there is an easy way to perform the update without using a CD or USB Stick.

As the firmware comes in form of an iso image containing Tiny Core Linux, we can instruct grub2 to directly boot from it. Here is how:

  1. append the following to /etc/grub.d/40_custom:
    menuentry "MX100 FW Update" {
     set isofile="/home/<USERNAME>/Downloads/MX100_MU02_BOOTABLE_ALL_CAP.iso"
     # assuming your home is on /dev/sda3 ATTENTION: change this so it matches your setup
     loopback loop (hd0,msdos3)$isofile
     linux (loop)/boot/vmlinuz libata.allow_tpm=1 quiet base loglevel=3 waitusb=10 superuser rssd-fw-update rssd-fwdir=/opt/firmware rssd-model=MX100
     initrd (loop)/boot/core.gz

    read this for details of the file format.

  2. run sudo update-grub
  3. reboot and select “MX100 FW Update”
  4. Now you can delete the menuentry created in step1

Note that this actually much “cleaner” than using windows where you have to download 150MB of the Crucial Store Executive Software which actually is a local webserver written in Java (urgh!). But all it can do is display some SMART monitoring information and automatically perform the above steps on windows.

Header Image CC-by MiNe

Categories: Articles
Ian Lawrence

Jozian Ltd

2015-04-06 14:35 UTC  by  Ian Lawrence
Needed to make a Company Presentation recently so thought I would add it here.
Categories: Hand selected teams
EDIT: Two things: IANAL. I'm not stating there is a violation here. You can look at what's linked to yourself - it worries me that the scripts I know to be central to building a mediatek kernel comes with strange headers as well. Not all that's grep'able here is used in kernel. Second, this is my own personal opinion and blog, not that of my employer.
Click to read 52670 more words

If you want to get your Xbox One/ Xbox 360 running on ubuntu you basically have the choice between the in-kernel xpad driver and the userspace xboxdrv driver.

Most of the guides recommend using xboxdrv as xpad has been stagnating. However using xboxdrv has some disadvantages; as it runs as a daemon in userspace you have to manually take care of starting/ stopping it and giving your user access to the virtual devices it creates.
Xpad on the other hand just works as any other linux driver directly inside the kernel which is more  efficient and hassle free.

Fortunately while pushing SteamOS Valve has updated the xpad driver bringing it on par with xboxdrv:

  • they added support for Xbox One Controller
  • they fixed the communication protocol – no more blinking controller light

Update July 22, 2015

Unfortunately there are still several issues with the SteamOS driver. This follow-up post discusses them and the solutions in detail.

The bottom line is that I updated the official linux driver with chunks found in the SteamOS driver, as well as in several patches floating around the internet. Code and install instructions are available at Github.

Categories: News

The build-in opencv line drawing function allows to draw a variety of lines. Unfortunately it does not allow drawing a gradient line interpolating the colors at its start and end.

However implementing this on our own is quite easy:

using namespace cv;

void line2(Mat& img, const Point& start, const Point& end, 
                     const Scalar& c1,   const Scalar& c2) {
    LineIterator iter(img, start, end, LINE_8);

    for (int i = 0; i < iter.count; i++, iter++) {
       double alpha = double(i) / iter.count;
       // note: using<T>(iter.pos()) is faster, but 
       // then you have to deal with mat type and channel number yourself
       img(Rect(iter.pos(), Size(1, 1))) = c1 * (1.0 - alpha) + c2 * alpha;
Categories: Graphics
Thomas Perl

Running Debian sid on Sailfish OS

2015-01-29 18:40 UTC  by  Thomas Perl
This assumes you have a Debian/Ubuntu host computer on which to run debootstrap. Theoretically you can run this on the device, but it's not as easy as on Harmattan (where you can just install the debootstrap package. On the host, run the first init and create a tarball:

sudo debootstrap --arch armhf --foreign sid sid
sudo tar czvf sid.tgz -C sid .
du -sh sid.tgz
# 98M sid.tgz
scp sid.tgz nemo@
To unpack the chroot tarball:

ssh nemo@
# password

mkdir sid
cd sid
tar xvf ../sid.tgz
chroot /home/nemo/sid/ /debootstrap/debootstrap --second-stage
chroot /home/nemo/sid/ apt-get clean
echo "deb sid main" \
To enter the chroot:

ssh nemo@
# password

mount --bind /proc /home/nemo/sid/proc
mount --bind /sys /home/nemo/sid/sys
mount --bind /dev /home/nemo/sid/dev
mount --bind /dev/pts /home/nemo/sid/dev/pts
cp /etc/resolv.conf /home/nemo/sid/etc/
chroot /home/nemo/sid/
apt-get update
Categories: chroot
Firefox for Mobile Firefox for Mobile Let's build a browser engine! Part 7: Painting 101 - November 5 from Matt Brubeck - Comment - Like

2014-10-21 Meeting Minutes

2014-10-26 21:19 UTC  by  peterleinchen

Meeting held 2014-10-21 on FreeNode, channel #maemo-meeting (logs)

Attending: (xes), Gido Griese (Win7Mac),
Jussi Ohenoja (juiceme), Peter Leinchen (peterleinchen)

Partial: Sicelo Mhlongo (sicelo)

Absent: Philippe Coval (RzR)

Summary of topics (ordered by discussion):

  • Mailing list moderation
  • Dead/old/obsolete content on entry page
  • Ongoing tasks: referendum, Code of Conduct, karma, e.V. sub pages, letter to Jolla

Topic (Mailing list moderation):

  • Jussi found out accidentally that the mailing list maemo-community bounces back a feedback to non-subscribed senders like "message is suspended until a moderator checks the content". But mails ending up in a queue that has not been checked for the last 1,5 years.
  • There was a short discussion about the way to handle:
    1.) we change the message to "posting is forbidden from unregistered accounts, please see bla bla bla..."
    2.) we actually get someone to check&moderate the postings. (council for example)
  • At the end juiceme took over the responsibility to check those logs from now on and moderate the mailing list(s).

Topic (Dead/old/obsolete content on entry page

  • On the top page of m.o are very old contents, like the announcements from 2013/2010. Furthermore the link to the "abandoned" Cordia project.
    And as I thought the Nokia links (which in fact are working and need to be there, at least the one to
    The one to is working, but not fully related to Maemo (but to MeeGo and therefore now MS).
  • So the council/board should decide what to do with that Cordia link. And if we keep the announcements ticker on entry page for e.V. reasons, or remove it and use t.m.o as announcement platform (as they belong together now).

Topics (Ongoing tasks: referendum, Code of Conduct, karma, e.V. sub pages, letter to Jolla):

  • Freemangordon showed up late and asked about contacting Jolla for fre(e)mantle source code support.
  • These topics were again shifted to be discussed in next week's meeting.

Action Items:
  • -- old items:
    • Check if karma calculation/evaluation is fixed. - Karma calculation should work, only wiki entries (according to Doc) not considered. To be cross-checked ...
    • NielDK to prepare a draft for letter to Jolla. - Obsolete
    • Sixwheeledbeast to clarify the CSS issue on with techstaff. - Done
    • juiceme to create a wording draft for the referendum (to be counterchecked by council members). - See
    • Everybody to make up their own minds about referendum and give feedback.
    • Peterleinchen to announce resignation of DocScrutinizer*/joerg_rw from council. Done
  • -- new items:
    • Next weeks tasks: referendum, karma check, voting for Code of Conduct, sub pages on m.o for e.V., abandoned link/announcement ticker
Categories: council