Related
I am proud to announce Savage-Kernel to the xda forms. Currently in beta testing we worked from the latest invisiblek kernel newly undervolted, HAVS with the SBC mod.
JUST FOR @PonsAsinorem:::::: DISCLAIMER!!!! IM NOT RESPONSIBLE FOR BRICKING YOUR PHONE... EVEN THOUGH THE KERNEL CANNOT BRICK A ROOTED PHONE UNLESS YOU FLASH A BAD RECOVERY..... DON'T MODIFY THE UPDATER-SCRIPT TO FLASH THIS TO YOUR RECOVERY!!!!!! .... ALL CHANGES TO THIS KERNEL STILL MEET THE MINIMUM SPECS OF THE INC.... UNLESS YOU OVERCLOCK... WHICH IS UNDERVOLTED... WHICH IS RUNNING AT THE STOCK VOLTAGE AND SHOULDN'T HARM YOUR PHONE ANYWAY.
SENSE BASED ROMS NOT SUPPORTED THIS IS FOR AOSP ROM'S ONLY
So far the Kernel works great in conservative governor. which all the devs prefer.
Devs:
jsseidel1 (co-creator)
luisrcastillo (co-creator)
ms79723 (SBC mod updates)
lithid-cm (contributer. Updater-script guru)
Credits:
invisiblek--> base kernel!!
ms79723 --> the SBC mod.
netarchy --> smartass gov
intersectRaven --> HAVS
(credits are given to the dev's where we got some code from, may no be original designer)
CFS Builds:
Alpha1 : Click Here to download
Stable v1 : Click Here to download
BFS Builds:
Follow the github on twitter @evokernelsrc
If you like our kernel and want to support us... donate (no obligation)
Change log
Code:
[B]Alpha 1[/B]
Undervolted to 925
HAVS implemented configured for conservative
smartass added for fans
SBC Mod added (trickle Charging)
Enabled OC to 1.19 and stable
conservative governor tweaks
HAVS tweaks
smartass governor tweaks
voltage tweaks
BFS360 (latest version) and CFS VERSION!!!
Added SBC v7
BFS tweaks to ondemand gov
tweaks to interactive gov
bad ass CFS tweaks!!!!!
aggressive swap drop
misc tweaks
[B]Stable v1[/B]
SBC v7 ported from Evo (better battery life, this is a HTC mod so doesnt matter that it came from Evo)
FAQ's
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
jsseidel1 said:
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
Click to expand...
Click to collapse
What kind of battery life are you getting with this? I know results vary, but just curious.
Sent from my ADR6300 using XDA App
excited to try this
jsseidel1 said:
All answers are based off latest stable build
Which governor should I use?
Use Conservative for best battery, if you get any lag or choppy or shutter switch to either Smartass or interactive.
Which governors are tweaked?
Conservative and Smartass
I'm running smartass and having screenwake issuesm what do I do?
We suggest you set up a screen off profile of 245/384 to avoid the wake issue.
Have any more? Just ask!!
Click to expand...
Click to collapse
How did you determine that conservative is the most power-friendly?
I would post a disclaimer about the SBC mod.
Sent from my ADR6300 using Tapatalk
Am I missing the link here or has it not been posted yet? I'm excited to test.
Guys, SBC *really* isn't good for the battery. Li-Ion batteries aren't designed to use trickle charging. IMO this will kill the batteries faster and isn't worth the extra charging.
waiting to try this... dont think it will hurt my battery in the short run... who keeps phones longer than 2 years anways?
True. I've gotten better battery life off of it, but I feel like my MIUI build recently has been getting worse due to the SBC mod.
Works on gingerbread roms?
Sent from my ADR6300 using XDA App
If it's AOSP, it should, but sometimes I've gotten weird reactions using kernels that are claimed to work on all AOSP ROMs (Kingx Kernel + MIUI = no-no. Also, MIUI + Hydra = no-no).
Point being, we should probably get this clarified. I've seen instances where people have lost touchscreen functionality (though usually that's due to a failure to wipe cache/dalvik) among other issues. Until we field test this on GB ROMs or until the OP states that it works on them, we should probably refrain from flashing it over a GB ROM. You can do it if you want, I'm in no way trying to make you turn away from it; I'm just saying take it with a grain of salt.
Plus there's the SBC issue to worry about; trickle-charging has negatively affected the battery performance of my MIUI ROM, so I'm going to switch kernels whenever I go back to it. Better charging in the short run < not needing to buy new batteries in the long run (and therefore saving money).
link??????
*sigh*...
Ok, clearly I need to start citing the comments I make. Here you go:
http://forum.xda-developers.com/showthread.php?t=885476&page=25
The first post on this last page pretty much sums it up (actually, read 23-25 to sum up the main issues, it also has links to OTHER posts talking about the issues), but if you want other chronological examples of touchscreen failure or other issues you can read examples from pages 2, 5, and some places past page 15. SBC is bad news on its own, and adding overclocking to it just makes it worse. Again, you can use the kernel if you want, I'm not gonna stop you, I'm just saying that there have BEEN problems with it on other AOSP ROMs. MIUI seems to take pretty well to SBC in terms of battery, as I've seen; but, it's been getting worse as of late. UltimateDroid had a touchscreen failure (page 5) in v1; I don't believe that's been fixed yet, but feel free to correct me. MIUI had a touchscreen failure in v2 (though I think there might have been a bad flash involved, because I flashed SBC to my MIUI 12.24 at the time and it worked fine), cited page 23. Need I go on? Lol.
Point is (I've said that a lot, I know) that it does damage, multiple AOSP ROMs are getting touchscreen failure, and there's more harm than good that comes out of it.
Read: http://www.ziggy471.com/2011/01/02/overcharging-batteries/
That's a good link also. It's actually in the thread I posted, but its equally as important if not more important than my post. Good job man XD
Sent from my HTC Incredible running Carbonite Red 1.5.
Ok you all need to relax. SBC does not over charge your battery. The trickle charging is essentially the battery staying at 100% while on the charger. Lithium ion batteries have tech built into them to protect from over charging and such. SBC just means when you take it off the charger it will really be at 100%. You can't over charge aanyway. This kernel allows you to overclock but it doesn't force it. You need to choose overclocking yourself in setcpu. ... and 90% of the kernels in this forum have SBC they just either don't say it or they call it the battery fix. You can see it in their gits. On the evo forums we just call it SBC. Ill be posting the kernel today. If you don't want to use it. Then don't. It was just requested that I port my evo kernel over to the Inc. So I am.
Sent from my PC36100 using XDA App
gmichaelow said:
How did you determine that conservative is the most power-friendly?
Click to expand...
Click to collapse
Conservative by nature is more power friendly as it only ramps up the processor as requested then brings it right back down to your min.
The way we have set our Governor is to optimize the Conservative Governor to get the most speed stability and battery life out of your phone.
I just got a config from one of your rom dev's to build the kernel so this should be posted by tomorrow.
I for one appreciate what you are doing. There is nothing wrong with having a variety of kernels to choose from. If you disagree with what this dev is doing, then use another kernel. We don't need to be running them off.
Sent from my ADR6300 using XDA App
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
Here we go - What I believe is the first custom kernel built from source for GT-N7000 ICS.
READ THIS POST INCLUDING KNOWN ISSUES BEFORE POSTING!
Driving Always For User Quality - DAFUQ!!!!
This is built by applying some small fixes to the GT-I9100 update4 source base so that the stylus and charger drivers build properly.
Source code is at: https://github.com/Entropy512/kernel_galaxys2_ics/commits/entropy_kernel_main
Initramfs git is at: https://github.com/Entropy512/initramfs_galaxynote_ics/commits/master
It has been tested so far with Criskelo's XXLPY-based release, but should work with most other Touchwiz-based N7000 ICS releases. AOSP firmwares are not supported by this kernel. They may boot and sort-of run, but no bug reports will be accepted if you're running an AOSP-based firmware. No bootloader flashing is required.
Features:
See my I777 ICS kernel thread for now - it's built off of the same source base (but N7000 users should post here)
The one specific feature I should advertise here - This is built from I9100 Update4 sources. This appears to be the only source base so far for Samsung Exynos4 kernels that doesn't carry a high risk of permanent damage to your eMMC chip. (e.g. it should be safe from all of the nightmares people have encountered with ICS leaks here, however I cannot make any guarantees.)
Known issues:
Some of you are used to kernels that autoroot a ROM for you - this one will not and never will especially now that two different Superuser packages exist. Flash SuperSU or Superuser in CWM, pick your poison.
Camera preview is black
Hardware accelerated video display is not working
Because of these known issues, the primary use for this kernel is to reset the flash counter with TriangleAway (which DOES work on this kernel)
Change Log
5/27/2012:
Pulled in some changes from the N7000 source release. Wifi and speakerphone are now working with XXLPY, however - hwaccel video is still broken.
Fixing hwaccel video requires major work or just trashing everything and starting from the N7000 source release and readding features there.
5/2/2012:
Charging now works normally. It turns out some devices have an SMB136 charger, others have an SMB328 - Now both are enabled.
4/26/2012:
Call audio fixed (Note only)
Bumped first GPU step default up to 100 MHz from 66 (Note only)
Increased conservative governor freq step from 5% to 10%
4/24/2012:
Initial release
FAQ
Q: What's up with the name?
A: Since I run CM9, this can no longer be considered my "daily driver" - so the Daily Driver name no longer really applies. I haven't picked a good name yet, expect this to change with my mood. Names may get more sensible as the mental damage caused by watching the ZOMBIE ASS trailer heals.
Something goes here...
Having issues uploading the ZIP file with EGL libs... please bear with me. XDA seems to have some silly upload timeout that makes me unable to post anything larger than 8-9 megabytes.
Find them at https://github.com/koush/proprietar.../ics/galaxys2-common/proprietary/graphics/lib for now - these go in /system/lib
Edit: Hopefully the "upload from dropbox" hack worked... not sure.
Awesome great work..
Wooohoooo!!time for note to enter the next dimension!!thank yo sooo much bro!!!
Sent from my GT-N7000 using xda premium
.zip fails to flash. installation aborted
I'll post more details and documentation later this week. I'm kinda tired now.
mikeyinid said:
.zip fails to flash. installation aborted
Click to expand...
Click to collapse
What did you flash it from? I had no problems flashing it.
The upload process from dropbox may have failed - can you manually unzip it? (Edit: Just checked, seems to be fine.)
Entropy512 said:
What did you flash it from? I had no problems flashing it.
The upload process from dropbox may have failed - can you manually unzip it? (Edit: Just checked, seems to be fine.)
Click to expand...
Click to collapse
re downloaded and it flashed fine. is this a stock kernel built from source? i mean did you uv it or add oc?
mikeyinid said:
re downloaded and it flashed fine. is this a stock kernel built from source? i mean did you uv it or add oc?
Click to expand...
Click to collapse
Hey Mikey, are you using this on stunner or did you flash off of that today? Just curious before I try it on it myself.
Sent from one of my Galaxies
skyhigh2004 said:
Hey Mikey, are you using this on stunner or did you flash off of that today? Just curious before I try it on it myself.
Sent from one of my Galaxies
Click to expand...
Click to collapse
im on lp6. it takes like 2-3 seconds for my screen to turn on when pressing the power button and noticeable lag when opening app drawer in nova. definitley didnt do those things before
lag is the wrong word. there is a stutter during transitions.
mikeyinid said:
re downloaded and it flashed fine. is this a stock kernel built from source? i mean did you uv it or add oc?
Click to expand...
Click to collapse
See the I777 thread and the git commits for what's in there.
It is in general battery-optimized - Mali 3-step defaults are battery-oriented, default governor is a tuned conservative, reduce the polling interval of it for better results.
As this is built off of I9100 sources, there might be some Note-specific things missing. I never did Gingerbread kernel development on the Note. One thing is - this should not burn out your eMMC like many of the leaks can.
Entropy512 said:
See the I777 thread and the git commits for what's in there.
It is in general battery-optimized - Mali 3-step defaults are battery-oriented, default governor is a tuned conservative, reduce the polling interval of it for better results.
As this is built off of I9100 sources, there might be some Note-specific things missing. I never did Gingerbread kernel development on the Note. One thing is - this should not burn out your eMMC like many of the leaks can.
Click to expand...
Click to collapse
its usable for sure, was definitely not saying it wasnt. cant wait to see where this goes from here. i know an ics kernel from source is probably the only thing stopping official cm build.
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
disregard the stutter post lol. went intio setcpu and changed to ondemand and this thing is butter smooth. and undervolts
mikeyinid said:
its usable for sure, was definitely not saying it wasnt. cant wait to see where this goes from here. i know an ics kernel from source is probably the only thing stopping official cm build.
Click to expand...
Click to collapse
I'm working with codeworkx and xplodwild on getting that going. I need to clean up extract-files.sh and the vendor/prop repo, among a few other things. I won't have time to work it the next few days though.
If you want to improve performance, try bumping up the GPU frequency for the lowest step and reduce its staycount to 0. For battery-saving purposes, the first GPU step is a bit on the low side. I might bump it up a little, there's a BIG jump between 66 and 100 MHz.
Instead of being 166/266 MHz, it's 66/166/266 MHz. Should improve screen-on battery life.
Entropy512 said:
I'm working with codeworkx and xplodwild on getting that going. I need to clean up extract-files.sh and the vendor/prop repo, among a few other things. I won't have time to work it the next few days though.
If you want to improve performance, try bumping up the GPU frequency for the lowest step and reduce its staycount to 0. For battery-saving purposes, the first GPU step is a bit on the low side. I might bump it up a little, there's a BIG jump between 66 and 100 MHz.
Instead of being 166/266 MHz, it's 66/166/266 MHz. Should improve screen-on battery life.
Click to expand...
Click to collapse
ok, so for ~5 seconds after you unlock the phone there is a noticeable stutter during transitions, even using ondemand.
scrolling is very smooth tho, even in plume...
Try increasing the frequency for the lowest GPU step, or reduce its staycount to 0.
Another option, try conservative but change freq_step to 15. I'm probably going to change that as the default.
Where can I find a nightly build to get initial extract-files ?
Entropy512 said:
Try increasing the frequency for the lowest GPU step, or reduce its staycount to 0.
Another option, try conservative but change freq_step to 15. I'm probably going to change that as the default.
Click to expand...
Click to collapse
seems the same using conservative with freq_step at 15. the first time you open the app drawer it stutters but the 2nd and 3rd times it get smoother til it doesnt stutter any more. turn the screen off and back on and its the same again.
---------- Post added at 09:25 PM ---------- Previous post was at 08:59 PM ----------
flashed to stunner and the stutter is even more noticable.
First time posting here. And first time user of custom ROMs.
I recently unlocked my Incredible S and flashed VivoKat 4.4 by szezso on it. It is a nice build and most things work in beta quite well; however, I don't have permissions to post on that board to report bugs and ask other build related questions, like how is battery life compared to other ROMs.
I noticed I barely get 1 battery charge per day, whereas I used to get 2 days with my old gingerbread.
So I was wondering if I should go with an older ROM, feature complete, that might have better battery life. If so, which build do you recommend?
Thanks
PS: to the guys on the VivoKat thread (since I can't post there), here are some of the bigger bugs I found:
- microphone doesn't work on speaker mode
- physical buttons don't work if you disable touch-vibration on them
- main screen icons/shortcuts disappear from time to time if the apps crash
Question:
- to install today's update of VivoKat do I need to wipe everything (all data) and flash the new version, or can I update without wiping everything clean?
- I have the full "ROM manager" app, but it doesn't find updates for this build. Will that be available at some point?
(I really like the look of 4.4 on this custom ROM so it's be nice to help out with finding bugs - good work szezso)
goodrix said:
First time posting here. And first time user of custom ROMs.
I recently unlocked my Incredible S and flashed VivoKat 4.4 by szezso on it. It is a nice build and most things work in beta quite well; however, I don't have permissions to post on that board to report bugs and ask other build related questions, like how is battery life compared to other ROMs.
I noticed I barely get 1 battery charge per day, whereas I used to get 2 days with my old gingerbread.
So I was wondering if I should go with an older ROM, feature complete, that might have better battery life. If so, which build do you recommend?
Thanks
PS: to the guys on the VivoKat thread (since I can't post there), here are some of the bigger bugs I found:
- microphone doesn't work on speaker mode
- physical buttons don't work if you disable touch-vibration on them
- main screen icons/shortcuts disappear from time to time if the apps crash
Question:
- to install today's update of VivoKat do I need to wipe everything (all data) and flash the new version, or can I update without wiping everything clean?
- I have the full "ROM manager" app, but it doesn't find updates for this build. Will that be available at some point?
(I really like the look of 4.4 on this custom ROM so it's be nice to help out with finding bugs - good work szezso)
Click to expand...
Click to collapse
That's the actual battery life. With each new android version, you have a lot more processes running in the background. A lot more Google processes too
It should be ok to just flash the update, but if you run into bugs, don't report them as developers don't have a way of telling whether its from issues caused from dirty flash or from the actual ROM itself.
No it will never be available in the ROM manager app. ROM Manager does not search XDA for ROMs and VivoKat is ported by Szeszo personally.
Thanks.
That answers my questions.
And battery life improved after turning off "Location"
You can also log-out from different accounts such as fb, and so one. some of apps are eating battery. For example some email clients...
moreover, you can turn off wifi
you use Vivokat as your daily driver, that one seems still in beta stage
according to my search, i have see many kernel of the ROM is overclock feature.
but the overclock is power consumption.
for now i have using the cyanvivo,
i de-overclock his GPU and it seems become normal.
otakux said:
according to my search, i have see many kernel of the ROM is overclock feature.
but the overclock is power consumption.
for now i have using the cyanvivo,
i de-overclock his GPU and it seems become normal.
Click to expand...
Click to collapse
Overclocking uses more battery because of both freq and voltage
Simple equation is this
Power used= freq * voltage^2
So if you lower the voltage to the same as the prev max freq, then you will be using more power still. Just fyi cause I don't think it's ever been brought up around here
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Overclocking uses more battery because of both freq and voltage
Simple equation is this
Power used= freq * voltage^2
So if you lower the voltage to the same as the prev max freq, then you will be using more power still. Just fyi cause I don't think it's ever been brought up around here
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
according to my test, i just lower the frequency to the normal.
and it actually consume less power.
so de-overlock is work for me.
otakux said:
according to my test, i just lower the frequency to the normal.
and it actually consume less power.
so de-overlock is work for me.
Click to expand...
Click to collapse
Voltage changes should make a lot of difference too. But not as evident on the vivo as on big quad core snapdragons
The Gpu oc is not really overclock, it's forcing to 245mhz to up performance
Sent from my HTC One using XDA Premium 4 mobile app
i did not explain my kernel.
the kernel that i using is default overclocking.
my work just tweak it to the normal.
before tuning, in idle situation, one day could consume a battery.
after tuning, a battery could use more than one day.
i just want it back to normal.
i do not know that it is really OC, but according to my test.
the frequency is actually higher that it default.
up to 353Mhz, default is 245M.
so i could sure it is overclocking.
this data is collected in it's kernel, the real runtime data.
otakux said:
i did not explain my kernel.
the kernel that i using is default overclocking.
my work just tweak it to the normal.
before tuning, in idle situation, one day could consume a battery.
after tuning, a battery could use more than one day.
i just want it back to normal.
Click to expand...
Click to collapse
Ahh, so you've got the stock acpuclock freq table I get it
You have git public so we can understand?
Sent from my HTC One using XDA Premium 4 mobile app
poondog said:
Ahh, so you've got the stock acpuclock freq table I get it
You have git public so we can understand?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
my work just tweak back the GPU, not CPU.
i am still think that i need to tweak the CPU back to normal or not.
because i did not ask the author that i could post or not.
now the code just store in my computer.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
this is the original kernel that i used.
tesco kernel
https://github.com/szezso/T.E.S.C.O-kernel_vivo
otakux said:
my work just tweak back the GPU, not CPU.
i am still think that i need to tweak the CPU back to normal or not.
because i did not ask the author that i could post or not.
now the code just store in my computer.
---------- Post added at 12:22 PM ---------- Previous post was at 12:17 PM ----------
this is the original kernel that i used.
tesco kernel
https://github.com/szezso/T.E.S.C.O-kernel_vivo
Click to expand...
Click to collapse
kernel code is GPL, if you got it from a publicly available source then no permissions really needed
If you come up with anything that you think may be beneficial.. maybe me or @szezso can work on integrating it or you can post it somewhere
poondog said:
kernel code is GPL, if you got it from a publicly available source then no permissions really needed
If you come up with anything that you think may be beneficial.. maybe me or @szezso can work on integrating it or you can post it somewhere
Click to expand...
Click to collapse
OK, i will.
the most benefit thing to me for now is to create other branch that did not overclock the GPU.
it will help solve the battery consume problem.
And split the kernel version, i need to manually search commit to find the cm 10.2's kernel.
otakux said:
OK, i will.
the most benefit thing to me for now is to create other branch that did not overclock the GPU.
it will help solve the battery consume problem.
And split the kernel version, i need to manually search commit to find the cm 10.2's kernel.
Click to expand...
Click to collapse
Coolies
The CM 10, 10.1, 10.2, 11 kernels are built from the same source
poondog said:
Coolies
The CM 10, 10.1, 10.2, 11 kernels are built from the same source
Click to expand...
Click to collapse
yes, but now the newest master is a beta version branch.
building that kernel will causing error.
you maybe need to post which the commit url that the cm version is using
by the way, i also patch another new feature in my kernel.
otakux said:
yes, but now the newest master is a beta version branch.
building that kernel will causing error.
you maybe need to post which the commit url that the cm version is using
by the way, i also patch another new feature in my kernel.
Click to expand...
Click to collapse
Maybe the git is not up to date, have not tried compiling his CM kernel, or any vivo kernel for that matter for MONTHS
What is the error? And what is this feature
poondog said:
Maybe the git is not up to date, have not tried compiling his CM kernel, or any vivo kernel for that matter for MONTHS
What is the error? And what is this feature
Click to expand...
Click to collapse
i have compile the newer code.
the error is after boot, nothing show on the screen.
feature is about disk IO, know as BFQ.
it could use just by apply patch, no need to change code by manually
otakux said:
i have compile the newer code.
the error is after boot, nothing show on the screen.
feature is about disk IO, know as BFQ.
it could use just by apply patch, no need to change code by manually
Click to expand...
Click to collapse
Oh nice. I do have the best results on my One with fiops, deadline, row though
poondog said:
Oh nice. I do have the best results on my One with fiops, deadline, row though
Click to expand...
Click to collapse
yep, but according to my linux desktop test, bfq is more better than cfq.
Hey XDA,
my Z3 broke and my insurance gave me 500€ to get a new phone so i got the Nexus 6 32GB Blue for 490 € at my workplace.
Before my Z3 i had many different Phones like the S5, LG G3, NEXUS 5, HTC ONE m7 and more
Well what mostly use me device for is communication, A LOT (LOT LOT³) OF Fn READING (Manga and Reddit Sync) and hearing my music on the way to school/work/whatever .
I am a experienced user with roms and flashing but with this new device i just want to flash something daily driver friendly but feature heavy rom and a good battery conserving kernel
So far ive looked around for some roms available here and already choosen the
CHROMA Rom because it seems to be popular here (Not sure why ?!) (What is "Layers" ?)
and the Vindicator Kernel because it looks very promising (Not sure if its the case tho) and it has a lot of features (for a kernel..)
So what do you guys use and show me some screens of your themes becuase i like the possibilty to use the cm theme engine
Thanks
RainbowSix
For stability.. Chroma/hellscore kernel
Or use the JDX based on latest android M which is pretty stable too but you may encounter few bugs
dex2grigg said:
For stability.. Chroma/hellscore kernel
Or use the JDX based on latest android M which is pretty stable too but you may encounter few bugs
Click to expand...
Click to collapse
What bugs may i encounter ?
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
danarama said:
"Best" ROM.
There is no such thing as a best ROM. The question itself is ambiguous. "Best" is obviously a subjective term.
What I want from a ROM may well differ from what you want from a ROM, ergo - what is best for me could be worst for you.
If you are asking what the most popular ROMs are, or which ROMs people are using, you can see which threads stay around on the first few pages (and have the most posts) in the Android Development or Original Android Development forums. You can also see what other people are running by reading the What are YOU running on your Nexus 6??? thread.
If you are asking which is the most stable, being a Nexus device - they're all pretty stable.
If you are asking which is best on Battery, ROMs only affect battery if they have a feature that is badly coded. You will likely be able to read about this in the ROM threads. ROMs do not impact battery life. The only impact to battery life are your apps, your settings, how you use the phone and mostly, environmental issues such as Phone Signal.
For tips about improving battery life, please read [Battery Life Help] Troubleshoot battery issues here!
"Best" Kernel
There is no such thing as the "Best" kernel. What we all want from a kernel is different. Again, many people have the misconception that Kernels affect battery life. Let's get this cleared up. Although Kernel devs will build in optimisations and efficiencies that will improve battery life, these are very, VERY tiny...and if 1 kernel has these optimisations, they likely all have.
People will often say "Kernel x is better than kernel y for battery life". This is actually wrong. Kernels respond to user settings. Setting up the governor to favour either battery life or performance is simple enough to do, you just have to do some learning. The reason people think Kernel x is better than y is because developers set their kernels up with their preferred governor settings. This is what we refer to as out-of-the-box settings. The out-of-the-box settings for kernel x may well produce better battery results than the out-of-the-box settings for kernel y, which favour performance. The fact is, you as the user have the ability to tune kernel x or y to perform the same, be that battery or performance - so start learning how to do this yourselves - that way, you can choose the kernel based on the FEATURES you want, and not the fictional performance benefits of one kernel over another.
Hope this helps
Click to expand...
Click to collapse
Wow thats an awesome and big post with a lot of tought from you, thanks
I never asked for a best rom/kernel.. just your recommendation and im sorry that i didnt see the other thread you showed me
Do you have a tutorial for kernel settings ? because i didnt have a nexus for a long time now i never messed with kernel settings that much
And what is your opinion on my choosen rom/kernel ? what are you using and why ?
rainbowsixpro1 said:
Wow thats an awesome and big post with a lot of tought from you, thanks
I never asked for a best rom/kernel.. just your recommendation and im sorry that i didnt see the other thread you showed me
Do you have a tutorial for kernel settings ? because i didnt have a nexus for a long time now i never messed with kernel settings that much
And what is your opinion on my choosen rom/kernel ? what are you using and why ?
Click to expand...
Click to collapse
No worries, but recommendations kind of fall under "best" in a way anyway and it is all subjective.
FWIW, I like to use Slim Alpha and ElementalX kernel.
As for tweaks, it all depends what you want. Performance Versus Battery. Easiest thing to tweak is the governor settings. Some governors will allow you to change the Up Threshold. The % of CPU load before it steps up to a higher frequency. Set the up threshold high, it will stay at a lower frequency for longer, of course that impacts performance.
danarama said:
No worries, but recommendations kind of fall under "best" in a way anyway and it is all subjective.
FWIW, I like to use Slim Alpha and ElementalX kernel.
As for tweaks, it all depends what you want. Performance Versus Battery. Easiest thing to tweak is the governor settings. Some governors will allow you to change the Up Threshold. The % of CPU load before it steps up to a higher frequency. Set the up threshold high, it will stay at a lower frequency for longer, of course that impacts performance.
Click to expand...
Click to collapse
Well i am thinking to go battery but not 100%. but more like 80%
Problem is i dont know what the apps need to work fluid (or not?)
With recommendation i meant something like this
"AWESOME DUDE, I HAVE A NEXUS 6 WITH ROM X AND KERNEL X AND USE IT FOR DD AND LOTS READING
ITS WORKING LIKE A CHARM NEVER hv HAPPIER BEFORE BECAUSE THIS DOES THAT AND THAT DOES THIS"
sounds stupid, i know but maybe someone else using the N6 is in the same scenario as i am.
Got some good news 3 hrs from now i will hold a fresh Nexus 6 in my handy and now someone is offering me a GS6 32GBlack for exchange xD
GOT IT GOT IT GOT IT earlier but happy about this new awesome toy to play with