Planet maemo

Oksana Tkachenko

2015-04-21 Meeting Minutes

2015-04-30 22:29 UTC  by  Oksana Tkachenko

Meeting held 2015-04-21 on FreeNode, channel #maemo-meeting (logs)

Jussi Ohenoja (juiceme), Oksana Tkachenko (Oksana/Wikiwide), Peter Leinchen (peterleinchen),

Gido Griese (Win7Mac),

Absent: William McBee (gerbick), Alexander Kozhevnikov (MentalistTraceur),

Summary of topics (ordered by discussion):

  • Miscellaneous
  • HiFo and MCeV: transfer

Topic (Miscellaneous):

  • Neo900's web-store will hopefully open within one month.
  • Next election will be acid test for PHP code's personal link generation.
  • Glitch within election machine which might be triggered by invalid ballots, or something else...
  • GMail within Modest, GMail vs personal mail server, bookmark syncing across devices and browsers.

Topic (HiFo and MCeV: transfer):

  • Council should write email to Jaffa (nearly the only member of HiFo Board who is currently in USA) and Rob (co-founder of HiFo), to convince them to fill in the required paperwork to transfer from HiFo to MCeV.
  • Required: HiFo's list of donations-expenses over time, something about taxes, and legal transfer of all assets of HiFo to MCeV
  • Oksana could take part in simple time-consuming work, over email...

Action Items:
  • -- old items:
    • The selected Code of Conduct (KDE) still needs to be published on (T)MO.
    • Looking into automatic calculation of election results ...
    • Contacting freemangordon and merlin1991 about auto-builder: CSSU-thumb target, GCC versions?
    • Getting maemo trademark registration (everywhere?) renewed (and transferred to MCeV) by the end of February (or within six months since expiry date).
    • archiving Ovi/Nokia store, especially for Harmattan.
  • -- new items:
    • Email to Jaffa and Rob about complete transfer of all assets from HiFo to MCeV.
Categories: council
Oksana Tkachenko

2015-04-14 Meeting Minutes

2015-04-17 00:01 UTC  by  Oksana Tkachenko

Meeting held 2015-04-14 on FreeNode, channel #maemo-meeting (logs)

Jussi Ohenoja (juiceme), Oksana Tkachenko (Oksana/Wikiwide),

Rüdiger Schiller (chem|st),


Absent: William McBee (gerbick), Alexander Kozhevnikov (MentalistTraceur), Peter Leinchen (peterleinchen),

Summary of topics (ordered by discussion):

  • TMO spam
  • gcc for CSSU-Thumb
  • eV: bank account
  • competition prizes

Topic (TMO spam):

  • Humans from Korean online casino created several accounts for spam-bots.
  • chemist closed registration for the time being, since humans can go through any anti-bot protections during registration.
  • akismet post checking filters 80% of legitimate posts.

Topic (gcc for CSSU-Thumb):

  • juiceme would like to help freemangordon with packaging gcc 4.7.2 - what was the problem, what was the compile environment?

Topic (eV: bank account):

  • juiceme's last shipment of bank papers hasn't arrived to chemist, yet.
  • chemist will send a draft to juiceme for court papers.

Topic (competition prizes):

  • juiceme: One thing we might start thinking about, is programming contests.
    It has been fairly long since we had one and and we have some promised donation devices too.

Action Items:
  • -- old items:
    • The selected Code of Conduct (KDE) still needs to be published on (T)MO.
    • Looking into automatic calculation of election results ...
    • Contacting freemangordon and merlin1991 about auto-builder: CSSU-thumb target, GCC versions?
    • Getting maemo trademark registration (everywhere?) renewed (and transferred to MCeV) by the end of February (or within six months since expiry date).
    • archiving Ovi/Nokia store, especially for Harmattan.
  • -- new items:
Categories: council

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: News

Introducing Sensors Unity

2015-02-07 14:23 UTC  by  madman2k

Sensors-Unity is a new lm-sensors GUI for the Unity Desktop. It allows monitoring the output of the sensors CLI utility while integrating with the Unity desktop. This means there is no GPU/ HDD support and no plotting.
If you need those you are probably better suited with psensor. However if you just need a overview of the sensor readings and if you appreciate a clean UI you should give it a shot.

Sensors Unity is available from this PPA

It is written in Python3 / GTK3 and uses You can contribute code or help translating via launchpad.


In contrast to other applications the interface is designed around being a application. Instead of getting another indicator in the top-right, you get an icon in the launcher:

The user interfaceThe user interface

The idea is that you do not need the sensor information all the time. Instead you launch the app when you do. If you want to passively monitor some value you can minimize the app while selecting the value to display in the launcher icon.

To get the data libsensors is used which means that you need to get lm-sensors running before you will see anything.

However once the sensors command line utility works you will see the same results in Sensors-Unity as it shares the configuration in /etc/sensors3.conf.


Unfortunately configuring lm-sensors via /etc/sensors3.conf is quite poorly documented, so lets quickly recap the usage.

  • /etc/sensors3.conf contains the configuration for all sensors known by lm-sensors
  • however every mainboard can use each chip in a slightly different way
  • therefore you can override /etc/sensors3.conf by placing your specific configuration in /etc/sensors.d/ (see this for details)
  • you can find a list of these board specific configurations in the lm-sensors wiki
  • to disable a sensor use the ignore statement
  • #ignore everything from this chip
    chip "acpitz-virtual-0"
     ignore temp1
     ignore temp2
  • to change the label use the label statement
  • chip "coretemp-*"
     label temp1 "CPU Package"

    Sensors-Unity Specific Configuration

Sensors-Unity allows using the Pango Markup Language for sensor labels. For instance if you want “VAXG” instead of “CPU Graphics” to be displayed, you would write:

label in4 "V<sub>AXG</sub>"

In order not to interfere with other utilities and to allow per-user configuration of the labels/ sensors Sensors-Unity first tries to read ~/.config/sensors3.conf before continuing with the lm-sensors config lookup described above.

Categories: Articles
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


2014-12-07 12:30 UTC  by  madman2k
0 is a new python wrapper for libsensors of the lm-sensors project. libsensors is what you want to use to programmatically read the sensor values of your PC with Linux instead of parsing the output of the sensors utility. is not the first wrapper – there are two alternatives, confusingly both named PySensors.

PySensors (ctypes) follows a similar approach to by using ctypes. However instead of exposing the C API it tries to be a object-oriented(OO) abstraction, which unfortunately lacks many features and makes the mapping to the underlying API hard. Furthermore it does not support Python3.

PySensors (extension module)  does not use ctypes and thus is more efficient, but if you write a python script probably compiling a extension module is worse than losing some performance when reading the values.
Additionally there is python3 support and also some OO abstraction. The latter is somewhere in between the C API and proper OO: sensors_get_label(chip_name, feature) is ChipName.get_label(feature) instead of feature.get_label().

So what makes immediately different is that it does not try to do any OO abstraction but instead gives you access to the raw C API. It only adds minor pythonification: you dont need to mess with pointers, errors are converted to exceptions and strings are correctly converted from/ to utf-8 for you.

However working with the C API directly is tiresome at times – therefore there is also an optional iterator API, which is best shown by a demo:

import sensors


for chip in sensors.ChipIterator("coretemp-*"):
    print(sensors.chip_snprintf_name(chip)+" ("+sensors.get_adapter_name(chip.bus)+")")
    for feature in sensors.FeatureIterator(chip):
        sfi = sensors.SubFeatureIterator(chip, feature)
        vals = [sensors.get_value(chip, sf.number) for sf in sfi]
        label = sensors.get_label(chip, feature)
        print("\t"+label+": "+str(vals))



coretemp-isa-0000 (ISA adapter)
	Physical id 0: [38.0, 80.0, 100.0, 0.0]
	Core 0: [37.0, 80.0, 100.0, 0.0]
	Core 1: [35.0, 80.0, 100.0, 0.0]
	Core 2: [38.0, 80.0, 100.0, 0.0]
	Core 3: [36.0, 80.0, 100.0, 0.0]

for a more sophisticated example see the in the repository.

Categories: News

If you use your laptop as a desktop replacement, you will at some point get an external display and a mouse/ keyboard for more convenient usage.
At this point the laptop becomes only a small case of non-upgradable components.

Click to read 2118 more words
Categories: Articles
Firefox for Mobile Firefox for Mobile Let's build a browser engine! Part 7: Painting 101 - November 5 from Matt Brubeck - Comment - Like