{
"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"
}
Z5/SUMIRE/E6653 CYANOGENMOD 13.0 UNOFFICIAL SABERMOD BUILDS
CURRENT BUILD: 20160613
MARSHMALLOW 6.0.1_r46
DOWNLOAD
ROM CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-ANDROID 4.9.x (20160520)
KERNEL CODE COMPILED WITH LATEST SABERMOD AARCH64-LINUX-GNU 4.9.x (20160520)
SOURCE: https://github.com/infected-mm/android_kernel_sony_msm - 3.10.x
CURRENT ISSUES: - camera not at 100%, but usable.
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK KERNEL
- USING GAPPS FROM SECOND POST
- NO MODS OF ANY SORT
CHANGELOG:
http://www.cmxlog.com/12.1/z3/
BUILDBOT:
(intel core i7 [email protected] (1.22v), asus p8z77-v, 16gb corsair vengeance pro 2133mhz cl11 (1.5v), msi nvidia gtx 970, 1x samsung 850 evo 250gb + 1x samsung ssd 840 pro 128gb, 4x western digital wd3200aaks raid 10 array, samsung f1 1tb, seagate 2tb, silverstone olympia 1000w psu, antec 1200 high-tower)
(wc setup: swiftech apogee xt cpu-block, ek coolstream xtx 240 radiator, 2x scythe slipstream 120mm 1900rpm fans, swiftech mcp355 water-pump, danger den 5.25" reservoir bay)
DISCLAIMER:
These builds are freshly compiled/synced from CyanogenMod Rom open-source code:
https://github.com/CyanogenMod
SPECIAL THANKS
CyanogenMod Dev Team = for the source code.
@davidteri91 = for the device trees.
XDA:DevDB Information
Z5/SUMIRE/E6653 CyanogenMod 13.0 Sabermod Builds, ROM for the Sony Xperia Z5
Contributors
infected_
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest TWRP recovery and Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2016-06-13
Last Updated 2016-06-13
How-To
Coming from stock sony:
- download build, and extract boot.img
- fastboot flash boot boot.img
- download twrp from here, and as alternative cm recovery from here (note that cyanogenmod recovery doesnt support busybox)
- fastboot flash recovery twrp_recovery_20160607.img
- enter recovery, wipe and flash build, plus gapps.
- reboot and you are done!
Coming from an aosp based rom:
- enter recovery, wipe and flash build, and gapps
- you are done!
Reserved
F.A.Q (Frequently Asked Questions)
What is the difference between these builds and the official builds?
These are unofficial builds of CyanogenMod 13.0 for the Xperia Z5 (E6653)
ROM is built using the same source code (github) like the official one but with these following additions:
Compiled using sabermod aarch64-linux-gnu 4.9.4 (kernel code) & sabermod aarch64-linux-android 4.9.4 (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?
To compile any Android project like a kernel or ROM, developers need to use a toolchain. As per elinux.org, a toolchain is a set of distinct software development tools that are linked (or chained) together by specific stages such as GCC, binutils and glibc (a portion of the GNU Toolchain). Toolchains may contain a debugger or a compiler for a specific programming language as C++ or other. Quite often, the toolchain used for embedded development is a cross toolchain, or more commonly known as a cross compiler. All the programs (like GCC) run on a host system of a specific architecture (such as x86) but produce binary code (executables) to run on a different architecture (e.g. ARM).
The most commonly used toolchain is GCC, initially released almost 20 years ago. A lightly modified GCC is used by Google during the AOSP build process. While Google’s GCC is considered to be the most stable toolchain around, it has some pretty decent competitors like Linaro and SaberMod. These projects are known to boost the overall system performance significantly on many devices. Let’s take a quick look to see the background of these projects.
Click to expand...
Click to collapse
Source: http://elinux.org
What is SaberMod?
The term "SaberMod" is coming from:
the SaberMod project. Initially the project was used on SaberMod ROM for the Nexus 7 WiFi model (2013). This continued onto the Nexus 4 and Nexus 5 through help of user donations. The toolchains are based on GNU GCC 4.8, 4.9, and 5.0 with AOSP patches forward ported into GNU GCC. SaberMod also provides extra optimization features unlike Google’s toolchain, which gives options for a few amendments in the ROM itself to add more performance gains, such as graphite loop transformation optimizations. SaberMod tracks other utilities from GNU in the toolchain source components that are generally more up to date than AOSP or Linaro toolchains, and almost always tracks the development branches of GNU GCC for the latest patches and bug fixes. The toolchain ecosystem of SaberMod is very different from AOSP, using complex scripts to provide quick, up to date toolchains. Other toolchain sources like the AOSP based toolchain build repository have been heavily modified to work in favor of the way SaberMod toolchains are produced. I have approached some toolchain developers to ask a few questions.
Click to expand...
Click to collapse
Source: http://www.xda-developers.com/interview-with-developers-of-sabermod-hyper-toolchains/
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/
Optimization Flags in GCC
What are flags?
For compilers such as GCC, flags are essentially options. A flag can enable or disable an option or feature that is used when compiling (building) code.
What are optimizations?
Optimizations, in the context of compiler flags, are flags that improve some aspect of the code, whether it be size, speed, memory use, and debugging, among other possibilities.
General Optimizations
These optimizations are basic flags in GCC, typically implemented into projects to improve an aspect of the final compiled code.
-O1: Optimization level 1, very basic optimizations, rarely used.
-O2: Optimization level 2, basic optimizations, most commonly used.
-O3: Optimization level 3, basic + experimental optimizations. Large performance boost, but can produce bugs.
-Os: Optimize for size. Most of the optimizations from levels 1 and 2, with extras added to decrease the size of code.
-Ofast: All Optimizations from levels 1, 2, and 3, with extra fast math optimizations.
Typically produces the most bugs, with a large performance gain.
-Og: No performance boost, optimizes the debugging experience, making errors and
warnings more informative to help developers.
-g0: Disables all extra debugging, usually makes code faster.
-fomit-frame-pointer: Removes frame pointers when they aren’t needed, streamlining the code.
-fipa-sra: Removes unused parameters/variables and replaces parameters with the called value, streamlining the code.
-fkeep-inline-functions: Emits static inline functions, even after they’ve been called.
-fmodulo-sched: Reorders instructions in loops in the most optimal way.
-fmodulo-sched-allow-regmoves: a more aggressive -fmodulo-sched, optimizing loops further by allowing register moves
-fgcse-sm: Moves stores out of loops to decrease the workload of loops.
-fgcse-las: Removes redundant loads after a store to reduce the workload.
-fgcse-after-reload: Removes redundant loads after a reload.
-funsafe-loop-optimizations: Optimize more by making assumptions, can create bugs from loops overflowing.
-fira-hoist-pressure: Decreases size of the code by evaluating register pressure for hoist expressions.
-fira-loop-pressure: Makes code smaller and faster by evaluating the register pressure of loops.
-DNDEBUG: Passes the variable for no debugging.
-flto: Enables link time optimizations (LTO) for improved library and executable performance.
Graphite Optimizations
Graphite is a project within gcc that uses the integer set library (ISL) and the chunky loop generator (CLooG) to improve memory use and optimize loops.
-fgraphite: Performs basic graphite loop and memory optimizations.
-floop-interchange: Switches two nested loops.
-floop-strip-mine: Splits a complex loop into a set nested loops.
-floop-block: Splits a loop into nested loops so that the memory fits into caches.
-fgraphite-identity: Creates a visual polyhedral representation of certain graphite optimizations. with some optimizations from ISL such as dead code removal.
-floop-nest-optimize: Optimizes the order of nested loops for data-locality and parallelism. This flag is experimental
-floop-unroll-and-jam: Enable unroll and jam for the ISL loop optimizer.
-floop-parallelize-all: Use graphite data to find and parallelize loops that can be.
Multithreading optimizations
Make code run in multiple jobs (threads) to use a multicore cpu to its fullest potential.
-ftree-parallelize-loops=n: Run parallelized loops is n number of threads.
-pthread: Use the posix thread system for multi-threading.
-fopenmp: Use the OpenMP thread system for multithreading. Tends to use less ram than posix.
Sanitizer Flags
These flags use libsanitizer for memory optimizations.
-fsanitize=leak: Sanitize memory leaks to reduce memory use
-fsanitize=address: Sanitize memory addresses to reduce memory use
-fsanitize=thread: Sanitize excess threads to reduce memory/cpu use. Only for 64bit.
Hardware Optimizations
These optimizations optimize code for the targets cpu, gpu, or ram.
-marm: Uses the ARM instruction set for executable code, improving performance.
-mthumb: Uses the Thumb2 instruction set, improving compatibility.
-mthumb-interwork: Improves compatibility between Thumb and ARM code.
-march=X: Optimizes code for your CPU’s arch, such as armv6, armv7-a, etc
-mcpu=X: Optimizes code for your specific CPU such as cortex-a15, cortex-a53, etc.
-mtune=X: Refer to -mcpu
-mfpu=X: Optimizes code for your CPU’s FPU such as vfpv3. vfpv4, neon, etc.
-mabi=X: Optimizes code ABI for your CPU, such as 32 or 64
Click to expand...
Click to collapse
woot. finally it's own thread. thank you
been using this since the first build as DD tho wish camera was as good as stock but it's sony's fault
anyway hoping we could see more builds and more new roms from you?
Finally its here. Thanks for your incredible work!
Oh so thanks for thıs
Thank you
Sent from my E6603 using XDA-Developers mobile app
Thanks for your work! So everything is working except camera? Fingerprint reader for example?
diemadedrei said:
Thanks for your work! So everything is working except camera? Fingerprint reader for example?
Click to expand...
Click to collapse
yes. better than stock in my end ?
camera works but not 100% sadly. go try it.
Sent from my Nexus 6p using Tapatalk
Thanks, I will later this week.
@infected_ I tried the 0613 ver but it's not charging. when plugged in. the batt icon indicates it's charging but it's not. checked via ampere and I get -500. plus the led indicator just blinks red saying the batt is low.
is it kernel related? how can I fix this? tried flashing 2x clean install
LegionCommander said:
@infected_ I tried the 0613 ver but it's not charging. when plugged in. the batt icon indicates it's charging but it's not. checked via ampere and I get -500. plus the led indicator just blinks red saying the batt is low.
is it kernel related? how can I fix this? tried flashing 2x clean install
Click to expand...
Click to collapse
its charging.. i think LED has a small bug, yet to be fixed, during charging.
just leave it pluged for one hour or whatever time, and youll see that it charges.
regards.
infected_ said:
its charging.. i think LED has a small bug, yet to be fixed, during charging.
just leave it pluged for one hour or whatever time, and youll see that it charges.
regards.
Click to expand...
Click to collapse
Not only that I see that if you use the phone while its connected to charger it will stop charging but when you leave it for to minutes it will continue charging. Maybe it's a feature to not overheat.
Sent from my E6653 using XDA-Developers mobile app
albertobom said:
Not only that I see that if you use the phone while its connected to charger it will stop charging but when you leave it for to minutes it will continue charging. Maybe it's a feature to not overheat.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
+1 to this. it's kinda irritating tho. but no complaints
I want to report two errors:
The first is that the screen sometimes turns upside down when coming from lock screen. The screen redirect to the right direction when locking und unlocking the screen.
The second one is that the color of the screen turns sometimes pallid (hope this is the correcrt word .. otherwise: pale). But only at half-round area on the right side. Everything is okay after a reboot.
Is there anything I or others could do to improve the camera functionality? Whats the problem with it?
AND THX FOR THE GREAT PORT!
SpiGAndromeda said:
I want to report two errors:
The first is that the screen sometimes turns upside down when coming from lock screen. The screen redirect to the right direction when locking und unlocking the screen.
The second one is that the color of the screen turns sometimes pallid (hope this is the correcrt word .. otherwise: pale). But only at half-round area on the right side. Everything is okay after a reboot.
Is there anything I or others could do to improve the camera functionality? Whats the problem with it?
AND THX FOR THE GREAT PORT!
Click to expand...
Click to collapse
can you grab me dmesg and logcat when that happens? ill try have a look.
and thanks for the support.
regards.
albertobom said:
Not only that I see that if you use the phone while its connected to charger it will stop charging but when you leave it for to minutes it will continue charging. Maybe it's a feature to not overheat.
Sent from my E6653 using XDA-Developers mobile app
Click to expand...
Click to collapse
Abaddon said:
+1 to this. it's kinda irritating tho. but no complaints
Click to expand...
Click to collapse
logcat and dmesg please also. when grabbing logcat, reproduce what you said.
regards.
Snapdragon camera is the app camera in this rom?? I think so cm choose this camera for cm official rom.
And another thing... Is it possible that cm advantage your work for will do official cm build?? Maybe more devs are encouraged for will make new roms... Like du, pure aosp...
Thank for your efforts!!
Enviado desde mi E6653 mediante Tapatalk
uripiruli said:
Snapdragon camera is the app camera in this rom?? I think so cm choose this camera for cm official rom.
And another thing... Is it possible that cm advantage your work for will do official cm build?? Maybe more devs are encouraged for will make new roms... Like du, pure aosp...
Thank for your efforts!!
Enviado desde mi E6653 mediante Tapatalk
Click to expand...
Click to collapse
Actually there're not much differences between official and unofficial builds, and devs who aren't member in CM still can contribute their works and if it's helpful/useful, CM team will merge it to official source, so don't be worry about "unofficial" thingy.
RyTekk said:
Actually there're not much differences between official and unofficial builds, and devs who aren't member in CM still can contribute their works and if it's helpful/useful, CM team will merge it to official source, so don't be worry about "unofficial" thingy.
Click to expand...
Click to collapse
It's true but official cm has automatic builds with the news and the unofficial depends on that dev and his willingness to build future roms, it's a hobby and the devs have personal life and maybe the dev sale his device etc....
When one is a pity is leaving a rom with the effort that is behind it.
Enviado desde mi E6653 mediante Tapatalk
uripiruli said:
It's true but official cm has automatic builds with the news and the unofficial depends on that dev and his willingness to build future roms, it's a hobby and the devs have personal life and maybe the dev sale his device etc....
When one is a pity is leaving a rom with the effort that is behind it.
Enviado desde mi E6653 mediante Tapatalk
Click to expand...
Click to collapse
No, you can set up an own jenkin, and infected_ did it for his computer to build ROMs for Z2.
Related
Q: Are you Dead?
A: No. But on these day, I'm do something else (learning C/Python). I will come back in some day.
This is an experimental kernel based on the latest Air kernel(v4.4). I patched and re-config the kernel for testing and/or for fun.
My patches will never ever comes into other kernels.
1. using ext4 subsystem for ext2/3.
A very funny thing is Air kernel enabled "using ext4 subsystem for ext2/3", but independent ext2 support enabled, too.
I know It is insignificant for the performance. But that makes me feel sick So I disabled independent ext2 support to get a smaller(0.5kb lower?) kernel.
2. using the BFS scheduler.
For small systems, the default scheduler - CFS, is a very complex things, and complex code cause a low performance in embedded systems. BFS is a simple scheduler for embedded systems. It can makes the CPU go faster. In fact, some people think it makes Android UI slower than before.
BFS is written by Con Kolivas.
For more information, you can visit Con Kolivas blog: http://ck-hack.blogspot.com/
3. UKSM
Linux kernel uses KSM to merging same pages for KVM virtual machine. Cyanogenmod modified Android, so KSM can work with Dalvik too. And we can get more RAMs. UKSM is a new project, it more powerful than KSM. It works without any modify. UKSM will scan all data in memory and merge them.
UKSM is a Chinese project, and it's still in development.
You can visit http://http://kerneldedup.org/en to learn more. But there only one page is available in English now.
Usage of UKSM: http://kerneldedup.org/en/projects/uksm/uksmdoc/usage/
4.Deadline for default I/O scheduler. (In v0.06)
CFQ cause low boot performance and missing app icons on my phone. So I set deadline for default scheduler.
WARNING: Don't use it with Jelly Bean, if you do it, your phone will unable to boot, unless you flash a Jelly Bean's kernel.
Latest version
The latest version is v0.09.
All version (included broken/buggy kernel) downloads: http://biergaizi.info/pub/
Voodoo color
It has Voodoo color only(no 65fps or blue color)
Download: http://biergaizi.info/pub/[BFS returns][Air kernel 4.4][0.09][voodoo-color].zip
65fps+Blue color
It has 65fps + blue color.
Download: http://biergaizi.info/pub/[BFS returns][Air kernel 4.4][0.09][65fps+blue].zip
Known Issue:
1.Random crashes/reboots.
Note1: I think it's a upstream issue.
Note2: Issue 1 was no longer exist in v0.06
Found a bug?
If you phone is crashed or auto-rebooted, please type this command after you first reboot:
cat /proc/last_kmsg > /sdcard/kernel_log.txt
Then you can find a file in your sdcard(usb mass storage) and its name is kernel_log.txt
Please reply and upload it for attach file, it can help me to solve the problem.
The source code is available from patches, sources on Github will remove soon:
http://biergaizi.info/pub/sources/
About the version number:
My zips' name are follow these rules:
[BFS returns][Air kernel x.x][x.x][voodoo-color]
.......^...............^.............^...........^
..Codename..Based on what...Main.....voodoo-color or
.....................version of....version....65fps+blue color
.....................Air kernel.....number
For example, [BFS returns][Air kernel 4.4][0.05][voodoo-color] is stand for:
the kernel's codename is 'BFS returns', based on Air kernel 4.4, the main version number is 0.05, and this kernel is a voodoo-color-kernel.
And I must talk about the main version number:
...x.........................xx..................x...............-...x.
...^..........................^..................^..................^
."Milestone".............times of.............small fix for.....complied version or zipped
version with major.....small changes......this release...version (changed kernel
....changes..........................................................config, version of gcc,
.........................................................................or fixed a broken zip file)
For example:
0.05 is stand for no major changes, and the fifth time of release with small changes, no small fix for it, just complied one time.
Q&A:
What is a scheduler?
Your computer often has 1-8 CPUs only, a CPU can do one thing in one time only. But you can run 500 processes on it. Why? Because scheduler switches processes. For example, You have 1 CPU only, and you opened 100 processes, scheduler will let one process run some time, and interrupt it, then let the next process run. So, there is a single process running only. But CPU is very fast, and scheduler switches them quickly, so you can't feel it.
How long does the scheduler let one process run? Different schedulers have different answers. But all of them are using algorithms to schedule process rational.
The history of CFS & BFS?
5 years ago, there was a scheduler called CFS. It's a very high performance scheduler, so it replaced O(1) scheduler when it merged. Facts have proved that, it is really high performance, because it can use on a supercomputer with 4096 CPUs.
On a supercomputer, a priority is very important and useful. Because many people are connecting to the supercomputer and work on it, so, you must specify the priority to people, to share the resources fairly. CFS is this kind of scheduler: it has advanced priority system. Such as group scheduled, so we can specify the priority to every single user & usergroup.
But, Does the most people use the supercomputer??
For me, I still use a computer with legacy device: a Pentium M CPU sometimes. And I use SCMs, such as a MP3 player, or devices with ARM chips, such as routers, iDevices, and my Nexus S smartphone.
By design, CFS will use on everywhere. So, it can't optimize for the device you are use. For example, we still use a supercompuer to elaborate it: priority is important on the supercomputer, but how about on the SCMs or smartphones? There are only one user at the same time. But, CFS is trying to compute the priority of the users every second!! These things are useless on low-performance-devies, and cause the low performance. It really not optimized for the low-performance-devices.
So, Con Kolivas, the designer of CFS (he just wrote some paper for it, the developer is Ingo Molnár. He also is the developer of O(1), wroto CFS before Con Kolivas. Con Kolivas is very angry for that) wrote a new scheduler for low-performance-devices, called BFS, Brain **** Scheduler. Why Brain ****? Because it very easy and simple, and kind of stupid scheduler, but it can improve performance on low-performance-devices. It removed some "awesome" design, such as advanced priority, but a stupid and simple one, etc.
It really a bad scheduler for 8-core-systems, and a terrible scheduler for 16-core-systems. But a great system with single-core and dual-core. Con Kolivas said it will never be in to the mainline Linux kernel, because it isn't a general scheduler, but I will keep update for it outside the mainline kernel code.
But now, CFS is better than before too. Lots of people think, CFS is the winner now.
Tell me something about UKSM.
This is an improvement upon KSM.
Its new features:
1. Full system scan:
It automatically scans all user processes' anonymous VMAs. Kernel-user
interaction to submit a memory area to KSM is no longer needed.
2. Rich area detection:
It automatically detects rich areas containing abundant duplicated
pages based. Rich areas are given a full scan speed. Poor areas are
sampled at a reasonable speed with very low CPU consumption.
3. Ultra Per-page scan speed improvement:
A new hash algorithm is proposed. As a result, on a machine with
Core(TM)2 Quad Q9300 CPU in 32-bit mode and 800MHZ DDR2 main memory, it
can scan memory areas that does not contain duplicated pages at speed of
627MB/sec ~ 2445MB/sec and can merge duplicated areas at speed of
477MB/sec ~ 923MB/sec.
4. Thrashing area avoidance:
Thrashing area(an VMA that has frequent Ksm page break-out) can be
filtered out. My benchmark shows it's more efficient than KSM's per-page
hash value based volatile page detection.
5. Full Zero Page consideration(contributed by Figo Zhang)
Now uksmd consider full zero pages as special pages and merge them to an
special unswappable uksm zero page.
How to tweak UKSM?
http://kerneldedup.org/en/projects/uksm/uksmdoc/usage/
You are just add BFS patch to Air kernel, the kernel is useless, everyone can do it!!!
Yes, I am a patcher and a compiler. Some kernel in XDA, also just add some patch and small hack to improve proformance. And users will not compile their own kernels, right? I'm doing the same thing. I will do more work soon.
Catalog:
Jul.24.2012 | 0.09:
1. Backported Codel queue management algorith from Linux 3.5.
Jul.23.2012 | 0.08:
1. Updated kernel source to Linux 3.0.38!
P.S: This time I didn't just copy r_data's code, I did it by myself. Because r_data is working on Jelly Bean's kernel and forgot to update this kernel!
Jul.15.2012 | 0.07:
1. New UKSM patchset.
2. r_data just updated him version information.
Jun.28.2012 | 0.06:
1. New UKSM patchset.
2. Deadline for default I/O scheduler.
3. Based on real Air kernel 4.4, not 4.3 weekly.
Jun.23.2012 | 0.05:
1.Updated kernel source code to Air kernel 4.4.
2.ext2/3 mounted by ext4 subsystem.
3.UKSM replaced KSM.
Apr.09.2012 | 0.03:
1.Update kernel source code to Air kernel 3.9.5.
2.There are not High Bigmem/Non-High Bigmem versions, because I don't want to build 4 versions. And I don't know my kernel is a what version. I think it's a High Bigmem version.
3.Source code are not on Github yet.
Apr.08.2012 | 0.02:
1.Use r_data's config, a major update!
2.Based on Air Kernel 3.9
3.Fix a BFS of bug.
4.Source code are not on Github yet!
5.[Apr.09]Quickfix: Fix the bad zip file.
Apr.05.2012 | 0.01:
1.First release.
2.Based on Air Kernel 3.8
3.BFS kernel.
biergaizi said:
Catalog
Apr.05.2012 | 0.01:
1.First release.
2.Based on Air Kernel 3.8
3.BFS kernel.
Click to expand...
Click to collapse
I'm a huge fan of Air. I don't really get the idea of how BFS can improve an already awesome kernel, but I'll give it a try, and report back asap. Thanks for your work.
EDIT: Sorry, still not as smooth as Air. Going back to v3.8. Good job anyway. Cheers!
Sent from my Nexus S
apatal said:
I'm a huge fan of Air. I don't really get the idea of how BFS can improve an already awesome kernel, but I'll give it a try, and report back asap. Thanks for your work.
EDIT: Sorry, still not as smooth as Air. Going back to v3.8. Good job anyway. Cheers!
Sent from my Nexus S
Click to expand...
Click to collapse
I'm sorry for that. Because I just want to add latest BFS to the kernels for somebody who want to try it (included me). And I use Linux a long time, I just want to learn how to compile Android kernel.
But I can't get r_data's kernel config file, and I don't know his Email address. So, I write a terrible one. This kernel has lots of bugs. I think you was saw the version number of it, 0.01
I will still improve it.
Thanks.
I did a comparison of the performance of bfs and cfs a while back using the two kernels that provided both, Matr1x and GlaDOS. CPU scores improved with bfs but graphics deteriorated and i noticed UI lags with bfs. The results are still available to view on the kernel spreadsheet (see link in my signature).
kernels ; battery ; ROM ; gov/sched
Now with summaries in the first posts. Convenient for XDA app users!
Because BFS use interrupts for multitasking, so it cause UI lags. But the overall performance should improved I think.
Your test proved it. Thanks
biergaizi said:
because bfs use interrupts for multitasking, so it cause ui lags. But the overall performance should improved i think.
Your test proved it. Thanks
Click to expand...
Click to collapse
终于! 有个中国人开始写内核了, 支持支持~~~
biergaizi said:
Because BFS use interrupts for multitasking, so it cause UI lags. But the overall performance should improved I think.
Your test proved it. Thanks
Click to expand...
Click to collapse
I am curious... You said earlier you wanted to develop a kernel to use BFS... but then you said you "found" r_data's config file.... meaning he didn't give it to you, so you haven't actually "developed" anything... so that you can add a scheduler for users who typically don't use BFS.
By Bedalus' own own testing, the BFS causes some lags in UI functions, but "may improve overall system performance".
So I am curious; when there are well developed, and tested kernels like Matr1x, Glados, Steve Garon's, and the official Air Kernel with amazing performance, speed, smoothness and responsiveness, what benefit does your kernel offer?
I am a consummate kernel flasher, and guess I would like to know your sales pitch. You know benefits, etc.
While I try many kernels, I try none without some research first. and so far, sooner than later I return to Air Kernel for it's stability and responsiveness.
Thanks
Steviemac12 said:
I am curious... You said earlier you wanted to develop a kernel to use BFS... but then you said you "found" r_data's config file.... meaning he didn't give it to you, so you haven't actually "developed" anything... so that you can add a scheduler for users who typically don't use BFS.
.......
So I am curious; when there are well developed, and tested kernels like Matr1x, Glados, Steve Garon's, and the official Air Kernel with amazing performance, speed, smoothness and responsiveness, what benefit does your kernel offer?
Click to expand...
Click to collapse
C'mon, give the kid a break, he's got his heart in the right place
It's open source and on a git somewhere; he is also crediting r_data.
So although it still isn't a very compelling kang of the Air kernel, he hasn't done anything sleazy.
Sent from my Nexus S using xda premium
motorator said:
C'mon, give the kid a break, he's got his heart in the right place
It's open source and on a git somewhere; he is also crediting r_data.
So although it still isn't a very compelling kang of the Air kernel, he hasn't done anything sleazy.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
My apology... never said he did anything "sleazy". Re-reading now, It came off a bit... well not exactly as I intended.
Just trying to understand where he is going with his project.
Again... biergaizi no offense intended. I think I am having sour grapes (jealous) because I wish I could learn to do what you guys do.
will give this one a try and maybe I can be more constructive.
Thanks Motorator for the kick in the pants..
I'm in the same boat as you in that I wish I knew how to code or at least compile some of this stuff.
Don't take it the wrong way. I didn't mean anything harsh; I just don't want young'uns like the OP to get discouraged.
Maybe this gets traction, or maybe it goes the way of most hobby coding projects. Whichever it is, we should at least let him try
Sent from my Nexus S using xda premium
motorator said:
I'm in the same boat as you in that I wish I knew how to code or at least compile some of this stuff.
Click to expand...
Click to collapse
+1 on this.
I've been hanging out in this forums and I'm getting an itch to start contributing as well, that is, contributing beyond merely test-driving their creations and actually coming out with something useful myself.
I even have the beginnings of a plan on how to go about it. Wish me luck!
apatal said:
I even have the beginnings of a plan on how to go about it. Wish me luck!
Click to expand...
Click to collapse
All the best with your plan. I hope you succeed and motivate us all to also take part :thumbup:
Sent from my Nexus S using xda premium
Nice try, and keep on going.
Steviemac12 said:
I am curious... You said earlier you wanted to develop a kernel to use BFS... but then you said you "found" r_data's config file.... meaning he didn't give it to you, so you haven't actually "developed" anything... so that you can add a scheduler for users who typically don't use BFS.
By Bedalus' own own testing, the BFS causes some lags in UI functions, but "may improve overall system performance".
So I am curious; when there are well developed, and tested kernels like Matr1x, Glados, Steve Garon's, and the official Air Kernel with amazing performance, speed, smoothness and responsiveness, what benefit does your kernel offer?
I am a consummate kernel flasher, and guess I would like to know your sales pitch. You know benefits, etc.
While I try many kernels, I try none without some research first. and so far, sooner than later I return to Air Kernel for it's stability and responsiveness.
Thanks
Click to expand...
Click to collapse
In Linux community, there are lots of people don't develop anything, but just compile the source code into binary. And do you know Zen Kernel? It just add other hacker's(not in mainline kernel)patches into it.
Why I can't do the same thing in XDA
qtwrk said:
终于! 有个中国人开始写内核了, 支持支持~~~
Click to expand...
Click to collapse
谢谢支持。看来Unicode还是很强大的。
-------------------------
Unicode is really a great characterset.
biergaizi said:
In Linux community, there are lots of people don't develop anything, but just compile the source code into binary. And do you know Zen Kernel? It just add other hacker's(not in mainline kernel)patches into it.
Why I can't do the same thing in XDA
Click to expand...
Click to collapse
Please accept my apology. Sometimes I talk out of my ass and this was one of those times.
Wish I could do what you are doing.
Sent from my Nexus S using xda premium
Just flashed this kernel and I think it's pretty snappy, I think basing it on Air Kernel is a good idea. I would say that this is something we're missing here in the NS forums is a Kernel based on BFS, I know most kernels come with the option of either, but a focused BFS kernel is certainly not a bad thing, I used to love it back in my days on the Desire.
I remember the days of compiling kernels for my Linux boxes when I was younger, I now just let updates decide what's best since I was constantly tinkering and getting it wrong.
toyface said:
Just flashed this kernel and I think it's pretty snappy, I think basing it on Air Kernel is a good idea. I would say that this is something we're missing here in the NS forums is a Kernel based on BFS, I know most kernels come with the option of either, but a focused BFS kernel is certainly not a bad thing, I used to love it back in my days on the Desire.
I remember the days of compiling kernels for my Linux boxes when I was younger, I now just let updates decide what's best since I was constantly tinkering and getting it wrong.
Click to expand...
Click to collapse
I'm using Linux everytime. And I'm carzy, I think install from source will get a high performance(because I was had a laptop with legacy hardware, compile packages with march= is really works). So, I using Gentoo, compile everything.
But I'm also a funs of Fedora.
If today I'm lazy to compile:
I will boot Fedora
Else:
I will boot Gentoo
ROM as been moved to this thread: http://forum.xda-developers.com/showthread.php?t=2134196
Re: [ROM] CM 10.1 with bionic patches (next version to be built with Linaro toolchain
Can i use trinity kernel for this rom?
Sent from my Nexus 4 using xda app-developers app
zarboga said:
Can i use trinity kernel for this rom?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Any kernel that works with CM 10.1 will work. I just posted the ones I've tested and had success with.
Re: [ROM] CM 10.1 with bionic patches (next version to be built with Linaro toolchain
What are bionic patches ?
Verstuurd van mijn Nexus 4 met Tapatalk
Ibsonic said:
What are bionic patches ?
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
They are patches that improve performance. A lot of ROMs include them. From what I understand, it has to do with code that is more optimized to our CPU than what is in AOSP.
Re: [ROM] CM 10.1 with bionic patches (next version to be built with Linaro toolchain
Is this updated to JOP40G?
How often do you plan to sync with latest CM sources and update this?
Michealtbh said:
Is this updated to JOP40G?
How often do you plan to sync with latest CM sources and update this?
Click to expand...
Click to collapse
Yes, I did a repo sync last night. Build number: cm_mako-userdebug 4.2.1 JPO40G eng.adam.20130203.024746 test-keys
I'd like to update at least once a week, maybe more, until if/when CM adds the bionic patches.
Ibsonic said:
What are bionic patches ?
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
Hi,
viking37 said:
It's a performance enhancement "built" in the ROM.
A little explanation from Morfic:
morfic said:
bionic is the "libc" of android, there are hardware optimized memcpy/memset and a few others for cortex-a9 and/or armv7-a, but also others specifically for krait, using those instead of stock bionic versions perform the same job a lot better than the more generic versions in aosp.
That affects memory throughput significantly and anything where you move data and need memory throughput using those functions will benefit from it.
there are other (math) functions that can be optimized more for the particular hardware
hope this helps
Click to expand...
Click to collapse
And an example from Simms22:
simms22 said:
{
"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"
}
Click to expand...
Click to collapse
Thank you to them
Click to expand...
Click to collapse
EvoXOhio, you should do run Antutu at stock CPU freq for see (here you are at 1.18 Ghz...), normally you have over 20 000 at 1.51 Ghz. With a compilated Linaro ROM and (for example) Trinity kernel it will be rocking!!!
But you should test with the CM kernel at stock CPU freq...
Nice, I will give it a try , well done
As far as I know it's the first fully based CM ROM with bionic patches (nevermind, it seems there is another one...).
I thanked you and give 5 stars to the thread!
viking37 said:
EvoXOhio, you should do run Antutu at stock CPU freq for see (here you are at 1.18 Ghz...), normally you have over 20 000 at 1.51 Ghz. With a compilated Linaro ROM and (for example) Trinity kernel it will be rocking!!!
But you should test with the CM kernel at stock CPU freq...
Nice, I will give it a try , well done
As far as I know it's the first fully based CM ROM with bionic patches (nevermind, it seems there is another one...).
I thanked you and give 5 stars to the thread!
Click to expand...
Click to collapse
That's weird, I checked and it's set to 1.51 gHz and the interactive governor. Maybe I'll re-run them again but force it to performance governor. Or maybe my particular phone is slower for some reason. The important part to look at is the improvement, not just the raw numbers.
Where is the other CM based ROM with bionic patches? The whole reason I made this one is because I couldn't find one.
Thanks for the feedback!
Re: [ROM] CM 10.1 (JOP40G) with bionic patches (next version with Linaro toolchain)
Awesome job! I hope the next version with linaro will be soon
Sent from my Nexus 4
EvoXOhio said:
That's weird, I checked and it's set to 1.51 gHz and the interactive governor. Maybe I'll re-run them again but force it to performance governor. Or maybe my particular phone is slower for some reason. The important part to look at is the improvement, not just the raw numbers.
Where is the other CM based ROM with bionic patches? The whole reason I made this one is because I couldn't find one.
Thanks for the feedback!
Click to expand...
Click to collapse
Re,
Interactive is not bat but try with Ondemand governor, but it's weird that Antutu see 1.18 Ghz CPU freq... maybe a conflict between an app and the buit-in CPU settings ...
Also your Quadrant score does not reflect a score at 1.51 Ghz...
Maybe try another kernel for test (Trinity kernel).
If I have time I'll flash your ROM today and test.
EDIT: here for the another CM "bionic patched": http://forum.xda-developers.com/showthread.php?t=2131378 (compiled with Linaro it seems). Contact him and discuss with him about Linaro compiling...
0.0 said:
Awesome job! I hope the next version with linaro will be soon
Sent from my Nexus 4
Click to expand...
Click to collapse
Running a build now. If it works it will be up later today.
EvoXOhio said:
Running a build now. If it works it will be up later today.
Click to expand...
Click to collapse
that is awesome man! i saw some good merges too, like the privacy notification for the Messaging app and a fix that i liked for the call statistics :good:
Thank you. So much. I have wanted to go back to CM10.1 for a while, but didn't like not having the bionic patches. Can't wait for the Linaro patches to be sorted out.
:good:
Connor Baker
P.S. I have eight thanks good sir. You are going to receive every one of them.
viking37 said:
Hi,
EvoXOhio, you should do run Antutu at stock CPU freq for see (here you are at 1.18 Ghz...), normally you have over 20 000 at 1.51 Ghz. With a compilated Linaro ROM and (for example) Trinity kernel it will be rocking!!!
But you should test with the CM kernel at stock CPU freq...
Nice, I will give it a try , well done
As far as I know it's the first fully based CM ROM with bionic patches (nevermind, it seems there is another one...).
I thanked you and give 5 stars to the thread!
Click to expand...
Click to collapse
Firstly please downsize the images or link them, it's rather massive for anyone on a slower net connection or just plain annoying (no offense).
Secondly, you are misinformed about Linaro. Linaro is responsible for sets of patches to devices which can improve your performance. This very patch, the Bionic strings patch, comes from Linaro. They also make a toolchain. That toolchain is reputed to be slightly faster than others, maybe (and I'd say 5% at most), but it isn't what gives the gains shown in your presentation, that is the patches to the kernel/AOSP (like this one). These patches include handwritten assembly code that is written directly for the processor in our phones (Cortex-A9 Krait), and multiplies the speed of those functions. Compiler tweaks just make a bad assembly code generator very slightly better.
I seek only to stop misinformation, lots of people are confused about Linaro
Ranguvar said:
Firstly please downsize the images or link them, it's rather massive for anyone on a slower net connection or just plain annoying (no offense).
Secondly, you are misinformed about Linaro. Linaro is responsible for sets of patches to devices which can improve your performance. This very patch, the Bionic strings patch, comes from Linaro. They also make a toolchain. That toolchain is reputed to be slightly faster than others, maybe (and I'd say 5% at most), but it isn't what gives the gains shown in your presentation, that is the patches to the kernel/AOSP (like this one). These patches include handwritten assembly code that is written directly for the processor in our phones (Cortex-A9 Krait), and multiplies the speed of those functions. Compiler tweaks just make a bad assembly code generator very slightly better.
I seek only to stop misinformation, lots of people are confused about Linaro
Click to expand...
Click to collapse
And you have a little misinformation about "Krait" too:
Krait (CPU)
From Wikipedia, the free encyclopedia
Krait is an ARM-based central processing unit included in Snapdragon S4 System on chips. It is a successor to Qualcomm's Scorpion CPU and has architectural similarities to ARM Cortex-A15.
Click to expand...
Click to collapse
rskyline said:
And you have a little misinformation about "Krait" too:
Click to expand...
Click to collapse
Architectural similarities. It's halfway between the two.
I say Cortex-A9 because when you're a developer, you consider the lowest case.
If you try to write Cortex-A15 assembly for the Krait, it won't work (not specifically optimized code).
The Bionic strings patch was written for the Cortex-A9.
The CPU frequency seems to be wrong but it isnt. http://www.scottsroms.com/showthread.php?447-CPU1-governor-change-with-MPDECISION-file-script
Thank you Evo, thisis exactly what I was looking for for a long time, mostly CM but with those bionic optimizations
You already got all my thanks for today.
Keep it up while I'm going to flash it
EvoXOhio said:
That's weird, I checked and it's set to 1.51 gHz and the interactive governor. Maybe I'll re-run them again but force it to performance governor. Or maybe my particular phone is slower for some reason. The important part to look at is the improvement, not just the raw numbers.
Where is the other CM based ROM with bionic patches? The whole reason I made this one is because I couldn't find one.
Thanks for the feedback!
Click to expand...
Click to collapse
Looks like you're getting thermal throttled, which is very common. Performance governor probably won't do any better.
In this thread you may find my customized kernel 3.0.x for JB 4.2.2 rom (CM10.1 and derivatives).
I hope it will be useful, and ensures better performance and battery life.
Of course, your feedback, as always, are welcome and certainly valuable.
Main Features:
-- Kernel 3.0.86
-- Compiled with Linaro 4.7.4 modded by christopher83
-- Sources synched with Cm10.1 branch
-- Built with Cortex-A8 and NEON VFP optimization flags
-- Kernel is very Stable
-- 374 mb of free RAM
-- Init.d support
-- Battery Life eXtender support ( thanks ezekeel and ryuinferno)
-- Optimized AES and SHA1 routines for ARM cpu architecture
-- Optimized ARM RWSEM (read/write semaphore) algorithm
-- Optimized asynchronous I/O latency on solid state disks
-- Optimized string and memcopy libs
--Fast Random generator (frandom) support
-- optimized LPDDR RAM timings (~10% throughput increase)
-- Dynamic management of dirty page writebacks
-- Added optimized CRC32 algorithm.
-- Voku and Dorimanx Tweak for LowMemoryKiller
-- Disable Gentle Fair Sleep for better perfomance
-- Asynchronous I/O latency
-- Lower swappiness 600----->45
-- Add -O3 optimization for modules
-- CK3 con Kolivas Tweaks
Avaible Cpu Governors
-- PegasusQ
-- ZenX
-- Nightmare
-- Ktoonservative
-- Sakuractive
-- HYPER
-- LagFree
-- AbyssPlug
-- Wheatley
-- HotPlug
-- Conservative
-- Perfomance
-- UserSpace
-- PowerSave
-- Ondemand
-- Interactive
Avaible I/O schedular
-- VR
-- Sio
-- Row
-- CFQ
-- DeadLine
-- Noop
Demon-Kernel MediaFire Folder
Sources : My sources of DemonProjects and other projects
CREDITS:
BIG THANKS FOR CHRISTOPHER FOR HIS HELP !!
Mnazim
fuss
Codeworkx for all
Ryuinferno
DOOMSDAY94
Diablo55 for helped my
Christopher83 for his toolchain and his source
voku to vokulmk
cyanogen team =D
and other =))
ChangeLog :
Code:
[B]Mangekyou-Kernel V2 03-07-2013[/B]
adjustes some file
fix name of kernel in defconfig
add [B]CK3[/B] Con Kolivas Tweaks !
[B]Mangekyou-Kernel 02-07-2013[/B]
- Change name of kernel ( because i use mangekyou image in my github and i like this name :P )
- Update LMK
- Voku and Dorimanx Tweak for LowMemoryKiller
- Disable Gentle Fair Sleep for better perfomance with good battery status
- Asynchronous I/O latency to a solid-state disk greatly increased
- Lower swappiness 600----->45
- Add -O3 optimization for modules
[B]Demon-Kernel 01-07-2013[/B]:
-Initial Release
wow first rep........
is it inspired from vampire diaries character........:silly:
just kidding.......
only on 4.2.2 aosp roms???????
for the moment...yes
biagio7xD said:
for the moment...yes
Click to expand...
Click to collapse
whokay then its time to flash new rom after a neat's release.........:silly:
will give feebback by tom may be with screenies.......
will flash on mokee......
I like the sharingan icon so much
Mangekyo sharingan of Itachi
Sent from my GT-I9100G using xda premium
Project Nexus kernel is dead?
Whats the different between this n nexus kernel??
Sent from my GT-I9100G using xda app-developers app
cyelanius said:
Whats the different between this n nexus kernel??
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
nexus kernel have more features and nexus is a perfomance kernel.....not battery friendly...this kernel is more stable and more battery friendly...this is better than nexus
EDIT: release version 20130702.... Mangekyou kernel
I had just installed your damon kernel and was ready to thank you, but saw that there was already a new version. Whooow, if you're speaking of fast, this is fast. So thanks man, and do so on I would say. Doing well. BTW, downloading Mangekyou kernel now!
Verstuurd van mijn GT-I9100G met Tapatalk
wackowizzard said:
I had just installed your damon kernel and was ready to thank you, but saw that there was already a new version. Whooow, if you're speaking of fast, this is fast. So thanks man, and do so on I would say. Doing well. BTW, downloading Mangekyou kernel now!
Verstuurd van mijn GT-I9100G met Tapatalk
Click to expand...
Click to collapse
It is just a rename, no changes yet...as seen from his GitHub...expect if he did not update it before releasing as per real world law...
Hi, at first I wanted to congratulate you on releasing your kernel, but you disappointed me again:
Misconception:
-- Init.d support [all AOSP kernel supports this, it is a feature in stock but not AOSP, already told you before]
-- Add -O3 optimization for modules [not done anywhere]
Below are the features from Slim kernel:
-- Optimized AES and SHA1 routines for ARM cpu architecture
-- Optimized ARM RWSEM (read/write semaphore) algorithm
-- Optimized asynchronous I/O latency on solid state disks
-- Optimized string and memcopy libs
-- Voku and Dorimanx Tweak for LowMemoryKiller
-- Disable Gentle Fair Sleep for better perfomance
-- Asynchronous I/O latency
-- Lower swappiness 600----->45 [it's 60]
What you did:
Compiled with Linaro 4.7.4
optimized LPDDR RAM timings (~10% throughput increase)
add Frandom v2
Added NEON compilation flag
mm: Dynamic management of dirty page writebacks
Battery Life eXtender (BLX)
add New Governor From Nexus Kernel
Added optimized CRC32 algorithm
So this kernel is very based on Slim kernel...and why didn't you state it and credit @mnazim properly?
And, removal of sources of the old Nexus kernel means you cannot share it in public anymore...didn't you learn anything since the Semaphore kernel incident?
Ryuinferno said:
It is just a rename, no changes yet...as seen from his GitHub...expect if he did not update it before releasing as per real world law...
Hi, at first I wanted to congratulate you on releasing your kernel, but you disappointed me again:
Misconception:
-- Init.d support [all AOSP kernel supports this, it is a feature in stock but not AOSP, already told you before]
-- Add -O3 optimization for modules [not done anywhere]
Below are the features from Slim kernel:
-- Optimized AES and SHA1 routines for ARM cpu architecture
-- Optimized ARM RWSEM (read/write semaphore) algorithm
-- Optimized asynchronous I/O latency on solid state disks
-- Optimized string and memcopy libs
-- Voku and Dorimanx Tweak for LowMemoryKiller
-- Disable Gentle Fair Sleep for better perfomance
-- Asynchronous I/O latency
-- Lower swappiness 600----->45 [it's 60]
What you did:
Compiled with Linaro 4.7.4
optimized LPDDR RAM timings (~10% throughput increase)
add Frandom v2
Added NEON compilation flag
mm: Dynamic management of dirty page writebacks
Battery Life eXtender (BLX)
add New Governor From Nexus Kernel
Added optimized CRC32 algorithm
So this kernel is very based on Slim kernel...and why didn't you state it and credit @mnazim properly?
And, removal of sources of the old Nexus kernel means you cannot share it in public anymore...didn't you learn anything since the Semaphore kernel incident?
Click to expand...
Click to collapse
this is based on cyanogen source....nexus is based on slim....not this
biagio7xD said:
this is based on cyanogen source....nexus is based on slim....not this
Click to expand...
Click to collapse
You said Nexus was based on CyanogenMod before this...your sources on GitHub is not supporting your speech...your old repo is gone too...
Real law means intellectual property right? Well then i have to state my opinions. One, this kernel is not earning any money or use ad like someone. Second, original creator of such code is also not earning money frm his creation so i can only see a moral intellectual property rights which is to demand this thread to credits those people properly. Third intellectual property rights is not so easy to be claim as you think. There are few principle such as improvising or this op did expanded his labour work n time to compile and the extent of his own work to actually produce this piece of kernel.
Sent from my GT-I9100G using xda app-developers app
cyelanius said:
Real law means intellectual property right? Well then i have to state my opinions. One, this kernel is not earning any money or use ad like someone. Second, original creator of such code is also not earning money frm his creation so i can only see a moral intellectual property rights which is to demand this thread to credits those people properly. Third intellectual property rights is not so easy to be claim as you think. There are few principle such as improvising or this op did expanded his labour work n time to compile and the extent of his own work to actually produce this piece of kernel.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Nope...real law as in GPL...it is different from what you are saying...I did not say he broke it just yet (athough he did before), I was just saying he has to follow GPL, that's all...faux123 got penalised a few times for not adhering to GPL...
Even there is no such law (which is not the case), can't an innocent "user" like me know what's being modified and done to my device? :angel:
Ryuinferno said:
Nope...real law as in GPL...it is different from what you are saying...I did not say he broke it just yet (athough he did before), I was just saying he has to follow GPL, that's all...faux123 got penalised a few times for not adhering to GPL...
Even there is no such law (which is not the case), can't an innocent "user" like me know what's being modified and done to my device? :angel:
Click to expand...
Click to collapse
:thumbup::thumbup: on the GPL point but well xda is at own risk afterall for what you flash isnt it?
Sent from my GT-I9100G using xda app-developers app
cyelanius said:
:thumbup::thumbup: on the GPL point but well xda is at own risk afterall for what you flash isnt it?
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
On your own risk, but what's the point of sharing if people do not know what's going on?
And what is the point with such restriction that will reduce development in xda which was meant to promote n encourage people to develop and introduce ways to put our device to better use? Op since last time in s plus thread got good reputation in his works and even now in s2. I hope this wil not stop people from giving their time n energy working on their works.
Sent from my GT-I9100G using xda app-developers app
cyelanius said:
And what is the point with such restriction that will reduce development in xda which was meant to promote n encourage people to develop and introduce ways to put our device to better use? Op since last time in s plus thread got good reputation in his works and even now in s2. I hope this wil not stop people from giving their time n energy working on their works.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
*facepalm*...I'm not gonna argue anymore...the fact is, things can be done, but get your path right... That's all I want to convey...
cyelanius said:
And what is the point with such restriction that will reduce development in xda which was meant to promote n encourage people to develop and introduce ways to put our device to better use? Op since last time in s plus thread got good reputation in his works and even now in s2. I hope this wil not stop people from giving their time n energy working on their works.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
I do not care if the op has a good reputation. The op isn't going to buy me a new device if I brick mine due to this kernel now would he? A kernel is far more important to how a device functions rather than a ROM. If there's little to no CORRECT information given, how would I know what I'm flashing is safe. You may tell me to just skip this and not flash this. But what about other people who sees the stuff in the op but isn't getting what they came for. Complying to GPL is a lot more than what you may think it is. It also helps learning and experienced people know exactly what they're getting.
Sent from my Nexus 7
Ate too much KitKat?
Download: here
Mirror: here (DontPushButtons tries to mirror as soon as new versions are released. Please remember to thank him)
F2FS help: this post/page
- features my own governor 'preservative' with 702MHz touch/GPU activity boost for responsive UI and smooth scrolling
- in kernel hotplugging (thanks to myfluxi)
- debug stuff disabled
- various safe optimisations
- built on the latest 4.4.3 source (no new source was released for 4.4.4)
- offers reduced heat and better better performance through my original bus speed mod: higher bus speeds at lower CPU speeds allows max FPS at lower CPU speeds, and keeping the CPU speed low is the best way to save power. UV is not the way! (Established 'wisdom' debunked here)
- includes kexec-hardboot patch for multiROM thanks Tasssadar
- includes Fast Charge, Gamma, and Audio-gain mods
- support for F2FS and multirom
User Reviews
- This is the only one you'll need: here
{
"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"
}
Objectives
- a high standard of performance
- as power saving as possible, but not compromising the first point
- keeping it simple
- remaining stock-like as much as possible for stability, but I'll add features if I personally want them!
Caveats - Flashing this will void your warranty, and may cause you to grow hairy man boobs, and this is the last thing anyone needs (ladies doubly so). I'm not a developer a such. I can just about program well enough in C to be able to understand what I'm doing. I've taken code from other sources and merged it in. Credit goes to mrg666, myfluxi, morfic, faux123, franciscofranco, hellsgod, ak, stratosk, and of course the hundreds of developers of the linux and android kernel source. I'm so lazy with git that often my commit history gets re-written and the original source of my cherry-picks gets lost. If this is an issue please pm me and I'll try to fix it, otherwise let me be lazy.
I think you should add... - Although I'm happy to hear suggestions, before you start you should be prepared to hear a 'no'. This is a personal project that I'm just sharing.
Source: https://github.com/bedalus/nexus4
Linaro Toolchain: [url="http://forum.xda-developers.com/showthread.php?t=2098133]click here[/url] thread by @Christopher83 (a15 4.9.x version) Thanks for the awesome work!
bedalus said:
A simple OP for simple KitKat kernel featuring nearly nothing.
http://d-h.st/LAP
- intellidemand governor with 192MHz min freq and 702MHz optimal freq
- useless frequencies disabled
- 2 core minimum when screen is on
- in kernel hotplugging
- debug stuff disabled
- various safe optimisations (take a look at the rather short commit history on github)
The Goal - to make the minimum changes to the stock source required to make a smooth experience that doesn't bake your hands.
Caveats - Flashing this will void your warranty, and may cause you to grow hairy man boobs. I'm not a developer a such. I can just about program well enough in C to be able to understand what I'm doing. I've taken code from other sources and merged it in. Credit goes to morfic, faux123, franciscofranco, hellsgod, stratosk, and of course the hundreds of developers of the linux and android kernel source. I'm so lazy with git that often my commit history gets re-written and the original source of my cherry-picks gets lost. If this is an issue please pm me and I'll try to fix it, otherwise let me be lazy.
Why's this in general? - because I'm not really developing anything. This kernel is more like my personal preference for how a kernel should be configured. I reserve the right to change my mind about what I want. I also reserve the right not to change anything for months on end.
I think you should add... - Although I'm happy to hear suggestions, before you start you should be prepared to hear a 'no'. This is a personal project that I'm just sharing.
There are lots of other fast moving and exciting kernels out there. I want this one to be more like a Daiquiri at the beach. Lazy, slow and probably asleep.
Source: https://github.com/bedalus/nexus4
Linaro Toolchain: [url="http://forum.xda-developers.com/showthread.php?t=2098133]click here[/url] thread by @Christopher83 (I always grab the latest 4.7.x arm-unknown version) Thanks for the awesome work!
Click to expand...
Click to collapse
Wow you're here too? I will try this kernel now!!
TO DO: 2 core minimum
Subscribed. Glad to see a thread for your kernel, its always nice to see a development growing good luck with furthure goals too bad you didnt left marmite as a name, it was so popular in nexus s days.
Sent from Pure Nexus⁴
Yes, a new joke name for a new era of ineptitude! Good to see you as always
Omg bedalus you are here too! Missing the Nexus S days man hahah
Sent from my Nexus 4 using Tapatalk
There's no way I'm running all those benchmarks and power drain tests again! My nexus s is still going strong in the hands of my wife
bedalus said:
There's no way I'm running all those benchmarks and power drain tests again! My nexus s is still going strong in the hands of my wife
Click to expand...
Click to collapse
Haha, nowdays its not all about numbers, its about user experience. just a two questions, do you plan to add min 1 core online and abillity to UV?
Sent from Pure Nexus⁴
Glad to see you here dude
Sent from my Nexus⁴
Wow, someone was quick off the mark. I see a download before I even finished updating the OP.
Anyway....
OP UPDATED!
- two core minimum fixed.
alen1901 said:
Haha, nowdays its not all about numbers, its about user experience. just a two questions, do you plan to add min 1 core online and abillity to UV?
Sent from Pure Nexus⁴
Click to expand...
Click to collapse
Nope to one core. See the updated op for more info.
UV is a big no-no in my eyes. Remember in the nexus s section I did those battery drain measurements? I didn't find any benefit to it, and it can make your device unstable. It's just not worth it
Nice to see you
always loved your marmite kernel on my nexus s... will try this out as soon as i can
one question: is custom colors included in this kernel?
thanks
@bedalus glad to see you here man! Loved your work on my Nexus S and now on the Nexus 4 too
qaz2453 said:
Nice to see you
always loved your marmite kernel on my nexus s... will try this out as soon as i can
one question: is custom colors included in this kernel?
thanks
Click to expand...
Click to collapse
I may have a little mess around with the colours. They look okay to me since kitkat dropped. But while I'm on the subject I think that stratosk had decent colours as default... unless I'm imagining it? Can anyone confirm?
bedalus said:
I may have a little mess around with the colours. They look okay to me since kitkat dropped. But while I'm on the subject I think that stratosk had decent colours as default... unless I'm imagining it? Can anyone confirm?
Click to expand...
Click to collapse
Yeah stock colors (which I believe is what stratosk uses) is decent enough. It's definitely way better than when the Nexus 4 was first released.
In that case I think I'll leave it for now. I'm not looking to blaze through commits like the old days
kernel update, see OP
I've begun the process of merging in the mainline commits, but I'm only merging in patches that apply cleanly, and only if they affect code that's actually being built. There's no point cluttering my git repo with commits for code that isn't going to be built in my kernel! I automated the process a little with a fun script. If you're interested take a look at the head commit in my github/maKKo_02
It took me most of the day today to get from v3.4.0 to v3.4.14 so it'll be quite a long time before I get to v3.4.70 but I'll upload a new version every 10 sets or so...
Here's another one: http://d-h.st/6Kp
I can't stick it in the OP right now because I'm using tapatalk and editing is a pain.
I've merged up to 3.4.16 and taken the hellscore zip as a base to ensure the low fq of 192 is available on first boot.
Edit: I forgot to mention that I switched to xz compression so it's reduced the zip size somewhat
Also, does anyone play sword & sorcery? Is it normal for the back to get so hot on this game?
bedalus said:
Here's another one: http://d-h.st/6Kp
I can't stick it in the OP right now because I'm using tapatalk and editing is a pain.
I've merged up to 3.4.16 and taken the hellscore zip as a base to ensure the low fq of 192 is available on first boot.
Edit: I forgot to mention that I switched to xz compression so it's reduced the zip size somewhat
Also, does anyone play sword & sorcery? Is it normal for the back to get so hot on this game?
Click to expand...
Click to collapse
Im glad u are here! A couple months ago i asked if u would do a n4 kernel, the awnser was negative... But u finally did it!
Anyway, most games heat up quite a lot the back of the phone, mainly those who require internet connection and/or GPS at the same time
(Doubletaptowake? U think its usefull enough to be added?)
sent from my NEXUS 4 tasting KitKat for the first time
So... could we say this should be the best kernel for battery life for 4.4?
Thanks a lot!! This is what I was waiting for!!
Kangaroo Kernel for the HTC One GSM: Sense ROMs
Linux 3.4.104+, with many features and improvements from Linux 3.12 and 3.14
{
"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"
}
For android 4.4.3 Sense ROMs
Based off HTC 6.09.401.5 sources for 4.4.3 Sense
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!
Naming convention
KANGAROO KERNEL MKIV IS FOR 4.4.3 ONLY (it will have _443 at the end of the filename)
JOEY AOSP CM (ckxxx): AOSP/CM based ROMs depreciated
JOEY GPE (post 4): sense based 4.4.2 and GPE 4.4.2 depreciated
KANGAROO KERNEL SENSE (kkxxx): sense based 4.4.2 ROMs and GPE only depreciated
Click to expand...
Click to collapse
Features:
Compiled with latest Linaro Christopher83 Linaro 4.9.1 toolchain
Better performance and battery savings due to the use of more efficient algorithms and updated, optimized code
Kernel is aimed at reducing heat while saving battery and increasing performance over stock
IN DEPTH FEATURE LIST IN CHANGELOG AND ON GIT
Better to look at changelog cause I miss things when I try to condense it
CPU governors (italics for default): ondemand, performance, userspace, msm-dcvs, powersave
io sched: no-op, deadline, CFQ
KANGAROO CONTROL SCRIPT IN POST #3
Can be used to control all options, plus more
Click to expand...
Click to collapse
Installation:
1. Download kernel
2. Reboot to recovery
3. Backup
*if you come from faux or tbalden please reflash your rom, you don''t need a wipe. They have some trickery with their own hotplugs so they have reomved mpdecision, so without reflashing your phone will be stuck on quad core*
4. Flash kernel
5. Reboot
*Please let it sit for ~10 mins before judging as it will need to settle down. Do not judge battery life unless you've run it through at least 3+ cycles after flashing*
Click to expand...
Click to collapse
DISCLAIMERS:
1) Excessive under/overvolting can cause damage to the internal parts of your phone. It can cause the phone's lifespan to deteriorate quickly so make sure you know boundaries
2) If you OC'ed/OV'ed/UV'ed and now are in a boot loop or your phone is slow, or acting weird or just died - it means your phone does not like the changes. Voltage control is for those who know what the risks are, know what they are doing and know how to fix it. Perhaps when you change these, test them for an hour or so before setting on boot
3) Any changes to the phone, including flashing the kernel itself is done at your own risk.
4) Every phone is differentt
5) Please DO NOT use any task killers (or additional init.d scripts), they DO NOT improve performance/battery. The kernel is designed to be used with stock settings: my settings and anything else can cause problems
Click to expand...
Click to collapse
Download latest version:
http://forum.xda-developers.com/showthread.php?t=2768222&page=53#post55839886
If you want logo options:
http://forum.xda-developers.com/showpost.php?p=54759427&postcount=5140
All previous versions:
Can now be found in changelog posts.
All older versions:
http://www.androidfilehost.com/?w=files&flid=15247
Sauce: https://github.com/poondog/kangaroo-m7-mkIV
*Please do not re upload without permission, I like to count downloads*
Changelog will be in post 2
What is not coming via requests:
- replacement for mpdecision
- additional useless governors
- aroma
- anything useless: this kernel was made for me and I shared it with a few people until now
Click to expand...
Click to collapse
With thanks to (in no particular order)
franciscofranco
faux123
anarkia1976/ak
imoseyon
flar2
teamseven
n3ocort3x
morfic
maxwen
labodj
ktoonsez
tpbklake
janarp
szezso
Synthetic.Nightmare
ZeroInfinity
Sabermod team
Stratosk
Lens-F
Savoca
tiny4579
neniick
geko95gek
brymaster
buckmarble
Click to expand...
Click to collapse
XDA:DevDB Information
Kangaroo Kernel, Kernel for the Sprint HTC One
Contributors
poondog
Kernel Special Features:
Version Information
Status: Stable
Created 2014-05-31
Last Updated 2014-10-05
Reserved
Changelog will go here
4.4.3 Sense kernel:
Code:
*****v058*****14 September
.shorten some wakelocks (for better sleeping)
.some more tweaks for better overall battery and performance
.upstream fixes and improvements to TOPOLOGY drivers (to do with queuing of tasks to individual cores, from Linaro)
.optimize TOPOLOGY further for Krait devices (neobuddy89)
.introduce BFQ IOSCHED v7r5
.introduce FIOPS IOSCHED (default)
.enable ILLINOIS to be set as default, and set it default for TCP
.introduce LINARO POWER EFFICIENT WORKQUEUES (heaps of battery savings)
.some fixes to bluetooth
.upstream backports to EVENTPOLL subsystem from 3.14+ (Efficient event retrieval implementation, thx neobuddy)
.fix some more compile warnings for better optimized code (cl3kener)
.drop i2c clock a bit more (to save battery, ref. @zeroblade1984/Samsung/OPPO
.remove some more debug (less energy waste)
.strip most debug from modules, reduce size by 90%
.enable all sleep states, based on 4.4.2 kernel tests (for better battery especially in sleep)
.remove depreciated sched sysfs since they are removed up upstream kernels and don't really do anything
.some LINARO ARM code improvements
.update to HTC 6.09.401.5 kernel source (not much really lol, a few internet related fixes)
.introduce USB FAST CHARGE (flar2, off by default)
.cleanup some HTC junk
.some improvements to LOWMEMORYKILLER from moto/upstream (to do with multitasking)
.some improvements to ONDEMAND governor for better power savings with no smoothness loss
.fixed USB DAC audio (Thanks @hq5 for testing)
.introduce KEXEC_HARDBOOT aka MULTIROM (still needs patched RAMDISK, I do not include this)
.fix compass on Sprint and Verizon (brymaster5000)
.add some more doge
http://forum.xda-developers.com/showpost.php?p=55423362&postcount=5983
*****v045*****6 September*****
.2w: change feedback slightly, now it doesn't vibrate heaps on sweep2sleep
.further updated workqueue (for better battery and efficiency)
.some network tweaks
.heaps of "under the hood" improvements (lead to better efficiency for speed/battery)
.reduce internal USB wakelocks to improve battery
.patched kernel futex vulnerability (from CM, for security)
.compress with LZ4 for faster boot speeds and built with latest binary
.updated all compressors to latest versions
.add lower GPU frequencies and scale to them (for better battery)
.upstream backports to OOM handler from 3.16+ (related to memory use, see here https://www.kernel.org/doc/gorman/ht...rstand016.html)
.optimized deadline scheduler for better use on flash
.quad core cpu stats (faux123)
.lower max i2c clock to 384MHz to save some juice, no negative effects in testing
.some general code fixes and improvements
.enable ILLINOIS tcp algorithm and set default
.enable NTFS r/w support
http://forum.xda-developers.com/showthread.php?t=2564895&page=582#post55259490
*****v027*****30 August*****
.massive improvements to the workqueue, synced with AOSP+ (franciscofranco)
.BCM4335: attempt to decrease wakelocks
.signature tweaks to SLIMBUS (me/zeroinifity)
.msm: memutils: memcpy, memmove, copy_page optimization from motorola
.use freezable blocking calls kernel wide (for more efficiency and less waste of resources, comes from upstream android)
.slimmed down kernel, stripped of some things it doesn't need
.removed some more debugging
.much under the hood tweaks (wow)
http://forum.xda-developers.com/showpost.php?p=55136831&postcount=5636
*****v021*****22 August*****
.2w: default to sweep2wake and doubletap2wake on
.backport RANDOM and RANDOM32 drivers from Linux 3.16. FULL port, not just a few patches
.patch all the way to Linux 3.4.103 latest. These include bugfixes, enhancements that have been seen fit to be merged into the mainline 3.4.y kernel
.scale L2 and CPU in sync, up to 1134MHz where the L2 maxes out. Results in smoothness at higher freqs and battery saving at lower
.begin to work on workqueue, for now just a few fixes
.drop all CPU voltages by 50mV for battery improvement and heat reduction
.begin to tweak kernel to be cooler and leaner
http://forum.xda-developers.com/showthread.php?p=54976133#post54976133
*****v006*****5 August*****
.patch upstream to 3.4.25
.introduce all 2w features from Kangaroo Kernel 4.4.2, including dt2w, s2w, bi-directional etc
.button backlight notifications (tbalden)
.tweak makefile flag optimizations based on our testing on 4.4.2 Sense
.some minor fixes and enhancements
.disabled systemrw protection (Tiny4579)
http://forum.xda-developers.com/showthread.php?p=54619213&highlight=update#post54619213
*****v001*****29 July*****
.few compiler tweaks based on what worked well on 4.4.2 kernel
.some minor code optimizations and fixes
.compile with Christopher83 Linaro 4.9.1 2014.07 toolchain
.vfp with neon hard optimization levelz
http://forum.xda-developers.com/showpost.php?p=54454303&postcount=4973
Reserved
24 August: kangaroo Kernel control script with modified mountpoints for SPRINT
Thanks for sharing.
Get out of here!!! I've been waiting on the kernel like forever. Thanks poondog!!
SENT FROM MY SENSE 6 SPRINT HTC ONE
THADDIUS25 said:
Get out of here!!! I've been waiting on the kernel like forever. Thanks poondog!!
SENT FROM MY SENSE 6 SPRINT HTC ONE
Click to expand...
Click to collapse
ok I will get out
Running nice so far
Sent from my HTCONE using XDA Free mobile app
YAYAYAYAYAYAY; I found your kernel for the gpe edition a month ago and hoped someday it will be ported for sprint, looks like my prayers are answered! Thank you!!!:laugh:
Nice thanks for sharing!!!
Frigging sweet!
Sent from my HTCONE using Tapatalk
davidkrocks said:
YAYAYAYAYAYAY; I found your kernel for the gpe edition a month ago and hoped someday it will be ported for sprint, looks like my prayers are answered! Thank you!!!:laugh:
Click to expand...
Click to collapse
Lucky you lol
slickrick54 said:
Nice thanks for sharing!!!
Click to expand...
Click to collapse
Thanks for the support, hope you enjoy
FrozenRiff said:
Frigging sweet!
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Do I remember you from the evo 3d nsfw wallpaper thread?
Sent from my Nexus 7 using XDA Premium 4 mobile app
poondog said:
kangaroo Kernel control script
Click to expand...
Click to collapse
Is this needed, or can I just use something like trickster mod? Also, thanks for supporting this device!
cygnus said:
Is this needed, or can I just use something like trickster mod? Also, thanks for supporting this device!
Click to expand...
Click to collapse
Depends what you want to do most of the time you can use trickster. But, for frequencies you'll need to use the script to cap it since o have pnpmgr enabled
Pnpmgr is HTC power and performance manager and it is responsible for boosting CPU and gou when needed. So its enabled to eliminate any stutter
poondog said:
Depends what you want to do most of the time you can use trickster. But, for frequencies you'll need to use the script to cap it since o have pnpmgr enabled
Pnpmgr is HTC power and performance manager and it is responsible for boosting CPU and gou when needed. So its enabled to eliminate any stutter
Click to expand...
Click to collapse
I just want to set governors and clock speeds, as well as modify screen wake settings and such. Is that possible without the script?
cygnus said:
I just want to set governors and clock speeds, as well as modify screen wake settings and such. Is that possible without the script?
Click to expand...
Click to collapse
Since you say clock speeds, you will need the script
However I am a strong believer in keeping the clock speeds stock. It has great battery already (I always last the day on one charge) and lowering the max freq say to 1.4GHz will extract a bit moer battery, maybe you will end up on 20% instead of 12% at the end of the day. If I want to underclock I will use the poewr saver option for CPU (assuming it works for you on this device, since some roms it doesn't work on) I know viperone has this working
imo, try without the underclocking and if you need it you will need to use teh script. its easy, I can walk you through it if you'd like
Do this got dt2w and ntfs support
Sent from my EVO using XDA Premium 4 mobile app
liljthatbol said:
Do this got dt2w and ntfs support
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes
poondog said:
Yes
Click to expand...
Click to collapse
Any reasons to not use SMARTMAX over Ondemand?
Also I am not familiar with FIOS. I always used ROW but looking for best battery life.
Quick question for the kernel guru, I noticed the kernel mentions how it increases the gpu bandwidth, the question I'm wondering if you can elaborate what it is? I googled the feature and I only came up with hits from you!
Two words...luvvv it!
Sent from my HTCONE
numus said:
Any reasons to not use SMARTMAX over Ondemand?
Also I am not familiar with FIOS. I always used ROW but looking for best battery life.
Click to expand...
Click to collapse
personally, i dont notice a lot of difference between different schedulers, but we had a discussion about it in the gsm thread here . as for the governors, i prefer ondemand, because (for me) it has the best combination of battery and performance, but some prefer smartmax or preservative more. you can also find some infos about that in the gps thread