Deployed 767a2d7 with MkDocs version: 1.6.1

Author: FPSensor

en/build/index.html

@@ -460,48 +460,50 @@
 
 
 <h1 id="the-android-build-guide">The android build guide</h1>
-<p>on this guide i will explain u how to find device trees, prepare the env, requeriments, and more</p>
+<p>on this guide i will explain u how to find device trees, prepare the env, requeriments, and more    </p>
 <h2 id="reqs">Reqs</h2>
 <ul>
-<li>64bit decent cpu</li>
-<li>32GB of RAM</li>
-<li>500GB+ space (SSD recommended)</li>
-<li>a good internet (or much patience)</li>
-<li>a brain</li>
-<li>a bit of knowledge of linux terminal</li>
+<li>64bit decent cpu    </li>
+<li>32GB of RAM    </li>
+<li>500GB+ space (SSD recommended)    </li>
+<li>a good internet (or much patienceand a very stable internet)    </li>
+<li>common sense    </li>
+<li>a bit of knowledge of linux terminal    </li>
 </ul>
+<p>can u use lowest specifications? ye, these ae the most recommended but u can try others. u can by example to use a lot of swap or waiting 3 days to the rom to be compiled but with these specifications u can be sure that u wont have problems  <br />
+anothehr recomendation is that if u are going to make a PC to buildalways search AMD, the compilation is a work that uses the whole CPU at the same time and on long periods and for that a good AMD multicore is the best    </p>
 <h2 id="recomendations">recomendations</h2>
 <ul>
-<li>do just Lineage <ul>
-<li>for the first try i recommend u that u try a simple rom, dont try aospa, aosp, etc. do a rom that all of us know that works well</li>
+<li>do just Lineage     <ul>
+<li>for the first try i recommend u that u try a simple rom, dont try aospa, aosp, etc. do a rom that all of us know that works well    </li>
 </ul>
 </li>
-<li>learn git (a guide is coming soon)<ul>
-<li>its not necesary to make the rom but u will need it wen u want to do changes and u dont want to push commits without author and "update x.x" if u dont want the community hates u</li>
+<li><a href="../git/">learn git</a>    <ul>
+<li>its not necesary to make the rom but u will need it wen u want to do changes and u dont want to push commits without author and "update x.x" if u dont want the community hates u    </li>
 </ul>
 </li>
-<li>dont ask for mainteinership<ul>
-<li>u did your rom? congrats, but u still have to learn a lot to be a maintainer of a rom, maintainer is a person that can update the rom constantly and can fix reported bugs reading logs and making changes in trees</li>
+<li>dont ask for mainteinership    <ul>
+<li>u did your rom? congrats, but u still have to learn a lot to be a maintainer of a rom, a maintainer is a person that can update the rom constantly and can fix reported bugs reading logs and making changes in trees. u dont want that the creators of the rom to put u in a blacklist    </li>
 </ul>
 </li>
 </ul>
 <h2 id="getting-server">getting server</h2>
-<p>if u dont have the specs mentioned before u will need a server
-for that we have some options </p>
+<p>if u dont have the specs mentioned before u will need a server  <br />
+for that we have some options     </p>
 <ul>
-<li>buy a server<ul>
-<li>since no one of server sellers  promote me i wont send u anyone but its really easy to find a server seller in tellegram, they usually manages on paypal</li>
+<li>buy a server    <ul>
+<li>since no one of server sellers  promote me i wont send u anyone but its really easy to find a server seller in telegram, they usually manages on paypal    </li>
 </ul>
 </li>
-<li><a href="https://cloud.google.com">Google Cloud Platform Free triel</a><ul>
-<li>make a new google account since wen u have 0 credits u have to delete it</li>
-<li>u need a credit card (dw, no costs at all)</li>
+<li><a href="https://cloud.google.com">Google Cloud Platform Free triel</a>    <ul>
+<li>make a new google account since wen u have 0 credits u have to delete it    </li>
+<li>u need a credit card (dw, no costs at all)    </li>
 </ul>
 </li>
 </ul>
 <h2 id="getting-device-trees">getting device trees</h2>
-<p>doesnt makes sense that we sync a rom if there is not device trees for my device so the next step is to look for a device tree
-how we plan to do that?</p>
+<p>doesnt makes sense that we sync a rom if there is not device trees for my device so the next step is to look for a device tree  <br />
+how we plan to do that?    </p>
 <p>first try, XDA   <br />
 i have a Xiaomi Redmi Note 7 [lavender]  <br />
 now we will ook for the xda  <br />
@@ -513,23 +515,23 @@ <h2 id="getting-device-trees">getting device trees</h2>
 <p>xda has no luck?  <br />
 lets try another  <br />
 go to github.com   <br />
-go to search button and search kernel_brand_device(or _soc ex sm8250)     </p>
-<p>if u found your device trees then lets come with the next step  <br />
-if u have no luck then probably can <a href="https://t.me/FPSensor">contact me</a> to see if we have luck, else the guide ends here for u    </p>
-<p>wen we have his kernel we will go to his github profile and look for these:</p>
+go to search button and search kernel_brand_device(or _soc ex ssm660)     </p>
+<p>if u found your kernel tree then lets come with the next step  <br />
+if u have no luck then can <a href="https://t.me/FPSensor">contact me</a> to see if we have luck, else the guide ends here for u    </p>
+<p>wen we have his kernel we will go to his github profile and look for these:    </p>
 <ul>
-<li>device_brand_name</li>
-<li>vendor_brand_name</li>
-<li>kernel_brand_name (it can be kernel_brand_soc ex: sm8250)</li>
-<li>device_brand_soc-common (if exist)</li>
-<li>vendor_brand_soc-common (if exist)<ul>
-<li>for vendor repos if u found device and kernel from lineage org then there will be on TheMuppets org probably</li>
+<li>device_brand_name    </li>
+<li>vendor_brand_name    </li>
+<li>kernel_brand_name (it can be kernel_brand_soc ex: sdm660) (that we already have)    </li>
+<li>device_brand_soc-common (if exist)    </li>
+<li>vendor_brand_soc-common (if exist)    <ul>
+<li>for vendor repos if u found device and kernel from lineage org then there will be on TheMuppets org probably    </li>
 </ul>
 </li>
-<li>hardware_brand (if exist, else we will take it from LineageOS organization)</li>
+<li>hardware_brand (if exist, else we will take it from LineageOS organization)    </li>
 </ul>
-<p>in some cases it will have android_, its the same, dont worry</p>
-<p>if we can find a local_manifests repo very good cuz we can use it, save it cuz will be important</p>
+<p>in some cases it will have android_ or proprietary_, its the same, dont worry    </p>
+<p>if we can find a local_manifests repo very good cuz we can use it, save it cuz will be important    </p>
 <h2 id="preparing-the-env">preparing the env</h2>
 <p>i recommend u to use Ubuntu (i use 20.04 but others should work too)</p>
 <pre><code>sudo apt install bc bison build-essential ccache curl flex g++-multilib gcc-multilib git git-lfs gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev liblz4-tool libncurses5 libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-gtk3-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc zip zlib1g-dev python
@@ -547,19 +549,19 @@ <h2 id="sync-the-rom">sync the rom</h2>
 <pre><code>mkdir LineageOS
 cd LineageOS
 </code></pre>
-<p>we will start the rom sync</p>
-<p>BUT WAIT WAIT WAIT
-you got a local_manifests repo?
-do this</p>
+<p>we will start the rom sync    </p>
+<p>BUT WAIT WAIT WAIT  <br />
+you got a local_manifests repo?  <br />
+do this    </p>
 <pre><code>git clone LINK .repo/local_manifests
 </code></pre>
-<p>now lets sync the rom
-be ready for a long time of downloading, have a good internet in that moment</p>
+<p>now lets sync the rom  <br />
+be ready for a long time of downloading, have a good internet in that moment    </p>
 <pre><code>repo init -u https://github.com/LineageOS/android.git -b lineage-XX (replace XX with lineage version, should be same as tree adroid version)
 repo sync -c --no-clone-bundle -j12 --force-sync
 </code></pre>
 <p>u should get a message like "Repo sync succesfully"    </p>
-<p>ok so if we had local_manifest all things we need are cloned   <br />
+<p>ok so if we had local_manifests all things we need are cloned   <br />
 else we will take a look on the repos we got  <br />
 i will do a command for example and then u guys will reply    </p>
 <p>git clone https://github.com/android_device_motorola_rhode device/motorola/rhode -b [the branch should be the same as lineage or android version]  <br />
@@ -569,9 +571,11 @@ <h2 id="sync-the-rom">sync the rom</h2>
 in the clkone path we do this  <br />
 device/xiaomi/lavender  <br />
 so we ignore the android_ or the proprietary_ and we replace these _ with /  <br />
-done, we have all clonned    </p>
+done, we have all clonned  <br />
+we will do this with all the repos we found in the search of dts    </p>
 <h2 id="prepare-device-trees-for-the-rom">prepare device trees for the rom</h2>
 <p>we will move to device/brand/devicename  <br />
+if we see that xx_devicename.mk is linege_devicename.mk we will skip these next steps
 now we will look for AndroidProducts.mk  <br />
 we will replace all xx_devicename with lineage_devicename   <br />
 save and now we will search for xx_devicename.mk and rename as lineage_devicename.mk  <br />
@@ -581,7 +585,7 @@ <h2 id="prepare-device-trees-for-the-rom">prepare device trees for the rom</h2>
 on it we will look if there is any vendor/xx definition and will replace with vendor/lineage  <br />
 done, we will move back to main folder    </p>
 <h2 id="time-to-build">time to build</h2>
-<p>we will do this</p>
+<p>we will do this on the main build directory</p>
 <pre><code>. build/envsetup.sh
 lunch lineage_devicename-userdebug
 m bacon
@@ -590,7 +594,7 @@ <h2 id="time-to-build">time to build</h2>
 now test and good luck    </p>
 <h2 id="ask-me-a-question">Ask me a question</h2>
 <p>want me to modify the guide? need help with the guide? contact me in my <a href="https://t.me/FPSensorSupport">support group</a>    </p>
-<p>this guide was done with my hands, with my knowledge and never searched in another site for a reference wen writing (besides these env commands that i took from crDroid) so it may can have issues, make suggestions in my group</p>
+<p>this guide was done with my hands, with my knowledge and never searched in another site for a reference wen writing (besides these env commands that i took from crDroid) so it may can have redaction issues, make suggestions in my group</p>
 <p>thank you</p>
 
 

en/git/index.html

@@ -370,9 +370,9 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#who-are" class="md-nav__link">
+  <a href="#who-are-you" class="md-nav__link">
     <span class="md-ellipsis">
-      who are ?
+      who are you?
     </span>
   </a>
 
@@ -465,13 +465,13 @@ <h1 id="gitgithubgitlab-guide">Git/Github/Gitlab guide</h1>
 u should have a git account of a git site ofc.  <br />
 u should had installed git already    </p>
 <h2 id="initialize-my-first-repo">initialize my first repo</h2>
-<p>new repo</p>
+<p>new repo    </p>
 <pre><code>mkdir repo
 cd repo
 git init
 </code></pre>
-<h2 id="who-are">who are ?</h2>
-<p>with the information u provided to create a account u have to fil this</p>
+<h2 id="who-are-you">who are you?</h2>
+<p>with the information u provided to create a account u have to fil this    </p>
 <pre><code>git config --global user.name
 git config --global user.email
 </code></pre>
@@ -484,7 +484,7 @@ <h2 id="doing-our-first-change">Doing our first change</h2>
 </code></pre>
 <h2 id="pushing-to-our-repo">pushing to our repo</h2>
 <p>in our github we should make a repository with the name we want to add to it  <br />
-i want to clarify that i use github cuz its the more ommon but its the same for all    </p>
+i want to clarify that i use github cuz its the more common but its the same for all    </p>
 <pre><code>git remote add origin https://github.com/FPSensor/hi
 git push -f -u origin HEAD:master
 </code></pre>
@@ -493,46 +493,45 @@ <h2 id="first-chaper-is-done-some-things-to-clarify">first chaper is done, some
 2: no need to put -m on the git commit command, if u dont add -m it will open the editor, this is better for long commit messages.  <br />
 3: that larger push command is only for new branches, should be another way but if u clone the repo again a "git push" is enough    </p>
 <h2 id="clone-a-repo">clone a repo</h2>
-<p>as simple as "git clone link -b branch"</p>
+<p>as simple as "git clone link -b branch Descargas/hola"    </p>
 <h2 id="who-did-this">who did this?</h2>
 <p>i took a commit from another guy, how to recognize his work?  <br />
-in android comunity we dont want people that doesnt add authors to commits and u will be like trash for they (i say by previous experiences) so, 
-we should add who did that.
-this will be applied for the previous commit, i will tell us how to do for others</p>
+in android comunity we dont want people that doesnt add authors to commits and u will be like trash for they (i say by previous experiences) so,   <br />
+we should add who did that.  <br />
+this will be applied for the previous commit, i will tell us how to do for others more later.    </p>
 <pre><code>git commit --amend --author=&quot;FPSensor &lt;gkartyt@gmail.com&gt;&quot;
 </code></pre>
-<p>but, how we got that info
-i took a commit from a repo where i was looking, how we can get that?
-in the commit link add .patch 
-this will literally make the commit a patch file, something that we will talk later about, but the point is:
-we can use it to get the author, check it.</p>
+<p>but, how we got that info  <br />
+i took a commit from a repo where i was looking, how we can get that?  <br />
+in the commit link add .patch   <br />
+this will literally make the commit a patch file, something that we will talk later about, but the point is:  <br />
+we can use it to get the author, check it.    </p>
 <h2 id="i-want-a-cherry">i want a cherry</h2>
-<p>a cherry pick is literally wn you pick commits from another repo
-to do it is really simple
-we have to initialize the repository and its changes with their commit hashes:</p>
-<pre><code>}git remote add cherrypick https://github.com/FPSensor/FPSensor
+<p>a cherry pick is literally wen you pick commits from another repo  <br />
+to do it is really simple  <br />
+we have to initialize the repository where the commit is and its changes with their commit hashes:    </p>
+<pre><code>git remote add cherrypick https://github.com/FPSensor/FPSensor
 git fetch cherrypick
 git cherry-pick hfwdhuwhfuiwuihfvuiwfhefhruifhfuihiuwe
 </code></pre>
-<p>u can just copy the hash from the commit 
-i have to pick 300 commits, how?
-things to have in account?
-its a start commit and a end commit, everything after the first commit and before the final commit will be picked, no metter what it is</p>
+<p>u can just copy the hash from the commit   <br />
+i have to pick 300 commits, how?  <br />
+things to have in account?  <br />
+its a start commit and a end commit, everything after the first commit and before the final commit will be picked, no metter what it is    </p>
 <pre><code>git cherry-pick commit-start~..commit-end
 </code></pre>
-<p>oh, no
-we got a conflict of context at hi file</p>
-<p>how we look into it?
-a git conflict its where git dont know what to do cuz your source and the source of the repo before that commit are different
-its really simple</p>
+<p>oh, no  <br />
+we got a conflict of context at hi file    </p>
+<p>how we look into it?  <br />
+a git conflict its where git dont know what to do cuz your source and the source of the repo before that commit are different  <br />
+its really simple    </p>
 <pre><code>&lt;&lt;&lt;&lt;&lt;&lt;&lt; HEAD
 ======= that source with the commit applied (should appear as a hash of commit)
 &gt;&gt;&gt;&gt;&gt;&gt;&gt; end of the confflict
 </code></pre>
-<p>we dont want to apply a commit cuz tons of confflicts and urlazy?</p>
+<p>we dont want to apply a commit cuz tons of confflicts and u are lazy?    </p>
 <pre><code>git cherry-pick --ship
 </code></pre>
-<p>this also applies for commits that was already dont and are uplicated</p>
 <h2 id="to-be-continued">to be continued</h2>