We spent last year designing and creating MED so it was nice to find this video created by Microsoft explaining what it is and how it works

Dear friends and Maemoans, as it happens we did not get enough confirmed candidates in the set nomination period, so according to the Council Election Rules we need to extend the nomination period by 4 weeks.

This will push all dates one month to future. The new schedule of the voting is as follows:

• Nomination period continues until Saturday 29.08.2015
• Contemplation period starts on Sunday 30.08.2015 and continues until Saturday 05.09.2015.
• Election period starts on Sunday 06.09.2015 and continues until 12.09.2015.

Currently we have 5 confirmed candidates. (endsormeans, juiceme, reinob, Win7Mac, peterleinchen)

On behalf of the outgoing community council,

Jussi Ohenoja

Meeting held 2015-07-28 on FreeNode, channel #maemo-meeting (logs)

Attending: Jussi Ohenoja (juiceme), Peter Leinchen (peterleinchen), Gido Griese (Win7Mac), Paul Carlin (endsormeans)

Partial: Ruediger Schiller (chem|st)

Absent: Oksana Tkachenko (Oksana/Wikiwide), William McBee (gerbick), Alexander Kozhevnikov (MentalistTraceur)

Summary of topics (ordered by discussion):

• Ongoing Council Elections
• TM donation status

(Topic Ongoing Council Elections):

• Elections announcement and nominations
• Wiki page
• Juiceme asked if endsormeans is willing to run for Council, and after some consideration he accepted candidacy.
• There are now four confirmed candidates (reinob, endsormeans, peterleinchen, juiceme) but more are needed.

(Topic TM donation status):

• Bitcoin account setup is going on.
• Win7Mac is going to contact reinob for assistance/information on TM related matters.
• Recap on the expiring TM's;
  • Europe - already expired, needs immediate refresh
  • USA - already expired, will not be refreshed
  • Taiwan - 2016
  • Brazil - 2018
  • Singapore - 2019
  • Japan, Korea, Russia, Switzerland, Norway - 2020
  • Canada - 2023

Action Items:

• old items:
  • The selected Code of Conduct (KDE) still needs to be published on TMO.
  • 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.
  • Contacting Daphne Won on Facebook and LinkedIn to get administrator rights on Facebook for a Maemo member to migrate the plugin to v2.0 API and maintain it in the future.
• new items:

I decided to use a different target platform for my project. Initially, I was using Android Kitkat + Galaxy Nexus (ARMv7 + TI OMAP 4460). To obtain best performance with some crypto operations, I am now using Android Lollipop + Nexus 9 (ARMv8 64bits). I did some tests with basic OpenSSL examples (for example, AES-128 and SHA1) and the numbers are impressive.

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.

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

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.

Present

• 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.

Agenda

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.

Minutes

1. 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.
2. 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.
3. 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.

Needed to make a Company Presentation recently so thought I would add it here.

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.