Replicant contributors meeting - July 27-28 2019, Paris, France

Date

The meeting took place the 27 and 28 July 2019.

Location

The event took place in the April office. April is an association for the defense and promotion of free software.

Precise location: April, 44/46 rue de l'Ouest, b√Ętiment 8, 75014 Paris (It's accesible through the "place de la Catalogne", on the left of the "Biocoop" supermarket). Select "April" on the intercomm.
map: https://www.agendadulibre.org/events/19754
Phone number of the April office: 01 78 76 92 80.

The April office is relatively close to the Gare Montparnasse railway station.

In addition to trains, Gare Montparnasse railway station has also, in the same building, there is a metro station where you can access the metro lines 4, 6, 12 and 13.

Related events

On Friday, a dinner took place.

Dinner meeting time: From 18h30 to 18h45
Dinner meeting location: Near the Montparnasse tower . The Montparnasse tower is very close to the Montparnasse railway station.

At 18h45 we planned to try to find a restaurant nearby.

Airports

The two main airports near Paris are the Roissy Charles de Gaulle International Airport and the Paris Orly Airport.

Roissy Charles de Gaulle International Airport <-> Gare Montparnasse railway station

To get to the Gare Montparnasse railway station from the Roissy Charles de Gaulle International Airport by public transportation, you can take the RER B metro line up to the Denfert-Rochereau station where you can take the line 6 up to the Gare Montparnasse railway station.

Paris Orly Airport <-> Gare Montparnasse railway station

To get to the Gare Montparnasse railway station from the Paris Orly Airport by public transportation, you can take the Orlyval up to the Antony stop, and from there take the RER B metro line up to the Denfert-Rochereau station where you can take the line 6 up to the Gare Montparnasse railway station.

More information

Wikivoyage has a page on Paris and France which have many practical information such as:

It also has pages on the Roissy Charles de Gaulle International Airport and the Paris Orly Airport with more details on the public transportation lines to use to go to Paris, which tickets to buy, etc.

Contacting the organizers

You could use the Replicant private contact mail address in advance to obtain the cellphone number of an organizer to be able to use it in case of issue (like being lost, not finding the location of the meeting, etc).

Presentations

Topic Source code Slides Video Rationale of the talk
Replicant history
$ git clone --recursive https://git.replicant.us/GNUtoo/presentations.git
$ cd path/to/presentation
$ make
pdf 720p ogv The borders had to be cut to preserve the privacy of people passing by in the street. It was also encoded 3 times instead of 2 to save human time. * Has some context that might be useful for new Replicant contributors
* Has information on the relationship between Replicant and GNU/Linux
Replicant and bootloaders pdf 720p webm * The Galaxy SIII (and similar devices) bootloader status is complicated and relevant to Replicant 9
Replicant and modems: introduction pdf 720p webm * Meant to enable new contributors to work on the modem part
Replicant and modems: Samsung IPC pdf 720p webm
Replicant and oFono based Java RIL pdf 720p webm
Porting AOSP for a new device Made with Libreoffice which leaks metadata pdf Not recorded
Graphics acceleration on Replicant
$ git clone https://git.replicant.us/hominoid/graphics-presentation.git
$ cd graphics-presentations
$ make
pdf 720p webm * Explains why Replicant needs special care on the graphics stack.
* Introduces both graphics' hardware and software architecture.
* Dives into the implementation decisions.
* Lays out future plans.

License: CC-BY-SA 4.0 International

Planned discussions

The discussions were not recorded for privacy/intimacy reasons but a sumary of some of the important ones are available below on this page.

Topic Time and dependencies Status Rationale
Discussions on the bootloader situation on the Galaxy SIII and similar smartphones After the talk on the bootloaders
Discussions on minimal requirement to accept a device in Replicant:
* Do we still accept devices with modems that are not isolated?
* Do we have plan to require free software bootloaders?
* Do we require replacable batteries?
After the talk on modems and bootloaders
Discussions on the future of Replicant:
* Which devices do we target
* Do we continue focusing on devices with signed bootloaders
* Allwinner tablets, upstream Linux, and scalability
* Devices with non-replacable batteries
After the talk on Replicant history
Discussion about Upstream components, design choices, and cultural re-appropriation of technology
* Upstream
* Issues when combining together different build systems (Example: Android build system with Kconfig)
* Sharing work with GNU/Linux to enable more political control and cultural re-appropriation of mobile device in the long run, and the risk associated with it
* Android upstream anti-features and political design choices
* How subjective security is, threat models, and the difference between free software and device maker point of view
Please take a look at Upstream before attending if possible.

Known schedule constraints

Available hardware

Devices

Good practices:
Person Hardware Comments Usage
GNUtoo Galaxy SIII (I9300) with the stock bootloader
Galaxy SIII 4G (I9305) with the stock bootloader
Galaxy SIII 4G (I9305) with u-boot
Galaxy Nexus (I9250) with the stock bootloader
Galaxy SII (I9100) with the stock bootloader
GTA04 A3
GTA04 A4
Optimus black (P970)
GTA01 Used in a presentation about Replicant history
GTA02
HTC Dream
N900 Testing the battery charger driver is still needed but require a heavy PSU
Fil Galaxy Note 2 (N7100) stock bootloader [Working] Available for non-critical tests * Test the upstream touchkey driver
=> TODO:
* Bring a Parabola microSD (GNUtoo)
* Test the patch with an I9300
* Rebase the patch on master or linux-next
Galaxy SIII (I9300) stock bootloader [Working] Test Subject available for any experiment
Galaxy SIII (I9300) stock bootloader [Bricked] available for hardware hacking * Test fixing the phone
Galaxy Tab 2 7.0 (GT P3100) Property of the Replicant Project * Add support for it in the BackupTheEFS instructions
Paulk Galaxy Note (N7000) * Add support for it in the BackupTheEFS instructions
Galaxy Tab 2 10.1 (P5100) * Add support for it in the BackupTheEFS instructions
Looking for a Galaxy Note 8.0 (N5100) * Add support for it in the BackupTheEFS instructions

Debug utilities

Person Hardware Comments Usage
GNUtoo Serial port cable with variable resistors
Multimeter
Simtrace 1: Can get the dialog between the modem and the SIM card in wireshark
SIM card that is not recognized in Replicant (STK related?) Test on Replicant 4.2 and on Replicant 6.0
SIM card + phone that can trigger the audio call issue
Sigrok compatible adjustable power supply Not sure to bring it (heavy)
Fil SIM card that is not recognized in Replican 6

Discussion results

Do we care about supporting devices with non-removable batteries?

Points that were mentioned or discussed: Consensus in that meeting:

Do we require free software bootloaders ?

Points that were mentioned or discussed: Consensus in that meeting:

Do we require isolated modems ?

Points that were mentioned or discussed: Consensus in that meeting:

How to handle the various keys used to sign releases, and other related things and should the recovery check signatures

Points that were mentioned or discussed: Consensus in that meeting:

Improve information for current and potential Replicant users

Points that were mentioned or discussed:

Improving the Replicant website

Points that were mentioned or discussed: Consensus in that meeting:

Making it easier for anyone to contribute to Replicant

Points that were mentioned or discussed: Consensus in that meeting:

Funding work on f-droid

Consensus in that meeting:

Using oFono RIL

Points that were mentioned or discussed: Consensus in that meeting:

FSDG compliance and How to moderate the forums

Points that were mentioned or discussed:

People in this discussion realized that the forum is relatively small so it's doable to have it moderated.

Plan of action:

Do we ship some external applications in Replicant

Points that were mentioned or discussed:

Using wayland for the graphic stack?

Points that were mentioned or discussed:

AOSP vs LineageOS

Points that were mentioned or discussed: Consensus in that meeting:

Android upstream vs GNU/Linux upstream

Consensus in that meeting:

Video encoding

Sound

The microphone was mono, with only a channel from the left. So we need to create mono audio files from the videos.

To make the sound go in both channel, do the following in Audacity:

Video

The videos were recorded with some equipement that was lent to us:

=> Next time ask if they have a second microphone available for questions.

Kdenlive is being used for that.

Using kdenlive with Nouveau (with default settings), xfce4 under Parabola manage to freeze the screen (there are some messages like "nouveau: kernel rejected pushbuf: Cannot allocate memory" that can be observed when launching kdenlive through SSH).

To workaround that the following was used:

=> It's still slow while zomming in the timeline but it manage not to freeze the whole graphics stack.

To edit a video with kdenlive: Once that is done you can remove the part before the presentation this way:

Files