Project

General

Profile

Upstream » History » Version 408

Fil Lupin, 12/05/2020 12:17 AM
typo

1 12 Denis 'GNUtoo' Carikli
h1. Upstream Linux
2 1 Denis 'GNUtoo' Carikli
3 57 Denis 'GNUtoo' Carikli
{{>toc}}
4
5 362 Denis 'GNUtoo' Carikli
h2. Tracking upstream patches
6 100 Denis 'GNUtoo' Carikli
7 362 Denis 'GNUtoo' Carikli
We have a "new issue tracker":https://redmine.replicant.us/projects/upstreaming/issues for tracking upstream status of various patches.
8 100 Denis 'GNUtoo' Carikli
9 11 Denis 'GNUtoo' Carikli
h2. Benefits of using Upstream Linux
10 2 Denis 'GNUtoo' Carikli
11 11 Denis 'GNUtoo' Carikli
Currently, Replicant uses device specific Hardware Abstraction Layers, because device manufacturers implemented non-standard kernel interfaces. However, Android works with upstream 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).
12 2 Denis 'GNUtoo' Carikli
13
Benefits:
14
* It would allow supporting external WiFi dongles such as the ones supported by the ath9k_htc driver and free firmwares without the need for a specific application or configuration.
15 46 Denis 'GNUtoo' Carikli
* It would make devices last longer by alleviating the device specific maintenance burden: If LineageOS stops supporting a Replicant supported device, Replicant would need to maintain it by its own. This would require a lot of work, unless the device is already supported the upstream Linux kernel and generic hardware abstractions layers. This would also enable Replicant to support devices that are not currently supported by LineageOS with a lot less work.
16 11 Denis 'GNUtoo' Carikli
* It would enable the support for devices that are or will be added to upstream Linux.
17 2 Denis 'GNUtoo' Carikli
18 22 Denis 'GNUtoo' Carikli
As GNU/Linux expects standard kernel interfaces, this would also enable to run GNU/Linux out of the box on such devices.
19
This has some interesting outcomes:
20 46 Denis 'GNUtoo' Carikli
* The device specific work could be shared between GNU/Linux communities and Replicant communities. This could result in less work to do to support individual devices. Since Android libraries depends on Android's libc, non-standard proprietary libraries might be harder to reuse than the free software implementations, so we might get even more collaboration thanks to that.
21
* It would enable GNU/Linux distributions to more easily support smartphones and tablets, which would hopefully enable FSDG distributions to be able to focus on usability instead of hardware support. This way, if one day Android devices stop using the Linux kernel, stops being free software, or if the code takes directions that are too much problematic, already having GNU/Linux based Android alternatives would reduce the amount of work needed to be able to get again a fully free software distribution for smartphones and tablets.
22 23 Denis 'GNUtoo' Carikli
* Older devices with less amount of RAM than Replicant current minimum requirements could be used with GNU/Linux and possibly repurposed for other usages, reducing the amount of electronic devices waste.
23 22 Denis 'GNUtoo' Carikli
24 2 Denis 'GNUtoo' Carikli
h2. Requirements
25
26 404 Fil Lupin
* For the other standard interfaces (like ALSA, etc) a device running a upstream Linux Kernel with as few patches as possible is required.
27 2 Denis 'GNUtoo' Carikli
28 4 Denis 'GNUtoo' Carikli
h2. Devices
29
30 5 Denis 'GNUtoo' Carikli
It is best to use a device that requires the least amount of work to be functional under Replicant.
31
More precisely we want to minimize:
32 11 Denis 'GNUtoo' Carikli
* The work needed to have the device usable with upstream Linux.
33 5 Denis 'GNUtoo' Carikli
* The work porting or writing Android hardware abstractions layers.
34
35
To achieve that we can choose a device that:
36
* requires no or very minimal work to be fully supported by Linux.
37
* have less hardware features (so we don't need to support them in Linux and in the HALs).
38
* is easy to buy, so the work can be shared among multiple people.
39 53 Denis 'GNUtoo' Carikli
* doesn't have more freedom flaws than the devices currently supported by Replicant
40 5 Denis 'GNUtoo' Carikli
41 54 Denis 'GNUtoo' Carikli
It is also a good idea to keep one image per device at first, as trying to make a single image that
42 55 Denis 'GNUtoo' Carikli
would work on all ARM device supported by upstream Linux is complicated: Even GNU/Linux
43
distributions have a hard time doing that for ARM devices.
44 6 Denis 'GNUtoo' Carikli
45 58 Denis 'GNUtoo' Carikli
h2. Linux upstream status
46
47 403 Kurtis Hanna
In some cases, even if the upstream status looks good, nonfree bootloaders can get in the way. We have a list of stock bootloaders incompatible with upstream Linux in this page: [[BootloadersIncompatibleWithLinux]].
48 363 Denis 'GNUtoo' Carikli
49 400 Denis 'GNUtoo' Carikli
See "LinuxSupportedDevices":https://redmine.replicant.us/projects/upstreaming/wiki/LinuxSupportedDevices in the upstreaming sub project for the upstream status for various devices.
50 78 Denis 'GNUtoo' Carikli
51 134 Denis 'GNUtoo' Carikli
h1. Bootloaders
52 1 Denis 'GNUtoo' Carikli
53
h2. Bootloader status
54
55 402 Denis 'GNUtoo' Carikli
See the "BootloaderStatus":https://redmine.replicant.us/projects/upstreaming/wiki/BootloaderStatus page on the upstream subproject.
56 121 Denis 'GNUtoo' Carikli
57 1 Denis 'GNUtoo' Carikli
h2. See also
58
59
* [[Google Summer of Code 2018]]
60 12 Denis 'GNUtoo' Carikli
61 379 Denis 'GNUtoo' Carikli
h1. GNU/Linux components
62 19 Denis 'GNUtoo' Carikli
63 182 Denis 'GNUtoo' Carikli
h2. Modem support
64 1 Denis 'GNUtoo' Carikli
65 183 Denis 'GNUtoo' Carikli
|_. Protocols |_. Implmentation |_. comments |
66 190 Denis 'GNUtoo' Carikli
| QMI | Android <-> RIL <-> libqmi-ril to be completed <-> libqmi | |
67 184 Denis 'GNUtoo' Carikli
|/2. * QMI
68 1 Denis 'GNUtoo' Carikli
* AT
69 190 Denis 'GNUtoo' Carikli
* Other | Android <-> RIL <-> libraries to be written | 
70 226 Denis 'GNUtoo' Carikli
| "android_frameworks_opt_telephony_ril_ofono":https://github.com/scintill/android_frameworks_opt_telephony_ril_ofono + ofono + ofono backend (AT, QMI, etc) | * Using ofono would enable us to share more effort with upstream GNU/Linux and support many other protocol like AT for the GTA04 or qmi-ril for the Galaxy SIII 4G (I9305) or the Galaxy Note II 4G (N7105)
71 405 Fil Lupin
* According to the "README":https://github.com/scintill/android_frameworks_opt_telephony_ril_ofono/blob/master/README.md, it has already been tested with most of Replicant 6 code but on a smartphones not yet supported by Replicant. Calls, Audio, SMS, etc are known to work.
72 281 Kurtis Hanna
* "BuildRilWrapper.java":https://github.com/scintill/android_frameworks_opt_telephony_ril_ofono/blob/master/build/java/net/scintill/ril_ofono/BuildRilWrapper.java seems to use introspection to automatically generate the API between the Framework Java RIL and itself (which replaces rild) (See the "official documentation":https://source.android.com/devices/tech/connect/ril for background information on the Android architecture)
73 282 Kurtis Hanna
* Replicant and oFono based Java RIL "video presentation":https://redmine.replicant.us/projects/replicant/wiki/ContributorsMeetingJuly2019#Presentations |
74 198 Denis 'GNUtoo' Carikli
|/5. samsung-ipc | Ofono (rilmodem backend/driver) <-> rild <-> libsamsung-ril <-> libsamsung-ipc | * Might be usable for GNU/Linux distributions with "libhybris":https://en.wikipedia.org/wiki/Hybris_%28software%29
75 1 Denis 'GNUtoo' Carikli
* Could be usable for testing Replicant as ofono could run on the host computer and the rild socket could be exported with adb
76 197 Denis 'GNUtoo' Carikli
* Some forks exist: check if they still have interesting patches
77 281 Kurtis Hanna
* https://github.com/rilmodem/ofono|
78 347 Denis 'GNUtoo' Carikli
| Android <-> rild <-> libsamsung-ril <-> libsamsung-ipc | * Currently in use in Replicant
79
* Well integrated with Android
80
* Potentially usable by other distributions
81
* No known way to support different modems protocols in the same Replicant image with that |
82 189 Denis 'GNUtoo' Carikli
| Android <-> Ofono <-> libsamsung-ipc | * "An ofono fork with libsamsung-ipc support is available":https://github.com/fourkbomb/ofono
83 346 Denis 'GNUtoo' Carikli
"Patches":https://lists.ofono.org/pipermail/ofono/2012-September/013777.html to add that upstream were "refused":https://lists.ofono.org/pipermail/ofono/2012-September/013778.html because upstream didn't want to make the project become GPLv3 (libsamsung-ipc was GPLv3 at the time) but now libsamsung-ipc has been relicensed to GPLv2+
84
* Could be used to have generic a Replicant image supporting many devices with very different modems protocols (like libsamsung-ipc or QMI based ones) and have ofono do the modem detection |
85 185 Denis 'GNUtoo' Carikli
|
86 197 Denis 'GNUtoo' Carikli
| FSO <-> libsamsung-ipc | * Probably not easily usable in Replicant
87 194 Denis 'GNUtoo' Carikli
* Is FSO still actively maintained?
88 193 Denis 'GNUtoo' Carikli
* Was used by SHR and potentially other GNU/Linux distributions supporting the Openmoko GTA04 smartphones |
89 182 Denis 'GNUtoo' Carikli
90
h2. Upstream userspace hardware support libraries
91
92
|_. Usage |_. Replicant |_. GNU/Linux |_. comments |
93
| Bluetooth stack | BlueDroid | Bluez | |
94
| GPS hardware support | ? | gpsd | |
95
96 16 Denis 'GNUtoo' Carikli
97 20 Denis 'GNUtoo' Carikli
h2. Upstream non-hardware specific userspace
98 18 Denis 'GNUtoo' Carikli
99
|_. Usage |_. Replicant |_. GNU/Linux |_. comments |
100 151 Denis 'GNUtoo' Carikli
| Unix command line tools | ? | * Busybox
101
* Coreutils | * Busybox already has Android specific code in it but no Android.mk 
102
* Busybox build is very similar to Linux, and Linux can be built by Android |
103 44 Denis 'GNUtoo' Carikli
104 354 Denis 'GNUtoo' Carikli
h2. MTP
105
106 355 Denis 'GNUtoo' Carikli
TODO: 
107
* look at https://github.com/viveris/uMTP-Responder to see if it can be integrated in Android. It is known to work with the upstream kernel.
108
* Also compare with other implementation, including the Android one.
109 354 Denis 'GNUtoo' Carikli
110 229 Denis 'GNUtoo' Carikli
h2. libc
111
112
|_. Feature |_. Advantages |_. Disadvantages |_. sustainability |
113
| glibc + libhybris | * You just need an Android.mk to compile GNU/Linux software | * You need to link the Android part that need bionic functions to libhybris | TODO: Evaluate how close to bionic is libhybris |
114
| bionic | Android default | * You spend lot of time trying to run GNU/Linux debug tools like evtest on Android:
115
* Parabola cannot be used on old kenrels (FATAL: kernel too old)
116
* GuiX and libreCMC might not have the package and might need tweaking to be recompiled with an old glibc and kernel headers
117
* TODO: try crosstool-ng
118 230 Denis 'GNUtoo' Carikli
* Most of the other GNU/Linux distributions are not FSDG compliant or do not support ARM
119
* The software might not work on Android due to missing bionic functions like versionsort(...) |
120 229 Denis 'GNUtoo' Carikli
121 44 Denis 'GNUtoo' Carikli
h2. Other projects interested in using upstream Linux and/or contributing to it
122
123 339 Kurtis Hanna
h3. PostmarketOS
124
"pmOS wiki: upstream kernel":https://wiki.postmarketos.org/wiki/The_Mainline_Kernel
125
"pmOS wiki: i9305 with upstream kernel":https://wiki.postmarketos.org/wiki/Samsung_Galaxy_SIII_LTE_(samsung-i9305)#Mainline_Kernel
126
127 340 Kurtis Hanna
h3. O-DROID
128
129
h3. osmocomBB
130
131
h3. Mali
132
133
h3. LineageOS
134
135
h3. oFono
136
137
h3. Parabola
138 116 Denis 'GNUtoo' Carikli
139 380 Denis 'GNUtoo' Carikli
h1. GNU/Linux distributions
140 318 Denis 'GNUtoo' Carikli
141 320 Denis 'GNUtoo' Carikli
h2. Halium
142
143 318 Denis 'GNUtoo' Carikli
Some GNU/Linux distributions like Plasma Mobile, LuneOS, Ubuntu Touch use libhybris through the "Halium project":https://halium.org/ to reuse proprietary Android libraries
144 1 Denis 'GNUtoo' Carikli
145 323 Denis 'GNUtoo' Carikli
h2. Mer
146
147 324 Denis 'GNUtoo' Carikli
* Mer uses ofono for handling the modem
148
* For OpenGL it's not clear if they use nonfree drivers. It would be worth looking into it. Their stack seem to be able to use free implementations as well as nonfree implementations.
149 323 Denis 'GNUtoo' Carikli
150
See the "Mer architecture":https://wiki.merproject.org/wiki/Architecture for more details.
151
152 320 Denis 'GNUtoo' Carikli
h2. PostmarketOS
153
154 322 Denis 'GNUtoo' Carikli
"PostmaketOS":https://postmarketos.org/ is probably not using libhybris at all and is instead working with upstream and probably doesn't depend on nonfree libraries
155 320 Denis 'GNUtoo' Carikli
156
h2. Replicant strategies
157
158 381 Denis 'GNUtoo' Carikli
Replicant is currently involved with upstream GNU/Linux, but it would probably be a good idea to collaborate more with  distributions that don't depend on libhybris.
159 318 Denis 'GNUtoo' Carikli
160 378 Denis 'GNUtoo' Carikli
h1. Android distributions
161 1 Denis 'GNUtoo' Carikli
162 384 Denis 'GNUtoo' Carikli
h2. AOSP
163
164
AOSP doesn't support many devices, but it seem to support some devboards. 
165
166
The advantage is that in general devboards are well supported by upstream kernels.
167
168 385 Denis 'GNUtoo' Carikli
Supported devboards[1]?:
169 384 Denis 'GNUtoo' Carikli
| Devboard | Freedom issues | Comments |
170
| Beagleboard-X15 | No free GPU driver | Well supported by GNU/Linux, free bootloader |
171
| Cuttlefish emulator | ? | ? |
172 1 Denis 'GNUtoo' Carikli
| Other | ? | ? |
173 385 Denis 'GNUtoo' Carikli
174
The official documentation also "mentions some devboards":https://source.android.com/setup/build/devices .
175 384 Denis 'GNUtoo' Carikli
176
fn1. Some of the devboards in this page are probably supported: https://wiki.linaro.org/AOSP#AOSP_Dev_Board_Reference_Information
177
178 150 Denis 'GNUtoo' Carikli
h2. LineageOS
179 141 Denis 'GNUtoo' Carikli
180 327 Denis 'GNUtoo' Carikli
See "device-support-requirements.md":https://github.com/LineageOS/charter/blob/master/device-support-requirements.md for more information on LineageOS expectations.
181 120 Denis 'GNUtoo' Carikli
182 327 Denis 'GNUtoo' Carikli
Replicant has "a script":https://git.replicant.us/replicant/vendor_replicant-scripts/tree/research that is able to parse the "LineageOS wiki data":https://github.com/LineageOS/lineage_wiki . That can be useful to find information on devices supported by LineageOS.
183 326 Denis 'GNUtoo' Carikli
184 325 Denis 'GNUtoo' Carikli
The "devices supported by LineageOS 16":https://wiki.lineageos.org/devices/ have either:
185
* A Qualcomm SOC with an integrated modem inside (MSM*) for many devices
186
* A Qualcomm SOC without a modem inside (APQ*) for many devices
187 1 Denis 'GNUtoo' Carikli
* A HiSilicon Kirin 970 SOCs for devices like:
188 326 Denis 'GNUtoo' Carikli
** The "Huawei Honor View 10":https://wiki.lineageos.org/devices/berkeley
189 325 Denis 'GNUtoo' Carikli
** The "Huawei P20 Pro":https://wiki.lineageos.org/devices/charlotte
190
* A Samsung Exynos 7580 SOC for the following device
191 328 Denis 'GNUtoo' Carikli
** "Galaxy S5 Neo":https://wiki.lineageos.org/devices/s5neolte (Smartphone): It has shared memory between the modem and the SOC
192 120 Denis 'GNUtoo' Carikli
193 1 Denis 'GNUtoo' Carikli
It may be because they rely on nonfree software to support devices, which has not been ported to Android 9, or may be because they need more time to add devices with other SOCs like exynos.
194 141 Denis 'GNUtoo' Carikli
195 388 Denis 'GNUtoo' Carikli
h2. CustomROMs
196
197
CustomROMs seem to be a space for unofficial port of LineageOS. The idea is probably to develop the port until they manage to meet LineageOS's "device-support-requirements.md":https://github.com/LineageOS/charter/blob/master/device-support-requirements.md . When the requirements are met, they are probably included in LineageOS directly.
198
199
Interesting ports:
200
* The Galaxy SIII (GT-I9300) is being ported to more recent LineageOS versions. There is "a thread on the collaboration with Replicant":https://github.com/CustomROMs/android_local_manifests_i9300/issues/1 in github. The person/people doing the port seem to alternate between an upstream kernel and a older kernel based on the vendor code depending on the amount of work required to finish the port and/or the difficulties encountered. As we are also using a kernel based on upstream Linux we collaborate on that part by reusing each other work when applicable.
201
202 374 Denis 'GNUtoo' Carikli
h2. DivestOS Mobile
203
204
This distribution is based on LineageOS. While they seem to reuse nonfree software to make the hardware work, they spent some time cleaning up LineageOS code itself.
205
206
For instance it contains patches to remove privacy issues and nonfree software included in CyanogenMod or LineageOS.
207
208 375 Denis 'GNUtoo' Carikli
As we need to do that too in Replicant as long as we use LineageOS as base, it would be interesting to collaborate more with DivestOS on that part.
209
210 374 Denis 'GNUtoo' Carikli
Web site:
211
*https*: https://divestos.org/
212
*Onion*: http://6sdlxbqgcxdbkvysoir2qvqqs5ro3fxgyl3phvuphcdyklv7rg57jhid.onion
213
214 376 Denis 'GNUtoo' Carikli
h2. Fairphone
215
216
As October 2020, they are porting the Fairphone 2 to Android 9. However to do that, they are using 3.4 kernel and not any upstream kernels.
217
218 406 Fil Lupin
In addition, they don't seem very interested in free software bootloaders, and the Fairphone 1 and 2 use Qualcomm System On a Chip.
219 376 Denis 'GNUtoo' Carikli
220
However they are probably interested in free software libraries to make the port to newer Android versions easier.
221
222 382 Denis 'GNUtoo' Carikli
h2. Android x86
223
224
At the time of writing, the most recent images are RC images for Android 9, but there are branches for Android 10.
225
226
As they use (mostly?) upstream kernels, they sometimes have interesting code.
227
228
*Source code*: https://git.osdn.net/view?a=project_list;pf=android-x86
229 383 Denis 'GNUtoo' Carikli
*Manifest*: git://git.osdn.net/gitroot/android-x86/manifest.git
230 382 Denis 'GNUtoo' Carikli
231
Branches[1]: 
232
233
| Branch | Android version |
234
| q-x86 | 10.0 |
235
| pie-x86 | 9.0 |
236
| oreo-x86 | 8.1 |
237
| nougat-x86 | 7.1 |
238
| marshmallow-x86 | 6.0 |
239
| lollipop-x86 | 5.1 |
240
| kitkat-x86 | 4.4 |
241
| jb-x86 | 4.3 |
242
| ics-x86 | 4.0 |
243
| honeycomb-x86 | 3.2 |
244
| gingerbread-x86 | 2.3 |
245
| froyo-x86 | 2.2 |
246
| eclair-x86 | 2.1 |
247
| donut-x86 | 1.6 |
248
| cupcake-x86 | 1.5 |
249
 
250
fn1. https://www.android-x86.org/source.html
251
252 150 Denis 'GNUtoo' Carikli
h2. AOSP and LineageOS
253 141 Denis 'GNUtoo' Carikli
254
| Feature | AOSP | LineageOS |
255
| Code quality | Better than LineageOS | |
256 142 Denis 'GNUtoo' Carikli
| Documentation | Better than LineageOS | |
257 141 Denis 'GNUtoo' Carikli
| root | Not sure if supported or not | Supported |
258 200 Denis 'GNUtoo' Carikli
| Minor release versioning | supported with Git tags | Not supported.
259 202 Denis 'GNUtoo' Carikli
For instance frameworks/native has no LineageOS tags (only cm-1x tags) and has no other branch for lineage OS 16.0 than the lineage-16.0 branch, as the other branches name are for other things. This was confirmed after running 'git fetch github' in frameworks/native to fetch the other branches that are not fetched by repo by default.
260 200 Denis 'GNUtoo' Carikli
Despite that, some code was even merged in after the lineage-16.0 release:
261
<pre>
262
commit 22abc3cf4077644463a2dc1c59a5a74e9518ea16
263
Merge: 9e96d54 8a6b6c3
264
Date:   Sat Jul 13 18:57:45 2019 +0200
265
266
    Merge remote-tracking branch 'aosp/pie-gsi' into lineage-16.0-pie-gsi
267
</pre> |
268 141 Denis 'GNUtoo' Carikli
| GUI features for developers
269
* Advanced reboot | ? | Supported |
270 407 Fil Lupin
| Integrated kernel builds | Unsupported | Supported |
271 155 Denis 'GNUtoo' Carikli
272 306 Denis 'GNUtoo' Carikli
h2. Building a collaboration with other Android distributions
273
274
Given that:
275
* Replicant doesn't want to support devices that have more freedom issues than the ones currently supported.
276 407 Fil Lupin
* Many other Android distributions probably don't have the same goals with the freedom of the devices they support.
277 306 Denis 'GNUtoo' Carikli
* Replicant 9 is based on upstream Linux and will have to maintain its userspace libraries.
278
* Some users may still want to support devices that have more freedom issues than the ones supported by Replicant.
279
280
It could be a good idea to share the maintenance of the code used to make Replicant 9 with other distributions.
281
282 155 Denis 'GNUtoo' Carikli
h2. Design decisions
283
284 256 Kurtis Hanna
Some decisions have been taken by upstream projects, for instance the the Android Open Source Project (AOSP) is pushing device manufacturers to use "signed bootloaders":https://source.android.com/security/verifiedboot/device-state#root-of-trust and not give the users the ability to replace those bootloaders. Therefor it is best to revisit such decisions and decide whether or not to implement a given feature.
285 1 Denis 'GNUtoo' Carikli
286 210 Denis 'GNUtoo' Carikli
h3. Various
287
288 1 Denis 'GNUtoo' Carikli
| Feature | Advantages | Disadvantages |
289
| adb and root at boot | Easier to debug:
290
* We get the logs at boot
291
* May be able to diagnose non-booting devices (partition not mountable, etc) | Way less secure:
292
* Vulnerable to "Juice_Jacking":https://en.wikipedia.org/wiki/
293
* Vulnerable to an attacker that just connect an usb cable to a running phone
294
* Breaks the user's expectation of security (lock screen etc) |
295 210 Denis 'GNUtoo' Carikli
296 377 Denis 'GNUtoo' Carikli
We can get both: we can enable users to get logs at boot while avoiding any security issues. 
297
298
To do that we can keep disable adb and root disabled at boot, and enable users to add it back by editing the boot.img or recovery images. We have a tutorial for that in the [[AddingADBRootToAnImage]] page and we are working on script to automate it even more.
299
300 210 Denis 'GNUtoo' Carikli
h3. root filesystem related
301
302
|_. Feature |_. Advantages |_. Disadvantages |_. sustainability |
303
| System as root | * The kernel size can be bigger
304
* You have to hardcode the root partition in the cmdline or use PARTLABEL which might be a security issue: if a microSD has a partition named SYSTEM, the kernel may boot on it instead | having an initramfs adds some flexibility:
305
* Selecting partitions can potentially be more  flexible | |
306
| System as root + dm-verity + "dm-init":https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/device-mapper/dm-init.txt | * The kernel size can be bigger
307
* The partition selection is flexible and secure  | | |
308
| read-only /system | * more secure and more easily understandable by users and developers | * need to ship in replicant user-scripts or add them to vendor/ | |
309 160 Denis 'GNUtoo' Carikli
310
h3. Gatekeeper HAL backend
311
312 209 Denis 'GNUtoo' Carikli
*Background information*: Gatekeeper is a daemon that is used to store passwords and other secrets.
313
314 1 Denis 'GNUtoo' Carikli
| Backend used | Advantages | Disadvantages |
315 161 Denis 'GNUtoo' Carikli
| simple userspace implementation | * Fast to do
316 213 Denis 'GNUtoo' Carikli
* Simple to understand 
317
* Good enough for most use cases| |
318 164 Denis 'GNUtoo' Carikli
| kernel keyring (man 7 keyrings) | * Secure
319 294 Kurtis Hanna
* The Linux kernel is well known and updated regularly
320 215 Denis 'GNUtoo' Carikli
* Some users are already used to the userspace/kernel security model
321 408 Fil Lupin
* Probably fun to implement, can learn how to implement Android daemons and how to use the keyring along the way |
322 1 Denis 'GNUtoo' Carikli
| Free software Trusted Execution Environment (TEE) | * Android does it | * Require access to TrustZone, which doesn't work for all SOCs
323 294 Kurtis Hanna
* Unfamiliar to users and developers (it's supposed to tick in suspend, knowledge about TrustZone is less spread than Linux, etc)
324 214 Denis 'GNUtoo' Carikli
* Probably requires to port a TrustZone OS to every SOC or phone 
325 294 Kurtis Hanna
* The Linux kernel is well known and updated regularly |
326 165 Denis 'GNUtoo' Carikli
| Proprietary software Trusted Execution Environment (TEE) | None: we really want to get rid of it if possible | 
327 160 Denis 'GNUtoo' Carikli
Cannot be trusted:
328
* Not free software
329
* Not under the user control |
330 203 Denis 'GNUtoo' Carikli
331
h3. Handling dynamic major/minor /dev/ nodes
332
333 219 Denis 'GNUtoo' Carikli
*Background information*: We can manage to avoid this use case for now.
334 207 Denis 'GNUtoo' Carikli
335 203 Denis 'GNUtoo' Carikli
| Backend used | Advantages | Disadvantages | sustainability |
336 205 Denis 'GNUtoo' Carikli
| Android default + Upstream Linux | | * does not work by default, probably impossible to make it work as-is |
337 204 Denis 'GNUtoo' Carikli
| Android default + Upstream Linux + very dirty userspace scripts | * Minimal changes | * Not robust
338
* Might eat up resources
339
* Already implemented cleanly in mdev | |
340
| Android default + hacked drivers to use fixed major/minor | * Minimal changes in Linux
341
* No changes required on Android side | * Require to change userspace software (libsamsung-ipc) | * Not upstreamable in Linux |
342 294 Kurtis Hanna
| devtmpfs + hacked Android init | * Minimal changes if upstreamed
343
* Init is hard to debug | * Complex to do as debugging at this stage is complicated | * Need to be upstreamed in Android |
344 1 Denis 'GNUtoo' Carikli
| Stock Andrdroid init + mdev (busybox) | * Bad integration in the Android build system | * Changes are minimal | * Android build system integration need to be upstreamed or maintained |
345 219 Denis 'GNUtoo' Carikli
346
h3. Firmware loading
347
348
| Backend used | Advantages | Disadvantages | sustainability |
349
| system/core/init/firmware_handler.cpp | * Stock Android implementation | None | Already upstream in Android |
350
| Something else | None | The stock Android implementation is good enough and firmware loading is trivial anyway | Not upstream in Android |
351 220 Denis 'GNUtoo' Carikli
352 305 dl lud
h3. Embeddable web engine
353 296 Denis 'GNUtoo' Carikli
354 299 dl lud
The Android API for embedding a web engine is WebView.
355 1 Denis 'GNUtoo' Carikli
356
| Project | Comments |
357 305 dl lud
| "AOSP WebView API implemented with Chromium":https://developer.android.com/reference/android/webkit/WebView | * Built from Chromium compiled for WebView
358 1 Denis 'GNUtoo' Carikli
* Latest additions to the API seem more and more tied to Chromium (e.g. getWebViewRenderProcess, getWebChromeClient) | 
359 305 dl lud
| Old AOSP WebView API implemented with WebKit | * Not used anymore, since Android 4.4
360
* Does not implement the current WebView API |
361 299 dl lud
| "GeckoView":https://mozilla.github.io/geckoview/ | * Not the same API as WebView 
362
* Could be used to implement WebView
363
* Would need to be modified to expose more features from Gecko (e.g. zoom) while others are straightforward |
364 300 dl lud
| "Qt WebEngine":https://doc.qt.io/qt-5/qtwebengine-index.html | * Not the same API (C++ instead of Java)
365 299 dl lud
* Probably the smallest subset of Chromium available |
366 304 Denis 'GNUtoo' Carikli
| "Wine Internet Explorer implementation":https://wiki.winehq.org/Gecko | * Uses Gecko under the hood
367 296 Denis 'GNUtoo' Carikli
* Might be interesting to look at how they did it |
368
369 312 Denis 'GNUtoo' Carikli
h1. Web engine backend
370 296 Denis 'GNUtoo' Carikli
371 313 Denis 'GNUtoo' Carikli
We have an issue with webview (bug #1780):
372
* Using a recent webview based on chromium would create freedom issues as we don't know the license of chromium
373
* Using and old webview based on webkit would bring back many security issues
374
375
To solve that we need to find a solution that depends on a good upstream as we are not going to write a web browser engine ourselves.
376
377 314 Denis 'GNUtoo' Carikli
h2. Upstream web browser engine comparison
378
379
This lists upstream projects that are not forks tracking another upstream project.
380 313 Denis 'GNUtoo' Carikli
381 298 Denis 'GNUtoo' Carikli
| Project | Comments |
382 296 Denis 'GNUtoo' Carikli
| Gecko | * Clear licensing
383 315 Denis 'GNUtoo' Carikli
* Friendly upstream: The tor-browser project works with Mozilla to upstream privacy features in Firefox. So we could probably work with them as well too. |
384 1 Denis 'GNUtoo' Carikli
| Chromium | * Unclear licensing 
385 315 Denis 'GNUtoo' Carikli
* Google has goals for Chromium that are directly opposed to our goals (tracking, linked to google)
386
* Probably unfriendly upstream because of the opposed goals |
387 1 Denis 'GNUtoo' Carikli
| Webkit | ? |
388 315 Denis 'GNUtoo' Carikli
389
h2. Forked web browser engine comparison
390
391
TODO: Add various chromium versions here.
392 220 Denis 'GNUtoo' Carikli
393 317 Denis 'GNUtoo' Carikli
h2. How and if to implement a webview compatible API
394
395
TODO
396
397 307 Denis 'GNUtoo' Carikli
h1. Tools and build systems
398
399
Replicant has an issue with licensing (bug #1973) where we don't know under which license is Replicant. This due to the fact that the Android build system doesn't use a package manager during the build, and so it doesn't have license definition for each repositories.
400
401
A good way to fix that and also gain the ability to natively build GNU/Linux components like MESA or ofono would be to use a build system that use a package during at least during the build.
402
403
Some other communities have issues that do or could also benefit from that:
404
* GNU/Linux distributions need to package Android tools which are built with the custom Android build system
405 309 Denis 'GNUtoo' Carikli
* Some distributions mixes GNU/Linux and Android
406 1 Denis 'GNUtoo' Carikli
407 310 Denis 'GNUtoo' Carikli
h2. Projects
408 308 Denis 'GNUtoo' Carikli
409 309 Denis 'GNUtoo' Carikli
|_. Project |_. use case |_. Comments |
410 396 Denis 'GNUtoo' Carikli
| Android | - Build images
411 395 Denis 'GNUtoo' Carikli
- Build the Android NDK and SDK
412 398 Denis 'GNUtoo' Carikli
- Build the Android tools | - Wrapping build systems (like autotools, cmake, etc) is way too primitive:
413 395 Denis 'GNUtoo' Carikli
-- In LineageOS (not AOSP) The kernel is wrapped with .mk files, but the downside is that it runs make inside Linux source each time it needs to compile something
414
-- In AOSP there is no infrastructure for building software with other build systems, still mesa is built in it, but not the kernel |
415 397 Denis 'GNUtoo' Carikli
| Archlinux | - Build and package Android tools(Fastboot, adb, etc) | - relies on a "fragile script":https://git.archlinux.org/svntogit/community.git/tree/android-tools/trunk/generate_build.rb
416 395 Denis 'GNUtoo' Carikli
- The package for Android tools is self contained and doesn't have its dependencies (like liblog, libcutils, etc) splited in other packages | 
417 392 Denis 'GNUtoo' Carikli
| Debian | | relies on "custom Makefiles":https://salsa.debian.org/android-tools-team/android-tools/tree/master/debian/makefiles |
418 395 Denis 'GNUtoo' Carikli
| [[GuixBuildSystem|Guix]] | - Build android tools 
419
                             - Build the android ndk | Findings:
420
                                                       - Guix uses "android-make-stub":https://github.com/daym/android-make-stub.git to wrap Android.mk 
421
                                                       - We have real packaging of dependencies, however not all dependencies are exported, most are though
422
                                                       - The Android build system is wrapper in a ndk-android-build-system function
423
                                                       - The package definition needs very light and straigtforward patching. See [[GuixBuildSystem|Guix]] for more details. |
424 309 Denis 'GNUtoo' Carikli
| "The GNU/Linux distribution of quectel-modems":https://osmocom.org/projects/quectel-modems | Mix an Android kernel with GNU/Linux userspace | |
425 316 Denis 'GNUtoo' Carikli
| "AsteroidOS":https://github.com/AsteroidOS/asteroid/blob/master/prepare-build.sh#L68 | Mix an Android kernel with GNU/Linux userspace | |
426 1 Denis 'GNUtoo' Carikli
| "openembedded-android":https://github.com/anguslees/openembedded-android | Build the Android NDK? | strongly outdated version of openembedded |