Database Develop

[TUTORIAL]Compile Xperia Z ROM with Linaro including O3 strict-aliasing optimizations

First of all, many thanks to @trailblazerz11 for bringing full Linaro ROM to our fellow S4 Pro devices like Nexus 4 with resourceful build guide. This guide is based on his repository with my own fixes that needed to be done outside his repository. This works fine on CM10.1 and should also work on AOSP as well with manual fixes applied. As current AOSP being incompetent, I'll leave that until it actually works without relying on CM10.1 patches.
Features
1. Replace stock kernel and recovery with @jeroenqui's MEOW-kernel and TWRP recovery. (Optional)
2. Replace Google toolchains for arm/linux with Linaro 4.8 ones from Mustaavalkosta's github
3. Apply build configuration with Linaro suggested optimizations “-O3 -pipe -Wl,--hash-style=gnu -fno-tree-vectorize -fstrict-aliasing -Wstrict-aliasing=2 -Werror=strict-aliasing”
4. Fix codes breaking strict aliasing rules
5. Comes in form of automate shell script, the easiest Linaro build guide EVER
Requirements:
1. CM10.2 build environment - You can check on Build for yuga wiki for detailed instructions.
2. Oracle Java - Skip OpenJDK in wiki and install better ones from this link including adb and fastboot.
3. You need to install additional packages for compiling kernel. Type "sudo apt-get install lzop ccache" so that build kernel won't break mid-way.
4. Make sure your default compiled ROM works without trouble as I got boot problems before and thought Linaro messed it.
Instructions:
1. Open terminal and go to your Android git repository.
2. Modify local manifests for jeroenqui’s kernel and TWRP by typing “gedit .repo/local_manifests/roomservice.xml” and hit enter. Added the following lines before '</manifest>'.
Code:
<project name="Mustaavalkosta/android_prebuilts_gcc_linux-x86_arm_arm-eabi-4.8.git" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="github" revision="master"/>
<project name="Mustaavalkosta/android_prebuilts_gcc_linux-x86_arm_arm-linux-androideabi-4.8.git" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" remote="github" revision="master"/>
#Add this if you want to use MEOW-kernel (You can use others if you want at your own risk)
<remove-project name="CyanogenMod/android_kernel_sony_apq8064" />
<project name="MEOW-kernel/android_kernel_sony_apq8064" path="kernel/sony/apq8064" remote="github" />
#Add this if you want to use TWRP
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project name="TeamWin/Team-Win-Recovery-Project.git" path="bootable/recovery" remote="github" revision="twrp2.7"/>
3. Download Linaro NDK package in tar.gz format and place in Android git repository
3. Make linaro patch script by typing "gedit linaro_patch.sh" and hit enter. Put contents inside with this ones and save then exit.
Code:
#!/bin/bash
#Windows X's CM10.2 Linaro patch for Xperia Z
DIR=$(pwd)
#Linaro NDK files extraction (change 'android-ndk-r9-linaro-linux-x86_64.tar.bz2' and 'android-ndk-r9-linaro' to match what you place before)
cd $DIR
tar -vxf android-ndk-r9-linaro-linux-x86_64.tar.bz2
rm android-ndk-r9-linaro-linux-x86_64.tar.bz2
cp -f ndk/Android.mk android-ndk-r9-linaro/
cp -f ndk/CleanSpec.mk android-ndk-r9-linaro/
rm -r -f ndk
mv android-ndk-r9-linaro ndk
cd $DIR/build
git fetch https://github.com/WindowsX/android_build.git cm-10.2 && git cherry-pick ec9e3eea9cb1dc1929e45736f0608a888f97eb0f
git fetch https://github.com/WindowsX/android_build.git cm-10.2 && git cherry-pick 43ee5fdfaa404e474372072a8bd85ea613646861
git fetch https://github.com/Mustaavalkosta/android_build.git && git cherry-pick ffcaf82831783a420a5490e9894c016644e79743
cd $DIR/kernel/sony/apq8064
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick 71a48e15f0066e72b401d92afca7dd8b45efac1b
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick e748106f0ffcad5376e76b336dea287c493977dc
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick 7beb0a0de015a204745a46d03d7a1ca36775c5e8
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick bf46e6bc58141778af27bd49f0093a52df141aba
#Uncomment the following commit if you use original CM kernel
#git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick 3c8432deaaf673b3dfd0673d8000a3d068001926
#TWRP Recovery Linaro fix (Comment these out if you stick with default CWM Recovery)
cd $DIR/bootable/recovery/
git fetch https://github.com/WindowsX/Team-Win-Recovery-Project.git && git cherry-pick fc866246fe05d743ac5917ee44dbdffe1f620714
git fetch https://github.com/WindowsX/Team-Win-Recovery-Project.git && git cherry-pick 4e0cc5ba0b883413834a81d32d9501a802022053
cd $DIR/device/sony/fusion3-common
git fetch https://github.com/jeroenqui/android_device_sony_fusion3-common.git && git cherry-pick fab74e8c2faa8e2afc405b44c7233d7e32ba96dd
cd $DIR/bionic
git fetch https://github.com/WindowsX/android_bionic.git cm-10.2 && git cherry-pick f607f6c8129eb41c602451b6bfe39be6d734d799
cd $DIR/device/generic/goldfish
git fetch https://github.com/WindowsX/android_device_generic_goldfish.git cm-10.2 && git cherry-pick f21fa86fcea62580a7d1ea3e32df168628517a82
cd $DIR/external/bash
git fetch https://github.com/SaberMod/android_external_bash.git && git cherry-pick d746365ea911c73ede17ed65933237875e29d9c3
cd $DIR/external/clang
git fetch https://github.com/WindowsX/android_external_clang.git && git cherry-pick 81d67da93bd3afa9ce7f5064562ddb0c91ba0a0c
cd $DIR/external/dnsmasq/
git fetch https://github.com/trailblazerz/android_external_dnsmasq.git && git cherry-pick 446fceadb803f8c28de809907d55dfab82e9827f
cd $DIR/external/e2fsprogs/
git fetch https://github.com/trailblazerz/android_external_e2fsprogs.git && git cherry-pick 0e540a3cf8c4dd22205ef39a6f9d6edfa0d1183a
cd $DIR/external/openssh/
git fetch https://github.com/WindowsX/android_external_openssh.git cm-10.2 && git cherry-pick bddb1dd7b9d594913061cdb6b2cd8bf77d047186
cd $DIR/external/openssl/
git fetch https://github.com/trailblazerz/android_external_openssl.git && git cherry-pick b43b3c2935e8f27b74c53be2f67fe49f3a515228
cd $DIR/external/ping/
git fetch https://github.com/WindowsX/android_external_ping.git cm-10.2 && git cherry-pick 46fb65c7a1c4b8b95b7b4b78fa10a1d4139f8339
cd $DIR/external/ping6/
git fetch https://github.com/WindowsX/android_external_ping6.git cm-10.2 && git cherry-pick 5f093083b78433b6056a532b39dc7e3d83330690
cd $DIR/external/skia
git fetch https://github.com/WindowsX/android_external_skia.git cm-10.2 && git cherry-pick 8000ce63239c673aacc905aeb48e357d07aca533
cd $DIR/external/stlport/
git fetch https://github.com/trailblazerz/android_external_stlport.git && git cherry-pick 05c206e22eddf9d09b3c497721a94aa23b922811
cd $DIR/frameworks/av/
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick 8e10843ad4902943e50a7f4d23194319a78668ef
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick 5735647d6c70660d20cf16ee5346159c345ad648
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick d67b1fa60b2680e731a6683968856ef91362b1b3
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick b5973bd61fa55ec7693103036fd618234e1ae4f7
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick 2b7cd9fa973e829cc8a4842376280d01b3e9a487
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick f1a15bce88881376c6f88546b9e698cdcd19732b
cd $DIR/frameworks/base/
git fetch https://github.com/WindowsX/android_frameworks_base.git cm-10.2 && git cherry-pick 937e6f24e503ca9fa203044a584b158edcc7840f
cd $DIR/frameworks/ex/
git fetch https://github.com/trailblazerz/android_frameworks_ex.git && git cherry-pick aa5da9c8956f09072bb9e783dee2a67798663bb6
cd $DIR/frameworks/native/
git fetch https://github.com/WindowsX/android_frameworks_native.git cm-10.2 && git cherry-pick 8b555aaaceee3ff422d239596c2f132329e80d7d
cd $DIR/frameworks/opt/net/voip
git fetch https://github.com/WindowsX/android_frameworks_opt_net_voip.git cm-10.2 && git cherry-pick 33f09279eaf8577753fc855611290acd29852b94
cd $DIR/frameworks/wilhelm/
git fetch https://github.com/trailblazerz/android_frameworks_wilhelm.git && git cherry-pick 07251f657bb21080ab96093dc5275b37589bbf37
git fetch https://github.com/trailblazerz/android_frameworks_wilhelm.git && git cherry-pick 48cc6405503668dc38b4713a98e08d1174b2340c
cd $DIR/hardware/qcom/media-caf
git fetch https://github.com/WindowsX/android_hardware_qcom_media-caf.git && git cherry-pick 4d64d4a65f4c04bce4ef3e373681337b967d4fb9
cd $DIR/external/chromium
git fetch https://github.com/WindowsX/android_external_chromium.git cm-10.2 && git cherry-pick 9631db924123e44ae0170aa4c52c122928a26b3b
cd $DIR/libcore
git fetch https://github.com/trailblazerz/android_libcore.git && git cherry-pick 40617f103bf38e61c43edee4c4ecbc2ea4aaedea
cd $DIR/external/webkit/
git fetch https://github.com/trailblazerz/android_external_webkit.git && git cherry-pick bb873522bc0ed7a4aaa3552527872ece198db104
cd $DIR/external/lsof/
git fetch https://github.com/trailblazerz/android_external_lsof.git && git cherry-pick 8a0665c786f53019acbcd28dfed8a5781bc3471e
cd $DIR/external/openvpn/
git fetch https://github.com/trailblazerz/android_external_openvpn.git && git cherry-pick b2cec9e8bd24ce3340fd23473b14258d063d580d
cd $DIR/system/qcom
git fetch https://github.com/WindowsX/android_system_qcom.git cm-10.2 && git cherry-pick ea84d6aab1b5011e6ae4f9ad938733c8af3d5c5e
This will replace Google NDK with Linaro ones and patch build configuration and codes that break strict aliasing rules.
4. Make Linaro patch executable by typing "chmod a+x linaro_patch.sh" and enter.
5. Re-sync again by typing "repo sync" and enter. It will take a while for downloading new toolchains.
6. Apply Linaro patches by typing "./linaro_patch.sh" and enter. All should goes well but keep your eyes on each patch and see if there's anything failed to cherry-pick or not. Fix those failed to cherry-pick yourself and move on.
7. Reload build configuration by typing "source build/envsetup.sh" and enter.
8. Your ROM is ready be cooked with Linaro now. Build it with whatever method you prefer and enjoy.
Credits
trailblazerz11 - For his Linaro ROM for Nexus 4 and resourceful guide making Linaro Yuga implementations a lot easier.
DooMLorD - for his awesome DooMKernel tweaks. My Xperia Z won't be so lovely as today without his tweaks, seriously.
jeroenqui - for his helpful effort to port DooMKernel tweaks into CM10.1.
TeamWin - for awesome recovery system.
Mustaavalkosta - For his 4.8 toolchains and commits
And don't forget to press thanks if you find this tutorial helpful

Hey mate, awesome to see that you made it eventually! Respect, nice job done!
Thanks a lot for the guide!

UPDATE #1: CM10.1 has changed build configuration to use qcom_media-caf instead so I fixed instructions and change stuff for default CM10.1 environment.

Updated #2: Added Linaro cortex string handling routines optimizations and fuse fix and change twrp to version 2.6.

Updated #3: Fixed TWRP's duplicated fuse model with CM10.1.2 and cherry-pick failed in linux-perf-tools with OS X 10.9 fixes. You can use this to on CM10.1.2 without trouble now.

Updated #4: Fixed TWRP 2.6 being gone and cherry picking cortex string optimizations from different branch.

It took me a while as things keep changing back and forth with CM10.2. Since CM10.2 has tons of bionic optimizations, I decided to leave cortex string optimizations for time being and added latest 4.8 toolchains for arm/linux and its own NDK. TWRP and jeroenqui's kernel are included as usual.

JESUS
Windows X said:
First of all, many thanks to @trailblazerz11 for bringing full Linaro ROM to our fellow S4 Pro devices like Nexus 4 with resourceful build guide. This guide is based on his repository with my own fixes that needed to be done outside his repository. This works fine on CM10.1 and should also work on AOSP as well with manual fixes applied. As current AOSP being incompetent, I'll leave that until it actually works without relying on CM10.1 patches.
Features
1. Replace stock kernel and recovery with @jeroenqui's MEOW-kernel and TWRP recovery. (Optional)
2. Replace Google toolchains for arm/linux with Linaro 4.8 ones from Mustaavalkosta's github
3. Apply build configuration with Linaro suggested optimizations “-O3 -pipe -Wl,--hash-style=gnu -fno-tree-vectorize -fstrict-aliasing -Wstrict-aliasing=2 -Werror=strict-aliasing”
4. Fix codes breaking strict aliasing rules
5. Comes in form of automate shell script, the easiest Linaro build guide EVER
Requirements:
1. CM10.2 build environment - You can check on Build for yuga wiki for detailed instructions.
2. Oracle Java - Skip OpenJDK in wiki and install better ones from this link including adb and fastboot.
3. You need to install additional packages for compiling kernel. Type "sudo apt-get install lzop ccache" so that build kernel won't break mid-way.
4. Make sure your default compiled ROM works without trouble as I got boot problems before and thought Linaro messed it.
Instructions:
1. Open terminal and go to your Android git repository.
2. Modify local manifests for jeroenqui’s kernel and TWRP by typing “gedit .repo/local_manifests/roomservice.xml” and hit enter. Added the following lines before '</manifest>'.
Code:
<project name="Mustaavalkosta/android_prebuilts_gcc_linux-x86_arm_arm-eabi-4.8.git" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="github" revision="master"/>
<project name="Mustaavalkosta/android_prebuilts_gcc_linux-x86_arm_arm-linux-androideabi-4.8.git" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" remote="github" revision="master"/>
#Add this if you want to use MEOW-kernel (You can use others if you want at your own risk)
<remove-project name="CyanogenMod/android_kernel_sony_apq8064" />
<project name="MEOW-kernel/android_kernel_sony_apq8064" path="kernel/sony/apq8064" remote="github" />
#Add this if you want to use TWRP
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project name="TeamWin/Team-Win-Recovery-Project.git" path="bootable/recovery" remote="github" revision="twrp2.7"/>
3. Download Linaro NDK package in tar.gz format and place in Android git repository
3. Make linaro patch script by typing "gedit linaro_patch.sh" and hit enter. Put contents inside with this ones and save then exit.
Code:
#!/bin/bash
#Windows X's CM10.2 Linaro patch for Xperia Z
DIR=$(pwd)
#Linaro NDK files extraction (change 'android-ndk-r9-linaro-linux-x86_64.tar.bz2' and 'android-ndk-r9-linaro' to match what you place before)
cd $DIR
tar -vxf android-ndk-r9-linaro-linux-x86_64.tar.bz2
rm android-ndk-r9-linaro-linux-x86_64.tar.bz2
cp -f ndk/Android.mk android-ndk-r9-linaro/
cp -f ndk/CleanSpec.mk android-ndk-r9-linaro/
rm -r -f ndk
mv android-ndk-r9-linaro ndk
cd $DIR/build
git fetch https://github.com/WindowsX/android_build.git cm-10.2 && git cherry-pick ec9e3eea9cb1dc1929e45736f0608a888f97eb0f
git fetch https://github.com/WindowsX/android_build.git cm-10.2 && git cherry-pick 43ee5fdfaa404e474372072a8bd85ea613646861
git fetch https://github.com/Mustaavalkosta/android_build.git && git cherry-pick ffcaf82831783a420a5490e9894c016644e79743
cd $DIR/kernel/sony/apq8064
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick 71a48e15f0066e72b401d92afca7dd8b45efac1b
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick e748106f0ffcad5376e76b336dea287c493977dc
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick 7beb0a0de015a204745a46d03d7a1ca36775c5e8
git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick bf46e6bc58141778af27bd49f0093a52df141aba
#Uncomment the following commit if you use original CM kernel
#git fetch https://github.com/WindowsX/android_kernel_sony_apq8064.git cm-10.2 && git cherry-pick 3c8432deaaf673b3dfd0673d8000a3d068001926
#TWRP Recovery Linaro fix (Comment these out if you stick with default CWM Recovery)
cd $DIR/bootable/recovery/
git fetch https://github.com/WindowsX/Team-Win-Recovery-Project.git && git cherry-pick fc866246fe05d743ac5917ee44dbdffe1f620714
git fetch https://github.com/WindowsX/Team-Win-Recovery-Project.git && git cherry-pick 4e0cc5ba0b883413834a81d32d9501a802022053
cd $DIR/device/sony/fusion3-common
git fetch https://github.com/jeroenqui/android_device_sony_fusion3-common.git && git cherry-pick fab74e8c2faa8e2afc405b44c7233d7e32ba96dd
cd $DIR/bionic
git fetch https://github.com/WindowsX/android_bionic.git cm-10.2 && git cherry-pick f607f6c8129eb41c602451b6bfe39be6d734d799
cd $DIR/device/generic/goldfish
git fetch https://github.com/WindowsX/android_device_generic_goldfish.git cm-10.2 && git cherry-pick f21fa86fcea62580a7d1ea3e32df168628517a82
cd $DIR/external/bash
git fetch https://github.com/SaberMod/android_external_bash.git && git cherry-pick d746365ea911c73ede17ed65933237875e29d9c3
cd $DIR/external/clang
git fetch https://github.com/WindowsX/android_external_clang.git && git cherry-pick 81d67da93bd3afa9ce7f5064562ddb0c91ba0a0c
cd $DIR/external/dnsmasq/
git fetch https://github.com/trailblazerz/android_external_dnsmasq.git && git cherry-pick 446fceadb803f8c28de809907d55dfab82e9827f
cd $DIR/external/e2fsprogs/
git fetch https://github.com/trailblazerz/android_external_e2fsprogs.git && git cherry-pick 0e540a3cf8c4dd22205ef39a6f9d6edfa0d1183a
cd $DIR/external/openssh/
git fetch https://github.com/WindowsX/android_external_openssh.git cm-10.2 && git cherry-pick bddb1dd7b9d594913061cdb6b2cd8bf77d047186
cd $DIR/external/openssl/
git fetch https://github.com/trailblazerz/android_external_openssl.git && git cherry-pick b43b3c2935e8f27b74c53be2f67fe49f3a515228
cd $DIR/external/ping/
git fetch https://github.com/WindowsX/android_external_ping.git cm-10.2 && git cherry-pick 46fb65c7a1c4b8b95b7b4b78fa10a1d4139f8339
cd $DIR/external/ping6/
git fetch https://github.com/WindowsX/android_external_ping6.git cm-10.2 && git cherry-pick 5f093083b78433b6056a532b39dc7e3d83330690
cd $DIR/external/skia
git fetch https://github.com/WindowsX/android_external_skia.git cm-10.2 && git cherry-pick 8000ce63239c673aacc905aeb48e357d07aca533
cd $DIR/external/stlport/
git fetch https://github.com/trailblazerz/android_external_stlport.git && git cherry-pick 05c206e22eddf9d09b3c497721a94aa23b922811
cd $DIR/frameworks/av/
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick 8e10843ad4902943e50a7f4d23194319a78668ef
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick 5735647d6c70660d20cf16ee5346159c345ad648
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick d67b1fa60b2680e731a6683968856ef91362b1b3
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick b5973bd61fa55ec7693103036fd618234e1ae4f7
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick 2b7cd9fa973e829cc8a4842376280d01b3e9a487
git fetch https://github.com/WindowsX/android_frameworks_av.git cm-10.2 && git cherry-pick f1a15bce88881376c6f88546b9e698cdcd19732b
cd $DIR/frameworks/base/
git fetch https://github.com/WindowsX/android_frameworks_base.git cm-10.2 && git cherry-pick 937e6f24e503ca9fa203044a584b158edcc7840f
cd $DIR/frameworks/ex/
git fetch https://github.com/trailblazerz/android_frameworks_ex.git && git cherry-pick aa5da9c8956f09072bb9e783dee2a67798663bb6
cd $DIR/frameworks/native/
git fetch https://github.com/WindowsX/android_frameworks_native.git cm-10.2 && git cherry-pick 8b555aaaceee3ff422d239596c2f132329e80d7d
cd $DIR/frameworks/opt/net/voip
git fetch https://github.com/WindowsX/android_frameworks_opt_net_voip.git cm-10.2 && git cherry-pick 33f09279eaf8577753fc855611290acd29852b94
cd $DIR/frameworks/wilhelm/
git fetch https://github.com/trailblazerz/android_frameworks_wilhelm.git && git cherry-pick 07251f657bb21080ab96093dc5275b37589bbf37
git fetch https://github.com/trailblazerz/android_frameworks_wilhelm.git && git cherry-pick 48cc6405503668dc38b4713a98e08d1174b2340c
cd $DIR/hardware/qcom/media-caf
git fetch https://github.com/WindowsX/android_hardware_qcom_media-caf.git && git cherry-pick 4d64d4a65f4c04bce4ef3e373681337b967d4fb9
cd $DIR/external/chromium
git fetch https://github.com/WindowsX/android_external_chromium.git cm-10.2 && git cherry-pick 9631db924123e44ae0170aa4c52c122928a26b3b
cd $DIR/libcore
git fetch https://github.com/trailblazerz/android_libcore.git && git cherry-pick 40617f103bf38e61c43edee4c4ecbc2ea4aaedea
cd $DIR/external/webkit/
git fetch https://github.com/trailblazerz/android_external_webkit.git && git cherry-pick bb873522bc0ed7a4aaa3552527872ece198db104
cd $DIR/external/lsof/
git fetch https://github.com/trailblazerz/android_external_lsof.git && git cherry-pick 8a0665c786f53019acbcd28dfed8a5781bc3471e
cd $DIR/external/openvpn/
git fetch https://github.com/trailblazerz/android_external_openvpn.git && git cherry-pick b2cec9e8bd24ce3340fd23473b14258d063d580d
cd $DIR/system/qcom
git fetch https://github.com/WindowsX/android_system_qcom.git cm-10.2 && git cherry-pick ea84d6aab1b5011e6ae4f9ad938733c8af3d5c5e
This will replace Google NDK with Linaro ones and patch build configuration and codes that break strict aliasing rules.
4. Make Linaro patch executable by typing "chmod a+x linaro_patch.sh" and enter.
5. Re-sync again by typing "repo sync" and enter. It will take a while for downloading new toolchains.
6. Apply Linaro patches by typing "./linaro_patch.sh" and enter. All should goes well but keep your eyes on each patch and see if there's anything failed to cherry-pick or not. Fix those failed to cherry-pick yourself and move on.
7. Reload build configuration by typing "source build/envsetup.sh" and enter.
8. Your ROM is ready be cooked with Linaro now. Build it with whatever method you prefer and enjoy.
Credits
trailblazerz11 - For his Linaro ROM for Nexus 4 and resourceful guide making Linaro Yuga implementations a lot easier.
DooMLorD - for his awesome DooMKernel tweaks. My Xperia Z won't be so lovely as today without his tweaks, seriously.
jeroenqui - for his helpful effort to port DooMKernel tweaks into CM10.1.
TeamWin - for awesome recovery system.
Mustaavalkosta - For his 4.8 toolchains and commits
And don't forget to press thanks if you find this tutorial helpful
Click to expand...
Click to collapse
I was surfing around Google and accidentally found this tutorial.
YOU ROCK!!!
I was looking to enable strict-aliasing to my custom ROM!
Although my device is using Exynos processor, I'll let you know how it all goes
NICE WORK
Btw, your kernel seems to NOT using strict-aliasing. In Makefile, the -fno-strict-aliasing option is given, resulting in strict-aliasing disabled completely.
Ps2. please give a flto option a try and... please write down the tutorial similar to this one...

You're right. I forgot to remove it. How silly of me

@Windows X will there be a cm11 guide for this, looking forward for it =D

CM11 is yet to be stable enough to make this guide. Maybe sometimes after Sony releasing 4.4 ROM and CM kernel gets 4.4 blobs updated.

Windows X said:
CM11 is yet to be stable enough to make this guide. Maybe sometimes after Sony releasing 4.4 ROM and CM kernel gets 4.4 blobs updated.
Click to expand...
Click to collapse
Alright, thank you so much for replying!

[ROM][4.3.1] AOKP :: jb-mr2 :: nightlies | test builds :: yuga {Z}

DISCLAIMER
You need to have an unlocked bootloader to use this ROM & kernel. Also I or any contributor in the software DOES NOT take responsibility of damages caused to your phone due to this ROM.
{
"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"
}
1. Copy ROM zip and gapps zip to sdcard
2. Flash any kernel which has recovery (if you do not have any recovery yet)
3. Reboot device and go to recovery by pressing Vol-UP when LED is pink
4. If coming from 4.2 or 4.1 ROM wipedata/factory reset your phone
5. Flash ROM zip
6. Flash Gapps zip
7. Reboot and enjoy.
Official Nightlies (automatically built every 3 days on AOKP buildbox) :
http://aokp.co/devices/yuga
Unofficial Test Builds (will contain experimental changes for testing) :
http://aokp.co/unofficial-builds#odin
Gapps :
http://goo.im/gapps/gapps-jb-20130813-signed.zip
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.
Donate to AOKP
Donate to CyanogenMod
Every donation is cherished and loved.
If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
Latest merges on Gerrit
http://gerrit.aokp.co/#/q/sony+status:merged,n,z
Check out the ROM source on github. Open source, in the spirit of community kangage.
CREDITS
I cannot thank more for the hard work of FreeXperia Team (Jerpelea ( @FXP ), @Bin4ry, @Kali-, @Entropy512, @codeworkx and others) for working on Xperia devices.
Also huge thanks to Sony Mobile AB for having been very developer-friendly and helping us in all sorts of ways.
XDA:DevDB Information
[ROM][4.3.1] AOKP :: jb-mr2 :: nightlies | test builds :: yuga {Z}, a ROM for the Sony Xperia Z
Contributors
championswimmer, @FXP, @Bin4ry, @Kali-, @Entropy512, @cdesai, @codeworkx
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Alpha
Created 2013-09-18
Last Updated 2013-10-12

Reserved

Reserved

AWESOME!
Sent from my C6603 using xda premium

Very Very Good!
For the first build divine
With the build 2013-09-16 I found three bugs:
* Android Keyboard crashes after use the swype function
* the battery indicator updated first at 70%. Previously the indicator shows ever 100%. It's just the indicator in the status bar.
* If I start the Settings => Device Options the Settings will crashed
I will test the new build and will give you then feedback if the bugs are fix or not.
Can I make a mirror for the new build by uploaded and or or Google Drive?

Any feedback on this early version? It may make me think about unlocking my BL...

Yes, read my post!

@championswimmer:
How do you build the build?
When I type:
.build/envsetup.sh && brunch yuga
I become the follow erorr:
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/quincyatt/vendorsetup.sh
including device/samsung/toroplus/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/aokp/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/aokp/vendorsetup.sh
build/core/product_config.mk:205: *** No matches for product "aokp_yuga". Stop.
** Don't have a product spec for: 'aokp_yuga'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Can you help me?

heubergen said:
@championswimmer:
How do you build the build?
When I type:
.build/envsetup.sh && brunch yuga
I become the follow erorr:
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/quincyatt/vendorsetup.sh
including device/samsung/toroplus/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/aokp/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/aokp/vendorsetup.sh
build/core/product_config.mk:205: *** No matches for product "aokp_yuga". Stop.
** Don't have a product spec for: 'aokp_yuga'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Can you help me?
Click to expand...
Click to collapse
repo init -g all,-notdefault,yuga,sony

Thanks for the answer, but I become the same error
After 3 hours or something I destroy my aokp/.repo
When I do report sync it gives me the error
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
fatal: no revision for project AOKP/device_sony_common within /Volumes/android/aokp/.repo/manifest.xml
Can you help me, please?

heubergen said:
Thanks for the answer, but I become the same error
After 3 hours or something I destroy my aokp/.repo
When I do report sync it gives me the error
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
warning: local_manifest.xml is deprecated; put local manifests in `/Volumes/android/aokp/.repo/local_manifests` instead
fatal: no revision for project AOKP/device_sony_common within /Volumes/android/aokp/.repo/manifest.xml
Can you help me, please?
Click to expand...
Click to collapse
you need to remove your local_manifest.xml file

new build up
camera fixed

I've successfully built my own version . Thanks for your work.
But my recovery seems not working right. I only get an black screen but I can adb into it and see it booted up. Any idea what could be the problem?
Update:
I found the problem. Recovery is missing "/sbin/minivold" because the AOKPs vold does not provide it.
The missing commit is here:
https://github.com/CyanogenMod/android_system_vold/commit/aa564abda8315ea523180785d0f7e9bf552f8583

@djselbeck:
Do you use for the build the command:
. build/envsetup.sh && brunch yuga?
@championswimmer:
Thanks.

heubergen said:
@djselbeck:
Do you use for the build the command:
. build/envsetup.sh && brunch yuga?
@championswimmer:
Thanks.
Click to expand...
Click to collapse
Code:
source build/envsetup.sh
brunch yuga
is my build command.

Thanks!
Have you never see the follow error or you now what are the mistake?
build/core/product_config.mk:205: *** No matches for product "aokp_yuga". Stop.
** Don't have a product spec for: 'aokp_yuga'
** Do you have the right repo manifest?
I try allways a never found a solution.
Which repo init commond do you use?

I use the repo init a few posts above.

Do you use:
repo init -u git://github.com/AOKP/platform_manifest.git -g all,-notdefault,yuga,sony
Because, by me that command gives me a error called:
...
* [new tag] jb-mr1_milestone-2 -> jb-mr1_milestone-2
error: revision refs/heads/master in manifests not found

First I did
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr2
repo sync -j4
after it finished I did:
Code:
repo init -g all,-notdefault,yuga,sony
repo sync -j4

I think I start new and give then a new feedback.

[Dev][Rom][Kitkat][LiteStalk - 4.405] Nightlies - The Legacy Optimised

{
"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 m proud to present LiteStalk rom created by me and @Saki3d
LiteStalk is derived From idea To Make something which "Slim , as well as Fast and most imp Less space consuming"
it is an attempt to create something useful to users
its like "for the users :: to the users "
Features List :
Cyanogenmod Based
removed useless stuffs to make rom clean
Optimisations overall in framework
Removed ART - semc 2011 only
The Team Bro :
[* @Saki3d - Rom maintainer :: Buildbox :: typical gentleman
@officiallysonyrebel :: Rom maintainer :: typical troller loves android
and YOU :good: :: rom creator / user / everything
​
Rom SIggie :
http://forum.xda-developers.com/showpost.php?p=47907554&postcount=8242
thanks to
* @mikeioannina - we all know why
* @Freaky25 - for rom banner
* @Recognized Noob - Rom Siggie
* @DomusX10
XDA:DevDB Information
LiteStalk, a ROM for the Sony Ericsson Xperia Arc
Contributors
officiallysonyrebel, saki3d, androidarmv6 , scott.hart.bti
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2013-12-05
Last Updated 2013-12-05

Downloads
-LiteStalk-4.405-anzu - 06/12/2013
LiteStalk-4.405-anzu
ChangeLog LiteStalk 4.405 :
Latest Cm changes till today
bumped version to 4.405
Removed every usless thing
optimised framework for legacy devices
--- Device Specific ----
Latest Changes by mike
revert to old volume id method for know
Important Info
WE NEED YOUR HELP!
NEW!!! BUG Tracker
If you want to help fixing those bugs, please report the bugs in the bug tracker. Thanks!
Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.
Sources
Rom :- Github.com/SlimKang
Kernel : Kernel Source
Link to Lx Thread :- http://forum.xda-developers.com/showthread.php?p=47895754#post47895754
How To Build LiteStalk
Initialize the LiteStalk source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system
repo init -u git://github.com/SlimKang/android.git -b cm-11.0
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.github.com/LegacyXperia/local_manifests/cm-11.0/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-11.0/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Get the prebuilts
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
Setup the environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast device
Build the ROM (takes long time)
Code:
brunch device

This is what I call "Taking care of customers" :highfive::highfive:
This project it's wonderful.
As I wrote, I prefer that test it well and calmly before releasing it.
I'm not in a hurry (although I admit that I'm dying) because I prefer things tested, rather than made ​​in a hurry. You have all time that you need to release this ROM, that for me, it will be a dream come true.
Light Kit Kat, optimized and customizable the right, without useless system apps or thing.
I stay in touch and follow the development of things. :good::good:
I wish you good job. :fingers-crossed::fingers-crossed:
EDIT: I made this in attachment for you:

Waiting for first release
Any ScreenShots?

i m closing this thread until i will upload rom then will re-pen thread.... i have created this thread cause later maybe i will not get time for making thread

officiallysonyrebel said:
can u convert it in rle ...?? of these sizes
1. 320 x480
2. 480 x 854
i will make it boot logo
Click to expand...
Click to collapse
Here I'm! Let me know if are good.

DomusX10 said:
Here I'm! Let me know if are good.
Click to expand...
Click to collapse
great i will test them ... out:highfive:

thread reopened :silly:
Builds for All supported devices will be availble in 2-5 hours

waiting... excited

@officiallysonyrebel
The download link is dead, please fix.
Looks great btw

ArnisHoti said:
waiting... excited
Click to expand...
Click to collapse
wait is over
Dr.SAM88 said:
@officiallysonyrebel
The download link is dead, please fix.
Looks great btw
Click to expand...
Click to collapse
fixed!
thanks
- rebelos

Dr.SAM88 said:
@officiallysonyrebel
The download link is dead, please fix.
Looks great btw
Click to expand...
Click to collapse
Yea its true.
Please give us some screenshots
edit: Heh now download link working

Lite Gapps?? is it included in the zip?

officiallysonyrebel said:
thread reopened :silly:
Builds for All supported devices will be availble in 2-5 hours
Click to expand...
Click to collapse
coming for hallon??

kachrukamble said:
Lite Gapps?? is it included in the zip?
Click to expand...
Click to collapse
lite one
mido_fedo said:
coming for hallon??
Click to expand...
Click to collapse
yes ..

tnx for work.
kernel does not have logo, and rom is not booting.

bane.twit said:
tnx for work.
kernel does not have logo, and rom is not booting.
Click to expand...
Click to collapse
FTW..??? try gain

officiallysonyrebel said:
FTW..??? try gain
Click to expand...
Click to collapse
DarkKernel for 4.4 not Work i Flash Kernel inside zip and Report.

Schneiderle said:
DarkKernel for 4.4 not Work i Flash Kernel inside zip and Report.
Click to expand...
Click to collapse
yes that will be great

officiallysonyrebel said:
yes that will be great
Click to expand...
Click to collapse
Kernel Logo ?

[ROM][5.0.2][N5110][Nightlies] Omni-Rom Official

{
"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"
}
What is Omni Rom?
A new Android custom rom has been announced at the BABBQ (Big Android BBQ) by @XpLoDWilD, @Chainfire, @Dees_Troy & Team. For more information go to omni rom's site: http://omnirom.org/
Root has not been merged into OmniRom yet, so please flash the Super SU zip in recovery if you want root. FYI, only unofficial builds include the experimental and unfinished Multi-Window feature.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* cyber warfare, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device.
* If you dont like this rom, Stay away from this thread!
*/
Download Links:
GAPPS
Super SU
CWM 6.0.4.4 w/ swipe - Heimdall
TWRP 2.6.3.0 touch recovery w/ working AROMA touch (N5110)
Nightlies
How To Flash Coming From New Rom:
Download ROM, Gapps, SuperSU
Reboot into Recovery (have only tested TWRP)
Wipe / Factory Reset
Install Omni Rom
Install GApps
Install SuperSu (Optional)
Wipe Cache and Dalvik
Reboot and Enjoy
How To Flash Updates:
Install OmniRom
Install GApps
Install SuperSu (Optional)
Wipe Cache and Dalvik
Reboot and Enjoy
If you are coming from earlier Omni builds no wipe SHOULD be required. If you happen to experience random force closes, reboot and do a wipe.
Bugs:
Same as CM
Rotation is wonky. - Fixed Dec. 15th
Recent apps thumbnails are sideways. - Fixed Dec. 15th
Front camera freezes (some models?) - Fixed Feb. 9th
You tell me!
Screenshots:
Credits
Code:
OmniRom for their sources and building guides
@titanshadow for helping me with questions
@sbrissen for his CM device tree
@nickdollahz for TWRP
xplodwild for the multi-window feature
Paranoid Android for their Gapps
Chainfire for SuperSU
Sources:
Device Tree
Kernel
My GitHub
XDA:DevDB Information
Omni-Rom Official, ROM for the Samsung Galaxy Note 8.0
Contributors
ryukiri
Source Code: https://github.com/omnirom
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Alpha
Created 2013-12-14
Last Updated 2015-03-03

How to Build this ROM with MultiWIndow
1) Setup Your Computer
Stop at
Code:
$ mkdir ~/android
$ cd ~/android
2) Download Source and Compile!
Code:
$ mkdir Omni4.4
$ cd Omni4.4
$ repo init -u git://github.com/omnirom/android.git -b android-4.4
$ mkdir .repo/local_manifests
$ curl https://gist.github.com/ryukiri/8309070 > .repo/local_manifests/local_manifest.xml
$ repo sync
$ cd frameworks/base
$ git fetch https://gerrit.omnirom.org/android_frameworks_base refs/changes/10/1510/17 && git cherry-pick FETCH_HEAD
$ cd ../..
$ . build/envsetup.sh
$ brunch n5110
3) Wait till it finishes and grab the zip from the out directory.
*Note: Syncing the repo will take a long time (downloads about 15 gbs of source), depending on your internet speed.
**You shouldn't get any cherry-pick conflicts when adding in multi-window. If you do, simply resolve them or wait for a fix.

N5100:
ROM for N5100 has been moved to here. Thanks to @xpipa for testing the initial release and confirming that it works.

****************** All links below this are UNOFFICIAL builds ******************
Dec. 13th, 2014 ROM
Changes:
-Initial Release
-Multi-window PatchSet 12
-Android 4.4.2
Dec. 15th, 2014 ROM
Changes:
-Multi-window PatchSet 13
-Fixed rotation
-Fixed recent apps thumbnails
-Fixed Screenshot
-Upstream Omni Sync
Jan 2nd, 2014 ROM
Changes:
-Multi-window PatchSet 15
-Custom button actions is back in settings
-Upstream Omni Sync
Jan 23th, 2014 ROM
Changes:
-Multi-window PatchSet 21 (currently undergoing some concept changes may be a bit unstable for now)
-Upstream Omni Sync
Jan 24th, 2014 ROM
Changes:
-Multi-window PatchSet 18 (reverted back to a more stable patchset...use the build from Jan 23rd if you feel adventurous)
-Upstream Omni Sync
Feb 3rd, 2014 ROM
Changes:
-Multi-window PatchSet 18
-Upstream Omni Sync (includes new OmniSwitch)
Feb 11th, 2014 ROM
Changes:
-Multi-window PatchSet 18
-Upstream Omni Sync
-Fully working camera
March 2nd, 2015
Changes:
-Initial Lollipop unofficial release
-Upstream Omni Sync

If You want i can test on my n5100 can you add me on g+ https://plus.google.com/+PietroPassarini I'm interesting in multiwindow support
Sent from my GT-N5100 using XDA Premium 4 mobile app

I can test this rom. At least I can test if all the basic stuff are working. Will report back shortly, downloading this right now.

I can't flash this... Keep on getting can't open zip error. Downloaded multiple times. Also the link to the zip is not linked properly
Sent from my GT-N5110 using Tapatalk

I got the same problem

Bliger241 said:
I can't flash this... Keep on getting can't open zip error. Downloaded multiple times. Also the link to the zip is not linked properly
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Sorry about that, should be fixed now.

It works fine, I just came up with the screen rotation glitch, the same bug that the CM 11.0 for GT-N5110 had before (has been fixed). I haven't came up with anything else yet.

AddiKTi said:
It works fine, I just came up with the screen rotation glitch, the same bug that the CM 11.0 for GT-N5110 had before (has been fixed). I haven't came up with anything else yet.
Click to expand...
Click to collapse
I don't really have anything to add, IR blaster works, s pen works, multiwindow has some problems but it's in beta
Sent from my Nexus 5 using Tapatalk
Edit: active display is borked and constantly fc settings and freezes the system

AddiKTi said:
It works fine, I just came up with the screen rotation glitch, the same bug that the CM 11.0 for GT-N5110 had before (has been fixed). I haven't came up with anything else yet.
Click to expand...
Click to collapse
I think the rotation glitch is in the frameworks, not the device tree.. so give it some time and it should be fixed. Since its a relatively minor issue, I'll work on getting us official support first before I go see what exactly is wrong with the rotation.
Bliger241 said:
I don't really have anything to add, IR blaster works, s pen works, multiwindow has some problems but it's in beta
Sent from my Nexus 5 using Tapatalk
Edit: active display is borked and constantly fc settings and freezes the system
Click to expand...
Click to collapse
Hmm, did you do a clean flash? I'm using active display and it looks fine to me. Nothing unusual is going on.

I'm getting Error status 7.
Sent from my SM-N9005 using Tapatalk HD

abax44 said:
I'm getting Error status 7.
Sent from my SM-N9005 using Tapatalk HD
Click to expand...
Click to collapse
Change recovery first post
POWER BY REBEL ROM NOTE8

I install on my n5100. Call is ok, multi windows is OK, there is tree bug the first you know is the position of the screen if I click recent applications, the second if I made a screenshot tell me he can't write it on memory ( but external is OK ) the third is same problem I have with cm11 the last icon in the dock on the right desapear if I reboot the system.
Sent from my GT-N5100 using XDA Premium 4 mobile app

albertmurcia said:
Change recovery first post
POWER BY REBEL ROM NOTE8
Click to expand...
Click to collapse
First post? How am I not seeing it still?
Sent from my SM-N9005 using Tapatalk HD

abax44 said:
First post? How am I not seeing it still?
Sent from my SM-N9005 using Tapatalk HD
Click to expand...
Click to collapse
Try one of these:
If you have a N5100 you need the N5100 recovery, which is twrp2.6.3.0.TOUCHDRIVERSFIXED.zip
If you have a N5110 you need the N5110 recovery, which is twrp2.6.3.0.TOUCHDRIVERSFIXED-N5110.zip

New build is up with bug fixes.

I am using this rom and it is all working fine. The previous bugs was fixed (thanks!) but I still have the rotation glitch when locking the screen.
When pressing the lock button, the screen rotates and gets locked. It is really fast, but I can see. Other bug I have it is when I try to uninstall a app using the tablet in landscape mode, I get this:
The icon for uninstall and info appears to be cuted.
Thanks for your work!
Sent from my GT-N5110 using xda app-developers app

Fuhrmanns said:
I am using this rom and it is all working fine. The previous bugs was fixed (thanks!) but I still have the rotation glitch when locking the screen.
When pressing the lock button, the screen rotates and gets locked. It is really fast, but I can see. Other bug I have it is when I try to uninstall a app using the tablet in landscape mode, I get this:
The icon for uninstall and info appears to be cuted.
Thanks for your work!
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
The homescreen bugs, ie the 7th Dock icon missing and cut off stuff is a Google experience launcher bug, not anything that can be fixed until Google releases and updated Google search apk
Sent from my GT-N5110 using Tapatalk

[GUIDE] Using Gerrit code review

Purposes of this guide​This guide want to be a how-to use Gerrit, allowing everyone to contribute on AOSP like projects.
Divided in 3 parts:
Now few important stuff needs to be setup before proceeding- -> Minimal setup to use Gerrit.
How to setup & submit for recurent contributes
How to submit patches one time
Here we will setup clones, outside of the build tree. See faq for commit testing.
This mean you do not need build environement to contribute
Important: for projects using Gerrit, Github pull request will never be merged! This also mean you do not need to create a Github fork for every changed projects :victory:
So firstly, I'll explain few terms that are important for you to learn before going towards a bit tricky side. ​
Git - To be precise, git is a code-sharing website/software that allows you to share your project resources you can 'Make Software, better, together'(That's what the tag line says )!
Now, before I go to gerrit, read this: Major Open Source Projects, like, CyanogenMod, AOKP, OmniROM etc. don't directly accept pull requests and in case you want to make a change in their source for a fix/feature or anything, you need to send them patches over gerrit which are then reviewed by the trusted members of the community and if they find it valuable enough, gets merged into the git repository!
Gerrit(Copying the definition from Wiki) - Gerrit is a free, web-based team software code review tool. Software developers in a team can review each other's modifications on their source code using a Web browser and approve or reject those changes. It integrates closely with Git, a distributed version control system.
So, now, git and gerrit are so closely related, that a patch verified over gerrit can directly be merged on git without much hassel, also please note that your gerrit and git username must be same.
Pull Requests - Pull requests are sent over Git after you fork a repository, make some changes into it and then want the owner to merge those changes into his repository, and that's how community development and Open Source works.
Patches - In simple terms, any changes you make to repos of Open Source Projects like LineageOS, OmniRom or AOKP and send them over gerrit for code review are called Patches.
You can find the Gerrit URL of the project you are working on, on the contribute webpage of the project. Example: OmniRom gerrit is https://gerrit.omnirom.org/ , LineageOS is https://review.lineageos.org/
How GERRIT works?! ​Now, Gerrit is deployed in place of this central repository and adds an additional concept, a store of pending changes. Everyone still fetches from the authoritative repository but instead of pushing back to it, they push to this pending changes location. A change can only be submitted into the authoritative repository and become an accepted part of the project once the change has been reviewed and approved.
I found a nice diagram explaining this over the internet that will clear your doubts(if any ) -
{
"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"
}
There is two different way to use gerrit:
With git , on your computer (useful for recurrent contribute)
Using the Gerrit WebUI (useful for punctual contribute)
Now few important stuff needs to be setup before proceeding-​
Install up Git:
Debian/Ubuntu:
Code:
sudo apt-get install git
Fedora:
Code:
yum install git
ArchLinux:
Code:
pacman -S git
openSUSE:
Code:
zypper install git
Configuring git:
This step is very very important as those ID will be the one which identify you and you cannot change them later!
WARNING: You need to setup the same email as on github.com !
WARNING: email is case sensitive!
(For username I highly recommend to use the same as on your computer, but you could use any username you want)
Code:
git config --global user.email "[email protected]"
Code:
git config --global user.name "your-username"
Setting up SSH Keys(Skip this if you have already set them up) -
Code:
ssh-keygen -t rsa -C "[email protected]"
Now this will create 2 files in ~/.ssh directory as follows:
Adding SSH Keys to your Account :
Code:
cat /home/username_on_pc/.ssh/id_rsa.pub
This will show up few lines over terminal, copy those and add them into your Gerrit profile (Will not be detailed, there is a lot of guides on internet for this part)
Important: you need to setup your username into gerrit UI, otherwise you will never be able to push changes (on the screenshot there is no option to modify username as it is already setup but you should see one):
Test ssh is correctly working :
Code:
ssh -p 29418 <username>@<gerrit address>
If you see this message, then everything is setup and ready to propose changes :
If you get any errors, reread the howto to ensure you are not missing something.
You can also contact your team (there is probably an IRC channel for this) and ask for help.
Setting up the hook Change-ID :
WARNING: this need to be done in every repository or upload will fail!
Code:
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <username>@<gerrit address>:hooks/commit-msg ${gitdir}/hooks/

Making Changes and Submitting Patches -​Way 1. (for recurrent contribute) :
If you have a full build environment setup, the best practice say to not use your build trees for change & submit patches. If you do not have build environment setup, just don't care about this warning
Create a folder (like ~/clones/) where your clones with your changes will reside:
Code:
mkdir ~/clones
cd ~/clones
Go to git where you would make the change and copy the Clone link:
Code:
https://github.com/omnirom/android_device_sony_shinano-common.git
Go back into your terminal and clone the repo (optional: you can specify the branch name with -b <branch name>), then get into clone folder:
Now you can make the change using your favorite text editor (<escape> then ':q<enter>' to exit vim ):
Code:
git status
It tells you what files you modified(In Red color ) and shows on which branch you're currently on.
Now, the committing part,
Run:
Code:
git add -A
Run git status again, and it'll show the files in green color, telling you that the changes have been added.
Now:
Code:
git commit -s
This will commit the changes and open up a Text Editor called NANO. Here you need to edit the commit message that appears at the side of the gerrit window to describe what the patch does.
After writing the commit message, press Ctrl+O and then Enter key to save the commit message and then Ctrl+X to exit the editor. This is the committing part done. :good:
Optional (but better ): you can control what your commit changed, then rework if necessary (see last part of the guide):
Code:
git diff HEAD^
Now submitting the patch -
You need to catch the project path from the Gerrit interface. Go into project, list, and find the repository you changed:
Here the path is android_device_sony_shinano-common. It could include a 'sub-folder' like LineageOS do. For example, same repo on Lineage will be LineageOS/android_device_sony_shinano-common.
WARNING: path is case sensitive.
Go back to your shell and type:
Code:
git push ssh://<username>@<gerrit address>:29418/<repo path> HEAD:refs/for/<branch name>

Way 2. (for punctual contribute) :
Log-in into the Gerrit instance you want to commit into. Go into 'Projects', list, then choose the repo you want to make the change in:
Hit the 'Create Change' button:
This open a popup asking for some information:
Select branch for new change: the branch you want to commit in,
Enter topic for new change: leave empty
Description: Enter commit message
Finally hit Create
Now your change page is open, you can start editing files with the Edit button on the right:
then Add the file you want change:
The file open in an editor, make the needed changes and save with Save button, then Close:
(Redo the step if you need to change multiples files.)
When all your changes are present, hit the Done Editing button to validate your changes.
Your changes are pending and you can display it while clicking on file name:
The changed section is highlighted. If you made a mistake you can use the
icon:
Use the
button to get back on the summary page.
WARNING: your change is only a draft for now, you need to publish it:

Ask for review :
Once your commit is on Gerrit you need to setup a reviewer. This person will comment, reject or submit your patch.
Hardest part is to find the reviewer. You can ask in the dedicated IRC chan of your rom, or use some tricks like check who merged the commits into the repo.
Once you find who will be the reviewer, add it on the dedicated gerrit field:
Once your commit is ok and you want the reviewer take care of it, set-it 'Code-Review +1' and add a comment (will stay on gerrit) about why this change should be merged:
Guess what?! Done!
Congratulations, you just learned gerrit and know how you use it. I hope you'll send some nice patches and respect the Open Source. :victory:
Credits -
v_superuser said:
> Original kanged thread
Click to expand...
Click to collapse

FAQ​
Ensure your clone is up to date
Before picking and before writing patch you need to ensure your clone is up-to-date with the remote repository.
Go into the needed folder, then check the remote name:
Here the remote is named 'origin'.
We need to fetch the remote, on the right branch, then switch to that branch:
Code:
git fetch <remote name> <branch>
Code:
git checkout <remote name>/<branch>
(You can notice in my right prompt the current HEAD changed for remote/<remote name>/<branch name> . It is now up to date. )
Warning: Only the checkout command switch your local tree
Warning: git fetch use space between remote name & branch name but git checkout use slash (/) !
How to test pending changes
To test a change pending on Gerrit you need a working build environment for your rom. This guide will not explain how to set it up.
Once you have located the change you want to test,
go into the corresponding folder. Use the project path for hints:
here folder will be device/sony/msm8974-common.
Next use the download button into Gerrit interface
and copy paste the command in your terminal:
If you have merge conflict you will need to solve (with git mergetool, internet search and brain).
Now you can do this step again to merge other commits, or trigger the build for testing.
Update a pending change
You made a commit but notice some problem and it need to be reworked, without creating another one.
You need to follow the Ensure your clone is up to date then How to test pending changes with the commit who need reworking.
Once the commit is fetched locally you can make your changes:
Trigger the amend of the commit:
Code:
git commit [B]--amend[/B]
The git editor open and allow you to change the existing commit message:
Once your change is done, upload it:
The commit is updated (new Patch Set) on Gerrit (no new one was created):
Setup Gerrit as remote for easy reuse
Typing the push command each times could be painful if you upload patches often.
You can add Gerrit as a remote for easy reuse:
git remote add <local name> ssh://<username>@<gerrit url>:29418/<repo name>
Now you can simply use git push command:
Warning: need to be done in each repos!
Warning: This tip do not prevent typing HEAD:refs/for/<branch> each time !

reserved

This is absolutely wonderful guide , thank you for your contribution

git init
Click to expand...
Click to collapse
command should be passed before the below command! otherwise it willl show some error!
gitdir=$(git rev-parse --git-dir); scp -p -P 29418 <username>@<gerrit address>:hooks/commit-msg ${gitdir}/hooks/
Click to expand...
Click to collapse

Thanks for your guide, however, on the 3.4 or more version has a little change, can you update the article?
In addition, your article has a defective attachment (in "Adding SSH Keys to Your Account"), please fix it!

I was looking for it from so long
Thanks man