[KERNEL][08/11][3.10.102][UBER-5.4] Unofficial AK - 067 - Nexus 6P Android Development

Introduction
Hello everyone, this is my unofficial version of @ak's kernel. As he has been busy with life lately, I wanted to keep up with the Android security patches since this kernel runs amazingly on my phone; so I did just that. Because these are unofficial, you are NOT to discuss the use of them in ak's thread. Do that here. Read ALL of this post, I go over almost everything you could need to know. This kernel will only receive security updates and upstream Linux patches; I will not be changing anything else.
For those of you who have come here before, I have moved the more feature packed kernel to here: http://forum.xda-developers.com/nexus-6p/development/kernel-ninja-kernel-v1-0-t3437247
Differences from official
AK versions 064-066 (unreleased officially by ak)
Linux versions 3.10.74-3.10.83 and 3.10.102
August security patch
Patches for some CVEs
Compiled with latest Uber 5.4 toolchain
Downloads
Main folder
Installation
If on a previous version of my build OR the kernel that comes with your ROM: Flash the zip in TWRP and reboot.
If on another custom kernel: Dirty flash your ROM OR the boot.img if on stock, flash the zip in TWRP, and reboot.
Changelog
Code:
[b]067[/b]
[LIST]
[*]Initial release
[/LIST]
Frequently asked questions
1.1 Q: I am having an issue, can you help me?
1.1 A: Keep in mind I am by no means a kernel developer. However, start by reading the release posts, as I may make note of a particular issue. Also search the thread to see if I have discussed it before. If you see nothing and then provide me with a dmesg/last_kmsg and logcat plus your ROM/kernel version, I'll do my best to assist you.
Code:
adb logcat -d > logcat.txt
adb shell dmesg > dmesg.txt
1.3 Q: Can you add xyz feature?
1.3 A: Sorry, no. I will only be adding security patches. If you want a fully updated and feature packed kernel, check out my Ninja Kernel: http://forum.xda-developers.com/nexus-6p/development/kernel-ninja-kernel-v1-0-t3437247
1.4 Q: How do I control the kernel?
1.4 A: AK recommends using Synapse; if you do not care for Synapse, I would flash this UKM uninstaller in TWRP to keep your /data partition clean. Personally, I recommend using either @flar2's EX Kernel Manager or @Yoinx's Kernel Adiutor-Mod; both are extremely solid and have given me no issues.
1.5 Q: What are your settings?
1.5 A: Here are my regular/tried and true settings for what I consider great performance and battery life:
CPU:
CPU governor: Interactive
CPU governor (Cluster 2): Interactive
Stock governor profile
Max CPU frequency: 1708 MHz
Min CPU frequency: 302 MHz
Max CPU frequency (Cluster 2): 2054 MHz
Min CPU frequency (Cluster 2): 302 MHz
Input boost frequency: 0:768000 1:0 2:0 3:0 4:0 5:0 6:0 7:0
Input boot milliseconds: 60
msm_thermal: Enabled
core_control: Disabled
Graphics:
No modifications
Gestures:
Sweep2Wake: Up, Down
Camera launch gesture: Enabled
Sound:
No modifications
Memory:
No modifications (I leave zRAM enabled)
Miscellaneous:
No modifications (sioplus and 1536 are the defaults, which I use)
Thanks to:
@ak for the fantastic kernel
The various developers for their patches (@flar2, @franciscofranco, and @imoseyon to name a few)
@DespairFactor for helping me with some kernel compilation issues and the Uber prebuilt toolchains I use
All of you guys for viewing the thread
DISCLAIMER: I openly welcome off topic in my threads. Mods, please do not clean off topic discussion and users, do not complain about off topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.
XDA:DevDB Information
Unofficial AK Kernel, Kernel for the Huawei Nexus 6P
Contributors
nathanchance, ak
Source Code: https://github.com/nathanchance/AK-Angler
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v067
Stable Release Date: 2016-08-11
Created 2016-06-19
Last Updated 2016-08-11

How to compile the kernel for yourself
1. Configure your environment
In order to compile this kernel, I'd recommend using Linux (OS X should be acceptable but this guide will be tailored for Linux). To get the environment configured, either use Google's own guide here or my guide (only section 1) here.
2. Grab the source
Grab my AK source
Code:
mkdir ~/Android
cd ~/Android
git clone https://github.com/nathanchance/AK-Angler.git AK
Explanation:
First command makes a directory named Android in your home folder (mkdir = make directory). You can change the location if you want but keep it consistent throughout the guide.
Second command moves into that directory (change directory)
Third command pulls the source from my Github into a directory named AK (git clone <url> <folder_to_clone_in_to> is the format of the command).
Grab my AnyKernel source
Code:
cd ~/Android
git clone https://github.com/nathanchance/AK-Angler-AnyKernel2 AK-AK2
Explanation:
First command moves into the Android directory we made above (change directory)
Third command pulls the source from my Github into a directory named AK-AK2 (git clone <url> <folder_to_clone_in_to> is the format of the command).
Grab the toolchain you want to use to compile the kernel
Code:
cd ~/Android
git clone <kernel_url>
Explanation:
In order to compile the kernel, we need to grab a toolchain (bunch of compilation tools). I currently compile 11 options, you'll only be doing one. Below are the list of possible URLs to clone; copy and paste it after the words git clone above:
AOSP: https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
Uber 4.9: https://bitbucket.org/DespairFactor/aarch64-linux-android-4.9-kernel.git
Uber 5.4: https://bitbucket.org/DespairFactor/aarch64-linux-android-5.x-kernel.git
Uber 6.1: https://bitbucket.org/DespairFactor/aarch64-linux-android-6.x-kernel.git
Uber 7.0: https://bitbucket.org/DespairFactor/aarch64-linux-android-7.0-kernel.git
Linaro 4.9: https://android-git.linaro.org/git/.../aarch64/aarch64-linux-android-4.9-linaro.git
Linaro 5.4: https://android-git.linaro.org/git/.../aarch64/aarch64-linux-android-5.4-linaro.git
Linaro 6.1: https://android-git.linaro.org/git/.../aarch64/aarch64-linux-android-6.1-linaro.git
DF-Linaro 4.9: https://bitbucket.org/DespairFactor/aarch64-linux-android-4.9-kernel-linaro.git
DF-Linaro 5.4: https://bitbucket.org/DespairFactor/aarch64-linux-android-5.x-kernel-linaro.git
DF-Linaro 6.1: https://bitbucket.org/DespairFactor/aarch64-linux-android-6.x-kernel-linaro.git
3. Setup the build
Make sure everything looks right
After following the above steps, type:
Code:
ls
You should see something like this:
Code:
aarch64-linux-android-6.x-kernel-linaro AK AK-AK2
The toolchain directory make be different depending on what you cloned above. If it looks different, delete the Android folder and do step 2 again.
Select the correct kernel branch
Code:
cd ~/Android/AK
git checkout <branch>
Example:
Code:
cd ~/Android/AK
git checkout m-eas
Explanation
First command will move you into the AK source directory we cloned above.
Second command will checkout the branch you want to compile for. A git repo can have multiple branches. For mine, these are the possible options:
m-standard (for the M Normal branch)
m-eas (for the M EAS branch)
m-nethunter (for the M NetHunter branch)
n-testing (for the N Normal branch)
Select the correct AnyKernel branch
Code:
cd ~/Android/AK-AK2
git checkout ak-angler-anykernel
Explanation
First command will move you into the AK AnyKernel directory we cloned above. This is what allows you to flash the kernel (thank you very much @osm0sis for all the work you do).
Second command will checkout the correct branch (in this case, ak-angler-anykernel)
4. Make the kernel
Tell the makefile what toolchain and architecture you are building for
Figure out the full path of your toolchain folder
Assuming you have done this whole process correctly, you can move into your toolchain directory and type:
Code:
cd ~/Android/<toolchain_folder>
pwd
Example:
Code:
cd ~/Android/aarch64-linux-android-6.x-kernel-linaro
pwd
You should get something like this:
Code:
/home/nathanchance/Android/aarch64-linux-android-6.x-kernel-linaro
Tell the compiler where that toolchain is
Copy and paste that file location above into this command:
Code:
export CROSS_COMPILE=<toolchain_dir>/bin/aarch64-linux-android-
Example:
Code:
export CROSS_COMPILE=/home/nathanchance/Android/aarch64-linux-android-6.x-kernel-linaro/bin/aarch64-linux-android-
Set the architecture
Angler is a 64-bit device so we need arm64
Code:
export ARCH=arm64
export SUBARCH=arm64
Clean up from a previous compilation and update the source
Code:
cd ~/Android/AK-AK2
git reset --hard origin/ak-angler-anykernel
git clean -f -d -x > /dev/null 2>&1
git pull > /dev/null 2>&1
cd ~/Android/AK
git reset --hard origin/<kernel_branch>
git clean -f -d -x > /dev/null 2>&1
make clean && make mrproper
Example:
Code:
cd ~/Android/AK-AK2
git reset --hard origin/ak-angler-anykernel
git clean -f -d -x > /dev/null 2>&1
git pull > /dev/null 2>&1
cd ~/Android/AK
git reset --hard origin/m-standard
git clean -f -d -x > /dev/null 2>&1
make clean && make mrproper
git pull
Explanation:
First set:
The first command moves you into the AK AnyKernel directory.
The second command will undo any local commits you have done and align your source with the most recent commit from me.
The third command will clean any untracked or compiled files (this is send to /dev/null so you do not see it happen).
The fourth command will pull any new AnyKernel changes from me into the source.
Second set:
The first command moves you into the AK source directory.
The second command will undo any local commits you have done and align your source with the most recent commit from me.
The third command will clean any untracked or compiled files (this is send to /dev/null so you do not see it happen).
The fourth and fifth command (strung together with &&) will remove you
The sixth command will pull any new kernel changes from me into the source.
Set up the defconfig
A defconfig tells the compiler which features you want in the kernel. This is already set up by me. To set up the defconfig, type the following:
Code:
cd ~/Android/AK
make ak_angler_defconfig
Name the kernel
If you notice in About Phone > Kernel Version, it shows 3.10.102-AK.066-9.UBER4.9 (or something similar). You can customize this like so:
Code:
export LOCALVERSION=-"kernel name"
Example:
Code:
export LOCALVERSION=-"AK-Nathan-Personal"
Make the kernel!
Code:
make -j#
Example:
Code:
make -j4
Explanation:
The # after the "j" is how many simultaneous threads are run. Traditionally, this is the number of cores you have plus one. So a quad-core CPU would be -j5.
5. Zip it up and flash!
Copy the zImage to the AnyKernel directory
Code:
cd ~/Android/AK/arch/arm64/boot
cp -v Image.gz ~/Android/AK-AK2/zImage
Explanation:
We need to copy the newly compiled kernel (which resides in the arch/arm64/boot folder) to the AnyKernel directory, while changing its name to zImage.
cp = copy
-v = verbose (prints the copying)
Image.gz = file to be copied
~/Android/AK-AK2/zImage = destination and name
Make a current dtb file
Code:
cd ~/Android/AK-AK2
tools/dtbToolCM -v2 -o dtb -s 2048 -p ~/Android/AK/scripts/dtc/ ~/Android/AK/arch/arm64/boot/dts/
Explanation:
No explanation, just do it :silly:
Zip it up!
Code:
cd ~/Android/AK-AK2
zip [email protected] -r9 ak-kernel.zip *
Using the above commands, your newly completed kernel will be located at ~/Android/AK-AK2/ak-kernel.zip
If you followed all of the above steps successfully, congratulations, you built the kernel!! Once you have done all five steps, you will just need to follow steps 4 and 5 to update in the future. Below, I have linked a script that will do all of this for you (with some variable edits at the top); however, please do it manually first so you know exactly what you are doing enjoy!
https://raw.githubusercontent.com/nathanchance/Android-Tools/master/ak.sh

nathanchance said:
Reserved
Click to expand...
Click to collapse
Definitely quicker than PN mm2 release ......lol
thanks a lot

Well look what's cooking! Kudo's

Thx 4 this Nate!

Any useable with DP4
Sent from my Nexus 6P using Tapatalk

kenbrownstone said:
Any useable with DP4
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, Marshmallow only.

@nathanchance
Can you share your EXKM settings?

Asselalf said:
@nathanchance
Can you share your EXKM settings?
Click to expand...
Click to collapse
Sure. They are added in the OP and will be updated if I ever change them.

OK, i'll try that. Thanks for sharing

Thank you the kernel.
I use Resurrection Remix ROM with ElementalX kernel. Can I install the AK.066-2.ANGLER.UBER6.1.zip after the ElementalX kernel? Or should I go back the apascual kernel and then install the AK.066-2.ANGLER.UBER6.1.zip?

raymondoliviero said:
Thank you the kernel.
I use Resurrection Remix ROM with ElementalX kernel. Can I install the AK.066-2.ANGLER.UBER6.1.zip after the ElementalX kernel? Or should I go back the apascual kernel and then install the AK.066-2.ANGLER.UBER6.1.zip?
Click to expand...
Click to collapse
Go back to the included kernel then flash this one.

nathanchance said:
Go back to the included kernel then flash this one.
Click to expand...
Click to collapse
Ok, thank you.

raymondoliviero said:
Ok, thank you.
Click to expand...
Click to collapse
I'll add installation instructions to the OP, thanks for the reminder.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's very fast, thank you very much. I use your settings.
Sent from my Nexus 6P using XDA-Developers mobile app

Sorry for the double, please delete this.

What ROM do you use Nathan. Just wondering.

Pandawg said:
What ROM do you use Nathan. Just wondering.
Click to expand...
Click to collapse
Pure Nexus, I am using the mm2 branch that I compiled myself. Should be available publicly here soon.

Awesome Work as always Nathan and Congrats for crossing the 10,000 mark on the Thanks meter

Hey thanks for this Nathan, you've done an excellent job. This is the smoothest kernel I've tried. Running RR it is very smooth.
Sent from my Nexus 6P using XDA-Developers mobile app

Related

[ROM] [4.2.2] Unofficial Root-Box w/ Inverted Gapps [2013-08-17] FOCAL

This is an unofficial port of Vanilla Root-Box.
I compiled this ROM from Root-Box and other sources and have
added my own modifications and other apps not normally included.​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would love any feedback, suggestions, help and even complaints.
I want to learn as much as I can about building my own ROMs and believe
the only way I can truly get better is through the XDA community.
I've only just started learning this stuff and have had a huge amount of
help from mikeshepard and jrior001 in learning and getting this ROM to build.
FEATURES
All features found in Vanilla Root-Box
Compiled with -O3 optimizations with GCC 4.8
Added Apollo
Added CM File Manager
Added Nova Launcher Basic (Will Update from Market)
Added Android Terminal Emulator (Will Update from Market)
RootBoxOTA
Includes patch for Android Master Key bug #8219321 and bug # 9695860
Custom default PA DPI settings for Calculator, Gmail, Email, Play Store and Settings.
Dark Root-Box Gapps - turning on Dark Root-Box will invert these gapps.​
Downloads:
You can find all my builds on Devhost.
DevHost - http://d-h.st/users/tjarnold/?fld_id=18388#files
Most Recent ROM - 08-08-2013 - RootBox-JB-jewel-Unofficial-20130808.zip*
Gapps - Black-Box_Gapps_Aroma_20130801-signed.zip - Custom Dark Rootbox Compatible Gapps
Focal - Focal.apk - Built from sources created by the CyanogenMod team. Install like any other apk.
Changelog For ROM:
08-08-2013 - RootBox-JB-jewel-Unofficial-20130817.zip*
- Updated all non-Root-Box sources.
- Changed to 3.4.11 CyanogenMod/msm8960 kernel. (The 3.4.49 kernel was presenting too many stability issues.)
- Added Intellidemand governor to kernel.
- Added underclocking to 192MHz
- Updated the following Root-Box repos:
1. bionic
2. bootable_recovery
3. dalvik
4. Superuser
5. frameworks_av
6. frameworks_base
7. frameworks_native
08-08-2013 - RootBox-JB-jewel-Unofficial-20130808.zip*
- Update all sources.
- Added Lionheart and Intellidemand Governors.
- Added underclosking to 192MHz and overclocking to 1674MHz. (For some reason it defaults to 1674MHz and not 1512MHz.)
- Put Deck's RIL fixes back in. (As some of you noticed, I screwed up and left these out of the last build.)
- Updated Nova Launcher Basic.
08-03-2013 - RootBox-JB-jewel-Unofficial-20130803.zip*
- Update all sources
- Compiled with GCC 4.8
- RootBoxOTA - replaces Goo Manager.
07-30-2013 - RootBox-JB-jewel-Unofficial-20130730.zip
- Updated all sources
- Superuser Fix
- Changed Wallpaper
- Works well with Black-Box_Gapps_Aroma_20130731-signed.zip
- Stability fix for reboots
07-23-2013 - RootBox-JB-jewel-Unofficial-20130723.zip
- Most recent sources
- Includes patch for Android Master Key bug #8219321 and bug # 9695860
- Added Android Terminal Emulator (Term.apk - this will update through the market)
- Added Apollo
- Added Deck's RIL fix (patch 23) for data dropping. (These commits have still not been committed and are considered to be a work in progress. With that being said, most reports are showing that this fix is working.)
07-21-2013 - Minor Update
- Synced Repos
- Added CM File Manager
- New custom DPI setting for Calculator (Adds extra keys)
07-19-2013 - initial build
- All current Root-Box sources.
- Added Nova Launcher basic as a launcher option.
- Custom default PA DPI settings for a few apps.
- Root-Box wallpaper from Rootbox.ca
- Compiled with -O3 optimizations with GCC 4.7
*While I normally say a dirty flash should not cause any problems, I have found that for some reason I do get rare reboots with a dirty flash. I would recommend using TiB to restore your apps if you run into this problem rather than a nandroid.
Custom Dark Root-Box Gapps
* I did not create any of these Gapps. They were created by CM or SlimROMS. *
These gapps can be used in place of any other gapps. The modifications I made will allow the dark Root-Box setting to affect all the Gapps.
*There is an update in the playstore for Google Hangouts. Do not install the update as you will lose the dark version.
Changelog:
08-01-2013 - Black-Box_Gapps_Aroma_20130801-signed.zip
- Fixed install problem with Google Now and TTS
07-31-2013 - Black-Box_Gapps_Aroma_20130731-signed.zip
All Gapps can be individually installed or left out if you do not use them.
Core apks, libs, ect. are installed without having to select them. (No need to figure out for yourself what HAS to be there.)
Gapps Included:
- Google Play Store
- Gmail
- Google Now
- Google Music
- Hangouts (Formerly Talk)
- YouTube
- LatinIME
- Text To Speech
- Voice Dialer
- Talkback
- Google Ears
- News & Weather
07-29-2013 - Black-Box_gapps_20130729-signed.zip
I took the gapps-jb-20130301 and removed the following files:
- Google Play Store
- Google Talk
- Google Now
- GmsCore.apk
I then added the following Gapps from SlimRom Gapps:
- Google Play Store
- Google Music
- Gmail
- Google Hangouts
- Google Now
- Youtube
- GmsCore.apk
Credits:
I want to thank these guys for their work that has led me to get here. Without them, I would not have been able to even start compiling for myself.
mikeshepard - His instructions on building Root-Box for Jewel got me started on this.
jrior001 - Debugged and fixed recent compiling issues.
kushdeck - Deck's CM builds started me off getting away from stock ROMs since his builds were always top notch.
bajee11 - Root-Box is his creation and IMHO is awesome.
jamieg71 - His Root-Box ROM was the first non-sense ROM I tried. I've been hooked on Root-Box ever since.
sylentprofet
dragonstalker
(If there is anyone that I have not mentioned and I am using your work, please let me know.)
Sources
Root-Box
jrior001
mikshepard
tjarnold
CyanogenMod
WARNING:
Please use this ROM at your own risk. I am not responsible for anything that happens to your phone including the emergence of skynet as a result of using this ROM.
Building from Source
Guide for building Root-Box from source​
To start off, you need Ubuntu 12.04 or higher, 64-bit version installed. You cannot build Android 4.2.2 unless you are using a 64-bit OS. I am personally using Ubuntu 13.04 but I started on 12.04 so either way should be fine.
Everything is done in terminal. Please make sure to type or copy the commands exactly to avoid any issues.
Next we need to get the correct version of Java installed and set up as default. I would recommend removing any other versions. If you want to remove some other common versions that may be installed on your system run:
Code:
sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
Now we need to add a self updating repository for Java.
Code:
sudo add-apt-repository ppa:webupd8team/java
Lets install Java 6
Code:
sudo apt-get update && sudo apt-get install oracle-java6-installer
In case you decided to leave other versions of java or you have another version of Java installed we need to make sure that your computer will use the correct version to compile Android.
Code:
sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_45/jre/bin/java 1
sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.6.0_45/bin/javac 1
sudo update-alternatives --install /usr/bin/jar jar /usr/lib/jvm/jdk1.6.0_45/bin/jar 1
sudo update-alternatives --install /usr/bin/javadoc javadoc /usr/lib/jvm/jdk1.6.0_45/bin/javadoc 1
Now we tell your computer exactly which version of Java to use. After typing each line one of your choices should be JDK1.6.0_45. This is the one you want to choose.
Code:
sudo update-alternatives --config java
sudo update-alternatives --config javac
sudo update-alternatives --config jar
sudo update-alternatives --config javadoc
Now we need to install everything else needed to build Android.
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev python
And
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Here we tell your computer how to "repo".
Code:
kdir ~/bin
export PATH=~/bin:$PATH
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Create a folder to build in and change to that folder.
Code:
mkdir ~/rootbox_jewel
cd ~/rootbox_jewel
Initialize and sync Root-Box sources. This will take quite a while. (Like 3-6 hours with a decent connection. I sync for the first time overnight.) After the first sync, you will only get updates or changes so its much faster. You can also add -jX to the sync command (ex. repo sync -j6) where X is the number of threads being downloaded at the same time. The default is 4. I typically use 6. If you have problems or your system locks up you may want to use a smaller number.
Code:
repo init -u https://github.com/tjarnold/platform_manifest.git -b jb-mr1
repo sync
Download Term.apk. The build will fail without this since I added it into the makefiles.
Code:
cd ~/rootbox_jewel/vendor/cm
. get-prebuilts
Now you are finally ready to compile your ROM.
Code:
. build_rootbox.sh jewel
There are also some extra commands you can add on to the above command. Just type all 3 of these options after the command above. They need to be in the same order otherwise it will not work. 1) sync or nosync - will sync your repo before building, 2) any number - number of threads to build at once (the aboe command defaults to 4), 3) clean or noclean - the clean option will clear out all old build files from a previous build. This is useful if there is a major change or something gets screwed up during the build.
Code:
. build_rootbox.sh jewel sync 4 clean (run repo sync, 4 threads, delete old build files)
. build_rootbox.sh jewel nosync 2 noclean (don't sync, use 2 threads, don't remove old build files)
. build_rootbox.sh jewel sync 6 noclean (run repo sync, 6 threads, don't remove old build files)
If you have followed the directions above, the resulting .zip can be found in:
~/home/rootbox_jewel/out/target/product/jewel
Nice and thanks!
Sent from my EVO using xda app-developers app
Do you have the kernel as a separate file to try and flash it S-On?
Thanks for sharing BTW!!
welshwarriorsf said:
Do you have the kernel as a separate file to try and flash it S-On?
Thanks for sharing BTW!!
Click to expand...
Click to collapse
You can pull it straight from the root directory of the zip file. boot.img is the file you're looking for.
louched1 said:
You can pull it straight from the root directory of the zip file. boot.img is the file you're looking for.
Click to expand...
Click to collapse
OK thanks, I just flash the boot.img 1st then the ROM?
Thanks OP. Great to see new people. Thanks for sharing. :thumbup:
Sent from my EVO using xda premium
New Nightly
New Nightly Up
RootBox-JB-jewel-Unofficial-20130723.zip
Changelog:
- Most recent sources
- Includes patch for Android Master Key bug #8219321 and bug # 9695860
- Added Android Terminal Emulator (Term.apk - this will update through the market)
- Added Apollo
- Added Deck's RIL fix (patch 23) for data dropping. (These commits have still not been committed and are considered to be a work in progress. With that being said, most reports are showing that this fix is working.)
Does this have 4G LTE? I haven't picked anything up yet, but my area is very spotty.
c64fan said:
Does this have 4G LTE? I haven't picked anything up yet, but my area is very spotty.
Click to expand...
Click to collapse
LTE does work. It's just coming into my area so it only works for me in some places.
One thing that I noticed with this ROM after adding Deck's RIL fix is that I had to reboot the ROM for it to connect to data. If anyone else can confirm this.
Nice 1. Thanks for sharing man. Looking forward to see what you bring in the future
SENT FROM MY LTEVO
Does this have the ribbon feature?
downloading now baby!!
@tjarnold since I build RB for the HTC DNA (somewhat similar device) let me know if you can figure out later how to get the camera to work when compiling with GCC 4.7 and -O3, because I ran into the same issue. I fixed it by using GCC 4.6 and -O2 everything compiled fine.
mcwups1 said:
Does this have the ribbon feature?
Click to expand...
Click to collapse
Yes, ribbons are included. They were one of the first reasons that got me back on Root-Box. I love using the ribbons and have a couple set up at any one time.
.torrented said:
@tjarnold since I build RB for the HTC DNA (somewhat similar device) let me know if you can figure out later how to get the camera to work when compiling with GCC 4.7 and -O3, because I ran into the same issue. I fixed it by using GCC 4.6 and -O2 everything compiled fine.
Click to expand...
Click to collapse
I have my rom compiled with GCC 4.7 and -O3. While I did not fix the issue compiling the camera myself, you can see what was done here. I am very new to this so you may be referring to something different.
tjarnold said:
I have my rom compiled with GCC 4.7 and -O3. While I did not fix the issue compiling the camera myself, you can see what was done here. I am very new to this so you may be referring to something different.
Click to expand...
Click to collapse
Mike pm'ed me about what he did to fix it shortly after I posted that post lol but thanks anyways
Sent from my Nexus 7 using XDA Premium HD app
Anyone else have the media volume change with the buttons instead of the ringer? No matter if in an app or not
Sent from my EVO 4G LTE using xda app-developers app
reeher3287 said:
Anyone else have the media volume change with the buttons instead of the ringer? No matter if in an app or not
Sent from my EVO 4G LTE using xda app-developers app
Click to expand...
Click to collapse
Yes. That is the way it is set up. The repos I'm using have it set that way. I like it that way since I keep my ring on silent and use to accidentally hit the volume button and either turn it up or turn off vibrate and this annoyed me.
I have never looked into where this setting is. I did check to see if I could find something in settings to change this, but did not find one.
its all good, ive kinda grown to like it myself lol.
on another hand, this rom and jellbeer latest i keep getting random reboots and when it would boot back up system process fc's, never had these problems before using cm based roms for the past year. any ideas??
latest firmware and etc except the ts driver btw

[ANGLER] [8.0.0] [3.10.107] [GCC 7.2.1] Flash Kernel v3.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Hello everyone, this is my personal kernel for the Nexus 6P. While I am not a super star kernel developer, I do know my way around it. My philosophy on kernels is pretty simple:
Follow upstream Linux always
Stable kernel rules work best
Security and stability are paramount
Features will be added only as needed
Hopefully you enjoy
Thread Rules
I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this. More on bug reporting policy here.
Keep things civil, I do NOT tolerate flaming of any kind.
OT is allowed.
Features
Here are the major features of the kernel (feel free to explore Github)
Updated to the latest security patch on the latest Android version (August on Oreo)
Updated to the latest Linux upstream version (3.10.107)
Several CVE fixes
Upstream patches from CAF and Linux
Touchboost force disabled
High brightness mode
KCAL color control
Adreno Boost
Wake gestures (sweep2wake, doubletap2wake, sweep2sleep, and camera launch gesture)
Faux Sound Control with high performance audio
ZRAM from 3.18
Maple I/O scheduler
Wakelock controls
TCP algorithms: bic, cubic, highspeed, htcp, hybia, illinois, lp, reno, scalable, vegas, veno, westwood (default)
F2FS support (latest from here)
Compiled with a Linaro 7.2.1 toolchain built with crosstool-NG (located here).
Makefile optimizations (courtesy of @adinkwok)
Forced encryption and dm-verity disabled
Hides bootloader unlock from SafetyNet (can still fail through other means)
Flashed with AnyKernel2 (thanks to @osm0sis)
Downloads
8.0.0 (v3.x): https://github.com/nathanchance/angler/releases
Legacy downloads:
7.1.2 (v1.x-v2.x): https://github.com/nathanchance/angler/releases
7.1.1 (4.x): Main
7.0 (3.x): Main
6.0.1 (1.x): Main
Do not mirror my kernels!
Installation
If you are on stock:
If you are on the stock kernel: flash the kernel zip and reboot
If you are on a custom kernel: flash the stock boot image matching your build number, flash the kernel zip, and reboot
If you are on a custom ROM:
If you are on the kernel that came with your ROM: flash the kernel zip and reboot
If you are on a custom kernel: dirty flash your ROM zip, flash the kernel zip, and reboot
Upgrading from one Flash version to the other:
Just flash the kernel zip and reboot
Changelog
Latest post
Kernel: https://github.com/nathanchance/angler/commits/8.0.0-flash
AnyKernel: https://github.com/nathanchance/AnyKernel2-archive/commits/angler-flash-public-8.0.0
Frequently asked questions
1.1 Q: I am having an issue, can you help me?
1.1 A: I am not an amazing kernel developer but I will certainly try my best. First, start by reading the release posts, as I may make note of a particular issue. Also search the thread to see if I have discussed it before. If you see nothing, please provide me with a dmesg/last_kmsg and logcat, your ROM/kernel version, and a detailed description of the issue, following this guide. If I can't reproduce reliably though, I'm not going to fix the issue.
1.2 Q: Can you add xyz feature?
1.2 A: If you link me the commits or tell me what kernel you had the feature in, I can take a look at them. I will not go digging super hard for commits and I will ignore requests that don't include this information. I won't promise that I will merge every request but I will always take it into consideration.
1.3 Q: How do I control the kernel?
1.3 A: I'd recommend using either @flar2's EX Kernel Manager or @Yoinx's Kernel Adiutor-Mod; both are extremely solid and have given me no issues.
1.4 Q: What ROM are you on? What are your settings?
1.4 A: Currently, I am on Dirty Unicorns and my settings are available here
1.5 Q: OMFG MY BATTERY SUXXXX PLS FIX!!!
1.5 A: The kernel doesn't drain any battery, use an app like BetterBatteryStats to figure out what app is screwing with your phone.
Thanks to:
@neobuddy89 for always providing great fixes and being a shining example of a great kernel developer
The various other developers for their patches (@ak, @Buckmarble, @flar2, @franciscofranco, @frap129, @imoseyon, and @Yank555 to name a few)
@osm0sis for AnyKernel2
@DespairFactor for helping me with some kernel compilation issues
@kwoktopus for giving me good advice on Makefile flags and other patches
@kantjer for being a beta tester along the way!
@malybru for my nifty new signature!
@phantom146 for the thread banner and default profile GlassCannon
All of you guys for viewing the thread
A note about donations
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Kernel source links
8.0.0: https://github.com/nathanchance/angler/tree/8.0.0-flash
7.1.2: https://github.com/nathanchance/angler/tree/7.1.2-flash
7.1.1: https://github.com/nathanchance/angler/tree/7.1.1-flash
7.0: https://github.com/nathanchance/angler-old/tree/release-7.0
6.0.1: https://github.com/nathanchance/angler-old/tree/release-6.0.1
DISCLAIMER: I openly welcome off topic in my threads. Mods, please do not clean off topic discussion and users, do not complain about off topic discussion here. I may direct you to another thread if it is so suited but I won't have the discussion cleaned. Thank you.
XDA:DevDB Information
Flash Kernel, Kernel for the Huawei Nexus 6P
Contributors
nathanchance
Source Code: https://github.com/nathanchance/angler
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v3.1
Stable Release Date: 2017-09-17
Created 2016-08-11
Last Updated 2019-07-02
How to compile the kernel
BUILD GUIDE: https://github.com/nathanchance/Android-Tools/blob/master/Guides/Building_Flash.txt
BUILD SCRIPT: https://github.com/nathanchance/Android-Tools/blob/master/Scripts/build-flash.sh
FORMER GUIDE:
1. Configure your environment
In order to compile this kernel, I'd recommend using Linux (OS X should be acceptable but this guide will be tailored for Linux). If you can't dual bot, use Virtual Box to create a virtual machine. To get the environment configured, either use Google's own guide here or my guide (only section 1) here.
2. Grab the source
Grab the kernel source
Code:
mkdir ~/Android
cd ~/Android
git clone https://github.com/Flash-Kernel/angler.git Flash
Explanation:
First command makes a directory named Android in your home folder (mkdir = make directory). You can change the location if you want but keep it consistent throughout the guide.
Second command moves into that directory (change directory)
Third command pulls the source from my Github into a directory named Ninja (git clone <url> <folder_to_clone_in_to> is the format of the command).
Grab the toolchain you want to use to compile the kernel
Code:
cd ~/Android
git clone <kernel_url>
Explanation:
In order to compile the kernel, we need to grab a toolchain (bunch of compilation tools). I currently use DF-LINARO4.9 (third to last option in this list) but I have used all of these in the past. Below are the list of possible URLs to clone; copy and paste it after the words git clone above:
AOSP: https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
Uber 4.9: https://bitbucket.org/DespairFactor/aarch64-linux-android-4.9-kernel.git
Uber 5.4: https://bitbucket.org/DespairFactor/aarch64-linux-android-5.x-kernel.git
Uber 6.1: https://bitbucket.org/DespairFactor/aarch64-linux-android-6.x-kernel.git
Uber 7.0: https://bitbucket.org/DespairFactor/aarch64-linux-android-7.0-kernel.git
Linaro 4.9: https://android-git.linaro.org/git/.../aarch64/aarch64-linux-android-4.9-linaro.git
Linaro 5.4: https://android-git.linaro.org/git/.../aarch64/aarch64-linux-android-5.4-linaro.git
Linaro 6.1: https://android-git.linaro.org/git/.../aarch64/aarch64-linux-android-6.1-linaro.git
DF-Linaro 4.9: https://bitbucket.org/DespairFactor/aarch64-linux-android-4.9-kernel-linaro.git
DF-Linaro 5.4: https://bitbucket.org/DespairFactor/aarch64-linux-android-5.x-kernel-linaro.git
DF-Linaro 6.1: https://bitbucket.org/DespairFactor/aarch64-linux-android-6.x-kernel-linaro.git
3. Setup the build
Make sure everything looks right
After following the above steps, type:
Code:
ls
You should see something like this:
Code:
aarch64-linux-android-4.9-kernel-linaro Flash
The toolchain directory make be different depending on what you cloned above. If it looks different, delete the Android folder and do step 2 again.
Select the correct kernel branch
Code:
cd ~/Android/Flash
git checkout release
Explanation
First command will move you into the Flash source directory we cloned above.
Second command will checkout the branch you want to compile for (in this case, release)
4. Make the kernel
Tell the makefile what toolchain and architecture you are building for
Figure out the full path of your toolchain folder
Assuming you have done this whole process correctly, you can move into your toolchain directory and type:
Code:
cd ~/Android/<toolchain_folder>
pwd
Example:
Code:
cd ~/Android/aarch64-linux-android-4.9-kernel-linaro
pwd
You should get something like this:
Code:
/home/nathan/Android/aarch64-linux-android-4.9-kernel-linaro
Tell the compiler where that toolchain is
Copy and paste that file location above into this command:
Code:
export CROSS_COMPILE=<toolchain_dir>/bin/aarch64-linux-android-
Example:
Code:
export CROSS_COMPILE=/home/nathan/Android/aarch64-linux-android-4.9-kernel-linaro/bin/aarch64-linux-android-
Set the architecture
Angler is a 64-bit device so we need arm64
Code:
export ARCH=arm64
export SUBARCH=arm64
Clean up from a previous compilation and update the source
Code:
cd ~/Android/Flash
git reset --hard origin/n
git clean -f -d -x > /dev/null 2>&1
make clean && make mrproper
git pull
Example:
Code:
cd ~/Android/Flash
git reset --hard origin/n
git clean -f -d -x > /dev/null 2>&1
make clean && make mrproper
git pull
Explanation:
The first command moves you into the Flash source directory.
The second command will undo any local commits you have done and align your source with the most recent commit from me.
The third command will clean any untracked or compiled files (this is send to /dev/null so you do not see it happen).
The fourth and fifth command (strung together with &&) will remove you
The sixth command will pull any new kernel changes from me into the source.
Set up the defconfig
A defconfig tells the compiler which features you want in the kernel. This is already set up by me. To set up the defconfig, type the following:
Code:
cd ~/Android/Ninja
make flash_defconfig
Name the kernel
If you notice in About Phone > Kernel Version, it shows 3.10.103-FLASH-v3.10 (or something similar). You can customize this by opening the Makefile in the source directory and editing the EXTRAVERSION variable (this will be undone next time you compile).
Make the kernel!
Code:
make -j#
Example:
Code:
make -j4
Explanation:
The # after the "j" is how many simultaneous threads are run. Traditionally, this is the number of cores you have plus one. So a quad-core CPU would be -j5.
5. Zip it up and flash!
Copy the zImage to the AnyKernel directory
Code:
cd ~/Android/Flash/arch/arm64/boot
cp -v Image.gz-dtb ~/Android/Flash/anykernel/zImage
Explanation:
We need to copy the newly compiled kernel (which resides in the arch/arm64/boot folder) to the AnyKernel directory, while changing its name to zImage.
cp = copy
-v = verbose (prints the copying)
Image.gz-dtb = file to be copied
~/Android/Flash/anykernel/zImage = destination and name
Zip it up!
Code:
cd ~/Android/Flash/anykernel
zip -r9 flash-kernel.zip * -x README flash-kernel.zip
Using the above commands, your newly completed kernel will be located at ~/Android/Flash/anykernel/flash-kernel.zip
If you followed all of the above steps successfully, congratulations, you built the kernel!! Once you have done all five steps, you will just need to follow steps 4 and 5 to update in the future. Below, I have linked a script that will do all of this for you (with some variable edits at the top); however, please do it manually first so you know exactly what you are doing enjoy!
https://raw.githubusercontent.com/nathanchance/angler/release/build-flash.sh
Below are screenshots of me doing this process in a virtual machine (Mint 18) with 2 cores, 4GB of RAM, and 15GB of storage on my MacBook with a 2.5 GHz Intel Core i5 and 8GB of RAM (fairly average in the world of PC specs I think). It's totally possible to do this on your own. Additionally, in the next post, I have provided some tips for customizing the kernel even further!
How to do your own modifications to the kernel
Introduction
When I was getting started with compiling kernels, I relied a lot on Google and git documentation (this website is the best) to get what I wanted to accomplished. As a lot of that reading can be kind of dense. I decided to boil it down to the few commands and procedures you will need to modify this kernel (or any git repo).
LEARN GIT FROM THE COMMAND LINE. Seriously, do not use a program like SmartGit, it will cripple you and your workflow and potentially screw up authorship. Do it the right way using this guide.
Note: This is NOT supposed to be a super technical guide/how-to on Git. If there is something that is glaringly inaccurate, I will fix it but I am not going to add a ton of extra text here as there are plenty of Git tutorials you can easily find with Google. This is a crash course.
Git Introduction
What's a git?
Git is a version control system that allows developers to keep track of their changes to code. This is extremely helpful when working with large amount of code and changes across a large range of files (such as a kernel or ROM) as it allows you to easily revert or add changes as you see fit.
Terminology
These are not super precise definitions (you can find technical ones by Googling "what is a <word> git"):
Repository: the location that holds all of your code changes and files (this can be local or remote).
Commit: a change to your code
Branch: different snapshots of your code
Cloning: copying a remote repo to a local one
Forking: copying a repo (either remote or local) and making changes to it without affecting the other
Reading Github
Github is the most popular site for hosting git repositories. This is what my repo is hosted, which I will be using for my example. If you go to https://github.com/nathanchance/Ninja-Kernel, you will be greeted with this screen:
Here we will unpack those terms above. The repository (that view) contains files. At the top, you will see a tab called Commits. Clicking on this will bring you to a view similar to this:
This is a full list of the changes to the repository. The name of the commit message generally describes what it does and clicking on the title of the commit will bring you into the detailed view:
In this commit, I have renamed the version from 1.1.1 to 1.2. Some commits will be very small like this, others won't be. Additionally, in the righthand corner of the commit message, you'll see a commit hash (bunch of numbers and letters). That will come in handy later.
Back on the home page of the repo, if you click on the branch dropdown, you will see the various different branches of the repo:
If you click on a branch (let's do n in this case), you'll be brought to a page similar to the home page but there may be different commits in the commits tab. In this case, I have committed version 2.1 instead of 1.1:
This should help you navigate around Github and find commits you may want to merge.
Git Documentation
Throughout the next sections, I will be using commands to show you how to modify the source. This section goes over the command format, what it does, and an example.
git clone
Format:
Code:
# Clone a repo into a directory the same as its remote name
git clone <url>
# Clone a repo into a directory with a specified name
git clone <url> <name_of_folder>
What it does:
- Copies a remote repo into a folder on your computer
Example:
Code:
git clone https://github.com/nathanchance/Ninja-Kernel.git
git clone https://github.com/nathanchance/Ninja-Kernel.git Ninja
Screenshot:
git checkout
Format:
Code:
# Changes to the specified branch (if it does not exist, it creates one)
git checkout <branch>
# Creates a new branch based off the specified one
git checkout -b <branch> <branch_to_be_based_on>
What it does:
- Whenever you want to make changes to files, you need to make sure you are on the right branch. You can see what branch you are currently on by running git branch; if you are on a different one, switch to the right one using the above commands
- If you want to create a new branch, use the second command.
Example:
Code:
# Switches to the m branch
git checkout m
# Creates a new branch "new-branch" based on old-branch
git checkout -b new-branch old-branch
Screenshot:
git add
Format:
Code:
# Adds a file to the staging index
git add <file>
# Adds all of the changed files to the staging index
git add -a
What it does:
- This adds a file to the list of changes to commit (staging). So let's say you modify the README of your repo, deleting a line, and adding one. In order to register that change, you need to add the file to your staging index.
Example:
Code:
# Adds the file README to the index
git add README
Screenshot:
git status
Format:
Code:
# Tells you what the status is of your repo
git status
What it does:
- Allows you to see what files you have staged for commit, where you are relative to where you are with your remote
Example:
Code:
Screenshot:
git commit
Format:
Code:
# Commit your changes and bring up a nano window to write your message
git commit
# Commit your changes and create the message as a parameter
git commit -m "Commit message here"
What it does:
- Saves all of your staged changes in a commit
Example:
Code:
git commit -m "This is a test commit message"
Screenshot:
git revert
Format:
Code:
# Undoes the changes by a certain commit
git revert <hash>
What it does:
- Undoes the commit you have chosen.
- NOTE: It is a good idea to add to the commit message why you are reverting a commit so people don't have to guess (did you not like it or did it break something?)
Example:
Code:
git revert 18d72d42648de9fde9bedcc810a936e0d253af9c
Screenshot:
git pull
Format:
Code:
git pull
What it does:
- Retrieves the latest changes from your remote repository (like Github)
Screenshot:
git push
Format:
Code:
git push
What it does:
- Opposite of git pull, it sends your latest changes from your local repository to the remote
Screenshot:
git fetch
Format:
Code:
# Fetches the commits from the main branch of a remote repository
git fetch <url>
# Fetches the commits from the specified branch of a remote repository
git fetch <url> <branch>
What it does:
- Whenever you want to merge or cherry pick something from a repository other than your own, you need to fetch it so git knows where to pull commits from.
Example:
Code:
# Fetches the commits from the n branch of my repo
git fetch https://github.com/nathanchance/Ninja-Kernel.git n
Screenshot:
git merge
Format:
Code:
# Merge one branch of your repo with the current one
git merge <branch_to_merge>
# Merge a remote branch into the current one
git merge <remote>/<branch_to_merge>
What it does:
- Takes the commits in the specified branch and merges the ones that are not present in the current branch.
Example:
Code:
git merge n
git cherry-pick
Format:
Code:
# Takes a commit either from another branch or the list you fetched and merges it into your current branch
git cherry-pick <hash>
# Pick a range of commits
git cherry-pick <hash_1>^..<hash_2>
What it does:
- If you have a commit in another branch and want to merge it into your current branch, get the hash either from Github if pushed or git log (below) and run git cherry-pick
- If you have a commit in a remote repo you want to merge into your current branch, fetch the remote repo and run git cherry-pick with its hash (found on the remote repo's website)
Example:
Code:
git cherry-pick 68a8ff686ccb2ff01cbaa7b2704c4da6c066ecc8
gcp 7204eedd1076bd87c624aab4fb9c0cc6ac50933b^..102a72b895afb063240fb09292c17e11155e8dd9
Screenshot:
git log
Format:
Code:
# Brings up a list of commits with their full messages and hashes
git log
# Brings up a list of commits with the title of their message and full hashes
git lot --format="short"
# Brings up a list of commits with short hashes and messages
git log --oneline
What it does:
- This command allows you to see the revision history of your local repo
Screenshots: (git log, git log --format=short, then git log --oneline
How To's
Merge Android security updates
There are two ways to do this (I personally recommend cherry-picking)
1. Cherry pick the individual commits
1. Fetch Google's repo
Google's kernel repository is located here: https://android.googlesource.com/kernel/msm/
Currently, Angler is on the branch android-msm-angler-3.10-marshmallow-dr1.6-1
Thus, the command looks like this:
Code:
git fetch https://android.googlesource.com/kernel/msm/ android-msm-angler-3.10-marshmallow-dr1.6-1
2. Figure out which commits you need to pick
Click on the branch you want to merge commits from in Google's list
Click on the "log" link next to the commit hash
In that list, find the first commit at the top of the list and open it in a new tab (now referred to as the last commit)
Start skimming the list, looking for the next commit that has a green android-6.0.1_r# next to it
Open the commit right above that commit (now referred to as the first commit)
Copy the individual hashes of the first and last commit (make sure to know which is which!)
3. Pick the commits!
Code:
git cherry-pick <hash_of_first_commit>^..<hash_of_second_commit>
Example
Commit log located here: https://android.googlesource.com/kernel/msm/+log/android-msm-angler-3.10-marshmallow-dr1.6-1
First commit: https://android.googlesource.com/kernel/msm/+/46b9920417db45ee0a93f16a07e80666219446d3
Last commit: https://android.googlesource.com/kernel/msm/+/909746bb5e4be07344b4fe4ce95c57fbfc8d9595
Code:
git fetch https://android.googlesource.com/kernel/msm/ android-msm-angler-3.10-marshmallow-dr1.6-1
git cherry-pick 46b9920417db45ee0a93f16a07e80666219446d3^..909746bb5e4be07344b4fe4ce95c57fbfc8d9595
2. Merge the whole branch
1. Add a remote
Google's kernel repository is located here: https://android.googlesource.com/kernel/msm/. A remote allows us to easily fetch a repo we use often. To add a remote, follow the below format:
Code:
git remote add <name> <url>
In this case:
Code:
git remote add aosp https://android.googlesource.com/kernel/msm/
Example:
2. Fetch the repo
Format:
Code:
git fetch <name_of_remote_above>
Example:
Code:
git fetch aosp
3. Merge the branch
On the left of Google's website, you will notice there are some branches. Currently, Angler is on android-msm-angler-3.10-marshmallow-dr1.6-1 (you can tell by the commit date of the first commit)
The format looks like this:
Code:
git merge <name_of_remote>/<branch_to_merge>
Example:
Code:
git merge aosp/android-msm-angler-3.10-marshmallow-dr1.6-1
Merge new Linux kernel updates
1. Fetch the kernel.org repo
We are on the 3.10 branch of the stable repo: https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git
Code:
git fetch git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.10.y
2. Figure out which commits you need
Go to the kernel.org website
In the 3.10 line, click browse
You will be presented with a full list of commits
Open the first one in a new tab (which should be something in the form of "Linux 3.10.y" (now known as last commit)
Use the next link at the bottom of the list and skim through the list of commits until you see the next commit in the form of "Linux 3.10.y"
Open the commit directly above the previous commit (now known as the first commit)
Copy the hash of the first and last commits (making sure you know the difference!)
3. Pick the commits
Code:
git cherry-pick <hash_of_first_commit>^..<hash_of_last_commit>
Example
First commit of 3.10.102: https://git.kernel.org/cgit/linux/k.../?id=ce9588a047eae53baf1607a408a8d1d5363f5fde (found on this page)
Last commit of 3.10.102: https://git.kernel.org/cgit/linux/k.../?id=ca1199fccf14540e86f6da955333e31d6fec5f3e (found on this page)
Code:
git fetch git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.10.y
git cherry-pick ce9588a047eae53baf1607a408a8d1d5363f5fde^..ca1199fccf14540e86f6da955333e31d6fec5f3e
If you get any conflicts. resolve them using the fix merge conflicts section below.
Add a feature from another kernel
I will be using @flar2's wake gestures as an example but this process will work for any set of commits. I have provided a Git example repo here. On the aosp-latest branch will be the latest kernel source from AOSP. If you want to follow along in this tutorial, clone that repo and checkout the branch like so:
Code:
git clone https://github.com/nathanchance/Git-Example.git && cd Git-Example && git checkout aosp-latest
1. Figure out which commits you need
This can be a little bit tricky. When adding a feature, there may be more than one commit you need to grab. The trick I use for figuring out if this is the case is going into the detailed commit view (take this commit for example), copying the location of one of the files changed, going back to the head of the repo (in this case, here), navigating to that file, and clicking the history button in the right hand corner. This should give you something like this:
Now copy all of the commit hashes (you can click the little arrow clipboard icon next to the commit message to do this automatically. That gives us this list for wake gestures:
12cea9ee691f9794d3b0a76c6b381b4bde670bda
f4286dee51fde5c1082732381c9474c8381b8fb6
4c9e7f3f63eaf7514154633d320a6d4dd4f94831
5d10751af74617c23dfaf93bdf8149e39ce6da41
79d2aae008e51ed32d64e8a4a1dcf03231a22439
6495a2b15e501ce81bb58d39edd5923d52c2e45f
37daa721971b17a01d503c6dfa66c7c93b7cde2d
2. Fetch the repo
Now we need to fetch the repo that has the commits we need (in this case, the ElementalX repo).
Code:
git fetch https://github.com/flar2/angler.git ElementalX-1.00
Example:
3. Pick the commits
After fetching the repos, make sure you are on the proper branch using git checkout and git branch. Once this looks good, run git cherry-pick with the hashes:
Code:
git cherry-pick 12cea9ee691f9794d3b0a76c6b381b4bde670bda
git cherry-pick f4286dee51fde5c1082732381c9474c8381b8fb6
git cherry-pick 4c9e7f3f63eaf7514154633d320a6d4dd4f94831
git cherry-pick 5d10751af74617c23dfaf93bdf8149e39ce6da41
git cherry-pick 79d2aae008e51ed32d64e8a4a1dcf03231a22439
git cherry-pick 6495a2b15e501ce81bb58d39edd5923d52c2e45f
git cherry-pick 37daa721971b17a01d503c6dfa66c7c93b7cde2d
Screenshot:
In this case, I was lucky not to have any conflicts. If you try to pick something and there are differences between the code that conflict, you'll get a merge conflict which you will need to fix before committing the cherry pick.
4. Check for any conflicts
Now when you merge a feature, you may need to enable in your defconfig. In this case, we need to add the line CONFIG_WAKE_GESTURES=y (tells the compiler to build the wake gestures module and add it). You can see an example of this here and here.
Fix merge conflicts
I'm not going to explain it any better than these guides
https://help.github.com/articles/resolving-a-merge-conflict-from-the-command-line/
https://githowto.com/resolving_conflicts
http://stackoverflow.com/questions/161813/how-to-resolve-merge-conflicts-in-git
Special note: Authorship
Authorship is very important in the open source world, as it is what allows people to determine who is responsible for the commit and receive the proper credit. The general rule of thumb is if you didn't think of the idea and write the code, you are not the author. If you are cherry-picking properly, authorship should be automatically maintained; however, if you have to commit something that isn't yours or do some other wonky stuff, you may become the author. No worries though, it is very easy to fix it!
Apply authorship during commit:
Format:
Code:
git commit --author="Full Name <[email protected]>"
Example:
Code:
git commit --author="Nathan Chancellor <[email protected]>"
Screenshots:
Apply authorship after commit
Format:
Code:
git commit --amend --author="Full Name <[email protected]>"
Example:
Code:
git commit --amend --author="Nathan Chancellor <[email protected]>"
Screenshots:
Note: if you have already pushed your commit, you will need to amend the commit and force push it to change it:
Code:
git push origin --force
Good to see you with a kernel of yours.
Should have done this earlier
Sent from my angler using XDA Labs
Congrats!
I found you a cover picture
Nice, let's test, thanks.
cool
Gesendet von meinem Nexus 6P mit Tapatalk
Cool ?
Envoyé de mon Nexus 6P en utilisant Tapatalk
Nice one buddy, been using the kernel now for a few hours and its stable and blazing fast.
Only thing I noticed and maybe you could look into this, is sometimes when I unlock the phone and I am using chill governor it gets stuck at 302 frequency and will not go up at all........ Tried it on other kernel with chill, running same setup and was not the case. Thanks for the awesome kernel, very snappy!
Thanks @nathanchance. Great to see your own kernel make a debut.
Glad to see you adding your own flavors and goodies and sharing the finished product with us!
Flashing this now!
Nice looking kernel dish! Kudo's
yung40oz84 said:
Only thing I noticed and maybe you could look into this, is sometimes when I unlock the phone and I am using chill governor it gets stuck at 302 frequency and will not go up at all........ Tried it on other kernel with chill, running same setup and was not the case. Thanks for the awesome kernel, very snappy!
Click to expand...
Click to collapse
What kernel had it working properly? I am going to guess it is a wakeup issue or something. That governor is based on conservative, which has not be updated (at least on our Linux versiom 3.10.x) for big.LITTLE, so I am a little surprised it is working well elsewhere.
I went with the 'tried & true' settings, and immediately noticed ui was snappier. Only been running it half a day so I expect things to get better as it settles.
Nice work!
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Just flashed this along with PN, excited to give it a run. Thanks for the kernel
Flashed it along with beltz rom and so far I'm very satisfied! Thank you.
Sent from my Nexus 6P using XDA-Developers mobile app
Best kernel for 6P. Not even an opinion, just based on performance.
I run Arise always and usually i need to put min freq of clust 1 to 480 MHz, so theres no clipping. This is with other kernels.
Ninja runs it perfect and smooth even with min freq set to 302 MHZ.

[GUIDE] Building Pure Nexus

Introduction
Alright guys, there was a lot of talk about building Pure Nexus in the main thread, which was a little irritating for some so now we get our own thread! In this post, I will be giving you some resources to go over in order to help you with compilation. If you have any questions, just ask!
If you compile successfully, feel free to share your accomplishment and your computer specs
Compilation Guide
This is available on my Github, where it may be a little more up to date.
0. Getting started
In this guide, I will go over how to build Pure Nexus on your Linux machine. This particular tutorial will focus on Ubuntu 16.04 (Mint 18 is also good) since that is what Google recommends but this should work with any version of Linux (here are steps for setup with Arch Linux, which will cover step 1); it does need to be 64-bit however. I will leave the installation of that up to you, Google is a wonderful resource. If you don't have a good computer but still want to build, check out this thread on XDA: http://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
1. Set up your environment
1. Automatically
Code:
sudo apt-get install git-core
git clone https://github.com/akhilnarang/scripts
cd scripts
ls
bash <script-name>
<script-name> should be one of the scripts in the folder for your particular architecture.
2. Manually
1. Install Java 8
Code:
sudo apt-get update
sudo apt-get install openjdk-8-jdk
sudo apt-get install openjdk-8-jre
2. Install other build tools
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc unzip
2. Configure repo and git
If you have any problems with the below commands, try running as root:
Code:
sudo -s
Git is an open source version control system which is incredibly robust for tracking changes across repositories. Repo is Google's tool for working with Git in the context of Android. More reading if you are interested: https://source.android.com/source/developing.html
Run these commands to get repo working (only do this if you did the manual set up method above:
Code:
mkdir ~/bin
PATH=~/bin:$PATH
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Run these commands to get git working:
Code:
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
3. Download the source
First, before downloading the source, create a folder for the source and move into it.
Code:
mkdir ~/<foldername> (eg. mkdir ~/PN or ~/PureNexus)
cd ~/<foldername>
Then, we need to grab the manifest and sync down the repositories. Here are the commands to do this for Pure Nexus for Nougat (make sure you are in the source folder you made above):
Code:
repo init -u https://github.com/PureNexusProject/manifest.git -b android-7.1
repo sync --force-sync
NOTE: The value for the -b flag, "android-7.1", may change; you will need to go to the manifest's page and see what the branch currently is.
Here is the process generally for other ROMs:
When you go to build a ROM, you must download its source. All, if not most, ROMs will have their source code available on Github. To properly download the source, follow these steps:
Go to your ROM's Github (e.g. http://github.com/PureNexusProject)
Search for a manifest (usually called manifest or android_manifest).
Go into the repo and make sure you are in the right branch (located right under the Commits tab).
Go into the README and search for a repo init command. If one exists, copy and paste it into the terminal and hit enter.
If one does not exist, you can make one with this formula:
Code:
repo init -u <url_of_manifest_repo>.git -b <branch_you_want_to_build>
For example:
Code:
repo init -u http://github.com/PureNexusProject/manifest.git -b android-7.1
After the repo has been initialized, run this command to download the source:
Code:
repo sync --force-sync
This process can take a while depending on your internet connection.
4. Build it!
At this point, it'd be a good idea to set up ccache. ccache is a compiler cache, it stores previously compiled files in a directory and pulls from that instead of recompiling if nothing has changed. This speeds up compilation a LOT. If you want to use it, follow the below steps:
Open up your .bashrc file in your home directory using a text editor or nano and append this to the end of it:
Code:
export USE_CCACHE=1
Then type:
Code:
source ~/.bashrc
After that, run one of the below command (replacing the # with how many GBs of ccache you want, 50 is recommended)
Use this one if you used the manual method of set up in section 1:
Code:
prebuilts/misc/linux-x86/ccache/ccache -M #G
Use this one if you used the automatic method of set up in section 1:
Code:
ccache -M #G
After that, it's time to build!
Code:
. build/envsetup.sh
breakfast angler
mka bacon
After that, your computer will build the flashable zip file and if you see something that says make completed, you've done it!
Any time that you want to rebuild, type the following commands:
Code:
repo sync --force-sync
. build/envsetup.sh
breakfast angler
mka clobber
mka bacon
I also have a script to do this on my Github here
Frequently Asked Questions
1.1 Q: I got an error, what do I do??
1.1 A: Well to start, if it is anything with Ninja, I would go ahead and disable it. You can add this to your .bashrc file:
Code:
export USE_NINJA=false
Then type this
Code:
source ~/.bashrc
. build/envsetup.sh
breakfast angler
mka clobber
mka bacon
If it is saying you ran out of memory, follow this post.
If it isn't Ninja related, check out @AzraelsKiss's post here, where he has documented a few common issues. If none of those apply, post here with a detailed list of what you have done and we will do our best to help you.
1.2 Q: Can you guys share your personal builds?
1.2 A: No, personal builds are just that: personal. Beans releases whenever he feels that the release is ready for the masses and if a bunch of personal builds are floating around, that tarnishes the Pure Nexus name. We are more than happy to help get you up and running but we will not be sharing our builds. Thanks for understanding!
MOD EDIT - THIS IS A DEVELOPER DISCUSSION. NOT FOR ORDINARY USERS. There is No Rom for you to Flash. Nor will there be any support for you. Any ETA or other NON-DEVELOPMENT posts here will be removed without warning!
XDA:DevDB Information
A Guide to Building Pure Nexus for Nougat, ROM for the Huawei Nexus 6P
Contributors
nathanchance, BeansTown106
Source Code: https://github.com/PureNexusProject
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-09-15
Last Updated 2017-01-15
Building PureNexus Nougat
RESERVED
Building PureNexus Nougat
Ubuntu is what Google recommend for Android AOSP development. See you http://source.android.com/source/requirements.html
Sent from my Nexus 6P using XDA-Developers mobile app
XDA:DevDB Information
Building Pure Experience Nougat, ROM for the Huawei Nexus 6P
Contributors
Fralund
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2016-09-15
Last Updated 2016-09-15
Fralund said:
Ubuntu is what Google recommend for Android AOSP development. See you http://source.android.com/source/requirements.html
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
But you can actually use most any flavor you wish... You just have to figure out the speedbumps yourself. You can even build using OSX, but that's a whole nutter ball of worms...
Have a good one!
AzraelsKiss said:
I'm a little late, but better late that never... Brand new build with the brand new vendor and blobs... It runs so pretty...
Have a good one!
Click to expand...
Click to collapse
Link?
iSilverBullet said:
Link?
Click to expand...
Click to collapse
It's a personal build, so no link.
iSilverBullet said:
Link?
Click to expand...
Click to collapse
As nathanchance has already said... Personal builds shouldn't be passed around. It's disrespectful to the devs...
Have a good one!
nathanchance said:
Code:
export USE_NINJA=false
mka clobber
breakfast angler
mka bacon
Does that work?
Click to expand...
Click to collapse
Worked very well for me
For those of you that are building PN Nougat, are some minor customizations implemented yet? I ask since I am compiling a copy for myself right now.
laxattack said:
For those of you that are building PN Nougat, are some minor customizations implemented yet? I ask since I am compiling a copy for myself right now.
Click to expand...
Click to collapse
https://plus.google.com/+NathanBenis/posts/21sRasA8Abj
From the sound of Nate's post... He's just got the ROM to the point that he's ready to start on customization. We do have a power menu though.
Have a good one!
laxattack said:
For those of you that are building PN Nougat, are some minor customizations implemented yet? I ask since I am compiling a copy for myself right now.
Click to expand...
Click to collapse
Advanced reboot menu, ADB over network, and stock nav bar tuner and night mode re-enabled are the major ones right now.
Somehow haven't been able to get my virtual machine to compile PN over the weekend (really need to convert my old laptop into a Linux only machine, that's for another day).
So since I want my first N rom to be PN on my N6P and am waiting patiently for it, that means that my Samsung Tab S 8.4 is running Nougat first
Go figure!
GO PN
laxattack said:
For those of you that are building PN Nougat, are some minor customizations implemented yet? I ask since I am compiling a copy for myself right now.
Click to expand...
Click to collapse
nathanchance said:
Advanced reboot menu, ADB over network, and stock nav bar tuner and night mode re-enabled are the major ones right now.
Click to expand...
Click to collapse
What @nathanchance said. But I was surprised to find that after restoring all my previous apps, it works very well and very fast. Definitely faster than 6 builds. Too early to tell
Substratum works with no issues.
Could not get some apps to work like gmd gestures, etc . Not the roms fault but the apps have to be updated for nougat support.
kipue said:
Somehow haven't been able to get my virtual machine to compile PN over the weekend (really need to convert my old laptop into a Linux only machine, that's for another day).
So since I want my first N rom to be PN on my N6P and am waiting patiently for it, that means that my Samsung Tab S 8.4 is running Nougat first
Go figure!
GO PN
Click to expand...
Click to collapse
With some support from this thread, I had no issues compiling... ( I am a super newbie )
aalupatti said:
What @nathanchance said. [...]
With some support from this thread, I had no issues compiling... ( I am a super newbie )
Click to expand...
Click to collapse
Yeah something is wrong with my environnement, the repo sync does not even complete.
I suspect is that I need to give my VM more room to breeze RAM wise.
Anyhow, will see that on my side, that's probably quite OP already.
Thanks ^^
Hey, @nathanchance I'm pretty certain you are running Ubuntu on a VM, right? If so can you share how much memory and storage you have allocated to the VM? I didn't allocate enough space I don't think. Thanks!
I'm attempting to repo sync and it had failed a few times. Could this be due to lack of room on partition? I followed your guide.
Sent from my Nexus 6P using Tapatalk
jmtjr278 said:
Hey, @nathanchance I'm pretty certain you are running Ubuntu on a VM, right? If so can you share how much memory and storage you have allocated to the VM? I didn't allocate enough space I don't think. Thanks!
Click to expand...
Click to collapse
No I have a server I build on but I would say you should allocate half of your computer's memory at a minimum.
Sent from my Nexus 6P using XDA Labs
nathanchance said:
No I have a server I build on but I would say you should allocate half of your computer's memory at a minimum.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Thanks. I edited my post with another question. Could you have a peek for me please?
Sent from my Nexus 6P using Tapatalk
jmtjr278 said:
Hey, @nathanchance I'm pretty certain you are running Ubuntu on a VM, right? If so can you share how much memory and storage you have allocated to the VM? I didn't allocate enough space I don't think. Thanks!
I'm attempting to repo sync and it had failed a few times. Could this be due to lack of room on partition? I followed your guide.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I haven't been running Linux under VM for more then a year now but back then 8 GB memory allocated to VM was needed to build (I know some say 4 GB should do the trick but it never worded fine for me).
Disk space I would suggest at least 100-150 GB, If you have the space allocated 200-250GB, that will give you space for ccache and a custom kernel if you like.
jmtjr278 said:
Thanks. I edited my post with another question. Could you have a peek for me please?
Click to expand...
Click to collapse
Depends on what they are. If they are fetch errors, use this: https://android.googlesource.com/new-password
Sent from my Nexus 6P using XDA Labs
kantjer said:
I haven't been running Linux under VM for more then a year now but back then 8 GB memory allocated to VM was needed to build (I know some say 4 GB should do the trick but it never worded fine for me).
Disk space I would suggest at least 100-150 GB, If you have the space allocated 200-250GB, that will give you space for ccache and a custom kernel if you like.
Click to expand...
Click to collapse
Thanks @kantjer I have reallocated the space to 250gb and the memory to 4gb. That's the most I can use and run the VM. I will attempt repo sync again. I appreciate there help! Have been here a while and never attempted this. Wish me luck!
Sent from my Nexus 6P using Tapatalk

[REFERENCE] [3.10.105] Stock kernel with upstream Linux patches - May 9th

Introduction
Hello all, I am bringing you this thread as a jumping off point to compiling kernels and working with upstream Linux. I will include a guide, some links, and some terms that will help you get started with modifying kernel source. This is also a good reference point for existing developers as I have consolidated all upstream patches into one repo. Let's get down into it!
What in the world is upstream Linux?
When an OEM sets up a device, they will pick a stable longterm branch from the Linux kernel to base their modifications around (drivers and such). In the case of Shamu, they picked 3.10.40. Currently, the Linux kernel's 3.10 is updated to 3.10.105, as you can see on kernel.org. This means that Google is "missing" versions 3.10.41 to 3.10.105. Now, why does this matter? Well, the way that the Linux kernel runs its stable branches, the only things that get merged into there are bug fixes and security updates. That's it, there are no wonky features or unstable patches. The only way you get a patch into a stable branch is by having it be in the mainline branch first. Some developers have an aversion to adding upstream because they claim it is excessive and not necessary and they are partially right since not all the patches that come in are relevant to our architecture (arm). However, upstream Linux is not unstable and by adding each version one at a time, you can verify this. Being up to date is good since you keep yourself protected from bugs and security issues that crop up. Google has been better about doing this lately with their monthly security updates but it never hurts to take matters into your own hands.
I suggest watching one of these talks given by Greg Kroah-Hartman, it is really interesting to see how the process goes:
https://www.youtube.com/watch?v=SPY0LyTU53w | https://www.youtube.com/watch?v=L2SED6sewRw
What did you do?
All I did was fetch the latest kernel.org patches from here and cherry pick them on top of the latest kernel source from Google.
I merge these patches by cherry-picking each version individually (3.10.40 to 3.10.41, 3.10.41 to 3.10.42, etc), that way I can verify that the kernel compiles fine and that there are no merge conflicts. Google will sometimes pick certain commits from upstream that are of a higher importance than others which can result in conflicts if you try to pick it again. Additionally, upstream might fix a bug one way and Google has done it another (which is not really good, Google should be pushing their fixes back to upstream so everything stays in sync).
What do I do with this?
I have created two repos below: one with the latest N security update branch with the latest upstream patches picked up on top of it (the shamu-upstream branch) and another one with a plain AnyKernel source for you to modify (shamu-stock is the most basic, shamu-decrypt contains an fstab file that will disable both forced encryption and dm-verity). You are free to fork these or base other branches on them, that's the whole point of this post. I have verified that all the patches contain no major detectable issues. I would like some credit if you do use it but it's not required since the kernel is licensed under GPL Another reason I offer this is I have seen a lot of developers picking in upstream in patch sets, so you get one single commit for an upstream version. This is detrimental as you start to add your own patches as you cannot fully tell what was modified and for what reason without the individual commits. It might look cleaner but you don't get full history which hurts you in the long run.
Links
Kernel source: https://github.com/nathanchance/shamu/tree/upstream-7.1.1
AnyKernel source: https://github.com/nathanchance/AnyKernel2/tree/shamu-stock-decrypt
Toolchain source: https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/
How to compile
This will be a quick, step by step guide on how to compile this kernel from source. By using this process, you can start to make modifications to the kernel source and make a flashable zip.
Clone the kernel source, the AnyKernel source, and toolchain source
Code:
cd ~
mkdir Kernel && cd Kernel
git clone https://github.com/nathanchance/shamu.git source
git clone https://github.com/nathanchance/AnyKernel2.git anykernel
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8 AOSP-4.8
Explanation:
First command: make sure you are in your home directory (or whatever directory you want to hold the kernel folder we are about to make.
Second command: make a Kernel folder and move into it
Third command: clone the kernel source from my repo into a folder named source
Fourth command: clone the AnyKernel source from my repo into a folder named anykernel
Fifth command: clone the Google 4.8 toolchain into a folder named AOSP-4.8
AnyKernel is the name of the zip we are going to make which allows the kernel to be flashed over any ROM.
A toolchain is a set of compiler tools that allow us to compile the kernel on any computer architecture.
Make sure you are on the correct branches
Code:
cd source && git checkout upstream-7.1.1
cd ../anykernel && git checkout shamu-stock-decrypt
Explanation:
First command: move into the source directory and checkout the branch "upstream-7.1.1", which is the necessary branch for this device.
Second command: move into the AnyKernel directory and checkout the branch "shamu-decrypt". If you don't want to disable forced encryption, use the "shamu-stock" branch.
Tell the compiler what you are are compiling
Code:
export CROSS_COMPILE=${HOME}/Kernel/AOSP-4.8/bin/arm-eabi-
export ARCH=arm && export SUBARCH=arm
make clean && make mrproper
make shamu_defconfig
Explanation:
First command: point the compiler to the location of your toolchain. If you have done anything different with the folder locations, you will need to modify the "${HOME}/Kernel/AOSP-4.8" part.
Second command: tell the compiler which architecture we are compiling for. In this case, our device is an arm device.
Third command: clean out any compiled files and remove our previous defconfig.
Fourth command: tell the compiler which options we want in the kernel using the shamu_defconfig.
A defconfig is a file that will tell the compiler which features we want in the kernel. No computer ever uses all of the options in the kernel since there are different drivers for various devices.
Make the kernel!
Code:
make -j$(nproc --all)
Explanation:
make tells the compiler to make the kernel (duh) and the -j$(nproc --all) tells the compiler to use the maximum number of cores your computer has available
Make the AnyKernel zip
Code:
cp -v arch/arm/boot/zImage-dtb ../anykernel
cd ../anykernel
zip -r9 stock-upstream.zip * -x README stock-upstream.zip
Explanation:
First command: copies the completed kernel (zImage-dtb) into the AnyKernel folder
Second command: moves us into the AnyKernel folder
Third command: makes the zip file (named stock-upstream.zip) in the AnyKernel folder.
If you ever want to do this again, run these commands and go straight to step 3:
Code:
cd source && git clean -fxd && git pull
cd anykernel && git clean -fxd && git pull
NOTE: This thread is aimed to be a breeding ground for kernel development, a place to jump off if you will. I am happy to answer how to questions about building kernels or flashing the one I have provided but this is not supposed to be a general Q&A thread. Please use another thread or create your own in Q&A if you need assistance.
Nice write up.
One suggestion though. Instead of using the current version as the branch name, you may want to just name them for the device, like "Shamu-Upstream" then tag the versions once you've gotten to the version commit. This will prevent you from having to update the thread for this command anytime that you pull in more upstream changes. It also makes it alot cleaner/easier if someone for whatever reason wanted to checkout a specific patch version as they could just checkout the tag rather than resetting back to the commit.
For lack of a better explanation, tags are sort of like sub-branches within a branch.
Very new to kernel building and AOSP in general. Followed the guide but I'm getting stuck when make mrproper is ran. Build stops and i get the error : unknown target 'mrproper' then the build fails. Any help?
The Flash said:
Another reason I offer this is I have seen a lot of developers picking in upstream in patch sets, so you get one single commit for an upstream version. This is detrimental as you start to add your own patches as you cannot fully tell what was modified and for what reason without the individual commits. It might look cleaner but you don't get full history which hurts you in the long run.
Click to expand...
Click to collapse
That's true. Some devs are lazy to commit each patch and bring up from 3.10.40 to 3.10.103 which comprises nearly 3000 patches.
neobuddy89 said:
That's true. Some devs are lazy to commit each patch and bring up from 3.10.40 to 3.10.103 which comprises nearly 3000 patches.
Click to expand...
Click to collapse
Exactly lol. It's also annoying for people looking at your source because if you had to fix anything, it is going to be lumped in with that enormous patch.
Root Wizard said:
Very new to kernel building and AOSP in general. Followed the guide but I'm getting stuck when make mrproper is ran. Build stops and i get the error : unknown target 'mrproper' then the build fails. Any help?
Click to expand...
Click to collapse
can I see a full terminal window/log showing you entering all the commands?
The Flash said:
can I see a full terminal window/log showing you entering all the commands?
Click to expand...
Click to collapse
Just logged off for the night. Will give a full report back tomorrow with pictures. Basically all the commands go good up to 'make mrproper' . 'make clean' runs fine but the 'make mrproper' goes through incuding all the aosp files for build, then ninja enters build directory, then the error 'unknown target 'mrproper' ' comes up, and the build fails.
Root Wizard said:
Just logged off for the night. Will give a full report back tomorrow with pictures. Basically all the commands go good up to 'make mrproper' . 'make clean' runs fine but the 'make mrproper' goes through incuding all the aosp files for build, then ninja enters build directory, then the error 'unknown target 'mrproper' ' comes up, and the build fails.
Click to expand...
Click to collapse
Oh you're building this into a ROM? Alright, that might make things different but yeah show me pictures tomorrow and I'll try to get you up and running.
The Flash said:
Oh you're building this into a ROM? Alright, that might make things different but yeah show me pictures tomorrow and I'll try to get you up and running.
Click to expand...
Click to collapse
Ah I guess I should have metioned that I was building an aosp rom. Thanks for your quick assistance. Will get back tomorrow.
If you're building into a rom, you just need to change the existing kernel source to this one in the xml for this device.
Yoinx said:
If you're building into a rom, you just need to change the existing kernel source to this one in the xml for this device.
Click to expand...
Click to collapse
Can you explain how to do this? First time building with aosp, not very familiar which xml file or what to change to apply the upstream patch.
Root Wizard said:
Can you explain how to do this? First time building with aosp, not very familiar which xml file or what to change to apply the upstream patch.
Click to expand...
Click to collapse
For shamu in aosp, the kernel is pulled with the main aosp source by that manifest. https://github.com/android/platform_manifest/blob/master/default.xml#L65
You world need to substitute this repo with the new one, and delete your existing kernel source. Then next time you sync the repo tool will pull it down.
On other roms it gets pulled in during the breakfast/brunch process. I can't remember exactly where that comes from, but I think that is in the vendor directory for the device, maybe.
How to modify rom manifests and such though is a little outside of this thread's topic. If you need more info I'd recommend opening a thread in the Q&A forum unless this is something that The flash wants to cover in this thread.
There are a few other caveats with doing it in the rom as well. The defconfig name would need to match what the rom build expects and you would need to go in and checkout the correct branch.
Yoinx said:
For shamu in aosp, the kernel is pulled with the main aosp source by that manifest. https://github.com/android/platform_manifest/blob/master/default.xml#L65
You world need to substitute this repo with the new one, and delete your existing kernel source. Then next time you sync the repo tool will pull it down.
On other roms it gets pulled in during the breakfast/brunch process. I can't remember exactly where that comes from, but I think that is in the vendor directory for the device, maybe.
How to modify rom manifests and such though is a little outside of this thread's topic. If you need more info I'd recommend opening a thread in the Q&A forum unless this is something that The flash wants to cover in this thread.
There are a few other caveats with doing it in the rom as well. The defconfig name would need to match what the rom build expects and you would need to go in and checkout the correct branch.
Click to expand...
Click to collapse
Ok, thanks for your help.
For those of you who have forked my kernel, you will need to revert this patch: https://github.com/nathanchance/and...mmit/0b17006c16bba286ecc9d7bacd75a3902a26835e
It causes issues with Wi-Fi and Chrome.
The Flash said:
For those of you who have forked my kernel, you will need to revert this patch: https://github.com/nathanchance/and...mmit/0b17006c16bba286ecc9d7bacd75a3902a26835e
It causes issues with Wi-Fi and Chrome.
Click to expand...
Click to collapse
It does? I have been using Chrome Beta (on wifi) since last night fine with that patch. Maybe its just a matter of time before things start failing. Thanks anyway, will keep a heads up.
Root Wizard said:
It does? I have been using Chrome Beta (on wifi) since last night fine with that patch. Maybe its just a matter of time before things start failing. Thanks anyway, will keep a heads up.
Click to expand...
Click to collapse
If you toggle Wi-Fi, start flipping through pages in Chrome, and toggle Wi-Fi again, it will reboot. Oddest issue I have ever dealt with.
Sent from my Nexus 6P using XDA Labs
The Flash said:
If you toggle Wi-Fi, start flipping through pages in Chrome, and toggle Wi-Fi again, it will reboot. Oddest issue I have ever dealt with.
Click to expand...
Click to collapse
Interesting, will look into this. I also have been getting reboots from searching forums in xda labs app. Logcat says a ton of "PowerHAL_touch_boost failed to send: Connection refused" before reboots. Is this what is happening to you?
Root Wizard said:
Interesting, will look into this. I also have been getting reboots from searching forums in xda labs app. Logcat says a ton of "PowerHAL_touch_boost failed to send: Connection refused" before reboots. Is this what is happening to you?
Click to expand...
Click to collapse
No I haven't had that happen but that error shouldn't cause reboots.
The Flash said:
No I haven't had that happen but that error shouldn't cause reboots.
Click to expand...
Click to collapse
Huh, odd
Github and the kernel in the OP are updated to 3.10.104.

GIT 101 - Newbie Friendly

Hello,
Today I would like to share an easy git tutorial for all of you. We at XDA believe everyone loving Android and passionate about the same can contribute something or other to the community. Not everyone is an expert at everything like theming, bootanimations, building ROMs, Kernels etc etc. But git is an essential yet powerful tool in most aspects. This thread is for new users and old alike , wanting a correct direction of learning basic Android by starting with git. Okay enough of lectures? Bwahaha I know it's boring lol
So let's start
Gitlab? What exactly it is? How is it different from github?
GitLab is an application to code, test, and deploy code together. It provides Git repository management with fine grained access controls, code reviews, issue tracking, activity feeds, wikis, and continuous integration. Inshort and in simple english, it is a place to store all your sources, it maybe private, public or restricted.
Difference : GitHub is a publicly available, free service which requires all code (unless you have a paid account) be made open.GitHub currently hosts the source code for tens of thousands of open source projects. GitLab is a github like service that organizations can use to provide internal management of git repositories.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Signing up, Creating an account and setting up git
Go to gitlab web
You have an option to sign in with google, github, twitter or bitbucket. It's the easiest way. I prefer github
Now let's download the git package. I use Linux Mint 18 so,
Code:
sudo apt-get install git
Verify if it is correctly installed in your system
.
Now let's configure the terminal
Code:
git config --global user.name "Your Name Here"
git config --global user.email "[email protected]"
Now let's generate ssh keys
go to your terminal and type
Code:
ssh-keygen
and hit enter thrice I guess until you are back to bash.
Or
Code:
ssh-keygen -t rsa -C "[email protected]"
Now
Code:
cd .ssh
cat id_rsa.pub
(.pub is your public key while the other one is private key, Don't ever share private keys with anyone)
Now let's verify all that we've done so far.
Code:
git config --global --list
Now let's add ssh-keys we generated to our account at gitlabs OR we get this
Click : Add an ssh key and copy paste the ssh-key (id_rsa.pub) there and click okay.
Now let's check if everything works
Code:
ssh -T [email protected]
This warning...
Code:
The authenticity of host 'github.com (207.97.227.239)' can't be established.
# RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
# Are you sure you want to continue connecting (yes/no)?
Type YES and here we're done with configuration part
XDA:DevDB Information
GIT 101, Tool/Utility for the Samsung Galaxy Chat
Contributors
Vatsal, malybru, sawdoctor
Version Information
Status: Testing
Created 2016-12-09
Last Updated 2016-12-20
XDA:DevDB Information
GIT 101 - Newbie Friendly, ROM for the Android General
Contributors
The Arrow
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2018-04-25
Last Updated 2018-04-25
Now let's start with creating a new repo and importing it from github (If you are a previous github user and want to switch to gitlabs)
Just click new project button and you'll have this
And I click import the project with github and I choose the project I wish to import
And I have this :
Please be patient and grab some coffee?
It will import the entire project with all the branches.
And it's done..
Now let's clone the project locally to make changes. We can make the changes on web too but well it's really a mess so most people prefer CLI way.
Click the copy to clipboard button as in screenshot
and clone it locally.
Command :
Code:
git clone <Paste the URL copied> -b <branch name>
Note : the default branch is cloned with you clone with .git
Wait for it to finish and get back to bash done.
Now we have the repo locally. Now we go to the repo to check the files and edit as we wish.
First we grab the latest changes from the original repo to check if we have latest changes.
Code:
Example : the repo I am cloning is forked on my github and I imported from there to gitlabs.
The original repo is here https://github.com/CyanogenMod/android_device_xiaomi_hydrogen.
So I make sure I have the latest changes.
To get the latest changes, I use
Code:
git pull <original repo URL> <branch name>
So here, I am pulling from the CM repo I mentioned above and cm-14.1 branch.
Now I just edit something and make change so as to commit it.
So I just deleted the cm.dependencies file from the repo.
Now we
Code:
git add -A
to add the untracked changes.
A more detailed info is here
The important point about git add . is that it looks at the working tree and adds all those paths to the staged changes if they are either changed or are new and not ignored, it does not stage any 'rm' actions.
git add -u looks at all the already tracked files and stages the changes to those files if they are different or if they have been removed. It does not add any new files, it only stages changes to already tracked files.
git add -A is a handy shortcut for doing both of those.
So let's commit now by using
Code:
git commit
and we get this
Write the commit name (Any you like). Now save and exit and we have this
Now let's learn further about
Code:
git status
.
Just as the name suggests, it tell us the status of the particular repo.
It displays the path and difference between cloned repo and the orginal repo.
DESCRIPTION
Displays paths that have differences between the index file and the current HEAD commit, paths that have differences between the working tree and the index file, and paths in the working tree that are not tracked by Git (and are not ignored by gitignore[5]). The first are what you would commit by running git commit; the second and third are what you could commit by running git add before running git commit.
Now it's time to push the changes we made to the gitlabs repo.
Calm down! It is no rocket science. Infact the easiest part.
Command :
Code:
git push <URL of the repo> HEAD:<branch name>
Enter your username and password correctly.
And pushed...
And now let's check at gitlabs if it is successfully pushed.
Done :victory:
So now we learnt pull, push, status. We proceed with The most important command
Code:
cherry-pick
{Most of the people might have heard of it, and wonder what it is?}
Cherry picking in Git is designed to apply some commit from one branch into another branch, one repo into another
Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit).
When it is not obvious how to apply a change, the following happens:
The current branch and HEAD pointer stay at the last commit successfully made.
The CHERRY_PICK_HEAD ref is set to point at the commit that introduced the change that is difficult to apply.
Paths in which the change applied cleanly are updated both in the index file and in your working tree.
For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of git-merge[1]. The working tree files will include a description of the conflict bracketed by the usual conflict markers <<<<<<< and >>>>>>>.
No other modifications are made.
So I would wish to cherry-pick a particular commit on the same repo we have been working upon.
This is the commit I want to pick in my repo.
For cherry-picking, first we need to learn
Code:
git fetch
What does git fetch do?
git fetch - Download objects and refs from another repository
Command :
Code:
git fetch <URL> <Branch>
Fetch branches and/or tags (collectively, "refs") from one or more other repositories, along with the objects necessary to complete their histories. Remote-tracking branches are updated (see the description of <refspec> below for ways to control this behavior).
By default, any tag that points into the histories being fetched is also fetched; the effect is to fetch tags that point at branches that you are interested in. This default behavior can be changed by using the --tags or --no-tags options or by configuring remote.<name>.tagOpt. By using a refspec that fetches tags explicitly, you can fetch tags that do not point into branches you are interested in as well.
git fetch can fetch from either a single named repository or URL, or from several repositories at once if <group> is given and there is a remotes.<group> entry in the configuration file.
When no remote is specified, by default the origin remote will be used, unless there’s an upstream branch configured for the current branch.
So we fetch it from the AICP github with branch name n7.1
and then we cherry-pick it by using
Code:
git cherry-pick <commit ID>
and now it's cherry-picked. We have that commit in our repo.
Note : This was an easy pick but most picks aren't this easy. We will learn about fixing conflicts later on
Now we push it to gitlabs repo.
and we'll check if our gitlabs repo has it now !?
Now we learn how to create a new branch and push to that branch.
We create a new branch by
Code:
git branch <new branch name>
This creates a new branch with the new branch name specified in the command.
Now we checkout the branch to switch to that particular branch.
Command :
Code:
git checkout <branch name>
git checkout <branch>
To prepare for working on <branch>, switch to it by updating the index and the files in the working tree, and by pointing HEAD at the branch. Local modifications to the files in the working tree are kept, so that they can be committed to the <branch>.
If <branch> is not found but there does exist a tracking branch in exactly one remote (call it <remote>) with a matching name, treat as equivalent to
Code:
git checkout -b <branch> --track <remote>/<branch>
You could omit <branch>, in which case the command degenerates to "check out the current branch", which is a glorified no-op with a rather expensive side-effects to show only the tracking information, if exists, for the current branch.
Now that we have successfully cherry-picked,
we will learn to show the commits logs in terminal itself (Not GUI).
Code:
git log
can help us with that.
We can also add a flag besides it for example 'git log -3' to see the last 3 commits.
Shows the commit logs.
The command takes options applicable to the git rev-list command to control what is shown and how, and options applicable to the git diff-* commands to control how the changes each commit introduces are shown.
Now we learn how to revert a cherry-pick ?
Well it's pretty easy.
So I grab the commit ID from the commit I wish to revert.
Here's the command
Code:
git revert <commit ID>
After reverting make sure to push it to the repo to see the revert there as well
Supposing we make a change to a repo and we don't wish to commit it. Instead we wish to reset the repo to the previous state,
Here is a ways we can do it.
Code:
git stash
It discards all the local changes and gets it back to the last commit.
Also suppose if we want to revert 20 odd commits and we have force push access (And you are lazy like me ), we don't revert it one by one. Instead we can just hard reset the repo to the last commit
Command :
Code:
git reset --hard <commit ID>
This is the easiest way to do it.
Now the last one. Force pushing
Sometimes github doesnt let us push after resetting hard because the previous commits dont exist in our repo.
We can just force push to force it accept the commits
Command :
Code:
git push -f <URL name> <branch name>
It is basically a noob method to just add changes easily after a failed or unsuccessful push.
Credits
- @malybru , @sawdoctor for always being there for me.
- @eagleeyetom , @Neo , @Perseus , @Darth , @KennyG123 , @The Merovingian for a lot of things (Will fill up pages if I start writing ).
- The entire XDA Staff
- @TechExhibeo and @@jackeagle for helping me through my noob days
- Gitlab ofcourse
-GZR Team for not killing me when I asked a lot of stupid questions.
- Legacy Team for guiding me through lot of stuffs.
- Everyone, that I forgot to mention.
And this too. Moar spams incoming..
Great Help for Newbies
Thanks Vatsal Sir _/|\_
This will be very helpful for Newbies learning stuffs.
Great Work :*
-TechExhibeo
Wonderful Guide and great work @Vatsal ! This will help newbies a lot Every aspect of git is mentioned in 1 Guide Keep up the spirit sir!
Cheers!
jackeagle
Forum Moderator
Nicely written
Nias works
Well tutorial
Thanks for this Tut!
Would be my Git Reference *bookmarks*
Good work mate!
A great help to newbies
Arvind7352 said:
Thanks for this Tut!
Would be my Git Reference *bookmarks*
Click to expand...
Click to collapse
This is a little more than a tutorial, if members are having trouble learning git they can ask here and will get actuall help rather than being told to read
Sent from my SM-N930F using Tapatalk
I will be available to answer in whatever capacity I can as well. There are many of you however that are far beyond my knowledge of git though
I'm sure I'll be learning something
Thanks for such a wonderful guide
Thanks for the guide vatsal
Nice...finally got something to learn.thank @Vatsal
Neo said:
I will be available to answer in whatever capacity I can as well. There are many of you however that are far beyond my knowledge of git though [emoji14]
I'm sure I'll be learning something
Click to expand...
Click to collapse
Thanks for your support for this project. I know I speak for Malybru and vatsal as well it means a lot that you are on board [emoji106] [emoji106]
Sent from my SM-N930F using Tapatalk
Excellent resource! Kudos for this. :good::highfive:

Categories

Resources