DeveloperGuide » History » Version 88

Denis 'GNUtoo' Carikli, 09/06/2019 02:58 PM
Separate submiting patches

1 31 Paul Kocialkowski
h1. Developer guide
2 1 Paul Kocialkowski
3 15 Paul Kocialkowski
5 3 Paul Kocialkowski
h2. Prerequisites
7 8 Paul Kocialkowski
Developing on Replicant isn't much harder than developing on any other free software project as it doesn't require specific knowledge. In fact, you'll probably learn a lot along the way regarding how hardware works, how the Android system is composed, how the kernel works, etc, but you don't need to know all of this to start. However a basic set of skills is required, among which:
8 83 Denis 'GNUtoo' Carikli
* C language programming skills and the ability to understand other languages such as C++, Java and shell scripts.
9 82 Denis 'GNUtoo' Carikli
* Makefile skills (no need to know every detail about it, a general idea of how Makefiles work is enough). If you don't know how Makefiles work, Wikipedia has "an good article on make": that has some examples Makefiles.
* Git skills (basically, how to commit changes, send them to our repos, dealing with branches without making a mess, etc). If you don't know git yet, you can find some documentation about Git at: to learn it.
11 3 Paul Kocialkowski
If you think you can cope with the requirements, then developing on Replicant should cause you no particular issue.
14 70 Wolfgang Wiedmeyer
The [[Index#Replicant-porting-guides|porting guides]] provide instructions for porting a new device to Replicant and also offer some tips for developing on Replicant.
15 3 Paul Kocialkowski
16 70 Wolfgang Wiedmeyer
Have a look at the [[Tasks]] page and feel free to [[Index#Contact|ask around]] for help to get started.
17 40 Wolfgang Wiedmeyer
18 70 Wolfgang Wiedmeyer
h3. Notes on writing free software replacements
19 59 Wolfgang Wiedmeyer
20 70 Wolfgang Wiedmeyer
Writing free software replacements for non-free components may require more skills depending on what you're trying to achieve, though there may be people with the adequate knowledge to help you and from whom you will likely learn a lot.
21 50 Wolfgang Wiedmeyer
22 88 Denis 'GNUtoo' Carikli
h2. Code hosting
23 40 Wolfgang Wiedmeyer
24 1 Paul Kocialkowski
Replicant's source code is hosted at "": If you plan to contribute to Replicant, you are welcome to host your Replicant-related projects there under your own username there. You only need to [[People#Active-developers|contact one of Replicant's developers]] and ask for an account. Please include in your request the name, username and Email address that should be used for creating your account. Your repos will then show up on the "contributor repos": page.
25 88 Denis 'GNUtoo' Carikli
h2. Submitting patches
27 40 Wolfgang Wiedmeyer
28 53 Wolfgang Wiedmeyer
Replicant currently doesn't accept merge requests. There are two ways to get your patches included: You can either send them to the "mailing list": or open an issue on the "issue tracker":/projects/replicant/issues and attach the patches to the issue. Replicant developers will then review your changes.
29 40 Wolfgang Wiedmeyer
30 75 Kurtis Hanna
See the Git documentation for "creating a patch": Patches can be sent with "@git send-email@": If it's too much hassle for you to set up @git send-email@, sending the patches with your favorite mail client should be fine, too.
31 3 Paul Kocialkowski
32 81 Denis 'GNUtoo' Carikli
h2. Pushing patches
If you already have the ability to push patches into the main Replicant repositories, you still need to send your patches to the mailing list if they are to be applied on a Replicant version that is currently supported, or if they apply to the Replicant website.
You will then need to wait either for:
* One other developer to review the patch and add "per's": Acknowledgement.
* One week if no other developer did review your patches.
40 71 Wolfgang Wiedmeyer
h2. Writing free software replacements
41 1 Paul Kocialkowski
42 71 Wolfgang Wiedmeyer
Here are some tips that may help you achieving a free software replacement for a specific component (some may be more or less relevant regarding the nature of what the component does):
* Look for interested people from other projects: LineageOS people are constantly fighting with non-free blobs and are sometimes happy to help replacing one.
44 1 Paul Kocialkowski
* Try to make the non-free binary as verbose as possible by enabling all the possible debug options on the config file or such.
45 85 Denis 'GNUtoo' Carikli
* You can use @string@ to try to find out the command line debug options, list of commands, etc.
46 71 Wolfgang Wiedmeyer
* Run the program in @strace@ and analyze the trace to understand what the program does.
* Add verbose debug prints in the concerned kernel driver (with @printk@ and show them via the @dmesg@ tool).
* Read the corresponding kernel driver: you can sometimes learn a lot by reading comments or headers.
* Collect data out of the kernel driver (via debug prints) and out of the non-free binary (via debug prints on the upper-layer).
* If there is a mathematical algorithm involved, force the values returned by the kernel to the non-free binary and analyze how it reacts, for instance with spreadsheet software.
51 1 Paul Kocialkowski
* If you're directly dealing with a hardware component, try to find a datasheet for the chip, it may hold precious details. In the best case, you may also be able to find a reference software implementation!
52 84 Denis 'GNUtoo' Carikli
* Make sure that the methods you use are legal where you live, and that the Replicant project is able to legally redistribute your work. In doubt, you could ask the Replicant developers in the mailing list and/or at the private contact address. The Replicant project has also access to legal advise through the FSF.
53 2 Paul Kocialkowski
h2. Upstreaming work
56 1 Paul Kocialkowski
It is generally a good idea to send some changes back to upstream, assuming that they will benefit from it as well.
57 2 Paul Kocialkowski
58 1 Paul Kocialkowski
When it is about the replacement of a non-free component present in the upstream systems, make sure that your replacement is reliable and complete.
Contact the interested developers on the upstream projects before attempting to send your replacement.
h3. LineageOS
63 86 Denis 'GNUtoo' Carikli
The LineageOS project has a "checklist": of requirements for adding support for a device.
As the LineageOS developers have to make sure that the checklist requirements are met, make sure that your replacement is complete enough to either meet the checklist requirements, or that the LineageOS developers are interested in working together with you to make sure that the free software replacement meets such requirements.
67 1 Paul Kocialkowski
The LineageOS team uses Gerrit to manage patch submissions. The process to get your patch included in LineageOS repos is explained on their wiki: "Gerrit":
68 2 Paul Kocialkowski
You can also push directly using git using the following scheme (untested):
git push ssh://<sshusername><projectname> HEAD:refs/for/<branchname>
73 25 Paul Kocialkowski
h3. AOSP
The Android Open Source Project uses Gerrit to manage patch submissions. Some information about submitting patches to AOSP is available:
You can push to AOSP's review using:
79 3 Paul Kocialkowski
git push HEAD:refs/for/master
82 43 Wolfgang Wiedmeyer
83 71 Wolfgang Wiedmeyer
h2. Commonly-used terminology
84 3 Paul Kocialkowski
85 71 Wolfgang Wiedmeyer
In order to keep everything clear and consistent, we use the following terms with a precise meaning in mind:
* *Driver*: Software that is part of the *kernel* (builtin or as a module) and deals with communicating with the hardware
* *Hardware Abstraction Layer (HAL)*: Software that runs in *user-space* and deals with communicating with the hardware (usually through a kernel driver)
* *module*: Android HALs are also often called modules, so we may referrer to e.g. the @audio HAL@ as the @audio module@
* *blob*: Proprietary HAL
* *firmware*: Software that does not run on the main processor (the CPU) but rather in a separate chip (e.g. the Wi-Fi firmwares runs on the Wi-Fi chip)
91 1 Paul Kocialkowski
h2. Wiki guidelines
In order the keep the wiki simple and consistent, a few guidelines must be followed when editing.
Regarding the content:
* Only Replicant-specific topics should be covered by the wiki: there is no point in writing usage guides for generic Android aspects, such as the user interface.
* The content on each page should *only* be relevant to the latest Replicant version: make sure to update the content with newer Replicant versions.
* Substantial changes must be discussed before modifying the wiki.
* A comment should be added in the comment field at the bottom that shortly describes the change.
101 72 Wolfgang Wiedmeyer
* Make use of the wiki formatting possibilities: "quick reference":/help/en/wiki_syntax_textile.html and "detailed syntax overview":/help/en/wiki_syntax_detailed_textile.html
102 1 Paul Kocialkowski
  By using @[[Index]]@, it's possible to link to the start page of the wiki.
103 6 Paul Kocialkowski
104 3 Paul Kocialkowski
Regarding the writing style:
* Every page in the wiki has to be written in correct English, we do not aim to provide information in any other language.
106 17 Paul Kocialkowski
* Addressing readers directly should be avoided when possible: Instead, what is described should always be the subject of sentences.
107 4 Paul Kocialkowski
* Links to pages should be incorporated in text (Instructions to [[ToolsInstallation#ADB|install ADB]] shouldn't be: Instructions to install ADB: [[ToolsInstallation#ADB]]).
108 14 Paul Kocialkowski
Regarding the naming of pages:
110 34 Paul Kocialkowski
* Pages must be named in a consistent manner ([[NexusSI902xFirmwares]] is not to be called [[FirmwaresOnTheI902xNexusS]]).
111 1 Paul Kocialkowski
* Common prefixes and suffixes should be used for naming new pages ([[BuildDependenciesInstallation]] is not to be called [[InstallationOfBuildDependencies]]).
112 34 Paul Kocialkowski
* Page and section names should always be named using nouns, not verbs, either active or not ([[DeveloperGuide]] is not to be called [[DevelopingGuide]]).
* Page titles shouldn't contain space or any delimiter character (such as - or_) but use upper-case characters as word delimiters ([[BuildDependenciesInstallation]] is not to be called [[Build_dependencies_installation]]).
* Page titles *as shown on the page* should use lower-case when upper-case is not needed, even if the page name uses upper-case as word delimiters.
116 49 Wolfgang Wiedmeyer
Regarding the naming of devices:
117 53 Wolfgang Wiedmeyer
* Devices should be named after their model number and codename, without mention of the manufacturer.
118 49 Wolfgang Wiedmeyer
* Common device naming conventions should be followed consistently (the @Galaxy S 3 (I9300)@ is not to be called @Samsung S3 GT-I9300@ or @Galaxy S III@).
119 34 Paul Kocialkowski
120 71 Wolfgang Wiedmeyer
h2. Repositories
121 34 Paul Kocialkowski
122 71 Wolfgang Wiedmeyer
When working with Replicant repos, make sure to avoid breaking things. For instance, if you push a commit introducing a compilation error, it will break the whole build process.
It is better to create separate branches (that are not used by the official manifest branches) when your work is still in progress.
Creating branches that add debug infos on a particular topic is usually a good idea since it will save you time next time you want to debug the same component.
126 80 Denis 'GNUtoo' Carikli
See [[SourceCodeRepositories]] for more details about how to create or mirror repositories on Replicant server.
127 71 Wolfgang Wiedmeyer
h3. When creating a repository
129 78 Denis 'GNUtoo' Carikli
130 71 Wolfgang Wiedmeyer
In order to keep repo naming consistent, please name repositories by their name on the tree, replacing the @/@ by @_@.
For instance, when forking the LineageOS repo: @android_device_samsung_crespo@, rename it to @device_samsung_crespo@ on the Replicant repos.
This creates a more consistent way of naming repositories and makes it easier when pushing: just look at the location in the source tree and replace @/@ by @_@.
h3. When creating a branch
Official Replicant branches are named the following way:
* The @replicant-@ prefix
* The Replicant version
Such as: @replicant-2.3@ This should be used on the projects repositories as well as the manifest repository.
Any other branch should be considered as Work In Progress (WIP) and thus not be part of any official branch of the manifest.
There is although one exception, with the @master@ branch, that can be used by any project and be in any manifest given that the code held in the @master@ branch will work on any Replicant version.
144 16 Paul Kocialkowski
145 33 Paul Kocialkowski
h2. New images release
146 1 Paul Kocialkowski
147 33 Paul Kocialkowski
# Modify the changelog in the vendor files:
149 54 Wolfgang Wiedmeyer
cd path/to/replicant-6.0/vendor/replicant
150 33 Paul Kocialkowski
edit CHANGELOG.mkdn
git add CHANGELOG.mkdn
152 54 Wolfgang Wiedmeyer
git commit -sS -m "Replicant 6.0 0001 images release"
git push replicant-6.0
154 33 Paul Kocialkowski
155 65 Wolfgang Wiedmeyer
# Increment the release in the "release scripts":
156 33 Paul Kocialkowski
cd path/to/release-scripts
158 58 Wolfgang Wiedmeyer
git add
160 1 Paul Kocialkowski
git commit -sS -m "Replicant 6.0 0001 images release"
git push replicant-6.0
162 58 Wolfgang Wiedmeyer
163 63 Wolfgang Wiedmeyer
# Tag all the repositories with the release tag script:
path/to/release-scripts/ path/to/replicant-6.0
167 58 Wolfgang Wiedmeyer
# In the manifest repo, merge the replicant-6.0-dev branch into the replicant-6.0 branch and increment the release in the manifest:
cd path/to/manifest
git checkout replicant-6.0
git merge replicant-6.0-dev
edit default.xml
git add default.xml
git commit -sS -m "Replicant 6.0 0001 images release"
git push replicant-6.0
176 33 Paul Kocialkowski
# Tag the manifest:
178 61 Wolfgang Wiedmeyer
git tag -u 5816A24C10757FC4 replicant-6.0-0001 -m "Replicant 6.0 0001 images release"
git push replicant-6.0-0001
182 64 Wolfgang Wiedmeyer
# Verify all tags:
cd .repo/manifests
git verify-tag $(git describe)
cd ../..
187 68 Wolfgang Wiedmeyer
repo forall -ec ' { echo "Verifying $REPO_PROJECT" && git verify-tag $(git describe) 2>/dev/null; } || { echo "Error: verification failed!" && exit 1; } '
188 64 Wolfgang Wiedmeyer
189 56 Wolfgang Wiedmeyer
# Update prebuilts and start the build (in a newly opened shell with the Replicant keys and certificates installed):
path/to/release-scripts/ path/to/replicant-6.0
193 33 Paul Kocialkowski
# Release the images with the release script:
195 55 Wolfgang Wiedmeyer
rm -rf path/to/images/replicant-6.0/0001
196 54 Wolfgang Wiedmeyer
mkdir -p path/to/images/replicant-6.0/0001
path/to/release-scripts/ path/to/replicant-6.0 path/to/images/replicant-6.0/0001
198 1 Paul Kocialkowski
199 33 Paul Kocialkowski
# Sign the binaries with the release script:
201 54 Wolfgang Wiedmeyer
path/to/release-scripts/ path/to/replicant-6.0 path/to/images/replicant-6.0/0001 signatures
202 1 Paul Kocialkowski
203 33 Paul Kocialkowski
# Compress the release files
205 54 Wolfgang Wiedmeyer
cd path/to/images/replicant-6.0
tar -cjf 0001.tar.bz2 0001
207 1 Paul Kocialkowski
208 33 Paul Kocialkowski
# Upload the release to OSUOSL:
210 66 Wolfgang Wiedmeyer
rsync -P -4 -ze ssh 0001.tar.bz2
211 54 Wolfgang Wiedmeyer
212 67 Wolfgang Wiedmeyer
# Unpack the release on OSUOSL, ensure permissions are correct and run the @trigger-replicant@ script
213 33 Paul Kocialkowski
# Update [[ReplicantImages]] with the release
# Update each device's page with the release
# Update [[ReplicantStatus]] with the latest status
216 62 Wolfgang Wiedmeyer
# Verify if other wiki pages need to be updated due to changes introduced by the release (e.g. [[Index#Replicant-build|build pages]] or [[ToolsInstallation]])
217 33 Paul Kocialkowski
# Announce the release on the blog
# Update the release on the website and IRC topic
219 5 Paul Kocialkowski
220 33 Paul Kocialkowski
h2. New device documentation
221 22 Paul Kocialkowski
222 19 Paul Kocialkowski
1. Create the device main page, following the naming guidelines applied to other devices (e.g. the Samsung Galaxy S II GT-I9100 is called *Galaxy S 2 (I9100)* and its page is [[GalaxyS2I9100]])
223 74 Wolfgang Wiedmeyer
2. Create all the related sub-pages (build guide, install guide and firmwares list at least), following the naming guidelines applied to other devices (e.g. [[GalaxyS2I9100Build]], [[GalaxyS2I9100Installation]] and [[GalaxyS2I9100LoadedFirmwares]])
224 5 Paul Kocialkowski
3. Link the sub-pages to the main page in the index
4. Update the [[ReplicantStatus]] page of the wiki with the current status of the device
226 47 Wolfgang Wiedmeyer
5. Modify the [[Index]] page of the wiki and add the new device in the following sections:
* [[Index#Replicant-status|Replicant status]]
* [[Index#Replicant-installation|Replicant installation]]
* [[Index#Replicant-build|Replicant build]]
* [[Index#Supported-devices|Supported devices]]
231 24 Paul Kocialkowski
232 43 Wolfgang Wiedmeyer
6. Add new issues categories to the Replicant project Redmine
233 73 Wolfgang Wiedmeyer
7. Add the device to the "Supported devices page": on the website