Z1/HONAMI/C6903 CYANOGENMOD 11 LINARO/SABERMOD NIGTHLY BUILDS
DOWNLOAD
(infected server)
(md5sum included with all builds)
kernel code compiled with linaro arm-eabi-4.9.1 2014.07 toolchain
rom code compiled with with sabermod arm-linux-androideabi-4.8.4 2014.07 toolchain
FEATURES
-O3 optimizations (ROM & Kernel code)
strict-aliasing rules
custom performance flags (ROM & Kernel code)
+30 cherry-picks used
Original Android KitKat UI (holo)
graphite
extra governors and schedulers
CHANGELOGS
(check build/sync date and compare)
http://www.cmxlog.com/11/honami/
http://changelog.bbqdroid.org/#/honami/next
(buildbot: intel core i7 [email protected], asus p8z77-v, 8gb corsair vengeance pro 2133mhz cl9, sapphire hd7970 dual-x, 2x samsung 128gb ssd 840 pro raid 0 array,
4x western wigital wd3200aaks raid 10 array, samsung f1 1tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, black-ice gtx-lite 240 radiator, 2x noiseblocker eloop b12-3 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
(Linux Mint 17 x64 "Qiana" 3.13.0-24)
HOMEPAGE
http://infectedbuilds.net
DONATIONS
if you can, please make a small donation... it will help with my work on these builds, keep website and dedicated server up and running, so i can deliver fast and unlimited downloads, and host the builds.
many thanks,
infected_
Click to expand...
Click to collapse
Disclaimer:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:
https://github.com/CyanogenMod
latest linaro arm-eabi-4.9.1 used to compile the kernel code & sabermod arm-linux-androideabi-4.8.4 toolchains to compile ROM code
Special Thanks
CyanogenMod Dev Team = for the source code
Linaro Dev Team = for the fresh linaro toolchains
Linaro Dev Team = linaro toolchain
@kecinzer = sabermod toolchains
@Cl3Kener = for the fresh linaro/sabermod toolchains
@aznrice2k4 = for the always fresh boosted toolchain
XDA:DevDB Information
Z1/Honami/C6903 Linaro/Sabermod CyanogeMod 11 Builds, ROM for the Sony Xperia Z1
Contributors
infected_
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest CWM Recovery or TWRP
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-07-05
Last Updated 2014-07-24
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (extract boot.img from an official cm 11 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps = http://forum.xda-developers.com/showthread.php?t=2397942
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod ROM for the Xperia Z1/Honami/C6903.
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using linaro arm-eabi 4.9.1 14.05 (kernel code) & sabermod arm-linux-androideabi 4.8.3 14.05 (rom code) toolchain compilers
May contain some custom cherry-picks. Always see changelog for details.
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124 . Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
What is graphite?
Graphite has been around for a while in GCC. During this time a lot of people tested Graphite and Sebastian fixed many bugs. As of today the Graphite infrastructure is pretty stable and hosts already specific optimizations such as loop-interchange, blocking and loop-flattening.
However, during the development of Graphite we also found areas where we are still way behind our possibilities. First of all we realized that the use of a rational polyhedral library, even though it provides some functionality for integer polyhedra, is blocking us. Rational rational polyhedra worked OK for some time, but we have now come to a point where the absence of real integer polyhedra is causing problems. We have bugs that cannot be solved, just because rational polyhedra do not represent correctly the set of integer points in the loop iterations. Another deficit in Graphite is the absence of a generic optimizer. Even though classical loop transformations work well for certain problems, one of the major selling points of polyhedral techniques is the possibility to go beyond classical loop transformations and to forget about the corresponding pass ordering issues. Instead it is possible to define a generic cost function for which to optimize. We currently do not take advantage of this possibility and therefore miss possible performance gains. And as a last point, Graphite still does not apply to as much code as it could. We cannot transform a lot of code, not only because of the missing support for casts (for which we need integer polyhedra), but also because of an ad hoc SCoP detection and because some passes in the GCC pass order complicate Graphite's job. Moving these road blocks out of the way should increase the amount of code we can optimize significantly.
Click to expand...
Click to collapse
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
Downloading. Will install later. Loved infected builds on i9100
this what i need for my phone :angel:
download and install now
One more great rom, will download it and try it when im on pc ^_^, thks dev.
Sent from my C6903
Another awesome Dev from i9100!, gonna try this rom soon
Sent from my C6903 using XDA Free mobile app
screens showing toolchains used on the build, are in attachment.
regards.
install finito
Screen flow like mercury
smooth and fast as F hell :laugh:
love the heads up :angel:
keep up man :good:
check this out better camera app
http://forum.xda-developers.com/goo...ps/app-cameranext-one-plus-one-cm11s-t2730715
The update check in settings is from CM or from your server? In other words to update and stay infected we must check in the settings or we have to check manually from the link? Really fast rom by the way!
if possible, please let me know about the battery life , im really curious
I would test it myself but I have too much crap on my phone that needs to be saved and cleared out
regards
ilmorga said:
The update check in settings is from CM or from your server? In other words to update and stay infected we must check in the settings or we have to check manually from the link? Really fast rom by the way!
Click to expand...
Click to collapse
If you use the in-built CM Updater, you will end up with official CM nightly, and not linaro/sabermod build.
hassanman1997 said:
if possible, please let me know about the battery life , im really curious
I would test it myself but I have too much crap on my phone that needs to be saved and cleared out
regards
Click to expand...
Click to collapse
battery is good.
i will try to fix a commit merge error, and add some extra governors and schedulers from a hammerhead kernel, so we can play a bit with them..
battery is good
19% for= 4 hours 1 hour sccren on wifi on 2g
it's really good
Thank you, ill try this rom ASAP :laugh:
Finally, Infected_ builds for Honami
Thanks for the awesome work..
e30luismi said:
pimped kernel work?
Click to expand...
Click to collapse
tried the latest regular and light version, both of them dont work.
e30luismi said:
pimped kernel work?
Click to expand...
Click to collapse
infected_ said:
tried the latest regular and light version, both of them dont work.
Click to expand...
Click to collapse
Actually not a ROM problem.. Pimped kernel needs updation
abbychauhan said:
Actually not a ROM problem.. Pimped kernel needs updation
Click to expand...
Click to collapse
yeah... i know its not a ROM problem...
Related
Kernel+ for AOSP 4.2.2 ROMs
This is a kernel that I have been compiling and using on my own device for a while, and I want to share this with the community. I enjoy the CM10.1 stock kernel, but I want to keep up to date with the newest Linux version and CodeAuroraForum source. I also want the most optimized experience possible, along with a few extra features. Kernel+ is always built with the latest Linux kernel and Qualcomm CAF sources to provide a fast, stable, and bleeding edge experience. The source can be found on my GitHub here Enjoy .
What is this?
This is a kernel based off of CyanogenMod's 'cm-10.1' branch of the Galaxy S III kernel.
Kernel+ is built with the goals in mind:
To always be up to date with the latest source from CodeAuroraForum and Kernel.org
To optimize as much as possible for the smoothest user experience
To base closely off of the CM10.1 kernel for optimal stability, not features
To provide a fast, stable, and bleeding edge experience for users
Features
Linux 3.4.54
always up to date with the latest source straight from Qualcomm's CodeAuroraForum
latest Linaro 4.7 toolchain compiled
CPU frequency from 384Mhz - 1.5Ghz
FauxSound App support
FRandom built-in
GPU overclocked to 480 Mhz default
custom voltage control
excellent battery life
optimized and stable
small kernel size
more coming soon...
Click to expand...
Click to collapse
Downloads
All downloads can be found here: CLICK ME
Note: d2att and d2tmo version are identical; please download the d2att version
Click to expand...
Click to collapse
Instructions for Installing
1. Download the kernel.
2. Copy it to your phone.
3. Flash with TWRP or CWM.
Note: Kernel+ is packaged with invisiblek's AnyKernel, meaning that it will unpack your current ramdisk and repack it with this kernel during the flashing process. This means that it will be compatible with any AOSP 4.2.2 ROM, even if they have different ramdisks. Also, please make sure that you are currently running a stock AOSP kernel (CM10.1, AOKP, SlimBean, etc) before flashing Kernel+ so that your ramdisk will be compatible.
Click to expand...
Click to collapse
ChangeLog
7/23/13
Linux 3.4.54
pulled in updates from CM
lots of updates from CAF
pulled in latest CodeAuroraForum and Kernel.org patches
7/5/13
Linux 3.4.52
fixed voltage control (I compiled with the wrong defconfig before...my fault)
pulled in a few updates from CM
synced with latest CAF
pulled in latest CodeAuroraForum and Kernel.org patches
7/2/13
fixed bug where init.d script permissions was not set correctly
7/2/13
Linux 3.4.51
GPU 3D overclocked to 480 Mhz default
custom voltage control
lots of CAF updates...look at GitHub and see how many times I've merged CAF over week long period!
changed min CPU frequency to 384 MHz
synced with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
6/24/13
Linux 3.4.50
lots of updates straight from CAF
many updates from CyanogenMod source; merged 'next' branch for support for media-caf
fixed frandom in build
added init.d script to enable frandom at boot - feel the speed increase!
pulled in latest CodeAuroraForum and Kernel.org patches
6/19/13
fixed flickering (last time, I promise )
added frandom (Entropy Seeder - increases overall smoothness)
lots of updates from CodeAuroraForum
pulled in latest CodeAuroraForum and Kernel.org patches
6/16/13
Linux 3.4.49
lowered MDP bandwidth values - flickering is gone now with the original values after the CAF merge
reverted Bluetooth "revert" code from CM - BT seems to be fixed from the latest CAF merge now
updated display code
Updated FauxSound to v2.1 with PowerAmp Amplifier Controls
sync'ed with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
Bleeding Edge!!
6/12/13
adjusted MDP bandwidth values - no more flickering
fixed bluetooth
added support for FauxSound
added 189Mhz step with lowered voltage
sync'ed with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
6/8/13
initial release
Linux 3.4.48
pulled in latest CodeAuroraForum and Kernel.org patches
compiled with the latest Linaro 4.7 toolchain
already 200+ commits ahead of the stock CM10.1 kernel
Click to expand...
Click to collapse
Thanks to:
CyanogenMod for their work and source for d2's
invisiblek for his AnyKernel package
Kernel.org
CodeAuroraForum
AndroidFileHost
...if I forgot you, please let me know!
Click to expand...
Click to collapse
FAQ
Frequently Asked Questions
How do I disable GPU overclock?
By default, the GPU is allowed an extra 480 Mhz freq step, whereas stock only allowed up to 400 Mhz. If you feel that you do not need the extra GPU 3D power, then you can disable it by adding the line:
Code:
echo 1 > /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_pwrlevel
to the file /system/etc/init.d/98kernelplus. Then reboot.
How do I adjust the voltages?
You can control the CPU freq voltages by using an app such as Trickster, System Tuner, SetCPU, etc.
What is frandom? How do I enable it?
Frandom is basically a more efficient random generator. It can be used in place of /dev/urandom and is 10 - 50 times faster. Using frandom will use very little of the kernel's Entropy pool, which in turn will provide better performance and smoothness. Frandom is already built-in to the kernel and enabled via an init.d script. No need to manually enable it.
one more...
klin1344 said:
one more...
Click to expand...
Click to collapse
i will test drive, thanx op
Miss your rom work thanks for the kernal
Sent from my SGH-T999 using xda app-developers app
Thanks klin good work man!
Sent from my SGH-T999 on Tapatalk 2 running LiquidSmooth v2.5 featuring the latest Lean Kernel experimental build.
I just finished tweaking the MDP bandwidth parameters, and I think I have found the sweet spot. There is no more flickering at all. Just a few more things I *need to add and it will be ready for the next update, probably tomorrow*
Sent from my SGH-T999 using Tapatalk 2
klin1344 said:
. Just a few more things I
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
.......... Keeping us in suspense I see
Thanks for your work, ready to flash the newest
DylanTheVillian said:
.......... Keeping us in suspense I see
Thanks for your work, ready to flash the newest
Click to expand...
Click to collapse
Haha sorry, I don't know why tapatalk failed on me... I have added the second part of my reply.
Also, fauxsound has been merged, and I have added a 189Mhz CPU step with a lower voltage. I will be testing these tonight :laugh:
klin1344 said:
Haha sorry, I don't know why tapatalk failed on me... I have added the second part of my reply.
Also, fauxsound has been merged, and I have added a 189Mhz CPU step with a lower voltage. I will be testing these tonight :laugh:
Click to expand...
Click to collapse
Thanks klin!!! Can I test too?! :silly:
DylanTheVillian said:
Thanks klin!!! Can I test too?! :silly:
Click to expand...
Click to collapse
You can test once I release it
You just have to wait one day...
Sent from my SGH-T999 using Tapatalk 2
KLIN! So glad to see you dev'ing again!!!
+Cool story, bro!
+The "Thanks" button should be more versatile. So, the "Thanks" you get from me is not just thanks, but can be laughing, props, +1, and so on.
Sorry guys, I got really busy today, so I wasn't able to release the update...
I'll try my best to find some time tomorrow to build and upload them.
thanks for variety of kernels
doe's this address any bt issues?:fingers-crossed:
trofmoc said:
doe's this address any bt issues?:fingers-crossed:
Click to expand...
Click to collapse
The 6/8 build doesn't have it yet, but in my source I have patched up Bluetooth and the fix will be in the next update.
Sent from my SGH-T999 using Tapatalk 2
6/12/13 Update
The new update is out! Below are the changes from 6/8/13.
Changes:
6/12/13
adjusted MDP bandwidth values - no more flickering
fixed bluetooth
added support for FauxSound
added 189Mhz step with lowered voltage
sync'ed with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
Click to expand...
Click to collapse
klin1344 said:
The new update is out! Below are the changes from 6/8/13.
Changes:
Click to expand...
Click to collapse
Thanks buddy!
6/16/13 Update
New update is uploaded!
Changes:
6/16/13
Linux 3.4.49
lowered MDP bandwidth values - flickering is gone now with the original values after the CAF merge
reverted Bluetooth "revert" code from CM - BT seems to be fixed from the latest CAF merge now
updated display code
Updated FauxSound to v2.1 with PowerAmp Amplifier Controls
sync'ed with CyanogenMod source
pulled in latest CodeAuroraForum and Kernel.org patches
Bleeding Edge!!
FFC
Can anyone confirm that the front facing camera doesn't cause phone to reboot when trying to take a pic?
corlissak said:
Can anyone confirm that the front facing camera doesn't cause phone to reboot when trying to take a pic?
Click to expand...
Click to collapse
I have never experienced that.
Sent from my SGH-T999 using Tapatalk 4 Beta
Donning a new name in favour of the new delicious version of Android... Welcome to the ThunderKat Project!!
Heavily based of my Flaming Monkey kernel configurations and the stock AOSP kernel source, here's my standalone kernel for the Nexus 10. I will maintain this independently.
It will always remain close to the AOSP exynos kernel for manta (Nexus 10) with a few useful tweaks and additions, but will not have any OC/UV, colour controls and any advanced customisation options. It is a stable kernel and will not have frequent updates.
This kernel uses the AnyKernel method and is ROM independent. I have tested this on 4.4 (Stock & AOSP) based ROMs.
Features:
1. Linux Kernel 3.4.39.
2. Based on AOSP KitKat MR1 kernel source for exynos/manta.
3. Built using the Google ARM GCC 4.8 toolchain with -O3 CFLAGS & AFLAGS optimisations & ARM Cortex A15 build optimisations.
4. Enabled Conservative & Powersave CPU frequency governors (in addition to Interactive, Performance & Userspace). Interactive set as default.
5. Preserve correct sysfs permissions on governor change.
6. KSM (Kernel Samepage Merging) support.
7. NTFS, F2FS, EXT4 xattr (extended attributes) support.
8. Networked file systems support (NFS V3, NFS V4 & CIFS).
9. HIDRAW support (supports non-conformant HID devices).
10. Support for more input devices (keyboards, mice & joysticks) including Logitech Unifying devices.
11. Support for USB serial modems (PPPOE).
12. Support for multi-card readers (multi-lun devices). This allows you to mount multiple cards using a multi-card reader. May need an app like StickMount. (Credit @nvertigo67)
13. Removed SWAP support.
14. Removed some un-needed debugging.
15. Increased thermal throttle limits
16. Scalable CPU frequencies
Changelog [2014/08/24]:
1. Built using Graphite optimized GCC4.8 toolchain
2. Added ROW & SIO I/O schedulers
3. Set ROW as default I/O scheduler
4. Upstream F2FS changes
5. Miscellaneous I/O improvements
Changelog [2014/06/05]:
1. Update to AOSP 4.4.3 kernel source (kitkat-mr2)
2. Added F2FS filesystem support
Changelog [2013/12/15]:
1. Update to AOSP 4.4.1/4.4.2 kernel source (kitkat-mr1)
Changelog [2013/11/21]:
1. Initial release
Information:
1. Flash using a custom recovery (TWRP/CWM).
2. This kernel is ROM independent and uses the AnyKernel method. Hence it uses the current ramdisk. You may have issues if this is flashed after a kernel with a custom ramdisk. If so, reflash your ROM and then flash this kernel.
3. Needs an unlocked bootloader.
4. Make sure you have at least 50% battery charge before flashing this.
Download:
ThunderKatKernel-4.4.4-20140824 (AndroidFileHost)
ThunderKatKernel-4.4.4-20140824 (Goo.im)
Archive (4.4.x) - (AndroidFileHost)
Archive (4.4.x) - (Goo.im)
Archive (4.3.x) - Unsupported
Archive (4.2.x) - Unsupported
Source:
GitHub
Disclaimer:
While I have extensively tested this and even though it is heavily based on the AOSP kernel, you may encounter issues. I will try to help you, but I will not take any responsibility if anything goes wrong. Please exercise caution.
Credits:
Google, Samsung, CM, AOKP, PA, ktoonsez, morfic, franciscofranco, Goo.im, AndroidFileHost
Reserved. Just in case
craigacgomez said:
Reserved. Just in case
Click to expand...
Click to collapse
Very cool! I will be trying this tomorrow, will have time to play with it. Nice to see KSM in it.
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Wow, great news, thanks craig!
brGabriel said:
Nicely done. I'm running your kernel as we speak--snappy, snappy! No issues so far. :good:
Only thing left to do now is give it a catchy name like: "The CRAIGINATOR"
Click to expand...
Click to collapse
Thanks...and yes, I will be renaming my ROM and kernel to something more... well, appealing... when I restart the ROM project...
Once I'm at 50% I'll be all over this like a rash
Sent from my Nexus 10 using xda premium
Great job, runs great! Only issue is it defaults to cfq scheduler on boot even when I have it set to run deadline.
More of a preference than an issue.
This kernel is really good, I was very impressed by your previous Rom and look forward to the new Rom you said will be released later in the year (hopefully!). Your hard work is much appreciated. Using your kernel with Carbon Rom right now and it seems very stable.
Sent from my Nexus 10 using XDA Premium HD app
Yep, snappy, snappy!
Sent from my Nexus 10 using Tapatalk HD
this kernel works best on my N10. no reboot, no SOD and no battery drain.
my tablet is 10 days up without a single problem or recharge! :good:
i hope it will be continued in the future!
Yes, I will continue supporting this kernel... though there will not be many updates... the aim to to remain close to AOSP, yet provide some useful tweaks and additions... I will be building a newer version soon (having problems with the cross compiler on my work laptop, else I would have done it today)...
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
teodor_ch said:
Hi!
Can I flash this kernel to the stock ROM?
And revert back when new android version comes out to OTA update?
Thank you
Click to expand...
Click to collapse
Yes, this will work fine on stock...and you can easily revert back using the boot.img from the factory images provided by Google...
Updated release in OP...
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
I just installed the kernel, very smooth, I was having shutdowns on Trinity latest and RootBox. Hopefully is not a ROM problem and this kernel fixes it, I really like RootBox.
Thanks for the awesome work and support.
Erik
situman said:
Does this have the latest wifi and or gpu drivers? I know wifi drivers are kernel level, not sure about the gpu though. Anyways, its a very nice and smooth kernel. It's been a baron wasteland in mantaland. I guess Google didn't sell many of these.
Click to expand...
Click to collapse
I have yet to incorporate the updated wifi and gpu kernel level drivers... I will be working on these soon...
Anyone here with sufficient kernel knowledge to merge the updated mali graphics drivers (http://malideveloper.arm.com/develo...n-source-mali-t6xx-gpu-kernel-device-drivers/)... There are a few updates that are beyond my kernel & C/C++ capabilities... like osk has been replaced by kbase... Please PM me if you can help!! Thanks!
Great work on this kernel! First time reaching 9 hours on screen time. Paired with Mr Robinson AOKP.
UberTC optimized for A8 & A9
This is basically UberTC toolchain built for A8 and A9 CPUs.
If you don't know what a toolchain is made for don't post here please
Note that i haven't tested A9 builds. If you find any bug, feel free to post it here.
Downloads: https://bitbucket.org/Coldwindofnowhere/
All credits goes to @Cl3Kener
Contributors
@Cl3Kener
Source: https://github.com/UBERTC/
Version Information
Status: Stable
Created 2015-11-09
Last Updated 2015-11-09
Which version should i choose ?
- Use A8 version if you want to build for any Cortex-A8 based device : i9000 (and all of it's variants), i9001, ...
- User A9 version if you want to build for any Cortex-A9 based device : i9100, i9300, i9305, ...
How to use this toolchain for your builds ?
Add this to your local manifest (for arm-eabi 4.9 with A8 optimisations)
Code:
<remote fetch="https://bitbucket.org/" name="bitbucket" />
<project name="Coldwindofnowhere/arm-eabi-4.9-cortex-a8" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" remote="bitbucket" revision="master" />
(I will add more stuff later)
Reserved
Thanks for the contribution.
I thought that the same optimization can be obtained from editing the kbuild_cflags or build cflags (as which chet kener said himself) ? Unless I'm just assuming the wrong things
Last question, will there be regular builds compiled everytime there is a new release?
gsstudios said:
Thanks for the contribution.
I thought that the same optimization can be obtained from editing the kbuild_cflags or build cflags (as which chet kener said himself) ? Unless I'm just assuming the wrong things
Last question, will there be regular builds compiled everytime there is a new release?
Click to expand...
Click to collapse
Well i was doing the same (editing cflags) but i've noticed a speed improvement when i built the toolchain by myself using the right flags, could you try it and tell me if you notice any differences ? Also the additional flags i'm using are (for A8) :
Code:
--with-float=soft --with-fpu=neon --with-cpu=cortex-a8 --with-tune=cortex-a8
For the updates, i will try to update it a much as possible.
Coldwindofnowhere said:
Well i was doing the same (editing cflags) but i've noticed a speed improvement when i built the toolchain by myself using the right flags, could you try it and tell me if you notice any differences ? Also the additional flags i'm using are (for A8) :
Code:
--with-float=soft --with-fpu=neon --with-cpu=cortex-a8 --with-tune=cortex-a8
For the updates, i will try to update it a much as possible.
Click to expand...
Click to collapse
Sure, I'll try building with your toolchain builds on the s2. I'm pretty sure that the differences will be minor, considering how great the toolchain is even without any tuning at all.
thanks, gsstudios
Edit: Please disregard what I've just said. Don't have time due to commitments to exams. Maybe sometime later this week I will be free.
I've uplodaded A8 optimized arm-eabi 5.3 & 6.0 toolchains (if anyone cares)
Tell me if you need A9 optimized ones.
Coldwindofnowhere said:
I've uplodaded A8 optimized arm-eabi 5.3 & 6.0 toolchains (if anyone cares)
Tell me if you need A9 optimized ones.
Click to expand...
Click to collapse
Yup i'd like to try the A9 ones for eabi 6.0 if possible
aaz03 said:
Yup i'd like to try the A9 ones for eabi 6.0 if possible
Click to expand...
Click to collapse
Sure, i'll build it in a bit.
Edit : uploaded, tell me if you face any issues.
Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?
djkoloda said:
Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?
Click to expand...
Click to collapse
Sounds like a gub of the toolchain, i have no clue how to solve it. I'll try to compile a rom with it to see if it get the same error.
Coldwindofnowhere said:
Sounds like a gub of the toolchain, i have no clue how to solve it. I'll try to compile a rom with it to see if it get the same error.
Click to expand...
Click to collapse
Thanks! The same error is also in UberTC from https://bitbucket.org/UBERTC
What build system do you use? Standard Omni build system or some other?
djkoloda said:
Hi, Coldwindofnowwhere! I tried with an updated compiler arm-linux-androideabi-4.9, but the error now appears. What is wrong with the compiler or a bug at the Omni source?
Click to expand...
Click to collapse
Umm, what compiler flags are you using ?
Coldwindofnowhere said:
Umm, what compiler flags are you using ?
Click to expand...
Click to collapse
I used the optimization flags from Alberto96, but they are probably not compatible with UberTC. I returned to the original state and try to recompile .
djkoloda said:
I used the optimization flags from Alberto96, but they are probably not compatible with UberTC. I returned to the original state and try to recompile .
Click to expand...
Click to collapse
Compiling without these flags has not given results. I tried to arm-linux-androideabi-4.8 UberTC instead of that of the Omni and everything compiled.
Hi oneplus2 people!
This is my modified kernel with some kernel optimizations and some compiler optimizations.
The goal of abyss is to achieve improved performance/battery without the cost of stability.
I will not be overhauling this project with changes that are not logical to add.
This kernel should work on the latest 7.x.x roms like CyanogenMod.
It might work on other roms, but there will be little support for them.
How does one achieve this?
- build kernel with an optimized toolchain
- use compiler optimization flags (experimental)
- remove redundant code
- improve existing code with more efficient code
- etc. (most are not so easy to explain)
This kernel is built with mdalexca's latest UBER GCC 4.9.
Is there actually a performance improvement?
With all the changes added up, there should be. Whether or not one notices the difference is another thing.
For those interested in how the kernel optimizations will benefit/work, please look at my github source and read the commit messages.
For those interested in how the compiler optimizations/hacks will benefit/work, please look at this article.
Downloads:
Latest release
BasketBuild
Source:
GitHub
This was made by request from dsst22 who also tested this bad boi like crazy.
XDA:DevDB Information
abyss kernel for the OnePlus 2, Kernel for the OnePlus 2
Contributors
kwoktopus, dsst22, OnePlus, grarak, The Flash, arter97, Lord Boeffla, frap129, Linux, Google, CAF, a bunch of other major OEMs
Source Code: https://github.com/abyss-kernels/oneplus2
Kernel Special Features:
Version Information
Status: Nightly
Current Stable Version: 1.20
Stable Release Date: 2016-12-05
Created 2016-12-05
Last Updated 2016-12-13
Key Changes:
- upstream interactive governor (with Flash 1.0 profile by The Flash) (Google and CAF)
- upstream cpufreq driver (Google and CAF)
- upstream cpu-boost driver (Google and CAF)
- upstream random driver from Linux 4.1.31 (performance..!)
- slub/slab/slob/vmalloc patches
- flar2's slightly modified thermal driver
- using Linaro's power efficient workqueues throughout kernel
- using Adreno idler by arter97 to reduce frequency scaling without performance cost
- using power efficient "relaxed" macros throughout kernel (assembler)
- KCAL Control Driver by Savoca
- Android-Keyboard patch, use your device as an external keyboard!
- too many to list here, check out my source
How to install:
Place zip in to your internal storage
Place current ROM zip on to your storage
Boot into TWRP recovery
(If you're coming from a different kernel, dirty flash current ROM)
Flash kernel zip
Reboot
Don't like the defaults?
Use Kernel Adiutor to change the settings!
Frequently Asked Questions:
Is this a custom kernel?
I was asked this question once, and it posed as a real good question. I do not consider abyss to be a "custom kernel" per se, but more so as a modified kernel. The patches and features that go into this kernel do not make it customizable. What they do is improve what has already been implemented. It is like swapping a car's engine for a better one rather than just adding LED flooring lights and fancy car mats.
Can you add [this] and [that] feature?
Something I pride myself with this kernel is that it does not have a bunch of random, useless features or patches mashed into it. Everything put into this kernel is thought out and tested. I see a lot of works being made popular because it has [this] and [that] feature when really, it's nothing revolutionary. As a matter of fact, most things added to any kernel will not make it 5x better than any other kernel. Most of the time, simple is better; and in this case it definitely is!
For me
Thanks! I'll give it a go.
Giving it a go
Yess! Been waiting for this ever since i saw your OP2 repo!
Does this kernel install on a f2fs formatted system?
suraj.das said:
Yess! Been waiting for this ever since i saw your OP2 repo!
Click to expand...
Click to collapse
You can thank @dsst22 for helping with testing, or else you would have waited a very long time :silly:
socialdistortion said:
Does this kernel install on a f2fs formatted system?
Click to expand...
Click to collapse
I have not made any file system changes to the kernel. If the stock CM kernel supports, then this one will too.
Is kcal support present..??
chl1810 said:
Is kcal support present..??
Click to expand...
Click to collapse
unfortunately no.
good to see new kernel for our device, thanks and good luck
suraj.das said:
unfortunately no.
Click to expand...
Click to collapse
I wish it had
chl1810 said:
I wish it had
Click to expand...
Click to collapse
I can remember the YoshiShaPow falcon kernel
chl1810 said:
I wish it had
Click to expand...
Click to collapse
In the future
PeterImmel said:
I can remember the YoshiShaPow falcon kernel
Click to expand...
Click to collapse
You can probably see how much I've grown as a developer since then too :angel:
Works on a f2fs filesystem based rom. Testing it now...
Edit: No obvious bugs at the moment. Is it possible to implement some sort of charging control. The USB charging speed is super slow (on both this kernel and stock CM kernel).
kwoktopus said:
In the future
Click to expand...
Click to collapse
Nice!! thank you!!
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
adame09 said:
Pretty smooth haven't found any bugs. Love the simplicity.
I can't imagine what it would be like with a little over clock.
Click to expand...
Click to collapse
I trust the engineers that designed the chip to choose a safe maximum clock speed. Here's a pretty good article on the risks vs benefits, which outline some strong points.
But, if I were to add it, I would set the max value at boot to stay as stock values; so I'll leave it up to @dsst22 to decide.
I'll try this out for you dude. Impressive what you've done.
hi Guys,
as some of u maybe know from the OPO/OP2/OPX/OP3(T) area i'm doing a "build-service" for non official boeffla kernel builds and as we recently also got a boeffla kernel
for the One Plus 5 device (kudos and thx to @Lord Boeffla!) i want to share with u my self made Linaro/Uber builds for that device in addition.
i'm gonna reduce redundancy and keep it shorter this time as about how this started and my primary intention can also be taken from the corresponding Samsung Thread
so without further ado let's go:
First of all the obligatorily Disclaimer:
As also written in the title please note these builds are UNOFFICIAL, are NOT SUPPORTED in any way by Lord Boeffla or myself and might be EVEN UNSTABLE! So take them as they are! As always flash them at your own risk and make a backup before flashing! (yeah take this advice seriously!)
About bugs: Before you report ANY issues with the linaro/uber builds provided here (doesn't matter which one!) FIRST TRY the non-linaro/uber official builds from HERE to see if they will be gone then. if they wont, you can go on and report your problems in the official boeffla kernel threads! I hope you understand that we have to treat and keep these builds here completely separate from official ones as they have in no terms something to do with each other! Not respecting this will force me to stop building further linaro/uber builds of boeffla kernel.
About benchmarks and comparisons between toolchains:
It's common known that linaro (maybe also uber?) builds might give us higher benchmark rates and that seems great for some people (in fact it's pointless per se in my opinion)
so please if you really must, post them ONLY here and NOT in official boeffla kernel thread, thanks!
Now some more precise informations about what's going on here:
what i did:
the images are always build with original sources from official boeffla kernel OP5 repositories with some not worth to mention minor changes
to be able to build it on my build environment with non stock toolchains.
all images are compiled from special branches from a forked Boeffla Kernel repository
with recent versions of Linaro - Credits and Thx to @The flash for pre-configured/-build 7.x.x toolchains
with recent versions of Linaro original pre-build toolchains (Versions < 7.x.x)
and recent verisions of Uber Toolchains - Credits to Team Uber and Thx and Credits to @DespairFactor for the pre-configured/-build toolchains
Sources:
all images are build with changes from different branches in following repositories:
https://github.com/zanezam/boeffla-kernel-oos-oneplus5
Beside of some additional fixes from my side all changes are taken from repositories of @ak
so all credits to him, and thx again for the starting point!
what i will do:
build the source code with linaro/uber toolchain and (like Lord Boeffla usually does) provide a recovery image of recent boeffla kernel versions.
do a test for about 1 day with this builds and if they work without any big issues, add them on the corresponding download locations.
i will try to keep the linaro/uber toolchains as up-to-date as possible till the need of bigger code change will be reached.
not providing versions that are not released by Lord Boeffla yet.
not providing an image if it is not working - well of course not *g* but it will be marked as "canceled" then for info.
not change the source code to add/remove features or fix boeffla kernel related bugs.
not support the whole stuff here.
what i will maybe do (sooner or later):
provide ZZMoove Governor test builds if there are any new versions to test - more infos and discussions about ZZMoove Governor can be found HERE
provide builds for special operations like a nethunter special build (no plans, they will just pop-up)
maybe tune the build flags if some more linaro/uber experienced dev comes up with "better" ones (feel free to post and let me know, toolchain specialists! *g*)
Downloads:
One Plus 5 Oxygen OS v4.x.x
(*lxxx* linaro / *uxxx* uber)
One Plus 5 Oxygen OS v5.x.x
(*lxxx* linaro / *uxxx* uber)
Mirror on Mediafire:
One Plus 5 Oxygen OS v4.x.x
(*lxxx* linaro / *uxxx* uber)
One Plus 5 Oxygen OS v5.x.x
(*lxxx* linaro / *uxxx* uber)
OnePlus 5T:
One Plus 5T Oxygen OS v5.x.x
(*lxxx* linaro / *uxxx* uber)
Mirror on Mediafire:
One Plus 5 Oxygen OS v5.x.x
(*lxxx* linaro / *uxxx* uber)
Mirror on Androidfilehost for all devices (only latest kernel versions)
reserved
reserved 2
Sweet!
I'm waiting impatiently to see new zzmoove governor!
Old i9300 user Regards! :highfive:
Woohoo! @ZaneZam ! long time no see! glad to see you there ! :good::highfive:
moreover, on a device we have in common again!
I can see you are now RC since! gratz and well deserved!
Cheers' mate
New Builds!
Ok Guys lets start with that "toolchain game"
builds of...
Boeffla-kernel-1.0-beta5-OOS4xx-OnePlus5
...uploaded
Changelog:
- Uber v4xx and v5xx images build with recent toolchain version 20170615 (again thx and credits to @DespairFactor for the pre-builded toolchains)
- Linaro v4xx and v5xx images build with recent toolchain version from linaro.org
builds with more recent versions (gcc v6.x.x and v7.x.x) are WIP because there are issues (like always *g*) with toolchain versions above v5.x.x and the used source: they build, yaay! they boot yaay! yaay!
but they don't scale mmmpfh! but hey the now released ones work well and as always im not giving up to bring up and out the builds with newer toolchains too.
ok now enjoy!
ZZ
PS: hi nice to see u here @AndroidGX yeah long time no see, paths crossing again
Amazing
Enviado desde mi SM-G955F mediante Tapatalk
New Builds!
Hi Guys,
builds of...
Boeffla-kernel-1.0-beta6-OOS4xx-OnePlus5
...uploaded
enjoy!
ZZ
I presume you'll be doing LOS based kernels when Boeffla gets his 2nd device and starts those?
djsubterrain said:
I presume you'll be doing LOS based kernels when Boeffla gets his 2nd device and starts those?
Click to expand...
Click to collapse
yes your presumption is right even tho i need testers because i think i won't switch to LOS this time and the phone will be my daily soon so no risks wanted
and a to u if u are using LOS and want to contribute
New Builds!
Hi Guys,
builds of...
Boeffla-kernel-1.0-beta7-OOS4xx-OnePlus5
...uploaded
Changelog:
- Linaro images build with recent toolchain versions from www.linaro.org
- Uber images build with recent toolchain version 20170720 (thx and credits to @DespairFactor for the pre-builded toolchains)
enjoy!
ZZ
ZaneZam said:
Hi Guys,
builds of...
Boeffla-kernel-1.0-beta7-OOS4xx-OnePlus5
...uploaded
Changelog:
- Linaro images build with recent toolchain versions from www.linaro.org
- Uber images build with recent toolchain version 20170720 (thx and credits to @DespairFactor for the pre-builded toolchains)
enjoy!
ZZ
Click to expand...
Click to collapse
I am updating my toolchain again right now
DespairFactor said:
I am updating my toolchain again right now
Click to expand...
Click to collapse
Thx matt
Sorry, but what is difference between linaro and uber builds?
Official boeffla builds are compiled with?
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
here something to read (yeah i missed putting the uber link into OP -> will be done soon *g*)
https://forum.xda-developers.com/android/software/toolchain-uber-toolchains-t3527997
https://www.linaro.org/downloads/
in short both use a similar ways but with the same goal -> to optimize code -> which can have benefits in speed and battery usage (marginal) but also can produce problems -> even though fortunately they happen not often at least for the images which run out of the box they run well. in addition i use full optimization flags so this is the max we can gain from the toolchain/code optimizing point of view.
official boeffla kernel on the other hand is build with google toolchian 4.9 and so it's the same as stock kernel but lord boeffla recently switched also flags from size optimizing to speed optimizing (but this is O2 optimizing which is still "in stock range")
hope i shed some more light but try it out and see what feels best for u. u can flash over my and unoffical images and vise versa whithout loosing settings
ZaneZam said:
here something to read (yeah i missed putting the uber link into OP -> will be done soon *g*)
https://forum.xda-developers.com/android/software/toolchain-uber-toolchains-t3527997
https://www.linaro.org/downloads/
in short both use a similar ways but with the same goal -> to optimize code -> which can have benefits in speed and battery usage (marginal) but also can produce problems -> even though fortunately they happen not often at least for the images which run out of the box they run well. in addition i use full optimization flags so this is the max we can gain from the toolchain/code optimizing point of view.
official boeffla kernel on the other hand is build with google toolchian 4.9 and so it's the same as stock kernel but lord boeffla recently switched also flags from size optimizing to speed optimizing (but this is O2 optimizing which is still "in stock range")
hope i shed some more light but try it out and see what feels best for u. u can flash over my and unoffical images and vise versa whithout loosing settings
Click to expand...
Click to collapse
Of course, you recommend zz governor with your kernel, right?
Boeffla by Default uses interactive
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
liver20 said:
Of course, you recommend zz governor with your kernel, right?
Boeffla by Default uses interactive
Enviado desde mi ONEPLUS A5000 mediante Tapatalk
Click to expand...
Click to collapse
yes of course
but i'm also not mad if u think another governor is better
the interactive recommendation is because it's stock and
the most stable selection u can do make. not saying that zzmoove isn't
stable. actually can't say that as im using it on ALL my 8 devices since meanwhile
even years w/o an issue (well we have got one on the opo recently but that
was related to a special feature and is sorted)
but again try it some time and see how it plays on your system
New Builds!
Hi Guys,
builds of...
Boeffla-kernel-1.0-beta8-OOS4xx-OnePlus5
...uploaded
Changelog:
- Uber images build with recent toolchain version 20170730 (thx and credits to @DespairFactor for the pre-builded toolchains)
enjoy!
ZZ