Project

General

Profile

PortingToAndroid11 » History » Version 18

Denis 'GNUtoo' Carikli, 05/03/2021 01:25 PM
update build launch: the kernel build is integrated and we ported replicant 6 script

1 1 Joonas Kylmälä
h1. Porting Replicant to Android 11
2
3
{{>toc}}
4
5
Active development has moved towards AOSP 11.
6
7 11 dl lud
The basic features working on Replicant 9 and 10 have been confirmed to work on Replicant 11, but not everything has been tested yet on either version. The source code and build instruction for both these previous versions have been kept to do regression tracking:
8
* [[DeprecatedPortingToAndroid9|Porting Replicant to Android 9]]
9
* [[DeprecatedPortingToAndroid10|Porting Replicant to Android 10]]
10 1 Joonas Kylmälä
11 12 Denis 'GNUtoo' Carikli
h2. Precautions
12
13
See [[RunningReplicant11]] before installing Replicant 11 on your device to not break it.
14
15 1 Joonas Kylmälä
h2. Building Replicant 11
16
17
h3. Source code
18
19
<pre>
20
$ repo init -u https://git.replicant.us/replicant-next/manifest.git -b replicant-11-dev
21
$ repo sync
22
</pre>
23
24
Alternatively a shallow copy of the source tree can be fetched in order to save on disk space:
25
26
<pre>
27
$ repo init -u https://git.replicant.us/replicant-next/manifest.git -b replicant-11-dev --depth=1
28
$ repo sync -c
29
</pre>
30
31
To unshallow a specific module:
32
33
<pre>
34
$ cd path/to/module
35
$ git fetch --unshallow <remote>
36
</pre>
37
38
h3. Build dependencies
39
40
h4. For Trisquel 8
41
42
<pre>
43 16 Denis 'GNUtoo' Carikli
sudo apt-get install bc bison build-essential bsdmainutils ccache curl flex g++-multilib gcc-multilib gettext git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop python-mako python3-mako pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev
44 1 Joonas Kylmälä
sudo apt-get install gcc-5-arm-linux-gnueabi
45
</pre>
46
47 14 Denis 'GNUtoo' Carikli
You will also need to install repo as described in the bug #2199.
48
49 15 Denis 'GNUtoo' Carikli
h4. For Trisquel 9
50 14 Denis 'GNUtoo' Carikli
51 15 Denis 'GNUtoo' Carikli
This section is a work in progress.
52
53
<pre>
54 17 Denis 'GNUtoo' Carikli
sudo apt-get install bc bison build-essential bsdmainutils ccache curl flex g++-multilib gcc-multilib gettext git gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop python-mako python3-mako pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev
55 15 Denis 'GNUtoo' Carikli
sudo apt-get install gcc-5-arm-linux-gnueabi
56
</pre>
57
58
You will also need to install repo as described in the bug #2199.
59 14 Denis 'GNUtoo' Carikli
60 1 Joonas Kylmälä
h3. Fixing the build environment
61
62
h4. Allow system binaries for building
63
64
By default, the Android 11 build system can only use the prebuilt binaries it ships.
65
66
While having binary toolchains is better for reproducible builds, and that the binaries are free software, this creates a number of issues:
67
* We need to be able to rebuild the binaries, and so far no one did it yet.
68
* Binaries are way harder to trust than source code and not everyone trust Google.
69
70
As GNU/Linux distribution's tools can be rebuilt and are easier to trust, we are using that for now.
71
72
h4. Java heap space
73
74
The Java heap size is automatically set according to the available system memory. On machines with 8 GB or less RAM, it is set to a value which is too low, and will result in the following error during the build:
75
76
<pre>
77
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
78
</pre>
79
80
The heap size can be "increased with an envirnoment variable":https://stackoverflow.com/a/60474592/1313087:
81
82
<pre>
83
$ export _JAVA_OPTIONS="-Xmx3g"
84
</pre>
85
86
h4. Reduce parallel jobs to avoid killed processes
87
88
Increasing the Java heap space is not enough to get a successful build on machines with 8 GB or less RAM. It is also necessary to reduce the number of parallel jobs, to avoid processes from being killed due to lack of memory. This typically happens during the build of @frameworks/base@ components.
89
90
For greater speed, you may let your build run with the defaults, wait for it to fail due to killed processes, and then relunch the build with:
91
92
<pre>
93
$ make -j1
94
</pre>
95
96
By default, "Ninja":https://ninja-build.org/manual.html, the underlaying build system for Android, used when you run @make bacon@, computes the number of parallel jobs according to the number of CPUs on your machine (typically #CPUs + 2 parallel jobs).
97
98
h3. Launching the build
99
100 18 Denis 'GNUtoo' Carikli
You can either launch builds with our wrapper script like that:
101 1 Joonas Kylmälä
<pre>
102 18 Denis 'GNUtoo' Carikli
$ ./vendor/replicant/build.sh i9305
103
</pre>
104
105
Or manually launch it (so you could adjust the number of jobs with -j for instance):
106
<pre>
107 1 Joonas Kylmälä
$ source build/envsetup.sh
108 18 Denis 'GNUtoo' Carikli
$ lunch lineage_i9305-userdebug
109
$ make -j2
110 1 Joonas Kylmälä
</pre>
111 18 Denis 'GNUtoo' Carikli
112 1 Joonas Kylmälä
113
h3. Install the images
114
115
h4. From scratch
116 13 Denis 'GNUtoo' Carikli
117
118 1 Joonas Kylmälä
Due to the bug #2235 we can't use the same commands than before with Replicant 9 and 10:
119
<pre>
120
$ cd out/target/product/i9305
121
$ sudo heimdall flash --BOOT boot.img --USERDATA userdata.img --SYSTEM system.img 
122 13 Denis 'GNUtoo' Carikli
</pre>
123
124
Instead we have to install it in a different way:
125
* First we need to flash the images with @heimdall flash --BOOT boot.img  --RECOVERY recovery.img --SYSTEM system.img@
126
* Then we need to reboot to recovery during the boot by pressing the volume up, menu and power buttons
127
* Then we need to select @Wipe data/factory reset@ and then @Factory data reset@
128
* And finally we can boot to Replicant 11 by selecting @Reboot the system now@
129
130
131
132 1 Joonas Kylmälä
133
134
h4. Update previous installation
135
136
<pre>
137
adb remount
138
adb sync
139
</pre>
140
141
h3. Get adb
142
143
As the device IDs are the ones given by the Linux kernel, they are not in the adb udev rules, so for now it requires to run adb as root:
144
<pre>
145
$ sudo adb shell
146
* daemon not running; starting now at tcp:5037
147
* daemon started successfully
148
i9305:/ #                                 
149
$ sudo adb kill-server
150
$ adb shell
151
* daemon not running; starting now at tcp:5037
152
* daemon started successfully
153
error: no devices/emulators found
154
</pre>
155
So make sure to kill the adb-server and run it as root:
156
<pre>
157
$ adb kill-server
158
$ sudo adb shell
159
* daemon not running; starting now at tcp:5037
160
* daemon started successfully
161
i9305:/ # 
162
</pre>
163
164
h3. Boot progress
165
166
You can also follow the boot progress with adb:
167
<pre>
168
adb logcat
169
adb logcat -b main
170
</pre>
171
172
Note that the device can go into suspend at any time, so adb might be interrupted. That looks like that:
173
First you get a shell
174
<pre>
175
$ sudo adb shell
176
i9305:/ #
177
</pre>
178
179
Then the connection is interrupted:
180
<pre>
181
$ adb shell
182
i9305:/ # [randomdev@fullyfreelaptop ]$                                                                                                     
183
</pre>
184
185
The effect with adb logcat is similar.
186
187
h3. Getting the latest changes
188
189
* The repositories are being constantly modified with @git push --force@ as we are trying things out, and don't want to make the commits history look too dirty, so be sure to backup your local changes.
190
* Sometimes the manifest repository is also modified with @git push --force@. In that case the following commands will loose all the work you did locally but will make the repository consistent with upstream repositories again:
191
<pre>
192
$ rm -rf .repo/manifests .repo/manifests.git .repo/manifest.xml
193
$ repo init -u https://git.replicant.us/replicant-next/manifest.git -b replicant-11-dev
194
$ repo sync --force-sync
195
</pre>
196
* The following command might also be necessary to make the state consistent with upstream repositories again, when the manifest history wasn't rewritten, but it will also loose all the work you did locally: 
197
<pre>
198
$ repo sync --force-sync
199
</pre>
200 3 Denis 'GNUtoo' Carikli
201
h3. Known working distributions
202
203
|_. Distribution |_. Works |_. Comments |
204
| Trisquel 8 | Yes | Tested with an lxc chroot:
205 4 Denis 'GNUtoo' Carikli
                     * Builds images fine       |
206 3 Denis 'GNUtoo' Carikli
| Debian 10 | Yes | |
207 1 Joonas Kylmälä
208
h3. Build VM
209
210
If you use Parabola, you may be interested in running Trisquel 8 in LXC.
211
212
To do that first debootstrap a Trisquel 8 rootfs. 
213
214
Parabola's debootstrap does support Trisquel 8 and its manual has an example on how to do that:
215
<pre>
216
$ man debootstrap
217
[...]
218
# debootstrap flidas flidas-root http://archive.trisquel.info/trisquel
219
</pre>
220
221
Then you can use virt-manager to setup the LXC instance.
222
223
The advantages of this solution are that:
224
* The LXC guest and host shares their resources (CPU, RAM) with almost no penalty
225
* Trisquel 8 is not a rolling release distribution
226
227
The disadvantage of this solution are that:
228
* you need to configure the Trisquel 8 LXC instance (vimrc, sshd_config, etc)
229
* It's more complicated to setup
230
* The Android build system outputs a warning message about not being able to use namespaces which may become mandatory in newer Android versions
231 5 Denis 'GNUtoo' Carikli
232
h3. Known issues
233 9 Denis 'GNUtoo' Carikli
234 1 Joonas Kylmälä
h4. Trisquel 8
235 9 Denis 'GNUtoo' Carikli
236
With Trisquel 8 we have several issues.
237
238
First we can't update the repo, else we have:
239
<pre>
240
$ repo --force-sync
241
repo: error: Python 3 version is too old; Please use Python 3.6 or newer.
242
</pre>
243
244
The repo from the package may not work if you have python2 in /usr/bin/python.
245
246
To workaround both issues you could do that:
247
<pre>
248
$ sudo apt install repo
249
$ sudo install -m 755 /usr/bin/repo /usr/local/bin/
250
$ sudo sed 's&^#!/usr/bin/python$&#!/usr/bin/python3&' /usr/local/bin/repo -i
251
</pre>
252 10 Denis 'GNUtoo' Carikli
253 1 Joonas Kylmälä
h4. Using latest repo (from .repo/repo/repo) ?
254 10 Denis 'GNUtoo' Carikli
255
If you use your distribution's repo, you might have an old version of repo.
256
257 1 Joonas Kylmälä
When that happens, repo notify you about it:
258 10 Denis 'GNUtoo' Carikli
<pre>
259
... A new version of repo (2.8) is available.
260
... New version is available at: /home/replicant/replicant-11/.repo/repo/repo
261
... The launcher is run from: /usr/local/bin/repo
262
!!! The launcher is not writable.  Please talk to your sysadmin or distro
263
!!! to get an update installed.
264
</pre>
265
266
So in case you have a recent enough python3, you can upgrade.
267
268
Trisquel 8 doesn't have a recent enough python3 to do that.
269
270
h4. latest repo not working due to python2 in /usr/bin/python
271
272
If you have the latest repo and python2 is in /usr/bin/python, you might end with an issue like that:
273 5 Denis 'GNUtoo' Carikli
<pre>
274
$ repo init [...]
275
Traceback (most recent call last):
276
  File "[...]/replicant-11/.repo/repo/main.py", line 56, in <module>
277
    from subcmds.version import Version
278
  File "[...]/replicant-11/.repo/repo/subcmds/__init__.py", line 38, in <module>
279
    ['%s' % name])
280
  File "[...]/replicant-11/.repo/repo/subcmds/upload.py", line 27, in <module>
281
    from hooks import RepoHook
282
  File "[...]/replicant-11/.repo/repo/hooks.py", line 472
283
    file=sys.stderr)
284
        ^
285
SyntaxError: invalid syntax
286
</pre>
287
288
This is because /usr/bin/python is python2 instead of python3.
289 7 Denis 'GNUtoo' Carikli
290 5 Denis 'GNUtoo' Carikli
In that case you can use @python3 $(which repo)@ instead of @repo@) like that:
291
292
<pre>
293
$ python3 $(which repo) init [...]
294
</pre>
295
296
Or you can install repo in /usr/local/bin and modify the @#!/usr/bin/env python@ inside it with the following commands:
297 8 Denis 'GNUtoo' Carikli
<pre>
298 1 Joonas Kylmälä
$ sudo install -m 755 .repo/repo/repo -t /usr/local/bin
299
$ sudo sed 's&^#!/usr/bin/env python$&#!/usr/bin/env python3&' /usr/local/bin/repo -i
300 10 Denis 'GNUtoo' Carikli
</pre>
301
302 5 Denis 'GNUtoo' Carikli
Note that the sed command doesn't work for older versions of repo. See the section above about making it work on trisquel8 for one that works on older versions of repo.
303 1 Joonas Kylmälä
304
h2. Cleanups to be done
305
306
* Make adb work as user by using the right USB IDs, and make userspace do the USB setup.
307
* -Make the kernel not use hardcoded CMDLINE_FORCE- Not possible unless the bootloader is changed or Linux is very heavily patched.
308
* Make the kernel not use hardcoded partitions if possible (though we use system as root)
309
* Make a clean Gatekeeper HAL module implementation instead of using the same hack than goldfish
310
* Look at "init.rc":https://android.googlesource.com/platform/system/core/+/master/init/README.md documentation to see if init.rc can be overriden clearly with the override statement to see if it's possible to keep the serial console patch for -eng
311
312
h2. Upstreaming status
313
314
* The stock bootloader is incompatible with Linux, see [[BootloadersIncompatibleWithLinux#Devices-with-the-Exynos-4412]] for more information. So we maintain patches to enable the Galaxy SIII, and Galaxy Note II to boot with the stock bootloader. In the long run we need to look into using u-boot in the kernel partition as using u-boot instead of the stock bootloader currently require nonfree and non-redistributable software (BL1).
315
* For the patches that are not merged yet, see the "issues of the redmine upstreaming sub-project":https://redmine.replicant.us/projects/upstreaming/issues
316
317
h2. Graphics status
318
319
Progress of the graphics related tasks is tracked at [[GraphicsReplicant10]].
320
321
h2. Modem status
322
323
*libsamsung-ipc:* 
324
* Fully tested under GNU/Linux only
325
* Can initialize completely the modem and receive messages (see the #1954 bug report for the logs)
326
* Needs more cleanup but there is now a better abstraction
327
328
*libsamsung-ril:* 
329
* Ported to Replicant 9 using a wrapper for the API >=12 in libsamsung-ril source code that needs to be removed
330
* Tested under Replicant 9 without up to date libsamsung-ipc (no modem init)
331
* Tested and validated under Replicant 6 (doesn't break telephony)
332
333
h3. Modem status TODO
334
335
* Implement the missing part to shut down the modem, close the interfaces and such, in order to need to reboot after each test.
336
* Continue to clean up the libsamsung-ipc and libsamsung-ril patches, test the patches in Replicant 6 when applicable, and merge them in the upstream repositories.
337
* Convert the firmware loading driver to the upstream API and then adapt libsamsung-ipc for that. This should also benefit other devices like the Galaxy SIII 4G, and the Galaxy Note II 4G which probably don't need much more to get their modem supported by upstream Linux.
338
* Cleanup and convert the rest of the drivers to look like the ones for the Nokia N900 and adapt the userspace in libsamsung-ipc, and merge libsamsung-ipc support for that once the kernel API is stable.
339
* Test the code under Replicant 10 when the graphics status will enable to have decent enough speed to do some testing through human interaction.
340
341
h2. TODO
342
343
First month of full time equivalent work:
344
345
|_. Time estimation  |_.Task |_. Comments |
346
| DONE | -boot a device under AOSP9- | Only boots with graphics, not much more |
347
| -7h- DONE | -build it under a "FSDG compliant distribution":https://www.gnu.org/distros/free-distros.html like Trisquel8- | -WIP for AOSP, It's difficult to do precise time estimations as it could work out of the box or require one full time month of work depending on how much issues are encountered- 
348
Builds under Trisquel8|
349
| -21h- DONE | * -port the changes from AOSP9 to LineageOS 16-
350
* -cleanup the code-
351
* -build the kernel from the Android build system-
352
* -make sure it builds with an FSDG compliant distribution-
353
* -document the build procedure- |
354
Status:
355
* Boots with adb.
356
* Has ultra slow graphics |
357
| 14h | find, remove and document proprietary software in LineageOS 16 | |
358
| 21h | find, remove and document privacy issues in LineageOS 16 | |
359
| 7h | -Add support for the touch keys driver in the  galaxy-s3 dts- | "applied":https://lists.infradead.org/pipermail/linux-arm-kernel/2019-November/694100.html |
360
| 7h | -upstream the AAT1290 flash led Linux dts for the galaxy-s3 boards- | "Now in 5.3":https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.3&id=4e4dfcb2a425cccc6dd1fb7d46e060cd57999afc |
361
| 7h | rebrand LineageOS as Replicant | |
362
| 70h | -port and- cleanup the the Galaxy SIII (i9300) "modem":https://github.com/fourkbomb/linux/tree/modem Linux driver from 4.16 to 5.0| See the [[PortingToAndroid9/#Modem-status|modem status]] for more details |
363
|_\3. Total: 147h (~1 month) |
364
365
Second month of full time equivalent work:
366
| * port  libsamsung-ril and libsamsung-ipc to Android 9
367
* Make the modem driver and libsamsung-ipc work together | 157h | See the [[PortingToAndroid9/#Modem-status|modem status]] for more details |
368
|_. Total |_. 157h | ~1 month |
369
370
Third month of full time equivalent work:
371
|_. Task |_. Time estimation |_. Comments |
372
| -port the sensors libraries and other device specific libraries-
373
Look which sensor libraries can be used | 70h | Already done by the unofficial LineageOS port of the Galaxy SIII (i9300), needs testing |
374
| add support for Audio with the upstream kernel driver | 70h | Might be way faster, depending on what Android 9 uses
375
                                                               See also "this bugreport":https://github.com/CustomROMs/android_local_manifests_i9300/issues/1 |
376
| -add partial (no modem) support for the Galaxy SIII 4G (i9305) and- factorize the code with i9300 | 14h | * The source code on which the work was based changed from AOSP to an unofficial LineageOS port to a port of i9305 support for AOSP by Joonas to the official LineageOS so it's now supported by default
377
* The work to factorize the code between the i9300 and i9305 still need to be done |
378
 |
379
|_. Total |_. 154h | ~1 month |
380
381
|_. Task |_. Time estimation |_. Comments |
382
| create a recovery | 21h | |
383
| add internal WiFi support and validate the functionality | 6h | |
384
| add external WiFi dongles support | 20h | External dongles support might be tricky |
385
| -create new- update the install and upgrade instructions | -35h- | -Our current install instructions don't scale as we have one copy for each device.-
386
-We also created generic instructions but they tend to be harder to follow[1] than the device specific ones.-
387
-This will be made in a modular format (for instance in LaTeX) that enables to generate per device install instructions without requiring to have multiples copy of the same text.-
388
-The instructions will need to be able to be modified and compiled on an FSDG compliant distribution.-
389
Mostly done: 
390
* The installation instructions are now generic enough. 
391
* Some long standing TODO were also done along the way like adding backup instructions for the EFS.
392
* The current instructions are still for Replicant 6.0 and will need to be updated for Replicant 9.0 |
393
394
|_. Task |_. Time estimation |_. Comments |
395
| Estimate the amount of work to Reduce the attack surface | ? | |
396
| Estimate the amount of work to add in-system upgrades | ? | |
397
398
fn1. The generic instructions were tested at Install parties in Paris 
399
400
h3. Devices support:
401
402
h4. Easy, because it's similar enough to the Galaxy SIII (I9300)
403
404
|_\3. Galaxy Note II (N7100) |
405
|_. Task |_. Time estimation |_. Comments |
406
| port the EA8061 LCD Linux driver | 35h | |
407
| port the S6EVR02 LCD Linux driver | 35h | |
408
| port the MAX77693 flash led Linux driver | 7h | |
409
| android: add support for the Note II (N7100) and factorize the code with Galaxy SIII (i9300) and Galaxy SIII 4G (i9305) | 14h | Should be similar to the Galaxy SIII |
410
| port the sensors libraries and other device specific libraries | 70h | It's difficult to evaluate how much time it could take |
411
| add support for Audio with the upstream kernel driver | 14h | Should be similar to the Galaxy SIII |
412
413
|_\3. Galaxy Note 8.0 (N5100) and 8.0 WiFi (N5110) |
414
|_. Task |_. Time estimation |_. Comments |
415
| Evaluate the time required to do the port | 14h | TODO |
416
417
h4. Needs more work and unknown upstream Linux status
418
419
|_. Device |_. Time estimation |_. Comments |
420
| Galaxy S II (i9100) | | Linux: devboard dts upstream? unknown status |
421
| Galaxy Note (N7000) | | unknown Linux upstream status |
422
| Galaxy Nexus (I9250) | |/2. OMAP4, no dts upstream |
423
| Galaxy Tab 2 7.0 (P3100), 7.0 WiFi (P3110), 10.1 (P5100), 10.1 WiFi (P5110) | |
424
| GTA04 >= A4 | | TODO: a RIL needs to be written, userspace GPS support is missing, audio scenarios, etc |
425
426
h2. Documentation
427
428
h3. Replicant 6.0 changes
429
430
See [[Replican6Changes]].
431
432
h3. Other rebases
433
434
See the [[Samsung-ipc]] page.
435
436
h2. Other attempts
437
438
* It might be interesting to contact the people doing ports once we have something working well enough.
439
* It is also interesting to look at other attempts to understand if a given device is powerful enough to run Android 9 and what configuration was used to achieve it.
440
441
|_. Device(s) |_. Repository |_. status |_. Comments |
442
| i9300 | "CustomROMs":https://github.com/CustomROMs/android_local_manifests_i9300 | * "February 8 2020 Pie release":https://forum.xda-developers.com/galaxy-s3/development/rom-lineageos-16-0-t3875899 | |
443
| i9300 | "Team InFusion":https://github.com/team-infusion-developers/android_local_manifests_i9300 | * "August 20 2019 Pie release":https://forum.xda-developers.com/galaxy-s3/development/rom-optimized-lineageos-16-0-team-t3940142 | Issues: * Uses a Samsung kernel
444
* Uses too many nonfree libraries
445
=> Probably nothing we could reuse from its code |
446
| n7100 | "ComicoTeam":https://github.com/ComicoTeam/android_device_samsung_n7100 | * "January 4 2020 Pie release":https://forum.xda-developers.com/galaxy-note-2/development/rom-lineageos-16-0-20190112-comico-t3889281 | |
447
| i9100 | "rINanDO":https://github.com/rINanDO/android_device_samsung_galaxys2-common | * "March 20 2020 Pie release":https://forum.xda-developers.com/galaxy-s2/development-derivatives/pie-i9100-t3850588 
448
* "July 19 2020 Android 10 release":https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-lineageos-17-0-t4022733 | |
449
450
h3. Links for other attempts
451
452
* https://www.xda-developers.com/android-pie-android-9-port-custom-roms/
453
454
h3. CustomROMs i9300 components
455
456
|_. Repository |_. Tree path |_. Dependencies |_. Function |_. Comments |
457
|/8. https://github.com/CustomROMs/android_hardware_samsung
458
lineage-16.0 branch | hardware/samsung/macloader | | Loads the MAC Address of the WiFi network interface | Might be useful |
459
| hardware/samsung/wifiloader | | Loads the wifi kernel module (like modprobe) and setup firmware filesystems permissions | May be useful |
460
| hardware/samsung/audio | | seems to contains ril related stuff as well | Look if the ril stuff is required, go for standard audio |
461
| hardware/samsung/lineagehw/hidl/livedisplay | | livedisplay is a feature similar to what redshift does on GNU/Linux | Not sure if it works with mainline |
462
| hardware/samsung/exynos/multimedia/utils/ | seem meant for audio/video decoding offload | assembly obtimized color conversion and resize code | check assembly code license, not sure if useful |
463
| all other directories in hardware/samsung/exynos/ | nonfree firmwares, nonfree software?, smdk kernel? | audio/video decoding offload | Avoid using that |
464
| hardware/samsung/exynos3 |/2. nonfree firmwares?, nonfree software?, smdk kernel? |/2. some light libraries, display stuff (gralloc, etc), 2D acceleration (FIMG), camera (FIMC), 3D acceleration, etc |/2. Avoid using that for now |
465
| hardware/samsung/exynos4 |
466
467
h2. Known error messages that are safe to ignore
468
469
* TestHarnessModeService: Failed to start Test Harness Mode; no implementation of PersistentDataBlockManagerInternal was bound
470
* JniUtils: Could not load native library jni_latinimegoogle
471
472
h2. Links 
473
474
* "Android build requirements - hardware and software":https://source.android.com/setup/build/requirements
475
* "Why LineageOS Developers are building Android Go-optimized custom ROMs":https://www.xda-developers.com/android-go-old-android-8-1-oreo/
476
* "Android Go recommended default values for propreties for optimization":https://android.googlesource.com/platform/build/+/master/target/product/go_defaults_common.mk
477
* "Team InFusion i9300 optimized system.prop":https://github.com/team-infusion-developers/android_device_samsung_i9300/blob/lineage-16.0/system.prop#L23
478
* "Hack to fix high CPU usage caused by logd":https://github.com/team-infusion-developers/android_device_samsung_smdk4412-common/commit/c66015514fc9779edfed2665f67e841f3620c71e
479
* "Use low-end video codecs":https://github.com/team-infusion-developers/android_device_samsung_smdk4412-common/commit/adc919f04b981a4fe005fab2cf443596a22992b2
480
* "Optimize ActivityManager cached apps":https://github.com/team-infusion-developers/android_device_samsung_smdk4412-common/commit/24bc62970d35eb5a7a257463e7dbfe873ceb5779
481
* "Use 1Gb Dalvik config":https://github.com/team-infusion-developers/android_device_samsung_smdk4412-common/commit/8a7cebc5af772a2949420ac4a383f5f75236c65c