Project

General

Profile

Google Summer of Code 2018 » History » Version 49

Denis 'GNUtoo' Carikli, 01/23/2018 04:35 PM

1 1 Jeremy Rand
h1. Google Summer of Code 2018
2
3 33 Paul Kocialkowski
{{>toc}}
4
5 1 Jeremy Rand
Replicant intends to apply to GSoC 2018 as part of the FSF umbrella.  This page lists suggested projects for GSoC students.  *This list is a draft!*
6
7 21 Jeremy Rand
*Note: Working on most of these projects requires a sufficiently powerful computer with enough disk space to build Replicant.*
8
9 2 Jeremy Rand
h2. Advance the Optimus Black U-Boot and Linux mainline ports
10 1 Jeremy Rand
11 25 Paul Kocialkowski
The Optimus Black from LG is an interesting device from the perspective of freedom and privacy/security. It has the ability to run a free bootloader and uses an OMAP3 SoC that is well-documented and supported in upstream U-Boot (bootloader) and Linux (kernel). Its modem is well-isolated from the rest of the device, ensuring a sane base for privacy/security. Currently, the device-specific parts of the mainline U-Boot and Linux ports are still at an early stage, where they are functional with a very limited set of supported hardware.
12 1 Jeremy Rand
13 26 Paul Kocialkowski
Advancing the Optimus Black U-Boot and Linux mainline ports would allow using the device with free, up-to-date and maintainable software and would pave the way for support in GNU/Linux systems as well as Replicant. A list of priorities in hardware support will be defined, with the objective of tackling as many as possible.
14 1 Jeremy Rand
15 25 Paul Kocialkowski
*Difficulty*: Medium
16 1 Jeremy Rand
17 25 Paul Kocialkowski
*Requirements/Prerequisites*: C programming language, driver development
18 1 Jeremy Rand
19 25 Paul Kocialkowski
*Expected Outcomes/Deliverables*: Improved hardware support for the Optimus Black in U-Boot and Linux
20
21 31 Paul Kocialkowski
*Possible Mentors*: Paul (confirmed), GNUtoo (confirmed, backup)
22 1 Jeremy Rand
23 25 Paul Kocialkowski
h2. Advance the Kindle Fire (first generation) U-Boot and Linux mainline ports
24 1 Jeremy Rand
25 25 Paul Kocialkowski
The Kindle Fire (first generation) from Amazon is an interesting device from the perspective of freedom and privacy/security. It has the ability to run a free bootloader and uses an OMAP4 SoC that is well-documented and supported in upstream U-Boot (bootloader) and Linux (kernel). It does not embed a modem, ensuring a sane base for privacy/security. Currently, the device-specific parts of the mainline U-Boot and Linux ports are still at an early stage, where they are functional with a very limited set of supported hardware.
26 2 Jeremy Rand
27 26 Paul Kocialkowski
Advancing the Kindle Fire (first generation) U-Boot and Linux mainline ports would allow using the device with free, up-to-date and maintainable software and would pave the way for support in GNU/Linux systems as well as Replicant. A list of priorities in hardware support will be defined, with the objective of tackling as many as possible.
28 2 Jeremy Rand
29 25 Paul Kocialkowski
*Difficulty*: Medium
30 2 Jeremy Rand
31 25 Paul Kocialkowski
*Requirements/Prerequisites*: C programming language, driver development
32
33
*Expected Outcomes/Deliverables*: Improved hardware support for the Kindle Fire (first generation) in U-Boot and Linux
34 2 Jeremy Rand
35 31 Paul Kocialkowski
*Possible Mentors*: Paul (confirmed), GNUtoo (confirmed, backup)
36 3 Jeremy Rand
37 30 Paul Kocialkowski
h2. Implementing generic Hardware Abstraction Layers (HALs)
38
39
Currently, Replicant uses a dedicated Hardware Abstraction Layer per device, because device manufacturers implemented non-standard kernel interfaces. However, Android works with mainline kernels and supports plug-n-play hardware nowadays, so it makes sense to have generic Hardware Abstraction Layers for the standard interfaces of the Linux kernel (ALSA, V4L2, etc). In particular, this would allow supporting external Wi-Fi dongles such as the ones supported by the ath9k_htc driver and free firmwares without the need for a specific application or configuration.
40
41
*Difficulty*: Medium
42
43
*Requirements/Prerequisites*: C programming language, kernel interfaces knowledge
44
45
*Expected Outcomes/Deliverables*: A collection of generic HALs for Android and Replicant
46
47 46 Denis 'GNUtoo' Carikli
*Possible Mentors*: Forkbomb (confirmed), Paul (confirmed, backup), GNUtoo (confirmed)
48 30 Paul Kocialkowski
49 5 Jeremy Rand
h2. Access Point mode for RepWifi
50
51 11 Jeremy Rand
RepWifi is Replicant's app for using an external USB WiFi adapter.  RepWifi is useful for Replicant because there exist USB WiFi adapters with free firmware, while the built-in WiFi chipsets in mobile phones do not have free firmware.  Right now, RepWifi doesn't support acting as an access point (e.g. for WiFi tethering purposes); you can help by adding this functionality to RepWifi.
52 30 Paul Kocialkowski
53 45 Jeremy Rand
Note that, if we receive high-quality student proposals for both this project and *Implementing generic Hardware Abstraction Layers (HALs)*, we will probably prioritize *Implementing generic Hardware Abstraction Layers (HALs)* over this project.
54 5 Jeremy Rand
55
*Difficulty*: Easy to Medium
56
57 23 Fil Bergamo
*Requirements/Prerequisites*: Knowledge of Java and basic shell scripting. Basic knowledge about wpa_supplicant and general network management in POSIX environments.
58 24 Fil Bergamo
Required knowledge builds up very fast by trial and error, no need to be experts in networking, it's mostly about researching and learning.
59 5 Jeremy Rand
60 23 Fil Bergamo
*Expected Outcomes/Deliverables*: Make wpa_supplicant run in "Access Point mode", allowing another device to connect to the phone via WiFi, and use its mobile data connection to access the internet. Integrate the needed GUI functions into RepWifi.
61 5 Jeremy Rand
62 23 Fil Bergamo
*Possible Mentors*: Fil (confirmed)
63 5 Jeremy Rand
64 34 Paul Kocialkowski
h2. Port Replicant to a newer LineageOS version and support in-system updates
65 4 Jeremy Rand
66 47 Denis 'GNUtoo' Carikli
Replicant is currently based on LineageOS 13.  It would be desirable to upgrade Replicant to a newer release of LineageOS. While at it, it would be useful for a Replicant device to be able to update itself to a new version of Replicant without requiring being connected to a PC. LineageOS already supports this; we suspect that it should be possible to adapt this LineageOS functionality to Replicant. Whenever possible, it would be useful to complete and submit some of the code written for Replicant to LineageOS.
67 4 Jeremy Rand
68 19 Jeremy Rand
*Difficulty*: Medium
69 4 Jeremy Rand
70 19 Jeremy Rand
*Requirements/Prerequisites*: Knowledge of C, C++, and Java.
71 4 Jeremy Rand
72 34 Paul Kocialkowski
*Expected Outcomes/Deliverables*: Remove all proprietary components of LineageOS, port all the changes needed to successfully boot without any blobs, rebrand LineageOS as Replicant and support in-system updates
73 6 Jeremy Rand
74
*Possible Mentors*: Forkbomb (confirmed), Wolfgang?
75 4 Jeremy Rand
76 7 Jeremy Rand
h2. Implement the missing features of Samsung-RIL
77
78 12 Jeremy Rand
Samsung-RIL is the RIL (Radio Interface Layer) that many Replicant devices use to communicate with the modem.  It is a free, reverse-engineered replacement for the proprietary RIL that the Samsung phones ship with by default (which has been found to have backdoors). Right now, Samsung-RIL mostly implements only the protocol features that are absolutely necessary for the phone to be operable.  As a result, many more rarely used protocol features are unimplemented, which decreases functionality compared to the proprietary RIL.  You can help by implementing the missing features of Samsung-RIL.
79 7 Jeremy Rand
80 19 Jeremy Rand
*Difficulty*: Medium to Hard
81 7 Jeremy Rand
82 19 Jeremy Rand
*Requirements/Prerequisites*: Knowledge of C.
83 7 Jeremy Rand
84 20 Jeremy Rand
*Expected Outcomes/Deliverables*: Implement the missing features listed at [[Samsung-RIL]].
85 7 Jeremy Rand
86 18 Jeremy Rand
*Possible Mentors*: Forkbomb (confirmed), Wolfgang?
87 7 Jeremy Rand
88 8 Jeremy Rand
h2. Debug metallic sound in many 3G calls
89 1 Jeremy Rand
90
*We're folding this one into Samsung-RIL as an optional component or stretch goal.*
91
92
Replicant has been observed to sometimes exhibit a metallic sound quality when doing voice calls over 3G (2G works fine).  This is problematic, since most users prefer to stay in 3G mode (and some carriers are dropping support for 2G).  You can help by debugging the issue.
93
94
*Difficulty*: TODO
95
96
*Requirements/Prerequisites*: TODO
97
98
*Expected Outcomes/Deliverables*: TODO
99
100
*Possible Mentors*: GNUtoo (confirmed)
101 41 Jeremy Rand
102
h2. Implement a fully-featured QMI-RIL
103
104
The LTE variants of the Samsung Galaxy S3 and Samsung Galaxy Note 2 use a different modem from the non-LTE variants that Replicant currently supports.  You can help Replicant support those modems by implementing a QMI-RIL, which performs a similar role on the LTE variants as what Samsung-RIL performs on the currently-supported non-LTE variants.  Wolfgang has done some preliminary work on this, so you'll probably be picking up where he left off.
105
106 42 Jeremy Rand
*Difficulty*: Hard
107 41 Jeremy Rand
108 43 Jeremy Rand
*Requirements/Prerequisites*: Knowledge of C.
109 41 Jeremy Rand
110 44 Jeremy Rand
*Expected Outcomes/Deliverables*: A QMI-RIL that supports voice calls, SMS, and data, with as complete a protocol implementation as possible.
111 41 Jeremy Rand
112
*Possible Mentors*: Forkbomb (confirmed), Wolfgang?
113 8 Jeremy Rand
114 9 Jeremy Rand
h2. Optimize power consumption in external WiFi adapter firmware
115
116 16 Jeremy Rand
The USB WiFi adapters used with Replicant are originally intended for laptops, not phones.  As a result, they tend to consume a lot of power.  This poses two issues: they can adversely impact battery life, and they can randomly stop working completely (e.g. needing to unplug and replug the adapter periodically to keep it operational).  You can help by optimizing power consumption in the WiFi adapter firmware.
117 10 Jeremy Rand
118
*Difficulty*: TODO
119 9 Jeremy Rand
120
*Requirements/Prerequisites*: TODO
121
122
*Expected Outcomes/Deliverables*: TODO
123
124 31 Paul Kocialkowski
*Possible Mentors*: GNUtoo (confirmed)
125 9 Jeremy Rand
126 35 Paul Kocialkowski
h2. Tackle security issues in Replicant
127 1 Jeremy Rand
128 35 Paul Kocialkowski
Replicant is plagued by various security issues, that are mostly due to using a downstream codebase. One of the most crucial issues is that Replicant uses an old version of the Android WebView (from circa 2015), which is also a functionality drawback.
129
An initial evaluation of the security issues in Replicant should be conducted, followed by the integration or update of the concerned components of the system.
130 1 Jeremy Rand
131 35 Paul Kocialkowski
*Difficulty*: Medium-Hard
132 17 Jeremy Rand
133 35 Paul Kocialkowski
*Requirements/Prerequisites*: Android build system, knowledge of system security, advanced git
134 17 Jeremy Rand
135 35 Paul Kocialkowski
*Expected Outcomes/Deliverables*: Integration or update of components of Replicant to tackle security issues
136 1 Jeremy Rand
137 36 Jeremy Rand
*Possible Mentors*: Wolfgang?
138 18 Jeremy Rand
139
h2. Port the Galaxy S3 and Galaxy Note 2 to Mainline Linux
140
141 48 Denis 'GNUtoo' Carikli
The Galaxy S3 and Galaxy Note 2 currently use a vendor fork of Linux, which poses a maintainability and security issue.  Forkbomb has done some initial work on porting these devices to use mainline Linux.  You can help by continuing this work. This would also enable theses devices to use generic hardware abstraction layers (HAL) when abstractions layers are ready, and to do some research on whether the "TrustZone operating system":https://blog.fossencdi.org/u-boot-galaxys3.html can be removed of such devices.
142 18 Jeremy Rand
143 22 Jeremy Rand
*Difficulty*: Medium to Hard
144 18 Jeremy Rand
145 22 Jeremy Rand
*Requirements/Prerequisites*: Knowledge of C
146 18 Jeremy Rand
147 22 Jeremy Rand
*Expected Outcomes/Deliverables*: Audio working, modem working, and Replicant or LineageOS booting with mainline Linux.
148 18 Jeremy Rand
149 31 Paul Kocialkowski
*Possible Mentors*: Forkbomb (confirmed), GNUtoo (confirmed)
150 17 Jeremy Rand
151 49 Denis 'GNUtoo' Carikli
h2. Fix the Free software distribution guidelines issues and improve the build system.
152 28 Denis 'GNUtoo' Carikli
153 29 Denis 'GNUtoo' Carikli
Replicant has some issues with FSDG compliance: F-droid repository is not FSDG compliant anymore, and Replicant can't be built from an FSDG distribution. Replicant should also not depends on pre-built dependencies anymore and build without issues.
154 28 Denis 'GNUtoo' Carikli
155
*Difficulty*: Easy
156
157
*Requirements/Prerequisites*: Knowledge of shell scripts and the ability to learn the Android build system
158
159 49 Denis 'GNUtoo' Carikli
*Expected Outcomes/Deliverables*: The ability to compile Replicant from an FSDG distribution, F-droid only showing FSDG compliant software.
160 28 Denis 'GNUtoo' Carikli
161 31 Paul Kocialkowski
*Possible Mentors*: GNUtoo (confirmed)
162 28 Denis 'GNUtoo' Carikli
163 3 Jeremy Rand
h2. Projects mentored by other organizations
164
165
h3. llvmpipe ARM optimizations
166
167
(Project description: TODO; can probably be adapted from https://redmine.replicant.us/projects/replicant/wiki/GraphicsResearch#llvmpipe .)
168
169
*Difficulty*: TODO
170
171
*Requirements/Prerequisites*: TODO
172
173
*Expected Outcomes/Deliverables*: TODO
174
175
Mesa would probably be a good organization for mentoring this project.  If interested in working on this project, please propose it to Mesa.  (We're happy to help.)