Active development has moved towards LineageOS 17 (based on Android 10).
The basic features working on Replicant 9 have been confirmed to work on Replicant 10, but not everything has been tested yet on either version. Replicant 9 source code and build instruction have been kept to do regression tracking: Porting Replicant to Android 9.
$ repo init -u https://git.replicant.us/replicant-9/manifest.git -b replicant-10-dev $ repo sync
Alternatively a shallow copy of the source tree can be fetched in order to save on disk space:
$ repo init -u https://git.replicant.us/replicant-9/manifest.git -b replicant-10-dev --depth=1 $ repo sync -c
To unshallow a specific module:
$ cd path/to/module $ git fetch --unshallow <remote>
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 pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev sudo apt-get install gcc-5-arm-linux-gnueabi
By default, the Android 10 build system can only use the prebuilt binaries it ships. However, in Replicant's path to freedom, we would like to use the system binaries instead. Setting the following envrionment variable allows that:
$ export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true
Note that setting this variable does not automatically make the build system use the system binaries, it just allows it. Prebuilts are still being used now. Lots of further effort must be put into transitioning to the system binaries.
Not 100% sure if this is still needed:
$ subject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com' $ mkdir .android-certs $ for x in releasekey platform shared media testkey; do \ ./development/tools/make_key .android-certs/$x "$subject"; \ done
To avoid the following error:
16:20:13 See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information. [ 3% 2585/70375] build out/target/product/i9305/gen/STATIC_LIBRARIES/libmesa_nir_intermediates/nir/nir_builder_opcodes.h FAILED: out/target/product/i9305/gen/STATIC_LIBRARIES/libmesa_nir_intermediates/nir/nir_builder_opcodes.h /bin/bash -c "python external/mesa3d/src/compiler/nir/nir_builder_opcodes_h.py external/mesa3d/src/compiler/nir/nir_opcodes.py > out/target/product/i9305/gen/STATIC_LIBRARIES/libmesa_nir_intermediates/nir/nir_builder_opcodes.h" Traceback (most recent call last): File "external/mesa3d/src/compiler/nir/nir_builder_opcodes_h.py", line 106, in <module> from mako.template import Template ImportError: No module named mako.template 16:20:20 ninja failed with: exit status 1
You need to run the following command:
$ cd prebuilts/build-tools/path/linux-x86/ $ rm python && ln -s /usr/bin/python python
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:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
The heap size can be increased with an envirnoment variable:
$ export _JAVA_OPTIONS="-Xmx4g"
$ source build/envsetup.sh $ export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true $ lunch lineage_i9305-eng $ make bacon
$ cd out/target/product/i9305/obj/PACKAGING/target_files_intermediates/lineage_i9305-target_files-eng.<username>/IMAGES $ sudo heimdall flash --BOOT boot.img --USERDATA userdata.img --SYSTEM system.img
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:
$ sudo adb shell * daemon not running; starting now at tcp:5037 * daemon started successfully i9305:/ # $ sudo adb kill-server $ adb shell * daemon not running; starting now at tcp:5037 * daemon started successfully error: no devices/emulators found
$ adb kill-server $ sudo adb shell * daemon not running; starting now at tcp:5037 * daemon started successfully i9305:/ #
You can also follow the boot progress with adb:
adb logcat adb logcat -b main
Note that the device can go into suspend at any time, so adb might be interrupted. That looks like that:
First you get a shell
$ sudo adb shell i9305:/ #
Then the connection is interrupted:
$ adb shell i9305:/ # [randomdev@fullyfreelaptop ]$
The effect with adb logcat is similar.
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.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:$ rm -rf .repo/manifests/ # This enables me to force push and rebase the manifest repository as well $ repo init -u https://git.replicant.us/replicant-9/manifest.git -b replicant-10-dev $ repo sync --force-sync
$ repo sync --force-sync
If you use Parabola, you may be interested in running Trisquel 8 in LXC.
To do that first debootstrap a Trisquel 8 rootfs.
Parabola's debootstrap does support Trisquel 8 and its manual has an example on how to do that:
$ man debootstrap [...] # debootstrap flidas flidas-root http://archive.trisquel.info/trisquel
Then you can use virt-manager to setup the LXC instance.
The advantages of this solution are that:First month of full time equivalent work:
Time estimation | Task | Comments |
---|---|---|
DONE | |
Only boots with graphics, not much more |
|
|
Builds under Trisquel8 |
|
* * * * * |
Status: * Boots with adb. * Has ultra slow graphics |
14h | find, remove and document proprietary software in LineageOS 16 | |
21h | find, remove and document privacy issues in LineageOS 16 | |
7h | |
applied |
7h | |
Now in 5.3 |
7h | rebrand LineageOS as Replicant | |
70h | |
See the modem status for more details |
Total: 147h (~1 month) |
* port libsamsung-ril and libsamsung-ipc to Android 9 * Make the modem driver and libsamsung-ipc work together |
157h | See the modem status for more details |
Total | 157h | ~1 month |
---|
Task | Time estimation | Comments |
---|---|---|
Look which sensor libraries can be used |
70h | Already done by the unofficial LineageOS port of the Galaxy SIII (i9300), needs testing |
add support for Audio with the upstream kernel driver | 70h | Might be way faster, depending on what Android 9 uses See also this bugreport |
|
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 * The work to factorize the code between the i9300 and i9305 still need to be done |
Total | 154h | ~1 month |
Task | Time estimation | Comments |
---|---|---|
create a recovery | 21h | |
add internal WiFi support and validate the functionality | 6h | |
add external WiFi dongles support | 20h | External dongles support might be tricky |
|
|
Mostly done: * The installation instructions are now generic enough. * Some long standing TODO were also done along the way like adding backup instructions for the EFS. * The current instructions are still for Replicant 6.0 and will need to be updated for Replicant 9.0 |
Task | Time estimation | Comments |
---|---|---|
Estimate the amount of work to Reduce the attack surface | ? | |
Estimate the amount of work to add in-system upgrades | ? |
1 The generic instructions were tested at Install parties in Paris
Galaxy Note II (N7100) | ||
---|---|---|
Task | Time estimation | Comments |
port the EA8061 LCD Linux driver | 35h | |
port the S6EVR02 LCD Linux driver | 35h | |
port the MAX77693 flash led Linux driver | 7h | |
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 |
port the sensors libraries and other device specific libraries | 70h | It's difficult to evaluate how much time it could take |
add support for Audio with the upstream kernel driver | 14h | Should be similar to the Galaxy SIII |
Galaxy Note 8.0 (N5100) and 8.0 WiFi (N5110) | ||
---|---|---|
Task | Time estimation | Comments |
Evaluate the time required to do the port | 14h | TODO |
Device | Time estimation | Comments |
---|---|---|
Galaxy S II (i9100) | Linux: devboard dts upstream? unknown status | |
Galaxy Note (N7000) | unknown Linux upstream status | |
Galaxy Nexus (I9250) | OMAP4, no dts upstream | |
Galaxy Tab 2 7.0 (P3100), 7.0 WiFi (P3110), 10.1 (P5100), 10.1 WiFi (P5110) | ||
GTA04 >= A4 | TODO: a RIL needs to be written, userspace GPS support is missing, audio scenarios, etc |
See Replican6Changes.
See the Samsung-ipc page.
Device(s) | Repository | status | Comments |
---|---|---|---|
i9300 | CustomROMs | * March 3 2019 release | |
i9300 | Team InFusion | * August 20 2019 release | Issues: * Uses a Samsung kernel * Uses too many nonfree libraries => Probably nothing we could reuse from its code |
N7100 | ComicoTeam | * September 13 2019 release | |
I9100 | XDA |
Repository | Tree path | Dependencies | Function | Comments |
---|---|---|---|---|
https://github.com/CustomROMs/android_hardware_samsung lineage-16.0 branch |
hardware/samsung/macloader | Loads the MAC Address of the WiFi network interface | Might be useful | |
hardware/samsung/wifiloader | Loads the wifi kernel module (like modprobe) and setup firmware filesystems permissions | May be useful | ||
hardware/samsung/audio | seems to contains ril related stuff as well | Look if the ril stuff is required, go for standard audio | ||
hardware/samsung/lineagehw/hidl/livedisplay | livedisplay is a feature similar to what redshift does on GNU/Linux | Not sure if it works with mainline | ||
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 | |
all other directories in hardware/samsung/exynos/ | nonfree firmwares, nonfree software?, smdk kernel? | audio/video decoding offload | Avoid using that | |
hardware/samsung/exynos3 | nonfree firmwares?, nonfree software?, smdk kernel? | some light libraries, display stuff (gralloc, etc), 2D acceleration (FIMG), camera (FIMC), 3D acceleration, etc | Avoid using that for now | |
hardware/samsung/exynos4 |